After a 4 hour headache trying to get Fedora 17 to work with my printer. I said, you know what let me turn to Slackware again and try it out. So I read up alienbobs wiki and quickly started the cups service and installed driver. ANd presto!

I swear to you it took me 10 mins to download the driver and setup my printer and worked flawlessly with the driver and 2 simple commands in term. Now thats what I call simplicity. Thanks Alien Bob... I am converting back...

I admit that I hate reading. I prefer to just do things. But you have to read to get the job done. I have really underestimated Slackware Power. Next step will get my other Acer running slack with Catalyst driver for 13.37... my last attempt where unsuccessful. I will try out some new techniques as was mentioned by 1 of the forum posts in here.

ASUS UL30A works flawlessly on Slack. Hardware has been my number 1 problem with Linux.

PS I am sorry to say that I pissed a lot of people off. But I just had a lot of questions that I needed answers too and was quite frustrated. I think I got those with all the flames aside. In the end I learned... especially with volkerdi post on why he did not add a dep. resolver.

boo hoo.

At my last job, I was entry level web hosting support (Level II), My "Boss" said "the only difference between Level II and Level III is that Level IIIs read man pages."

You are too much in a hurry.
I urge you to have a look here at my slack.notes file or browse around my site. I too hate reading so I usually (b)log my stuff into recipes that only a true nutcase such as myself could recognise.

At my current job, I just spent 88 hours banging on collectl. Now I ask myself, "Self, did I add any value to my skill-set?" Hell Yes! What took me 88 hours to setup/admin/config/moderate/script/...up to yesterday...
Tomorrow, I can do in less than 88 hours. Just kidding, more like 1. Data massaging is more.

I could have mentioned searching the CUPS version installed on Fedora 17 and doing a printer check here... might have saved you some hours?

Slow down.
Running to and fro is for youngsters.
Make a Plan/List.
Write it down. Keep a shorthand slack.notes file on a drive and document everything you do.
What if the Catalyst driver doesn't work well on your Acer?...

Take time to read.
I seem to have visual and acuity issues myself, where I used to be all spry and gung-ho. Now I have to read, and read and read just to retain something. So I cheat. I make lots of .notes files and I turn stuff into recipes.
What I read is just as important as where I read it.

You are right on the edge of being a pretty decent admin I feel. Your inquiries into the "whys" and how comes" surrounding specific Linux Disros/DEs/OSs seem genuine, but you come off as impetuous.

Young Luke, Use the Force. You don't have to know the why, that comes later.

Peace.

1 members found this post helpful.

Yes my problem has pretty much been doing before learning how to do. Reason being that I hate studying with a passion.
Also The Division in Linux/Unix Os's bothers me a lot. Its no longer a flavor of icecream one is like a sandwich the other is like a banana (or hotdog for fedora lol).
The whole systemd and init scripts and shell scripting all bug me because I am unsure which one will be used "longterm". I would hate to invest my time trying to learn shell scripting if it has a short lifespan.
If there was just 1 system that everyone followed (for example Python Syntax) everything would be perfect. The root of the problem is Division... It makes life unnecessarily complicated. If all Linux Os's merged as 1 I would no longer jump from distro to distro like a cheap whore.
Slackware is a great system the way it is with its simplicity and minimalism. The problem is not really Slackware but rather that so many other distros make it hard for Slackware and its users.

PS I may have exaggerated on the hours... but it took me a long damn time.

You could see it as a 'challenge', why should it matter if your shell.fu is up to smack?
Pick a distro and fasten your seat belt. Sure slackware can seem a bit tedious at times, but didn't you quote it as "simplicity and minimalism"?

Shiite or get off the pot.

Who is everyone Kimosabe?

you think too much about stuff that won't affect you very long because you "jump from distro to distro like a cheap whore."

at the very least.

I, like a couple of others have sought to be a positive influence for your slackware experience.

This will be my last reply to you on any subject here until some I see some zen to your posts/replies.

Peace

i understand yea studying we go... i quit pot... maybe i should get back on it lol it calmed me down and kept me focused.

Shell scripts are used in much more than just init scripts, and they have been used in UNIX and other *nix systems for decades. The Bourne shell was introduced in 1977 and bash was released in 1989. All GNU/Linux distros, all of the *BSDs (including Mac OS X), and any UNIX-like or UNIX-derived system will contain a shell and allow you to select a different shell if you so desire (for example, FreeBSD uses tcsh -- a c shell -- but allows you to install and use bash or any other shell if you want). Even if shell scripts are removed from the init system, it is still a very useful (and mandatory, in my opinion) skill for system administration. Even if your scripting knowledge is limited to what is necessary to write compound commands rather than full-blown scripts, it is still better than not knowing it at all. If you ever have to ssh into a Linux PC and perform any real system administration then knowing bash, or any other shell (or even just a POSIX shell) would be beneficial. The benefit to learning bash in addition to something like python is that bash is a very simple language, and is very easy to learn and use. Python requires some real work to learn (like reading books/tutorials and practicing writing real scripts/programs, and can go as far as learning object oriented programming and C/C++ integration). Bash is pretty easy to pick up without that much effort and is useful in a pinch.

2 members found this post helpful.

Thank you, that is definitely great advice. If I understand basic bash that should be enough for simple scripts and for the more complex ones I will use python. The 3 langs I am most interested are the ones you mentioned C, Python and Bash its great that they are all related to each other and work together like a team. I am also interested in Lisp, but that I will deal with later if I ever get there.

Besides that they're all programming/scripting languages, there's really no relation between the 3. They all have quite different syntax, for a start.