-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'll tell ya, as far as the CL is concerned, I used the DOS CL for a long
time (about seven years) as my primary computer access. And even then, I
didn't know all there was... example: pipes. In DOS, there was really
only one use for a pipe:
A>TYPE FILENAME.EXT | MORE <ENTER>
You couldn't even do something like this:
A>TYPE FILENAME.EXT | PRINT <ENTER>
Which is pretty bad, now, to me, because I do things like that all of the
time. Example:
$ cat /proc/cpuinfo | lpr ; cat /proc/modules | lpr <ENTER>
This puts not only pipes to use, but allows me to put more than one
command on the same line, and both calls to lpr at the same time...
utterly convienent when you're collecting system information.
BTW, for those new to Linux, /proc is the place on your system where
things such as your memory, module, pci, and cpu information is stored for
Linux's usage. Many of the files there show up as 0-length, with the
exception of kcore, which is actually a pointer to the contents of your
system's RAM.
By looking at various things in /proc, it is like running MSD on a DOS
computer, except that the information in /proc is accessable to any
program, and accessable to the user, too.
- Mike
=====================================================================
Michael B. Trausch [EMAIL PROTECTED]
V: (419) 838-8104 F: (815) 846-9374
"Curiosity is the very basis of education and if you tell me that
curiosity killed the cat, I say only the cat died nobly."
- Arnold Edinborough
If you do not have my public PGP key, you are encouraged to obtain it
from my website at http://www.wcnet.org/~mtrausch/mt_pgp_key.gz. You
need to have PGP 5.0i or newer to use the key.
=====================================================================
On Sat, 20 Feb 1999, Dave G wrote:
> Ahhh......... I'll never give up my mouse for desktop work, not until
> everyone in Linux gets together and decides "whats what". At the risk of
> starting a flame attack I'll say Macintosh, if nothing else, did and does,
> one thing right. They call it the "User Interface Guidline". CMD P is
> CMD P, everywhere....................
> On a Mac CMD S saves no matter what application you are in. Windows,
> buttons, dialogs, keybindings, are common, learn one piece of software and
> you can learn another in minutes. It is like this for the vast majority of
> Mac software.
>
> I wish Linux was the same. I'd learn another editor besides Jed, but I'd
> have a gazillion different keystrokes for each editor to try and memorize
> before I could become productive. I've been told I can change the Key
> mapping in Emacs and Jed but I've not found out how, yet.
>
> But since my Linux box is a server I have removed X, I haven't used it
> lately except for tar and zip, now I telnet in when needed. I think more
> newcomers to linux would be comfortable in the command line if they knew
> how to use it. There is a real loss of good CL information out there, I
> just found out about pipes, I still don't know what they are for, just that
> some things use them, and what about these?
>
> more
> cat
> >
> printenvr
> ls -l /foo/bar (thats a neat one I discovered by accident!)
> tail
> head
> just to name a few, I'm sure there are more.
>
> All these things are cool and useful, we new guys just don't know about
> them. A good current starter tutorial (seen the dates on some of the
> How-To's ?) would be a God send, almost as helpful as mail list's. ;^)
>
> I'm getting used to it, and the more comfortable I get the more I like the
> command line for admin work, straight and simple.
>
> DAve.
>
> "On the Plains of Hesitation bleach the bones of countless millions who, at
> the Dawn of Victory, sat down to wait, and waiting -- died"
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv
iQA/AwUBNs57iBLC9wZKsFmxEQLBfACg24oN4pldHHPty1YDSrn2mSZGVzwAnjHo
QVvjkNFIGlN5PoHiAlR335wP
=3o3c
-----END PGP SIGNATURE-----
