Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!zephyr.ens.tek.com!wrgate!amadeus!brandonl From: brandonl@amadeus.WR.TEK.COM (Brandon G. Lovested) Newsgroups: comp.sys.amiga Subject: Re: Commodore and UNIX in AmigaWorld 68030 Summary: good points Keywords: UNIX CBM 68030 "gangly" Message-ID: <1033@wrgate.WR.TEK.COM> Date: 13 Dec 89 02:45:37 GMT References: <2318@jolnet.ORPK.IL.US> <38689@lanl.gov> <38703@lanl.gov> Sender: nobody@wrgate.WR.TEK.COM Lines: 62 In article <38703@lanl.gov>, tjf@lanl.gov (Tom J Farish) writes: > > The main problem those of use raised on VMS have with unix is the > lack of easily remembered commands, I think. A few examples: > > want to do a DIRectory? Use 'ls' of course! > Want to REName a file? Use 'mv' of course! > Very good points; I drev. (drev = agree, didn't you know that? ;-) ) If this really bugs you, and it does me, too, DO NOT APPROACH AN APOLLO WORKSTATION RUNNING _DOMAIN_. It is "Unix-like," but changes all those commands you had to memorize so that YOU can be Unix-like. > Want to mave files from one unix machine to another? Hmmm can't use > 'copy' or 'cp'....you have to use CFS or FILEM etc. > This depends on how the two Unix machines are connected (e.g.: LAN). > Want to SET some terminal bit or password or file attribute etc etc. > (USe 14 different unix commands, none of which are in the index of the > local UNIX maual) > Setting "terminal bit"s, as I understand you, is done within a device driver, in /dev, which accesses tables on info on "well known" terminal types. File attributes, such as write permissions, are changed easily with one command (chmod). Pass word change? => passwd The power in Unix is not in its operating system; that is heavily criticized. The power stems from the fact that Unix is an environment. It typically contains 250-500 little programs written as primitives, that when strung together, will create *very* powerful tools. Just read an introduction to a shell programming book. It can change your whole perspective. This flexibility can cause a little more work, if all you want to do is something *real* primitive, true. > I could go on, but I have to stude this %^&&^%$# unix manual to figure > out whether I should use : x or ctrl-d to get out of this ^&&*%$# > editor! > > Yours in flames, tjf Manual? You got a manual?! Lucky bum! AT&T manuals, as I have encountered them (pity me - I had to use a 3b2) *inhale with great force*, to put it politely. It would seem that in AT&T, like most big companies, the manual is written by people chosen for their total lack of involvement at any level with what the have too write about. This guarantees "freshness." - Just like those strips of paper over toilet seats, which is where most of those manuals should wind up. ================================================================================ | Brandon G. Lovested | "I will not be pushed, filed, stamped, | indexed, briefed, debriefed, or numbered! brandonl@amadeus.WR.TEK.COM | My life is my own." | ================================================================================