linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mika Kukkonen <mika@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>, cgl_discussion@osdl.org
Subject: Re: [cgl_discussion] Re: OSDL CGL-WG draft specs available for review
Date: Wed, 23 Apr 2003 21:22:08 +0100	[thread overview]
Message-ID: <20030423212208.B7383@infradead.org> (raw)
In-Reply-To: <1051122743.7515.97.camel@miku-t21-redhat.koti>; from mika@osdl.org on Wed, Apr 23, 2003 at 11:32:25AM -0700

On Wed, Apr 23, 2003 at 11:32:25AM -0700, Mika Kukkonen wrote:
> On Wed, 2003-04-23 at 09:49, Christoph Hellwig wrote:
> > >    4.10 Force unmount (2) 2 Experimental Availability Core
> (...)
> > This is very hard to get right.  What the expermintel implementation
> > you're referring to?
> 
> This feature was mentioned in v1.1 spec, so some distributions already
> provide "experimental" versions of this feature. There are no Open
> Source projects I know of, though.

How do they provide  "experimental" versions of this feature?  I don't
see how this can be done without major fileystem surgery, so it
kindof must be an OSS implementation..

> > Without really big kernel changes it's hard to get full POSIX thread
> > semantics. e.g. we still don't have credential sharing for tasks.  And
> > it doesn't lool like this makes 2.6.  I'd rather remove this one..
> 
> Ah, we are not aiming to get our features into a certain kernel version,
> and actually we do not expect or even want (because of 2.6
> stabilization) that our v2 spec kernel features get merged into 2.6 at
> this point of time (some of them might, though).
> 
> For us it is enough that the distros will pick most of the features
> after v2 specs get released and through that adaption some of
> those features will get merged into 2.7 or whatever is coming after 2.6.
> So we are not in hurry ;-)

Well, this is not doable ontop of any existing kernel without major
suregery (introducing a credential cache and passing it down to
every place that's doing uid/gid based access control).

So none of the CGL distros can really support that.


  reply	other threads:[~2003-04-23 20:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:46 OSDL CGL-WG draft specs available for review Mika Kukkonen
2003-04-22 20:55 ` Christoph Hellwig
2003-04-22 21:22   ` [cgl_discussion] " Mika Kukkonen
2003-04-22 21:25     ` Christoph Hellwig
2003-04-23 16:18       ` Mika Kukkonen
2003-04-23 16:26         ` Christoph Hellwig
2003-04-23 16:49 ` Christoph Hellwig
2003-04-23 18:32   ` [cgl_discussion] " Mika Kukkonen
2003-04-23 20:22     ` Christoph Hellwig [this message]
2003-04-23 22:03     ` [cgl_discussion] Re: OSDL CGL-WG draft specs available forreview Peter Badovinatz
2003-04-24  9:39   ` OSDL CGL-WG draft specs available for review Carl-Daniel Hailfinger
2003-04-24  9:46     ` Christoph Hellwig

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=20030423212208.B7383@infradead.org \
    --to=hch@infradead.org \
    --cc=cgl_discussion@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika@osdl.org \
    /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 NNTP newsgroup(s).