public inbox for elix@sourceware.org
 help / color / mirror / Atom feed
From: "Michael A. Olson" <mao@sleepycat.com>
To: "Bas Valkema" <bvalkema@knowhowww.nl>
Cc: elix@sourceware.cygnus.com
Subject: Re: EL/IX spec review, status
Date: Tue, 18 Jan 2000 14:38:00 -0000	[thread overview]
Message-ID: <200001182238.OAA09832@triplerock.olsons.net> (raw)
In-Reply-To: <003401bf6202$1d610f20$0303a0c0@BAS>

At 11:19 PM 1/18/00 +0100, you wrote:

> Sure, but what would be the difference between level 3 & 4 if the change is
> conducted? (sorry had no time to study the spec carefully.. ;-)

Level 4 right now has a bunch of system call interfaces not in
level 3.  They include:

	setuid/setgid
	process group support
	filesystem-based mutex support
	password and group database operations
	semaphores
	mapped memory
	shared memory
	some non-standard stream support
	popen() and friends
	named interfaces (if_nametoindex and friends)
	pty and raw terminal support
	common signal handling functions
	interfaces to spawn and manage processes

and just a couple of others.  The spec claims that the difference
between 3 and 4 is that 3 is multi-process and 4 is full Linux.
My argument is that shared memory is a useful abstraction for
multi-process, and belongs there.

The rest of the level 4 interfaces look right to me, based on
the designed differences between 3 and 4.

					mike
		

  reply	other threads:[~2000-01-18 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-18 11:15 Michael A. Olson
2000-01-18 12:24 ` Peter Buechler
2000-01-18 14:25   ` Bas Valkema
2000-01-18 14:38     ` Michael A. Olson [this message]
2000-01-19  2:57       ` Nick Garnett

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=200001182238.OAA09832@triplerock.olsons.net \
    --to=mao@sleepycat.com \
    --cc=bvalkema@knowhowww.nl \
    --cc=elix@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).