mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: wichert@cistron.nl (Wichert Akkerman)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][PATCH] New fs to control access to system resources
Date: Tue, 15 Jan 2002 10:54:18 -0700	[thread overview]
Message-ID: <200201151754.g0FHsIT13693@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <a21pfj$amj$1@picard.cistron.nl>
In-Reply-To: <87k7uj61tk.fsf@tigram.bogus.local> <200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca> <a21pfj$amj$1@picard.cistron.nl>

Wichert Akkerman writes:
> In article <200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca>,
> Richard Gooch  <rgooch@ras.ucalgary.ca> wrote:
> >Having to set the permissions like this on each boot seems a bit
> >painful. Why not have permissions persistence like devfs has?
> 
> Maybe you could abstract that persistency from devfs and move
> it into a general layer that other filesytems can also use.

I suggested that last week in another thread (about Yet Another
Virtual FS), and heard a deafening silence. I'm not sure if it's
easier to provide a general layer, or to just make things available
via devfs. Having a general layer implies multiple persistence daemons
(aka devfsd), one for each virtual FS with persistence.

I was hoping to start some discussion about this, but it seems people
care more about Aunt Tilly :-)

I'm sure some people will scream at the top of their lungs against the
idea of making other information available via devfs, but maybe some
of those screams will be muffled once I release v2.0 of the devfs core
(that's the one where the internal tree is ripped out and the dcache
is used instead: should be a big code reduction). At least with v1.9
of the devfs core all known races have been removed, so hopefully that
softens the resistance :-)

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2002-01-15 17:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 16:01 Olaf Dietsche
2002-01-15 16:53 ` Richard Gooch
2002-01-15 17:38   ` Wichert Akkerman
2002-01-15 17:48   ` Olaf Dietsche
2002-01-15 17:54   ` Richard Gooch [this message]
2002-01-16 19:05   ` Andreas Ferber
2002-01-15 22:13 ` Ben Clifford
2002-01-15 22:24   ` Measuring execution time Mark Cuss
2002-01-16 17:23     ` Chris Friesen
2002-01-16 17:53       ` Richard B. Johnson
2002-01-16 21:47       ` Jakob Østergaard
2002-01-16 17:18   ` [ANNOUNCE][PATCH] New fs to control access to system resources Olaf Dietsche
2002-01-16 18:26     ` Ben Clifford
2002-01-17  0:34       ` Olaf Dietsche
2002-01-15 22:51 ` CaT
2002-01-15 23:00   ` David Weinehall
2002-01-15 23:13     ` CaT
2002-01-16  4:19 ` dean gaudet
2002-01-16 17:18   ` Olaf Dietsche
2002-01-16 18:12     ` dean gaudet
2002-01-17  0:34       ` Olaf Dietsche
2002-01-16 18:51 ` Andreas Ferber
2002-01-16 13:38   ` gmack
2002-01-16 23:06   ` Greg KH
2002-01-17  9:26     ` Andreas Ferber
2002-01-18 19:38       ` Greg KH
2002-01-18 15:36 ` Anthony DeRobertis
2002-01-18 18:22   ` Olaf Dietsche

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=200201151754.g0FHsIT13693@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wichert@cistron.nl \
    /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®