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.
I'm planning to get a cheap laptop to supplement my desktop, and I've been looking at suitable distros. Puppy (4.3) was the best of those I tried, so to familiarise myself with it I decided to create a new partition and install it. The installation seemed to go well, so I went back to Fedora and altered grub.conf.
When I re-booted and selected Puppy from the grub menu, I was given a screen (why?) which offered
Linux on sda1
Linux on sda4
The second should have been Puppy, but it didn't work. When I examined /boot on the Puppy partition, I found there was no initrd or config, and /boot/grub had no grub.conf.
I went back to the live cd and re-installed. This time, instead of the option of installing grub on sda4, I chose MBR. I don't know what I was thinking about, because that trashed the Fedora grub! And I still couldn't boot Puppy — or Fedora either, now. Luckily I had my Fedora disk and was able to re-install grub from there.
So what did I do wrong? How do I install Puppy alongside Fedora?
Distribution: Mepis and Fedora, also Mandrake and SuSE PC-BSD Mint Solaris 11 express
That's a tough one. There is a file called menu.lst (or something similar) in the /boot directory which has all the information needed to boot a kernel of linux. If you are using GRUB for more then one Linux, you need both menu.lst files and you need to do some cutting and pasting so that all the information is there. The location is /boot/grub/menu.lst A text editor should open it. Be sure to edit the text file, not the binary just like it.
This reply tells me nothing; my post indicated that I know what ought to be in /boot (grub.conf is just Fedora-speak for menu.lst), and that Puppy was not producing a viable /boot. I would be surprised if it could start without an initrd file.
Make a directory on the partition you want to install Puppy to.
I called mine pup431.
copy vmlinuz, pup-431.sfs, and initrd.gz to it.
Then add this to your version of menu.lst.
# Linux bootable partition config begins
title Puppy Linux 431 frugal
kernel /pup431/vmlinuz pmedia=atahd psubdir=pup431 nosmp
# Linux bootable partition config ends
My installation was on the second hard drive on the third partition.
So adjust according to the drive and partition you put it on.
For example, if it is installed to the first partition of the first hard drive the root line would be root (hd0,0).