4 ms·
I did exactly the same in 2005. I even wrote my own init scripts, so I really understood a lot what's going on at startup time. Linux was quite simple at that t
by vbezhenar 10y ago
I did exactly the same in 2005. I even wrote my own init scripts, so I really understood a lot what's going on at startup time. Linux was quite simple at that time. I could write my own init, if I wanted. Unfortunately now this knowledge is obsolete. Systemd is a complex beast which uses a lot of arcane techniques, I'm hardly understanding it. chroot was a really simple concept, but nowadays people use containers, and they are much more complex than chroot. Logging is complicated. In the past I could try to load and then mount partition from livecd or another OS and read logs, now I don't know how to do it. Init scripts were simple bash scripts. They were verbose, may be buggy, but after all they were just bash scripts and every Linux user knows bash, so every Linux user could write or modify init script. Now systemd uses its own format, I'm spending hours every time I need to write new service or timer for RedHat. SELinux is just so complex. I know about UNIX permissions. They are so simple and elegant. I'm using them everywhere, when I need security. I could explain them in 2 minutes. SELinux has books. I have those books in bookmarks, may be I'll read them sometimes. But until then, I just use copy-pasta from internets to solve my tasks, like allow ssh to listen at non-standard port. I don't think that it's good, that I have to run some random strings on my computer from root without fully understanding what they are doing. SELinux has binary compiled configurations and some encrypted logs for tools to decipher them, what a mess! Sometimes I just disable it to get things done.
Don't get me wrong. I think that Linux looks more professional, more robust, especially for system administrators, who can devote their lives to learn about those systems. But for hobbyists, who doesn't have a lot of time, Linux became much less transparent.
May be if I didn't have that prior knowledge, it would be easier to learn those things from scratch. But I doubt it.
- plafl 10y agoSame here. After 20 years of using Linux I'm again a Linux newbie. I have given up, I just install Ubuntu. It's true that Linux works better than before but I feel it's just because there is so much more muscle behind not because of better design. I'm getting old I suppose.
- digi_owl 10y agoWhat is that legal term again, "Different in degree, not kind"? The more i find out about systemd and surrounding projects, the more i feel they should stop branding anything using it as Linux. It seems to be heading into Android territory, where it may have the kernel in common with classic (GNU?) Linux, but beyond that it is a whole new beast.
- cat199 10y agoIsn't the whole idea to kill Unix? Use funding to keep keep the 'cool things' purposefully incompatible, GPL'ed, and controlled via influence by well-staffed and funded corporate sponsors.. This keeps the IT people from getting too powerful w/r/t the managers...
- vetinari 10y agoNo. 20 years ago, there was the same scream about Redhat going to destroy Linux when switching from bsdinit to SysV init, or from libc5 to glibc2. Here we are today. Redhat is going to destroy Linux again. This time by switching from SysV init (or whatever).
- djsumdog 10y agoI've had to learn apparmour, which isn't too bad and a lot easier than SELinux (maybe not as powerful). Systemd is a religious argument at this point, but if you want simplicity check out Void. It uses runit and I love it. It's incredibly simple. Startup files are often less than 4 lines. I don't really like systemd either, but I will admit, as a package maintainer, it does make packaging a lot easier/universal. It'd be nice if there were drop in replacements for systemd that uses the target files for services and trashed everything else. UselessD was a cool project that attempted it, but it became to difficult to maintain. :( I currently work at a docker shop and I will say, containers are pretty nice. They're better isolated chroots with a lot of cool versioning support. There are pluses and minuses, but overall, I think docker is a nice evolution from chroots. Now all the eco-systems around docker: kubernets, DC/OS/marathon, nomad .. all totally different, proprietary and over-complicated.
- JdeBP 10y agoThe nosh toolset can of course import systemd socket, service, and target units into its native daemontools-encore-superset form; which can then be used on a BSD, on things like UbuntuBSD or Debian kFreeBSD, or (in theory) on Debian Hurd; as well as on Linux operating systems. * http://jdebp.eu./Softwares/nosh/worked-example.html http://jdebp.eu./Softwares/nosh/worked-example.html
- duncan_bayne 10y agoMaybe you should give FreeBSD a go. I've migrated to it from GNU/Linux for my everyday dev laptop, and haven't looked back. It's a lot like Linux used to be.