Linux\Slackware Suggested Reading?
I tried Slackware awhile ago, and I really liked it a lot, even though I wasn't very good with it. Software was pretty much installed on a case by case basis. I eventually slipped back into using Linux Mint, because I am a very weak person. After going through dependency hell, I find myself back at Slackware. Other Linux distributions don't force you to have an understanding of Linux like Slackware, which should be good for me in the long run... Right?
I want to get off on the right start this time. I definitely need to learn how to use the terminal better, but I'd also like to have a better understanding of Linux in general (with an emphasis where it will help me have a better experience with Slackware). I've already added the Slackbook to this list. I'm considering putting Linux From Scratch on there, too, but it may be a bit too comprehensive. Definitely keeping the thread So You Want to be a Slacker in mind as I go, too. What has helped you guys out? The book doesn't have to be free, but that's always a plus =) In a previous post some time ago I had about wireless problems (which did get fixed, I pretty much overcomplicated it), onebuck suggested the following to me... SlackwareŽ Essentials SlackwareŽ Basics Linux Documentation Project Rute Tutorial & Exposition Linux Command Guide Bash Reference Manual Advanced Bash-Scripting Guide Linux Newbie Admin Guide LinuxSelfHelp Getting Started with Linux Anything else I need? ^I'm hoping not to do that much reading, but I suppose certain aspects can be learned as I go-- I just want to make sure that I start out right this time. |
The best way, in my opinion, is not to be weak and slip back into other brainless linux distributions. These distributions try to hide things from you in a failed attempt to make it easier. Your best bet is to install slackware and read the directions on how to install it. Invest the time early on, it will pay off in the end. The instructions are available on slackware.com and perhaps at slackbook.org. Don't look for short cuts and distro specific applications to run your linux. When you come to a problem, read first and learn first. Look to do as much possible from the command prompt because these basic tools don't change very often and can be applied to many problems and issues.
Once you take a few extra minutes to read and learn, slackware will be 100 times easier then any of the other distributions. Those suggested reading materials are pretty good but start with installing/using slackware first. It will lead you to those other documents. Google can be your best friend and also this website -- it's a great place to ask questions and get them answered. |
Hi,
I'd suggest to read the manpages. Slackware comes with all programs vanilla which means that everything works exactly like it is described in the manpages. Markus |
A little about understanding the filesystem, a little old but still.....
http://tldp.org/LDP/Linux-Filesystem...-Hierarchy.pdf Like smooth103 said, Slackware was pretty full on when i first started as well. You need to take time to learn it, just get it online and research. When i first switched, i dropped Slackware because of the whole package-management thing. I distro-hopped for a while and finally landed back at Slackware. In which i've never left. Remember, that the time you spend learning Slackware will pay off for other distributions, as you'll most likely find them a breeze to work with. (expect the /etc/rc.d /etc/init.d :P ) still gets me ! lol. And if all else fails, Linux Questions to the rescue! I wish you all the best... Good Luck and welcome back to the real Linux --- Slackware. |
One of the best investments you can make -- after you've devoured the list that Onebuck gave you and gotten familiar with how things work -- is to take the time to dig into regular expressions.
Huh? As time goes on, you'll find that the Click 'n' Drool School will get boring, applications will start to feel limited, you'll want to do something or other and you'll want to be able to do more. Linux, the operating system itself is Linux all the rest are the utilities, will, once you've got things configured, become invisible; you start it up, it sits there mumbling to itself, and you don't need to tinker with it. So, then what do you do? Well, say a little light bulb pops on over your head and you think to yourself, "Wow! How can I make that happen?" And that's where all the utilities begin to look interesting. Virtually all the tools and utilities sitting there are for you to use to accomplish something quickly and easily. And all of them started out life as part of Unix, developed by a bunch of Really Smart Folks at AT&T Bell Laboratories. They built the tools to make what they were doing (essentially reinventing computer programming) easier. Ain't no easy, but there's a whole lot of easier. The Unix utilities got migrated to Linux as look-work-alike utilities developed by the Free Software Foundation (that's GNU) and contributors all over the world that saw a Good Thing and help migrate that to free and open source. Linux itself, the kernel, was developed by Linus Torvalds because he liked Unix but couldn't afford to buy a license for it so he developed a look-work-alike that we now have in hand. One of those Really Smart Folks is M. Douglas McIlory, a Bell Labs scientist (the guy that invented the Unix pipe, no small contribution) who postulated what has become known as the Unix Philosophy http://en.wikipedia.org/wiki/Unix_philosophy: Quote:
The question, then, is "OK, how?" Always keep in mind that everything hangs together -- the utilities, the tools, do work together. The output of one can be the input to another which, in turn, can output into the input of yet another and so on. That's the beauty of the pipe. The editors, ed, ex, sed and others are useful as text filters. So too are tools such as awk, grep, sort, uniq among a plethora of useful tools. The common denominator of all of these are regular expressions http://en.wikipedia.org/wiki/Regular_expression: Quote:
Consider a data file of thousands of lines containing hundreds of fields from which you only need the third, tenth and twenty-fifth fields to accomplish some task -- how would you do that? How would you remove all instances of multiple blanks; how would you remove trailing blanks; if you had all upper case text, how would you convert that to lower case but retain the first character of a sentence as upper case; if people's names were all upper case, how would you convert those to lower case but keep the first character as upper case and, oh, by the way, properly deal with Mc, Mac and other mixed case surnames? All of that, and much, much more, is easily dealt with if you have a good grasp of pipes and filters and, of course, regular expressions. Well worth your time investment, those. To solve problems with a computer (or, what the heck, pretty much anything else) requires that you have a clear understanding of three things: what have you got; what do you want; what do you have to do to get there. Learning about the tools and what you can do with them is a good use of your time. Hope this helps some. |
This list is a bit old, but there is a lot of good information: http://www.linuxfromscratch.org/hint...prereading.txt
|
Hello,
Quote:
Quote:
Markus |
See my bookshelf below - they are books on Linux
The titles of the first 2 books may sound intimidating but they are written for people like me - real newbies. DistroWatch (http://distrowatch.com/dwres.php?resource=major) says: Quote:
Code:
... but if you learn Linux, you'll know Slackware. |
This is fairly obvious, although I know at least one instance where it wasn't :); while you're clawing your way, tooth and nail, up the learning curve, it helps to have a separate computer connected to the internet. Personal experience.
Best wishes! Ferrel It's the ant, not the antennae. |
I read this every now and again:
http://www.ibm.com/developerworks/li...map/index.html |
This link is one of the best for getting your feet wet with the shell (command line). It starts off very basic and walks you though some fairly high level stuff by the end. I can't recommend it enough:
You can download the entire book here: http://linuxcommand.org/tlcl.php |
Hi,
Quote:
Keep Slackware specific sections in mind; Quote:
Plus do not forget one of the best on the Slackware team: Alien_Bob has provided the means to go multilib then look at Multilib Slackware for x86_64. Few more Alien_Bob's links that you will find VERY useful; Quote:
Happy Slacking! |
All times are GMT -5. The time now is 03:48 AM. |