- Super duper os x mac os x#
- Super duper os x install#
- Super duper os x upgrade#
- Super duper os x full#
- Super duper os x code#
Super duper os x install#
It comes with a “remove and install tool” as well as the software in its own installer package.Jethro did mention that the installer is a manual package only,but Apple is working on a fully automatic setup.Īpparently the one piece “remove/install” tool detects those funny rectangular pieces of plastic that Mr Drysdale gave him,removing one for safe keeping,and then the other end is used to open the cavity where the software installer package is inserted and the software is compressed to install it….only takes a couple of seconds and will leave a very COOOOL feeling,or so he claims.
Super duper os x full#
He was able to get the full demo at his local Apple Store. I spoke with Jethro today about Apple’s upcoming OS 10.3 upgrade,seems he has been able to get himself a Beta version.Properly called the “Cavity Search and Install Package”(TM),it puts the user in the middle of the experience.Jethro indicated it is going to be an annual err….experience.
While they all tend to follow a theme, a new name means a radically new model, as opposed to one which has just has its number incremented (a la 10.X.Y releases). But as they realized that most users didn’t understand the significance of the 10.X numbers, they started using the cat names publically.
Super duper os x code#
With the original OS X releases, the cat names were only internal code names. Torrey: You’re actually about as wrong as you could be about the cat names.
Super duper os x upgrade#
In short, I believe special pricing should only be used when the upgrade is from an unpolished system (like 10.0) to a polished system (like 10.1). I expect Panther to be like Jaguar, and since it will be a move from a polished system to a new polished system, I expect to pay full price. And since I was upgrading from one polished release to another, I don’t feel it was unjustified for me to pay the full price. I, for one, found the features more than ample enough. Basically, Apple moved from a “making it work” to a “making it better than before” phase. In addition to the benefits arising from its new core, Jaguar introduced new features above and beyond anything OS 9 had offered.
Super duper os x mac os x#
Jaguar (10.2) was, for me, what took Mac OS X beyond what OS 9 had been. So other than a bit of speed, nobody lost anything moving to 10.1. It fully implemented all of the features that OS 9 had. With the release of 10.1, Mac OS X was a fully useable desktop system. It was made clear from the start that 10.0 was an early adopters release, and Apple acted accordingly by making the 10.1 upgrade very cheap ($20 if I remember properly). I’ve been using Mac OS X on my G4/400 since the Public Beta, and I’ve never felt short changed by it. I too do not see the foundation of most of the price complaints. That, however, is probably a pipe dream, although not one as egregious as OS X on x86. I just hope, however, that they pull in a modern UFS implementation, preferably one supporting soft updates. Glad to see that Dominic Giampaolo has been hard at work. “Sources said Panther will add more database-like structures to the file system, although the underlying file system will remain HFS+, ensuring backward compatibility.” Nothing like any of these is mentioned in the article, however. The main reason for not converting is that the Finder works now, and the fact that it’s a Carbon application only affects 3rd party utilities designed to interface directly with Cocoa applications. I don’t think Apple has much of an excuse for the Finder remaining a Carbon application, except that they’re bound to their legacy codebase and aren’t willing to leverage the power of their own development environment to convert it to Cocoa.
Furthermore, these features would only be useful to end users with the addition of kqueue support to the Finder, so changes that occur outside of the Finder’s well-regimented environment appear immediately. Of course I would love to see support for kqueue() and kevent() added, but this probably isn’t going to happen any time soon. Furthermore, since it’s a system call the kernel must process this entire list each time, due to a lack of statefulness. It requires an externalized file descriptor table for a large set of connections which much be iterated before and after each select() invocation. Select() simply has one of the worst ABIs in history. I’m not sure how this would break 3rd party KEXTs except that it requires altering the system call table. Namely poll(), excluded from the past three OS X releases due to fear of breaking 3rd party KEXTs.
The system doesn’t have to be abandoned (although I’ve disabled it in favor of stability), but bugs in the prebinding tools must be fixed.Ģ) Introduction of more POSIX and BSD syscalls My biggest issue with OS X, the prebinding system introduced in Jaguar seems to be the #1 cause of system instability.
0 kommentar(er)
