archy

joined 1 year ago
[–] archy 3 points 1 week ago

Pro tip #2.
Any time they have your stuff - they will use it (sell it) sooner or later. Zero knowledge is the answer

[–] archy 8 points 1 week ago (2 children)

I heard that back in the day people survived without the AC

[–] archy 5 points 1 week ago (4 children)

At least they didn't pipe it into /dev/sdc1 that'd be a catastrophe

[–] archy 1 points 2 weeks ago

Hey, we worked at your airport for 4 months last year

[–] archy 7 points 2 weeks ago

Yes, it's called unbound

[–] archy 4 points 2 weeks ago

GrapheneOS as well with profiles

[–] archy 3 points 3 weeks ago
[–] archy 4 points 4 weeks ago (1 children)

Not sure about "designed", maybe evolved to be that way but not designed

[–] archy 16 points 2 months ago (7 children)

If the streaming apps will be deteriorated the only option left will be yt-dlp and mpv left

[–] archy 8 points 2 months ago

Why would you name your post like that???

[–] archy 2 points 2 months ago (1 children)

Good one, except available only where developed well

[–] archy 2 points 3 months ago (1 children)
14
submitted 8 months ago* (last edited 8 months ago) by archy to c/[email protected]
 

Does anyone have any issues with 6.5.7? I updated yesterday and could not boot. (1 of 2) A start job is running for /dev/mapper/root (30s / no limit) (2 of 2) A start job is running for /dev/disk/by-uuid/MY-UUID (30s / no limit)

Also during update my display resolution was set to 640x480 and I could not change it, so decided to reboot. I use a popular nowadays setup with LUKS encryption + unlock on TPM2, secure boot. I thought I messed with configs somewhere so started chasing that: changing configs and rebooting with no luck. The solution was to restore kernel 6.5.5 and everything booted back up without a hiccup. I am dreaded to see what happens during next kernel upgrade.

This is not asking for hep, more like a PSA if you have setup similar to mine, be aware


To those who stumble on this post in the future, I have found a solution that was in my case not knowing my system well enough. Since I decided to use Unified kernel images, I used mkinitcpio to compile those, but for some reason I used sbctl-bundle on top of that, which in itself is not any harm, just extra unnecessary work, and every single time I referenced an initramfs image from /boot which was an old one and was installed prior to me switching to UKI. When I read on Arch Wiki that I can delete those initramfs images from /boot - I deleted them, then had problems with sbctl bundle, and ONLY THEN it clicked - any new kernel install/upgrade doesn't generate initramfs in /boot but instead directly in UKI.

This is also good news because sbctl author announced deprecation of the bundle feature in the future.

view more: next ›