[gentoo-user] Gentoo SDcard updates tactics

[gentoo-user] Gentoo SDcard updates tactics

[meino.cramer]

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

Re: [gentoo-user] Gentoo SDcard updates tactics

[Alec Ten Harmsel]

On 10/06/2014 11:29 PM, meino.cramer@gmx.de wrote:
> 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
>
>
>
Seems like it should work as long as you didn't update the kernel or any
other files under /boot, but why not just dd it again? Then you can be
sure it works.

Regards,

Alec

Re: [gentoo-user] Gentoo SDcard updates tactics

[Neil Bothwick]

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

On Tue, 07 Oct 2014 00:29:10 -0400, Alec Ten Harmsel wrote:

> Seems like it should work as long as you didn't update the kernel or any
> other files under /boot, but why not just dd it again? Then you can be
> sure it works.

Given the inherent fragility of SD cards, I would use dd each time, via
and intermediate file. Then, when one of the cards fails, you have a
backup without taking the other card out of service.


-- 
Neil Bothwick

Press button to test: release to detonate.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] Gentoo SDcard updates tactics

[Hinnerk van Bruinehsen]

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

On Tue, Oct 07, 2014 at 05:29:11AM +0200, meino.cramer@gmx.de wrote:
> 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?
> 

Moin (again),

this will work quite well, at least if you take care (I used this way for
moving my systems to new drives or even via network to different boxes (in the
latter case CFLAGS and kernel config will become important again, as you can
imagine)).
Ideally you should run rsync with the option to remove files not found on the
source drive (otherwise you'll likely clutter the target with stale files
(especially documentation  but also older library versions).
You will also need to change the configs (at least static network & hostname,
possibly more) so that both systems don't clash, at least if you plan to run
both on the same network.
The "rm" option of rsync is potentially dangerous (e.g. you can delete files
from home).
If you are careful this is a valid way of doing that. Another option that would
move quite a bit work from one machine to the other is just building binpkgs on
one host and use the other one as binhost. That way (if you use identical
/etc/portage dirs) you can quite savely use portage and nonetheless negate the
use of compiling (there will still be the load of dependency resplution,
extracting etc).

WKR
Hinnerk

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Gentoo SDcard updates tactics

[meino.cramer]

Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de> [14-10-07 17:23]:
> On Tue, Oct 07, 2014 at 05:29:11AM +0200, meino.cramer@gmx.de wrote:
> > 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?
> > 
> 
> Moin (again),
> 
> this will work quite well, at least if you take care (I used this way for
> moving my systems to new drives or even via network to different boxes (in the
> latter case CFLAGS and kernel config will become important again, as you can
> imagine)).
> Ideally you should run rsync with the option to remove files not found on the
> source drive (otherwise you'll likely clutter the target with stale files
> (especially documentation  but also older library versions).
> You will also need to change the configs (at least static network & hostname,
> possibly more) so that both systems don't clash, at least if you plan to run
> both on the same network.
> The "rm" option of rsync is potentially dangerous (e.g. you can delete files
> from home).
> If you are careful this is a valid way of doing that. Another option that would
> move quite a bit work from one machine to the other is just building binpkgs on
> one host and use the other one as binhost. That way (if you use identical
> /etc/portage dirs) you can quite savely use portage and nonetheless negate the
> use of compiling (there will still be the load of dependency resplution,
> extracting etc).
> 
> WKR
> Hinnerk

Moin Hinnerk, ;)

Good points...I have not thought deep enough about it - I think
(recursion?)...
Currently the "master card" is being updated via eix/emerge...and
then... :)

Best regards,
Meino