The Point Of No Return (DS23G) Mac OS

This document is broken into four main parts:

If you are waiting for the point of no return, where Mac OS X is a complete no-brainer upgrade from Mac OS 9, you'll have to wait a little longer. If you plan to run Mac OS X full-time, you should. The point of no return But if Microsoft stands to gain as much as Apple by giving away free operating system upgrades to consumers, why is Windows 8.1 available only to Windows 8 adoptees? The Point of No Return v0.16 DS23Games The Point of No Return' is the story of Jennifer Turner, a mid-30's woman with a loving husband and a soon to be college bound daughter. Her idyllic smalltown existence is threatened when three fugitives decide to turn her home into a temporary hideout. „The Point of No Return' is the story of Jennifer Turner, a mid-30's woman with a loving husband and a soon to be college bound daughter. Her idyllic smalltown existence is threatened when three fugitives decide to turn her home into a temporary hideout. Planet's Edge: The Point of no Return Description When the alien craft entered Earth's solar system, the human race was alive with excitement.

1. Partitioning a disk
   • Partitioning using Drive Setup (Mac OS 9)
   • Partitioning using Disk Utility (Mac OS X)
   • Partitioning using pdisk and newfs (Mac OS 9, Mac OS X, Darwin, NetBSD, Linux)

Note: the Linux pdisk command does not properly set the flags for NetBSD/macppc. If you have already partitioned your disk using the Linux pdisk, you'll need to use the NetBSD pdisk to delete and re-create the NetBSD root and swap partitions.

This document describes in depth how to partition a disk for use with NetBSD/macppc and Mac OS. Whether you can boot your machine from a particular disk into a particular operating system depends on your machine's version of Open Firmware. The overall goal is to create an Apple Partition Map that Open Firmware can understand (and thus boot from) and that the NetBSD kernel can understand and use to find its root partition.

There are four tools to partition a disk: Apple's Drive Setup (Mac OS 9), Apple's Disk Utility (Mac OS X), NetBSD's pdisk(8) (all OSes), and NetBSD's disklabel(8) (NetBSD/macppc only). The first two tools (Drive Setup and Disk Utility) are distributed by Apple with Mac OS and are located on bootable Mac OS installation CDs. You can use them to partition a disk, create the filesystems, and to install Mac OS bootloaders (called disk drivers in Mac OS terminology). Quaddro 2 mac os.

The pdisk program is a command-line program which can be compiled and run on most unix-like systems (particularly the ones that run on PowerPC-based Macintosh and clone machines). This program can only partition a disk -- it can't install bootloaders or create filesystems.

NetBSD's disklabel creates a NetBSD-style disklabel(5). Unlike the other three tools, it can only create a fake Apple Partition Map (thus you can't use it to create a disk that's bootable by Mac OS). That's OK, since some versions of Open Firmware require you to use disklabel to install the bootloader. Additionally, disklabel is the partition tool that is used in the NetBSD installer.

In the tables below, 'yes' means the disk is bootable, 'mount only' means that the OS can mount partitions on the disk, but cannot boot from it, and 'no' means the OS can't mount partitions or boot from the disk.

Open Firmware 1.0.5 or 2.0.x:

Open Firmware 2.4 or 3:

The Apple Partition Map stores partition information as a numbered list (usually in order of location on disk). Partition 'zero' is where the primary bootloader is stored for Open Firmware 1.0.5 or 2.0.x models. The partition map is partition number 1. A disk with Mac OS 9 will usually have partitions 2 thru 8 reserved for its drivers. The user defined partitions (HFS, HFS+, UFS, NetBSD, etc.) will start at partition 9 (Mac OS 9 disk), or 2 (no Mac OS 9).

Keep in mind that Open Firmware uses Apple Partition Map numbers when determining the command to boot your machine into NetBSD/macppc. You can use pdisk to print out the Apple Partition Map, regardless of how it was created.

To make matters a little more confusing, NetBSD/macppc uses its own partition naming scheme, the letters 'a' thru 'h'. The root partition (regardless of its Apple Partition Map location) is partition 'a'. The swap partition is partition 'b'. Partition 'c' represents the whole disk. The '/usr' partition (if it exists) is partition 'g'. The rest of the partitions fill in the remainder of the letters.

See the section on Partition nomenclature below for a more thorough discussion.

There are a whole slew of filesystem types you may encounter. Briefly, HFS is Apple's old filesystem which has been in use since the '80s. HFS+ (also known as 'extended') is an enhanced version of HFS which allows larger file (and filesystem) size, storage of unix-style owner and permissions. HFS+ is the recommended filesystem type for Mac OS > 8.1, including Mac OS X. UFS is Apple's NeXT-derived version of good old BSD FFS. MS-DOS (also known as FAT) is the filesystem standardized on the MS-DOS/Windows platform. BSD FFS is the standard filesystem used by most BSD unix-like OSes since the '80s (including NetBSD). ext2fs is the most common linux filesystem.

You may want to consider whether to include a partition that will be shared among your OSes. The most compatible format is MS-DOS FAT, but it lacks features (such as permissions and good repair tools). Unfortunately, NetBSD doesn't yet support the Macintosh HFS and HFS+ file systems natively. NetBSD-current has full support for Apple's UFS. Here's the quick breakdown:

1 - Either use the stablehfsutils or the experimental in-kernel support.

2 - Either use the experimental hfsplus utilsor the experimentallinux-hfspluskernel module.

3 - Use the highly experimental Ext2 Filesystem kernelextension.

If you want to create a partition you can share with Mac OS 9, you should create an HFS partition which you will later convert to MS-DOS format. See Creating a shared MS-DOS filesystem after you've partitioned your disk.

If you don't care about Classic Mac OS, then UFS is probably the best bet. Just make the UFS partition from within Mac OS X or Darwin, and make sure you are using a -current NetBSD kernel. UFS will be supported in the next major release of NetBSD (i.e. not the 1.6.x branch).

Partitioning will erase the contents of your drive, so back up everything from the disk you will be partitioning. Follow the instructions for the partitioning tool you wish to use.

