mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: rothwell@holly-springs.nc.us (Michael Rothwell)
Cc: Josue.Amaro@oracle.com, linux-kernel@vger.kernel.org,
	unlisted-recipients:;;;@holly-springs.nc.us; (no To-header on
	input)
Subject: Re: Advanced Linux Kernel/Enterprise Linux Kernel
Date: Tue, 14 Nov 2000 23:25:02 -0500 (EST)	[thread overview]
Message-ID: <200011150425.eAF4P3l135592@saturn.cs.uml.edu> (raw)
In-Reply-To: <3A117311.8DC02909@holly-springs.nc.us> from "Michael Rothwell" at Nov 14, 2000 12:14:57 PM

Michael Rothwell writes:

> 1) Convenient remote terminal use. 
>
> Telnet, ssh, X windows, rsh, vnc, "screen," ethernet,
> serial, etc. I think we have this one.

Nope: /dev/audio, /dev/cdrom, /dev/floppy, fonts, etc.

Also one would want a local window manager for performance,
but this tends to interfere with starting apps on the other
system.

> 4) A high reliability internal file system. 

Now we want it distributed, with version control, with
mirroring onto N of M machines and migration toward usage...

> 5) Support for selective information sharing. 
>
> Linux has a rather poor security model -- the Unix one.
> It needs ACLs no only on filesystem objects, but on other
> OS features as well; such as the ability to use network
> interfaces, packet types, display ACLs, console ACLs, etc.

It would have been nice to have just put 2 entries right
in the inode years ago. With the KISS method, we'd be using
ACLs right now. Even just a list of UIDs that would share
permission bits with the file's GID would be very useful.
I just want to share a file with one other person!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-15  4:55 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14 14:59 Jesse Pollard
2000-11-14 15:47 ` David Weinehall
2000-11-14 17:14 ` Michael Rothwell
2000-11-14 16:20   ` Mike Dresser
2000-11-14 17:27     ` Michael Rothwell
2000-11-14 17:32       ` Michael Rothwell
2000-11-14 16:25   ` Richard B. Johnson
2000-11-14 17:29     ` Michael Rothwell
2000-11-14 16:38       ` Mark Hahn
2000-11-14 19:23         ` spam
2000-11-14 16:41       ` Richard B. Johnson
2000-11-14 17:06         ` Michael Meissner
2000-11-14 17:59           ` Richard B. Johnson
2000-11-14 17:51         ` Buddha Buck
2000-11-14 18:10         ` Michael Rothwell
2000-11-14 18:00           ` Richard B. Johnson
2000-11-15  0:31             ` Gerhard Mack
2000-11-14 20:08         ` Alexander Viro
2000-11-14 16:57       ` David Relson
2000-11-14 18:17     ` Rik van Riel
2000-11-14 19:15     ` spam
2000-11-14 16:53   ` David Relson
2000-11-14 17:06   ` Andrea Arcangeli
2000-11-14 17:55   ` Andreas Dilger
2000-11-14 18:35   ` Christoph Hellwig
2000-11-14 23:06   ` Werner Almesberger
2000-11-15  4:25   ` Albert D. Cahalan [this message]
2000-11-17 22:10   ` Daniel Phillips
2000-11-18  0:58     ` Eric W. Biederman
2000-11-18 20:13       ` Daniel Phillips
2000-11-18 16:40     ` Pavel Machek
2000-11-19 20:37       ` Daniel Phillips
2000-11-20 13:34         ` Pavel Machek
2000-11-14 17:34 ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2000-11-17  5:28 Bernd Eckenfels
2000-11-15  4:19 Marty Fouts
2000-11-14 18:20 Marty Fouts
2000-11-14 18:18 Marty Fouts
2000-11-14 18:10 Marty Fouts
2000-11-14 19:43 ` Steve VanDevender
2000-11-15  1:13   ` Leo Mauro
2000-11-14 18:06 Marty Fouts
2000-11-14 18:03 Marty Fouts
2000-11-08 20:31 [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI) richardj_moore
2000-11-13 21:56 ` Advanced Linux Kernel/Enterprise Linux Kernel Josue Emmanuel Amaro
2000-11-14  7:49   ` Lars Marowsky-Bree
2000-11-14 18:33   ` lamont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200011150425.eAF4P3l135592@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=Josue.Amaro@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rothwell@holly-springs.nc.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®