On 30 May 2005 07:10:35 -0700, "Mikhail Zotov" <muxaul@lenta.ru> wrote:
>Niki Kovacs wrote:
>> Suggestion: when you have a couple minutes left, why not write a sort of
>> "kernel configuration for the desktop". Nothing very detailed, just a
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^--> I don't use GNU/Linux desktop.
>> memento of things to do and not do.

One of the joys of making friends with unix is the endless learning, me
no expert. Still learning. I put up examples in the hope they stretch
or add to the 'ideas factory', but there are myriad ways to run computing
environment.

I choose a hybrid, networked system, so yesterday I could pull lspci
examples from three boxen running slackware, another box is msft GUI
interface running the system. Why? X is too slow, desktop over X is
disaster for me, compared to msft on same hardware.

I used to run NEdit on icewm over vnc, slackware taught me vim is
syntax highlighting editor, so I no longer bother with lightweight
GUI, lots of PuTTY terminals instead. Shell scripting is fun.

I belong to the group that considers a GUI as simply a neat way to
have many CLI sessions running )
>
>Yes, and submit it to The Slack World as a `featured article'. :-)
>I guess it won't take less than a couple of hours though.

You'd have to find me in a particular mood to do that, communication
is _not_ my forte. Information theory: before one can communicate,
both parties must agree on a common dictionary.

The skill I lack is in being able to effectively describe _my_
dictionary, prior to presenting info. I wouldn't mind being part
of a deeper documentation project, but not intro level, I lack the
patience.

--Grant.