public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frédéric L. W. Meunier <0@pervalidus.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: problem with devfsd compilation
Date: Fri, 2 Feb 2001 00:50:36 -0200	[thread overview]
Message-ID: <20010202005036.J160@pervalidus.dyndns.org> (raw)

Georg Nikodym wrote:

> Also, RH7's /etc/rc.sysinit can already start devfsd
> automatically with the following line:   

> [ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev

If devfs is mounted and devfsd exists, start devfsd.

> So, all you have to do is create an empty file /dev/.devfsd

Not true. I'm pretty sure /dev/.devfsd is only created when you
mount devfs at boot time or via mount -t devfs devfs /dev in
your system initialization script. Creating /dev/.devfsd with
touch defeats the purpose of /etc/rc.sysinit example.

crw-------  1 root     root     144,  0 Dec 31  1969 .devfsd

-- 
Frédéric L. W. Meunier - http://www.pervalidus.net/
0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-02-02  2:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-02  2:50 Frédéric L. W. Meunier [this message]
2001-02-02 14:46 ` problem with devfsd compilation Georg Nikodym
  -- strict thread matches above, loose matches on Subject: below --
2001-02-01 19:26 Andris Pavenis
2001-02-01 18:37 hiren_mehta
2001-02-01 18:44 ` Georg Nikodym
2001-02-01 18:45 ` Alan Cox
2001-02-02  6:25   ` Michael B. Trausch
2001-02-01 18:52 ` Georg Nikodym
2001-02-02  8:21 ` Michael B. Trausch

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=20010202005036.J160@pervalidus.dyndns.org \
    --to=0@pervalidus.net \
    --cc=linux-kernel@vger.kernel.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