From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9f3897940711221400q5d64714bk5db9115b905f9e56@mail.gmail.com> Date: Thu, 22 Nov 2007 23:00:04 +0100 From: "=?UTF-8?Q?Pawe=C5=82_Lasek?=" To: weigelt@metux.de, "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Nine4Linux [WAS: Glendix?] In-Reply-To: <20071122180134.GD13964@nibiru.local> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071116084254.GD17281@nibiru.local> <1b69251dfdcb6b8022ff78767f07ce86@quanstro.net> <20071122180134.GD13964@nibiru.local> Cc: Topicbox-Message-UUID: 0919daa4-ead3-11e9-9d60-3106f5b1d025 On Nov 22, 2007 7:01 PM, Enrico Weigelt wrote: > * erik quanstrom wrote: > > have you seen p9p (http://swtch.com/plan9port)? > > Yes, but I'm not yet sure if this is really what I have in mind. > But at least its a good step in that direction. > > I'm intending to trim down uclibc and maybe put the p9p base > library stuff (9P handling, etc) there. This should save us > the glibc overhead. It could be beneficial to talk with the guys behind RSBAC ( http://www.rsbac.org ). While their security model may differ from Plan 9's, their framework should be a fine tool to add proper semantics, like allowing everybody to have custom namespaces or Plan9 capabilities. After all, their system IIRC discards the whole security mechanism from Unix supplying different modules to create whatever policy you want. And glibc should be damned. IMHO, the main library in the system should be a library written for that OS, not some "multi-platform" thingy designed for different system than its main use :p > cu > -- > --------------------------------------------------------------------- > Enrico Weigelt == metux IT service - http://www.metux.de/ > --------------------------------------------------------------------- -- Paul Lasek