J?rg Barfurth wrote:
> Garrett D'Amore schrieb:
>> Cyril Plisko wrote:
>
>>> Since there is new utility being created and there are no issues
>>> with backward compatibility, - were any thoughts given to the name
>>> "audioadm" vs "audioctl" ?
>>>
>>> It seems that these days Solaris has many *adm tools, as opposed
>>> to only a few *ctl.
>>>
>>> raindrop:~$ ls /usr/man/man1*/*adm.1* | wc -l
>>> 66
>>> raindrop:~$ ls /usr/man/man1*/*ctl.1* | wc -l
>>> 7
>>> raindrop:~$
>>>
>>> Wouldn't it be consistent to stick to this (*adm) pattern ?
>>>
>>> And before you ask - no, I do not feel strongly about it - just an
>>> observation.
>>>
>>> [Spec materials deleted]
>>>
>>
>> Its not too late to change this. I actually thought about audioadm.
>> It wasn't clear to me that there was a consistency here; however, I'm
>> more than happy to concede the idea that there are more *adm
>> commands, and if folks prefer, I can trivially change the command now.
>>
>
> I'd expect a **adm command to have the purpose of administering a
> system service. Typically that would be an administrative (section 1M)
> command and require some form of privilege.
>
> For controlling a running service, in particular if I can do that as a
> user (section 1) I find **ctl more appropriate.
>
> As far as the pattern is concerned: almost all of the **adm commands
> are in section 1M, and the two that aren't on my system (NIS related
> admin) probably should be there too.
>
> If "audioadm" appears on the system, I'd expect it to provide the
> capability to create audio devices or control access to them, set
> global limit volumes or similar administration task with system scope.
>
> For changing volume and similar controls on audio devices I happen to
> own currently, I find "audioctl" or "audiocontrol" a better fit.
At present, this tool is used just by end-users to adjust personal
preferences. However, in the future it might be used to do some more
sophisticated things ... like configuring hotplug policies, etc.
Some settings could arguably said to be administration... such as the
configuration of jack retasking. (Is defining the purpose of jacks an
administrator or an end-user task? Its not clear to me.)
At the end of the day, I don't have a strong preference one way or the
other for the name. I think *ctl mostly evolved out of mixerctl.
As long is it isn't "audiotool". :-p
- Garrett
>
> Just my 2c
>
> - J?rg
>
