sax2 replacement?
in [Suse]
|
Prev: OpenSuses 11.0 & cpuset
Next: Servers down
From: Will Honea on 23 Jul 2010 16:40 houghi wrote: > mjt wrote: >> To put my COLA hat on for a moment, I'd say this is >> a good thing, as it makes for GNU/Linux adoption for >> the average user easier. One of the reasons adoption >> has been slow in coming is that GNU/Linux has been >> too much "hands on" to get it running or to fix some >> issue or to make an enhancement. > > No, it isn't. It is good that things are automated. It is NOT good that > the tool isn't supported anymore. > > Doing things automagically never should block the way of doing it in > other ways. > > What should happen is AND/AND not OR/OR. Also the focus is way to much > on KDE/GNOME instead of Xorg where everybody would benefit including KDE > and GNOME. My point exactly! Just because the developers worked hard to make the program smart enough to do most of the job we used to do manually doesn't mean we no longer need access to lower level functionality for some unique situations. Sax2 was a step above manually creating and maintaining the xorg.conf file, the new stuff fragments xorg.conf - not necessarily a bad thing - so we have less detail work to do IN MOST CASES. I applaud the ease of use moves but I deplore the loss of transparency when it is necessary - not just convenient but actually necessary - to tweek the low level stuff. Automation should be an additional capability/method, not a complete replacement. -- Will Honea
From: Paul J Gans on 23 Jul 2010 16:57 Will Honea <whonea(a)yahoo.com> wrote: >houghi wrote: >> mjt wrote: >>> To put my COLA hat on for a moment, I'd say this is >>> a good thing, as it makes for GNU/Linux adoption for >>> the average user easier. One of the reasons adoption >>> has been slow in coming is that GNU/Linux has been >>> too much "hands on" to get it running or to fix some >>> issue or to make an enhancement. >> >> No, it isn't. It is good that things are automated. It is NOT good that >> the tool isn't supported anymore. >> >> Doing things automagically never should block the way of doing it in >> other ways. >> >> What should happen is AND/AND not OR/OR. Also the focus is way to much >> on KDE/GNOME instead of Xorg where everybody would benefit including KDE >> and GNOME. >My point exactly! Just because the developers worked hard to make the >program smart enough to do most of the job we used to do manually doesn't >mean we no longer need access to lower level functionality for some unique >situations. Sax2 was a step above manually creating and maintaining the >xorg.conf file, the new stuff fragments xorg.conf - not necessarily a bad >thing - so we have less detail work to do IN MOST CASES. >I applaud the ease of use moves but I deplore the loss of transparency when >it is necessary - not just convenient but actually necessary - to tweek the >low level stuff. Automation should be an additional capability/method, not >a complete replacement. I fully agree. Running toward automation only means going down the path toward Windows. -- --- Paul J. Gans
From: Philipp Thomas on 25 Jul 2010 19:23
On Thu, 22 Jul 2010 22:27:57 -0600, Will Honea <whonea(a)yahoo.com> wrote: >Some of the older Intel chips, like the i815, are as bad or worse than than >my own Nvidia GeForce 6100. The thing is that the upstreams Intel X-Developers don't have any hardware with the i815 anymore, same with our (SuSE) X developers. Without hardware it's extremely hard to fix bugs or improve the situation. >Therein lies my beef with the new setup: it isn't smart enough to fail >gracefully and provide the tools to get to where I need to be when it can't >finish the job. It's the same game as with nearly every openSUSE versions. Some hardwae is just too old to run the current openSUSE version on. Philipp |