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.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Posted 07-10-2019 at 01:18 PM bythe dsc (linux-related notes)
Updated 07-10-2019 at 01:20 PM bythe dsc
At least that's what apparently happened to me.
On Unix' stack exchange I've found this handy way of recovering it, partly at least, if you happen to have another terminal open, from before the wipe-out:
Code:
history | cut -c 8- > histback_user1.txt
The person who gave this tip suggested doing it in "every terminal", but I believe it would just overwrite it completely for whatever number of times one did it, with the simple ">." In order...
I mostly use the scrollbar as "buttons," clicking below or above the handler, rather than grabbing the handler itself. So when I've scrolled down quite a bit, I'll often mistakenly click above the handler when I really wanted to scroll down. That's kind of possibly solved if those barely useful up and down buttons were large enough to be more useful than pressing page up, down, or arrow keys instead. So this usercss does that:
For reasons I don't fully comprehend, every now and then, one or more of these tools won't work, but hopefully at least one will. In order to preserve openbox' rc.xml key bindings, I came up with this script that "unifies" simple commands to lower or increase the volume:
For some reason, and I can't fathom what, Dolphin only saw the home's trash and two additional partitions, but missed another one. Even PCManFM-QT was able to see and use that trash partition, while files deleted there wouldn't show up on Dolphin/Konqueror (which wouldn't delete them when emptying), and files over there deleted from D/K would be dumbly moved to the home partition.
I'm sure that besides trying to create brand new Trash folders, I've even tried to copy (preserving...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
