From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][PATCH] New fs to control access to system resources
Date: Wed, 16 Jan 2002 20:05:31 +0100 [thread overview]
Message-ID: <20020116200531.D18039@devcon.net> (raw)
In-Reply-To: <87k7uj61tk.fsf@tigram.bogus.local> <200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201151653.g0FGrlG12428@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Tue, Jan 15, 2002 at 09:53:47AM -0700
On Tue, Jan 15, 2002 at 09:53:47AM -0700, Richard Gooch wrote:
>
> Having to set the permissions like this on each boot seems a bit
> painful. Why not have permissions persistence like devfs has?
At least for the moment I don't think this is necessary.
Keep in mind that accessfs with the current ressource coverage
contains only entries which are static after initialization (except
for user-initiated permission changes of course), not like devfs where
entries are appearing, disappearing and reappearing all the time when
modules are loaded/unloaded etc. So a small shell script which sets
permissions once after boot should suffice in all cases (one could
also write a script which saves permissions on shutdown, to
automatically preserve changes made by the admin).
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
next prev parent reply other threads:[~2002-01-16 19:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 16:01 [ANNOUNCE][PATCH] New fs to control access to system resources Olaf Dietsche
2002-01-15 16:53 ` Richard Gooch
2002-01-15 17:38 ` Wichert Akkerman
2002-01-15 17:54 ` Richard Gooch
2002-01-15 17:48 ` Olaf Dietsche
2002-01-16 19:05 ` Andreas Ferber [this message]
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=20020116200531.D18039@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche--list.linux-kernel@exmail.de \
--cc=rgooch@ras.ucalgary.ca \
/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