> On Tue, Sep 30, 2003 at 06:12:44PM -0400, st0rm wrote:
> > updateclient, by default creates a lilo.conf with "append root=/dev/ram0
> > load_ramdisk=1 prompt_ramdisk=0 vga=extended ramdisk_blocksize=4096"
>
> try root=/dev/ram instead of ram0
>
I've tried /dev/ram & /dev/ram0 in both specifications of the lilo.conf
file and still have the same result. In case this helps, the contents of
my lilo.conf file is below. Could this be an issue w/devfs or discover?
##################################################
# This file is generated by System Configurator. #
##################################################
# Do all the normal things lilo does
lba32
map=/boot/map
install=/boot/boot.b
vga=normal
# The number of deciseconds (0.1 seconds) to wait before booting
prompt
timeout=50
# The boot device where lilo installs the boot block
boot=/dev/ida/c0d0
# the default label to boot
default=SystemImager
# Device to be mounted as the root ('/')
root=/dev/ram
#----- Options for KERNEL0 -----#
image=/boot/kernel.systemimager
label=SystemImager
read-only
append="LAST_ROOT=/dev/ida/c0d0p6 root=/dev/ram load_ramdisk=1
prompt_ramdisk=0 vga=extended ramdisk_blocksize=4096"
initrd=/boot/initrd.img.systemimager
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
