Leopard running on an Atom Processor

May 27, 2021

Using PC_efi technology (a means to run OS X on a PC without kernel modification), an anonymous source for netkas.org has managed to run and benchmark Leopard on an Atom chip, which is rumored (and denied) to be headed for Mac.

The Atom Processor would certainly make a good candidate for a mini-tablet. It’s small enough to fit any form factor, and low power enough to run for long periods in small devices. According to netkas, you can even run one of these on solar power. Here are the results of an Xbench test, courtesy of netkas:

More details are available at netkas.org.

(Via The Unofficial Apple Weblog (TUAW).)

Airport Airdisk nearly useless with Leopard 10.5.1

January 12, 2021

Oh god, I just bought an Airport Extreme 802.11n thinking it would be the best networking experience of my life. I just bricked up my Linksys (flashing power light) by trying to upgrade to openWRT and needed to replace it.

So I picked up an airport extreme at BB along with a nice 360GB USB drive to serve as an airdisk.

I connect the airport, configured the network side with not much problems (except for the silly reboot every time you make a small config change… god, is this thing running Windows 98 or something ;-))

Next I connected my new Seagate HD enclosure. OK, airport complain about it and tell me that the disk need to be repaired… what? Don’t tell me the disk I just bought is defective!

I connect the disk to my mac and it came up with not problems what so ever. OK, what is the problem then? I simply reformat it as HFS+ to please the airport and connect again.

OK, now it see the thing. I configured file sharing on it and “restarted” it for the 10th time (it must really be running on windows)

What? Now I have two new network names in my finder bar… Airport and some strange cpe<mac address> name. Apparently airport won’t put a nice name on the CIFS side of the house… can I fix this please? How?

I could leave with all of the above… but what really kill me is the SLOW, SLOW, SLOW network transfer rate of the airdisk. Trying to copy a small 16MB application take like 2 minutes! But if I zip it it will transfer in like 10 seconds! What the heck is this? Is the airport that slow when transferring large qty of small files? Large file transfer rate is blazingly fast but lot of small files just kill the thing.

The other very slow thing is erasing files from the airdisk. Almost a minute to erase the 16MB application.

I am really really really disappointed with the Apple product. It is the 1st time I feel I tried a bad product from Apple… But everyone need a 1st. I hope this is the last bad Apple product I ever encounter.

I really hope there is a fix for this. I even downgrade my Airport Extreme firmware to 7.1.1 from 7.2.1 so the Airdisk would stay connected properly. With 7.2.1 it would simply not connect to airdisk after a while.

Please give me some advise!

P.S.: I don’t know if it is any better with Tiger (10.4.x) since I migrated completely to Leopard…

Leopard breaking AJAX browsers interfaces

October 28, 2021

OK, I confess, I am not an AJAX expert… but one thing I know is that Leopard broke some web sites AJAX upload features.

For example, using Apple Leopard, Vimeo upload and Flickr upload are broken. I have not done a huge search for other sites suffering from the same thing but I am sure there are a ton more.

The interesting thing is that this is not with Apple Safari browser… it is with Firefox 2.0.0.8! The exact same Firefox browser that I use in Tiger… And yes, I booted back into Tiger and verified that everything was working with it.

So for all I know Leopard is somehow breaking some of those nice AJAX interfaces… in both Firefox and Safari. Why? I have no idea! But it is rather odd that it impact both Safari and Firefox.

Update:

People on Digg have started to comment that MySpace suffer the same faith. I wonder if this is something Apple can address via a software update?

Digg this story!

Apple to release latest Leopard beta to developers who couldn’t make WWDC

June 24, 2021

A little green and blue TUAW birdie has just informed the web that Apple is planning to release the Leopard beta that WWDC attendees received last week to the rest of qualifying ADC members. As to when developers can fire up their browsers and download managers, the only language we have to go on is ’soon.’

We’re also told that this secondary release is happening quite a bit sooner than it did at last year’s WWDC, so I guess this might be a win for developers, all things considered.

[Source: TUAW]

ZFS is part of Leopard after all

June 12, 2021

Seeking to clarify a statement made on Monday by Brian Croll, senior director of Mac OS X Product Marketing, to two InformationWeek reporters that Apple’s new “Leopard” operating system would not include the ZFS file system, an Apple spokesperson indicated that ZFS would be available as a limited option, but not as the default file system.

[Via Information week]

OSX Leopard will not run on ZFS

June 12, 2021

Much to the dismay of those Macheads who’ve started hitting size limits in Tiger’s HFS+ file system (all ten of you), Apple has confirmed to InformationWeek that Leopard will not in fact adopt the more capacious ZFS alternative as promised last week by Sun CEO Jonathan Schwartz.

[Via Engadget]

ZFS will be OSX 10.5 default file system

June 6, 2021

Perhaps overcome with excitement (and forgetting that Apple doesn’t like such pre-emptive disclosures), Sun’s Jonathan Schwartz announced today at Sun event in Washington D.C. that Apple would be making ZFS “the file system” in Mac OS 10.5 Leopard

ZFS is a new kind of filesystem that provides simple administration, transactional semantics, end-to-end data integrity, and immense scalability. Thousands of filesystems can draw from a common storage pool, each one consuming only as much space as it actually needs.

The combined I/O bandwidth of all devices in the pool is available to all filesystems at all times. A scrub traverses the entire storage pool to read every copy of every block, validate it against its 256-bit checksum, and repair it if necessary.

ZFS provides unlimited constant-time snapshots and clones. Any snapshot can generate a full backup, and any pair of snapshots can generate an incremental backup. In addition to reducing space usage by 2-3x, compression also reduces the amount of I/O by 2-3x.

It should therefore be no surprise that Apple adopt this file system as the basis for “Time Machine“.

[Via MacRumors]

Update:

Sorry for the typo in the title ;-) Now corrected!