public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: jordan.breeding@attbi.com, linux-kernel@vger.kernel.org,
	adam@yggdrasil.com
Subject: Re: Patch: 2.5.62.4 small devfs
Date: Mon, 03 Mar 2003 16:45:42 +0000	[thread overview]
Message-ID: <3E6386B6.80301@walrond.org> (raw)
In-Reply-To: 200303031638.h23GcH131618@gaea.projecticarus.com

Hmmm

I'm already using the existance of .devfsd to see if devfs was mounted 
by the kernel at boot. This suggests I need a new test for small devfs?

Andrew

jordan.breeding@attbi.com wrote:
> if [ -f /dev/.devfsd ]; then
>   you know you have old devfs
> fi
> 
> Jordan (I am fairly certain that it is /dev/.devfsd, you can always do ls -
> al /dev/.* to find the real name)
> 
>>Hi Adam
>>
>>Could you suggest a simple bit of sh script that will tell me if I have 
>>a devfs or small devfs kernel, (so my init scripts can decide whether or 
>>not to load devfsd?)
>>
>>Andrew Walrond
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at  http://www.tux.org/lkml/
> 
> 



       reply	other threads:[~2003-03-03 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200303031638.h23GcH131618@gaea.projecticarus.com>
2003-03-03 16:45 ` Andrew Walrond [this message]
2003-03-03 18:15 Patch: 2.5.62.4 small devfs Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2003-02-28 22:29 Adam J. Richter
2003-03-03 16:27 ` Andrew Walrond

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=3E6386B6.80301@walrond.org \
    --to=andrew@walrond.org \
    --cc=adam@yggdrasil.com \
    --cc=jordan.breeding@attbi.com \
    --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