From mboxrd@z Thu Jan 1 00:00:00 1970 From: quanstro@quanstro.net (erik quanstrom) Date: Mon, 4 Apr 2011 12:02:10 -0400 Subject: [9fans] more "Plan 9 from Bell Labs" questions In-Reply-To: <68AEF27C-63A5-4508-BD1C-19AB8E5A6DD8@fastmail.fm> References: <68AEF27C-63A5-4508-BD1C-19AB8E5A6DD8@fastmail.fm> Message-ID: Topicbox-Message-UUID: c8440898-ead6-11e9-9d60-3106f5b1d025 On Mon Apr 4 11:54:45 EDT 2011, eekee57 at fastmail.fm wrote: > > On 4 Apr 2011, at 9:36 am, faif wrote: > > > > "Using streams to implement network interfaces in the kernel allows > > protocols to be connected together dynamically, such as to attach the > > same TTY driver to TCP, URP, and IL connections, but Plan 9 makes no > > use of this configurability." > > This one makes no sense to me. TTY driver... network interface? If > those two things make sense together, it still makes no sense to put > them both together in the Plan 9's kernel, I'm sure. plan 9 is fairly unique in that a file server can just as easily be in the kernel, or in user space, or on another machine; and a device driver is nothing more than a file server. put 'em all in the kernel for purely parsimonious reasons doesn't make too much sense to me. but that's just in theory. in practice, it's been easiest, simplist and fastest to put most hw drivers in the kernel. by the way, you can plug file servers together regardless of where they live. kernel, user space, another machine. it matters not. - erik