On Tue, 2009-10-20 at 01:16 +1100, Darren Reed wrote:
> Sebastien Roy wrote:
> > On Mon, 2009-10-19 at 23:50 +1100, Darren Reed wrote:
> >
> >> In many system administration environments, it is desirable to do
> >> system installation via jumpstart. Although jumpstart as we know
> >> it today will go away with IPS, IPS will provide a new mechanism
> >> to do automated network installs so this need does not go away...
> >>
> >> As it is today, dladm only appears to support automated installs
> >> creating bridge devices, leaving IP tunnels, vnics, aggregations
> >> and others out in the cold.
> >>
> >> How many of those that do not support -R can be "fixed"?
> >>
> >
> > It looks like every dladm create-* subcommand supports a -R option. I'm
> > unclear about what you're referring to.
> >
>
> $ dladm |& grep create
> create-aggr [-t] [-P <policy>] [-L <mode>] [-T <time>] [-u
> <address>]
> create-secobj [-t] [-f <file>] -c <class> <secobj>
> create-vlan [-ft] -l <link> -v <vid> [link]
> create-iptun [-t] -T <type> [-a {local|remote}=<addr>,...] <link>]
> create-vnic [-t] -l <link> [-m <value> | auto |
> create-etherstub [-t] <link>
> create-bridge [-R <root-dir>] [-P <protect>] [-p <priority>]
>
> oh... the "usage" output disagrees with the man page...
> silly me for not checking the man page.
That seems like a bug in the create-bridge synopsis. I believe -R was
taken out of all of the subcommand synopses in the usage output because
is caused too much clutter and was redundant. It looks like one was
re-introduced with create-bridge.
-Seb
_______________________________________________
networking-discuss mailing list
[email protected]
