I've just installed Slack 10 on a dual boot set-up, & when I uname on the
new install drive, it says 2.4.20 instead of 2.4.26. The kernel there is
2.4.26. The new install drive is an ide drive & the other drive is a scsi.

On 2004-10-04, Gwar wrote:
> I've just installed Slack 10 on a dual boot set-up, & when I uname on the
> new install drive, it says 2.4.20 instead of 2.4.26. The kernel there is
> 2.4.26. The new install drive is an ide drive & the other drive is a scsi.
>

It looks like you are booting the image 2.4.20 of the first install on the
scsi drive instead on 2.4.26 on the new ide install. In lilo image paths
have to be given relative to the partition that lilo is run from.

Try booting back into the first scsi install and mount the ide
partition in the /mnt directory, then edit /etc/lilo.conf "image"
path so that it points to the mounted ide image and rerun lilo.

Any editor can edit /etc/lilo.conf just make sure you are "root".

eg image = /mnt/a2/boot/vmlinuz
root = /dev/hda2
label = slak10
read-only


sorry don't know about grub as I don't use it.

cheers,
keith.

also don't forget to run "lilo" after you make your changes to
/etc/lilo.conf, so they can be written to the boot block of the hdd.
otherwise your changes wont take effect.. it took me a few hours to work
that one out ;-)

Otako wrote:
> On 2004-10-04, Gwar wrote:
>
>>I've just installed Slack 10 on a dual boot set-up, & when I uname on the
>>new install drive, it says 2.4.20 instead of 2.4.26. The kernel there is
>>2.4.26. The new install drive is an ide drive & the other drive is a scsi.
>>
>
>
> It looks like you are booting the image 2.4.20 of the first install on the
> scsi drive instead on 2.4.26 on the new ide install. In lilo image paths
> have to be given relative to the partition that lilo is run from.
>
> Try booting back into the first scsi install and mount the ide
> partition in the /mnt directory, then edit /etc/lilo.conf "image"
> path so that it points to the mounted ide image and rerun lilo.
>
> Any editor can edit /etc/lilo.conf just make sure you are "root".
>
> eg image = /mnt/a2/boot/vmlinuz
> root = /dev/hda2
> label = slak10
> read-only
>
>
> sorry don't know about grub as I don't use it.
>
> cheers,
> keith.

On 2004-10-04, slacker <user@host.com> wrote:
> also don't forget to run "lilo" after you make your changes to
> /etc/lilo.conf, so they can be written to the boot block of the hdd.
> otherwise your changes wont take effect.. it took me a few hours to work
> that one out ;-)

Hello,

Although it wasn't me who asked the original question/s, I just wondered if
I may ask what would happen if the lilo.conf file were renamed, or deleted.

I recently had a 'situation' where my lilo.conf suddenly 'forgot' about my
/dev/hdd being an 'ide-scsi'. I tried to add the line myself, but fudged it.
The cause of this 'amnesia' was probably down to me messing with /dev/hda,
which I'm sure lilo writes to. At least in my case.

As I had time on my hands, I thought I'd try reinstalling Slack 10. Thanks
to the previous installation's seperately partitioned /home etc etc
mountpoints (?), I was up and running again in no time with nothing lost,
except a few configs, which I've fixed now.

I seem to remember running a lilo command once, on Slack 10, and getting a
nice screen pop up which allowed me to config lilo right there and then,
with any 'appendages' I wanted to add. Was this because there was no
lilo.conf present already ? It was more than likely the case then, as I
always used to boot from a floppy, and leave the box running indefinitely.

I have looked through 'man lilo', and can't see anything that would've done
it, except maybe the 'lilo' command itself ? If I rename lilo.conf to
lilo.conf.OLD and then run 'lilo', would another one be created ?

I'm very reluctant to do this myself, as I don't fancy another re-install
quite so soon. Just a 'more than likely' will suffice. Thanks.

Thanks for your time.

Regards,

Pete.

lo
> I have looked through 'man lilo', and can't see anything that
would've done
> it, except maybe the 'lilo' command itself ? If I rename lilo.conf to
> lilo.conf.OLD and then run 'lilo', would another one be created ?
having issues with lilo.conf, man lilo.conf will tell you lots of nice
things
anyway the fabulous tldp generoussly offers this howto :
http://www.tldp.org/HOWTO/LILO.html

regards,

kevin

ps : google is your forever friends

On Monday 04 October 2004 05:38 am, Pete did deign to grace us with the
following:

> I have looked through 'man lilo', and can't see anything that would've
> done it, except maybe the 'lilo' command itself ? If I rename lilo.conf to
> lilo.conf.OLD and then run 'lilo', would another one be created ?
>
> I'm very reluctant to do this myself, as I don't fancy another re-install
> quite so soon. Just a 'more than likely' will suffice. Thanks.
>
> Thanks for your time.

You're looking for liloconfig, which you run as root, either from the
command line or by way of pkgtool/Setup [X] liloconfig OK.

Liloconfig creates a new lilo.conf, so if you have an existing lilo.conf,
rename (mv) it to, say, lilo.conf.backup so it doesn't get overwritten.

Have Fun!
Rich