Lubomir Sedlacik <salo@Xtrmntr.org>  wrote:
 > [ moving this thread to tech-userlevel, please remove current-users in
 > the next post ]
 > > > is there any reason why is the control utility inconsistently named
 > > > cgdconfig(8) and not cgdctl(8) to follow the way NetBSD does it?
 > > > cgdconfig(8) sounds more like FreeBSD tool for me.
 > >=20
 > > Well, there are already ccdconfig(8) and vnconfig(8). It looks pretty
 > > consistent to me.
 > 
 > well, i'd say they should be renamed too before it will end in chaotic
 > mess.  it is really confusing for newcomers when 1/3 of tools are called
 > *config and other 2/3 are called *ctl.  i can understand why tools like
 > ifconfig use their names for historical reasons but i don't see any
 > reason why new tools should be called *config when most native NetBSD
 > utilities uses *ctl suffix.

Don't forget wsconscfg(8) and wsconsctl(8).

I'm sure there's a reason that it's not "wsconsconfig" but I don't know
what it is. I'm also sure there's a distinction between 'config' and 'ctl'
in this case.  Maybe 'ctl' refers to knob-twisting programs, and 'config'
refers to setup type programs.

All the 'ctl's directly (or indirectly) manipulate kernel variables. All
the 'config's seem to instantiate functionality.

At least, that's my unofficial read on the matter.


---
Real PC Serial console & remote reset - The PC Weasel! http://www.realweasel.com