• Partitioning using Drive Setup (Mac OS 9)
• Partitioning using Disk Utility (Mac OS X)
• Partitioning using pdisk and newfs (Mac OS 9, Mac OS X, Darwin, NetBSD, Linux)
• A disklabel(8) is created by the sysinst installer when you follow the directions in the NetBSD 9.1 install notes.

1. You will need to use Drive Setup version 1.8.1 or later. This is the version that comes with Mac OS 9.0. If you are unsure, you need to select Drive Setup and pick Get Info from the File menu.

   If you have an older version of Mac OS, you can download either the Mac OS 9.0.4 (12.2 MB), Mac OS 9.1 (71 MB), Mac OS 9.2.1 (82 MB), or Mac OS 9.2.2 (21.3 MB) updates, all of which include a version of Drive Setup that works for us. Note, these are big Mac OS updates, so you will have to download a multi-megabyte disk image just to get the 500 KB Drive Setup application. Apple has not provided a recent version of Drive Setup as a standalone update.

   Also, the Darwin installer has a version of Drive Setup that works. Darwin is also enormous (120.7 MB), since it contains a complete operating system.

   You'll need to open the disk image and copy Drive Setup to a hard drive, RAM disk, Zip disk, or floppy disk (it can't run from the disk image).

2. When you first run Drive Setup, it'll give you a screen like this, where you can select the drive that you want to re-partition.

   Select the drive to re-partition and click the Initialize. button. This will open another dialog box. Click the Custom Setup. button.

3. Select the number of partitions you'll be using. You will probably need at least 5 partitions, see the INSTALL notes for suggestions.

   Pick the Partitioning Scheme first since you lose all of your Volumes info each time you chose a different number of partitions.

4. For each of the Volumes set the Type: under the Volume Info and Size: as suggested in the INSTALL notes.

   You can use the TAB key to rotate through the Volumes.

5. When you're done, you should have something like the following (you get to name the Mac OS partitions later from the Finder):

6. Click the OK button. It will request confirmation of the changes.

   This is the point of no return! If you accept the changes, it will erase all contents of your drive

7. After it's done partitioning and creating the HFS(+) partitions, it will return to the original screen.

   Note: the A/UX partitions are not accessible to Mac OS.

8. You can quit Drive Setup, you're done with it. Now, from the Finder, you can rename your HFS(+) partitions. If you are using an Open Firmware 1.0.5 or 2.0.x model, you're done -- continue with the INSTALL notes.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you still need to do one more step.

   You will need to copy ofwboot.xcf (the bootloader) and netbsd.GENERIC_MD.gz or netbsd.ram.gz (the installer) to one of the HFS(+) partitions on your drive. Make sure that you have downloaded these files in binary mode.

The Mac OS X Disk Utility program cannot directly create NetBSD partitions, but where there's a will, there's a way. The advantage of Disk Utility is that it is available from the Mac OS X install CDs. Disk Utility can only create 'Mac OS Extended' (HFS+), 'Mac OS Standard' (HFS), 'UNIX File System' (UFS), and 'Free Space' partitions.

NetBSD/macppc -current kernels can use UFS partitions, even as the root partition. At present, if there are no normal NetBSD A/UX-style partitions available, NetBSD/macppc does not fall back to assuming that an UFS partition is the root. You may need to figure out what partition NetBSD thinks the UFS is at (e.g. 'e') and create a kernel with the UFS partition specified as the root device.

If this doesn't suit your needs, then you can use Disk Utility to create your Mac OS HFS+ partitions and leave free space for NetBSD. You'll need to use pdisk to create the NetBSD partitions.

1. Launch Disk Utility. From the install CDs, it's under the 'Install' menu. From Mac OS X, open /Applications/Utilities/Disk Utility.

