Sorry "youngsters". Arrogantly ignore business tools at your own peril. I'm personally acquainted with someone who ignored their voice mail for several days and missed job interviews. Not cool at best.
That pilots aren't distracted while communicating to ground controllers or flight deck crews? Are drivers similarly distracted by conversations with passengers?
I sense something amiss here
They're being mean to me and I don't like it!
Well, boo hoo!
and to piggy back, I just had systemd go wonky on my system... Seems it decided not to talk to dbus. dbus was actually running. I couldn't login, issue a reboot command, start or stop processes. As I'm working remotely, I was kind of hosed. I kill'd -9 dbus, and that seems to have caused the system to reboot. I'm not sure though... there was no logging to investigate before OR after.
As has been mentioned, the idea of systemd seems like something to be looked at. Having poorly tested coded rammed into a critical part of systems is a very poor idea. The often espoused idea that if it's not rammed in it will never be sufficiently tested. That to me speaks of monumental arrogance and impatience at a minimum.
"A firewall is a MUST".... However
1.) If you are a contractor (or an employee for that matter), and you're explicitly told not to do something, document your concerns, in writing and either do what they tell you or quit. This covers your butt when thing blow up. Note I said, when, not if. You don't get to dictate the business objectives in either case (contractor or employee).
2.) The networks/firewalls are only one part of the picture. I've noted other posts asking questions concerning the surrounding environment. These are good, even if they don't address point (1.) If a "best practice" for an element in the environment breaks the environment, then the "best practice" is invalid and MAY be ignored. It may also be that the app in question is brain dead, but that's a whole 'nother topic.
I've seen way too many "best practices" that do not account for the specific environment and even more "checklist" jockeys who can't figure out how to make things work without them. Learn to do more than to follow a flowchart/checklist.
There are "solutions" that become problems in and of themselves. Workaholism is in the same category... It solves a problem for a while and then becomes a problem itself.
zypper and the tumbleweed repository in opensuse offers this, but then I'm stuck with systemd madness
... and the idea that they are pure poison is why I want away from distro packagers who think that way.
As any decent toxicologist will tell you, the poison is in the dose.
I started in '93 with Yggdrasil and slack. Ygg was a non-starter. slack is OK, but difficult to deal with even if I do like like and admire Patrick
Now to dig in!
I've also been considered insane from time to time.
What I want:
1.) rpm/zypper/yum based package management. This allows rpm dependency resolution and installed package verification by the package manager.
2.) SysV init. It's clean and it "just" works.
I think those two are a good start. Being able to use an established automated build system is probably a good idea too.
Any other thoughts?
...Actually, I THINK we may be able to give 'em a run for the money
It's a best practice... how can it be wrong?
and my favorite dirty phrase "best practices"... Meaning "tell me what to do, I have no clue what the theory of operation is"
It's sad and in my opinion, from over 30 years experience, the product of testing and certification programs.... And manager/HR people who look for exactly those properties.