Re: The new X-Kernel !

[Tim Jansen]

On Monday 22 October 2001 02:10, you wrote:
> Neither - It is a resource allocation problem, which all UNIX style systems
> seem to lack. And second, it doesn't happen at the present time with
> mice/keyboard/display unless somebody (root) did not configure the system
> properly (as in leave the device inodes accessable to world) OR change the
> protection to permit access.
> Once a resource is allocated to a user session (not process) it should not
> be accessable to other users.

But what's the point of doing it in the kernel instead of the user space? 
Basically X11 is nothing but a library for accessing mice/keyboard/display 
plus some daemon that manages these resource and introduces some policies 
(for example each process gets one or more windows it can draw in). And 
especially the display clearly needs some policy enforced to be useful for 
several processes.

> It is NOT sufficient for things like tape drives. The only way to prevent
> conflict at the present time is to change the ownership of the inode, and
> ensure that the protection mask only permits user access. It is ALSO
> necessary to ensure that no other processes have that device open at the
> same time.

Why should several process be allowed to access a tape drive? Raw access, 
like the kernel driver will provide, that allows things like fast-forward 
must be coordinated, at least. You need a higher level interface that 
coordinates things among processes. 

I do agree that the neccessary IPC for the communication between such a 
higher-level driver and the processes that use it is a problem though. That's 
why I like FUSD (http://www.circlemud.org/~jelson/software/fusd/), it gives 
you the ability to create higher-level drivers in user-space that behave like 
kernel drivers. (And, BTW, makes fun stuff possible like accessing 
device files on other computers over the network, without rewriting 
applications)

bye...