On Fri, 7 Apr 2000, H. Peter Anvin wrote:
> As far as numbers being maintainable: I have to apply the sledgehammer
> just as much to device *names* as I have to device *numbers*... there is
> just as much of a conflict problem in the string space (/dev namespace)
> as it is in the number space. Anything else is a fallacy.
Right now everything has both a name and a number. How can just having a
name be anything but simpler from the maintenance standpoint?
> Agreed. However, having a kernel-internal API for doing this instead of
> a bunch of ad hoc parsers, and a reasonable formatting (again, to allow
> user space to have structured tools like SNMP) would reduce the size of
> the kernel and simplify the user-space tools.
Pick a simplified markup language, preferably compatible with XML parsers.
Alternately, pick something that is consistent enough that it can
trivially be converted to XML.
> This *could* be done totally in user space, but would mean keeping a
> copy of the tree in user space at all times. Having easy access to the
> MIB IDs via the filesystem is, IMNSHO, a very good thing.
Huh? I don't see SNMP compatibility as mandatory, so I can't see why I'd
need this userspace tree at all..
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:11 EST