Re: [gentoo-user] Successfully upgraded to new profile 23.0
I use a buildhost for each of the 4 architectures I manage - binary emtytree installs are not to bad. However the initial build for low power arm systems is measured in multiple days (for just the initial toolchain, not hours :(. Only minor problems so far though which is good. At least it can build while online, unlike fresh installs which mean lots of downtime and more work for me in configuring. BillK On 9/4/24 05:14, Eli Schwartz wrote: On 4/8/24 10:03 AM, Dr Rainer Woitok wrote: Greetings, the upgrade on my old laptop with two 2.7GHz Dual-Core Skylake proces- sors took slightly more than 2 hours for the manual upgrading of "bin- utils", "gcc" and "glibc", and slightly more than 21.5 hours for the fi- nal upgrade of "@world", which had to process a total of 1061 packages. I'm wondering whether a fresh install from a stage 3 "tar" ball would have been faster? If you're okay doing a fresh install from a stage3 tar, which is faster at least to install the base system because it is all precompiled and you are not building the packages yourself, then I would assume you're also okay doing the update using the gentoo.org official binhost. They're both just the binaries that Gentoo's release automation builds for you. Extracting a bunch of gpkgs is much faster than compiling them, and not too much slower than extracting a single stage3 tarball. It also has the advantage that for amd64, more than just the stage3 package set can be sped up like this -- and you don't have to rebuild the installation, recreate @world, backup and restore user data, etc. Just enable the binhost and then do the same -e @world you were doing without the binhost. :) My first Gentoo installation on this laptop back in mid 2019 used pro- file 17.1 (which is still marked "experimental", by the way). Now, less than five years later this profile set is deprecated. Is five years a common intervall between enforced Gentoo profile upgrades? Well, 13.0 -> 17.0 -> 17.1 -> 23.0 so I suppose you could say they are fairly long intervals, yeah. As far as it being marked experimental: it was dropped from stable during the 23.0 announcement, but is being marked as stable again: https://github.com/gentoo/gentoo/pull/35871 Rationale: """ Making 17.1 exp immediately gives the impression that it's formally deprecated, which it isn't yet. """
Re: [gentoo-user] Successfully upgraded to new profile 23.0
On 4/8/24 10:03 AM, Dr Rainer Woitok wrote: > Greetings, > > the upgrade on my old laptop with two 2.7GHz Dual-Core Skylake proces- > sors took slightly more than 2 hours for the manual upgrading of "bin- > utils", "gcc" and "glibc", and slightly more than 21.5 hours for the fi- > nal upgrade of "@world", which had to process a total of 1061 packages. > I'm wondering whether a fresh install from a stage 3 "tar" ball would > have been faster? If you're okay doing a fresh install from a stage3 tar, which is faster at least to install the base system because it is all precompiled and you are not building the packages yourself, then I would assume you're also okay doing the update using the gentoo.org official binhost. They're both just the binaries that Gentoo's release automation builds for you. Extracting a bunch of gpkgs is much faster than compiling them, and not too much slower than extracting a single stage3 tarball. It also has the advantage that for amd64, more than just the stage3 package set can be sped up like this -- and you don't have to rebuild the installation, recreate @world, backup and restore user data, etc. Just enable the binhost and then do the same -e @world you were doing without the binhost. :) > My first Gentoo installation on this laptop back in mid 2019 used pro- > file 17.1 (which is still marked "experimental", by the way). Now, less > than five years later this profile set is deprecated. Is five years a > common intervall between enforced Gentoo profile upgrades? Well, 13.0 -> 17.0 -> 17.1 -> 23.0 so I suppose you could say they are fairly long intervals, yeah. As far as it being marked experimental: it was dropped from stable during the 23.0 announcement, but is being marked as stable again: https://github.com/gentoo/gentoo/pull/35871 Rationale: """ Making 17.1 exp immediately gives the impression that it's formally deprecated, which it isn't yet. """ -- Eli Schwartz OpenPGP_0x84818A6819AF4A9B.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
[gentoo-user] Steam and NFS, Fix for anyone also effected
So diskless clients and steam have had a bumpy road over the years, used to have to make a fakeflock.so to get around a locking bug. Then awhile after that, I believe when Proton reached version 8+ there was a horrible 30+ seconds of idle waiting time added to every game before it even attempted to load. The fix for that ended up being to mount a tmpfs over the runtime folder. Since late January an update caused a new bug to appear, I've scoured everywhere many times over, and the only real info I ever found was a race condition existing that even very low latency networking would result in SteamWebHelper crashing with a popup, and all the choices did nothing. So the only real choice was to either keep loading steam repeatedly and hope it worked (very low chances, maybe 1% for us here) or leave the popup alone and steam would continue to load, but in a crappy state, no friends, no sharing games, etc. I've tried many combinations and discovered a solution, you no longer need fakeflock or tmpfs. 1.emerge dev-util/vmtouch 2. start steam, let it get to the crash popup, and pick to close exit steam (only have to do this once so that all the files are unpacked into the correct locations) 3. open your preferred terminal and cd /home/UserName/.local/share/Steam/ubuntu12_64 4. vmtouch -L ./ (that locks the contents in RAM, for me around 1G of data 5. run steam, now it'll load much faster and not have any issues. 6. after steam loads you may control-C in the terminal vmtouch has the files locked in to let standard kernel memory management go back to doing its awesome job of caching what it actually needs to. Game on my fellow Gentoo Gaming Enthusiasts
Re: [gentoo-user] Successfully upgraded to new profile 23.0
On 4/8/24 07:03, Dr Rainer Woitok wrote: Greetings, the upgrade on my old laptop with two 2.7GHz Dual-Core Skylake proces- sors took slightly more than 2 hours for the manual upgrading of "bin- utils", "gcc" and "glibc", and slightly more than 21.5 hours for the fi- nal upgrade of "@world", which had to process a total of 1061 packages. I'm wondering whether a fresh install from a stage 3 "tar" ball would have been faster? My first Gentoo installation on this laptop back in mid 2019 used pro- file 17.1 (which is still marked "experimental", by the way). Now, less than five years later this profile set is deprecated. Is five years a common intervall between enforced Gentoo profile upgrades? Sincerely, Rainer I had to upgrade about 7 machines, and three wound up having weird troubles - so I did exactly that and started fresh on the rest. Working on the last one (my laptop) right now. Dan
[gentoo-user] Successfully upgraded to new profile 23.0
Greetings, the upgrade on my old laptop with two 2.7GHz Dual-Core Skylake proces- sors took slightly more than 2 hours for the manual upgrading of "bin- utils", "gcc" and "glibc", and slightly more than 21.5 hours for the fi- nal upgrade of "@world", which had to process a total of 1061 packages. I'm wondering whether a fresh install from a stage 3 "tar" ball would have been faster? My first Gentoo installation on this laptop back in mid 2019 used pro- file 17.1 (which is still marked "experimental", by the way). Now, less than five years later this profile set is deprecated. Is five years a common intervall between enforced Gentoo profile upgrades? Sincerely, Rainer
Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
Hey Michael Thank you for helping me. I have finally solved the issue by upgrading to kernel 6.8.4, see this: https://forums.gentoo.org/viewtopic-t-1168150.html Have a very nice week! Regards Nanderty
