Hi! > > Still, what we definitely want is _one single_ architecture independent > > whitelist. And there is where hal-info comes in which is easy to update > > for distributions etc. IMHO. I'm seeing this difficulty with the two > > different lists for quite some time know and thought about possible > > solutions. AFAICS, the main reason for heaving s2ram internal whitelist is > > that s2ram can be used completely without any trace of hal on some > > system. > > Today I'd say that 99% of all machines that need suspend quirks use HAL > anyway... just based on what software people use.. (embedded stuff > is
And what? Unfortunately for hal, the 1% of remaining machines is what matters, like my development machine. > Anyway, I know it's fine and all to not require HAL.. I mean, some > people do go out of their way to avoid having glib or Qt installed and > they're happy with twm instead of KDE/NOME/XFCE and so on... but in this > case it's just damn impractical since it means a ton of duplication > currently is going on... but as the maintainer of HAL I'm obviously > rather biased, hehe :-). I guess I'm just frustrated about the whole > thing. Anyway, sorry for ranting. It is just wrong layering. For debugging, it is important that s2ram works from init=/bin/bash... and AFAICT you can't do that with hal. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel