sax2 replacement?
in [Suse]
|
Prev: OpenSuses 11.0 & cpuset
Next: Servers down
From: Eef Hartman on 20 Jul 2010 04:13 mjt <myswtestYOURSHOES(a)gmail.com> wrote: > On Fri, 9 Jul 2010 16:56:39 +0200 > houghi <houghi(a)houghi.org.invalid> wrote: > >> I tried to find the replacement for sax2 as it is removed from 11.2. I >> could not a replacement. Somebody an idea? >> >> (And please do not start moaning that it is gone. It is gone.) > > Actually, it does exist in 11.2 ... it's in the OSS repo. > It's been deprecated, though. There's a typo in the original message, houghi meant 11.3, not .2 -- ****************************************************************** ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-27 82525 ** ******************************************************************
From: Eef Hartman on 20 Jul 2010 04:34 JT <reply_only_to(a)newsgroup.nl> wrote: > Maybe missing the point here (English being my 2nd lingo ;-) ), but I > myself haven't used sax2 for the better part of 5 years now. We use it to update the display info on our image deployment (we made an image ONCE, then deploy it to all new machines that are bought. In the image there is code like this: if ( test -f /.firstboot ) then echo "Configuring new hardware... (first boot)" /sbin/yast2 sound all /usr/sbin/sax2 -a -r # Remove /.firstboot rm -f /.firstboot # Reboot to new hardware config.... /sbin/reboot fi So there we use yast to detect the kind of sound card and sax2 to detect the kind of (mostly but not always NVidia) screen adapter, keyboard and mouse ON those new machines after deployment. -- ****************************************************************** ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-27 82525 ** ******************************************************************
From: Will Honea on 23 Jul 2010 00:27 Philipp Thomas wrote: > On Sun, 11 Jul 2010 20:50:16 +0200, houghi <houghi(a)houghi.org.invalid> > wrote: > >>It is 10 years back in tim. :-( > > No, definitely not! The X server of 10 years ago had next to no > autodetection and needed a configuration file. The current X server > can detect most stuff automatically and does not need a configuration > file. If you need one, you can tell the X server to generate one based > on the values it determined. > Granted a GUI tool like sax2 to tweak xorg.conf would be nice but so > far nobody has stepped up write such a tool. Between my own stuff and that of the churches I do volunteer maintenance for, I see a lot of old hardware - we are all to cash strapped to keep current and the churches use mostly donated hardware, stuff that the donors give away when they upgrade. So far, 11.3 has been a royal PITA simply because of all the hoops I have to jump through just to get usable video. Don't get me wrong, I'm a fan of 11.3 - once I get it running - and will likely implement it everywhere I can but to do that I have to keep a long cheat sheet of steps needed to get the video working. This is not just on Nvidia video. Some of the older Intel chips, like the i815, are as bad or worse than than my own Nvidia GeForce 6100. What I have to do in a whole bunch of steps is the same thing Sax2 did in one pass. I don't need Sax2 just tweek the setup, I need it to avoid the hassle WHEN AUTODETECTION FAILS. 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. When it works, it's great but that's no reason to omit the tools needed to get going when it doesn't. That's akin to welding the hood shut on a new car because it "just works" so the owner has no need to get under the hood. -- Will Honea
From: J G Miller on 23 Jul 2010 09:02 On Thursday, July 22nd, 2010 at 22:27:57h -0600, Will Honea wrote: > > That's akin to welding the hood shut on a new car because it > "just works" so the owner has no need to get under the hood. Sadly this is the direction that openSUSE and Mint Linux and Ubuntu had adopted and are blindly following -- in terms of the bootup sequence and launching of X11 session (particularly with gdm) it is being turned into an uncontrollable black box process.
From: mjt on 23 Jul 2010 12:43
On Fri, 23 Jul 2010 13:02:00 +0000 (UTC) J G Miller <miller(a)yoyo.ORG> wrote: > On Thursday, July 22nd, 2010 at 22:27:57h -0600, Will Honea wrote: > > > > That's akin to welding the hood shut on a new car because it > > "just works" so the owner has no need to get under the hood. > > Sadly this is the direction that openSUSE and Mint Linux and > Ubuntu had adopted and are blindly following -- in terms of > the bootup sequence and launching of X11 session (particularly > with gdm) it is being turned into an uncontrollable black box process. 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. -- Just remember: when you go to court, you are trusting your fate to twelve people that weren't smart enough to get out of jury duty! <<< Remove YOURSHOES to email me >>> |