Hmmm ... this push does not do enforcing of the read-only property for objects, just adds the property to the CLI. I am working on the enforcement. I've hit a snag.
NCP's do not have properties, they have sub-objects. This means that for the "automatic" NCP, the NCU's are the ones that are read-only. Is the NCP itself read-only? If so, then the UI has to filter by the name "automatic" to make it read-only. If the NCP is not read-only but the NCU's are, then more NCU's can be created for the "automatic" NCP. Which is the direction we want here? Thanks, Anurag Anurag.Maskey at Sun.COM wrote: > Author: Anurag S. Maskey <Anurag.Maskey at Sun.COM> > Repository: /hg/nwam/nwam1 > Latest revision: 84ba9a1634bb06a1dbcdcf2ef257bf38eb30c3c2 > Total changesets: 1 > Log message: > "read-only" property missing from the nwamcfg and grammar > > Files: > update: usr/src/cmd/cmd-inet/usr.sbin/nwamcfg/nwamcfg.c > update: usr/src/cmd/cmd-inet/usr.sbin/nwamcfg/nwamcfg.h > update: usr/src/cmd/cmd-inet/usr.sbin/nwamcfg/nwamcfg_grammar.y > update: usr/src/cmd/cmd-inet/usr.sbin/nwamcfg/nwamcfg_lex.l > _______________________________________________ > nwam-dev mailing list > nwam-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/nwam-dev >
