What kinds of things would you want in the GNU OS?

news news at sun.Eng.Sun.COM
Wed May 24 05:09:26 AEST 1989


What kinds of things should be in the GNU Kernel?
What kinds of features or design rationale should it use?
For instance:

File system:	SysV vs Berkeley? Something better?
		Embedded file types? >32-bit file offsets?

Security:	ACLs? Get rid of root? Security monitors? Auditing?
		Provably secure(A1)?

Scheduler:	Real-time support? Task-driven? Event driven?
		Direct brain hookups:-)?

Virtual Memory:	Should GNU run on non-VM machines? Algorithm ideas?
		How general (map *everything* into VM space, like Multics)?
		Shared libraries?

Networking:	NFS? RFS? Something better?
		Interfaces: Streams? TLI? Something better?
		TCP/IP? OSI? SAA/SNA:-)?
		RPC Services? What kind?

Overall Design:	What nice ideas from other OSes could we use?
		Multics? VMS? VM? DG/OS?
		Fault tolerance?

How about this? Make everything a user process which serves
a resource to a client. Resources include the CPU (scheduler),
memory (VM), disk (file system), network (sockets, etc),
serial lines (terminal handlers), etc. Each server determines the access
method and security criteria for its service. Make no arbitrary policy
decisions regarding a service! Don't like the VM server? Replace it! You
could have a security monitor provide a security policy on behalf of
your file system or IPC mechanisms. If you have no need for security,
don't run the monitor.



More information about the Comp.unix.wizards mailing list