public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Kreen <marko@l-t.ee>
To: Mirko Klemm <Mirko.Klemm@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: request advice: how stable is devfs in 2.4.0-test9?
Date: Tue, 31 Oct 2000 00:38:01 +0200	[thread overview]
Message-ID: <20001031003801.A2172@l-t.ee> (raw)
In-Reply-To: <00103022454801.00908@trabant>
In-Reply-To: <00103022454801.00908@trabant>; from Mirko.Klemm@t-online.de on Mon, Oct 30, 2000 at 10:45:48PM +0100

On Mon, Oct 30, 2000 at 10:45:48PM +0100, Mirko Klemm wrote:
> Could anyone please send me a comment on how actually usable the devfs 
> support in the 2.4.0 test series is at the moment?

Fine.  I was forced to use it from 2.3.99-something and
have not had any problems with it.  (I lifted whole system
from one disk to another and forgot to create /dev :)


> I am currently using 2.4.0-test* as an "ordinary user" and want to try some 
> of the 2.4 specific new features out, but this is my only system and I don't 
> want it to be messed up so much, so I'd like to hear some comments first.
> Which version of devfsd/utils is needed?

I have devfsd 1.3.10.

You better be sure you have following lines in devfsd.conf:

REGISTER        .*              MKOLDCOMPAT
UNREGISTER      .*              RMOLDCOMPAT

You can later reconfigure most stuff to use new layout
but especially X is a pain.

-- 
marko

-
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:[~2000-10-30 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 21:45 request advice: how stable is devfs in 2.4.0-test9? Mirko Klemm
2000-10-30 22:38 ` Marko Kreen [this message]
2000-10-31  2:51 ` Jeff Dike

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=20001031003801.A2172@l-t.ee \
    --to=marko@l-t.ee \
    --cc=Mirko.Klemm@t-online.de \
    --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