On Tue, Jun 9, 2009 at 10:01 PM, Jerry Gilliam<jerry.gilliam at sun.com> wrote: > > I am submitting the following as a fast-track on behalf of myself, with > a timeout set for 06/16/2009. ?Patch/micro binding is requested. > > ------------- > > 1. Introduction > ? 1.1. Project/Component Working Name: > ? ? ? ?EOF UCB Device Names ... > ? ? ? ?For patch/macro release relief, it is proposed to introduce a > ? ? ? ?service to manage ucblinks: svc:/system/ucb-device-names. ?With > ? ? ? ?a default of disabled, the out-of-the box experience will be > ? ? ? ?improved with no ucblinks generated and existing ucb compatible > ? ? ? ?names removed. ?Enabling the service will generate ucb compatible > ? ? ? ?names by running ucblinks, for any customer who desires this > ? ? ? ?compatibility to be retained.
Why add additional complexity? Someone wishing to disable this behaviour already has 3 (at least) options - pkgrm SUNWscpu, rm /usr/ucb/ucblinks, or edit /etc/init.d/devlinks. If it's disabled by default then customers who care could run it manually or edit the devlinks script to reactivate it. Adding a service to manage ucblinks seems to me to be hoping that two wrongs will make a right. (If devlinks were a service then whether ucblinks were enabled could simply be a property of that service. Moving the buggy bit you want to be rid of to a service while leaving the primary component unchanged doesn't seem right.) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
