LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: how to move off of using devfs with the 2.6 kernel
Date: Sun, 9 May 2004 13:51:11 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405091348290.19145@localhost.localdomain> (raw)


  here's another issue i'd like to resolve.  currently, in moving up to
the 2.6 kernel, i'm trying to do this as gently as possible so i retained
the devfs filesystem, even though it's marked as obsolete in 2.6.  (during
the boot process, i am getting:

  Mounted devfs on /dev
  Freeing unused kernel memory: 76k init

so it seems to still be feasible to use it.  but what's the quickest
reconfiguration to move off of devfs onto (i'm assuming) sysfs and udev?
is it really just a simple kernel reconfiguration?  thanks.

rday

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2004-05-09 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.58.0405091348290.19145@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linuxppc-embedded@lists.linuxppc.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