From: Heiko Baums <lists@baums-on-web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world technically?
Date: Sun, 3 Dec 2017 05:15:25 +0100 [thread overview]
Message-ID: <20171203051525.4c91fafd@lexx> (raw)
In-Reply-To: <20171203034559.qlwbla6hvkjnpn32@solfire>
Am Sun, 3 Dec 2017 04:45:59 +0100
schrieb tuxic@posteo.de:
> Suppose one would do an emerge @world...and then BOOOM! a powerfailyre
> would stop the whole thing.
In such a case you should consider buying a UPS.
Can't you do this over night or a weekend? And how often do you have a
power failure?
> Further suppose the filesystem, the
> hardware and anything has survived luckily -- only emerge @world needs
> to be restarted.
> And one does NOT an emerge --resume but an emerge @world.
If I'm not mistaken in this case an `emerge --resume` should be
the right thing. It usually resumes the last interrupted emerge command.
That is if you run `emerge -e @world` press Ctrl-C `emerge --resume`
should resume this previous started `emerge -e @world` including the
package which was built when it was interrupted. Ctrl-C is principally
the same as a power failure.
If this fails for some reason then you'd have to rerun the whole
`emerge -e @world` I guess.
> In this particular case...how does emerge knows from the previous
> emerge @world what packages has been recompiled already and are "PIE"?
Like I said before. emerge always calculates the dependency tree, which
is a lot faster in case of `emerge -e @world` than in case of `emerge
-uDN @world`. And then it knows which packages have already been
installed and which are not.
That said I haven't run an `emerge -e @world` before. So I'm actually
not sure if this works the same way as with an `emerge -uDN @world`.
Heiko
next prev parent reply other threads:[~2017-12-03 4:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 2:15 [gentoo-user] New profile 17: How urgent is the rebuild of world technically? tuxic
2017-12-03 2:30 ` Michael Orlitzky
2017-12-03 2:32 ` Adam Carter
2017-12-03 2:44 ` Michael Orlitzky
2017-12-03 3:26 ` tuxic
2017-12-03 3:35 ` Heiko Baums
2017-12-03 3:45 ` tuxic
2017-12-03 4:15 ` Heiko Baums [this message]
2017-12-03 9:53 ` Peter Humphrey
2017-12-03 11:56 ` Heiko Baums
2017-12-03 12:55 ` Dale
2017-12-03 14:09 ` Spackman, Chris
2017-12-03 14:16 ` tuxic
2017-12-03 14:39 ` Heiko Baums
2017-12-03 15:25 ` Peter Humphrey
2017-12-03 15:57 ` Neil Bothwick
2017-12-03 14:36 ` Heiko Baums
2017-12-03 14:27 ` Heiko Baums
2017-12-04 1:08 ` Dale
2017-12-04 1:18 ` Heiko Baums
2017-12-04 1:48 ` Walter Dnes
2017-12-03 5:26 ` Adam Carter
2017-12-03 10:51 ` Neil Bothwick
2017-12-03 3:47 ` Heiko Baums
2017-12-06 23:59 ` Frank Steinmetzger
2017-12-07 8:08 ` Neil Bothwick
2017-12-04 17:48 ` Stefan G. Weichinger
2017-12-04 20:21 ` Michael Orlitzky
2017-12-05 9:16 ` Stefan G. Weichinger
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=20171203051525.4c91fafd@lexx \
--to=lists@baums-on-web.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