On 26/02/2010 10:29, Casper.Dik at Sun.COM wrote: > >> Why just those two ? In general other than "type" I think all of the >> user_attr(4) keywords should be applicable in prof_attr (I wouldn't >> object to type being able to be specified in prof_attr though). > >> In particular: roles, project, lock_after_retries but all the others >> too. For me project would be the most useful of those but I can see an >> need for the others too. >> >> Similarly the TX specific ones would be useful in prof_attr(4) for >> defining collections of users all with the same operating label range >> (min_label and clearance keywords). > > While I agree with assessment in principle, each and every additional > keyword requires the same amount of additional code, so it's not "free" > to add additional keywords. > > I want to implement these keywords first and then we'll have a discussion > about the additional keywords and the market requirements.
I'm happy with that, particularly since there are a couple of existing user_attr(4) keywords (idlecmd, idletime) that are probably EOF given CDE is no longer shipped. The case gets my +1 as specified. -- Darren J Moffat
