Contributed by pitrh on from the not-your-grandpas-rfc1149 dept.
And it seemed like only moments later that Raf Czlonka was the first to report on the misc@ mailing list that his pre-ordered OpenBSD 5.7 CD set had arrived.
Even if you hadn't preordered, you still have a chance to order your CD set and other swag by visting the OpenBSD Store. If you want to support the project financially in other ways, the Donations page is, as always, a good place to start.
(Comments are closed)
By Renaud Allard (renaud) renaud@allard.it on
By Anonymous Coward (203.166.247.148) on
Comments
By d.c. (d.c.) on
By Stéphane (78.121.195.36) on
Comments
By Marco van Hulten (79.94.93.163) marco at hulten.org on http://www.advogato.org/person/hulten/
CD2 does not appear to be bootable on my amd64 system, while CD1 is. Possibly because the filenames are capitalised on the second CD (appears like this under GNU/Linux):
CD1:5.7/i386/bsd.rd
CD2:5.7/AMD64/BSD.RD
Is this a known issue with CD2?
Copying floppy57.fs to a floppy as suggested in the booklet comes up with an installation that does not certain hardware, among which my harddrive. (To be precise, I did a convert and copy of FLOPPY57.FS to a usb stick, as I do not have a floppy drive and the files on the CD are capitalised.)
Comments
By Anonymous Coward (72.95.251.217) on
Yes. See
Comments
By Richard Toohey (203.97.197.6) richardtoohey@paradise.net.nz on
> Is this a known issue with CD2?
>
>
> Yes. See
>
>
> http://marc.info/?l=openbsd-misc&m=143118582926916
>
Now confirmed to be an issue with all CD2s shipped:
http://marc.info/?l=openbsd-misc&m=143170159327247&w=2
Comments
By Marco van Hulten (hulten) marco at hulten.org on http://www.advogato.org/person/hulten/
By Richard Toohey (203.97.197.6) richardtoohey@paradise.net.nz on
But unfortunately has the ALL UPPER CASE FILE NAME problem with amd64. 8-(
Comments
By TOOGAM (TOOGAM) on http://toogam.com and http://cyberpillar.com
My solution was to press ! during the installer, to get to a shell prompt. Then make a local directory, and use the "ln -s" to create a bunch of symbolic links that had the expected filenames, pointing to the files that were accessible using other names. Note that not all of the files should be lowercase; specifically I recall that INSTALL.* should not be. The resulting OpenBSD installation worked just fine.
Of course, those symbolic links were being written to a directory I made on a memory filesystem ("RAM drive"), so those links got lost during the reboot at the conclusion of the successful OS installation. But, losing those links was rather acceptable, because there was no further need for them after that point.
Making those links was a tad bit of work, but less painful than downloading from the public servers (over a rather slow Internet connection, when somebody was waiting on me).
Did you check whether the same thing seems to happen when inserting the i386 disc?
By Anonymous Coward (72.95.251.217) on
I have the same problem. The AMD64 CD won't boot, either. Apparently, this is the "production problem" that delayed the shipment of the CDs. See
By Anonymous Coward (70.51.224.246) on
>
> But unfortunately has the ALL UPPER CASE FILE NAME problem with amd64. 8-(
Arrived in Canada, same deal. Contacted the OpenBSD store and they will be sending me a replacement once available. The company which burns the cds will be compensating OpenBSD. If you have a bad cd2, contact the store so they can put your name on the list to be resent a proper cd2 once they become available.