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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
label legacyOS2 (puppylinux+,old pc)
menu label legacy os2 = puppylinux+, old pc
append pmedia=ideflash root=boot/legacyos2 lang=en pkeys=de
original from iso cd was root=/dev/ram0 loglevel=3 PMEDIA=idecd
Which boot code should I use?
It say "cannot find Puppy files" before it abort (kernel loads and initrd starts)
(I can boot Puppy, Slitaz.. on this USB with syslinux)
This 'root=' tells the kernel which partition to mount after finally booting to look for /sbin/init which would run /etc/rc.d/rc.sysinit , which would do all the stuff to mount /proc and /sys and load the drivers - in Puppy .
The script in the initrd.gz gets changed quite often , and may or may not work with that "root=boot/legacyos2" parameter ; also the kernel .
In puppy the "root=" parameter is used mostly for full installations nowerdays , the root=/dev/ram0 is a very old parameter , which i dont know much about , except that it exists .
It is possible to gunzip the initrd.gz and "mkdir initrd.d && cd ./initrd.d && cat ../initrd | cpio -i -d > ./initrd.d" to read the main file "init" inside there .
The puppymain-forum@murga-linux has examples in the "Howto Section" , and there is a pet called "editinit" out there .
If you put the puppy initrd.gz inside the /legacy_os folder and not the initrd.gz of the legacy_os , the puppy-initrd.gz looks for puppy-dotSFS and puppy-dot2fs|dot3fs|4fs files on the disk|usb . It would not look for legacy_os files .
You could create your own init and initrd file to look for legacy_os files , or just leave the initrd line out , because i think you installed full and legacy_os might not use an init-ial-r-am-d-isk at all to support the boot process with additional modules.
Further I have to say that i don't know anything about legacy_os at all , just had read a few about OS/2 .
I have never had much luck putting the Puppy file in a subdirectory.
You could move them to the root of the USB flash drive and trying the default syslinux.cfg.
Mine that worked with all the Puppy files in the / directory is
default vmlinuz root=/dev/ram0 initrd=initrd.gz PMEDIA=usbflash
I am unsure if you can use the append option to add parameters or not.
You would have to read up on the bootloader to see.
Is your bootloader ldinlinux?
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate of http://www.linuxquestions.org/questi...0/#post4504739.