[RESOLVED] Broken link beagleboard bootloader?

[ggeorgan]

Thank you for your response.
$this->bbcode_second_pass_code('', 'bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
')
This is what I get in practice.

[WarheadsSE]

Ah, you said bzip! not gzip! tar xzf

[ggeorgan]

That was with $this->bbcode_second_pass_code('', 'tar -xjv') as in the Angstrom reference.

trying with tar -xjf I get
$this->bbcode_second_pass_code('', 'tar: Multiple archive files require `-M' option
Try `tar --help' or `tar --usage' for more information.')

[ggeorgan]

Same with $this->bbcode_second_pass_code('', 'tar -xzf').
$this->bbcode_second_pass_code('', 'tar: Multiple archive files require `-M' option
Try `tar --help' or `tar --usage' for more information.
')

[ggeorgan]

Just to keep track, I am trying to extract the file ArchLinuxARM-omap-smp-latest.tar.gz

[kmihelich]

If you're having trouble at the extraction stage, I very highly unquestionably recommend that you search out some Linux primers on the internet. If this is an issue, everything else you want to do with Arch will simply crush your abilities.

This isn't a personal attack, it's a serious recommendation.

[ggeorgan]

I totally agree ! I have seven years' user's and installer's experience with embedded linux and with Linux distros in general including Arch, but nowhere have I found it so difficult to perform such a simple task.
First, there is the issue of file integrity. Please note that I have had no response from any user on that. What is the correct md5sum of the file? If it is the one I get, why is a different md5sum posted on the downloads page ?
Second, assuming extracting the file is such a simple task, why have I spent two days looking for information on the internet and nobody seems to have gotten to a simple answer ? Perhaps nobody has actually tested extracting that particular file. It is true, however, that I am not equipped for the complete mysteries of tar. Perhaps in a couple of years.
Thank you very much for your recommendations.

[kmihelich]

I don't see how in seven years of experience issues with a tar file come up. It extracts fine for everyone else, it extracts fine for me, and as a point it just extracted fine on the server hosting the file. This is the only reported problem. There are no mysteries with tar, it's very simple; and with your stated background its operations should be ingrained to the point of muscle memory.

The correct md5 is c42f4e0038affe0e5deebab0718df135, which I've updated on the page now. Things get out of sync sometimes.

[ggeorgan]

No need to get upset, I am just as mystified as you are. But I am not questioning your background and there was something really amiss, although of minor importance. Maybe updating my development system (it runs a debian-sid derivative and is sometimes unstable) will do the job. On the other hand, extracting files for new installations is a job most users do rather infrequently. Plus it really is easy most of the time. This is why the rare snag is so irritating. No big issue, if one of many happy users gets unlucky.