Stable operating systems tend to have a high degree of configuration management. That means, changes to the operating system are highly managed. In the mainframe world, IBM's z/OS operating system uses a product called SMP/E to perform system changes. This tool is often used in conjunction with strict change control procedures, such as change ticket approvals, peer review meetings, and scheduled implementation.
The opposite is a system where anyone can just install anything they want whenever they want. These systems usually tend not to be very stable.
2006-06-19 06:16:13
·
answer #1
·
answered by TechnoRat60 5
·
1⤊
0⤋
Stable Operating System
2016-12-12 03:45:09
·
answer #2
·
answered by tepper 4
·
0⤊
0⤋
I would say simplicity and good code.
Simplicity, to me, means, don't try to do everything that some user may possibly want sometime in the future. Just design what is needed with the ability to add on when necessary.
Good code goes without saying. Garbage in = garbage out, wirte your code test your code and beta market your code so that someone besides you is auditing it. Fix the errors and gothrough the process again until it works as advertised. That way you have a chance of stability.
2006-06-19 06:16:43
·
answer #3
·
answered by macTard 3
·
0⤊
0⤋
I've always thought the most important things are good memory management and multitasking, but that answer might not be enough for school. I haven't taken an OS class yet.
2006-06-19 06:17:11
·
answer #4
·
answered by anonymous 7
·
0⤊
0⤋
it's only as stable as the original program & limited user interference.
2006-06-19 06:20:06
·
answer #5
·
answered by Jojo 3
·
0⤊
0⤋
Lack of bugs/errors/issues.
2006-06-19 06:14:44
·
answer #6
·
answered by ? 4
·
0⤊
0⤋
Its ability to schedule jobs.
2006-06-19 06:13:23
·
answer #7
·
answered by sinkablehail1978 5
·
0⤊
1⤋
Being UNIX/POSIX
2006-06-19 06:14:13
·
answer #8
·
answered by alakit013 5
·
0⤊
0⤋