Les comparto un datazo que descubri hace poco.
Si utilizan OpenRC, pueden probar a modificar el rc.conf y cambiar la variable ' rc_parallel="NO" ' por ' rc_parallel="YES" '.
Esto permitira que los servicios inicien en paralelo, haciendo que el arranque sea un poco mas "rapido". Tan rapido que si se te crashea un servicio no vas a poder leer el mensaje de error :p
Installing binary packages using the #portage package manager feels like watching paint dry, compared to other package managers. I can count multiple seconds per package, even when said package is empty (e.g. a virtual).
I've always wondered why that is. It *feels* wrong, and nobody has managed to explain it to me.
A few days ago, while waiting multiple hours for 1500 packages to install into a clean root, it finally bothered me enough to dig into it.
@verymetalsite I used #debian between 2003 to 2015 on and off, and it's a wonderful distro, sometimes I just try other distros, and I saw mint was very easy to use so I stayed
I also used #slackware in 1999 was my first linux and 2000 redhat and mandrake
#gentoo around 2010 and #freebsd too, maybe I just like #opensource
@cJ @jk In my point of view, #Gentoo is relatively stable over a couple of months regarding features. Granted, over a period of several years I had to adopt for different paths (distfiles was moved to /var/something, e.g.), now we have more /etc/*.d config directories, …). But certain things are very stable (if you want: still openrc, alsa, …)
There's even lilo in portage!
It's rather programs like firefox that break behaviour / configs (and there isn't a simple way to configure it, anyway).
It may be personal but I see it with a much different perspective.
I'm *immensely grateful* that it's possible to have a machine with so many millions of SLOC running pretty much exactly how I want, respecting my freedom, with me contributing so little in return.
I'm also grateful that I can get to learn and know what's inside, and via the stream of updates and breakages, essentially be getting free continuous learning and also staying updated.
I'm purposely running #gentoo on my main machine, playing that Tamagotchi game very much.
When I want to "get things done without surprises", I use a "stable" "supply chain", trading off my own risk against reduced functionality, increased cost.
The good thing with "Linux" is that in no case you lose your freedom.
So I am wondering if there is a good way to access my Nextcloud share without needing to use the desktop app. In Gentoo qtwebengine is a dependency and that takes forever to compile. Tried the WevDAV connection exactly once in Thunar and wasn't sure why it didn't stay an option afterwards.
Thoughts?
Oops! Bloody hell....some #rust fanboy/fangirl messed with some core system package and messed up and dish out half-arsed version , which essentially failed ....heck
Damnit! I have nothing against the new surge of Rust ...but for fuck's sake ....stop spoiling
#linuxadmin #rust #dracut #gentoo #opensource #operatingsystem
Context:
#dailyreport #rust #linux #gentoo #opensource #compiler
#security
I compiled Rust from sources with alternative compiler
Mrustc (C++) without any binary blobs.
As you may know Rust compiler distributed as Rust sources
meant to be build by older "snapshot" of itself. Which
violate open source paradigm.
I was able to solve this in Gentoo GNU/Linux OS with
reproducible way. First I compile Rust 1.74 version and
then in chain I compile all versions to 1.84.
All steps took approximately 8 hours, but after it is fast
to compile new version, without blobs.
蠡
Jak działają paczki z wieloma systemami budowania do wyboru (albo oficjalnie wspieranymi, albo przez użytkowników):
1. Paczka ma podstawowy system budowania, którym nie jest #CMake.
2. Ktoś dodaje wsparcie budowania przez CMake.
3. Przypadkowe inne paczki zaczynają używać plików eksportów, które są instalowane tylko przez CMake.
4. Dystrybucje zaczynają korzystać z budowania przez CMake.
5. W kolejnym wydaniu, budowanie przez CMake zostaje popsute (znowu).
6. Nikt nie wie, czy możemy przełączyć z powrotem na działający system budowania, bo nikt nie ma pojęcia, jak wiele paczek wymaga plików eksportów od CMake.
How packages with multiple build systems to choose from (either officially supported, or user-maintained) work:
1. The package has a primary non-CMake build system.
2. A #CMake build system is added.
3. Random reverse dependencies start depending on CMake exports from given package.
4. Distributions start switching over to CMake.
5. CMake turns out to be broken (again) in the next release.
6. You don't know if you can switch back, because you have no clue if some of the reverse dependencies don't require CMake exports.
Okay, now I'm so lazy that I'm writing a zsh script to automatically activate a `venv` if it's in the current directory and deactivate on any parent directories.
// check code in first reply, change `TRUST_DIR` and `venv` if you prefer another name.
K1 bekommt die Tage nen neuen PC für das tägliche Leben und zum Zocken. Einzige "Einschränkung": da wird nie im Leben Windoof drauf kommen. Ich habe gerade nach Wunsch-Distribution gefragz, und K1 sagte: "Ubuntu."
Ich: "Wieso? Mach doch ma Districhooser."
Tja. Jetzt überlegt K1, die beiden Top-Vorschläge zu testen: #Arch und #Gentoo. 
Buon compleanno, Gentoo! 
Ecco la tua torta, vai avanti e compilatela da solo 
One of the #Linux distributions we hear very little about in the industry for cloud/#VM usage is #GentooLinux. But that could change with the #Gentoo project now putting out official #QCOW2 disk images to make it easier deploying this source-based Linux distribution within #virtualmachines. With these QCOW2 images, the XFS file-system is their preferred choice used for its copy-on-write, reflinks, and other features.
https://www.phoronix.com/news/Gentoo-Linux-QCOW2-VMs
)
Lust auf 
