> Last week I was having troubles booting my alpha LX164 system into the
> install program. I've figured that all out.
> Now, I can't figure out what to type from the MILO> prompt to start up the
> O/S for the first time.
> milo finds the various partitions (sda1, sda2, etc), but I don't know what to
> type to boot (or at least nothing I type is recognized).
Typing things at random is surely not the way to make something to boot.
It would be good to know what you really installed.
> I've tried such things as:
> boot sda2:/vmlinux.gz root=/dev/sda2
If your /boot is not mounted from a separate partition (not a smart move
for various reasons) and your kernel and related files resides in /boot
then this has a zero chance to work. If these are separate partitions
then "sda2" in both places cannot be right.
Quote:> boot sda2:/boot/vmlinux.gz root=/dev/sda2
Are you sure that you have /boot/vmlinux.gz file? Remember that
milo does not handle symbolic links. Likely this is something
like /boot/vmlinux-2.4.... whatever. /etc/milo.conf may help
to reduce typing and will make the whole setup more flexible.
Quote:> boot sda2:/boot/vmlinuz root=/dev/sda2 etc.
Moreover if your kernel loads drivers to access your hard disk
from initrd then you will not have much of luck without it.
If you are using ext3 filesystem then drivers for that may reside
in initrd as well.
I do not know if milos are capable of getting initrd loaded; I heard
mixed reports about that. If not then you need a custom kernel
to get your system started from a hard drive.
Quote:> Can anyone provide some guidance?
As it was suggested previously a smart move would be to use SRM instead
if you do not have really good reasons to do otherwise.
Quote:> I've tried using cd and ls to poke around
> the disk, but ls doesn't seem to work properly.
I doubt it. If this is really the case then get better milo. But you
can boot your distribution media in a "rescue" mode (or switch to a text
console), mount your disk partitions and poke around. If you will do
mounting in a reasonable way then you can use 'chroot' to "switch" to
your installed system and take over from there.