>3 day old centos 7 install, gnome desktop with gnome applications
>do nothing but update installed packages
>boot today to start configuring it
>locks at boot[K[[0m[31m* [0m] A start job is running for udev Wait for Complete Device Initialization (1min 58s / 3min)
[K[[1;31m*[0m[31m* [0m] A start job is running for udev Wait for Complete Device Initialization (1min 58s / 3min)
[K[[31m*[1;31m*[0m[31m* [0m] A start job is running for udev Wait for Complete Device Initialization (1min 59s / 3min)
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for udev Wait for Complete Device Initialization (1min 59s / 3min)
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for udev Wait for Complete Device Initialization (2min / 3min)
[K[[1;31mFAILED[0m] Failed to start udev Wait for Complete Device Initialization.
Lennart Poettering - "If it's gone I guess we can close the bug. Feel free to reopen it if it reappears."
A stock install of CentOS 7 which is supposed to be the most widely supported and most stable Linux that there is magically stopped booting because of udev/systemd.
That's my ACTUAL EXPERIENCE with systemd and poetteringcode fucking my shit up.
Complexity is the bane of developers and the boon of the users
But of course, not the incompetent, unpaid volunteer developers that have nothing to lose except brownie points. Why the fuck should they handle complexity properly?
If you want GOOD open source software and it's clear it's a minor component and not something so important it has corporations working on it (like the kernel), you have to stick to shit that's simple, because the hobbyist devs are always going to be too lazy and stupid to deal with anything larger and more complex than system V's vi without royally fucking up
Well the system won't even boot now.
At least I know now to ever touch a distro with systemd again. What I'm worried about is all the non-systemd components that poettering has fucked with, namely udev.
>mfw writing service unit files is so easy I almost find myself liking systemd
Yup, that's what I'm doing. Hopefully FreeBSD doesn't have any systemd-tier liability code.
It's almost unbelievable that a fresh install of CentOS 7 would just fail like that (due to Poetteringcode). I did verify the media during install and it was detected as good.
>systemd started using "predictable" network interface names
>they're way less predictable than before in 99% of cases
>all of their "use cases" in which their system does it better could have been fixed with udev rules
>the fact that nobody actually did that outside of corner cases tells you nobody fucking cares
slackware just got a version number bump to 14.2 in the slackware-current log. Hopefully a new release is around the corner. No systemd there.
If this systemd shit spreads so far I can't run mozilla or kde apps or libreoffice or slackware without it, I'll be following right behind you to a bsd.
>Complains about systemd not being muh unix way
>Probably uses ZFS which is a massive bloated as fuck layering violation that needs a gig of ram minimum not to shit the bed
I didn't even get a chance to add the EPEL repo and install ZFS. The system shit the bed thanks to poettering's udev before I even got that far.
The difference between ZFS and systemd is that people aren't having giant fucking problems with ZFS. If ZFS was failing like systemd, you'd see everyone bitching about ZFS fucking up and wiping out their data.
(ZFS also uses a loooot more than 1gb of ram)
Consoles supporting ANSI color codes are a problem
Why should I waste my precious bandwidth on bytes and bytes of rice? That's worse than goddamn ncurses window refreshing. Not everyone lives 10 feet away from the datacenter, anon. Some of us can't even use vim because that terminal shit is so inefficient, and have to resort to emacs+tramp instead, because it's better than the fuck that is sshfs.
yes this is the real issue I have with poettering: he just says "not a bug"/"WON'T FIX" and closes bug reports left and right
for some reason political correctness and incompetency go hand-in-hand. see also subversion.
udev decided I shouldn't use CentOS 7 for my home file server. It did this by making my system stop booting (see log in OP). So I guess in this case it wasn't strictly systemd, but it was still Poetteringcode - he grabbed udev and corrupted it and absorbed it into systemd.
My original plan was CentOS 7 with zfs, rtorrent, rutorrent, screen and to run a home DNS server on it.
You know, some basic things you'd consider a stable distro like CentOS 7 to be able to handle.
I didn't even get to add any third party repos or packages before I got a torpedo-ed system.
Hardware in the server is fine according to the diag panel and an IBM system X diagnostics disc.
>zfs, rtorrent, rutorrent, screen and to run a home DNS
I keep forgetting linux can do all of that. Why not just use debian? I don't really do torrents but it works for me as a file server and DNS. Or does debian also have a SYSTEMD problem?
Do you exclusively use monochrome photos because "bytes and bytes of rice"?
Color provides a valuable visual cue for humans, and if using literally single digits of extra bytes ticks you off, maybe you should go back to pen and paper.