From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [Re: [gentoo-dev] Devfs permissions ?! [was:Permissions to dial out ?]]
Date: Fri Jul 13 09:03:02 2001 [thread overview]
Message-ID: <20010713090229.B18605@cvs.gentoo.org> (raw)
In-Reply-To: <20010713102907.4598.qmail@aw161.netaddress.usa.net>; from lakicsv@usa.net on Fri, Jul 13, 2001 at 11:29:07AM +0100
On Fri, Jul 13, 2001 at 11:29:07AM +0100, Viktor Lakics wrote:
> Thanks, Daniel,
>
> I added the appropriate permissions to devfsd.conf and now it works, the perms
> are stored (or regenerated accordingly).
>
> What is the storing system are you referring to? If I disable the
> "Automatically mount devfs at kernel boot" option, then I do not have the
> devfs at all, so I went back to the old file based system. Is this correct?
Actually, if you turn off that kernel option, the initscripts still mount
devfs if you are using a stock 1.0_rc5 setup.
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
prev parent reply other threads:[~2001-07-13 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 4:31 [Re: [gentoo-dev] Devfs permissions ?! [was:Permissions to dial out ?]] Viktor Lakics
2001-07-13 5:23 ` Collins Richey
2001-07-13 9:03 ` Daniel Robbins [this message]
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=20010713090229.B18605@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.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