On Fri, Jan 09, 2009 at 10:45:23PM -0500, [email protected] wrote:
> http://opensolaris.org/os/project/brussels/files/brussels2.pdf
> there- comments/opinions are invited.
Well, ipamd is probably a good idea, however, IMHO the syntax is to noisy
aka redundant and should be oriented to zfs commands - the comamnds,
which are usually much more used, than any other multi-command aka
'command line tools with sub-commands to be able to better document valid
switch/option combinations'.
In detail: It looks like, that ipadm cmd is always related to a specific
interface. So why the cluttering '-interface' at the end of create, modify?
Similar thing with address related stuff. If the command is related to a
specific address of an interface, this is already indicated by the '-a'
switch. So why the '-address' noise at the end of of add, delete? OK,
there is one exception wrt. to delete all addr from an interface. But
allowing an '-a all' analog to 'zfs list -t all' shouln't be too
challenging ...
Next thing is the set,show,init subcmd. It seems to be always related to a
"property". So why the noisy '-prop' at the end of the command and why
than the '-p' switch again ? What is the problem with
ipadm {set|get|init} key[=value] ...
Of course, the 'show' subcmd mimics some CLIs seen on certain
Switches/Routers, however, I would prefer an alias named 'list' ...
Last but not least I don't like the mandatory -P ... Isn't the utility
able to find out, what should be used if omitted aka able to use
reasonable defaults? E.g. if an IPv6 addr or -if6_intf_id is specified,
it implies -P v6. If an IPv4 addr is specified, type should default to v4
if not specified otherwise, etc. ...
My 2ยข ;-)
Regards,
jel.
--
Otto-von-Guericke University http://www.cs.uni-magdeburg.de/
Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2
39106 Magdeburg, Germany Tel: +49 391 67 12768
_______________________________________________
networking-discuss mailing list
[email protected]
