Originally posted by flux242
View Post
Announcement
Collapse
No announcement yet.
systemd Breached One Million Lines Of Code In 2017
Collapse
X
-
Originally posted by rene View Postdid it replace the Linux kernel already and become a freestanding OS yet? ;-)
- Likes 2
Comment
-
Originally posted by rtfazeberdee View Post
Seems like you don't understand systemd or what it does or why the tools exist so you blame the tool. You need to learn how to configure it for your purpose.
Comment
-
-
Originally posted by InsideJob View PostSystemD is an excellent office suite. It's more orderly than libreoffice and has fewer lines of code too. Why don't the haters and trolls recognize this fact? Linux rules on the desktop today because of people like Poettering.
It's modern software like systemd, udev, dbus in distributions like Ubuntu which actually made Linux usable on the desktop for a large number of users.
- Likes 2
Comment
-
-
Originally posted by Luke_Wolf View PostA million lines of code? Sounds about time for it to be all rewritten in Rust
Rust is FAR from being used for anything serious besides Firefox because of that. No enterprise distribution that isn't out of their mind would use plumberland written in Rust unless the language actually becomes stable.
- Likes 1
Comment
-
Originally posted by torsionbar28 View PostNot sure that I agree with you there. The boot messages scroll by so fast on a modern computer that it's almost useless. Sure, on my first PC back in the early 1990's, an i486 DX 33Mhz with 8 MB of RAM, booting up Slackware took minutes and you could read each message in detail - but this doesn't work anymore on modern hardware, particularly on machines booting from SSD.
Run 'dmesg' if you want to see the kernel messages since bootup, and 'cat /var/log/boot.log' to see the screen output of the init system starting up the services. Between those two, you have a complete picture of the machine's boot process, without having to read at Superman speed where if you blink you've missed it.
FWIW I've been on Red Hat for 23 years (since 1995) and have Red Hat certification on RHEL 5, 6, and 7.
- Likes 5
Comment
-
Originally posted by torsionbar28 View PostNot sure that I agree with you there. The boot messages scroll by so fast on a modern computer that it's almost useless. Sure, on my first PC back in the early 1990's, an i486 DX 33Mhz with 8 MB of RAM, booting up Slackware took minutes and you could read each message in detail - but this doesn't work anymore on modern hardware, particularly on machines booting from SSD.
Run 'dmesg' if you want to see the kernel messages since bootup, and 'cat /var/log/boot.log' to see the screen output of the init system starting up the services. Between those two, you have a complete picture of the machine's boot process, without having to read at Superman speed where if you blink you've missed it.
FWIW I've been on Red Hat for 23 years (since 1995) and have Red Hat certification on RHEL 5, 6, and 7.
Comment
Comment