public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] contents of /dev after initial installation
Date: Sat, 24 Dec 2005 16:43:30 +0100	[thread overview]
Message-ID: <43AD6CA2.8060307@gentoo.org> (raw)
In-Reply-To: <1133490923.15611.31.camel@sputnik886.ruz-net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthias Langer skrev:
> I'm just a more or less simple user of gentoo who somtimes tries to look
> a bit behind the curtain, so if you think this posting doesn't belong to
> gentoo-dev let me know.
> 
> However, maybe this is interesting to you:
> 
> Recently i've got serious trouble with one of my hard drives, so that i
> was forced to move my gentoo root partition from one hd to another. I
> successfully did so by mainly rsync -av source dest directory after
> diretcory. However, there are /proc, /dev and /sys which are different.
> Especially on the /dev part i was unsure how to do this, so i looked at
> the gentoo-udev guide once again, and found out, that for a working
> udev, which i can confirm as i'm writing this mail, only the nodes
> console and null are requred to exist in the /dev diretory initially.
> That's the reason why i was i little bit surprised as
> 
> # mkdir test
> # mount --bind / test
> # cd test/dev
> # ls
> 
> revealed that there are in fact hundrets of premade device nodes in the /dev directory. 
> And this is not only true for the box where i discovered this, which was brought up from a
> 2004.x cd, but also true for the box where i just installed gentoo from 2005.1-r1.
> 
> Is there any reason for this ?
> 
> Matthias
> 
> 

I know this topic is quiet old.
On my systems I only have /dev/{null,console} , and let udev managed the
rest.
When I do the install, I remove all the files in /dev (except those
two), and run mount --bind /dev /mnt/gentoo/dev , then I do the install,
and it works fine.

Is there any reason for not doing this, and then recommend that the
users that don't use udev/devfs to run MAKEDEV ?

Bjarke
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDrWyhO+Ewtpi9rLERAmBcAKCmrYf4h0ToZXY5RjyfC+CG0Fu+wgCfazZm
QyPdHTlEF1vQR8XfMGyfNmw=
=byxb
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-12-24 15:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02  2:35 [gentoo-dev] contents of /dev after initial installation Matthias Langer
2005-12-02  2:47 ` Stephen Bennett
2005-12-02  3:45   ` Georgi Georgiev
2005-12-02  3:57     ` Stephen Bennett
2005-12-02  5:32       ` Georgi Georgiev
2005-12-02  4:43     ` Greg KH
2005-12-02 13:17       ` Mike Frysinger
2005-12-02 17:00         ` Greg KH
2005-12-02 18:08           ` Mike Frysinger
2005-12-02 20:18             ` Matthijs van der Vleuten
2005-12-02 20:40               ` Mike Frysinger
2005-12-02 13:16     ` Mike Frysinger
2005-12-02 14:15 ` Petteri Räty
2005-12-02 14:46   ` Mike Frysinger
2005-12-24 15:43 ` Bjarke Istrup Pedersen [this message]
2005-12-24 18:59   ` Mike Frysinger

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=43AD6CA2.8060307@gentoo.org \
    --to=gurligebis@gentoo.org \
    --cc=gentoo-dev@lists.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