From: "Erik Troan" <[EMAIL PROTECTED]>
> > I did. The documentation was incomplete. Hence the rather impressive
> > demonstration of invective that followed as I battered the system into
> > appropriate submission. (I am too stupid to give up.)
>
> Did you file a bug? The docs that are there showed the right intention; they
> probably just got out of date as things have changed.
>
> Erik
Nope, this well predated my awareness of bugzilla, a good idea flawed by
a web interface. Once I got it working (back in xntp days) I just sort of
"left it." Pretty soon "ntp" replaced "xntp" and had a complete init file
in init.d. This was back when I was "relatively" new to playing around with
Linux at those levels.
BTW - the "hanging bugreport" I have is more or less obsolete at this
point. But I did note long ago that whatever the merits of KDE were (I
personally cannot stand the beast) the "kdm" tool is very nice. It feeds
through your GUI selection to the X scripts that run up your desired window
manager. (I posted some scripts from "those days" on my web site. I had
doctored the usual startup scripts that ran from an xdm startup so that]
they paid attention to the parameter that kdm passed. This worked remarkably
well when I was playing around with running about 10 different window
managers trying to find one that didn't bother me for one or another minor
deficiency. (And no, I am still not happy with GNOME either. {^_-}) Heck,
one version of that script set actually ran the "AmiWin" window manager
that mimiced the Amiga "Workbench." Alas, it didn't do a useable job because
the basic X metaphores are sorta backwards from what I prefer, which is
partially a lack in the commandline behavior of bash and of programs run
from bash. Anyway, I feel I should be able to select the window manager I
want from wahtever foo-dm that I run from a list of those the machine has
loaded and supports. And as noted "kdm" did a marvelous job of it and the
script modifications were minor.
(Oh, one other bug report is more or less out of your hands. Alan MAY have
finally nailed down what needs to be done to generate kernels that will
run on Wednesday. (I have too much "salvage" to do to grab off important
data from Morticia, the one that would probably spend more time in Linux
than Wednesday. At $50/hour for doing DirectX-MFC work telecommuting from
my home working my own hours I tend to bahave in typical mercenary fashion.
Wednesday is "polluted" by W2K most of the time.
(Another big bug report is my perennial lament that Linux lacks decent
"almost real time" performance, that is to say very low latency task swaps
with 1ms quanta. For these tasks W2K and NT4 behave remarkably nicely,
better than the '9x chain of trash even. Now THIS one I do not expect to
change very soon. But it would be fun to have a Linux that could receive
MIDI keyboard input and render it fast enough to please a keyboardist.)
These days configuring my gateway machine is mostly a "do it in my sleep"
operation on a rather old version of Red Hat by today's standards. From
the looks of things I *may* go through the trouble of upgrading it to the
next version to come out. I've been REAL conservative with it once I got
its 6.2 install actually working. It took a few revs to get the CDROM and
everything else on that antique machine working. 6.2 proved that even the
best sorta slip up from time to time.
{^_-}
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
