BTW: for my classes, giving full authority to a department head, who doesn't even teach at my school or at my level, meant I got an edict of "No programming!"
You've got to change that. Find a way to convince him. Use your social engineering skills, whatever it takes.
If only I could apt-get update and apt-get dist-upgrade.
and Slackware totally misses the boat when it comes to providing a usable system out of the box.
Slackware works great for me lol, and I'd be interested in hearing what your problems are with Gentoo's packaging.
I don't agree that was the situation by 2014 and earlier this year. I think by then the chain of dependencies was starting to form that was making things increasingly nasty.
btw I don't know why you think this. Do you have links to forum threads that back this up, or is it just a 'gut instinct?'
Looks good to me, but I use a proportional font for coding because it's easier for me to read
That sounds ridiculous to me, but hey, whatever floats your boat.
Replacing systemd say 20 years from now will be very difficult. Essentially the modules will each need to be reimplemented in a way that's backwards compatible, offers what the future features are and allows partial implementation.
The next post I am working on is trying to figure out how stable the interfaces have been over time, but man, that's such a miserable thing to research! lol
The problem isn't init scripts it is what to do with chains of dependencies on high availability. If you worked in Linux-HA think about the application specific restart code that each application had to do and how fragile it all was.
Yes, we were constantly thinking of restarting things, but systemd wouldn't help with the majority of that. The applications themselves need to be written with restart in mind, and that's where the difficulty really comes in. (actually we spent most of our time trying to create a novel system for nodes to discover each other, but that isn't related)
They all want an much richer environment of management tools. In real life I've never met anyone who thinks systemd is too thick, they all argue it is too thin.
It sounds like they are looking at things from a feature perspective, not an architecture perspective. Those are cool features, but architecturally, continuous test doesn't really belong in the init system.
That said, if systemd were modular, someone could build an init system that offered those services, and swap it out for systemd on large systems. I still don't think that would be a good idea architecturally.....systemd is designed to deal with local problems and events. When dealing with a cluster, restarting local processes is about the easiest part of the problem. Building on the systemd framework wouldn't get you much (and because of its instability, you will lose things).
I have to say though, building a system on the cloud with all those features looks really, really fun to me. Especially if it had ridiculous problems like interfacing with old, archaic software.
malice schmalice - If a hobbyest can push crap to the many (professionals), the framework is flawed.
He's a professional, he works for RedHat.
<< WAIT >>