SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
NUTS. Lilo still errors on install, but my boot manager, GAG (see freshmeat.net) does not seem to mind. But unfortunately the boot of the new kernel halts at the line "Releasing free kernal memory, 124xx" or something like that.
So far 12.0 has been a real challenge, but I will work it out....dedicated slack user.
Still using LILO, but I finally got it to go. Hmm, will have to look thru the source code for lilo, someone may have changed it to limit the size of the "/" partition, for some unknown reason.
I state this because the original error for lilo on v12 occurred on a ~40 gb partition, when I attempted to reduce it to ~20 gb, same error. Then when I reduced it to ~10 gb, no problem, installed and is up and running.
What an 'undocumented' issue, very MicroSoft like. Come on guys, document all, especially open source.
I finally have had more time to attempt some things to resolved my failed lilo install on v12.
I moved the swap partition to the end of the drive instead of the beginning and TA-DAH !! It worked.
Betting they recoded/fell back to having lilo in the first sectors of the drive, not sure why though.
Oh well, in case anyone else has the same issue, create your /boot or / partition at the beginning of the drive or take your chances and use the MBR (yuck !!!).
I had no lilo problems, but I did have problems booting off the DVD and CD since I have an old BIOS.
I usually create a 2 gig / at the beginning, then the swap then the rest is one big partition and mark it for the LVM. Then in the LVM, I partition out a /usr, /opt, /var, /home and whatever else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.