> > Parden me for throwing my two cents worth in here, but, when I first
> > got LINUX I spent over 2 weeks trying to get it to set up. I had to go
> > out and find a person that knew how to do LINUX and paid him to set up
> > my X-windows. Through it all I never said, this is a crappy system and
> > I am going back to M$. I was one that wanted out of the Make Bill rich
> > camp and was not going to stop till I got a working system. I have
> > bought at least 5 disros of LINUX, RedHat5.2, 6.1, SuSE 6.1, Caldera 1.3
> > (two times) and Caldera 2.2 I also gave a donation to get a copy of
> > Debian 2.2 All three of the ones RedHat6.1, SuSE 6.1 and Caldera 2.3 had
> > Graphic setups in them. If the person is going to throw up his hands
> > and quit at the first little set back, he needs to stay with M$
> > Windows. I feel LINUX is for thoughs that are willing to accept the
> > challenge to use a great system that will require them to think about
> > what the computer is doing, not just set and be spoon feed. This is the
> > meat of computing, not the milk. It is for people ready to take control
> > of their computer, not have the computer, control them. That said,
I know MAC users that hop on Windows 95/98 machines and are confused and angry
because Microsoft decent to do XYZ different than how Apple decided to do it
the ZYX way. I once meet a command line Unix junkie and showed him an Apple
machine and his exact words where "Where the hell is the command line, this is
confusing as sh** with all these damed windows popping up in my face"
It just depends on how you look at it.
There is a great book, the best book I have ever read about Unix. It is called
"The Unix philosy" and it doesn't have any Unix commands what so ever in it.
It doesn't have any syntax and nothing really techinally. It talks about the
how and they why Unix does it the XYYZ way. It talks about why it works, and
how to make it work.
It is a small book, about 100 pages, and doesn't get into all this dam techo
babbling, cryptic obscure weird syntax-ed commands. After you read it, you
will know why all this commands are hard to pronounce, ever try and pronounce
`ls -al` without saying l-s-space-dash-a-l? : )
Sure Unix is rough around the edges, some edges are sharper than others and
some drawn massive amounts of blood and huge headaches. But there is a reason
for this, with all those rough edges you can take Unix and SHOVE, STUFF and KICK
it into any space and it will fix perfectly, like a glove. It is extremely
flexible.
It can be used for anything from an answer machine, to a users workstation, to a
high performance database, to a 1000 nod cluster that renders high quality
virtual effects for motion pictures, to a ISP's mail server. It can run on
anything from a 386 w/4Meg's and a floppy drive to some of the world fastest
mainframes.
It can go anywhere and do anything, and it extremely stable, and uptime that
could counted in years. For this I take my scarps and cuts, I take the
headaches and accept the many days and nights I am working off of 2 hours of
sleep or less : )
I still consider myself a newbie and allot of stuff I still don't understand,
but when I look at in the 'big picture' ; in my eyes, this is the best way.
Jack
Note to self: don't post to mail lists when your caffeine intake would be
considered board-lining on a lethal dosage : )
> >
> > Good night Hal, we give you control of the ship to sleep. *G*
