Comment Re:Phttt. Sun changes their mind every two months (Score 0) 338
Its amazing that people tear into smf like this. UNIX init is a simple system from times long past which is being extended and in some senses replaced by a (while more complex in some regards) more flexible system to represent the age we live in today.
One of the things the Windows NT world has correct is the way services run and are managed on a system. Service-like tasks should be supervised, not merely fired by scripts and ignored. Status information should be able to be gleaned by monitoring tasks through a standard API, etc etc. Services should be able to depend (specifically and declaratively, not merely through an arbitrary numeric ordering) on other services, services should be able to be restarted upon certain conditions. There really is nothing wrong with innovating and extending systems in such a fashion, as long as you don't break the old way of doing things or make the new way unusable. Sun have done a good job in preserving rc*.d compatibility in Solaris 10, as well as making the new system work well.
Also, attempting to forcefully disable a core part of an operating system and then complaining when it doesn't go as well as you'd hoped is daft too.
And as far as zones go, there's been plenty of testing and there are plenty of uses and reasons why zones are somewhat more secure and flexible than jails. What happens in a zone *does* stay in a zone. If you're root in a zone it doesn't mean you can affect the global package database or filesystem, just the ones within your zone. Look here for some contrasts between Jails, Chroot and Zones if you don't fully understand the concept (which it appears you don't): http://uadmin.blogspot.com/2005/06/zones-vs-jail.h tml
I'm not up for spreading FUD about Linux, but I wish people like you would stop spreading said FUD about Solaris too.
One of the things the Windows NT world has correct is the way services run and are managed on a system. Service-like tasks should be supervised, not merely fired by scripts and ignored. Status information should be able to be gleaned by monitoring tasks through a standard API, etc etc. Services should be able to depend (specifically and declaratively, not merely through an arbitrary numeric ordering) on other services, services should be able to be restarted upon certain conditions. There really is nothing wrong with innovating and extending systems in such a fashion, as long as you don't break the old way of doing things or make the new way unusable. Sun have done a good job in preserving rc*.d compatibility in Solaris 10, as well as making the new system work well.
Also, attempting to forcefully disable a core part of an operating system and then complaining when it doesn't go as well as you'd hoped is daft too.
And as far as zones go, there's been plenty of testing and there are plenty of uses and reasons why zones are somewhat more secure and flexible than jails. What happens in a zone *does* stay in a zone. If you're root in a zone it doesn't mean you can affect the global package database or filesystem, just the ones within your zone. Look here for some contrasts between Jails, Chroot and Zones if you don't fully understand the concept (which it appears you don't): http://uadmin.blogspot.com/2005/06/zones-vs-jail.
I'm not up for spreading FUD about Linux, but I wish people like you would stop spreading said FUD about Solaris too.
