<mark_weaver>I found that to be an issue with my thinkpads, so I worked around it by making a little script that repeatedly suspends every 10 seconds. I Ctrl-C out of the loop when I really mean to wake it up.
<wingo>just write something to /sys/power/resume in the initrd and you are done
<mark_weaver>the method I've always used is to simply pass 'resume=/dev/sdaN' on the kernel command line, but I know there's another way to do it from within the initrd, and that's more general because it supports cases where modules need to be loaded in order to access the swap partition.
<mark_weaver>if there's only one swap device/file, they could use that one, but I don't know what it would do if there's more than one.
<davexunit>that reminds me, I need to configure a swap device on here
<mark_weaver>the thing is, passing 'resume=' is not usually how things are done in practice these days, and I kind of doubt that the kernel remembers that the initrd made a failed attempt to resume by writing something to /sys/power/resume
<wingo>civodul: so. base-services defines the udev service. but desktop-services should add upower, colord, and elogind udev rules.
<wingo>still should do the thing civodul said about mentioning services by name, but oh well
<wingo>though, if we did make udev look for rules in the system profile that would be another way of fixing udev :)
<mark_weaver>for that matter, I'd be thrilled if someone looked more at my 'wip-network-manager' branch and got it working :)
<wingo>probably won't be me in the near future :) getting married next w/e, whee
<mark_weaver>wingo: it's very tempting isn't it? the one reservation I have is this: I want to be able to install packages without worrying that they might do something dumb. basically, I don't want adding a package to 'packages' to run any code unless I ask for it.
<wingo>so here's what i would want. by default udev-service looks at the packages installed in your profile and also some base set of packages. you can override and specify the full set of packages manually.
<civodul>wingo: ooh next week-end, pressure increases! ;-)
<mark_weaver>e.g. changing %base-services and %desktop-services into procedures, and provide some way for services to advertise themselves to other services, e.g. elogind should be able to tell 'udev' and 'dbus': "hey, please add me to your list"
<wingo>civodul: :) things are all done, madame la procureur has signed off on the thing ;)
<mark_weaver>wingo: how about 'udev-service' looks at your other services, instead of the full set of packages?
<wingo>ok i get that. civodul what do you think about having a base-services procedure, and a desktop-services procedure?
<mark_weaver>the other thing is, it might make more sense for 'elogind' to tell 'udev' and 'dbus' about itself, rather than expecting 'udev' and 'dbus' to look through the list of services and recognize which ones should have rules or whatever.
<wingo>it would be simpler if dbus were in base-services...
<mark_weaver>but maybe services like 'elogind' could provide an alist with keys that 'udev' and 'dbus' know about.
<mark_weaver>although I like to hash things out on IRC, I find that civodul much prefers the ML, and I think that's reasonable, since people not on IRC (or not right now) should be able to participate in the discussion.