LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 02-10-2012, 10:19 AM   #1
lukameen
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 50

Rep: Reputation: 19
Edit lilo.conf, run /sbin/lilo, but lilo won't take changes


I've got a dual boot laptop (win7 and slack 13.37). I have lilo installed in the superblock (slack root partition) and chain-load off of the windows bootloader. I just upgraded to current and the 3.2.2 kernel through slackpkg.
I've edited lilo to boot the new kernel, run lilo -v, and lilo reports that my changes have been added.

I edited lilo.conf so I can boot both kernels (old and new), but when I boot those choices don't show up on the lilo screen. For some reason, the changes won't take. The way I have my dual boot setup requires copying a new bootsect.lnx to the windows root partition whenever I make a change to lilo. Lilo still boots, I haven't had to DD my linux root to make a new bootsect file and slack still boots to the old kernel.

Any help is greatly appreciated.
 
Old 02-10-2012, 12:16 PM   #2
saulgoode
Member
 
Registered: May 2007
Distribution: Slackware
Posts: 257

Rep: Reputation: 121Reputation: 121
Quote:
Originally Posted by lukameen View Post
The way I have my dual boot setup requires copying a new bootsect.lnx to the windows root partition whenever I make a change to lilo. Lilo still boots, I haven't had to DD my linux root to make a new bootsect file and slack still boots to the old kernel.
My understanding is that Microsoft's bootloader ignores the actual contents of your partition's superblock and only "understands" the file that you created (by DDing your bootsect). If you haven't DDed your new bootsect to a file and placed that file on your Windows partition, then your Microsoft bootloader will still be loading your original LILO bootsect.
 
Old 02-10-2012, 01:10 PM   #3
lukameen
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 50

Original Poster
Rep: Reputation: 19
Thank you. That did the trick.

I've been away from slack and recently came back. I forgot a few things. In the past (with XP), if I made changes to lilo without dd-ing the bootsect, slack wouldn't boot and the screen would fill with 99's. I should have done that first.

Now I'm on to working out a few more kinks in my new install of current.

Thanks again.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
trying to update lilo on my usb hdd tells me /etc/lilo.conf wasn't found daweefolk Slackware 8 04-23-2010 02:20 AM
run /sbin/lilo after update IF you use LILO (don't know) jdblick Suse/Novell 3 12-28-2004 04:06 PM
Upgraded kernel, lilo.conf, didn't run /sbin/lilo dtashima Linux - Newbie 4 10-18-2004 12:21 PM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 05:50 PM
lilo spits out this warning during /sbin/lilo .... purpleburple Linux - General 3 08-07-2002 04:09 PM


All times are GMT -5. The time now is 09:25 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration