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.
However arguable, some people want to trash by moving into another partition's trash folders. The linux/unix/whatever trash specifications theoretically prohibit that, but KDE's implementation doesn't. So a linked or bind-mounted trash into a different partition will behave normally, except it will move the file across, obviously.
If you also use trash-cli, which won't work with such hacks, it can be replaced with the kioclient command, that in turn can be scripted or perhaps even...
At least in Ubuntu wily, it doesn't seem to allow you to chose the default application to open a file type. You try to do it, but it "magically" restores the previous default association before your eyes. Even if you chanced the config file, somehow. (I'm assuming it's mimeapps.lst, but I'm not sure. It seems that it's cool nowadays to have cryptic, hidden config files, avoiding to mention them unless strictly necessary, pretending it's all magic and config files don't exist)
# volume changer+notifier, using notify-send, and tested only with xfce4-notifyd
# the syntax is the same of the "end" of what you'd use in plain amixer, see "$1"
# Ex.: 5%-, 5%+, 30, 60%
com=(`amixer set "Master" $1`)
# and here's why it won't work for everybody. The output of amixer includes
# things like soundcard features, which are array elements I'm just
Posted 03-15-2016 at 01:43 PM bythe dsc (linux-related notes)
Updated 03-16-2016 at 07:23 AM bythe dsc
First of all, you may be used to sometimes pasting stuff with shift+control+V instead of just control+V. Perhaps that's the way it's done in nano and/or some terminal emulators. The problem is that it's now also the default shortcut to enable "vi edit mode" in kwrite.
For people who like myself, don't really get "vi", using nano or something like that when forced to use cli editors, if you're in kwrite (perhaps also kate) and all of a sudden it seems to behave...