JATtho

gdb> break before it crashes
gdb> record full
gdb> continue
(segfault)

gdb> set exec-direction reverse

Bugs that have existed for +3 years in a component and are nearly immediately visible to the end user. Oldest source line I touched was from before 2010.

It's a FOSS project, so wish me luck, as you can now get it in the mail eventually.

I had to run a makepkg today, which now includes my self-written pieces of code in master. So I'm eating my own dog food now, and it's good. Also, the itch from before has somehow relieved.

Reaper of the VMAs.

I fckd up a git rebase -i today with git commit -a --amend...

Thankfully git reflog allowed me to assemble the branch again ... from pieces.

There were no unit tests and previous dev had opened the pandora's box with half-written implementation. Gasp

C++: The project is now led by university research comitee optimizing essays/second and consists 1k lines of template hieroglyphs.

I almost posted comment about this but I had to keep it short. The Nvidia has an problem with their driver tainting the customers kernel/system which renders the customer in bad situation. (Of not being able to get support from kernel devs)

The proprietary taint is there for exactly for this reason:

• You load an proprietary module and all bets are off.
• For starters, you cannot tell there isn't a backdoor engineered into it.
• Even if the module behaves well, you now cannot debug the rest of the system any more, because all trust is gone.
• You cannot (at least easily) audit such system.

Nvidia solution to this is breaking the kernel license terms and acting like illegal smugglers in-order to access those sweet sweet GPL-only kernel APIs as lazily as possible. I would say that this is just arrogant and greedy way of doing software development. On top of this the kernel devs get all the blame for their vigilantly of trying to exercise their own license terms.

I think if nvidia would not be this arrogant and vile to the kernel devs, they would already have an proper kernel module that could co-exist between the GPL and proprietary code. If the proprietary code is implemented only in user-space/firmware they can keep their secrets: The user-space <-> kernel-space is an boundary where kernel GPL ends. Implementing such thing would not be easy, but I don't regard it being impossible: look at android.

In extreme: If the hostility continues, kernel devs just might be forced to go invent an corporate blacklist that goes against all principles of co-operation.

Others slightly more sane hw vendors, probably thought: fuck it. It is more profitable to push some FOSS code into the public than keeping the entire thing an trade secret. (I assume this results in the weirdly large firmware blobs that obfuscate and separate the actual hardware from the FOSS drivers)

EDIT: I read more about this issue. From proprietary code vendors viewpoint the current kernel is kind of "GPL or gtfo" situation. Linux kernel doesn't really have an internal stable ABI for modules/drivers. Implementing such thing would require (partly) dropping the monolithic design of the Linux kernel... Such interface would be then able to added to the GPL exemption of syscall users. This would open such big can of worms that it looks to be impossible.

Until you would have to replace a HDD: +23 hours of nerve racking RAID repair time for 10TB drive at 120MB/s Even with some advanced (like ZFS etc.) system you can't go around the fact the HDDs are slow.

And when the HDD fails, you can't read it. It's toast. Some cheap non-volatile memory devices are like this too, but good ones go into read-only mode and you can at least attempt data recovery from them if no better option is left.

I'm liking that it is possible get cheap+good 1TB NVMe devices for less than 100€. The consumer SATA market for large SSDs (capacity over 1TB) is unfortunately quite dry. I need replacement for HDDs and even if the speed is capped by SATA bus it would be an massive improvement.

This post is literally an pwns-list of users admitting what they use as password manager that may be stolen.

I encrypted an file, I put it on a device and mostly forgot it exists. Now if service locks me out I have go hunting.

I recently switched my default search from Google to DuckDuckGo: Google has begun refusing to find anything while exact same search on DuckDuckGo just works. Google is slower because I have to think+ignore first half of the page due to Ads/SEO crud.