-
Website
http://linuxologist.com/ -
Original page
http://linuxologist.com/linuxhowto/the-7-habits-of-highly-effective-linux-users/ -
Subscribe
All Comments -
Community
-
-
Top Commenters
-
Popular Threads
All Comments
Great list.
VOTED for you at:
http://www.newsdots.com/tutorials/the-7-habits-...
Great article. Dugg.
I have pclos .93 on one of my partitions.
It isn't upgraded for a year, and runs just fine.
Pongscript. if a new one comes out, do you really have to install it?
Who is standing behind you with a gun to your head ?
I never upgraded to XP, just because it was there. I still run win98 without any problems.
I found SuSE handled my webcam better than Ubuntu then I found Mandriva did better than SuSE. Don't be afraid to multi-boot and you can have the best available.
Now, I usually have a dual- or triple-boot system, and I have made a storage partition, which goes into /mnt/storage.
After that, I have a script with:
ln -s /mnt/storage/documents ~
ln -s /mnt/storage/library ~
- and a couple of more folders which get symlinked in the home folder.
But I cant get the skinny elephant work...all I did is press Alt+SysRq+i, there would be nothing happen but a normal screenshot dialogbox popping up. Don't know much about this:)
(but hey, good article)
Nice article..
should be
"Why did the guide ask you to do thi..."
http://www.fsckin.com/2007/10/02/amazing-anime-...
that is 9 years. Nothing happened. But everytime
I log in as a simple user, I get a fit.
As for crash recovery, read the kernel documentation
file SAK.txt by A. Morton and hurry up: assign the
SAK key to .
these are age old tricks
when Ctrl+Alt+Del doesn't seem to work (or even you are unable to go to Terminal1 with Ctrl+Alt+F1) you naturally think about "cold rebot". There is much more civil way: Punch Ctrl+Alt+SysRq+(S, U, B). The sequence is important: first one Synces disks, second Unmounts the drives and third reBoots the system. The outcome is that most probably no data will be lost. This option however could be disabled in older kernels. to check if it works, go to terminal 1 and punch Ctrl+Alt+SysRq+H - it will display all available options.
I got a wallet.
I see your point, that backslash key is hard to reach, and double-quoting filenames is such a drag.
Stay on topic please, Bish
Nice.
By the way, pidof will show you proccess id of an application.
[QUOTE]If that doesn’t work, you might want to restart your GUI using the CTRL-ALT-Backspace combo. Beware, that this will kill all your GUI apps currently running[/QUOTE]
This will happen unless you programmed gnome to save your session.
...zzzzzzzzCiao
Thanks to everybody who commented and liked the article.
Thanks to the ones who fixed my spelling and/or mistakes
And as for the detractors, all I say, getting 100% approval rate is unheard of. Luckily it's a minority, I am sure there are other stuff on this blog you would appreciate :)
http://librenix.com/?inode=3223
http://en.wikipedia.org/wiki/Bootable_business_...
It's a silly piece of advice, really, for two reasons:
- it promotes carelessness, because sudo is perceived as a safety net.
- people typically just give themselves access to *everything* via sudo.
Personally, I would recommend learning Linux on a machine that you can afford to screw up, and *really* learn how to use Linux (i.e., login as root, don't use sudo). When you're forced to think about every command you type, you'll eventually reach a point where you simply don't make mistakes (assuming you proofread all CLI input beforehand).
1:
Nobody needs permanent root access. At least, if you aren't constantly configuring your system. Which you shouldn't be, being a highly effective Linux user. It's all about self control. Being root should be a rare, impressive experience. Not something you don't care about any more. It's this carelessness which leads to mistakes.
3:
I created an extra partition, mounted in /Data/. There I put /home/ and /usr/local/, pointing symlinks to them from the original positions.
This is just because, over time, I had many self-compiled stuff in /usr/local/ (distros normally don't install something there), which I'd also like to keep on upgrades. Maybe I'll put this /Data/ partition on an NFS-server. I can only recommend such an extra partition!
5:
My first distro was SUSE - man, I'm glad I switched to Slackware! Yeah, I know what they say: No package management and such... (which isn't even true - there's just no automatic dependency checking). But everyone just try it, before mocking around!
It's so damn sexy. No stupid scripts sitting everywhere, no being forced to use graphical config tools. And, @pongscript: No automatic upgrades ;-)
Perfect for learning how Linux works.
For testing other distros, I use QEMU. I don't really like Vmware.
stow/xstow is an excellent tool to organize your /usr/local/. Absolutely transparent and easy to use.
But you need a point 8. Install only the software provided by your Linux distro. The Linux distro does all the system's integration for you, making sure every installed program works with every other installed program no matter what's installed. Violate this rule if you're an expert, but otherwise you'll eventually experience Microsoft-like version incompatibilities and breakages, especially at upgrade time.
One of LInux's best features is that it just keeps working, even as you continually stay up to date with the latest software. The distros work hard to make this happen, if you get in the way be careful not to get run over.
Personally, I think number 1 should be "Never login to a graphical environment as root." It is ok to login on the console as root, just not graphically. One reason you don't mention for not logging in to a graphical desktop as root is that every single application on your desktop is now capable of trashing your machine. For example, if you run firefox and some page uses an exploit to run code on your machine, you are giving them a free pass to run it as root.
Also, I take issue with number 5. It seems to me that distro hopping is huge among those new to linux. I've known people to keep trying different distros until all their hardware "just worked" after install. I always tell them they would have learned a lot more if they had taken some time to get their first distro working. Fact is, you learn a lot more when things are not working and you have to fix them. I say, pick a distro and learn everything you can about it before trying another one. Sometimes, the best distro to choose when you are beginning is the one used by your local linux expert friend. That way you can learn a lot and get help from your friend.
@Oshu It's nice to see you drop by again :) As for your first point, yes maybe I should add it in the title, but that can be understood from the context of the paragraph.
As for the second point I did not mean by anyway to keep on going until you find the "just work" system. If you notice I encouraged using virtualization, a separate partition, or a whole different machine, all under the assumption that there is a base system to work on.
"As for the second point I did not mean by anyway to keep on going until you find the “just work” system. "
Oh, I'm sure you didn't mean it that way, but I think a lot of new users might see it that way.
Here is another tip: Buy a lot of books. Every crafty linux system administrator I know has a shelf or two of linux and related books. Best place to start if you ask me is Classic Shell Scripting (which will teach one all about the power of the command line as well as shell scripting).
Who's got time for books? Every crafty *nix SysAdmin I know uses a combination of Google, online eBook subscriptions (e.g., O'Reilly Safari), man pages, and their own PDF/CHM collection of whitepapers/books/technical documentation..
@deep:
While the internet is one of the best resources for learning Linux, when you break networking and you don't have a spare machine, nothing will save you quite like a Linux guide for dummies type of book. Just my $0.02 (plus it helps with learning the CLI, since you CAN'T copy/paste from a book!)
@peej: Write yourself up a script (bash, tcl, perl, python, whatever you're comfy with) that, first, runs your favorite editor, then runs your choice of ftp tool to get that file uploaded. That's how we do it around here: connect the dots, by piping together small programs, each of which does one thing and does it well, to get the functionality you want.
sudo uninstall vista.....
lol
I used to use QEMU for my virtual OS'es, but have found VirtualBox instead (which is also free btw) and it's MUCH faster, has a nice (corporate-like) gui-setup to use etc.
-using PCLinuxOS and loving it!
"Move /home to it’s own partition" should be "Move /home to its own partition"
Rami, thx for your education there. For me there is one logical step missing in your list. When applying step 4, and subsequently 2&3, how does one return to the original GUI session?
/peter