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.
Hi, I've been a long time puppy tinkerer, but I have a specific use that I need help with.
I have set up an old screenless laptop as a music player connected into my music system. I have done a full install to hard drive and set up xbindkeys to enable the media keys and am using vnc to control deadbeef player remotely.
The problem I'm having is that occasinally at boot up a drive check is performed which needs acknowledging before booting will continue. This stalls the system before the vnc server is started. My question is, is there a way to disable drive checking, I don't mind doing this manually occasionally but want to make things as easy to use as possible for my wife.
I assume the drive checking is done by /sbin/init after a hard poweroff leaving some kind of /fsckme.flg file on top of the disk (puppy 5 series or later) ?
This check would be a filesystem check aka e2fsck . AFAIK this file system check should be done without user intervention and after finishing this , puppy should reboot .
I cannot look into the newest racy sfs for now , because i am running a kernel atm that does not support xz compressed sfs files .
Thanks for the hint of where to look, just looked at /sbin/init, I think what I need to do is force an auto reboot straight after the file system check instead of waiting 4 minutes till rebooting
Also think I'm confusing myself. I'm sure I have seen a request for filesystem check after a certain number of restarts, but that could have been from Linux Mint Debian which is now may main distro on 2 other pc's.
Thanks for the help, thats probably all I need to do for now, but I'll probably have a play with MPD next if I can find a version for download while the forum is still down. I'll post another thread for that though