liloconfig freezes (Fixed)

[cpprice32]

Hello again....Just finished an install of Slackware 10. Everything went rather smoothly (had a problem with "startx" but that was because I was following the outdated "Slackware Linux Essentials" when I realized I had xorg instead of xf86".) But that is fixed now.

My only other problem is that I still have to boot from floppy. I have ran liloconfig several times but it freezes at the prompt Installing linux loader. My /etc/lilo.conf is as follows

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda2
#compact        # faster, but won't work on all systems.
prompt
timeout = 300
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda2
  label = Slackware
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
  label = Windoze
  table = /dev/hda
# Windows bootable partition config ends

any ideas?

[valan]

Make sure your lilo.conf is all set up right, 'man lilo.conf' will tell you all about that. Then just type 'lilo', when it's done then reboot and be sure it worked. No need to use any 'make it easier' tools for something so simple.

[cpprice32]

Fixed this problem. When I was running liloconfig I was scared off by the warning of installing the loader in the MBR may be unsafe so was choosing the safest choice.

This is probably the biggest problem that new users like myself run into, we are so paranoid of trashing our systems that we forget most of the time that we have a boot or rescue disk that we can use to fix most of our catastrophies.

[U-Turn]

You aren't the first to run in to this problem. As often as it crops up, I think liloconfig should contain a notice informing the user, if he plans on installing LILO to the superblock, that the superblock is actually the first data block on / and that / will need the boot flag, which will need to be reset by using fdisk or cfdisk, in order for it to work.