OT: Running Linux with filePro

[Fairlight]

Simon--er, no...it was Jay Ashworth--said:
> 
> And, if you're a SuSE-head, as I have been since 8.3 or so:
> 
> 11.2 is your fence.

11.1 was my fence.  When they announced "officially supported" in-place
upgrades and they -broke- the system so badly that I had to revert VDIs
entirely and try again two more times, and then the OS was so #$@(ed up
that I'd have preferred a manual migration, that was it for me.

> 11.3 has caused me quite a bit of grief everywhere I've put it, largely
> because they shifted from KDE3 (which I could train Windows users on in
> about 15 minutes) to KDE4, which while it may be *working* is nearly 
> completely useless -- even to me, and I've been doing this since
> SCO Xenix 1.3.  On Tandy 6000s.  Would you like to see the memo?[1]

I used to avoid the big, monolithic WMs like Gnome and KDE.  I still avoid
KDE.  I take GNOME by default, mostly because I know a lot of the people
that designed it, especially in the early days.  The reality is that I
prefer a small, lightweight WM like AfterStep (preferably 1.3, since 1.4
introduced the GNU configuration scheme, which -sucks- in its
over-complexity).  But I use the GUI so little anymore that I just leave
GNOME in place.  The only time I use the GUI is for something like
Wireshark, which I now use over VNC instead of restarting the VM in headed
mode (I run it in headless mode normally).  On a -physical- server, from
remote, the GUI is something I've used about three times since 1998 through
a few days ago.  And that was, to my memory, always to set up printers on
RH systems with printtool, which was the easiest way to do it.  (This was
back around the 7.x series.)

GUI on a server is a bit like tits on a bull, with a few exceptions like
the Wireshark scenario.  And technically you can use tshark, it's just not
as easy to visualise what's going wrong with the colour coding and such.

mark->
-- 
Audio panton, cogito singularis.