Help -warning message on lucid 5.2.8. -no bootup!!!
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.
Distribution: Started out w/Redhat 6.0,7.3,then Suse 8.2 , 9.2 ,10.open suse , KNOPPIX 2.73 &5.1 & Puppy
Posts: 164
Original Poster
Rep:
Log fi:les ???
Quote:
Originally Posted by unSpawn
Boot a Live CD then check your system and update log files for clues?
HMMMMM ,what exactly are log files & what directory/ branch would they be located under . Plus what can one do with them??
The only bad thing i could have done on this BOX is Unzip/open some TAR or TarGZ files (using the ZIP ICON , and NOT putting them in a definite folder/directory , Also maybe try ing out some RPM,S that broke. This is ALL from USB drive loaded stuff.
what exactly are log files & what directory/ branch would they be located under . Plus what can one do with them??
Log files are file where text gets logged about what the system does or can't do. You'll find the files in /var/log/. You can read them in your favorite editor or from the command line with for example 'less /var/log/messages'. I forgot though that since often Puppy runs from RAM it may destroy log files on shutdown.
Quote:
Originally Posted by chilibowl
The only bad thing i could have done on this BOX is Unzip/open some TAR or TarGZ files (using the ZIP ICON , and NOT putting them in a definite folder/directory , Also maybe try ing out some RPM,S that broke.
Right now you're missing a core library and your kernel won't boot Puppy. That doesn't happen all on its own. So saying "some TAR or TarGZ files" doesn't really give a clue as to what you have done. If these archives contained updates, libraries or applications it would have been better to mention them by name. If protracted diagnostics are not your thing I'd get your private files off off the stick and reload Puppy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.