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.
Distribution: multi booting whatever I feel like. Grub rocks!
is puppy messing with my boot settings?
I have been having some very strange problems. I have been using windows and various versions of puppy. I frequently shutdown and boot up from cd or usb, to check out something in a particular puppy version, and then back into windows, and back again. The very strange thing is that sometimes I find that my pc will not boot from the device I want it to. I press F2 during startup, and wow. Things are not the way I left them. Funny thing is it seems to be random. Sometimes it is the boot ORDER, like the hard drive is set to boot before the cd. Last two times it was because the hard drive was DISABLED. Is there any way that puppy is doing this? Is there any way someone is doing this to me remotely? Because it CANNOT be anyone in my home. It has happened with me sitting right here. If this were a battery problem, wouldn't I be seeing boot failures, instead of altered settings?
The reason I post it here is because this has not happened before, with any other distros. I am not saying that puppy is responsible, just that it started happening around the time I started messing with puppy.
Last edited by darinbolson; 09-20-2006 at 09:11 PM.
Linux does read the time from the hardware clock when it boots, and it might save the system time to the hardware clock when it shuts down, so this could theoretically disrupt your bios settings, especially on older machines with atypical hardware, but it's not really likely
other than setting the clock, Linux really should not be touching your bios settings at all
anyway, i don't think Puppy sets the hardware clock from the system time at shutdown
(the bios setting are stored in the clock chips memory)