Dark Voyage (alt Sokhibjon)

someone: i gonna take you myself @shakhzodme: nah brotha someone: i’ll get you a bitch @shakhzodme: brotha, i’m loyal to mine someone: i’ll get you 3 of them got me cracked 😭😂

@yetimdasturchi comments music

i’d love to devote my life to watch asahi lina but her contents are at least an hour long 😭😭😭

escaping the matrix with @orzklvb

army living peacefully with comfy software

~home, sweet home~

Important!!!| If you're a mac user who's Nix user and installed macOS 15 Sequioa beta, you might run into issues like _nixbld1 not existing in nixbld group. Well, after doing some extensive research, I found out that, macOS 15 creates some new users for its own new services like _aonsensed, _modelmanagerd, _reportsystemmemory, _swtransparencyd, _naturallanguaged.

_aonsensed:*:300:300:Always On Sense Daemon:/var/db/aonsensed:/usr/bin/false
_modelmanagerd:*:301:301:Model Manager:/var/db/modelmanagerd:/usr/bin/false
_reportsystemmemory:*:302:302:ReportSystemMemory:/var/empty:/usr/bin/false
_swtransparencyd:*:303:303:Software Transparency Services:/var/db/swtransparencyd:/usr/bin/false
_naturallanguaged:*:304:304:Natural Language Services:/var/db/com.apple.naturallanguaged:/usr/bin/false
_oahd:*:441:441:OAH Daemon:/var/empty:/usr/bin/false

Technically, Nix installer creates 32 builder users with UIDs starting with 300. However, this behaviour is modifiable via an environmental variable! Your solution would be first, uninstall existing installation of Nix, and then go bananas like this: `NIX_FIRST_BUILD_UID="305" sh <(curl -L https://nixos.org/nix/install)`

now, imagine this scenario... your company just have purchased a commercial software (this is where things get nasty) and asks to run it on specific servers that contains important infra for some reason. you're a typical devops guy and you're about to do your own duty. you just fire up your terminals and rsync'ed to all instances, set up just as in manual and run. oh no, kernel version has to be X version, glibc is old? you contact support of that commercial software to find out your company haven't purchased support tariff and suddenly management is aggressively forcing you to get it resolved as soon as possible. welcome to the hell buddy...

compiled on too new GLIBC? go fucking back... compiled on too old GLIBC? go fucking forward... this is exactly where nixos would have shined, seriously. you just indicate necessary glibc version. well, except specs and hardware layer, nothing limitates software with compatibility issues. real story: well, it's 2022 and we were about to launch a new service. well, the service was written in newest Rust and compiled in the freshest arch linux instance by that time and upon completion of compilation, the binary was ported to server. but little did i know, the server met it's EOL back in 2011 and is GYAATTTT old. spent additional week by hunting iso installer of image which was deleted from official website mirrors and setting up mirror for it downloaded from shady websites. yet another week for getting newer openssl work, cuz actix wasn't happy with crappy old openssl and downgrade some of specs and finally +3-4 days to compile program itself and get it working in the same os as server. in the end, i was late to deadline by a month and prior launch has been postponed to yet additional month to check for its conformances. i hate old system users & believer for a good damn reason as a developer. specifically most of the time, it's ecosystems that support AOT compilation that suffers from it and i'm a strong believer of nixos solving this issue once and forever.