Peter Pentchev <[EMAIL PROTECTED]> types:
> On Thu, Oct 11, 2001 at 06:48:48PM -0500, Mike Meyer wrote:
> > Cyrille Lefevre <[EMAIL PROTECTED]> types:
> > > Mike Meyer wrote:
> > > [snip]
> > > > conf/21722 The mixer settings are lost on system reboot.
> > > >
> > > > This should probably be closed due to the work being done on the
> > > > NetBSD rc system. The same functionality can be provided as a port,
> > > > which is probably better anyway. I'll do that if this one gets closed.
> > > much better is to keep it, at least to remember that something like
> > > that have to be done.
> > I'm not convinced it needs to be done. It's not really a critical
> > feature, and very few people seem to miss it. It makes a lot more
> > sense as a port that the few people who miss it can install. I've
> > already got the script; I just want to make sure I don't do the work
> > of turning it into a port only to have this thing committed.
> > The script is so trivial I use it as an example of how to do rc.d
> > scripts on -questions.
> The script is indeed trivial, and I could commit it as a port,
> listing you as maintainer. I have just one question: would it be
> wise to have /var/db/mixer-state removed upon port deinstall, or should
> it be left behind, just in case? I think it would rather be removed
> to leave the system cleaner; if it is removed as part of a port update,
> it will be regenerated at the next shutdown anyway.
Sure, go ahead and commit it as a port listing me as maintainer. Yes,
I'd remove /var/db/mixer-state when you deinstall the port. If someone
really wants to save the mixer state, they can do it by hand, or using
any of a number of different tools in the ports tree.
After the port is commited, you can close PR conf/21722.
Thanx,
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Q: How do you make the gods laugh? A: Tell them your plans.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
