[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (alpha) YES, we have working boot-floppies

Falk Hueffner wrote:
> Well, things may be different on Ruffian since it has it's own ARC
> variant. I'd then have to include some kludge to add an x86 bootsector
> to the image.

Well, Deskstation Ruffian is the only ARCS BIOS platform to
bother, as Linux never did run on Deskstation Raptor, right?
Just for the records: Ruffian is 164UX with ARCS BIOS, Raptor
is PC164 with ARCS BIOS, correct?

> Hm, I'm open for suggestions about which MILOs to take.  Should I just
> use those from potato?  I'm not sure they understand sparse
> superblocks...

Ummm, no they don't. More precise: I played around a while with
potato Milo and a PC164, creating new file systems on spare space
on one of my hard disks, and got the following results:

PC164 Milo from potato
- is not able to read from a file system with sparse superblocks
- is not able to read *any* filesystem created using potato (I
  tried "mkfs -O none <device>")
- is able to read from a ext2 filesystem created from within my
  "somehow" updated RedHat 5.1(!) installation (sorry, I have
  nothing "in between")

That leaves us ARC users (if it wasn't a pure coincidence that
Milo-2.2.17 didn't work for Don Spoon on his XLT) in a rather
weird situation:
- All "Reinauer" Milos do not work.
- Milo from potato does work, but can't read "up-to-date" ext2
  filesystems (maybe some other change before the introduction
  of sparse superblocks is to be blamed or maybe current impls
  simply are not able to create backwards compatible filesystems).

Other suggestions?
Stefan Schroepfer

Reply to: