Forum Home
Press F1
Thread ID: 48802	2004-09-01 10:16:00	Yoper Installation	Murray P (44)	Press F1

Post ID	Timestamp	Content	User
267999	2004-09-10 12:59:00	Yes I can browse the Mepis directories but the etc/lilo.conf file had a padlock symbol on it because yours truly wasn't using File Manager in super user mode ?? > You need to copy Mepis's kernel (and initrd if it uses one) into to Yopers > /boot directory. You had it pointing to the Mepis /boot partition. Do I need to actually copy it to Yopers /boot or is that what the lines in /lilo.conf do. This is the actual and real lilo.conf from Mepis, the bold is what I intend to place in Yopers .conf: map=/boot/map bitmap=/boot/mepis.bmp bmp-colors=2,,,3,, bmp-table=90p,160p,1,15,17 bmp-timer=400p,148p,3,2, boot="/dev/hda" backup=/dev/null timeout="150" prompt default=linux image="/boot/vmlinuz-2.4.22" vga=791 label="linux" append="nomce hdc=ide-scsi" (if I add: ,splash silent" to the end of this line it will work?) root="/dev/hdd6" image=/boot/vmlinuz-2.4.22 vga=791 label=failsafe append="nomce " root=/dev/hdd6 image=/boot/memtest86.bin label=memtest other=/dev/hda1 label="MSWinhda1" table=/dev/hda image="/dev/hdb1" root="/dev/hdd6" append="nomce hdc=ide-scsi" The modular bit in the previous one BTW, was from a Lilo How To I read. How come you have a 2.6.8.1.6.img for YOS on some lines whereas on others and mine show 2.6.8.1.3 have you been fiddling? Thanks for your help. I promise I will not do anything drastic, until the morning that is. Cheers Murray P	Murray P (44)
268000	2004-09-10 13:02:00	Cripes, -mepis at end of image= line and label= should be mepis where applicable not linux (although I gather the latter is not critical?) Cheers Murray P	Murray P (44)
268001	2004-09-10 13:26:00	> Yes I can browse the Mepis directories but the > etc/lilo.conf file had a padlock symbol on it because > yours truly wasn't using File Manager in super user > mode ?? Ah yes, that might account for that :p. Alternatively, you can just open up a konsole on the Mepis partition and "su -" to root, and enter in: cat /etc/lilo.conf This command will just display the contents of lilo.conf in the konsole window. > > You need to copy Mepis's kernel (and initrd if it > > uses one) into to Yopers > > /boot directory. You had it pointing to the Mepis > /boot partition. > > Do I need to actually copy it to Yopers /boot or is > that what the lines in /lilo.conf do. You need to copy vmlinuz-2.4.22 to Yoper's /boot and then edit lilo.conf so that it references that location for the Mepis kernel, and not its original location on the Mepis /boot partition. I'm sure someone can explain this more technically about the boot process and what gets mounted first. This is the only way I know how to dual boot Linux OS's. > This is the actual and real lilo.conf from Mepis, the > bold is what I intend to place in Yopers .conf: > image="/boot/vmlinuz-2.4.22" > vga=791 > label="linux" <<<<----- you can rename this to say "Mepis" if you like > append="nomce hdc=ide-scsi" (if I add: ,splash > silent" to the end of this line it will work?) > root="/dev/hdd6" append="nomce hdc=ide-scsi" <-- this is because Mepis still uses a 2.4 series kernel, and the scsi reference is no longer necessary under a 2.6 series kernel. You will need to keep this line for Mepis (unless you wish to update Mepis's kernel to the latest 2.6 kernel :D). I'm not sure what the "splash silent" option will do - see what the others say. > The modular bit in the previous one BTW, was from a > Lilo How To I read. How come you have a 2.6.8.1.6.img > for YOS on some lines whereas on others and mine show > 2.6.8.1.3 have you been fiddling? Of course I have been fiddling! :D This is actually a updated kernel I have installed, so my lilo still shows the old original kernel which I can choose to boot into if I wish. If you use synaptic you can find the newer kernel and install it if you wish as well.	Jen C (20)
268002	2004-09-10 13:39:00	Thanks for that Jen . That's pretty clear now . The "splash silent" bit I assumed was to do with the splash screen ie, Mepis's own splash screen won't show at boot in lieu of Lilo's or just to speed the process without extraneous bits laoding . I was just trying to figure if you could append it to the append string but I'll leave it for another time when I actually understand the consepts behind all this rather than learning by rote as I'm largely doin at the present time . I've updated the Synaptic files but as yet have not installed anything as I was wanting to do my house keeping first in an effort to take a more measured approach this time around . Cheers Murray P	Murray P (44)
268003	2004-09-11 03:26:00	Telling lilo (installed from Yoper) to look for kernel files in /mnt/mepis is a Bad Idea. And it can't work. ;-) "Why?", he asks. Because /mnt/mepis (in the Ypper file system) is just a "mount point." It doesn't get a disk partition mounted until after Yoper has booted. ;-) There's nothing there when lilo does its booting thing. :-( I can't think offhand of any "nice" way to do it rather than copying the mepis boot stuff into the Yoper boot space. I've found enough scope for cockups with one distribution per machine, so I've never goon looking for trouible. I'd definitely make a (Yoper) directory /boot/mepis to copy the files to. All lilo operations will have to be done from inside Yoper -- so delete /sbin/lilo from mepis for safety -- I think I would use a boot floppy for mepis. :D	Graham L (2)
268004	2004-09-12 01:40:00	> Telling lilo (installed from Yoper) to look for > kernel files in /mnt/mepis is a Bad Idea. And it > can't work. ;-) > > "Why?", he asks. > > Because /mnt/mepis (in the Ypper file system) > is just a "mount point." It doesn't get a disk > partition mounted until after Yoper has > booted. ;-) There's nothing there when lilo does its > booting thing. :-( Ah! I see, said the blind man. I have obviously completey misinterpreted the How To because I thought that was the very problem (plus having my MBR on a different partion to any OS) I was overcoming. So, instead I was making about to do avery good job of creating a balls up :D > I can't think offhand of any "nice" way to do it > rather than copying the mepis boot stuff into the > Yoper boot space. I've found enough scope for cockups > with one distribution per machine, so I've > never goon looking for trouible. I'd definitely make > a (Yoper) directory /boot/mepis to copy the files to. > All lilo operations will have to be done from inside > Yoper -- so delete /sbin/lilo from mepis for safety > y -- > > I think I would use a boot floppy for mepis. > :D I can see the sense in using a safety first boot floppy approach. I imagine I will need to reacquaint myself with rawrite. I can also feel some more research coming on, no worries, I'm enjoying Yoper and haven't missed Mepis too much so can wait a bit longer for the right result. Cheers Murray P	Murray P (44)
268005	2004-09-12 02:55:00	> I can see the sense in using a safety first boot > floppy approach. I imagine I will need to reacquaint > myself with rawrite. I can also feel some more > research coming on, no worries, I'm enjoying Yoper > and haven't missed Mepis too much so can wait a bit > longer for the right result. Me thinks you are being very good and reading every manual and how-to out there, but have ended up over analysing this. To add Mepis to the Yoper LILO bootmanager, you just need to copy over Mepis's kernel to Yopers /boot and then edit Yoper's lilo.conf to reference it. Then run /sbin/lilo on Yoper to get LILO to recognise the new lines and then reboot the machine - should take 10-15 mins tops. :) If you want to give me root ssh access to your machine, I could do it for you and also reboot your machine at the end ]:) :p If you don't have a boot floppy for Mepis, it is easy to make. Whip open a root console on the Mepis root partition and enter in: uname -r (this will give you the current running kernel) Then enter in: mkbootdisk <enter kernel name from previous command > Just pop a floppy in at the prompt and wait until it has finished making the boot floppy. Occassionally you will get an error about the files are too big for the floppy - hopefully this won't be the case for you. :)	Jen C (20)
1 2 3 4