public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Xi Shen <davidshen84@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] When copying an os to new disk
Date: Sat, 20 Feb 2010 17:50:40 +0800	[thread overview]
Message-ID: <53e35fd51002200150o4664418obfcb4531d084b838@mail.gmail.com> (raw)
In-Reply-To: <201002192225.29528.volkerarmin@googlemail.com>

On Sat, Feb 20, 2010 at 5:25 AM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
> On Freitag 19 Februar 2010, Harry Putnam wrote:
>> I'm currently rsyncing an OS (new gentoo install) from one vmware disk
>> to a newly created one.
>>
>> I know not to copy /proc but not sure about /dev.  Looking at an
>> unbooted OS disk with an install on it... I see /dev/ is populated
>> (with no boot up), but I recall seeing things during boot like
>> `populating /dev' (I think).
>>
>> So should I copy it over to new disk or not?
>
> no. You just create /dev/null, /dev/console and /dev/zero.
>

in my experience, only the /dev/null and /dev/console are required.
what does the /dev/zero for?


> Everything else is optional and not needed.
>
> man mknod will tell you everything you need to know.
>
>
>



-- 
Best Regards,
David Shen

http://twitter.com/davidshen84/



  reply	other threads:[~2010-02-20  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 20:34 [gentoo-user] When copying an os to new disk Harry Putnam
2010-02-19 20:58 ` Daniel Troeder
2010-02-19 21:25 ` Volker Armin Hemmann
2010-02-20  9:50   ` Xi Shen [this message]
2010-02-22  7:49 ` daid kahl
2010-02-25 17:59   ` daid kahl
2010-02-26  1:06     ` Stroller
2010-02-26 11:59       ` daid kahl
2010-02-26 15:46         ` Kyle Bader
2010-02-26 16:00           ` Alex Schuster
2010-02-26 18:13             ` Kyle Bader
2010-02-26 23:25             ` Neil Bothwick

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=53e35fd51002200150o4664418obfcb4531d084b838@mail.gmail.com \
    --to=davidshen84@googlemail.com \
    --cc=gentoo-user@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