SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
i was at one of my friend's places getting slackware 9 setup on his computer and i encountered an odd problem: when i set about the usual procedure to compile a fresh kernel, lilo doesn't update the boot listing correctly (even though i "updated" it by running /sbin/lilo after the kernel install). after i ran lilo it even gave me the "everything has updated fine" message (i.e. added new.slack old.slack). once i select slackware at the OS bootloader (a la windows XP) it gives me the original lilo screen w/ only one choice: Linux. the new.slack and old.slack selections that were supposed added are mysteriously absent.
perhaps this has something to do with lilo being on his superblock (it's on my MBR b/c i don't dual boot, so no problems here) and his running a dual boot w/ windows XP. when we did the dual boot install of slackware 9, we followed the usual procedure of copying the first 512 bytes of the root linux partition to disk, copying that to windows, adding crap to boot.ini, and having the windows OS loader take care of things.
i tried to use liloconfig to "recycle" the lilo.conf file to superblock, but i suspect i have no idea what's going on => big surprise, this didn't work. suggestions?