From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Gentoo SDcard updates tactics
Date: Tue, 7 Oct 2014 05:29:11 +0200 [thread overview]
Message-ID: <20141007032911.GA18442@solfire> (raw)
Hi,
There are two SDcards of the same brand and model.
The first one cariies a not so current Gentoo Linux.
The second one is empty.
Now the first one is image-copied to the second one with dd,
which copies the contents of the whole device (not the partitions).
Then the first one is put into my embedded system, boots up and
the normal eix-syn/emerge/compiel is done to update the system (whch
takes a longer time becaus this is an embedded system).
Will I get a technical identical working and valid copy of the first sdcard onto
the second sdcard if I rsync the relevant partition of the first onto
the second sdcard.
Or will I produce crap this way? Is this valid Gentoo-wise?
Thank you very much for any help in advance!
Best regards,
mcc
next reply other threads:[~2014-10-07 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 3:29 meino.cramer [this message]
2014-10-07 4:29 ` [gentoo-user] Gentoo SDcard updates tactics Alec Ten Harmsel
2014-10-07 7:49 ` Neil Bothwick
2014-10-07 7:39 ` Hinnerk van Bruinehsen
2014-10-07 16:01 ` meino.cramer
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=20141007032911.GA18442@solfire \
--to=meino.cramer@gmx.de \
--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