I. Szczesniak writes: > > - Clearview needs the /dev/net namespace for the flexible interface > > names and the zone-visible interfaces. > > The /dev/net name space just received it's first -1. The idea is a > maintenance hazard and should not be implemented. Devices are hardware > and /dev should mainly be used to describe hardware with only a few > exceptions.
"Few?" There are dozens of pseudo drivers in Solaris. kmem, arp, console, cryptoadm, icmp[6], ip[6], tcp[6], keysock, log, logindemux, null, zero, poll, random, ... They represent all sorts of things, including redirectors (/dev/console), control nodes (/dev/cryptoadm), protocol domains (/dev/ip), and so on. Some facet of "real" hardware exists under some of those, but not all, nor are they hardware drivers. > Physical network cards do not fall under the exception > rule and IP addresses are even less worthy to be listed under /dev In that case, you might want to participate in the Clearview project, which is driving the demand for this feature. Voting against one feature the larger devfs project enables seems off-topic, at least in this thread. Currently, it's not possible to grant even limited packet monitoring (snoop, ethereal) access within non-global zones due to the lack of "real" hardware in a zone. It's also not possible to monitor loopback traffic. Nor is it easy to view a single traffic for a single IPMP group. The /dev/net/* idea fixes those problems without creating overlap with any existing /dev/* nodes. If you've got better ways to do those things, then please do get involved. "No" doesn't help solve those problems. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
