> but /net is not a fs. '#I' the ip stack and '#l' the ethernet device > are usually bound in union on /net. ip subsumes its subprotocols and > arp. there is nothing preventing one from adding a new networking > protocol nor is there anything preventing one from adding a new type > of networking device. for example, one could run ip over atm > networking with no problems. i think this sort of thing is done with > blue gene. you could also run (say) xns over ethernet and have it all > appear like a big, happy family in /net.
Oooh, oooh, the gauntlet has been thrown down. Who will pick up the challenge of finding a way to implement RFC1149 (or 2549, if you want QoS) and binding it to /net? /net/speckled_jim0? (That's a reference to Blackadder for those who aren't fans of British comedy and in particular Rowan Atkinson (who, slightly apropos to our community, holds a degree in electrical engineering).) Bonus points if you can figure out how to get paid for it or get it funded by DARPA. And no, I haven't been drinking save for the Cherry Coke I'm finishing off after lunch. BLS