2. You may need to authenticate. If it says 'Click the lock to make changes.' in the lower left corner of the window, click the lock and type in your password (you are using an administrative account, aren't you).

3. Select the disk to partition in the left panel. Click on the 'Partition' tab. Pick your 'Volume Scheme' (i.e. the number of partitions you want).

4. Set the names, formats, and sizes of your partitions. Hint: to make partitions smaller than it recommends, type a number into the size box and hit enter to get it to accept your partition size. 'Mac OS Extended' HFS+ partitions have a minimum size of 4 MB. For example, on my two-partition disk (a small HFS partition for ofwboot.xcf and a large UFS partition for NetBSD), Disk Utility looks like this:

5. Choose whether to install Mac OS 9 disk drivers. This is your only opportunity if you think you'll ever want to access any partitions on this disk from Mac OS 9 or earlier. Even HFS partitions are inaccessible from Mac OS 9 if you don't click this button.

6. Click OK and follow through.

7. You can quit Disk Utility, you're done with it. Now, from the Finder, you can rename your HFS(+) and UFS partitions. If you are using an Open Firmware 1.0.5 or 2.0.x model, you're done -- continue with the INSTALL notes.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you still need to do one more step.

   You will need to copy ofwboot.xcf (the bootloader) to one of the HFS(+) partitions on your drive. Copy netbsd.GENERIC_MD.gz (the installer) to your UFS partition (though it can also sit on an HFS(+) partition). Make sure that you have downloaded these files in binary mode.

   Remember, you'll need a -current kernel to use UFS as a root partition, and it may not be recognized by NetBSD as partition 'a'.

Partitioning using pdisk and newfs (Mac OS 9, Mac OS X, Darwin, NetBSD, Linux)

The command-line pdisk utility is used to view and modify the Apple Partition Map on a disk. NetBSD, Mac OS X, and Darwin can all mount disks partitioned with pdisk. Mac OS 9 and earlier need special drivers to be installed to mount a disk (see Drive Setup and Disk Utility). pdisk can create partition maps which will be bootable on Open Firmware 2.4 or 3 machines running NetBSD, Mac OS X, and Darwin.

You may still find pdisk useful to modify a partition map created by another utility or simply to list the partition map of a disk. If you are merely interested in listing the partition map of a disk, follow steps 1 through 4.

Before starting, some caveats about partitioning:

• If you create the partition map from pdisk (not just modify a partition map created using a Mac OS utility), you won't be able to access the partitions on this disk from Mac OS 9 and earlier.

• You can't create NetBSD A/UX-style partitions using the native Mac OS X, Darwin, or Linux pdisk program.

• The Mac OS 9 pdisk is a little out of date, and may act slightly different than the stuff below, but it still does the job.

• Mac OS X and Darwin won't let you write the pdisk partition map onto a drive that is currently in use. This means you can't repartition your boot drive. Boot from another disk (or create a bootable CD using a tool like BootCD).

The partition numbers listed by pdisk are the same that Open Firmware uses. If you're trying to boot an Open Firmware 2.4 or 3 machine with this disk, remember which Apple_HFS partition number has ofwboot.xcf and which Apple_UNIX_SVR2 or Apple_UFS partition is your NetBSD root partition.

1. Get pdisk.

   • NetBSD -current, /sbin/pdisk

   • NetBSD 1.6.x, ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.macppc-1-6

   • Mac OS X 10.2.5 (known to also work on Mac OS X 10.1.5), ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.macos-10-2

   • Mac OS 9, ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/macos-utils/pdisk.sea.hqx

     Uncompress the archive, and run pdisk ppc

   • Everything else (Mac OS X, Darwin, Linux), ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.src.20030424.tgz

2. Determine the device name for the disk you're going to repartition or view. If you are repartitioning, unmount any of those disk's partitions that might be mounted.

   • NetBSD:

   • Mac OS 9:

     Drag the disk to the trash. Open pdisk ppc and type L to list the disks, their fake names, and their partitions

   • Mac OS X and Darwin:

   • Linux:

3. Run pdisk /dev/disk-device, where disk-device is something like:

   • NetBSD /dev/sd2c (use the 'c' partition)
   • Mac OS X and Darwin /dev/disk2 (use no partition designation)
   • Linux /dev/hdc (use no partition designation)

4. Double-check you're on the right disk. If it's already got an Apple Partition Map, everything should be OK.

   If the disk does not have an APM, it'll give you some errors and you'll need to initialize the APM before creating new partitions.

5. Delete unused partitions and create your partitions. There's no need to delete the Apple_Free partitions, those automatically take up any unassigned space.

   Use the P command to list the partitions to make sure you delete the right one(s).

   Useful partition types you might want to create are:

   Apple_HFS	HFS and HFS+ partitions (also shared MS-DOS)
   Apple_UFS	UFS partitions
   Apple_UNIX_SVR2	A/UX-style partition for NetBSD and Linux

6. Write out the new partition map and quit.

7. Create new filesystems.

   • NetBSD can only create its own filesystem (FFS) for the root and user partitions. It can't directly create UFS, HFS, HFS+, or non-floppy sized MS-DOS filesystems. You can use hfstools to create an HFS filesystem.

   • Mac OS 9 will ask to create HFS and HFS+ filesystems when you reboot. After the reboot, it will recognize the new partition map, notice those partitions don't have filesystems and ask to create them. See Creating a shared MS-DOS filesystem on how to format a shared MS-DOS partition.

   • Mac OS X and Darwin can create UFS, HFS+, and HFS filesystems. It can't create NetBSD FFS, or non-floppy sized MS-DOS filesystems using command-line utilities. You won't need an HFS (non-extended) partition unless you intend to use it with Mac OS 8.0 or earlier.

     (for HFS+)

     (for UFS)

   • Linux can only create its own filesystem (ext2fs) for the root, swap and user partitions and MS-DOS filesystems. It can't directly create UFS, HFS, or HFS+. You can use hfstools to create an HFS filesystem.

8. Mount your new filesystems. Excel for mac how to freeze top row.

   • NetBSD (use the same commands for FFS and UFS):

     (virtual mount)

   • Mac OS X and Darwin:

   • Linux:

     (BSD FFS)

     (OSX UFS)

     (virtual hfsutils mount)

     (experimental in-kernel HFS)

     (virtual hfsplus utils mount)

     (experimental in-kernel HFS+)

     (linux ext2fs)

9. If you are using an Open Firmware 1.0.5 or 2.0.x model, you may want to copy netbsd.GENERIC_MD.gz (the installer) to your FFS or UFS partition. Make sure that you have downloaded this file in binary mode. You'll still need to load ofwboot.xcf from another source to boot your machine, though.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you will need to copy ofwboot.xcf (the bootloader) to one of the HFS(+) partitions on your drive. From NetBSD, use the hcopy command. Copy netbsd.GENERIC_MD.gz (the installer) to your FFS or UFS partition (though it can also sit on an HFS(+) partition). Make sure that you have downloaded these files in binary mode.

   Remember, you'll need a -current kernel to use UFS as a root partition, and it may not be recognized by NetBSD as partition 'a'.

You can create an MS-DOS format partition that works in all OSes such that classic Mac OS will automatically mount it, and the unix-like OSes (NetBSD, Linux, Darwin, and Mac OS X) can mount it using the mount_msdos command. The steps below outline the most straightforward technique.

1. Partition your hard drive with an HFS partition (type Apple_HFS) reserved for MS-DOS.

2. Next, boot Mac OS 8.1-9.x, grab a copy of Disk Charmer or DiskCharmer, and set it up to create an MS-DOS file system. Your settings should look something like this:

3. Drag the partition onto DiskCharmer's window and it will prompt you before erasing it and creating an MS-DOS file system in place of the HFS file system you created in the first step.

4. Now, when you boot Classic Mac OS, this partition will automatically mount using PC Exchange or File Exchange (depending on what it's called in your version of Mac OS).

   When you boot into Mac OS X, Linux, or NetBSD, run the following command:

   where /msdos.filesystem is the mount point you'd like, and /dev/disk0s11 is the device name for your partition. Alternatively, for NetBSD and Linux, you can add an entry to your /etc/fstab to always mount this filesystem.

5. To get Mac OS X and Darwin to automatically mount your MS-DOS file system, you need to create a System Startup bundle. The SystemStarter HOWTO is a good reference if you want to learn more about creating your own startup bundles. There's probably a way to do this using autodiskmount, but this technique works fine. The only downside is that the MS-DOS filesystem is unavailable to the Classic environment. Here's an example of what to do:

   1. Create /Library/StartupItems/MountMSDOS/StartupParameters.plist with the following contents:

   2. Create /Library/StartupItems/MountMSDOS/MountMSDOS with the following contents:

There are three partition identification schemes you'll run across when using NetBSD/macppc. Each identification scheme sorts the partitions differently, even though the partition's location on the disk doesn't change. Some schemes hide certain partitions.

1. Actual order on the disk (0 thru max partition number):

   This is the scheme used by Open Firmware and the /dev/diskXsY device files in Mac OS X and Darwin. The order of partitions is directly related to the order you selected in Drive Setup, pdisk, or the NetBSD partitioning tools. You can print out this list from any OS using pdisk.

   0	A special 'partition' reserved for a primary bootloader.
   1	The Apple Partition Map.
   2 thru ~8	Reserved for Mac OS 9 drivers if the drive is formatted with a Mac OS tool. Otherwise, user created partitions.
   ~9 thru ~15	User created partitions, placed in order of their physical location on disk.

2. Mac OS-visible partitions (by partition name in Finder):

   While you may have created a bunch of partitions in Drive Setup, only those partitions visible to Mac OS will show up in the Finder.

   The only partitions visible to Mac OS 9 and earlier are those formatted in HFS, HFS+, or MS-DOS formats. The only partitions visible to Mac OS X and later are those formatted in HFS, HFS+, UFS, and MS-DOS (not NetBSD's 4.2BSD FFS).

3. NetBSD-visible partitions (letters a thru h, as seen by disklabel):

   NetBSD reorders the partitions such that things work out better for itself. The fstype reported by disklabel(8) is set by the Apple Partition Map flags, and does not depend on the actual type of filesystem on that partition (be it NetBSD FFS, Apple HFS, or MS-DOS). In particular, MS-DOS formatted partitions show up as HFS partitions, if created using the method in Creating a shared MS-DOS filesystem.

   a	Your 'A/UX Root' partition, regardless of its order on the disk
   b	Your 'A/UX Swap' partition, regardless of its order on the disk
   c	This is the entire disk (first sector to last sector)
   d-f	First few non-A/UX partitions (usually the user HFS(+) partitions)
   g	Your 'A/UX User' partition (if present), regardless of its order on the disk
   h	Additional non-A/UX partitions (usually user HFS(+) partitions)

So, for example the following is what Drive Setup created on my PowerBook (FireWire):

After installation, one of the HFS partitions, 'Untitled' (which is partition 9 to Open Firmware, and partition d to NetBSD) has ofwboot.xcf, and one of the A/UX partitions (which is partition 12 to Open Firmware, and partition a to NetBSD) has my NetBSD kernel, so I use the following command to boot:

It may not feel that way, but we Mac users have now had quite a long run with OS X. We're coming up on 12 years since the first public release of the operating system (and even longer if you consider the betas and developer previews), and we've seen OS X go through plenty of changes during that time. Indeed, even Mac veterans may—with the passing of the years—have forgotten just how shaky some of those early OS versions could be.

Don't remember what OS X used to look like back when dinosaurs used to roam the planet and Apple's OS ran only on PowerPC processors? We've mined more than a decade of our own OS X reviews—studiously authored by John Siracusa—for screenshots and other OS X-related memories that trace the development of Apple's desktop OS through the 2000s. If you're interested in seeing how various UI elements have evolved over the years, strap yourself in for this safari showcasing OS X's big cats.

Mac OS X 10.0: Cheetah

https://gold-free.mystrikingly.com/blog/mark-us-prototype-mac-os. OS X was officially released to the public in 2001 after a rollercoaster series of developer previews, some of which barely resembled the final product. Because it was brand new to most users coming over from Mac OS 9, the new OS featured a number of 'shocking' interface elements, such as the new file browser:

And because so many users were still making generous use of their OS 8 and 9 applications, OS X featured a 'Classic' mode. Take a look at 10.0's Classic mode settings panel:

In his review of Mac OS X 10.0, Siracusa concluded with this fairly mixed verdict:

Mac OS X shows tremendous promise, which is a nice way of saying that the 10.0 release is not quite ready for prime time. This is most certainly an early adopter's OS release. Interface responsiveness and effective stability are the two biggest fundamental problems, but missing features and compatibility issues rank just as high if you actually intend to use OS X as a full Mac OS 9 replacement: the 10.0 release cannot view DVD movies; printer drivers are still scarce; CD burning is not yet supported, even by Apple's own iTunes CD authoring application; and a lot of hardware (like my G3/400's serial port adapter to which my printer is attached) seem destined to be orphaned forever.

Perhaps the most important feature of the 10.0 release is the Software Update preference panel. A 10.0.1 update that includes a new kernel and classic environment, SSH support, a slew of updated drivers, and many other small fixes has been circulating on the net, and may be released by the time you read this. A regular series of free, network-distributed OS updates will go a long way towards making OS X fulfill even the limited promise of a first release of a brand new operating system. Let's hope Apple doesn't foolishly try to charge for the more significant upgrade due in time for July's MacWorld Expo in New York.

Unlike previous articles, this one was written almost entirely in OS X. I forced myself to do this, to some degree, and I certainly spent most of my time in classic applications like BBEdit and Photoshop even when running OS X. But the experience was at least tolerable, which is more than can be said for my experience with earlier releases.

Should you upgrade to Mac OS X? If you don't already have a copy (or plans to buy one), the answer is no. Most users should wait for a future release, and possibly new hardware to run it on. Should Apple have released OS X in its current state? I think so. Nothing stimulates application development like a shipping OS. Let's hope that the official release of Mac OS X also stimulates Apple itself to make improvements.

Mac OS X 10.1: Puma

The next major version of Mac OS X, 10.1, was released the same year (2001) as 10.0. Apple was quick to make some tweaks in the first six months. So what did it look like?

Here's Puma's Dock:

And the System Prefs:

The Login window also sported this Aqua-fied look:

The Point Of No Return (ds23g) Mac Os Download

Siracusa's take was only a bit more positive this time around, and believing in the new OS still required nothing short of faith:

I wrote at the start of this article that I want to believe in Mac OS X. I want to believe that it will replace Mac OS 9 in a way that improves upon every aspect of the classic Mac OS user experience. Unfortunately, although this may still come to pass, Mac OS X 10.1 is not that version of Mac OS.

The Point Of No Return (ds23g) Mac Os Update

But 10.1 improves on 10.0.x in many important ways. Overall system performance shows the biggest improvement, but it is not as drastic as some reports may lead you to believe. Other areas have stagnated. The user interface has not made significant strides since 10.0.x. Many annoying bugs remain, and many features have yet to be implemented.

Should you purchase Mac OS X 10.1? If you already use and enjoy Mac OS X 10.0, you should run out and pick up a free 10.1 upgrade CD at your local retailer as soon as possible. If you tried 10.0.x and found it somewhat lacking, I recommend at least giving 10.1 a try to see if the improvements are enough to push you over the edge. If you are waiting for the point of no return, where Mac OS X is a complete no-brainer upgrade from Mac OS 9, you'll have to wait a little longer. If you plan to run Mac OS X full-time, you should consider upgrading your RAM to what were previously through of as obscene levels (512MB or more). It will be the best thing you can do for Mac OS X, short of buying a faster Mac.

If you're not a Mac user at all, but are intrigued by the possibilities of Unix based operating system with friendly user interface (Linux fans, no flames, please), 10.1 is as good a version as any to dip your toe into. Windows users should not expect a feature set remotely comparable to Windows XP, but Mac OS X is different enough that it should still broaden some horizons. And Linux users might want to see how another operating system has chosen to build a GUI on top of a Unix core.

To amend my earlier sentiment, it might be more accurate to say that I want to believe not just in Mac OS X, but in Apple itself. I want to believe that they can produce the next insanely great platform: a powerful, stable OS with an interface every Mac user can love, running on stylish, high performance hardware. Both the software and the hardware end of that dream currently need work. And so the waiting game begins again, as Mac users settle in with 10.1 and prepare for the inevitable 10.1.x updates. Will there be more 10.1 users than there were 10.0.x users? Probably. But it says something about this supposed 'mainstream release' of OS X when Apple itself is still selling all its hardware configured to boot into Mac OS 9 by default.

1 - Either use the stablehfsutils or the experimental in-kernel support.

2 - Either use the experimental hfsplus utilsor the experimentallinux-hfspluskernel module.

3 - Use the highly experimental Ext2 Filesystem kernelextension.

If you want to create a partition you can share with Mac OS 9, you should create an HFS partition which you will later convert to MS-DOS format. See Creating a shared MS-DOS filesystem after you've partitioned your disk.

If you don't care about Classic Mac OS, then UFS is probably the best bet. Just make the UFS partition from within Mac OS X or Darwin, and make sure you are using a -current NetBSD kernel. UFS will be supported in the next major release of NetBSD (i.e. not the 1.6.x branch).

Partitioning will erase the contents of your drive, so back up everything from the disk you will be partitioning. Follow the instructions for the partitioning tool you wish to use.

• Partitioning using Drive Setup (Mac OS 9)
• Partitioning using Disk Utility (Mac OS X)
• Partitioning using pdisk and newfs (Mac OS 9, Mac OS X, Darwin, NetBSD, Linux)
• A disklabel(8) is created by the sysinst installer when you follow the directions in the NetBSD 9.1 install notes.

1. You will need to use Drive Setup version 1.8.1 or later. This is the version that comes with Mac OS 9.0. If you are unsure, you need to select Drive Setup and pick Get Info from the File menu.

   If you have an older version of Mac OS, you can download either the Mac OS 9.0.4 (12.2 MB), Mac OS 9.1 (71 MB), Mac OS 9.2.1 (82 MB), or Mac OS 9.2.2 (21.3 MB) updates, all of which include a version of Drive Setup that works for us. Note, these are big Mac OS updates, so you will have to download a multi-megabyte disk image just to get the 500 KB Drive Setup application. Apple has not provided a recent version of Drive Setup as a standalone update.

   Also, the Darwin installer has a version of Drive Setup that works. Darwin is also enormous (120.7 MB), since it contains a complete operating system.

   You'll need to open the disk image and copy Drive Setup to a hard drive, RAM disk, Zip disk, or floppy disk (it can't run from the disk image).

2. When you first run Drive Setup, it'll give you a screen like this, where you can select the drive that you want to re-partition.

   Select the drive to re-partition and click the Initialize. button. This will open another dialog box. Click the Custom Setup. button.

3. Select the number of partitions you'll be using. You will probably need at least 5 partitions, see the INSTALL notes for suggestions.

   Pick the Partitioning Scheme first since you lose all of your Volumes info each time you chose a different number of partitions.

4. For each of the Volumes set the Type: under the Volume Info and Size: as suggested in the INSTALL notes.

   You can use the TAB key to rotate through the Volumes.

5. When you're done, you should have something like the following (you get to name the Mac OS partitions later from the Finder):

6. Click the OK button. It will request confirmation of the changes.

   This is the point of no return! If you accept the changes, it will erase all contents of your drive

7. After it's done partitioning and creating the HFS(+) partitions, it will return to the original screen.

   Note: the A/UX partitions are not accessible to Mac OS.

8. You can quit Drive Setup, you're done with it. Now, from the Finder, you can rename your HFS(+) partitions. If you are using an Open Firmware 1.0.5 or 2.0.x model, you're done -- continue with the INSTALL notes.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you still need to do one more step.

   You will need to copy ofwboot.xcf (the bootloader) and netbsd.GENERIC_MD.gz or netbsd.ram.gz (the installer) to one of the HFS(+) partitions on your drive. Make sure that you have downloaded these files in binary mode.

The Mac OS X Disk Utility program cannot directly create NetBSD partitions, but where there's a will, there's a way. The advantage of Disk Utility is that it is available from the Mac OS X install CDs. Disk Utility can only create 'Mac OS Extended' (HFS+), 'Mac OS Standard' (HFS), 'UNIX File System' (UFS), and 'Free Space' partitions.

NetBSD/macppc -current kernels can use UFS partitions, even as the root partition. At present, if there are no normal NetBSD A/UX-style partitions available, NetBSD/macppc does not fall back to assuming that an UFS partition is the root. You may need to figure out what partition NetBSD thinks the UFS is at (e.g. 'e') and create a kernel with the UFS partition specified as the root device.

If this doesn't suit your needs, then you can use Disk Utility to create your Mac OS HFS+ partitions and leave free space for NetBSD. You'll need to use pdisk to create the NetBSD partitions.

1. Launch Disk Utility. From the install CDs, it's under the 'Install' menu. From Mac OS X, open /Applications/Utilities/Disk Utility.

2. You may need to authenticate. If it says 'Click the lock to make changes.' in the lower left corner of the window, click the lock and type in your password (you are using an administrative account, aren't you).

3. Select the disk to partition in the left panel. Click on the 'Partition' tab. Pick your 'Volume Scheme' (i.e. the number of partitions you want).

4. Set the names, formats, and sizes of your partitions. Hint: to make partitions smaller than it recommends, type a number into the size box and hit enter to get it to accept your partition size. 'Mac OS Extended' HFS+ partitions have a minimum size of 4 MB. For example, on my two-partition disk (a small HFS partition for ofwboot.xcf and a large UFS partition for NetBSD), Disk Utility looks like this:

5. Choose whether to install Mac OS 9 disk drivers. This is your only opportunity if you think you'll ever want to access any partitions on this disk from Mac OS 9 or earlier. Even HFS partitions are inaccessible from Mac OS 9 if you don't click this button.

6. Click OK and follow through.

7. You can quit Disk Utility, you're done with it. Now, from the Finder, you can rename your HFS(+) and UFS partitions. If you are using an Open Firmware 1.0.5 or 2.0.x model, you're done -- continue with the INSTALL notes.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you still need to do one more step.

   You will need to copy ofwboot.xcf (the bootloader) to one of the HFS(+) partitions on your drive. Copy netbsd.GENERIC_MD.gz (the installer) to your UFS partition (though it can also sit on an HFS(+) partition). Make sure that you have downloaded these files in binary mode.

   Remember, you'll need a -current kernel to use UFS as a root partition, and it may not be recognized by NetBSD as partition 'a'.

Partitioning using pdisk and newfs (Mac OS 9, Mac OS X, Darwin, NetBSD, Linux)

The command-line pdisk utility is used to view and modify the Apple Partition Map on a disk. NetBSD, Mac OS X, and Darwin can all mount disks partitioned with pdisk. Mac OS 9 and earlier need special drivers to be installed to mount a disk (see Drive Setup and Disk Utility). pdisk can create partition maps which will be bootable on Open Firmware 2.4 or 3 machines running NetBSD, Mac OS X, and Darwin.

You may still find pdisk useful to modify a partition map created by another utility or simply to list the partition map of a disk. If you are merely interested in listing the partition map of a disk, follow steps 1 through 4.

Before starting, some caveats about partitioning:

• If you create the partition map from pdisk (not just modify a partition map created using a Mac OS utility), you won't be able to access the partitions on this disk from Mac OS 9 and earlier.

• You can't create NetBSD A/UX-style partitions using the native Mac OS X, Darwin, or Linux pdisk program.

• The Mac OS 9 pdisk is a little out of date, and may act slightly different than the stuff below, but it still does the job.

• Mac OS X and Darwin won't let you write the pdisk partition map onto a drive that is currently in use. This means you can't repartition your boot drive. Boot from another disk (or create a bootable CD using a tool like BootCD).

The partition numbers listed by pdisk are the same that Open Firmware uses. If you're trying to boot an Open Firmware 2.4 or 3 machine with this disk, remember which Apple_HFS partition number has ofwboot.xcf and which Apple_UNIX_SVR2 or Apple_UFS partition is your NetBSD root partition.

1. Get pdisk.

   • NetBSD -current, /sbin/pdisk

   • NetBSD 1.6.x, ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.macppc-1-6

   • Mac OS X 10.2.5 (known to also work on Mac OS X 10.1.5), ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.macos-10-2

   • Mac OS 9, ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/macos-utils/pdisk.sea.hqx

     Uncompress the archive, and run pdisk ppc

   • Everything else (Mac OS X, Darwin, Linux), ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.src.20030424.tgz

2. Determine the device name for the disk you're going to repartition or view. If you are repartitioning, unmount any of those disk's partitions that might be mounted.

   • NetBSD:

   • Mac OS 9:

     Drag the disk to the trash. Open pdisk ppc and type L to list the disks, their fake names, and their partitions

   • Mac OS X and Darwin:

   • Linux:

3. Run pdisk /dev/disk-device, where disk-device is something like:

   • NetBSD /dev/sd2c (use the 'c' partition)
   • Mac OS X and Darwin /dev/disk2 (use no partition designation)
   • Linux /dev/hdc (use no partition designation)

4. Double-check you're on the right disk. If it's already got an Apple Partition Map, everything should be OK.

   If the disk does not have an APM, it'll give you some errors and you'll need to initialize the APM before creating new partitions.

5. Delete unused partitions and create your partitions. There's no need to delete the Apple_Free partitions, those automatically take up any unassigned space.

   Use the P command to list the partitions to make sure you delete the right one(s).

   Useful partition types you might want to create are:

   Apple_HFS	HFS and HFS+ partitions (also shared MS-DOS)
   Apple_UFS	UFS partitions
   Apple_UNIX_SVR2	A/UX-style partition for NetBSD and Linux

6. Write out the new partition map and quit.

7. Create new filesystems.

   • NetBSD can only create its own filesystem (FFS) for the root and user partitions. It can't directly create UFS, HFS, HFS+, or non-floppy sized MS-DOS filesystems. You can use hfstools to create an HFS filesystem.

   • Mac OS 9 will ask to create HFS and HFS+ filesystems when you reboot. After the reboot, it will recognize the new partition map, notice those partitions don't have filesystems and ask to create them. See Creating a shared MS-DOS filesystem on how to format a shared MS-DOS partition.

   • Mac OS X and Darwin can create UFS, HFS+, and HFS filesystems. It can't create NetBSD FFS, or non-floppy sized MS-DOS filesystems using command-line utilities. You won't need an HFS (non-extended) partition unless you intend to use it with Mac OS 8.0 or earlier.

     (for HFS+)

     (for UFS)

   • Linux can only create its own filesystem (ext2fs) for the root, swap and user partitions and MS-DOS filesystems. It can't directly create UFS, HFS, or HFS+. You can use hfstools to create an HFS filesystem.

8. Mount your new filesystems. Excel for mac how to freeze top row.

   • NetBSD (use the same commands for FFS and UFS):

     (virtual mount)

   • Mac OS X and Darwin:

   • Linux:

     (BSD FFS)

     (OSX UFS)

     (virtual hfsutils mount)

     (experimental in-kernel HFS)

     (virtual hfsplus utils mount)

     (experimental in-kernel HFS+)

     (linux ext2fs)

9. If you are using an Open Firmware 1.0.5 or 2.0.x model, you may want to copy netbsd.GENERIC_MD.gz (the installer) to your FFS or UFS partition. Make sure that you have downloaded this file in binary mode. You'll still need to load ofwboot.xcf from another source to boot your machine, though.

   If your model has Open Firmware 2.4 or 3, and you're going to make this disk bootable for NetBSD, you will need to copy ofwboot.xcf (the bootloader) to one of the HFS(+) partitions on your drive. From NetBSD, use the hcopy command. Copy netbsd.GENERIC_MD.gz (the installer) to your FFS or UFS partition (though it can also sit on an HFS(+) partition). Make sure that you have downloaded these files in binary mode.

   Remember, you'll need a -current kernel to use UFS as a root partition, and it may not be recognized by NetBSD as partition 'a'.

You can create an MS-DOS format partition that works in all OSes such that classic Mac OS will automatically mount it, and the unix-like OSes (NetBSD, Linux, Darwin, and Mac OS X) can mount it using the mount_msdos command. The steps below outline the most straightforward technique.

1. Partition your hard drive with an HFS partition (type Apple_HFS) reserved for MS-DOS.

2. Next, boot Mac OS 8.1-9.x, grab a copy of Disk Charmer or DiskCharmer, and set it up to create an MS-DOS file system. Your settings should look something like this:

3. Drag the partition onto DiskCharmer's window and it will prompt you before erasing it and creating an MS-DOS file system in place of the HFS file system you created in the first step.

4. Now, when you boot Classic Mac OS, this partition will automatically mount using PC Exchange or File Exchange (depending on what it's called in your version of Mac OS).

   When you boot into Mac OS X, Linux, or NetBSD, run the following command:

   where /msdos.filesystem is the mount point you'd like, and /dev/disk0s11 is the device name for your partition. Alternatively, for NetBSD and Linux, you can add an entry to your /etc/fstab to always mount this filesystem.

5. To get Mac OS X and Darwin to automatically mount your MS-DOS file system, you need to create a System Startup bundle. The SystemStarter HOWTO is a good reference if you want to learn more about creating your own startup bundles. There's probably a way to do this using autodiskmount, but this technique works fine. The only downside is that the MS-DOS filesystem is unavailable to the Classic environment. Here's an example of what to do:

   1. Create /Library/StartupItems/MountMSDOS/StartupParameters.plist with the following contents:

   2. Create /Library/StartupItems/MountMSDOS/MountMSDOS with the following contents:

There are three partition identification schemes you'll run across when using NetBSD/macppc. Each identification scheme sorts the partitions differently, even though the partition's location on the disk doesn't change. Some schemes hide certain partitions.

1. Actual order on the disk (0 thru max partition number):

   This is the scheme used by Open Firmware and the /dev/diskXsY device files in Mac OS X and Darwin. The order of partitions is directly related to the order you selected in Drive Setup, pdisk, or the NetBSD partitioning tools. You can print out this list from any OS using pdisk.

   0	A special 'partition' reserved for a primary bootloader.
   1	The Apple Partition Map.
   2 thru ~8	Reserved for Mac OS 9 drivers if the drive is formatted with a Mac OS tool. Otherwise, user created partitions.
   ~9 thru ~15	User created partitions, placed in order of their physical location on disk.

2. Mac OS-visible partitions (by partition name in Finder):

   While you may have created a bunch of partitions in Drive Setup, only those partitions visible to Mac OS will show up in the Finder.

   The only partitions visible to Mac OS 9 and earlier are those formatted in HFS, HFS+, or MS-DOS formats. The only partitions visible to Mac OS X and later are those formatted in HFS, HFS+, UFS, and MS-DOS (not NetBSD's 4.2BSD FFS).

3. NetBSD-visible partitions (letters a thru h, as seen by disklabel):

   NetBSD reorders the partitions such that things work out better for itself. The fstype reported by disklabel(8) is set by the Apple Partition Map flags, and does not depend on the actual type of filesystem on that partition (be it NetBSD FFS, Apple HFS, or MS-DOS). In particular, MS-DOS formatted partitions show up as HFS partitions, if created using the method in Creating a shared MS-DOS filesystem.

   a	Your 'A/UX Root' partition, regardless of its order on the disk
   b	Your 'A/UX Swap' partition, regardless of its order on the disk
   c	This is the entire disk (first sector to last sector)
   d-f	First few non-A/UX partitions (usually the user HFS(+) partitions)
   g	Your 'A/UX User' partition (if present), regardless of its order on the disk
   h	Additional non-A/UX partitions (usually user HFS(+) partitions)

So, for example the following is what Drive Setup created on my PowerBook (FireWire):

After installation, one of the HFS partitions, 'Untitled' (which is partition 9 to Open Firmware, and partition d to NetBSD) has ofwboot.xcf, and one of the A/UX partitions (which is partition 12 to Open Firmware, and partition a to NetBSD) has my NetBSD kernel, so I use the following command to boot:

It may not feel that way, but we Mac users have now had quite a long run with OS X. We're coming up on 12 years since the first public release of the operating system (and even longer if you consider the betas and developer previews), and we've seen OS X go through plenty of changes during that time. Indeed, even Mac veterans may—with the passing of the years—have forgotten just how shaky some of those early OS versions could be.

Don't remember what OS X used to look like back when dinosaurs used to roam the planet and Apple's OS ran only on PowerPC processors? We've mined more than a decade of our own OS X reviews—studiously authored by John Siracusa—for screenshots and other OS X-related memories that trace the development of Apple's desktop OS through the 2000s. If you're interested in seeing how various UI elements have evolved over the years, strap yourself in for this safari showcasing OS X's big cats.

Mac OS X 10.0: Cheetah

https://gold-free.mystrikingly.com/blog/mark-us-prototype-mac-os. OS X was officially released to the public in 2001 after a rollercoaster series of developer previews, some of which barely resembled the final product. Because it was brand new to most users coming over from Mac OS 9, the new OS featured a number of 'shocking' interface elements, such as the new file browser:

And because so many users were still making generous use of their OS 8 and 9 applications, OS X featured a 'Classic' mode. Take a look at 10.0's Classic mode settings panel:

In his review of Mac OS X 10.0, Siracusa concluded with this fairly mixed verdict:

Mac OS X shows tremendous promise, which is a nice way of saying that the 10.0 release is not quite ready for prime time. This is most certainly an early adopter's OS release. Interface responsiveness and effective stability are the two biggest fundamental problems, but missing features and compatibility issues rank just as high if you actually intend to use OS X as a full Mac OS 9 replacement: the 10.0 release cannot view DVD movies; printer drivers are still scarce; CD burning is not yet supported, even by Apple's own iTunes CD authoring application; and a lot of hardware (like my G3/400's serial port adapter to which my printer is attached) seem destined to be orphaned forever.

Perhaps the most important feature of the 10.0 release is the Software Update preference panel. A 10.0.1 update that includes a new kernel and classic environment, SSH support, a slew of updated drivers, and many other small fixes has been circulating on the net, and may be released by the time you read this. A regular series of free, network-distributed OS updates will go a long way towards making OS X fulfill even the limited promise of a first release of a brand new operating system. Let's hope Apple doesn't foolishly try to charge for the more significant upgrade due in time for July's MacWorld Expo in New York.

Unlike previous articles, this one was written almost entirely in OS X. I forced myself to do this, to some degree, and I certainly spent most of my time in classic applications like BBEdit and Photoshop even when running OS X. But the experience was at least tolerable, which is more than can be said for my experience with earlier releases.

Should you upgrade to Mac OS X? If you don't already have a copy (or plans to buy one), the answer is no. Most users should wait for a future release, and possibly new hardware to run it on. Should Apple have released OS X in its current state? I think so. Nothing stimulates application development like a shipping OS. Let's hope that the official release of Mac OS X also stimulates Apple itself to make improvements.

Mac OS X 10.1: Puma

The next major version of Mac OS X, 10.1, was released the same year (2001) as 10.0. Apple was quick to make some tweaks in the first six months. So what did it look like?

Here's Puma's Dock:

And the System Prefs:

The Login window also sported this Aqua-fied look:

The Point Of No Return (ds23g) Mac Os Download

Siracusa's take was only a bit more positive this time around, and believing in the new OS still required nothing short of faith:

I wrote at the start of this article that I want to believe in Mac OS X. I want to believe that it will replace Mac OS 9 in a way that improves upon every aspect of the classic Mac OS user experience. Unfortunately, although this may still come to pass, Mac OS X 10.1 is not that version of Mac OS.

The Point Of No Return (ds23g) Mac Os Update

But 10.1 improves on 10.0.x in many important ways. Overall system performance shows the biggest improvement, but it is not as drastic as some reports may lead you to believe. Other areas have stagnated. The user interface has not made significant strides since 10.0.x. Many annoying bugs remain, and many features have yet to be implemented.

Should you purchase Mac OS X 10.1? If you already use and enjoy Mac OS X 10.0, you should run out and pick up a free 10.1 upgrade CD at your local retailer as soon as possible. If you tried 10.0.x and found it somewhat lacking, I recommend at least giving 10.1 a try to see if the improvements are enough to push you over the edge. If you are waiting for the point of no return, where Mac OS X is a complete no-brainer upgrade from Mac OS 9, you'll have to wait a little longer. If you plan to run Mac OS X full-time, you should consider upgrading your RAM to what were previously through of as obscene levels (512MB or more). It will be the best thing you can do for Mac OS X, short of buying a faster Mac.

If you're not a Mac user at all, but are intrigued by the possibilities of Unix based operating system with friendly user interface (Linux fans, no flames, please), 10.1 is as good a version as any to dip your toe into. Windows users should not expect a feature set remotely comparable to Windows XP, but Mac OS X is different enough that it should still broaden some horizons. And Linux users might want to see how another operating system has chosen to build a GUI on top of a Unix core.

To amend my earlier sentiment, it might be more accurate to say that I want to believe not just in Mac OS X, but in Apple itself. I want to believe that they can produce the next insanely great platform: a powerful, stable OS with an interface every Mac user can love, running on stylish, high performance hardware. Both the software and the hardware end of that dream currently need work. And so the waiting game begins again, as Mac users settle in with 10.1 and prepare for the inevitable 10.1.x updates. Will there be more 10.1 users than there were 10.0.x users? Probably. But it says something about this supposed 'mainstream release' of OS X when Apple itself is still selling all its hardware configured to boot into Mac OS 9 by default.

The Point Of No Return (ds23g) Mac Os Catalina

I want to believe. But it looks like I'll have to wait a bit longer.