From: Ed L Cashin <ecashin@terry.uga.edu>
Cc: ntg-context@ntg.nl
Subject: Re: linux question
Date: 18 Jul 2001 11:36:18 -0400 [thread overview]
Message-ID: <m33d7uw8p9.fsf@terry.uga.edu> (raw)
In-Reply-To: <5.1.0.14.1.20010717104534.02096e08@server-1>
I'm a bit late, but I feel sympathetic to your desire to move away
from GUI-bloat! ;)
Hans Hagen <pragma@wxs.nl> writes:
...
> [I use suse7.1 but am slowly getting sick of the enourmous bunch of
> window stuff installed/loaded and getting rid of it seems
> impossible, so i wonder if i should continue with suse anyway. Are
> the otherw linux's leaner?]
I'm also a user who prefers lean, responsive software. A lot of linux
distributions come with KDE or GNOME configured to run, but you don't
have to use them.
Siep mentioned icewm. That's the window manager I use, because it's
light and has excellent keyboard support (you don't have to reach for
the mouse all the time). The default keyboard commands are
reminiscent of Windows keyboard shortcuts.
After a fresh install I configure the system *not* to boot into X, and
then I create a ".xinitrc" file in my home directory, along with a
".xsession" file in case I ever do start using xdm or some other
X-Windows-based login utility.
In the .xinitrc file, I have these lines:
xset s off
exec ssh-agent icewm
The first line turns off the default X screen saver and the second
tells the "ssh-agent" tool to invoke the icewm window manager. I use
the ssh-agent to handle ssh keys -- it's a convenient way to have to
type my password only once and still access many machines in a secure
way.
"exec" means that if someone kills X, they won't get my shell prompt.
If you're not interested in ssh-agent, this will work:
exec ssh-agent icewm
--
--Ed Cashin PGP public key:
ecashin@terry.uga.edu http://www.terry.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2001-07-18 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 8:55 Hans Hagen
2001-07-17 11:27 ` Giuseppe Bilotta
2001-07-17 18:54 ` Hans Hagen
2001-07-17 20:58 ` pdf not read by acrobat ?!?!? A. Villaveces
2001-07-18 10:06 ` Hans Hagen
2001-07-27 4:26 ` A. Villaveces
2001-07-27 7:16 ` Hans Hagen
2001-07-18 11:28 ` Henning Hraban Ramm
2001-07-18 13:32 ` Hans Hagen
2001-07-27 4:33 ` wrong listoffigures name in spanish!!! A. Villaveces
2001-07-27 7:32 ` Hans Hagen
2001-07-27 4:38 ` a problem with left margin or edge A. Villaveces
2001-07-27 7:18 ` Hans Hagen
2001-07-27 4:44 ` nice left lines? A. Villaveces
[not found] ` <5.1.0.14.1.200107 =?ISO-8859-1?Q?17104534.02096e0?=8@server-1>
[not found] ` <2042 53540.2001 =?ISO-8859-1?Q?0717132727@bigfo?=ot.com>
2001-07-27 7:29 ` Hans Hagen
2001-07-27 16:59 ` doc shell (was: nice left lines?) Henning Hraban Ramm
2001-07-17 11:28 ` linux question Mohit Agarwal
2001-07-17 11:46 ` Taco Hoekwater
2001-07-17 18:51 ` Hans Hagen
2001-07-18 6:36 ` siep
2001-07-27 20:15 ` Berend de Boer
2001-07-27 22:22 ` Re[2]: " Giuseppe Bilotta
2001-07-17 14:07 ` Tobias Burnus
2001-07-18 10:33 ` linux question / lucida fonts Hans Hagen
2001-07-17 20:52 ` linux question A. Villaveces
2001-07-18 9:58 ` Hans Hagen
[not found] ` <Pine.LNX.4.33.0107171629530.24353-100000@fourier.aero.iisc .ernet.in>
2001-07-18 9:56 ` Hans Hagen
2001-07-18 11:33 ` siep
2001-07-18 15:36 ` Ed L Cashin [this message]
2001-07-27 20:13 ` Berend de Boer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33d7uw8p9.fsf@terry.uga.edu \
--to=ecashin@terry.uga.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).