I just saw that #Gentoo now supplies tons of precompiled binaries. on AMD64 and AARCH64 you get nearly the whole portage tree.
My first thought was "WTF?", but thinking about it, that's a very reasonable decision. Keeping a Gentoo system up to date takes quite a lot of energy. Webkit compilation alone can keep a modern CPU at full load for several hours...
So, while I love the option to compile things from source, I'll enable "-g" by default right now.
Running into an interesting situation where #Gentoo#Linux only has v1.69 of #RustLang marked in the stable branch, but pretty much any cool little app I want to build is insisting on v1.70 or higher in the unstable branch. Upgrading is a no-go as it triggers a conflicting dependency in the same package slot, so I guess I just sit around and wait?
I'm the only person maintaining #Gentoo support for DEC Alpha. I was testing GTK-4 on Alpha for https://bugs.gentoo.org/838709 and noticed that its test suite generated a lot of unaligned accesses (where, e.g. a load of 4-bytes from an address that isn't 4-byte aligned). These are slow on Alpha because the kernel has to trap and emulate the memory operation.
#Gentoo mailing list archives are broken for almost 3 months now. While marc.info is advocated as a stop-gap solution, it doesn't cover all our mailing lists (I don't think any of the third-party archives do). We really need someone to fix this.
I've missed my train (the first time in years!) while debugging the latest #GPG issue. This is honestly the single worst piece of software ever written.
They reinvent every single thing and they do it badly. When you try to make it work for everyone (i.e. make it use system resolver and honor proxies), it just falls apart.
I would consider making #gemato use #Sequoia, except that #RustLang discriminates against even more users than GPG bugs do.
@devinprater I'm trying to improve the #Gentoo#Linux installation instructions so that they take blind users into account. I'm hitting a brick wall.
Right now #Gentoo boots a live ISO to a terminal. No SSH by default. No screen reader by default. Hell, if there is a problem at boot time with GRUB, you won't know.
What helps? The only thing I can think of is maybe having a serial interface an external device can "screen read" aloud. Any suggestions would be extremely helpful.
I love #gentoo. I end up with problems that require more than a simple search to figure out.
I was trying to get #dwarfTherapist working. But in order to give it the ability to read data from #dwarfFortress it required process_vm_readv enabled in the #kernel which I aparently did not have enabled. Only by searching dwarf therapist's github issues did I figure out that it required being enabled in the kernel.
I know this sounds like a pain in the ass, but only by figuring these things out do I actually learn more about the #linux#kernel. Practical experience will always trump theory in my experience.
Technically this isn't gentoo specific, as you can use a precompiled kernel and you can compile your kernel on other distros, but gentoo makes it super easy.
It is YEARS since I used noweb, but maybe I could use it again, say for ports to other languages than C of program06 (my program that VIOLATES BELL INEQUALITIES despite having nothing resembling the non-existent ‘entanglement’).
For the first time since forever I have a dedicated drive on my desktop PC where I’m test driving #Linux distros. And also for the very first time I have #Arch a try (I never used it before). I… like it 🤷🏻♂️ I did not expect to like it, but it reminds me greatly of #Gentoo only in binary form. I still prefer Gentoo’s handbook, but overall it’s been smooth sailing 👌🏻 Can I now say, “BTW I use Arch?” 😬
FYI if you're using OpenRC in a regular split /usr profile on #Gentoo (which is basically the default) be wary that the binary package for OpenRC itself assumes a merged /usr for the 23.0 profile. This will cause a migration from the 17.1 profile to break the boot process unless you use the source package (which works as expected).
For anyone doing some regular #linux system updates (especially since 2.12 got flagged "stable" on #gentoo), grub 2.12 changes the EFI install directories and enables shim lock by default, in the news update it tells you about the install directories (simply blow away your /boot/EFI and let grub rebuild it, way better than their instructions), the shim lock is a bit more tricky, it seems to not be working correctly in 2.12 and even with SB disabled trips up.
My computer reboots itself when compiling #Firefox (I use #Gentoo) if I use more than 12 cores of my AMD 5900x. I’ve verified that the CPU and NVME drive aren’t overheating and I’ve tested RAM by removing one stick at a time. I’m also not running out of memory. BIOS is up to date.
Apparently #Gentoo's sys-apps/sandbox (which ensures ebuilds don't make a mess outside of their build "sandbox") had a huge performance regression which caused webkit-gtk build times to go from 9 minutes to 1 hour.
After collecting a ton of data, applying patches, reverting patches, etc, I filed https://bugs.gentoo.org/910273 and it seems we have a fix.
Jeszcze jeden post w temacie xz/sshd, a także wcześniejszej sprzedaży "Simple Mobile Tools".
Dawno temu, nauczono mnie ważnej zasady bezpieczeństwa w IT: kiedy grożą ci przemocą, ulegnij. Życie i zdrowie twoje i twojej rodziny jest ważniejsze niż jakikolwiek projekt wolnego oprogramowania, nad którym pracujesz. Wielu ludzi będzie cię obwiniać, ale ci naprawdę ważni zrozumieją.
Ale co, jeśli przed twoim nosem wisi marchewka, a nie kij? Co, jeśli ktoś oferuje ci pieniądze w zamian za "zdradę"? Powinieneś się opierać czy ulec?
Lecz czy nie powinieneś spodziewać się kija na drugim końcu? Czy nie uderzy cię wówczas, kiedy odrzucisz marchewkę? Wszak czy pieniądze nie są po prostu "cywilizowanym" sposobem umywania rąk od implikowanej groźby przemocy?
A co, jeżeli naprawdę potrzebujesz tych pieniędzy? Jeżeli z trudem wiążesz koniec z końcem, a odrzucenie marchewki jest kijem samo w sobie?
Cóż, nie sugeruję, że w #Gentoo spotka mnie taka sytuacja (sytuacja łapówki; brak dochodu znam aż za dobrze), ale naprawdę nie wiedziałbym jak postąpić. I jestem w stanie zrozumieć każdego, kto przyjąłby te pieniądze.
A morał z tego taki: dopóki ludzie będą wykorzystywać twórców wolnego oprogramowania jako darmową siłę roboczą, dopóty nie będą mieli prawa się dziwić, że istotne dla nich projekty są sprzedawane albo niszczone od środka.
#Gentoo question; what is the best way to share a small improvement on an ebuild in the Guru repo? Asking to become a contributor sounds like overkill, with getting PGP working and all.
Would it be best to just create my own repo and add it to the list so it can be discovered?
(The improvement is making iio-sensor-proxy work on openRC by implementing a fix I found on the forums. Not that impressive, though now my Chromebook runs perfectly :))