Adding DSL to Linux computerForum: HD Install Topic: Adding DSL to Linux computer started by: dtf Posted by dtf on May 17 2006,17:41
I would like add DSL to a computer that currently dual boots suse and windows xp. It uses grub as the bootloader. I will be installing a new hard drive to hold the DSL-N image. I want a frugal type installation. I understand the basics of partitions etc. I think I understand that I add an item to the grub for DSL but I am not sure how and what images I should copy to the HD. I don't think I can use the installation menu because I am afraid it will overwrite the existing grub-menu. So is there an easy way to do this or a pointer to a howto. Thanks. Posted by mikshaw on May 17 2006,20:40
From Suse, as root....1) Mount the ISO
2) Copy the contents of the mountpoint to your new ext2 or ext3 partition
3) Add entry to Suse's /boot/grub/menu.lst (this example assumes DSL is on hdb1)
Posted by yeti on May 17 2006,22:55
mikshawI know this is not a DSL question, but I'd like to use this same idea to frugal install KNOPPIX4 or 5 the same way (but on otherwise Fedora). I think I'd be stopped in finding a suitable initrd. Any thoughts? Thanks, yeti Posted by mikshaw on May 18 2006,02:20
I've never used or even seen Knoppix, so i couldn't tell you. When you say "I think I'd be stopped in finding a suitable initrd" are you just speculating that the initrd wouldn't work, or is this an experience you had? Grub's initrd line allows you to specify the file precisely. If for some reason Knoppix doesn't have an initrd, you can probably leave out that line and it should still boot. I've never gotten around to creating an initrd for my slackware, and it still works without trouble.
Posted by yeti on May 18 2006,16:50
mikshawThis is a non-problem. I just couldn't see the initrd using emelfm. Perfectly usable kernel and initrd in KNOPPIX 4.0.2. KNOPPIX frugal install works like DSL setup, except result runs in unionfs. Thanks, anyway. yeti Posted by jimihieu on May 20 2006,08:45
Hi mikshaw, i did like that you mention and i got the following error: The boot lines go a few lines as normal before the error occur: Uncompress linux.....Ok! Booting the kernel ..... audit ...initialization.... RAMDISK incomplete write (-28 !=32768) 4194304 Kernel panic: not syncing . No init found: Please put some init = option into the kernel. At first my grub was like this: root (hd0,0) kernel (hd0,0)/boot/isolinux/linux root =/dev/hda1 frugal When see the error i add in boot line: root (hd0,0) kernel (hd0,0)/boot/isolinux/linux root =/dev/hda1 init=/etc/init frugal Still dont works! give it 1 more try: root (hd0,0) kernel (hd0,0)/boot/isolinux/linux root =/dev/hda1 init=/sbin/init frugal still dont works! another try: root (hd0,0) kernel (hd0,0)/boot/isolinux/linux root =/dev/hda1 init=/sbin/init frugal initrd (hd0,0)/boot/isolinux/minirt.gz (N.B: please note that all the "linux" and "minitrt.gz" are correct name according to my files names and all file structures are the same) STILL DONT WORK! Please give me some hints on how to fix thanx Posted by dtf on May 20 2006,12:30
jimihieu -This is what I came up with after several attempts that seems to work. Of course much of this is my personal settings. title dsl-linux root (hd2,0) kernel /boot/isolinux/linux24 root=/dev/hdc1 vga=0x31a restore=hdc3 mydsl=hdc3 home=hdc3 opt=hdc3 alsa lpr frugal initrd /boot/isolinux/minirt24.gz I am not sure why you are using hd0,0. That is pointing to your master drive ide1 first partition. Is this where you loaded dsl? In my case I loaded dsl on hd3,0 (master drive on ide2) first partition. But mikshaw knows this better than I do so you might want to see what he has to say. Posted by mikshaw on May 20 2006,13:40
jimihieu: Look at your kernel line, specifically "root =/dev/hda1". There is a space after "root" which should not be there.
Posted by torp on May 23 2006,13:34
torp Posted by jimihieu on June 02 2006,04:22
hi guys thanx for the help! i fixed it by using this "5 fromhd=/dev/hda1 " but another problem is came up as below: VFS: Cannot open root device "<NULL>" or unknow-block (3,1) any idea this time please? |