Well I meant two weeks is the longest period i can leave the system without updating and have no problems. And i have yet to break it with 300 pkgs updating at once.
I mean no harm.
Well I meant two weeks is the longest period i can leave the system without updating and have no problems. And i have yet to break it with 300 pkgs updating at once.
Arch maintenance: 0. Install it once. (The proper way)
pacman -Syu
I don’t get what is with this so hard? Yes, configs can be undecipherable but 90% time the merge involves just deleting the .pacnew versions.
A kernel was released that changed how the hash value got computed for casefolded filenames. (used for better windows compatibility) That kernel then went into production. This unfortunately split some file-systems that supported this into two incompatible versions, breaking the kernel rule 1.
There might now exist file-systems were created/modified with this bug present that the old/fixed kernels can’t understand.
I was reluctant to take this project, knowing well I would end up deleting nearly all existing code I would have to touch, all while having just mediocre skill writing its successor, if it ever becomes one.
I can no longer escape from this project, nor do have I will to.
deleted by creator
The point when the AI hallucinations become useful is the point where I raise my eye brows. This not one of those.
I do this exact same expression when I’m forced to gain knowledge of something potentially personally catastrophic…
Python is just a pile of dicts/hashtables under the hood. Even the basic int
type is actually a dict of method names:
x = 1
print(dir(x))
['__abs__', '__add__', '__and__', '__bool__', '__ceil__', '__class__', '__delattr__', '__dir__', ... ]
PS: I will never get away from the fact that user-space memory addresses are also basically keys into the page table, so it is hashtables all the way down - you cannot escape them.
This was truly a wtf moment of the month.
Last time I spent time watching him was when he freaking fixed the kexec syscall for IBM PowerPCs. for free
$ gdb -ex 'file /bin/gdb' run corrupted double-linked list Thread 1 "gdb" received signal SIGABRT, Aborted.
Yeah, try debug that.