I'm using a VAIO laptop with some Puppy Linux distros in the H/D ready to boot depending on my choice at the splash screen or, if no key is pressed within a short period of time, the default (first choice in list) will be booted up automatically. One of those choices is DSL (DamnSmallLinux). I've tried above a half-dozen different entries at the menu.lst file as suggested by others at some forums but it never worked for me. I would like to see some already tried entries that have, indeed, worked. Also, it would be helpful if the actual contents of the folder containing DSL files is shown as a list of files in there. My actual menu.lst entry for DSL is shown below:
While looking at this entry above I decided to change those parts that read "/boot/isolinux" to /dsl only. I'm following the same scheme I use for other OS that I'm actually able to boot from folders beside dsl. PS. This's the first time I'm posting here & have noticed something strange. When trying to insert text (various lines from the menu.lst files) using the tool for 'code' I was given a message to insert the text within a blue square but, even though the text was inserted, the format of the text was messed up. I finally did it by repeating the process for each line of text. Is this the correct behavior or there's another way? Thanks in advance for any info/help on the above issues! asked 16 Jul '13, 11:47 Benny |
The same thing happenned to me while trying to post previously (editing aspect of data), not a good thing for this site. See below for filesystem clarification (just adding missing data): sh-4.1# pwd I don't understand when you said above "try this" and there's a greyed text afterward (first entry of yours of the last 3 ones). I copied+pasted the menu.lst entries as you suggested, maked sure I took out that "/" after dsl. I now will to reboot & try it, posting afterward whatever happens... Edit: Before I rebooted I saw your last post/edit/comment & took remedy action at once; meaning that I inserted the "/" after the "=" sign at <knoppix_dir=dsl ...=""> entry. answered 03 Aug '13, 14:38 Benny |
In that case, I think the dsl paths in menu.lst should be modified to /mnt/home/dsl/ including the knoppix_dir= statement. Your / directory has an selinux kernel and initrd of it's own. It also has what appears to be a complete Linux filesystem. I've no idea what installation that would be from. answered 03 Aug '13, 15:04 purevw |
I'm suppossing you're referring in both instances to the kernel line (in relation to changing the paths to dsl), am I right? But, what about the initrd entry after the kernel one? I was about to reboot when I saw LE's thread has been updated so I haven't performed the experiment yet... I'll do it now. answered 03 Aug '13, 15:17 Benny |
Have you ever checked out pendrivelinux.com? They specialize in creating USB flash drives with multiple operating systems on them, much as you are doing with your hard drive. Having all those OSs on a single flash drive can be handy. Also, the way they set up everything may also help you with setting up the same thing on your hard drive. Might be worth a read. I had a setup like that. But on mine, I also installed DBAN, which is a system to find and destroy all partitions on a computer. I activated DBAN by mistake. In the one or two seconds it took me to stop it, the damage was done. I had two operating systems to re-install and 6 terabytes of data to restore from backups. DBAN is something that you need to consider seriously before you set it as a boot option. answered 03 Aug '13, 15:46 purevw |
I tried all the changes you first suggested & even re-introduced sda2 instead of hda2, but at the end all I got was "knoppix filesystem missing". I'm now going to try the "/mnt/home/dsl" thing & I'll post below what happens. answered 03 Aug '13, 15:53 Benny This one really didn't work. It spat at me the following: The only thing that I can think of is introducing the boot folder under dsl & putting everything in there. What do you thiink? I'm preparing to add that boot folder under dsl & to put in there some needed files. It will look like: sh-4.1# cd /mnt/home/dsl My RE-edited menu.lst file looks like: 7) Linux bootable partition config beginstitle Damn Small Linux 4.4 frugal in hda2 dir dslroot (hd0,1) rootnoverify (hd0,1)kernel /mnt/home/dsl/boot/linux24 root=/mnt/home/dsl knoppix_dir=/mnt /home/dsl/KNOPPIX knoppix_name=KNOPPIX kernel /dsl/linux24 root=/dev/sda2/ds knoppix_dir=/dsl/KNOPPIX knoppix_name=dsl/KNOPPIX/KNOPPIX frugal satainitrd /mnt/home/dsl/boot/minirt24.gz Linux bootable partition config endsHope the above enters the site's page unharmed due to editor complexities!
(03 Aug '13, 16:05)
Benny
|
This one really didn't work. It spat at me the following: The only thing that I can think of is introducing the boot folder under dsl & putting everything in there. What do you thiink? I'm preparing to add that boot folder under dsl & to put in there some needed files. It will look like: sh-4.1# cd /mnt/home/dsl My RE-edited menu.lst file looks like: # 7) Linux bootable partition config begins Hope the above enters the site's page unharmed due to site's editor complexities! Now to test it. answered 03 Aug '13, 16:55 Benny |
Grub was already reading the menu.lst file where it was. It will look for it at /boot/grub/ not at /mnt/dsl/boot/grub/ Grub is intact and working. Better to leave the files where they are. The # sign means "disregard this line" in most config files. I'm looking for a better answer. Grub error 15 simply means we got the path or disk entries wrong. answered 03 Aug '13, 17:59 purevw |
Sorry to say this but menu.lst file hasn't been moved anywhere. It has been siiting in the same spot all the time. What I cjanged was the location of the files under dsl folder, been careful not to touch the other folders there. See again my previous post in relation to the bold entries. The command you suggest me to run doesn't run like it's stated but without "sudo" it gave me:
This site's editor really messes my mind! It takes a lot of time to arrange things to appear as the original. The above really resembles well the output shell window after issuing that command. answered 03 Aug '13, 19:12 Benny |