> Just FYI I happen to have here a somewhat
> >unusual machine, :-) which is using milo, and which at this moment
> >can boot various variants of Linux from
> >/dev/sda2, /dev/sdb2, /dev/sdc2, /dev/sdc7 and /dev/sdc10
>
> Well that's marvelous and reassuring to hear. You make the notable point
> that they're all Linux partitions.
Somehow I suspect that we are talking about different stages of booting
here. If I boot Linux then I expect that its root partition will
be of a Linux type. :-) But kernel can be actually loaded from
any other partition/device which is readable to milo. It DOES NOT
have to be a root partition; even if usually is for the sake of a
convenience and sanity.
Are you failing trying to load milo? Your description of problems
is quite incomplete and confusing. Quoting actual error messages
(and what produced them) usually greatly help others to understand
what you are talking about. Otherwise you leave everybody guessing.
> I hoped for dual-boot Linux & NT4 without
> drama.
Yes, there is in reality nothing special to that. The same partition
which is used by your console to load an NT loader can hold milo, and
its first stage loader, and even your kernel image if you so desire.
Making a new directory for that stuff is recommended for organizational
reasons but not required. Your Linux root partition has to be somewhere
else. :-)
Were you attempting to load stuff from an NTFS partition - by any
chance? This will not work. Your firmware, and milo, do not know that
file system type.
> Milo says built on 2.0.30
This should not matter as long as you are not attempting to get milo to
load something from an ext2 file system formatted with a block size of
4096 and/or sparse superblocks. You want some cutting-edge stuff then
visit http://www.stefan-reinauer.de/Milo/
Michal
-- To unsubscribe: send e-mail to axp-list-request@redhat.com with 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail version 2a22 on Tue Aug 1 04:53:11 2000 PDT
Send any problems or questions about this archive to webmaster@alphalinux.org.