System Management Quotes

In the first few years, it was at least plausible to come in in the morning and read all the Usenet traffic that had come in, and 15 minutes later be off doing something useful.

I would therefore like to posit that computing's central challenge, how not to make a mess of it, has not yet been met.

Capitalism, wisely managed, can probably be made more efficient for attaining economic ends than any alternative system yet in sight, but that in itself it is in many ways extremely objectionable

Management does not know what a system is.

I work on OpenBSD fulltime, as the project leader. I set some directions, increase communication between the developers, and try to be involved in nearly every aspect of the base system.

We need to start looking at having a way of managing the whole ecosystem, because you can't pick away at it piece by piece, you have to truly start being coordinated and managing our resources as a system. We haven't gotten to that point yet.

Management's job is to optimize the whole system.

You don't make a system more effective by increasing the number of regulators.

The belief that complex systems require armies of designers and programmers is wrong. A system that is not understood in its entirety, or at least to a significant degree of detail by a single individual, should probably not be built.

So when they say I'm a low-level systems administrator, that I don't know what I'm talking about, I'd say it's somewhat misleading.

Ninety percent of cyber security companies begin in the detection stage. The issue is there are so many applications and alarming messages it is difficult for the user or the administrator to manage.

The fact that ACPI was designed by a group of monkeys high on LSD, and is some of the worst designs in the industry obviously makes running it at any point pretty damn ugly.

What is under our [the government’s] control is the signals we send and the way we organize ourselves.

Red Carpet Enterprise has been really well received since one guy can install it in about an hour, and it makes it trivial to deal with software management issues like deploying updates and creating standard package sets for your various machines.

You have to manage a system. The system doesn't manage itself.

Overall do I believe exchange with other cultures is good, people going back and forth is good, trade is good. Yes, all of these things are good. But I think you have to make sure the system's working. We need to know, virtually 100 percent of the time, when you come and when you leave. It's called entry and exit.

Organizationally what is required - and evolving - is systems management.

When you become a parent, or a teacher, you turn into a manager of this whole system. You become the person controlling the bubble of innocence around a child, regulating it.

There are considerable advantages to using many degrees of freedom to store information, stability and controllability being perhaps the most important.

Justin Trudeau had a message of asking Canadians to have trust in our immigration system. The problem is Canadians don't have trust in the Liberals to manage it.

Big Linux deployments have reached the point where it's become a real problem for administrators that they don't have nice tools to manage their servers and desktops.

A system must be managed. It will not manage itself. Left to themselves in the Western world, components become selfish, competitive. We cannot afford the destructive effect of competition.

A system must be managed. It will not manage itself.

It is management's job to direct the efforts of all components toward the aim of the system. The first step is clarification: everyone in the organization must understand the aim of the system, and how to direct his efforts toward it. Everyone must understand the damage and loss to the whole organization from a team that seeks to become a selfish, independent, profit center.