aT LEaZt iT wErKz
aT LEaZt iT wErKz
Iirc, the Arch wiki says you should synchronize all packages while adding new ones, and it’s technically unsupported. It might work in some cases, but personally I didn’t have to do much to not be able to launch something because symbols missing in libraries or no such file altogether. To avoid problems it’s better to sync packages fully at least once in a while.
HARDER!
Pasta with sweetened milk was very common back then and we called it “milk soup”. Some loved it, some hated it, I personally loved it, imo it was better than cornflakes. 90’s was tough times though and it’s not like we had access to too many things, it’s probably different today. And pasta with fruit sauce doesn’t seem strange to me even today.
Back then it was “too soon”
deleted by creator
But how do I sucessfuly M11
One that has never enough of livers
Exactly, while RTFM I haven’t have a single issue (apart from the driver quirks itself) and even automated the driver patching for NvFBC. Usual error is using nvidia-dkms and not setting up proper hook to rebuild the kernel module on kernel updates.
Great, it can drink the water
Is there Fortnite event when you shot dude in driving car using a sniper riffle?
She must have watch Trailer Park Boys with Ricky shooting at squirrels
Tak jak pan Jezus powiedział
What are you talking about? I wish I could do stuff like installing or managing my Arch installations more often, as it’s very relaxing and satisfying. The problem is, my installs never break and there’s nothing to do about them most of the time. I work in IT however and my job throws rocks at me all the time with some bullshit corporate software and horrible Sysadm/DevOps practices and boy’oboy is it frustrating….
Des
Pa
Cito
That was sick yoooooo
It hasn’t change since mid-2000s if you only talk about the installation process itself. Usually you would have at least some piece of hardware that wouldn’t work out of box and it used to be a lot of work until getting everything in place
AFAIK, the xz vulnerability was designed for Debian based on its workaround fixing systemd service status detection. Even if it shipped to something like Arch, the malicious code wouldn’t load.
Ahoj! No access to swamp