Steve Jeppesen wrote:
On Thu, 10 Feb 2005 00:24:04 +1300 SnapafunFrank <[EMAIL PROTECTED]> wrote:
Mikkel
<Big SNIP to focus on problem- made by Frank>
#other=/dev/ide/host0/bus0/target1/lun0/part2
# label="linux90"
# table=/dev/hdb
# image=/boot/vmlinuz
# root=/dev/hdb5
# initrd=/boot/initrd.img
# append="noapic devfs=mount acpi=ht splash=silent"
# vga=788
# read-only
<End of first big SNIP>
<Bit of a SNIP here - Frank >
It isn't that it is confusing because it raises question that my technical logic trips up and that is what may make things confusing. Keep the input coming as it is most helpful.You are correct that "image=/boot/vmlinuz" probably wouldn't work on your system because that is typically a link to which ever kernel version is installed. Your system appears to be setup to not use such a link, so you would just have to show it as "image=/boot/vmlinuz-2.whatever.version.youhave"
then you would also need to modify "initrd=/boot/initrd.img" to point to what ever version of initrd you would be using, like your other entries in lilo.conf do.
if you were to copy vmlinuz, initrd, config, etc. (not exactly sure off the top of my head which files you need to copy out of /boot - anybody know off hand?) from your 9.1 install IRC to which ever partition that controls your bootup, then instead of;
other=/dev/ide/host0/bus0/target1/lun0/part2 label="linux90" table=/dev/hdb image=/boot/vmlinuz root=/dev/hdb5 initrd=/boot/initrd.img append="noapic devfs=mount acpi=ht splash=silent" vga=788 read-only
how about this;
image=/boot/vmlinuz.your.version.here label="linux90" root=/dev/hdb5 initrd=/boot/initrd.your.version.here.img append="noapic devfs=mount acpi=ht splash=silent" vga=788 read-only
other than that, I would tend to suspect that maybe root=/dev/hdb5 may need to have a different partition number instead of 5.
Hope I am not too confusing!
< Brought over from another reply >
>I still don't know how you installed Linux on the second drive. But there are a couple of things you could do. One would be to something like this:
*** I had this hdd drive only to start with and successfully got dual booting with it before consigning it to be slave when I went to update to Mandrake10. ***
*** Now everything Mikkel writes here has finely woken me up to what needs to be done and I look forward to the challenge because Mikkel has 'hit the nail on the head', so to speak.
As Mandrake 9 was installed whilst the slave was the only hdd on my system then of course everything in the config files " points " to hda and of course will need to be changed. So where do I start and what do I look for once I have booted into this system ?
[ This is an exercise only for me and not a mission critical requirement so I will, hopefully with the help offered here, take this one step at a time and if it is worthwhile and others agree, I will post it to the TWiki as a possible system recovery idea.]
Anyway, with sleeves rolled up I venture forth.
Here are the files I need to investigate that I know about to date - please add others as you think of them. I'm of course referring to the hdb files only here.
/etc/fstab
/etc/lilo.config
>mkdir /boot-9 >mount /dev/hdb2 /boot-9
>Use this in lilo:
>image=/boot-9/vmlinuz label="linux90" > root=/dev/hdb5 > initrd=/boot-9/initrd.img > append="noapic devfs=mount acpi=ht splash=silent" > vga=788 > read-only
>Add a line in /etc/fstab to mount boot-9 in the future. >(Coppy the line for /boot, and change > /boot to /boot-9 and /dev/hda2 to /dev/hdb2)
>Now, if /dev/hdb was /dev/hda when you installed MDK9, >then you will have to edit /etc/fstab on that version, >and change everything that refers to /dev/hda to >/dev/hdb.
>Another way to do it is use:
>other=/dev/hdb > label="linux90"
>Then, in 9.0, change /etc/lilo.conf so that it installs in the MBR of the second drive.
Hmmm.... Not sure I can do this without actually having MDK9 running at the time otherwise to my way of thinking, it will install directly to the master MBR surely?? Even then I'm not sure how to control running /sbin/lilo to be sure it actually installs onto the hdb MBR.
>"boot=/dev/hda" becomes "boot=/dev/hdb".
>What happens then is when you pick "linux90", you get a second boot screen.
>Again, if you installed 9.0 when the >drive was the first hard drive,
>you have some editing to do. Both in /etc/fstab, and /etc/lilo.conf.
>You will also need to run lilo when in 9.0 to update the boot loader >on the second drive.
>Can you boot 9.0 now, or do you need instructions >on how to mount the partitions, and make the changes?
I haven't gone this way yet Mikkel because I think things will only fall over until all changes to config files are made.
I do like your idea of having the second logon screen option and will venture that way first once files are changed.
One thought also for now so as to keep my options open, will " # ln -s " my MDK9 vmlinuz from within the master hdd /boot partition offer a way?
I'm not sure that the link would cross hdd's at this point of booting a system so thought I'd just ask. ( Once the config files are dealt with of course ).
Another issue I may need to face is the fact that I have updated my nVidia driver - is it possible to recompile a kernel on another harddrive? I think I ought to be able to re-configure the kernel from " text " mode once I have access to the old installation - just a'wondering again.
Well that ought to do for now, back to forming a project list so as to not waste any of the valuable help given here.
A great way to get to know more of Linux and my own system even.
-- Newbie Seeking USER_FUNCTIONALITY always!
Regards
SnapafunFrank
Big or small, a challenge requires the same commitment to resolve.
Registered Linux User # 324213
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
