Re: [dev] Lessons Learned from 30 Years of MINIX

2016-03-06 Thread stanio
* Anselm R Garbe 2016-03-06 15:56 > I agree, though this is not stricly a problem with monolithic approaches > either. > In the end you have to trust the process governor to limit the > privileges of a process (or thread) to its specification/requirement. > If the governor is only one SPOF

Re: [dev] Lessons Learned from 30 Years of MINIX

2016-03-06 Thread Anselm R Garbe
On 6 March 2016 at 15:39, wrote: > * Anselm R Garbe 2016-03-06 14:20 >> On 6 March 2016 at 13:47, robin wrote: >> > Microkernels defenitely resonates with the unix philosophy "do one thing >> > and >> > do it well". >> > Having everything,

Re: [dev] Lessons Learned from 30 Years of MINIX

2016-03-06 Thread stanio
* Anselm R Garbe 2016-03-06 14:20 > On 6 March 2016 at 13:47, robin wrote: > > Microkernels defenitely resonates with the unix philosophy "do one thing and > > do it well". > > Having everything, except FUSE and such, in the kernel is doing more than > > one thing. >

Re: [dev] Lessons Learned from 30 Years of MINIX

2016-03-06 Thread Anselm R Garbe
On 6 March 2016 at 13:47, robin wrote: > Microkernels defenitely resonates with the unix philosophy "do one thing and > do it well". > Having everything, except FUSE and such, in the kernel is doing more than > one thing. IMHO the architectural decision for a

Re: [dev] Lessons Learned from 30 Years of MINIX

2016-03-06 Thread robin
On Fri, Mar 04, 2016 at 11:47:48PM +0100, FRIGN wrote: > On Fri, 4 Mar 2016 14:43:40 -0500 > Greg Reagle wrote: > > > The connection to suckless is that the author has strong minimalist and > > anti-bloat tendencies. > > when did this turn into a Hacker News here? > > --