public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] creating an image of the system
Date: Mon, 09 Sep 2013 14:39:53 -0500	[thread overview]
Message-ID: <522E2409.60305@gmail.com> (raw)
In-Reply-To: <522E1FCB.30801@hadt.biz>

[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]

Michael Hampicke wrote:
> Am 09.09.2013 21:05, schrieb Benjamin Block:
>> On 08:30 Mon 09 Sep     , Michael Hampicke wrote:
>>> Am 08.09.2013 20:51, schrieb Benjamin Block:
>>>> Hej folks,
>>>>
>>>> I wonder what is a good way to create an image of a gentoo-system, so
>>>> that one can apply it later to the same or other computers.
>>>>
>>>> In my case it is a rather simple setup: one partition, no encryption or
>>>> lvm. Its a debug-setup, so its only used for certain programming-tasks
>>>> and not for daily work, so no need for something fancy. The time I
setup
>>>> that system I also used only conservative compilation-flags and
>>>> optimisation, so that it can be used on other CPUs (well, they have to
>>>> be x86_64 and have to have mmx/sse[23] - but I think every setup that I
>>>> intend to use this on will have these properties).
>>>>
>>>> So I reckon that one could just use tar with
permission-preservation and
>>>> some excludes like dev/sys/proc/tmp. But is this a good idea or is
there
>>>> a better way to do this? I never cloned a gentoo-system, so thats why I
>>>> would like to be at least somewhat sure about it, so that I don't have
>>>> to reconfigure it later again, because I messed it up :D
>>>>
>>>
>>> Tar with permission preservation is fine. Just exlude everything in
>>> dev/sys/proc/tmp as you said. But make sure, that these directories are
>>> in your tar file, it does not matter if they are empty, but they have to
>>> exist in order to boot proplery.
>>>
>>> One special case. To boot you most likely will need /dev/console and
>>> /dev/null. Just inlcude those two device nodes in your tar file.
>>>
>>
>> Thanks for pointing that out, but why are these both special? Seems to
>> me like these are also (char)device-nodes and shouldn't they also be
>> generated by the kernel with DEVTMPFS and then udev at a very early
>> init-stage?
>
> If you have DEVTMPFS enabled you should be fine. But not everybody has
> that enabled, or even uses udev :-)
>

I would include them just in case.  Why take the chance that it fails
for whatever reason.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 3460 bytes --]

  reply	other threads:[~2013-09-09 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 18:51 [gentoo-user] creating an image of the system Benjamin Block
2013-09-08 19:19 ` Mick
2013-09-08 22:07   ` Dale
2013-09-09 18:50     ` Benjamin Block
2013-09-09 19:38       ` Dale
2013-09-09  6:30 ` Michael Hampicke
2013-09-09 19:05   ` Benjamin Block
2013-09-09 19:21     ` Michael Hampicke
2013-09-09 19:39       ` Dale [this message]
2013-09-11 11:01   ` Neil Bothwick
2013-09-11 11:55   ` Stefan G. Weichinger
2013-09-11 14:11     ` thegeezer

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=522E2409.60305@gmail.com \
    --to=rdalek1967@gmail.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