On Friday, November 8, 2002, at 11:42 PM, Frode Nordahl wrote:
Why do you need an acpid?
misc stuff
That's not going to get you anywhere.
instruct dhclient to get a new lease on resume (maybe free it on
sleep),
try to configure wlan if no link detected on ethernet etc.
This doesn't warrant an 'acpid'.
I put my computer to sleep instead of turning it of most of the time,
and having to run killall dhclient; dhclient dc0 every time I resume
it after coming home / go to work is a bit annoying :)
So fix the real problem.
I'm sure people have this and other things they want to configure their
computer to do on sleep / resume.
I'm sure that you think that FreeBSD needs an acpid because Linux
has an acpid.
For your specific, narrow example, how about you fix the
sleep/wakeup sequencing in FreeBSD's ethernet drivers so that
they correctly queue link-down/link-up events, and then fix
dhclient so that when it sees a link-down to link-up transition,
it reacquires its lease.
Then you will have solved a real problem in an almost correct
fashion, and people like me won't think you're a mindless drone.
Most of the other things that an 'acpid' would do are specific
examples of more general classes of events, for which software
should be able to request notification and handle it accordingly.
For an ugly but effective middle path, look at the Darwin
configd/Kicker mechanism. I don't recommend porting it because
the problems deserve better solutions, but perhaps it'll get
you thinking in a more general fashion.
= Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
