PuppyThis forum is for the discussion of Puppy Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Your grub.cfg looks like a kind of source-code that hasn`t been compiled yet.
grub.cfg isn`t the same as menu.lst !
I havn`t seen `loop` at one menu.lst until now.
menu.lst entries normaly look like:
Puppy 4.3.1 doesn`t uses initrd as second line. It boots up just loading kernel.
and .iso is to be extracted there. As I can remember a post at Lq there was a solution by putting the only one bootable flag to the desired partition by gparted.
I tried this too with one MacPup 4.2.1 from a magazine DVD to stick but somehow it did not work there and it seems there are some corrupted .iso on some linux-magazine-dvd. No .iso download I had until now was corrupted and I downloaded 15 to 20 .iso the last two weeks. Puppy 4.3.1 works fine, also MacPup 4.3.1 . So this time you shouldn`t fear leaving 4.2.1 . And to install something on stick and run a whole mainboard+screen with it is not advisable for me because the fittings are not so tight and there is the possibility of very short power disconnection between board and stick and it should be simple for rescue but I think if the OS doesn`t work just install new Linux. If the usb-fittings would be like the vga- or ttyS-fittings it would be safer.
is a first extracted .iso that has to be extracted a second time at first boot but how this would work I do not know. .sqashfs is also a common "ready-to-be-extracted"
Grub2's looback device option makes a ram drive and copies the kernel and initrd into that ramdisk. However, as soon as the kernel takes control, the ramdisk disappears. That's fine, because the kernel has already loaded its own ramdisk and uncompressed the initrd image to use as a temporary root.
To get Ubuntu to work with grub2's loopback device option, you have to pass the parameter "iso-scan/filename=/PATH/TO/ISO/FROM/GRUBS/PERSPECTIVE.iso"
Ubuntu's initrd scripts (casper) then mounts the pendrive device as /iso-device. Afterwards it mounts the iso from /iso-device/PATH/TO/ISO/FROM/GRUBS/PERSPECTIVE.iso to /cdrom. Since /cdrom is where it normally expects to see the CD-Rom device, the scripts can continue as normal from this point on.
In order to make Puppy work with Grub2, you'll need to modify the initrd.gz file in a manner similar to Ubuntu's Casper. Since this is something I'm interested in, I'd be happy to post any modifications I get working. However, don't expect me to get around to it in the next 2 weeks and I might not get it working. I have some experience modifying casper, but I haven't looked at Lucid Puppy's initrd yet.
Distribution: Linux Mint, Ubuntu Netbook Edition, et al
This is very interesting. I was hoping to essential make a setup where I could just make a "drop in" replacement with an ISO for these (like I'll be able to do with Ubuntu and other casper-like distros). That said, I would love to learn what you find out as I'm always up for learning these type of things.
Puppy is a nice-enough distro that I would make these mods in order to get it working with my grub2 usb.
You would also be making a significant contribution, because a quick Google search of this issue gives a nice amount of hits with people trying to make our our nice little doggie distro work in this fashion.
I appreciate your breaking down how the loopback works with casper. I figured it was something like this, but it was just guessing. Your explo gave it much more clarity.