Jim Patterson wrote:
> William Park wrote:
>
>> I'm still using Slackware-9.1. I just found out Slackware-current is
>> using X.org, instead of XFree86-4.4.
>>
>> For those of running X.org, I would to hear your experience with it?
>
>
> If you upgrade, be sure to check the Changelog, or at least this one entry:
>
> x/x11*6.8.1-i486-1.tgz: Upgraded to X.Org's X11R6.8.1 release.
> Note that the name of the keyboard driver in the xorg.conf file has
> changed from "Keyboard" to "kbd". You'll need to make this change in
> order to start X.
>
> My system was knocked offline for several days until I uncovered this
> little upgrade note (the system would boot, but X wouldn't start so I
> was left without a browser; I never did spend any time learning Lynx).
> It seems to have been a common problem, and a good example (I think) of
> why Linux is still not user-friendly enough for your average computer
> illerate to use.
>

Well I simply made a link to XF86Config without any change and it worked
OK at first try.

What didn't work was xdm that wouldn't accept remote X connection until
I put the:

LISTEN 0.0.0.0

in the Xaccess file in addition to enabling hosts.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
Registered Linux user #337974 <http://counter.li.org/>

William Park wrote:
> I'm still using Slackware-9.1. I just found out Slackware-current is
> using X.org, instead of XFree86-4.4.
>
> For those of running X.org, I would to hear your experience with it?
>
> --
> William Park <opengeometry@yahoo.ca>
> Open Geometry Consulting, Toronto, Canada
> Linux solution for data processing.

freedesktop.org broke the i810_drv when going to xorg-6.8.1, and hasn't
worked up a patch yet. So, if you are using an i810, stay with
xfree86, or don't go above xorg-6.7 in slack 10. Personally, I've seen
no improvement from xorg, and kinda wish slack had gone with
xfree86-4.4, which has a super config script to write the xf86config
file.

my $0.02,

On Fri, 10 Dec 2004 14:02:16 +0000, +Alan Hicks+ wrote:
> In alt.os.linux.slackware, Mats Holmberg dared to utter,

>> I never ran into problems with "Keyboard". And I wrote it manually in
>> xorg.conf myself =). But thanks for the notice, I just changed it -
>> everything works as usual.
>
> The above mentioned problem is with newer versions of X.org's X server
> such as the one's shipped by Slackware in -current and both SlackSec and
> GUS-Br in others.

Just "sed"ing it to uncapitalize seems to have worked for me...

~$ grep -m4 keyboard /etc/X11/xorg.conf
# (mouse and keyboard) settings.
# change the keyboard or mouse settings (currently only xset).
# Core keyboard's InputDevice section
Driver "keyboard"
~$ X -version

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: Linux 2.4.26 i686 [ELF]
Current Operating System: Linux desktop 2.4.28 #1 Wed Nov 24 00:39:22 CET 2004 i686
Build Date: 23 November 2004

....

--
-Menno.

On Fri, 10 Dec 2004 10:52:49 -0800, antispam wrote:

>
> <snip> and kinda wish slack had gone with
> xfree86-4.4, which has a super config script to write the xf86config
> file.
>

AFAIK, it's still in there - it's just renamed to reflect the new name of
the server - xorgconfig, instead of xf86config or whatever it was called.

On Thu, 09 Dec 2004 23:53:59 +0000, William Park wrote:

> I'm still using Slackware-9.1. I just found out Slackware-current is
> using X.org, instead of XFree86-4.4.
>
> For those of running X.org, I would to hear your experience with it?

I haven't really noticed any difference with the 6.7 series, and other
than the extra eye-candy that 6.8 added (and marked as unstable due to
stability problems - and they are) 6.8 seems the same.