Prev: kernel upgrade - touchpad unexpected behaviour
Next: PHP with unixODBC support
From: Mike Spencer on 12 May 2010 22:47

Mike Jones <luck(a)dasteem.invalid> wrote:

> I just stick IceWM on top of a basic X. As I keep my custom configs
> backed up, things tend to look and work the same at each upgrade.

Same here, modulo s/IceWM/twm/.

> I'm particularly interested in what progress has been made taming the
> runaway "automatic" mess Xorg made of X.

Care to expand on that? I'm using 11.0 (for reasons irrelevant here)
and will soon boot a 2nd box with 12.1. Is X in 13.0 truly bletcherous?

> Alternatives to HAL's "moving target" behaviour with devs would be
> attractive too.

Is hal mandatory in 13.x? I've just been googling up help on a
cdrecord failure and have learned that (as of last fall, anyhow) hald
was able to muck up cdercord.

--
Mike Spencer Nova Scotia, Canada
mspenbellscer(a)tallwhistlesships.ca
(Remove bells and whistles)

From: Mike Jones on 13 May 2010 06:17
Responding to Mike Spencer:

> Mike Jones <luck(a)dasteem.invalid> wrote:
>
>> I just stick IceWM on top of a basic X. As I keep my custom configs
>> backed up, things tend to look and work the same at each upgrade.
>
> Same here, modulo s/IceWM/twm/.
>
>> I'm particularly interested in what progress has been made taming the
>> runaway "automatic" mess Xorg made of X.
>
> Care to expand on that? I'm using 11.0 (for reasons irrelevant here)
> and will soon boot a 2nd box with 12.1. Is X in 13.0 truly bletcherous?


I hit lockup bugs with 11 and went back to 10.2 until 12.2 seemed to have
got the bugs sorted. I'm seeing the same pattern with the 13.? release.

Xorg have made some "significant (BETA) progress" that not only makes X
more complex to set up, but actively gets in the way of nailing things
down with an xorg.conf. By the time 13.2 comes out there will probably be
enough online "How do I...?" documentation for me to switch from 12.2.


>> Alternatives to HAL's "moving target" behaviour with devs would be
>> attractive too.
>
> Is hal mandatory in 13.x? I've just been googling up help on a cdrecord
> failure and have learned that (as of last fall, anyhow) hald was able to
> muck up cdercord.


The only reason I left HAL active was to mount up MP3 players and digital
cameras. I now have a udev-rules trick that replaces HAL and nails
manually mounted USB devices to their own permanent /dev/XYZ symlinks.

As you can tell, I'm not impressed with all these new KDE-style "I can't
believe its not Windows!" things that are creeping into Slackware as if
they are universally wanted. I'm of the "Nail it down with sensible
configs" school. (The VectorLinux Lite guys seem to think similarly.)

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Mike Spencer on 13 May 2010 15:09

Mike Jones <luck(a)dasteem.invalid> wrote:

>> Responding to Mike Spencer:
>
>> Care to expand on that? I'm using 11.0 (for reasons irrelevant here)
>> and will soon boot a 2nd box with 12.1. Is X in 13.0 truly bletcherous?
>
> I hit lockup bugs with 11 and went back to 10.2 until 12.2 seemed to
> have got the bugs sorted. I'm seeing the same pattern with the 13.?
> release.

I've had no lockups with Xorg on Slack 11. There's one odd little
thing: sometimes an xterm fails to recapture focus when the X-cursor
moves into it so that keystrokes evoke no response. Corrects after
twiddling the mouse in and out of the window. Otherwise, no problems.

> Xorg have made some "significant (BETA) progress" that not only
> makes X more complex to set up, but actively gets in the way of
> nailing things down with an xorg.conf. By the time 13.2 comes out
> there will probably be enough online "How do I...?" documentation
> for me to switch from 12.2.

Well, I think I'll just sit this one out, too. 10.1 and 11 are
working for me. I'll put 12.1 on one box because several apps are
significantly updated therein (e.g. cdrecord) and I already have the
CDs.


Tnx for the reply.

--
Mike Spencer Nova Scotia, Canada
From: Mike Jones on 13 May 2010 15:37
Responding to Mike Spencer:

> Mike Jones <luck(a)dasteem.invalid> wrote:
>
>>> Responding to Mike Spencer:
>>
>>> Care to expand on that? I'm using 11.0 (for reasons irrelevant here)
>>> and will soon boot a 2nd box with 12.1. Is X in 13.0 truly
>>> bletcherous?
>>
>> I hit lockup bugs with 11 and went back to 10.2 until 12.2 seemed to
>> have got the bugs sorted. I'm seeing the same pattern with the 13.?
>> release.
>
> I've had no lockups with Xorg on Slack 11. There's one odd little
> thing: sometimes an xterm fails to recapture focus when the X-cursor
> moves into it so that keystrokes evoke no response. Corrects after
> twiddling the mouse in and out of the window. Otherwise, no problems.
>
>> Xorg have made some "significant (BETA) progress" that not only makes X
>> more complex to set up, but actively gets in the way of nailing things
>> down with an xorg.conf. By the time 13.2 comes out there will probably
>> be enough online "How do I...?" documentation for me to switch from
>> 12.2.
>
> Well, I think I'll just sit this one out, too. 10.1 and 11 are working
> for me. I'll put 12.1 on one box because several apps are significantly
> updated therein (e.g. cdrecord) and I already have the CDs.
>
>
> Tnx for the reply.


12.2 has been pretty much rock solid for me, and even numbers are usually
better than odd ones when it comes to Linux version numbers. ;)

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Richard Herbert on 13 May 2010 18:16
On Thu, 13 May 2010 19:37:27 +0000, Mike Jones wrote:

> 12.2 has been pretty much rock solid for me, and even numbers are
> usually better than odd ones when it comes to Linux version numbers. ;)

Which "odd" version of Linux would you be referring to? Or are you just
saying that even-numbered versions of anything are usually better than odd
ones? I'm not THAT supertitious, but I gotta admit it took me a long time
to get around from upgrading Slackware 12.2 to 13.0. ;-)

--
Richard Herbert
Registered Linux user 14329
If there's nothing wrong with me, then ...
there must be something wrong with the Universe!
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: kernel upgrade - touchpad unexpected behaviour
Next: PHP with unixODBC support