LinuxQuestions.org - Can't add "read-write" to lilo.conf

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Can't add "read-write" to lilo.conf (https://www.linuxquestions.org/questions/slackware-14/cant-add-read-write-to-lilo-conf-462253/)

Can't add "read-write" to lilo.conf

I am booting slackware, Suse, and Windows. If I boot windows normaly I get an error and it restarts over and over. But if I add read-write after Windows at boot it starts up ok. I would like to add it to my lilo.conf. If I try to add read-write under Windows I get:

Quote:

Added Slackware *
Added Suse
Added SuseSafe
Added Windows
Syntax error at or above line 66 in file '/etc/lilo.conf'

Here is my Lilo.conf:

Quote:

image = /boot/vmlinuz
root = /dev/hda2
label = Slackware
read-only
image = /boot/suse/vmlinuz-2.6.16.13-4-smp
root = /dev/hda3
label = Suse
initrd = /boot/suse/initrd-2.6.16.13-4-smp
append="resume=/dev/hda5 splash=silent showopts"
vga=0x314
read-only
image = /boot/suse/vmlinuz-2.6.16.13-4-smp
root = /dev/hda3
label = SuseSafe
initrd = /boot/suse/initrd-2.6.16.13-4-smp
append="showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3"
vga=normal
read-only
other = /dev/hda1
label = Windows
table = /dev/hda
read-write This causes an error.

I am Stuck!

Have you tried running the lilo configuration utility? It will create a lilo.conf for you based on the information you give it.

regards,
...aaron

Take it out. There is no need to tell lilo to mount it as read-write, since all lilo does is hand off to windows or ntldr (or what ever it is).

The last statement should be table=/dev/hda. Once you have lilo boot windows it will then hand over the boot processes over to ntldr. as tormented-one said. (This is kinda funny becuase I just read this in my linux administration book about 20 minutes ago.)

Thanks for all of you help. I don't seem to have this problem anymore. I installed a Lilo that has a splash screen. It said it was a modified Suse one. I'm not sure if thats what did it but my problem seems to be fixed.

Maybe it was a problem with Windows?

If it was a problem with Windows installing a new Lilo wouldn't have fixed it. tormented one was correct.