I feel your pain - to an extent. But you aren't running OS X Server on your Ti, are you? If Apple wants to compete head-to-head in the enterprise space, then yeah, they ought to try to deliver the kind of behavior you're looking for. But you're not *just* running BSD on that TiBook and I think it is unrealistic for you to expect the same kind of experience you've had in the Unix world. If you want to be able to patch your system and not reboot, you surely could accomplish that with a PPC variant of Linux, right? :) If not, why be surprised (or bothered) that you have to reboot when you patch OS X? As far as running OS X Server on servers - I couldn't do it either - especially couldn't until they began offering a bundled hardware RAID solution. Now that the XRaid is out I could consider it hardware-wise, but I'll have to see some performance and reliability reviews from people who run *real* production systems before I take a chance on it. On Friday, February 14, 2003, at 02:27 PM, Chris Olson wrote: > That's one of the things that sucks about OS X, and why I have a hard > time believing I could run it ( OS X Server) on servers. There is no > need to restart a unix system unless you replace the kernel. You can > replace programs, libraries, or whatever, and just use the init > scripts to restart the upgraded app and load the new configs into > memory. I did not look at the date stamp on my kernel, so maybe the > kernel was replaced with this latest upgrade, but there again, a point > release does not replace the kernel on a unix upgrade. > > If you can imagine this type of thing on an XServe serving PHP pages, > and you run the upgrade and the system is broken - without warning, > and it requires a restart to complete the upgrade - simply > unacceptable for _any_ unix system, desktop or server.