rm wrote:

> False.  The command line is neither powerful nor efficient.

ROTFL !!!!!!!!

Sure, while I'm typing this:

#!/bin/bash
$user = whoami
./configure|make
su root %1
makeinstall
su $user

and saved this on file, I made an installer for Linux.
You're still loading the development environment in KDE.
Then, you have to look through the components and see if
there's anything you can use to do the work.

Now, the script might be incorrect in some places( I typed it at
hand while logged on with Windows ) but after a few man hits and it
will work on almost *ANY* Linux flavour of *any* kind installed, no
matter what hardware you're targetting at the very moment.

KDE-wise, you must AT LEAST recompile to make it work under
other hardware platforms.

> Especially efficient.  Go back to sleep.

Yes, it's efficient. Efficient doesn't mean pretty.
Efficient means that you can code it quickly and then
save and execute it. Then backup it.
You can backup an entire server configuration on an Intel
machine and then restore it to a Sun server.

That's *very* efficient and speedy.
Ok, you won't have the buttons <g> , but you'll be
able to start several background tasks and still do
your job at ease. You can also log in to more than one
terminal and have all of them working at the same time.
I use this when I'm looking up man pages.

You'll soon discover that a lot of graphical stuff
requires shell interation anyways( either by you or the
program ).

StartX itself, for example, is a script calling xdm or kdm or
whatever you use for the purpouse. Plus, the same scrpts sets the
SHELL environment up for graphics.

Think about it.

> cordially, as always,

Same here,

> rm

Andrew

[ Post a follow-up to this message ]