Summary: | freebsd-update: take a HardenedBSD-like approach to major upgrades | ||
---|---|---|---|
Product: | Base System | Reporter: | Slawomir Wojciech Wojtczak <vermaden> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | 0mp, arved, emaste, grahamperrin, r, steve.p, tomek |
Priority: | --- | Keywords: | feature, needs-qa, performance |
Version: | 11.1-RELEASE | ||
Hardware: | Any | ||
OS: | Any |
Description
Slawomir Wojciech Wojtczak
2018-05-21 13:00:40 UTC
Hi, I can confirm this behaviour. Trying to upgrade from 11.2-RELEASE to 12.0-RELEASE takes around 9 hours on a system with a SD card as disk and a poor network 3G link. If the network link have issues when the upgrade is in "Fetching xxx patchs", the whole process of upgrade crash and, at that point, it have been started up around 6 hours ago. Starting up it again begins at the beggining, it doesn't have any swich to start when it fails. The solution recomended by Vermaden looks reasonable. Thanks, Phase 2, which i believe is the world update, takes forever... well 2 hours on a 4 month old high end machine. 1GB network. I don't have time to debug at the moment. I used to be able to run make build-world faster. Did someone add a debug sleep to one of the processes somewhere and forgot to remove? This is painful. I did a little more research on an offline machine. The decompression is extremely slow on several files. This seems to be the largest impact on the installation. still slow in 13.0 Somehow related, I have reported an idea to add freebsd-update and pkg-static autiomation download: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257247 :-) Developers: please, can you foresee implementation of things such as this before PkgBase becomes the norm? ^Triage: * summary line edition, harmonious with the feature keyword * severity reduced to the norm for an enhancement request. |