PuppyThis forum is for the discussion of Puppy Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am not technically "new to linux", but have been using Linspire and Freespire for a couple of years. I am now trying to install Puppy Linux on my #2 drive and have Freespire 2.0.3 and Freespire 1.0.13 on my #1 drive.
I am here because I was on a Puppy Linux site and that site seems to have gone down so I am grasping at straws to get information.
The problem I am having is that when Puppy installs it wants to take over my Grub Menu on drive #1 and garbage it up. Its done it once already and it took two days to recover from it. So I am real hesitant about trying again till I get more information on Puppy install.
Can't you tell puppy to put its boot-loader in its own root partition?
And then just manually add it to your existing grub menu
as chainloaded?
Cheers,
Tink
That would be great, but it doesn't seem to have that capability and after being burned for two days worth of work I am afraid to try again until someone gives me detailed info on how to do it.
Got it done. Used SuperGrub CD to reset everything then cut and pasted till it worked. I still dont know why the boot starts with the menu.lst in the 4th partition on hd0 instead of with an earlier partition, such as partition #3 which also has a menu.lst on it. But I dont carte now as long as its working. It just made it hard to find which copy of menu-normal.lst it was using because I was expecting it to be the first Linux partition which is #3, not #4 I kept modifying the wrong menu-normal,lst and jiffyboot kept undoing everything I was doing until I disabled it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.