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.

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?
>

No problem
--
Robert - slackware

On 2004-12-10, Robert <redneck@lowtech.net> wrote:

>> For those of running X.org, I would to hear your experience with it?

No probs, so far. In fact, I simply substituted my old 9.1 config file into
10 and it ran without a hitch. To config from scratch, run
/usr/X11R6/bin/xorgconfig, which is like the old xf86config.

nb

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?
>

It's awesome... so far, at least. The whole XF84Config and XF84Config-4
names were bugging me anyways.

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.

--
Jim Patterson
Ottawa, Ont
CANADA

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.
>

Interesting. I have not encountered this one. I simply copied my (9.1)
XF86Config file to xorg.conf; and it works fine (using "Keyboard" and not
"kbd").

--

Greg Heilers
Registered Linux user #328317 - SlackWare 10.0

The box said:
"Requires Windows 98/2000/XP/NT, or better."
So, I installed LINUX!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?
>
Never had a problem getting xorg to work unlike xfree
MikeinAK
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBuVvWcap0jM1dpQcRAkFxAKCsbAiZ3XwuuCML3on8Wu n5tJG35gCgjJTf
wOEr7lG6hqnfvP+FczHK+tY=
=MRfk
-----END PGP SIGNATURE-----

Greg Heilers wrote:
> 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.
>>
>
>
> Interesting. I have not encountered this one. I simply copied my (9.1)
> XF86Config file to xorg.conf; and it works fine (using "Keyboard" and not
> "kbd").
>

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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBuaxylKR45I6cfKARArdvAKCIZN/p1StriHQHj3hLK9LSJbBROACfQUOW
cVvL9GdA7y5bSeM82D8MGGU=
=7J0g
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+Alan Hicks+ <alan@lizella.network> trolled:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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.

The X on SlackSec is _not_ official. The GUS version _is_ official.

cordially, as always,

rm

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQbmu0+EckfDWS6x8EQK4hQCfX6dTZ7gAvfRYENETkpPnlJ DeW1wAnR5Z
tjzosYXKGLggSJNIPqvWjINJ
=TRb4
-----END PGP SIGNATURE-----