Killexams.com 9L0-063 brain dumps | Pass4sure 9L0-063 brain dumps | | jeepmansoffroad

Pass4sure 9L0-063 dumps | Killexams.com 9L0-063 existent questions | http://www.jeepmansoffroad.com/

9L0-063 Mac OS X Troubleshooting 10.7

Study steer Prepared by Killexams.com Apple Dumps Experts


Killexams.com 9L0-063 Dumps and existent Questions

100% existent Questions - Exam Pass Guarantee with tall Marks - Just Memorize the Answers



9L0-063 exam Dumps Source : Mac OS X Troubleshooting 10.7

Test Code : 9L0-063
Test title : Mac OS X Troubleshooting 10.7
Vendor title : Apple
brain dumps : 65 existent Questions

worked difficult on 9L0-063 books, however the entire component own become on this test manual.
I got a satisfactory result with this bundle. Very satisfactory quality, questions are accurate and I got most of them on the exam. After I own passed it, I recommended killexams.com to my colleagues, and everyone passed their exams, too (some of them took Cisco exams, others did Microsoft, VMware, etc). I own not heard a indecent review of killexams.com, so this must live the best IT training you can currently find online.


can you harmonize with that every one 9L0-063 questions I had own been requested in existent check.
This instruction kit has helped me bypass the examination and gyrate out to live 9L0-063 licensed. I couldnt live more excited and grateful to killexams.com for such an clean and dependable coaching device. Im capable of affirm that the questions within the package deal are actual, this isnt always a faux. I selected it for being a dependable (advocated with the useful resource of a chum) manner to streamline the exam coaching. dote many others, I couldnt approach up with the cash for studying complete time for weeks or maybe months, and killexams.com has allowed me to squeeze down my preparation time and nonetheless win a incredible give up result. Remarkable retort for busy IT professionals.


No less expensive source than those 9L0-063 brain dumps dumps available but.
I surpassed the 9L0-063 certification these days with the assist of your furnished Questions solutions. This combined with the path that you exigency to prefer a satisfactory artery to become a certified is the manner to move. In case you finish but suppose that actually remembering the questions and answers is bar nothing you exigency to pass properly youre wrong. There had been pretty a few questions about the exam that are not inside the provided QA but in case you prepare these forms of Questions solutions; you may strive those very with out problem. Jack from England


Do no longer expend huge quantity on 9L0-063 courses, win this question bank.
The best preparation I own ever experienced. I took many 9L0-063 certification exams, but 9L0-063 turned out to live the easiest one thanks to killexams.com. I own recently discovered this website and wish I knew about it a few years ago. Would own saved me a lot of sleepless nights and grey hair! The 9L0-063 exam is not an easy one, especially its latest version. But the 9L0-063 Q and A includes the latest questions, daily updates, and these are absolutely undoubted and valid questions. Im convinced this is staunch cause I got most of them during my exam. I got an excellent score and thank killexams.com to making 9L0-063 exam stress-free.


What are requirements to bypass 9L0-063 exam in Little attempt?
way to killexams.com this website online gave me the tackle and self faith I needed to crack the 9L0-063. The websitehas treasured facts to cheer you to acquire success in 9L0-063 manual. In gyrate I got here to realize approximately the 9L0-063 education software program. This software program is outlining each topic matter and achieve query in random order just dote the test. you may win rating additionally to cheer you to evaluate yourself on unique parameters. outstanding


blessings today's 9L0-063 certification.
Hats down the fine 9L0-063 exam practise choice. I passed my 9L0-063 examination remaining week, and this set of examquestions and answers has been very beneficial. these things from killexams.com is proper. before making a purchase, I contacted customer service with questions about how up to date their materials are, and that they confirmed that they supplant bar nothing tests on nearly every day basis. They upload updates wherein vital, or simply double prefer a ascertain at the content material to originate sure its up to date. It justifies buying an examination sarcasm unload. With killexams.com, I recognizethat im able to depend on the todays examination materials, not some e-book that may grow to live obsolete every week after its published. So I assume this is the satisfactory exam preparation option. I assume i will expand my certification portfolio into some other carriers, Im simply not positive which of them but. however what Im positiveapproximately is that I will live the utilize of killexams.com as my fundamental practise resource.


Shortest question are blanketed in 9L0-063 query bank.
I searched for the dumps which satisfy my particular needs on the 9L0-063 examination prep. The killexams.com dumps certainly knocked out bar nothing my doubts in a short time. First time in my career, I honestly attend the 9L0-063 examination with handiest one instruction fabric and live successful with a much score. i am without a doubt satisfied, but the purpose imright here to congratulate you at the outstanding cheer you furnished in the shape of study cloth.


in which to symptom up for 9L0-063 exam?
First of bar nothing I want to recount Thanks to you people. I own cleared 9L0-063 Exam by subscribing to your study materials. So I wanted to share my success on your website. Thank you once again. Thank you very much for your much support. I own cleared my 9L0-063 with 90%.


where will I locate questions and solutions to own a ascertain at 9L0-063 exam?
Even though i own enough history and revel in in IT, I predicted the 9L0-063 exam to live less difficult. killexams.com has saved my money and time, without these QAs id own failed the 9L0-063 exam. I got harassed for few questions, so I nearly had to bet, however that is my fault. I must own memorized well and listen the questions better. Its amend to realize that I surpassed the 9L0-063 exam.


Take a smart circulate to pass 9L0-063
fantastic coverage of 9L0-063 examination ideas, so I scholarly precisely what I wanted during the 9L0-063 exam. I tremendously propound this education from killexams.com to anybody making plans to prefer the 9L0-063 exam.


Apple Apple Mac OS X

how to Revisit each version of Mac OS X from your Browser | killexams.com existent Questions and Pass4sure dumps

The Aqua GUI in Apple’s operating techniques has gone through a unbelievable evolution because March of 2000, when it discovered its artery into OS X 10.0, and you might possibly live stunned at simply how distinctive every thing appears now. because of the newly launched Aqua Screenshot Library, which you can revisit each version of OS X (and macOS) during the years and view the gradual evolution of Apple’s operating equipment—all out of your browser.

The huge gallery is the latest travail by means of 512 Pixels, an internet library that makes an attempt to hold tabs on bar nothing things Apple (including the Mac’s many wallpapers). The Aqua Screenshot Library, as creator Stephen Hackett notes, provides a complete look to live at the history of Apple’s operating programs, which covers its start to from bulkier CRTs to compact, LED-backlit displays; Apple’s quite a lot of font alterations over the years; and Apple’s rush from disc-based operating techniques to (free) digital downloads.

Let’s prefer a glance at some of these well-known Mac milestones.

Mac OS X 10.0 (“Cheetah”)

March 24, 2001, marked the first legitimate unlock of the Mac OS X operating equipment, following a public beta the yr earlier than. Hackett notes that its 128MB remembrance requirement became “more than most Mac users had of their programs on the time.” This result in many complaints in regards to the OS’s tedious efficiency and unreasonable useful resource demand. The Cheetah interface retained the pin-striped menu and window design from the beta, but it begun the feline-based mostly naming vogue which would final as much as edition 10.eight, “Mountain Lion.”

Mac OS X Leopard (10.5)

The closing months of 2007 brought some huge changes to OS X. The free up of Leopard saw Aqua prefer on a a all lot greater streamlined appear, with bar nothing home windows now defaulting to a single, elementary grey design, as neatly because the debut of a redesigned Finder tool. prior to this, discrete apps—and diverse types of OS X—had assorted UI designs (for better or worse). With Leopard’s free up, OS X started to ascertain more uniform. most importantly, it turned into the primary edition to encompass those rad, house-primarily based backgrounds.

OS X Mountain Lion (10.8)

Mountain Lion become the primary version of OS X to gain after Steve Jobs’ dying, and it concentrated on aligning Mac computers with the late CEO’s different well-known contribution to the tech business: the iPhone. The 2011 OS X update, Mac OS X Lion (10.7), kicked off Apple’s merging of iOS aesthetics into OS X, and the company doubled down with Mountain Lion. tackle and applications own been renamed after iOS facets, and Apple brought some tiny visible and input changes to bridge the two working programs even nearer collectively—in vogue, at least.

OS X Mavericks (10.9)

Mavericks became an stupendous business pivot for Apple, because it become the first version of the OS the company released for gratis, offered to clients as an upgrade by the utilize of the App reclaim in October 2013. Apple hasn’t long gone returned to paid operating systems considering that—happily. Mavericks was additionally the primary version of OS X to originate utilize of non-pussycat nomenclature. It furthermore ditched the galactic history theme for California landscapes, which they can bar nothing harmonize become an stupendous blunder. right?

macOS Sierra (10.12)

edition 10.12 of Apple’s operating tackle for the Mac is most is extraordinary for its tremendous rebranding. Apple dropped the “OS X” identify thoroughly in this free up, as a substitute calling its operating gadget “macOS” to align it the business’s working systems on different structures: iOS, watchOS, and tvOS. 

browsing the Aqua Screenshot Library is a enjoyable approach to behold just how far macOS has come, peculiarly to behold how Apple’s design priorities exchange between the fundamental releases. however, the Aqua Screenshot gallery is just one of 512 Pixels’ many initiatives to try. originate unavoidable to poke across the other Apple-themed collections Hackett has assembled over the years, too, including the astonishing 512 Pixels YouTube channel.


OS X/macOS now older than traditional Mac OS | killexams.com existent Questions and Pass4sure dumps

Older readers could nonetheless endure in sarcasm when Macs made the transition to OS X, more these days rebranded to macOS. but when you nonetheless kindly of suppose of that because the ‘new’ OS, as of these days it’s in reality now been round for longer than bar nothing of the preceding models – collectively and colloquially called basic Mac OS …

Jason Snell marked the occasion in a blog achieve up the day before today.

today marks 17 years, one month, and 29 days on account that Mac OS X 10.0 changed into launched on March 24, 2001. That’s a surprisingly unusual quantity—6,269 days—however additionally happens to live the exact size of time between January 24, 1984 (the launch of the long-established Macintosh) and March 24, 2001.

In other words, nowadays the Mac’s 2nd working gadget period, powered by Mac OS X (now macOS) has been in being provided that the first era was.

As he notes, it does depend just a Little on the artery you measure these things.

There became a Mac OS X public beta. The funeral for Mac OS 9 wasn’t held except 2002. basic Mode persisted to characteristic within Mac OS X except it became removed in Mac OS X 10.5 Leopard.

So for beta users, the milestone may additionally had been passed ages lower back, and for those that held onto Mac OS 9 for some time after OS X launched, it can not yet own arrived.

Early models of the Macintosh tackle utility had no answerable identify, with Apple referring most effective to Macintosh Toolbox ROM and the system Folder. It only became Macintosh gadget utility in 1987, with what was then referred to as system 5. Apple rebranded it to Mac OS in 1996, at tackle 7.6.

As to the long run, Snell says that he doesn’t behold a ‘seismic’ shift any time soon, more a gradual raise within the borrowing from iOS. however he does renowned that a original chip could behold the system gyrate up in bar nothing places again.

there was persisted hypothesis about Apple switching from Intel to ARM chips for future Macs, with one recent file suggesting it may ensue as quickly as 2020. I gave my very own view on that conception, concluding that the date may emerge unlikely, but that it's coming quickly.

that you can download bar nothing the default wallpapers in 5K from 512 Pixels.

by means of Daring Fireball. image: 512 Pixels

try 9to5Mac on YouTube for more Apple information:


listed here are the 13 most useful Mac shortcuts so that you can aid you finish every thing quicker | killexams.com existent Questions and Pass4sure dumps

apple white macbookmaster your MacBook. Mustafa Quraishi/AP

Apple's MacOS may look simple — however's an absolute powerhouse in case you comprehend how to utilize it.

one of the easiest the artery to win probably the most of out of Apple's laptop working device are hidden in undeniable sight: Keyboard shortcuts.

Flick between purposes and tabs. prefer screenshots. best-tune settings. knowing the usurp keyboard shortcuts will store a 2nd here and there — and over the course of per week, or a month, or a 12 months, it provides up dramatically.

if you are passion adventurous, Apple lists bar nothing of its Mac keyboard shortcuts here.

here are 13 of the most advantageous keyboard shortcuts with a view to reclaim you time on the Little things so you can focus on the large things:

(Max Slater-Robins contributed to an past edition of this article.)


9L0-063 Mac OS X Troubleshooting 10.7

Study steer Prepared by Killexams.com Apple Dumps Experts


Killexams.com 9L0-063 Dumps and existent Questions

100% existent Questions - Exam Pass Guarantee with tall Marks - Just Memorize the Answers



9L0-063 exam Dumps Source : Mac OS X Troubleshooting 10.7

Test Code : 9L0-063
Test title : Mac OS X Troubleshooting 10.7
Vendor title : Apple
brain dumps : 65 existent Questions

worked difficult on 9L0-063 books, however the entire component own become on this test manual.
I got a satisfactory result with this bundle. Very satisfactory quality, questions are accurate and I got most of them on the exam. After I own passed it, I recommended killexams.com to my colleagues, and everyone passed their exams, too (some of them took Cisco exams, others did Microsoft, VMware, etc). I own not heard a indecent review of killexams.com, so this must live the best IT training you can currently find online.


can you harmonize with that every one 9L0-063 questions I had own been requested in existent check.
This instruction kit has helped me bypass the examination and gyrate out to live 9L0-063 licensed. I couldnt live more excited and grateful to killexams.com for such an clean and dependable coaching device. Im capable of affirm that the questions within the package deal are actual, this isnt always a faux. I selected it for being a dependable (advocated with the useful resource of a chum) manner to streamline the exam coaching. dote many others, I couldnt approach up with the cash for studying complete time for weeks or maybe months, and killexams.com has allowed me to squeeze down my preparation time and nonetheless win a incredible give up result. Remarkable retort for busy IT professionals.


No less expensive source than those 9L0-063 brain dumps dumps available but.
I surpassed the 9L0-063 certification these days with the assist of your furnished Questions solutions. This combined with the path that you exigency to prefer a satisfactory artery to become a certified is the manner to move. In case you finish but suppose that actually remembering the questions and answers is bar nothing you exigency to pass properly youre wrong. There had been pretty a few questions about the exam that are not inside the provided QA but in case you prepare these forms of Questions solutions; you may strive those very with out problem. Jack from England


Do no longer expend huge quantity on 9L0-063 courses, win this question bank.
The best preparation I own ever experienced. I took many 9L0-063 certification exams, but 9L0-063 turned out to live the easiest one thanks to killexams.com. I own recently discovered this website and wish I knew about it a few years ago. Would own saved me a lot of sleepless nights and grey hair! The 9L0-063 exam is not an easy one, especially its latest version. But the 9L0-063 Q and A includes the latest questions, daily updates, and these are absolutely undoubted and valid questions. Im convinced this is staunch cause I got most of them during my exam. I got an excellent score and thank killexams.com to making 9L0-063 exam stress-free.


What are requirements to bypass 9L0-063 exam in Little attempt?
way to killexams.com this website online gave me the tackle and self faith I needed to crack the 9L0-063. The websitehas treasured facts to cheer you to acquire success in 9L0-063 manual. In gyrate I got here to realize approximately the 9L0-063 education software program. This software program is outlining each topic matter and achieve query in random order just dote the test. you may win rating additionally to cheer you to evaluate yourself on unique parameters. outstanding


blessings today's 9L0-063 certification.
Hats down the fine 9L0-063 exam practise choice. I passed my 9L0-063 examination remaining week, and this set of examquestions and answers has been very beneficial. these things from killexams.com is proper. before making a purchase, I contacted customer service with questions about how up to date their materials are, and that they confirmed that they supplant bar nothing tests on nearly every day basis. They upload updates wherein vital, or simply double prefer a ascertain at the content material to originate sure its up to date. It justifies buying an examination sarcasm unload. With killexams.com, I recognizethat im able to depend on the todays examination materials, not some e-book that may grow to live obsolete every week after its published. So I assume this is the satisfactory exam preparation option. I assume i will expand my certification portfolio into some other carriers, Im simply not positive which of them but. however what Im positiveapproximately is that I will live the utilize of killexams.com as my fundamental practise resource.


Shortest question are blanketed in 9L0-063 query bank.
I searched for the dumps which satisfy my particular needs on the 9L0-063 examination prep. The killexams.com dumps certainly knocked out bar nothing my doubts in a short time. First time in my career, I honestly attend the 9L0-063 examination with handiest one instruction fabric and live successful with a much score. i am without a doubt satisfied, but the purpose imright here to congratulate you at the outstanding cheer you furnished in the shape of study cloth.


in which to symptom up for 9L0-063 exam?
First of bar nothing I want to recount Thanks to you people. I own cleared 9L0-063 Exam by subscribing to your study materials. So I wanted to share my success on your website. Thank you once again. Thank you very much for your much support. I own cleared my 9L0-063 with 90%.


where will I locate questions and solutions to own a ascertain at 9L0-063 exam?
Even though i own enough history and revel in in IT, I predicted the 9L0-063 exam to live less difficult. killexams.com has saved my money and time, without these QAs id own failed the 9L0-063 exam. I got harassed for few questions, so I nearly had to bet, however that is my fault. I must own memorized well and listen the questions better. Its amend to realize that I surpassed the 9L0-063 exam.


Take a smart circulate to pass 9L0-063
fantastic coverage of 9L0-063 examination ideas, so I scholarly precisely what I wanted during the 9L0-063 exam. I tremendously propound this education from killexams.com to anybody making plans to prefer the 9L0-063 exam.


Unquestionably it is difficult assignment to pick dependable certification questions/answers assets regarding review, reputation and validity since individuals win sham because of picking incorrectly benefit. Killexams.com ensure to serve its customers best to its assets concerning exam dumps update and validity. The vast majority of other's sham report dissension customers approach to us for the brain dumps and pass their exams joyfully and effortlessly. They never trade off on their review, reputation and attribute on the grounds that killexams review, killexams reputation and killexams customer certainty is imperative to us. Uniquely they deal with killexams.com review, killexams.com reputation, killexams.com sham report objection, killexams.com trust, killexams.com validity, killexams.com report and killexams.com scam. On the off chance that you behold any erroneous report posted by their rivals with the title killexams sham report grievance web, killexams.com sham report, killexams.com scam, killexams.com protest or something dote this, simply recollect there are constantly Awful individuals harming reputation of satisfactory administrations because of their advantages. There are a huge number of fulfilled clients that pass their exams utilizing killexams.com brain dumps, killexams PDF questions, killexams hone questions, killexams exam simulator. Visit Killexams.com, their specimen questions and test brain dumps, their exam simulator and you will realize that killexams.com is the best brain dumps site.


Vk Profile
Vk Details
Tumbler
linkedin
Killexams Reddit
digg
Slashdot
Facebook
Twitter
dzone
Instagram
Google Album
Google About me
Youtube



70-548-Csharp questions and answers | 600-455 study guide | 350-025 practice questions | PSAT exam prep | LOT-952 practice test | 000-118 free pdf | 312-49v9 braindumps | SU0-211 pdf download | 650-325 mock exam | 70-355 test prep | 920-234 braindumps | 1Z0-863 existent questions | HP0-D13 exam questions | ST0-132 practice exam | 310-230 VCE | HP0-918 dumps questions | 000-958 existent questions | HP3-C29 free pdf download | 70-552-VB practice questions | E20-920 free pdf |


9L0-063 exam questions | 9L0-063 free pdf | 9L0-063 pdf download | 9L0-063 test questions | 9L0-063 real questions | 9L0-063 practice questions

People used these Apple dumps to win 100% marks
killexams.com is a answerable and trustworthy platform who provides 9L0-063 exam questions with 100% success guarantee. You exigency to practice questions for one day at least to score well in the exam. Your existent journey to success in 9L0-063 exam, actually starts with killexams.com exam practice questions that is the excellent and verified source of your targeted position.

If you are interested in properly Passing the Apple 9L0-063 exam to start incomes? killexams.com has leading aspect evolved Mac OS X Troubleshooting 10.7 test questions with the aim to originate sure you pass this 9L0-063 exam! killexams.com will proffer you the foremost correct, up to date and progressive updated 9L0-063 exam questions and out there with a 100 percent refund guarantee. There are several companies that proffer 9L0-063 brain dumps but those are not amend and recent ones. Preparation with killexams.com 9L0-063 original questions will live a nice manner to pass this certification test in swish manner. We are bar nothing properly watchful that a main pains within the IT business is there will live an absence of superior braindumps. Their test practice dumps provides you the all thing you will exigency to require a certification test. Their Apple 9L0-063 exam offers you with test questions with confirmed solutions that replicate the well-known test. These Questions and Answers provide you with the relish of taking the particular exam. High-quality and low cost for the 9L0-063 exam. 100% guarantee to pass your Apple 9L0-063 exam and acquire your Apple certification. they own a inclination at killexams.com are committed to assist you pass your 9L0-063 exam with tall scores. the probabilities of you failing your 9L0-063 exam, once memorizing their complete test dumps are little. Apple 9L0-063 is rare bar nothing over within the globe, and furthermore the business and programming arrangements gave via them are being grasped by means of each one amongst the businesses. they exigency helped in employing a giant style of firms on the far side any doubt shot means of accomplishment. so much attaining progressing to understand of Apple certifications are needed to certify as an well-known practicality, and furthermore the specialists showed through them are hugely prestigious altogether associations.

killexams.com encourages an unbelievable numerous applicants finish the tests and win their certifications. They own an extensive amount of compelling studies. Their dumps are strong, sensible, updated and of really best much to beat the issues of any IT certifications. killexams.com exam dumps are latest updated in rather overcome path on measure start and fabric is released discontinuously. Latest killexams.com dumps are reachable in experimenting with centers with whom they are holding up their dating to win most extreme late material.

The killexams.com exam inquiries for 9L0-063 Mac OS X Troubleshooting 10.7 exam is basically in perspective of two to live had game plans, PDF and practice test program. PDF record passes on the majority of the exam questions, arrangements which makes your making arrangements less dedicated. While the practice test program are the complimentary detail inside the exam protest. Which serves to self-overview your reinforce. The assessment gear furthermore works your infirm regions, where you exigency to situated more endeavor with the point that you may upgrade every one among your worries.

killexams.com recommend you to must endeavor its free demo, you will behold the classic UI and besides you will believe that its simple to change the prep mode. Regardless, ensure that, the genuine 9L0-063 exam has a greater wide assortment of inquiries than the preparatory shape. In case, you are assuaged with its demo then you could buy the genuine 9L0-063 exam question. killexams.com offers you 3 months free updates of 9L0-063 Mac OS X Troubleshooting 10.7 exam questions. Their grip aggregate is always reachable at returned capitulation who updates the material as and while required.

killexams.com Huge Discount Coupons and Promo Codes are as under;
WC2017: 60% Discount Coupon for bar nothing exams on website
PROF17: 10% Discount Coupon for Orders greater than $69
DEAL17: 15% Discount Coupon for Orders greater than $99
OCTSPECIAL: 10% Special Discount Coupon for bar nothing Orders


9L0-063 Practice Test | 9L0-063 examcollection | 9L0-063 VCE | 9L0-063 study guide | 9L0-063 practice exam | 9L0-063 cram


Killexams P2140-021 practice exam | Killexams 1Z0-521 examcollection | Killexams 922-101 cram | Killexams CFA-Level-I existent questions | Killexams 9A0-045 practice questions | Killexams 312-50v7 practice test | Killexams 650-059 study guide | Killexams E20-357 test questions | Killexams DEV-401 mock exam | Killexams HP0-S32 test prep | Killexams ADM211 exam prep | Killexams 1Z1-507 free pdf | Killexams 4H0-533 exam questions | Killexams M2040-641 braindumps | Killexams 1Z0-050 braindumps | Killexams HP0-697 exam prep | Killexams EX0-105 sample test | Killexams 820-427 questions and answers | Killexams 000-022 dump | Killexams EE0-501 practice test |


Exam Simulator : Pass4sure 9L0-063 VCE Exam Simulator

View Complete list of Killexams.com Brain dumps


Killexams C9060-509 existent questions | Killexams 000-M43 dumps questions | Killexams EE0-021 free pdf | Killexams 000-386 study guide | Killexams E20-597 questions and answers | Killexams 77-885 practice questions | Killexams MA0-150 free pdf | Killexams 000-N14 existent questions | Killexams HP2-E24 braindumps | Killexams A2010-569 test prep | Killexams P2020-795 dumps | Killexams MB3-210 practice exam | Killexams HP0-J17 study guide | Killexams A2010-573 braindumps | Killexams 650-296 braindumps | Killexams C7020-230 mock exam | Killexams 1D0-538 VCE | Killexams VCI510 practice test | Killexams A2010-578 brain dumps | Killexams 9L0-206 cram |


Mac OS X Troubleshooting 10.7

Pass 4 sure 9L0-063 dumps | Killexams.com 9L0-063 existent questions | http://www.jeepmansoffroad.com/

Inside Mac OS X 10.7 Lion: original Wi-Fi Diagnostics tool | killexams.com existent questions and Pass4sure dumps

 

Feature

Apple has added a original Wi-Fi Diagnostics utility to monitor the performance of wireless networks, record events, capture raw network frames, and log diagnostic data that can live sent to Apple by users for troubleshooting.The original app is in the hidden /System/Library/CoreServices folder, where Mac OS X stores a variety of utility apps that are integrated into the Mac desktop, including the Dock, Finder, Software Update, and Archive Utility.

Users can launch the tool by Option clicking on the Wi-Fi Menu Bar icon, which then presents an otherwise hidden "Open Wi-Fi Diagnostics" option (below).

After opening, the tool presents options to Monitor Performance, Record Events, Capture Raw Frames, or gyrate on Debug Logs. A Learn More button outlines what these options finish in a drop down sheet (below).

Monitor Performance works similar to AirPort Utility's Wireless Clients graphing feature, but provides a more detailed presentation of signal and hullabaloo for the client, rather than tracking every vigorous client on a given base station. It can furthermore Report the collected data to Apple for utilize in troubleshooting issues.

Other options log events or capture raw frame data in the background to a temporary .pcap (packet capture) file, which can similarly live reported to Apple for troubleshooting help.

Also noticeably original and different in Mac OS X Lion is network setup for 802.1x security. Formerly, users could manually enter settings or install a profile the automatically configured the settings. In Lion, Apple informs users that their network administrator will deliver a configuration profile (below).

Apple created configuration profiles for iOS along with a system site administrators can utilize to roll out initial settings and subsequent updates to their users. In Lion Server, the very infrastructure can live used to remotely deliver network configuration files that automate the management of Macs just dote iOS devices.


How to Create a Bootable Mac OS X USB Disk | killexams.com existent questions and Pass4sure dumps

This article will allow you to learn the necessary steps for creating your own bootable Mac OS X Leopard (or Lion) image on a USB remembrance stick. This might live needed if your Mac needs a reinstall or a “Repair Disk” procedure and it has problems reading the bundled Install disc. To utilize this tutorial an 8 GB or larger USB stick, a second Mac computer with a working SuperDrive or a Mac OS X Install disc DMG file will live needed.

If you ever had problems with your Mac OS X installation you know that the first thing you should finish is to check the startup volume using Disk Utility.

After the check has ended and, if the errors exceed a unavoidable smooth of seriousness, the Disk Utility application will require you to restart your Mac and utilize its Mac OS X Install disc counterpart.

Other users may own to reinstall OS X altogether, but will find, or already know, that their SuperDrive (a CD/DVD reader and write combo drive) is not functioning properly and it will not live able to read the Install disc.

Although this might occur to Mac OS X Leopard users due to faulty hardware, the vast majority of problematic SuperDrives will live encountered inside Snow Leopard running Macs.

This is due to the updated SuperDrive firmware included in either the Install disc or the software updates one has to install to gain the latest version of OS X, namely 10.6.6.

This can live fixed by flashing the SuperDrive’s stock firmware using free command line tools that one can find for free online (I will write about this process also, but at a later time because this article only focuses on allowing you to create your own alternative USB boot disc).

If you are reading this final bit of information with skepticism, than you should know that it happened to me too. Despite bar nothing my tries to originate it travail properly, the SuperDrive kept on munching any inserted DVDs and just popped them out in about twenty seconds.

The workaround to this issue was to create my own Leopard bootable USB remembrance stick. I am not suggesting a Snow Leopard bootable stick mainly because there are lots of users that own decided to buy the cheaper, Upgrade version, which I own not tested and, therefore, I’m not sure if it will travail properly once written to a USB disk.

And now, here are the exact steps you should ensue in order to obtain a fully bootable Leopard (or Lion) Install disc.

Step 1 (If you already own the Leopard install disc DMG file you can skip to Step 2)

Launch Disk Utility (you can find it inside /Applications/Utilities). Here select the Leopard Install disc in the list of drives on the left and click on the original Image menu entry at the top of the window. A reclaim message will emerge where you will own to select the Desktop as a destination.

Step 2

After Disk Utility has finished creating the Leopard DMG, insert your USB stick and cancel bar nothing data and reformat the disk. To finish this select the USB in the list of drives on the left and, after clicking on the cancel tab on the privilege side of the window, pick the Mac OS Extended (Journaled) format and click the cancel button beneath.

Step 3

After the USB has been reformatted, download the SuperDuper app from HERE and launch it. Once SuperDuper starts, you will only own to select the DMG in the Copy drop-down menu, your USB remembrance stick on the privilege and hit the “Copy Now” button.

One can furthermore utilize Disk Utility for this job but creating a bootable USB stick failed 2 out 4 times when copying the DMG to the stick (with the exact very settings each time). Creating the bootable stick using SuperDuper proved to live the consummate artery to finish it because it worked each of the 4 times I tested it.

The steps above can furthermore live used to create a bootable Mac OS X Lion USB by using the InstallESD.dmg image you can find inside the Lion installer (named “Install Mac OS X Lion.app”) downloaded from the Mac App Store in the /Applications folder.

To locate the InstallESD.dmg privilege click the Lion installer, select the “Show Package Contents” entry, fade inside the “Contents” folder, and from there into the “SharedSupport” folder. Inside this folder you can find the InstallESD.dmg you can utilize to create your own bootable Mac OS X Lion USB stick. To finish so, fade to the third step described above and utilize the InstallESD.dmg as the DMG to live copied to your USB disc.

That’s it! Once the process ends you will own a fully bootable Leopard (or Lion) USB disk that you can utilize as an alternative to the Apple’s DVD Install disc that comes bundled with bar nothing Macs.

To utilize your newly created bootable disk you will own to restart the Mac, press and hold the OPTION key until the Startup Manager appears. Here, select the Mac OS X Install disk using your keyboard arrows and press recur to start from the selected drive.

If you own any questions or any problems while following the above steps, leave a remark and I will win back to you with an retort as soon as possible.

[Update 1] Added the minimum USB stick size needed at the nascence of the article and Install Mac OS X Lion.app's location.


Mac OS X 10.7 Lion: the Ars Technica review | killexams.com existent questions and Pass4sure dumps

Mac OS X 10.7 Lion: the Ars Technica review reader comments 401 with 262 posters participating, including narrative author Share this story
  • Share on Facebook
  • Share on Twitter
  • Share on Reddit
  • Mac OS X 10.7 was first shown to the public in October 2010. The presentation was understated, especially compared to the bold rhetoric that accompanied the launches of the iPhone ("Apple reinvents the phone") and the iPad ("a magical and revolutionary device at an unbelievable price"). Instead, Steve Jobs simply called the original operating system "a sneak peek at where we're going with Mac OS X."

    Behind Jobs, the screen listed the seven previous major releases of Mac OS X: Cheetah, Puma, Jaguar, Panther, Tiger, Leopard, and Snow Leopard. Such brief retrospectives are de rigueur at major Mac OS X announcements, but long-time Apple watchers might own felt a slight tingle this time. The public "big cat" branding for Mac OS X only began with Jaguar; code names for the two earlier versions were not well known outside the developer community and were certainly not Part of Apple's official marketing message for those releases. Why bring the cat theme back to the forefront now?

    Want an eBook or PDF copy? back Ars and it's yours.

    The retort came on the next slide. The next major release of Mac OS X would live called Lion. Jobs didn't originate a tremendous deal out of it; Lion's just another tremendous cat name, right? Within seconds, they were on to the next slide, where Jobs was pitching the original release's message: not "king of the jungle" or "the biggest tremendous cat," but the "back to the Mac" theme underlying the entire event. Mac OS X had spawned iOS, and now Apple was bringing innovations from its mobile operating system back to Mac OS X.

    Apple had satisfactory reason to diffident away from presenting Lion as the pinnacle that its title implies. The final two major releases of Mac OS X were both profoundly shaped by the meteoric mount of their younger sibling, iOS.

    Steve Jobs presents the first seven releases of Mac OS X in a slightly unusual formatSteve Jobs presents the first seven releases of Mac OS X in a slightly unusual format

    Leopard arrived later than expected, and in the very year that the iPhone was introduced. Its successor, Snow Leopard, famously arrived with Your browser does not back the audio element. Click here to listen

    no original features , concentrating instead on internal enhancements and bug fixes. Despite believable official explanations, it was difficult to quiver the passion that Apple's burgeoning mobile platform was stealing resources—not to mention the spotlight—from the Mac.

    In this context, the title Lion starts to prefer on darker connotations. At the very least, it seems dote the conclude of the tremendous cat branding—after all, where can you fade after Lion? Is this process of taking the best from iOS and bringing it back to the Mac platform just the first angle of a complete assimilation? Is Lion the conclude of the line for Mac OS X itself?

    Let's achieve aside the pessimistic prognostication for now and consider Lion as a product, not a portent. Apple pegs Lion at 250+ original features, which doesn't quite match the 300 touted for Leopard, but I guess it bar nothing depends on what you consider a "feature" (and what that "+" is suppositious to mean). Still, this is the most significant release of Mac OS X in many years—perhaps the most significant release ever. Though the number of original APIs introduced in Lion may drop short of the landmark Tiger and Leopard releases, the most well-known changes in Lion are radical accelerations of past trends. Apple appears tired of dragging people kicking and screaming into the future; with Lion, it has simply decided to leave without us.

    Table of Contents
  • Installation
  • Reconsidering fundamentals
  • Lion's original look
  • Scroll bars
  • Window resizing
  • Animation
  • Here's to the crazy ones
  • Window management
  • Application management
  • Document model
  • Process model
  • The pitch
  • The reality
  • Internals
  • Security
  • Sandboxing
  • Privilege separation
  • Automatic Reference Counting
  • Enter (and exit) garbage collection
  • Cocoa remembrance management
  • Enter ARC
  • ARC versus garbage collection
  • ARC versus the world
  • The condition of the file system
  • What's wrong with HFS+
  • File system changes in Lion
  • File system future
  • Document revisions
  • Resolution independence
  • Applications
  • The Finder
  • Mail
  • Safari
  • Grab bag
  • System Preferences
  • Auto-correction
  • Mobile Time Machine
  • Lock screen
  • Emoji
  • Terminal
  • About This Mac
  • Recommendations
  • Conclusion
  • A brief note on branding: on Apple's website and in some—but not all—marketing materials, Apple refers to its original Mac operating system as "OS X Lion." This may well gyrate out to live the title going forward, but given the current condition of confusion and my own stubborn nostalgia, I'm going to convoke it "Mac OS X" throughout this review. Indulge me.

    Installation

    Lion's system requirements don't differ much from Snow Leopard's. You soundless exigency an Intel-based Mac, though this time it must furthermore live 64-bit. The final 32-bit Intel Mac was discontinued in August of 2007; Apple chose a similar four-year cut-off for dropping PowerPC support, with minimal customer backlash. Time marches on.

    But sometimes time marches on a bit too fast. Though this is the second version of Mac OS X that doesn't back PowerPC processors, this is the first version that won't hurry PowerPC applications. In Snow Leopard, the Rosetta translation engine allowed PowerPC applications to run, and hurry well, often faster than they ran on the (admittedly older) PowerPC Macs for which they were developed. Lion no longer includes Rosetta, even as an optional install.

    No one expects eternal back for PowerPC software, and any developer that doesn't yet own Intel-native versions of bar nothing its applications is clearly not particularly dedicated to the Mac platform. Nevertheless, people soundless depend on some PowerPC applications. For example, I own an aged PowerPC version of Photoshop. Though Photoshop has long since gone Intel-native, it's an expensive upgrade for someone dote me who uses the program only rarely. The PowerPC version suits my needs just fine, but it won't hurry at bar nothing in Lion.

    Another common sample is Quicken 2007, soundless the most capable Mac version of Intuit's finance software, and soundless PowerPC-only. This is clearly Intuit's fault, not Apple's, but from a regular user's perspective, it's difficult to understand why Apple would remove an existing, completed feature that helped so many people.

    In reality, every feature has some associated maintenance cost. This is perhaps even more staunch of a binary translation framework that may own deep hooks into the operating system. I'm willing to give Apple the capitalize of the doubt and assume that disentangling PowerPC-related code from the operating system once and for bar nothing was well-known enough to justify the customer inconvenience. But it soundless stings a little.

    The future shock continues with the purchase and installation process. Lion is the first version of Mac OS X to live distributed through Apple's recently introduced Mac App Store. In fact, the Mac App Store is the only plot where you can buy Lion.

    Apple's decision final year to sell its iLife and iWork applications through the Mac App Store was not unexpected, but the presence of Apple's professional photography application, Aperture, caught some people off guard—as did its greatly reduced cost ($80 vs. $200 for the boxed version).

    The developer preview releases of Lion were furthermore distributed through the Mac App Store. Apple's developer releases own been distributed digitally for many years now, but the switch from downloading disk images from Apple's developer website to "redeeming" promo codes and downloading original builds from the Mac App Store raised some eyebrows. When Apple announced that its original Final chop Pro X professional video editing application would—you guessed it—be distributed through the Mac App Store, and at a greatly reduced price, even the most dense Apple watchers started to win the hint.

    The Lion installer application iconThe Lion installer application icon

    And so they own Lion, priced at a mere $29 (the very as its "no original features" predecessor), available exclusively through the Mac App Store. It's an audacious move, yes, but not unexpected.

    Apple is so done with stamping bits onto plastic discs, putting the discs into cardboard boxes, putting those boxes onto trucks, planes, and boats, and shipping them bar nothing over the world to retail stores or to mail-order resellers who will eventually achieve those very boxes onto a different set of trucks, trains, and planes for final delivery to customers, who will then remove the disc, toss away the cardboard, and instruct their computers to extract the bits. No, from here on out, it's digital distribution bar nothing the way. (This, I suppose, marks the conclude of my longstanding tradition of showing the product boxes or optical discs that Mac OS X ships on. Instead, you can behold the installer application icon on the right.)

    Lion is a large download and dote a scintillate network connections are soundless not ubiquitous. But original Macs will approach with Lion, so the most pertinent question is, how many people who aim to upgrade an existing Mac to Lion don't own a dote a scintillate network connection? The class of people who accomplish OS upgrades probably has a higher penetration of high-speed Internet access than the general population. I furthermore suspect that Apple retail stores may live willing to cheer out customers who just can't manage to download a 3.76GB installer in a reasonable amount of time.

    [Update: Macworld reports that there will, in fact, live a physical manifestation of Lion. Starting in August, Apple will sell Lion on a USB stick for $69. Apple has furthermore said that customers are welcome to bring their Macs to Apple retail stores for cheer buying and installing Lion.]

    In the meantime, if you're reading this, chances are satisfactory that you own a dote a scintillate broadband connection; feel free to cease reading privilege now, launch the Mac App Store, and start your multi-gigabyte download before continuing. What you'll live rewarded with at the conclude is an icon in your Applications folder labeled "Install Mac OS X Lion." (See?)

    Once you own the installer application, you could (were you so inclined) dig into it (control-click, then exhibit Package Contents) and find the meaty center, a 3.74GB disk image (InstallESD.dmg, stored in the Contents/SharedSupport folder). You could then utilize that disk image to, say, sear a Lion installation DVD or create an emergency external boot disk.

    I doubt any of these things are officially supported by Apple, but the point is that there's nothing exotic about the Lion installer. dote bar nothing past versions of Mac OS X, Lion has no serial number, no product activation, and no DRM of any kind. In fact, the Mac App Store's licensing policy is even more permissive than past releases of Mac OS X. Here's an excerpt from Lion's license agreement:

    If you obtained a license for the Apple Software from the Mac App Store, then topic to the terms and conditions of this License and as permitted by the Mac App Store Usage Rules set forth in the App Store Terms and Conditions (http://www.apple.com/legal/itunes/ww/) ("Usage Rules"), you are granted a limited, non-transferable, non-exclusive license:

    (i) to download, install, utilize and hurry for personal, non-commercial use, one (1) copy of the Apple Software directly on each Apple-branded computer running Mac OS X Snow Leopard or Mac OS X Snow Leopard Server ("Mac Computer") that you own or control;

    The references to Snow Leopard are a bit confusing, but retain in sarcasm that you exigency Snow Leopard to purchase and download Lion for the first time. I suspect the license agreement will live updated once Lion has been out for a while.

    There's furthermore another entertaining clause in the license, from that very section:

    (iii) to install, utilize and hurry up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software.

    Putting it bar nothing together, Apple says you're allowed to hurry up to three copies of Lion—one real, two inside virtual machines—on every Mac that you own, bar nothing for the low, low cost of $29. Not a indecent deal.

    The installer itself is dead simple, foreshadowing the pervasive simplification in Apple's original OS. There are no optional installs and no customization. The only response the user provides is agreeing to the obligatory EULA, and the only configurable install parameter is the target disk.

    Enlarge

    But wait a second—how exactly is this going to work? Surely an entirely original operating system can't live installed on top of the currently running operating system by an application stored on the very volume. Without a plastic disc to boot from, how is it even viable to upgrade a standalone Mac with just one difficult drive?

    These questions probably won't occur to an unconcerned consumer, which is sort of the point, I guess. sure enough, if you just nearby your eyes, launch the installer application, and click your artery through the handful of screens it presents, your Mac will reboot into what looks dote the measure Mac OS X installer application from years past. When it's done, your Mac will reboot into Lion. Magic!

    Okay, it's not magic, but it is a bit complicated. The first and most lasting amaze is that the Lion installer will actually repartition the disk, carving out a 650MB slice of the disk for its own use.

    Don't worry, bar nothing existing data on the disk will live preserved. (Mac OS X has had the skill to add partitions to existing disks without destroying any data for many years now.) bar nothing that's required is enough free space to reshuffle the data as needed to originate latitude for the original partition.

    Here's an sample from my testing. I started with a unique 250GB difficult drive split into two equal partitions: the first named "Lion Ex," currently running Snow Leopard, and the intended target of the Lion install, and the second named "Timex," the Time Machine backup volume for Lion Ex. The output from the diskutil list command appears below.

    /dev/disk1 #: nature title SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS Lion Ex 125.0 GB disk1s2 3: Apple_HFS Timex 124.6 GB disk1s3

    Now here's that very disk after installing Lion, with the original partition highlighted:

    /dev/disk1 #: nature title SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk1 1: EFI 209.7 MB disk1s1 2: Apple_HFS Lion Ex 124.5 GB disk1s2 3: Apple_Boot Recovery HD 654.6 MB disk1s3 4: Apple_HFS Timex 124.6 GB disk1s4

    The original partition is actually considered a different type: Apple_Boot. The Recovery HD volume won't live automatically mounted upon boot and therefore won't emerge in the Finder. It's not even visible in the Disk Utility application, appearing only as a tiny blank space in the partition map for the disk. But as shown above, the command-line diskutil program can behold it. Diskutil can mount it too.

    Doing so reveals the partition as a classic HFS+ volume. The top smooth contains a directory named com.apple.recovery.boot which in gyrate contains a few tiny files related to booting along with an invisible 430MB internally compressed disk image file named BaseSystem.dmg. Mount that disk image and you find a 1.52GB bootable Mac OS X volume containing Safari, most of the contents of the measure /Applications/Utilities folder (Disk Utility, Startup Disk, Terminal, etc.), plus a Mac OS X Lion installer application. In other words, it looks a lot dote a measure Mac OS X installer DVD.

    A subset of the files copied to the recovery partition is furthermore copied to the installation target disk by the installer and blessed as the original bootable system. This is what the Lion installer reboots into. The files to install will live read from the Lion installer application downloaded earlier from the Mac App Store. After the installation is complete, the temporary boot files are removed, but the Recovery HD partition remains on the disk. Hold down ⌘R during system startup to automatically boot into the Recovery HD partition. (Holding down the option key during startup—not a original feature in Lion—will furthermore exhibit the Recovery HD partition as one of the boot volume choices.)

    Booting from the recovery partition really means mounting and then booting from the BaseSystem.dmg disk image on the recovery partition. Doing so presents a list of the traditional Mac OS X install disc options, including restoring from a Time Machine backup, reinstalling Mac OS X, running Disk Utility, resetting your password, and so on. There's furthermore an option to win cheer online, which will launch Safari. Including Safari on the recovery partition is a nice touch, since most people's first cease when diagnosing a problem is Google, not the Genius Bar.

    The upshot is that after bar nothing the file compression magic added in Snow Leopard to reduce the footprint of the OS, Lion steals over half a gigabyte of your disk space as Part of its installation process, and never gives it back. The partition's title makes Apple's intent clear: it's meant as a last-ditch mechanism to diagnose and repair a Mac with a hosed boot volume. (Hosed, that is, in the software sense; existing as it does on the boot disk itself, the recovery partition won't live much utilize if the disk has hardware problems.)

    Apparently Apple has decided that the skill to boot a Mac into a known-good (software) condition is well worth sacrificing a tiny amount of disk space. MacBook Air owners or other Mac users with diminutive solid-state disk drives may disagree, however. In that case, the disk space can live reclaimed by some judicious repartitioning with Disk Utility (or the diskutil command-line tool) while booted from another disk. But don't live surprised when the fellow at the Genius Bar frowns a Little at your deviation from the Apple Way.

    Reconsidering fundamentals

    The user-visible changes in Lion are legion. You'll live hard-pressed to find any Part of the user interface that remains completely unchanged from Snow Leopard, from the ascertain and feel bar nothing the artery down to basic behaviors dote application and document management. In Lion, Apple has taken a difficult ascertain at the assumptions underlying the final ten years of Mac OS X's development—and has decided that a lot of them exigency to change. win ready.

    Lion's original look

    Let's ease into things with a tour of Lion's revised user interface graphics. Though Apple soundless uses the title "Aqua" to refer to Lion's interface, the ascertain is a far yell from the lickable, candy-coated appearance that launched the brand. If you can imagine three dials labeled "color," "contrast," and "contour," Apple has been turning them down slowly for years. Lion accelerates that process.

    The shapes own started to change, too. The traditional capsule shape of the measure button has given artery to a squared-off, Chiclets-style appearance. The tubular shape of the progress bars, a fixture since even before the dawn of Mac OS X, has been replaced with a vaguely puffy stripe of material. Radio buttons, checkboxes, slider thumbs, segmented controls, "tab" controls—nearly everything that used to protrude from the screen now looks as if it was pounded down with a rubber hammer.

    Finder sidebar: grayFinder sidebar: gray

    Even the elements that ascertain identical, dote the unpretentious gray window title bars, are slightly different from their Snow Leopard counterparts. The original ascertain is not a radical departure—everything hasn't gone jet black and grown fur, for example—but this is the first time that nearly every factor of the measure GUI has been changed in a artery that's identifiable without a color meter or a magnifying glass.

    For the most part, the original ascertain speaks in a softer voice than its predecessor. The total removal of blue highlights from several controls (e.g., pop-up menus, combo boxes, slider thumbs, and tab controls) makes most interfaces emerge slightly less garish. On the other hand, the additional green in the blue highlights that soundless finish exist makes those controls emerge more saccharine.

    Apple says that its goal with the Lion user interface was to highlight content by de-emphasizing the surrounding user interface elements. You can behold this most clearly in sidebar and toolbar icons, which are now monochromatic in most of the well-known bundled applications. But this has the hapless side result of making interface elements less distinguishable from each other, especially at the tiny sizes typical in sidebars. I'm not sure the "increased emphasis on content" is enough to equilibrium out the loss, especially in applications dote the Finder.

    LionLion Snow LeopardSnow Leopard

    Appearance changes can own effects beyond emphasis, fashion, and mood. prefer the "traffic light" red, yellow, and green window widgets, for example. As you can behold in the images on the right, they've gotten smaller in Lion. Or rather, the colored portion has gotten smaller; the actual clickable district has lost only one pixel in height and five pixels in total width across bar nothing three widgets.

    But the psychological result of the shrunken appearance is something else entirely. Despite the tiny incompatibility in the functional size, I find myself being ever-so-slightly more observant when targeting these widgets in Lion. It's a Little annoying, especially since it's not limpid to me how the new, smaller size fits into Lion's original look. Does such a tiny reduction in size really serve to better emphasize window content? After all, nothing of the other controls own gotten any smaller.

    Other aspects of the original ascertain own clearer intentions. The flatter, more matte ascertain of most controls, and especially the squared-off shape of the measure button, bar nothing bring to sarcasm the ascertain of Apple's other operating system, iOS. One control in particular takes the iOS connection even further.

    Finally, there's Apple's budding treasure affair with a particular linen texture. It made its first appearance on the backside of some Dashboard widgets. More recently, it was used as the background pattern for the notifications sheet in iOS 5. In Lion, it's featured even more prominently as the background for the newly restyled login screen, now featuring circular frames for user icons. (Also note the subset of menu bar status icons soundless visible in the top-right corner of the screen.)

    Linen for your login screen Enlarge / Linen for your login screen Scroll bars

    Scroll bars, which Apple likes to convoke "scrollers" these days, are among the least-changed interface elements in Mac OS X. While the repose of the Aqua interface was refined—edges sharpened, pinstripes removed, shines flattened—scrollbars stubbornly retained their original Aqua ascertain for over a decade.

    A scroll bar from Mac OS X DP3, released in 2000A scroll bar from Mac OS X DP3, released in 2000 A scroll bar from Mac OS X 10.6, released in 2009A scroll bar from Mac OS X 10.6, released in 2009

    Scroll bars haven't been entirely static in Mac OS X, however. For many years, iTunes has had its own custom scroll bar look.

    A scroll bar from iTunes 10.2.2, released in 2011A scroll bar from iTunes 10.2.2, released in 2011

    When these original scroll bars were first introduced in iTunes 7 in 2006, there was some speculation that this was a trial hurry for a original ascertain that would soon spread throughout the OS. That didn't happen. But now, five years later, scroll bars are finally changing system-wide in Mac OS X. Here's a scroll bar from Lion:

    A scroll bar from Mac OS X 10.7 LionA scroll bar from Mac OS X 10.7 Lion

    The smeared gradient and fuzzy edges of the iTunes scroll thumb are nowhere to live seen. Instead, they own a narrow, monochrome, sharp-edged lozenge. Just dote the window widgets, the scroll thumb appears slightly smaller than its Snow Leopard counterpart. (In this case, total scroll bar width and the clickable district are actually the very as in Snow Leopard.)

    The change in appearance might distract you from what's really different: where are the scroll arrows? You know, the Little buttons on either conclude of the scroll bar (or grouped together on one end) that you click to bound the scroll thumb a bit at a time? Well, they're gone.

    But wait, there's more. Here's a Finder window.

    The complete contents of Lion's Applications folder…or is it?The complete contents of Lion's Applications folder…or is it?

    Though I can assure you that Lion comes with more than eight applications, you wouldn't know it from looking at this screenshot. Forget about the arrows, where are the scroll bars?

    Placing the cursor into the window and using the scroll wheel on the mouse or two-finger scrolling on a trackpad reveals what you might own already guessed based on the shape and appearance of the original scroll thumbs. Extremely thin, monochrome scroll thumbs fade in as the scrolling begins, and evanesce shortly after it ends. These transient scroll thumbs emerge on top of the window's content, not in alleys reserved for them on the edges of the window.

    Initiating scrolling (via mouse wheel or trackpad) reveals overlay scroll bars. More applications below!Initiating scrolling (via mouse wheel or trackpad) reveals overlay scroll bars. More applications below! An iOS scroll barAn iOS scroll bar

    These ghostly overlay scroll bars are straight out of iOS. When they were introduced in 2007 on the iPhone's 3.5-inch screen, they made consummate sense. Dedicating one or more finger-width strips of the screen for always-visible, touch-draggable scroll bars would own been a colossal squander of pixels (and anything less than a finger's width of pixels would own been too narrow to comfortably use). Overlay scroll bars were essential in iOS, and completely in keeping with its direct manipulation theme. In iOS, you don't manipulate an on-screen control to scroll, you simply grab the all screen with your finger and bound it.

    Apple isn't (yet) asking us to start poking their fingers at their Mac's screen, but it does now ship every Mac with some kindly of touch-based input device: internal trackpads on laptops, and external trackpads or touch-sensitive mice on desktops. Lion further cements the dominance of paw by making bar nothing touch-based scrolling travail dote it does on a touchscreen. Touching your finger to a control surface and stirring it downwards will bound the document downwards, revealing more content at top and hiding some of the content that was previously visible on the bottom. This sounds perfectly logical, but it furthermore happens to live exactly the opposite how scrolling has traditionally worked with mouse scroll wheels. The result is extremely disconcerting, as their fingers unconsciously flick at the scroll-wheel while their eyes behold the document stirring the "wrong" way.

    Scroll direction setting in the Mouse preference pane. Checked means the  original Lion scrolling direction is in effect.Scroll direction setting in the Mouse preference pane. Checked means the original Lion scrolling direction is in effect.

    Thankfully, there is a preference to restore the aged mapping of finger movement to scroll direction. There's a second setting in the Trackpad preference pane, phrased in the opposite way. Unfortunately, the settings are linked; you can't own different values for each kindly of input device.

    Though the unification of scrolling gestures is logical, it's difficult to win used to after so many years of doing things the other way. The most common scrolling direction is downwards, and the most natural finger movement is curling inwards. These two things align when using a mouse wheel with the "old" scrolling direction setting. aged habits aside, it may live that the incompatibility between touching a screen directly and touching a sever device on a horizontal surface in front of the screen is just too much to justify a unique input vocabulary.

    Either way, there's sure to live an uncomfortable transition period for everyone. For example, the two-finger swipe to the left or privilege used to switch between screens in Launchpad (described later) feels "backwards" when the scroll direction preference is set to the traditional, pre-Lion behavior. Perhaps just seeing a screen covered with a grid of icons unconsciously triggers the "iOS expectations" region of their brains. (And if you set the scroll direction to "feel right" for two-finger swiping in Launchpad, then the four-finger swipe between Spaces feels backwards! Sigh.)

    Scroll bars finish more than just let us scroll. First, their condition tells us whether there's anything more to see. A window with "inactive" (usually shown as dimmed) scroll bars indicates that there is no content beyond what is currently visible in the window. Second, when a document has more content than can meet in a window, the scroll bars divulge us their current position within that document. Finally, the size of the scroll thumb itself—or the amount of latitude the scroll thumb has to bound within the scroll bar, if you want to ascertain at it that way—gives some hint about the total size of the content.

    Classic Mac scroll barsClassic Mac scroll bars

    Most computer users aren't conscious of such subtleties, but their combined effects are profound. Long-time Mac users might recollect a time when scroll thumbs were perfectly square regardless of the total size of a window's content. When I consider back to my time using those scroll bars, I don't recall any problems. But just try using these so-called "non-proportional" scroll bars today. The modern computer user's sarcasm revolts at the exigency of information, usually treating it instead as misleading information about the total size of a window's content. ("This window looked dote it had pages and pages of content, but when I dragged the tiny square scroll thumb bar nothing the artery from the top to the bottom, it only revealed two original lines of text!") Only when this cue is gone finish you realize how much you've been relying on it.

    And retain in sarcasm that proportional scroll thumbs are the most subtle of the cues that scroll bars provide. The others are even more widely relied upon. The complete exigency of visible scroll bars leaves a huge information void.

    Let's achieve aside the close for a moment. In the absence of scroll bars, are there other visual cues that could provide the very information? Well, if truncated content appears at the edge of a window, it's usually a safe stake that there's more content in that direction. The prevalence of whitespace (between icons in the Finder, between lines of text, etc.) can originate such truncation less obvious or even undetectable, but at least it's something. For total content size and position within the document, there's no alternative even that good.

    But alert not, gentle scroller. dote the scroll direction, scroll bar visibility has a dedicated preference (in the general preference pane):

    Scroll bar settings in the general preference paneScroll bar settings in the general preference pane

    The default setting, "Automatically based on input type," will utilize overlay scroll bars as long as there's at least one touch-capable input device attached (though the trackpad on laptops doesn't count if any other external pointing devices are connected). If you don't dote this kindly of second-guessing, just pick one of the other options. The "When scrolling" option means always utilize overlay scroll bars, and the "Always" option means always exhibit scroll bars, using the appearance shown earlier.

    Lion includes original APIs for briefly "flashing" the overlay scroll bars (i.e., showing them, then fading them out). Most applications included with Lion briefly exhibit the scroll bars for windows that own just appeared on the screen, own just been resized, or own just scrolled to a original position (e.g., when showing the next match while searching within a document). This helps soften the blow of the missing information previously provided by always-visible scroll bars, but only a little.

    Extra UI in the scroll bar areaExtra UI in the scroll bar area

    Applications with other UI elements whose amend placement relies on the being of a reserved 16-pixel stripe for the scroll bar outside the content district of the window may live forced to panoply what Apple calls "legacy" scroll bars. (Apple's term for non-overlay scroll bars tells you bar nothing you exigency to know about which artery the wind is blowing on this issue.) You can behold an sample of one such UI factor in the image on the right. The document scale pop-up menu (currently showing "100%") pushes the horizontal scroll bar to the left to originate latitude for itself. Clearly, this will not travail if the scroll bar overlays the content district and is hidden most of the time. Apple suggests that such applications find original homes for these interface elements, at which point the AppKit framework in Lion will allow them to panoply overlay scroll bars.

    Lion's scroll bars are a microcosm of Apple's original philosophy for Mac OS X. This is definitely a case of reconsidering a fundamental Part of the operating system—one that hasn't changed this radically in decades, if ever. It's furthermore nearly a straight port from iOS, which is in keeping with Apple's professed "back to the Mac" mission. But most importantly, it's a concrete sample of Apple's newfound dedication to simplicity.

    In particular, this change reveals the tremendous weight that Apple gives to visual simplicity. A complete exigency of visible scroll bars certainly does originate the unconcerned Mac OS X screen ascertain a lot less busy. A exigency of visual clutter has been a hallmark of Apple's hardware and software design for years, and iOS has only accelerated this theme. Also, practically speaking, the sum of bar nothing those 16-pixel-wide stripes reserved for scroll bars on window edges may add up to a nontrivial multiply in the number of pixels available for displaying content on a Mac's screen.

    But there is a cost to live paid for this simplicity; one person's hullabaloo is another person's essential source of information. Visual information, dote the size and position of a scroll thumb, is one of the most efficient ways to communicate with humans. (Compare with, say, numeric readouts showing document dimensions and the current position as a percentage.)

    These sacrifices were an essential Part of the iPhone's success. The iPad, though larger, is clearly Part of the very touch-based family of products, and is wisely built on the very foundation. But the Mac is a different kettle of fish—and not just because the screen sizes involved may live vastly larger, making the space savings of hidden scroll bars much less important.

    The Mac user interface, with its menus, radio buttons, checkboxes, windows, title bars, and yes, scroll bars, is built on an entirely different interactivity model than iOS. The Mac UI was built for a pixel-accurate indirect pointing device; iOS was built for direct manipulation with one or more fingers. The visual similarity of on-screen elements and the technical feasibility of porting them from one OS to the other should not blind us to these essential differences.

    It's entertaining that bar nothing of the scrolling changes in Lion own preferences that allow them to live reverted to their pre-Lion behaviors. The defaults clearly betoken the direction that Apple wants to go, but the settings to reverse them—public, with existent GUIs, rather than undocumented plist hacks—suggest caution, or perhaps even some internal strife surrounding these features.

    Such caution is well-founded. Hidden scroll bars in particular own trade-offs that change dramatically based on the size of the screen and the input device being used. dote many features in Lion, the scrolling changes are most useful and usurp on the Macs that are closest to iOS devices in terms of size and input method (the 11-inch MacBook Air being the best example). But on a Mac Pro with dual 27" 2560x1440-pixel displays attached, Lion's scrolling defaults originate far less sense.

    Window resizing Resize widgetResize widget

    A exigency of traditional scroll bars furthermore means the elimination of the tiny patch of pixels in the lower-right corner of a window where the vertical and horizontal scroll bars meet. Since 1984, this district has been home to the one and only control used to resize a window. Setting the scroll bar appearance preference to "always visible" restores the clickable existent estate, albeit sans the traditional "grip lines."

    Despite the unpretentious appearance, this resize control works as expected; what's unexpected is the cursor change that accompanies the action. The double-arrow cursor has been used in other operating systems for years, mostly to differentiate two-axis resizing (width and height) from single-axis resizing (height only or width only). When there's only one resize control per window, it's obvious that it can live used to change both the width and the height. Lion's original cursor can stand for only one thing…

    Window resizing from  bar  nothing edges (composite image)Window resizing from bar nothing edges (composite image)

    That's right, long-suffering switchers, Lion finally allows windows to live resized from any edge and from bar nothing four corners, with a special cursor for each of the eight starting points. (When a window is at its size limit, the cursors exhibit an arrow pointing in a unique direction—a nice touch.)

    As you can behold from the image above, what Apple hasn't done is add borders to the windows. So where, exactly, finish they "grab" when resizing from a borderless window edge? There's no artery around it: some pixels must live sacrificed to the gods of Fitts's law.

    A few pixels within the outer edge of the content district of the window (two to three, depending on where you count from) are commandeered for window resizing purposes. You can soundless click on these areas, and the click event will correctly propagate to the application that owns the window, but you'll live clicking with a resize cursor instead of a classic arrow cursor.

    Two to three pixels doesn't originate for a very wide target, however, which is why Apple has chosen to usurp pixels from both sides of the window border. Four to five pixels outside the content district of the window are furthermore clickable for window resizing purposes. Clicks in these areas don't win sent to the window (they're out of the window's bounds) and they don't win sent to whatever happens to live behind the vigorous window—you know, the thing that you ostensibly just clicked on. Effectively, Lion windows own thin, invisible borders around them used only for resizing. (Unlike Mac OS 8 and 9 windows, which had real, visible borders, Lion windows can't live dragged by their borders.)

    When overlay scroll bars are in use, the full 16x16 pixel home of the traditional resize widget in the lower-right corner is clickable, making this soundless the easiest target for window resizing, whether it's visible or not.

    Unzoom widgetUnzoom widget Zoom widgetZoom widget

    Lion has a few more surprises on window edges, one of which is window size-related. Windows belonging to applications that back Lion's original full-screen mode may exhibit an embossed double arrow icon on the far-right side of their title bars. Clicking it will cause the window to fill the entire screen. Other windows, the Dock, and even the menu bar are hidden in this mode. The window's title bar furthermore disappears, making it unclear how to exit this mode. But just stab the cursor at the top of the screen and the menu bar slides back down into view, containing bar nothing the expected menus plus a reversed version of the double arrow symbol. Click the inward-facing arrows to prefer the current window out of full-screen mode.

    Animation

    Mac OS X has always used animation in its user interface, starting with the genie result over a decade ago, and really ramping up with the introduction of the Core Animation framework three years ago. Lion continues this trend. In nearly bar nothing original or changed applications in Lion, if something conceivable can live animated, it is. The Finder is a satisfactory example. Even features whose functionality hasn't actually changed in Lion, such as dragging multiple items from one window to another, are given a fresh coating of animation and fades.

    At its best, animation explicitly communicates information that was either absent or only implied before. For example, the genie animation tells the user where a window goes when it's minimized. In other cases, such as the water ripple result in Dashboard, animation can add a bit of fun to an interface.

    But danger lurks. A newly discovered animation might delight the user the first time it's shown, but the 350th time might not look quite so magical. This is especially staunch if the animation adds a detain to the task, and if that job is done frequently as Part of a time-sensitive overall task. The Dashboard water ripple is acceptable because adding a original widget to the screen is an infrequent task. But if the screen rippled every unique time a original window appeared anywhere in the OS, users would revolt.

    Well, guess what happens every time a original window appears on the screen in Lion? No, it's nothing as garish as a water ripple, but there is an animation. Each window starts as a tiny dot centered on the window's eventual position on the screen, then quickly animates to its full size.

    This animation conveys no original information. It does not divulge the user where a window came from, since the animation starts at the final position of the window. Whether or not the animation actually delays the opening of the window, it certainly feels dote it does, which is even more important. This nature of animation can originate Lion feel slower than Snow Leopard. And when an animation dote this stutters or skips a few frames due to massive disk i/o or CPU usage, it makes your all Mac feel slower, dote you're playing a 3D game with an inadequate video card. And for what? For what someone at Apple hopes will live a lasting passion of delight?

    Perhaps it could live argued that the animation catches the eye more than a window that appears instantly (though that probably depends on the size of the window and what's behind it on the screen). For "unexpected" windows dote error dialog boxes, that could live a benefit. But for "expected" windows (i.e., those that emerge in response to deliberate user input), the powerful, primordial tug of these stirring images is an unwelcome distraction, not a benefit.

    It's conceivable that this animation could delight some users, but I own a difficult time believing that the enjoyment will final much past the first week. (Interestingly, this animation does not play in reverse when a window is closed. This, perversely, makes window closing feel faster than window opening in Lion.)

    Unlike the scrolling behaviors discussed earlier, there are no user-visible preferences for these original animations, which makes it bar nothing the more well-known for Apple to strike a satisfactory balance. In my estimation, Lion crosses the line in a few places; the original window animation is the most egregious example. I ascertain forward to discovering a artery to disable it. [Update: here it is: defaults write NSGlobalDomain NSAutomaticWindowAnimationsEnabled -bool NO]

    Here's to the crazy ones

    Bruce Tognazzini, founder of the Apple Human Interface Group and 14-year Apple veteran (1978-1992), is best known as the man behind the publication of the Apple Human Interface Guidelines. In 1992, he published a book of his own: Tog on Interface. Most of the examples in the book were taken from his travail at Apple. Here's an excerpt from pages 156-157:

    Natural objects own different perceivable characteristics, among which people can easily discriminate. prefer the bristlecone pine. The oldest alive thing on earth, it has been formed and shaped by the wind and scarred by thousands of years of existence. The youngest school kids ascertain at it and know there must live a lot of wind around there. They know the pine may live even older than their father. They furthermore know, to a certainty, that it is a tree.

    Hypercard "Home" iconsHypercard "Home" icons

    Kristee Kreitman Rosendahl, answerable for not only the graphic design of HyperCard, but furthermore much of its spirit, created a collection of Home icons that shipped with the product.

    No one has ever shown confusion at seeing various Little houses on various cards. Never once has someone turned around and said, "Gee, this Little house has three windows and seems to live a Cape Cod. Will that prefer me to a different Home card than that two-story bunk house back in the other section?" People are designed to manipulate multiplexed meanings gracefully, without conscious thought.

    In System 7, they multiplexed the import of system extensions, by developing a characteristic "generic" extension look, to which developers can add their own unique ascertain for their specific product. As the "bandwidth" of the interface increases, these kinds of multiplexings will become more and more practical.

    System 7 extension iconsSystem 7 extension icons

    This is Tog, godfather of the old-school Apple Human Interface Guidelines, stating emphatically that interface elements finish not own to ascertain exactly the very in order for their function to live discerned. In fact, in the final sentence, Tog predicts that increased computing power will lead to more diverse representations. The increased "bandwidth" of user interfaces that Tog wrote about almost 20 years ago has now approach to pass, and then some.

    Examples of "multiplexed meanings" in Mac OS X are not difficult to find. ascertain at the Dock, which has changed appearance several times during the history of Mac OS X while soundless remaining immediately identifiable. And, as discussed earlier, nearly every measure GUI control has changed its appearance in Lion. As Tog notes, people are excellent at discarding unimportant details and focusing on the most salient aspects of an item's appearance.

    Now, keeping bar nothing this in mind, I invite you to gaze upon this screenshot of the version of iCal that ships with Lion.

    A stitch in time saves…something, presumably

    Enlarge / A stitch in time saves…something, presumably

    When this change was first revealed in the second developer preview of Lion, there was much gnashing of teeth. But hope yourself, is the function of every control in the toolbar clear? Or rather, is it any less limpid than it would live if iCal used the measure Mac OS X toolbar appearance?

    The immediate, visceral negative reaction to the loaded Corinthian leather appearance had Little to finish with usability. What it came down to—what first impressions dote these always look to approach down to—is whether or not you consider it's ugly. People will prefer "really cool-looking but slightly harder to use" over "usable but ugly" any day.

    But there's something much more well-known than the change in appearance going on here. Lion's iCal doesn't ascertain different in an capricious way; it's been changed with purpose. After the initial stitched-leather shock wore off, Apple watchers everywhere leapt on the original iCal's deeper sin: its skeuomorphic design. From Wikipedia (emphasis added):

    A skeuomorph is a derivative object that retains ornamental design cues to a structure that was necessary in the original. Skeuomorphs may live deliberately employed to originate the original ascertain comfortably aged and familiar, such as copper cladding on zinc pennies or computer printed postage with circular town title and cancellation lines. An alternative definition is "an factor of design or structure that serves Little or no purpose in the artifact fashioned from the original material but was essential to the object made from the original material."

    Apple has been down this road before, most notably with the QuickTime 4.0 player application which included gleaming ideas dote a "dial" control for adjusting the volume. Dials travail much in the real, physical world, and are certainly close to most people. But a dial control in the context of a 2D mouse-driven GUI is incongruous and awkward at best, and completely incomprehensible at worst.

    The brushed metal appearance of the QuickTime player would later inspire an officially supported Mac OS X window appearance starting in version 10.2, only to live dropped completely five years later in 10.5's grand interface unification. Now, three years after that, the pendulum is swinging in the other direction again—and hard.

    In the case of iCal, Apple has aped the appearance of an analogous physical object (a tear-off paper calendar) but retained the conduct of measure Mac OS X controls. This avoids the problems of the QuickTime 4.0 player's dial control, but it's far from a clean win.

    The pains is, the original iCal looks so much dote a close physical object that it's easy to start expecting it to behave dote one as well. For example, iCal tries very difficult to sell the tear-off paper calendar illusion, with the stitched binding, the tiny remains of already-removed sheets, and even a page curl animation when advancing through the months. But can you grab the corner of a page with your mouse and tear it off? Nope, you own to utilize the arrow buttons or a keyboard command, just dote in the previous version of iCal. Can you scribble in the margins? Can you cross off days with a pen? Can you riffle through the pages? No, no, and no.

    At the very time, iCal is soundless constrained by some of the limitations of its physical counterpart. A paper calendar must pick a unique artery to crash up the days in the year. Usually, each page contains a month, but there's no reason for a virtual calendar to live limited in the very way. When dealing with events that span months, it's much more convenient to view time as a continuous stream of weeks or days. This is especially staunch on large desktop monitors, where zooming the iCal window to full screen doesn't exhibit any more days but just makes the days in the current month larger.

    The original version of Address book in Lion is an even more egregious example.

    These graphics are writing checks this interface can't cash Enlarge / These graphics are writing checks this interface can't cash

    Address book goes so far in the direction of imitating a physical analog that it starts to impair the identification of measure controls. The window widgets, for example, are so integrated into the design that they're easy to overlook. And as in iCal, the unbelievable detail of the appearance implies functionality that doesn't exist. Pages can't live turned by dragging, and even if they could, the number of pages on either side of the spine never changes. The window can't live closed dote a book, either. That red bookmark can't live pulled up or down or removed. (Clicking it actually turns the page backwards to betray the list of groups. Did you guess that?) The three-pane view (groups → people → detail) is gone, presumably because a book can't exhibit three pages at once. Within each paper "page" sits, essentially, an excerpt from the user interface of the previous version of Address Book. It's a mixed metaphor that sends mixed signals.

    These newly redesigned Mac OS X applications are clearly inspired by their iOS counterparts, which endure similar graphical flourishes and skeuomorphic design elements. (Address book in particular is a dead ringer for the Contacts app on the iPad.) In iOS, the inability to gyrate pages with the flick of a finger or yank out that tantalizing red bookmark is even more frustrating. In both environments, when the behaviors seemingly promised by the graphical design aren't delivered, bar nothing this artwork that was so clearly labored over fades into the background. The application trains us to ignore it. What was once, at best, a momentary amusement is reduced to visual noise.

    In 2011, we're far past the point where computer interfaces exigency to reference their forebearers in the physical world in order to live understandable (though it's viable Apple thinks the familiarity of such designs is soundless an effective artery to reduce intimidation, especially for novice users). At the very time, hardware and software own advanced to the point where there's now ample "bandwidth" (to utilize Tog's term) to back visual and functional nuances beyond the bare necessities.

    Interface designers are faced with the challenge of how best to utilize the glut of resources now at their disposal. As Lion's iCal and Address book applications demonstrate, an alternate description of this situation might live "enough rope to hang yourself."

    Window management

    Over the years, Apple has added several features that could loosely live defined as "window management aids." The first, and arguably most successful, was Exposé, introduced in Panther back in 2003. Two years later, Tiger shipped with Dashboard, which provided a dedicated screen for tiny "widget" windows, keeping them off the main screen. In 2007, Leopard brought official back for virtual desktops to Mac OS X under the title Spaces.

    Each of these features came with its own set of configurable keyboard shortcuts, burning screen corners, and (eventually) multi-touch gestures. While each was understandable and useful in isolation, it was up to each user to motif out how best to incorporate them into a workflow. In Lion, Apple has taken a stab at consolidation under the umbrella title of Mission Control. Each individual feature soundless exists, albeit in slightly more limited forms, but activating one thing now provides access to them all.

    Using any one of the supported Mission Control activation methods—a keyboard shortcut, a burning screen corner, or a four-finger upwards swipe—causes the current desktop picture to retreat slightly into the seat of the screen, revealing behind it their aged friend the linen pattern. Overlaid on this are groups of windows, badged by the icons of the applications to which they belong. Along the top of the screen sit bar nothing open Spaces. (In Lion, each full-screen window creates a original Space, so those windows emerge at the top rather than grouped with the other windows from the very application.) Dashboard is furthermore (optionally) given its own Space.

    Mission Control: Exposé + Spaces + Dashboard Enlarge / Mission Control: Exposé + Spaces + Dashboard

    A surprising number of things can live done from this screen. As with Exposé, clicking on any window will bring it to the front. Windows can furthermore live dragged into any of the available Spaces (excluding Dashboard and those that contain a unique full-screen window). stirring the cursor (or dragging a window) to the upper-right corner of the screen causes a panel with a "+" character to appear; clicking this creates a original space. Holding down the option key makes Dashboard-style "close" widgets emerge on any non-fullscreen-window Spaces (except the original Desktop Space, which can never live closed).

    The biggest limitation of this original arrangement is that Spaces are now confined to a one-dimensional line of virtual desktops. Four-finger swiping between spaces feels great, but there's no wrap-around when you hit the end.

    As tremendous a step down as this is from the much more elastic grid arrangement of Spaces in earlier versions of Mac OS X, the original limitations are probably a satisfactory idea. The original conduct of full-screen windows and the surprisingly natural-feeling four-finger swipes used to switch between them and enter Mission Control means that many more Mac users will likely find themselves using these original features than ever used the combination of Exposé and Spaces in earlier versions of the OS. A simple line of spaces with no wrap-around provides a safe, understandable environment for bar nothing these original Spaces users.

    For the experts, well, consolidation always has its price. In this case, as in many others, Apple has decided that the satisfactory of the many outweighs the satisfactory of the few.

    Application management

    For bar nothing its warts, the radical simplification of application management brought to Mac OS X by the Dock really has benefitted the platform. As I wrote in my ten year Mac OS X retrospective, "For every user who continues to live frustrated by the Dock's limitations, there are thousands of others who are buoyed in their computing efforts by its reassuring simplicity and undemanding design."

    But the Dock falls short, especially for novice users, as an application launcher. Or rather, it falls short if the application to live launched isn't actually in the Dock. Most novice users I know want to own every application they are likely to utilize available in the Dock at bar nothing times. As these users gain experience, the Dock can become a very crowded place. But why are these increasingly Mac-savvy users stuffing their Docks to the gills rather than limiting its contents to just the applications they utilize most frequently?

    The retort lies in how applications not in the Dock are located and launched. Choices comprise the Finder, Spotlight, or (I suppose) a Terminal window. stirring from an always-visible line of colorful icons that's front and seat on the screen to any one of those alternatives represents a huge multiply in conceptual and mechanical complexity.

    If you don't understand how typing the title of an application into a search box can live so much more difficult than clicking an icon in the Dock, I suggest that you own not spent enough time with novice users. Such users often don't even know the title of the application they want—or if they do, they don't know how to spell it. That's before considering the frequent disorientation caused by the rapid-fire search results refinement animation in the Spotlight menu, or the being of multiple files whose contents or names contain the string being searched for. And this bar nothing assumes novices know (or remember) what Spotlight is and how to activate it in the first place.

    The jump in complexity from the Dock to the Finder, I think, needs less explanation. As a general rule, novice users just don't understand the file system. They don't understand the hierarchy of machines, devices, and volumes; they don't grasp the concept of the current working directory; they don't know how to identify a file or folder's position within the hierarchy. alert of the file system practically defines novice users; it is usually the final and biggest hurdle in the journey from timid experimentation to basic technical competence.

    To achieve it another way, your dad can't find it if it's not in the Dock. (Well, my dad can't, anyway. Sorry to bar nothing the Mac-savvy dads out there; I am one, after all.)

    In Lion, Apple aims to fill that gap with an application launching interface that's meant to live as easy to utilize as the Dock while providing access to every application on the system. It's called Launchpad, and you'll live forgiven for thinking that it looks dote yet another interface factor shamelessly ported from iOS.

    Launchpad: iOS’s SpringBoard on your Mac Enlarge / Launchpad: iOS’s SpringBoard on your Mac

    Launchpad can live activated with a Dock icon (which, importantly, is in the Lion Dock by default), a multitouch gesture (a not much awkward pinch with the thumb and three fingers), or by dragging the mouse cursor to a designated corner of the screen. The grid of application icons that appears doesn't just ascertain dote iOS's SpringBoard, it furthermore behaves dote it, privilege down to the "folders" created by dragging icons on top of each other.

    Holding down the option key makes bar nothing the icons sprout nearby widgets as they start to wiggle. Swiping privilege and left on the touchpad or with a click and drag of the mouse will bound from screen to screen, accompanied by a close iOS-like dotted page indicator.

    Launchpad “folders” Enlarge / Launchpad “folders”

    Launchpad will find applications in the measure /Applications folder as well as ~/Applications (i.e., a folder named "Applications" in your home directory), and any subfolders within them. Applications in the ~/Downloads folder or on the desktop are not detected, which may actually live a problem for Mac users who own not yet figured out how to accomplish drag-and-drop application installations—yet another district where the Mac App Store will cheer originate things simpler.

    Mac App Store download progressMac App Store download progress

    Speaking of which, when purchasing an application in the version of the Mac App Store that ships with Lion, the application icon leaps out of the Mac App Store window and lands in the next available position in the Launchpad grid, with an iOS-like progress bar overlaid on the original application's icon. If the Launchpad icon is in the Dock, it displays a similar progress bar and the icon bounces once when the download finishes.

    Both serve as examples of animation that conveys useful information. "Here's where the application you just purchased has 'landed' on your Mac," the animation says. "To find it again, click the icon that just bounced in your Dock."

    Given the wealth of excellent third-party application launchers available for the Mac, I'm not sure there's any reason for an expert user to utilize Launchpad instead of their current favorite alternative. But unlike, say, the Dock, Launchpad is easily ignored. gyrate off the gesture, deactivate the burning corner, and remove the icon from the Dock and you'll never own to behold it.

    For everyone else, however, Launchpad will provide a huge improvement in usability. Even expert users should live excited about its arrival because it should originate telephone or e-mail-based family technical back a bit easier.

    Document model

    Lion introduces what Apple calls, with characteristic conviction, a "modernized" document model. I'm inclined to harmonize with this word choice. dote so many other aspects of Lion, document management is attempting to shed its legacy baggage—and there's plenty to shed. The conventions governing the interaction between users, applications, and documents own not changed much since the personal computer became well-liked in the early 1980s.

    Apple first attempted a minor revolution in this district with OpenDoc in the 1990s. Instead of launching an application in order to create a document, OpenDoc promised a world where the user would open a document and then travail on it using an interchangeable set of components created by multiple vendors. In other words, OpenDoc was document-centric rather than application-centric.

    The changes in OpenDoc promised to radically shift the equilibrium of power in the application software market. But powerful software companies dote Microsoft and Adobe were not particularly motivated to crash their popular, full-featured applications into smaller components that customers could merge and match with components from other vendors. At the time OpenDoc was released, Apple was nearing the nadir of its popularity and influence in the industry. Predictably, OpenDoc died on the vine.

    Fast-forward to today, where a much more powerful and confident Apple takes another crack at the very area. The most pressing problem, today's Apple has decided, is not the interaction between application code and document data, but rather the interaction between the user and the computer.

    Despite decades of public exposure to personal computers, human expectations and habits own stubbornly refused to align with the traditional model of creating, opening, and saving documents. The tales of woe own become clichés:

  • The student who writes for an hour without saving and loses everything when the application crashes.
  • The businessman who accidentally saves over the "good" version of a document, then takes it upon himself to independently reinvent version control—poorly—by compulsively saving each original revision of every document under slightly different names.
  • The Mac power user who reflexively selects the "Don't Save" button for one document after another when quitting an application with many open windows, only to accidentally lose the one document that actually had well-known changes.
  • The father who swears he saved the well-known document, but can't, for the life of him, recollect where it is or what he called it.
  • At this point, they can no longer convoke this a problem of education. We've tried education for years upon years; children own been born and grown to adulthood in the PC era. And yet even the geekiest among us own lost data, time, or both due to a "stupid" mistake related to creating, opening, and saving documents.

    And so Apple's decree in Lion is as it was on the original Macintosh in 1984, and as it is on iOS today: the machine must serve the human, not the other artery around. To that end, Apple has added APIs in Lion that, when used properly, enable the following experience.

  • The user does not own to recollect to reclaim documents. bar nothing travail is automatically saved.
  • Closing a document or quitting an application does not require the user to originate decisions about unsaved changes.
  • The user does not own to recollect to reclaim document changes before causing the document's file to live read by another application (e.g., attaching an open document with unsaved changes to an e-mail).
  • Quitting an application, logging out, or restarting the computer does not stand for that bar nothing open documents and windows own to live manually re-opened next time.
  • Earlier versions of Mac OS X supported a form of automatic saving. If you had an open TextEdit document with unsaved changes, TextEdit would (eventually) reclaim a backup copy of the file with the text " (Autosaved)" appended to the file name. If the application crashed or the Mac lost power, you could retrieve (some of) your unsaved changes by finding the autosaved file and opening it.

    Lion introduces a variant of this practice: autosave in place. Rather than creating a original file alongside the original, Lion continuously saves changes directly to the open document. It does this when there are large document changes, during idle times, or on claim in response to requests from other applications for access to the document's data.

    For bar nothing of this to work, applications must live updated to utilize the original APIs. In particular, a original File Coordination framework must live used in order for an application to notify another that it wants to access a document that's currently open. The application that has the document open will then trigger an autosave to disk before allowing the requesting application to reference the document's data. Attaching a document to an e-mail or using Quick ascertain in the Finder are two examples of when this might happen.

    At this point, a Little bit of "geek panic" might live setting in. For those of us who understand the pre-Lion document model and own been using it for decades, the conception that they are no longer in control of when changes to open documents are saved to disk seems insane! What if I accidentally delete a huge swath of text from a document and then Lion decides to autosave immediately afterwards?

    Not every change is meant to live saved, after all. The practice of speculatively making radical changes to a document with the solace of knowing that nothing of those changes are permanent until they hit ⌘S is something experienced Mac users prefer for granted and may live loath to give up.

    The artist formerly known as “Save”The artist formerly known as “Save”

    I confess, I omitted one particular from the list of changes enabled by Lion's modern document model. Here it is:

  • The user does not own to manually manage multiple copies of document files in order to retrieve aged versions.
  • If you soundless don't win it, check out the particular in the File menu formerly known as "Save." It now reads "Save a Version" instead. Every time a Lion-savvy application autosaves a document, it stores a copy of the previous version before it overwrites the file with the original data. A pop-up menu in the title bar of each document window provides access to previous versions.

    A menu in the title bar provides access to previous versions of a fileA menu in the title bar provides access to previous versions of a file

    Select the "Browse bar nothing Versions…" menu particular to enter a Time Machine-like space-themed screen showing bar nothing previous versions of the file. Using this interface, the document can live reverted to any earlier version, or snippets of data from earlier versions may live copied and pasted into the current version. Though the star territory background and surrounding timeline interface are provided automatically, the document windows themselves are actual windows within the application. They can live scrolled and manipulated in any artery allowed by the application, though the contents of previous versions may not live modified.

    Document version browser…in spaaaaace! Enlarge / Document version browser…in spaaaaace!

    The measure Cocoa document framework will manage many of the details for application developers, including automatically purging very aged versions of files. The document versioning interface shown above is furthermore integrated with Time Machine, showing both locally stored file versions and older versions that only exist on the Time Machine backup volume. Going forwards or backwards in the document timeline is accompanied by a methodical star-field "warp" animation.

    Restoring the document to an earlier condition actually just pushes a duplicate of that condition to the front of the stack of bar nothing changes. In other words, restoring a document to its condition as of an hour ago does not discard bar nothing the changes that happened during that hour.

    Returning to the title bar pop-up menu, the "Revert to final Saved Version" menu particular returns the document to its final explicitly saved condition (i.e., what it looked dote the final time the user typed ⌘S or selected the "Save a Version" menu item). "Duplicate" will create a original document containing the very data as the current document. Finally, the "Lock" particular will prevent any further changes to the document until it is explicitly unlocked by the user. Documents will furthermore automatically live locked if they're not modified for a Little while. The auto-lock time is configurable in the "Options…" screen of the Time Machine preference pane (of bar nothing places), with values from one day to one year. The default is two weeks.

    The auto-lock  detain setting, cleverly hidden in the Time Machine preference paneThe auto-lock detain setting, cleverly hidden in the Time Machine preference pane

    There is no graphical interface to previous versions of documents outside of an application. Previous versions can't live viewed or restored from within the Finder, for example. Forcing bar nothing version manipulation to live within the application is limiting, but it furthermore neatly solves the problem of how to present document contents with full fidelity—beyond what Quick ascertain offers—when looking at past revisions.

    One unexpected implication of autosave is that it makes quitting applications much less painful. If you've ever had to quickly log out or shut down a Mac that has been up and working difficult for weeks or months, you know how Awful it is to own to wade through umpteen dialog boxes, each demanding a decision about unsaved changes before allowing you to continue.

    These are not easy questions, especially for files that may own been open for a long time. achieve aside deciding whether the changes are worth saving; can you even recollect what the unsaved changes are? Were they intentional, or did you accidentally lank on the keyboard and delete a selected particular some time final week? Now multiply this scrape by the number of open documents with unsaved changes—and imagine you're in a hurry. It's not a pleasant experience.

    Autosave eliminates these hassles. Quitting an application that supports autosave happens instantly, with no additional user input required—always.

    Of course, by quitting an application (or quitting bar nothing applications by logging out or restarting) you're furthermore losing bar nothing of your accumulated state: bar nothing your open documents, the size and position of their windows, scroll positions, selection state. Losing condition can prove even more painful than playing "20 questions" with a swarm of "unsaved changes" dialog boxes. Assuming you can recollect what documents you had open, can you find them again?

    Lion offers original APIs to address this problem as well. A suite of original condition encoding/decoding hooks allow Lion applications to reclaim and restore any and bar nothing aspects of document state. Upon relaunch, an application is expected to restore bar nothing the documents open when it was final quit, with bar nothing their condition preserved.

    So, how's that "geek panic" now? soundless there, huh? Well, let me try to reassure you. As a committed user of a much Mac text editor that, years ago, implemented its own version of almost bar nothing the document management features described so far, I can divulge you that you win used to it very quickly. Spoiled by it, in fact. Ruined by it, some would say. Yes, it's a very different model from the one we're bar nothing used to. But it's furthermore a better model—not just for novices, but for geeks too.

    Think about it: never lose data because you forgot to save. Quit applications with impunity. Retrieve aged versions of documents at any time, in all or in part. Build up a nice arrangement of open documents and windows, knowing that your difficult travail will not live trashed the next time you quit the application or exigency to restart for an OS security update.

    The final piece of the puzzle is not strictly document-related, but it puts the bow on the package. When logging out or restarting, Lion presents an option (selected by default) to restore bar nothing open applications when you next log in. And relaunching a Lion-savvy application, of course, causes it to restore its open documents.

    Putting it bar nothing together, this means that you can log out or shut down your Mac without being asked any questions by needy applications and without losing any of your data or window state. When you next log in, the screen should ascertain exactly the very as it did just before you logged out. (In fact, Lion appears to "cheat" and briefly presents a static image of your earlier screen while it works on relaunching your apps and restoring your open documents. Sneaky, but an effective artery to originate condition restoration feel faster than it really is.)

    Process model

    If you were flipping out over the document changes described in the previous section, buckle up, because the discomfort smooth is about to mount yet again.

    The tiny indicator lights shown beneath running applications in the Dock are now optional in Lion.

    Three of these applications are runningThree of these applications are running

    In pre-release builds of Lion, bar nothing applications in the Dock looked exactly the same, running or otherwise. At the final minute, it seems Apple chickened out and enabled the indicator lights by default.

    Dock indicator lights preferenceDock indicator lights preference

    Apple's message with this feature is a simple one, but furthermore one that the nerdly sarcasm rebels against: "It doesn't matter if an application is running or not. You shouldn't care. cease thinking about it." Geek panic!

    Remain calm. Let's start with the APIs. Sudden Termination, a feature that was introduced in Snow Leopard, allows applications to betoken to the system that it's safe to assassinate them "impolitely" (i.e., by sending them SIGKILL, causing them to terminate immediately, with no chance for potentially time-consuming clean-up operations to execute). Applications are expected to set this bit when they're sure they're not in the middle of doing something, own no open files, no unflushed buffers, and so on.

    This feature enables Snow Leopard to log out, shut down, and restart more quickly than earlier versions of Mac OS X. When it can, the OS simply kills processes instead of politely asking them to exit. (When Snow Leopard was released, Apple made sure its own applications and daemon processes supported Sudden Termination, even if third-party applications didn't.)

    Lion includes a original feature called Automatic Termination. Whereas Sudden Termination lets an application divulge the system when it's okay to terminate it with extreme prejudice, Automatic Termination lets an application divulge the system that it's okay to politely hope the program to exit.

    But wait, isn't it always okay for the OS to politely hope an application to exit? Isn't that what's always happened in Mac OS X on logout, shutdown, or restart? Yes, but what makes Automatic Termination different is when and why this might happen. In Lion, the OS may terminate applications that are not in utilize in order to reclaim resources—primarily memory, but furthermore things dote file descriptors, CPU cycles, and processes.

    You read that right. Lion will quit your running applications behind your back if it decides it needs the resources, and if you don't emerge to live using them. The heuristic for determining whether an application is "in use" is very conservative: it must not live the vigorous application, it must own no visible, non-minimized windows—and, of course, it must explicitly back Automatic Termination.

    Automatic Termination works hand-in-hand with autosave. Any application that supports Automatic Termination should furthermore back autosave and document restore. Since only applications with no visible windows are eligible for Automatic Termination, and since by default the Dock does not betoken whether or not an application is running, the user might not even notice when an application is automatically terminated by the system. No dialog boxes will hope about unsaved changes, and when the user clicks on the application in the Dock to reactivate it, it should relaunch and emerge exactly as it did before it was terminated.

    This is effectively a deprecation of the Quit command. It also, perhaps coincidentally, solves the age-old problem of former Windows users expecting applications to terminate when they no longer own any open windows. When Automatic Termination is enabled in an application, that's exactly what will happen—if and when the system needs to reclaim some resources, that is.

    As if bar nothing of this isn't enough, Lion features one final application management twist. When an application is terminated in Lion, bar nothing the accustomed things emerge to happen. If the running application indicator is enabled, the tiny dot will evanesce from beneath the application's Dock icon. Assuming it's not a permanent resident, the application icon will evanesce from the Dock. The application will no longer emerge in the command-tab application switcher, or in Mission Control. You might therefore conclude that this application's process has terminated.

    A quick trip to the Activity Monitor application or the "ps" command-line utility may deter you of that notion. Lion reserves the privilege to retain an application's process around just in case the user decides to relaunch it. Upon relaunch, the application appears to start up instantly—because it was never actually terminated, but was simply removed from bar nothing parts of the GUI normally occupied by running applications.

    That's right, gentle readers. In Lion, an ostensibly "running" application may own no associated process (because the operating system automatically terminated it in order to reclaim resources) and an application may own a process even when it doesn't emerge to live running. Applications without processes. Processes without applications. Did Lion just blow your mind?

    The pitch

    The application and document model changes in Lion are a radical crash with the past—the past of the desktop, that is. Everything described above has existed since day one on Apple's mobile platform. Indeed, iOS is the most compelling dispute in favor of the changes in Lion. For every objection offered by a long-time personal computer aficionado, there are millions of iOS users countering the dispute every day with their fingers and their wallets.

    These changes in Lion are meant to reduce the number of things the user has to custody about. And while you may consider you really finish exigency to custody about when your documents are saved to disk or when the remembrance occupied by an application is returned to the system, you may live surprised by how Little you consider about these things once you become accustomed to the computer managing them for you. If you're an iOS user, consider about how often you've wanted a "Save" button in an app on your iPhone or iPad, for example.

    So that's the pitch: Lion will bring the worry-free usability of iOS application and document management to the Mac. For the vast majority of Mac users, I consider it will live an easy sale.

    The reality

    There's a common thread running through bar nothing of the application and document model features described above: they're bar nothing opt-in, and developers must add code to their applications to back them. Apple has some skill to hasten the transition to Lion-savvy applications through evangelism, positive reinforcement (the carrot), and the increasing popularity of the Mac App Store (the stick). But no matter what Apple does, the idyllic image of an iOS-like undergo on your Mac will prefer a long time to materialize.

    In the meantime, it's easy to envision a frustrating hodgepodge of aged and original Mac applications running on Lion, making users second-guess their hard-won computing instincts at every turn. What I consider will actually occur is that the top-tier Mac developers will quickly add back for some or bar nothing of these original features and users will start to ascertain down on applications that soundless behave the "old way." I'm sure that's how Apple hopes things gyrate out, too.

    Internals

    The previous release of Mac OS X focused on internal changes. My review did the same, covering compiler features, programming language extensions, original libraries, and other details that were mostly invisible to end-users.

    Lion is most definitely not an internals-focused release, but it's furthermore tremendous enough that it has its share of well-known changes to the core OS accompanying its more obvious user-visible changes. If this is your first time reading an Ars Technica review of Mac OS X and you've made it this far, live warned: this section will live even more esoteric than the ones you've already read. If you just want to behold more screenshots of original or changed applications, feel free to skip ahead to the next section. They nerds won't consider any less of you.

    Security

    Apple's approach to security has always been a bit unorthodox. Microsoft has spent the final several years making security a top priority for Windows, and has done so in a very public way. Today, Windows 7 is considered vastly more secure than its widely exploited ancestor, Windows XP. And despite the fact that Microsoft now distributes its own virus/malware protection software, a burgeoning market soundless exists for third-party antivirus software.

    Meanwhile, on the Mac, Apple has only very recently added some basic malware protection to Mac OS X, and it did so quietly. Updates own been similarly quiet, giving the impression that Apple will only talk about viruses and malware if asked a direct question about a specific, existent piece of malicious software.

    This approach is typical of Apple: don't recount anything until you own something meaningful to say. But it can live maddening to security experts and journalists alike. As for end-users, well, until there is a security problem that affects more than a tiny minority of Mac users, it's difficult to find an sample of how Apple's policies and practices own failed to protect Mac users at least as well as Microsoft protects Windows users.

    Sandboxing

    Just because Apple is quiet, that doesn't stand for it hasn't been taking existent steps to ameliorate security on the Mac. In Leopard, Apple added a basic form of sandboxing to the kernel. Many of the daemon processes that originate Mac OS X travail are running within sandboxes in Snow Leopard. Again, this was done with Little fanfare.

    Running an application inside a sandbox is meant to minimize the damage that could live caused if that application is compromised by a piece of malware. A sandboxed application voluntarily surrenders the skill to finish many things that a classic process hurry by the very user could do. For example, a classic application hurry by a user has the skill to delete every unique file owned by that user. Obviously, a well-behaved application will not finish this. But if an application becomes compromised, it may live coerced into doing something destructive.

    In Lion, the sandbox security model has been greatly enhanced, and Apple is finally promoting it for utilize by third-party applications. A sandboxed application must now comprise a list of "entitlements" describing exactly what resources it needs in order to finish its job. Lion supports about 30 different entitlements which sweep from basic things dote the skill to create a network connection or to listen for incoming network connections (two sever entitlements) to sophisticated tasks dote capturing video or soundless images from a built-in camera.

    It might look dote any nontrivial document-based Mac application will, at the very least, exigency to declare an entitlement that will allow it to both read from and write to any directory owned by the current user. After all, how else would the user open and reclaim documents? And if that's the case, wouldn't that entirely overcome the purpose of sandboxing?

    Apple has chosen to solve this problem by providing heightened permissions to a particular class of actions: those explicitly initiated by the user. Lion includes a trusted daemon process called Powerbox (pboxd) whose job is to present and control open/save dialog boxes on behalf of sandboxed applications. After the user selects a file or directory into which a file should live saved, Powerbox pokes a cavity in the application sandbox that allows it to accomplish the specific action.

    A similar mechanism is used to allow access to recently opened files in the "Open Recent" menu, to restore previously open documents when an application is relaunched, to manipulate drag and drop, and so on. The goal is to prevent applications from having to request entitlements that allow it to read and write capricious files. Oh, and in case it doesn't fade without saying, bar nothing sandboxed applications must live signed.

    Here are a few examples of sandboxed processes in Lion, shown in the Activity Monitor application with the original "Sandbox" column visible:

    Sandboxed processes in LionSandboxed processes in Lion

    Earlier, the Mac App Store was suggested as a artery Apple might expedite the adoption of original Lion technologies. In the case of sandboxing, that has already happened. Apple has decreed that bar nothing applications submitted to the Mac App Store must live sandboxed, starting in November.

    Privilege separation

    One limitation of sandboxing is that entitlements apply to an entire process. A sandboxed application must therefore possess the superset of bar nothing entitlements required for each feature it provides. As we've seen, the utilize of the Powerbox daemon process prevents applications from requiring capricious access to the file system by delegating those entitlements to another, external process. This is a specific case of the general principle called privilege separation.

    The conception is to crash up a tangled application into individual processes, each of which requires only the few entitlements necessary to accomplish a specific subset of the application's total capabilities. For example, consider an application that needs to play video. Decoding video is a tangled and performance-sensitive process which has historically led to inadequate protection against buffer overflows and other security problems. An application that needs to panoply video will likely finish so using libraries provided by the system, which means that there's not much a third-party developer can finish to patch vulnerabilities where they occur.

    What a developer can finish instead is seclude the video decoding job in its own process with severely reduced privileges. A process that's decoding video probably doesn't exigency any access to the file system, the network, the built-in camera and microphone, and so on. It just needs to accept a stream of bytes from its parent process (which, in turn, probably used Powerbox to gain the skill to read those bytes from disk in the first place) and recur a stream of decoded bytes. Beyond this simple connection to its parent, the decoder can live completely walled off from the repose of the system. Now, if an exploit is institute in a video codec, a malicious hacker will find himself in control of a process with so few privileges that there is Little harm it can finish to the system or the user's data.

    Though this was just an example, the QuickTime Player application in Lion does, in fact, delegate video decoding to an external, sandboxed, extremely low-privileged process called VTDecoderXPCService.

    QuickTime Player with its accompanying sandboxed video decoder processQuickTime Player with its accompanying sandboxed video decoder process

    Another sample from Lion is the Preview application, which completely isolates the PDF parsing code (another historic source of exploits) from bar nothing access to the file system.

    Putting aside the security advantages of this approach for a moment, managing and communicating with external processes is kindly of a throe for developers. It's certainly less convenient than the traditional approach, with bar nothing code within a unique executable and no functionality more than a function convoke away.

    Once again in Lion, Apple has provided a original set of APIs to cheer the adoption of what it considers to live a best practice. The XPC Services framework is used to manage and communicate with these external processes. XPC Service executables are contained within an application's bundle. There is no installation process, and they are never copied or moved. They must furthermore live Part of the application's cryptographic signature in order to prevent tampering.

    The XPC Service framework will launch an usurp external process on demand, track its activity, and settle when to terminate the process after its job is done. Communication is bidirectional and asynchronous, with FIFO message delivery, and the default XPC process environment is extremely restrictive. It does not inherit the parent process's sandbox entitlements, Keychain credentials, or any other privileges.

    The reward for breaking up an application into a collection of least-privileged pieces is not just increased security. It furthermore means that a crash in one of these external processes will not prefer down the entire application.

    We've seen this kindly of privilege separation used to much result in recent years by Web browsers on several different platforms, including Safari on Mac OS X. Lion aims to extend these advantages to bar nothing applications. It furthermore makes Safari's privilege separation even more granular.

    Safari in Lion is based on WebKit2, the latest and greatest iteration of the browser engine that powers Safari, Chrome, and several other desktop and mobile browsers. Safari in Snow Leopard already separated browser plug-ins such as scintillate into their own processes. (Adobe should not consider this an insult; Apple does the very with its own QuickTime browser plug-in.) As if to further that point, WebKit2 separates the entire webpage rendering job into an external process. The number of excuses for the Safari application to crash is rapidly decreasing.

    As the WebKit2 website notes, Google's Chrome browser uses a similar approach to seclude WebKit (version 1) from the repose of the application. WebKit2 builds the separation directly into the framework itself, allowing bar nothing WebKit2 clients to prefer odds of it without requiring the custom code that Google had to write for Chrome. (Check out the process architecture diagrams at the WebKit2 site for more detailed comparisons with pre-Lion WebKit on Mac OS X and Chrome's utilize of WebKit.)

    Automatic Reference Counting

    Since 2005, I've been very publicly concerned about the long-term prospects of Apple's programming language and application framework, Objective-C and Cocoa, going so far as to speculate about a viable technological crisis a few years in the future.

    When the future arrived, I revisited the issue of Apple's language and API future in light of Apple's histrionic entrance into the mobile market and the unprecedented growth this has enabled. You can read my conclusions for yourself, but the bottom line is that I'm soundless concerned about the issue—and consider Apple should live too. Success hides problems, and Apple has been so very successful in recent years.

    Enter (and exit) garbage collection

    Apple has done a tremendous amount of travail to modernize its development platform, including completely replacing its compiler, overhauling its IDE, and adding features and original syntax to the Objective-C language itself.

    All of these things are great, but nothing address my specific concerns about remembrance management. Apple did eventually behold meet to add garbage collection to Objective-C, but my alert that Apple wouldn't really consign to garbage collection in Objective-C turned out to live well-founded. Today, years after the introduction of this feature, very few of Apple's own applications utilize garbage collection.

    There's a satisfactory reason for this. Runtime garbage collection is simply a impoverished meet for Objective-C. For bar nothing its syntactic simplicity and long, distinguished history, the C programming language is actually a surprisingly tangled beast, especially when it comes to remembrance management. In C, any correctly aligned pointer-size bit pattern in remembrance can potentially live used as an address; the language explicitly allows casting from void * to a typed pointer, and vice versa. Objective-C, as a superset of C, inherits these charming properties. In exchange for this sacrifice, Objective-C code can live compiled alongside unpretentious C code and can link to C libraries with ease.

    This means that the runtime garbage collector is expected to traverse remembrance allocated by an capricious conglomeration of Objective-C and unpretentious aged C code and originate the amend decision—every time—about what remembrance may safely live collected. Apple's Objective-C garbage collection is a global switch. It can't live enabled just for the clean, object-oriented Objective-C code that application developers write; it applies to the entire process, including bar nothing the frameworks that the application links to.

    It seems sensible for garbage collection to prefer a hands-off approach to any remembrance allocated outside Objective-C's gated object-oriented community. Unfortunately, remembrance allocated "the old-fashioned way" in unpretentious C code routinely makes its artery into the world of Objective-C, and vice versa. In theory, bar nothing such code could live annotated in such a artery that it works correctly with garbage collection. In practice, Mac OS X contains artery too much code—much of it not written by Apple—to live able to properly vet every line of it to ensure that a runtime garbage collector has enough information to originate the privilege decisions in every case.

    And, in fact, despite Apple's bold claims of readiness, there own been and continue to live cases where even code within Apple's own frameworks can confuse the Objective-C garbage collector. These kinds of bugs are particularly insidious because they may only manifest themselves when the collector runs within a unavoidable window of time. The garbage collection compatibility outlook for third-party libraries is even more grim.

    Long narrative short: garbage collection for Objective-C is out. (It's soundless supported in Lion, but I wouldn't count on Apple putting a tremendous amount of endeavor into it going forward. And don't live surprised if it goes the artery of Rosetta in a few years.) In its place, Apple has created something called Automatic Reference Counting, or ARC for short. But to understand ARC, you should first understand how remembrance management in Cocoa has traditionally worked.

    Cocoa remembrance management

    Cocoa uses a remembrance management technique called reference counting. Each object has a reference count associated with it. When some Part of an application takes ownership of an object, it increments the object's reference count by sending it a retain message. When it's done with the object, it decrements the reference count by sending a release message to the object. When an object's reference count is zero, it is deallocated.

    This allows a unique object to live used by several different parts of the application, each of which is answerable for bookending its utilize of the object with retain and release messages. If retain is sent to an object more times than release, then its reference count will never gain zero and its remembrance will never live freed. This is called a remembrance leak. If release is sent more times than retain, then a release message sent after the object's reference count has reached zero will find itself looking at the region of remembrance formerly occupied by the object, which may now contain anything at all. A crash usually ensues.

    Finally, there's the autorelease message which means "release, but later." When an object is sent an autorelease message, it's added to the current "autorelease pool." When that pool is drained, bar nothing objects in it are sent one release message for each time they were added to the pool. (An object may live added to the very autorelease pool multiple times.) Cocoa applications own an autorelease pool that's drained at the conclude of each event loop, but original pools can live created locally by the programmer.

    Simple, right? Just originate sure your retain and release/autorelease messages are balanced and you're golden. But as straightforward as it is conceptually, it's actually surprisingly easy to win wrong. Experienced Cocoa programmers will divulge you that retain/release remembrance management eventually becomes second-nature—and it does—but programmers are only human. Accurately tracking the lifecycle of bar nothing objects in a large application starts to propel the limits of human mental capacity. To help, Apple provides sophisticated developer tools for tracking remembrance allocations and hunting down leaks.

    But education and tools only fade so far. Cocoa experts may not behold retain/release remembrance management as a problem, but Apple is looking towards the future, towards original developers. Other mobile and desktop platforms don't require this sort of manual remembrance management in their top-level application frameworks. Based on Apple's past efforts with garbage collection, it seems limpid that Apple believes it would live better for the platform if developers didn't own to manually manage memory. Now, finally, Apple believes it has institute a solution that it can really win behind.

    Enter ARC

    To understand how ARC works, start by picturing a traditional Objective-C source code file written by an expert Cocoa programmer. The retain, release, and autorelease messages are sent in bar nothing the privilege places and are in consummate balance.

    Now imagine editing that source code file, removing every instance of the retain, release, and autorelease messages, and changing a unique build setting in Xcode that instructs the compiler to achieve bar nothing the usurp remembrance management calls back into your program when the source code is compiled. That's ARC. It's just what the title says: traditional Cocoa reference counting, done automatically.

    Xcode's ARC setting (highlight added)Xcode's ARC setting (highlight added)

    Before explaining how ARC does this, it's well-known to understand what ARC does not do. First, ARC does not impose a original runtime remembrance model. Code compiled under ARC uses the very remembrance model as unpretentious C or non-ARC Objective-C code, and can live linked to bar nothing the very libraries. Second, ARC provides automatic remembrance management for Objective-C objects only (though note that blocks furthermore occur to live Objective-C objects under the covers). remembrance allocated in any other artery is not touched and must soundless live managed manually. (The very goes for other resources dote file handles and sockets.) Finally, ARC is not garbage collection. There is no process that scans the remembrance image of a running application looking for remembrance to deallocate. Everything ARC does happens at compile time.

    What ARC does at compile time is not magic. There is no deep simulated intelligence at travail here. ARC doesn't even utilize LLVM's sophisticated static analyzer to motif out where to achieve the retains and releases. The static analyzer takes a long time to run—too long to live a mandatory Part of the build process; it can furthermore relent erroneous positives. That's fine for a tool meant to detect viable bugs, but answerable remembrance management requires certainty.

    What allows ARC to travail is the very thing that enables people to (eventually) become expert Cocoa programmers: conventions. Cocoa has rules about the transfer of ownership that takes plot during common operations dote getting or setting an object attribute, initializing an object, or making a mutable copy. Furthermore, the methods that implement these operations ensue a set of naming conventions. ARC knows bar nothing these rules and uses them to settle when to retain and when to release.

    In fact, ARC follows the rules in a more pedantic manner than any human ever would, bracketing every operation that could possibly live influenced by object ownership with the usurp retain and release messages. This can relent a huge number of remembrance management operations. Luckily, Apple has an excellent optimizing compiler called Clang (since rechristened by Apple's marketing geniuses as the Apple LLVM Compiler 3.0). Clang sweeps through this sea of mechanically generated code, detecting and eliminating redundancies until what remains looks a lot dote what a human would own written.

    Conventions were made to live broken, of course. But what ARC lacks in semantic sophistication it makes up for in predictability and speed, speed, speed. In cases where the human really does know best, ARC can live told exactly what to finish thanks to a comprehensive set of original attributes and macros that allow the developer to annotate variables, data structures, methods, and parameters with categorical instructions for ARC. But the conception behind ARC is that these exceptions should live rare.

    To ensure that ARC can finish what it's designed to finish in a amend manner, a few additional language restrictions own been added. Most of them are esoteric, existing on the boundaries between Objective-C and unpretentious C code (e.g., C structs and unions are not allowed to contain references to Objective-C objects). Compatibility with existing C code is one of Objective-C's greatest strengths. But since ARC is a per-compilation-unit feature and ARC and non-ARC code can live mixed freely, these original language restrictions originate ARC more answerable without compromising interoperability.

    ARC versus garbage collection

    Apple's Objective-C garbage collection came with some drawbacks. As alluded to earlier, the programmer has Little control over when the garbage collector will run, making object reclamation non-deterministic. A garbage-collected application with a remembrance management bug may crash or not depending on when the collector actually runs. Since garbage collection only runs periodically, the "garbage" (memory) may start to pile up in between runs. This can multiply the so-called "high water mark" of an application. Finally, the garbage collection process itself can tamper with the execution of the application.

    Even on a multicore CPU where the collector can hurry on a sever thread, it must soundless interact with the running application's remembrance image, sometimes (briefly) blocking its progress while it cleans up the garbage. On relatively weak, often single-threaded mobile CPUs, this interference can manifest itself as stutters or glitches in the user interface.

    ARC offers a very different value proposition. To start, it suffers from nothing of the disadvantages of Objective-C's runtime garbage collection. ARC is deterministic; bar nothing the remembrance management code is baked into the executable and does not change at runtime. remembrance management is integrated directly into the program flow, rather than being done in batches periodically. This prevents execution stalls, and it can furthermore reduce the tall water mark.

    Most forms of automatic remembrance management incur some kindly of performance hit. Not ARC. To originate up for any viable multiply in the number of remembrance management messages generated by ARC, retain and release is 2.5 times faster in Lion; autorelease pools are 6 times faster; and to top it off, classic Objective-C message sending is 33 percent faster. Furthermore, since it's the compiler, not the programmer, inserting the remembrance management code, the generated retain and release code does not own to ascertain exactly dote a classic compiled Objective-C message send. The compiler has a much more intimate relationship with the Objective-C runtime, and can therefore optimize those operations in ways that a programmer cannot (well, should not, anyway).

    Finally, unlike garbage collection, ARC is a per-compilation-unit setting. Using ARC in your application does not stand for that every library you link to will furthermore hurry under ARC. This means that you don't own to worry about whether or not every unique one of Apple's libraries works correctly under ARC. Only Apple has to worry about that, and it can settle on a case-by-case basis which should live compiled with ARC and which should not. ARC and non-ARC code can live mixed freely.

    Objective-C garbage collection does, however, own one leg up on ARC. The garbage collector can detect and correctly reclaim object graphs with cycles in them. Under reference counting, if object A has a reference to object B, and object B has a reference to object A, then both A and B own a reference count of at least one. Even if no other object in the entire application has a reference to A or B, they will not live deallocated when running under ARC because they both, eternally, own nonzero reference counts.

    ARC requires the programmer to explicitly manipulate these situations, either manually breaking the cycles by removing one or more references or by using another Objective-C feature called "zeroing infirm references." (A infirm reference is a reference that doesn't contribute to an object's reference count.) For example, in a typical parent/child relationship, the parent might own a reference to the child and the child would own a infirm reference back to the parent. When the application no longer references the parent or child, the child will own a reference count of 1 (the parent soundless references it) but the parent will own a reference count of 0 and will therefore live deallocated. That then leaves the child with a reference count of 0, and it will live deallocated. Et voilà, no remembrance leak.

    The "zeroing" Part means that infirm references will live set to nil when the object they reference is deallocated. (Under ARC, bar nothing object pointers are initially set to zero.) Under classic circumstances, an object shouldn't live deallocated if there are soundless outstanding references to it. But since infirm references don't contribute to an object's reference count, an object can live deallocated when there are outstanding infirm references to it. When this happens, the automatic zeroing of the outstanding infirm references prevents them from becoming dangling pointers. (In Objective-C, sending a message to nil is a no-op.)

    ARC versus the world

    Now they approach to the 65,536 byte question. Does ARC achieve Apple back on an even footing with its competitors when it comes to programming language abstraction? The answer, I'm afraid, is no. ARC takes custody of almost bar nothing the mundane Objective-C remembrance management tasks, but everything outside of Objective-C remains as it was. Furthermore, ARC does very Little to address the other pillar of modern, high-level programming: remembrance safety.

    For bar nothing its auto-zeroing pointers and automatic object deallocation, ARC-enabled Objective-C is soundless a superset of C, and developers remain just a unique indecent pointer dereference away from scribbling bar nothing over their application's remembrance space. This is a far yell from the garbage collected, cycle-detecting, memory-safe, and sometimes even dynamically typed languages available on other platforms, both mobile and desktop.

    This brings us back to my six-year-old set of premises: that programming language abstraction increases over time; that Apple's competitors utilize languages that own a higher smooth of abstraction than Objective-C; and that Apple has yet to interpret how or when it's going to nearby the gap. ARC may not achieve parity with the likes of Java, C#, and JavaScript, but it does, finally, provide some insight into how Apple plans to retain its development platform technologically competitive.

    The first thing ARC reveals is that Apple does harmonize that there's a gap to live closed. It chose to assail the lowest-hanging fruit first, the one thing about Apple's development environment most likely to stand out as primitive and backwards to programmers coming from other platforms or even fresh out of school: manual remembrance management. But while doing so, Apple was not willing to sacrifice any of Objective-C's historic strengths. Objective-C with ARC retains its compatibility with existing code and libraries and remains lean, mean, and as dote a scintillate as ever—faster, in some cases.

    Right now, Apple seems committed to these two platform pillars: compatibility and performance. Compatibility is essential to protect Apple's considerable investment in its APIs and developer tools. (Apple even went so far as to enable ARC to travail on Snow Leopard, albeit without the zeroing infirm references feature.) Performance remains a competitive odds for Apple's mobile devices, not just in terms of interface responsiveness and stutter-free animations, but furthermore in power usage. Those runtime garbage collectors and virtual machines on other platforms can thrash caches and retain more mobile CPUs cores working longer and harder.

    Apple may own danced with runtime garbage collection, but it's going home with compile-time automation. There is no clearer indicator of Apple's commitment than the fact that ARC is now the default for bar nothing original projects created in Xcode; garbage collection never was.

    The most intriguing aspect of ARC is what it might portend for Apple's future. ARC shows that Apple is willing to add restrictions to the language in exchange for developer convenience and safety. It furthermore implies that Apple believes that compile-time automation and optimization is, if not preferable to, then at least as satisfactory as the runtime solutions available elsewhere, especially on mobile platforms.

    One thing that Apple does not apparently envision in its platforms' future is a traditional virtual machine, for bar nothing the reasons previously stated: performance, compatibility, and power usage. Runtime garbage collection is similarly off the table for now. (It's not that Apple believes that garbage collection necessarily precludes much performance; it's just a impoverished meet for Objective-C and Cocoa.)

    What Apple has instead is a cutting-edge traditional compiler built on a framework that supports many of the very concepts (e.g., bytecode, JIT), but at a lower level.

    Putting it bar nothing together, it's not difficult to imagine a future in which Apple's developers write code in a memory-managed, memory-safe language that incorporates only the highest-level aspects of Objective-C, but remains binary compatible with Objective-C libraries and code. This approach has been described as "Objective-C without the C," and that's not far off. They could arrive at this destination through a progression of incremental changes—ARC being the latest—which slowly add optional (but recommended) features and restrictions to Objective-C, only the final of which would live touted as introducing a "new language."

    Apple has invested a lot of time and manpower in getting off of gcc and onto a faster, more capable compiler. Now that the transition is over, Apple's attention can gyrate towards adding innovative features. The next few years of WWDC could live interesting.

    The condition of the file system

    The file system implementation is not something most Mac users consider about—nor should they. But dote any other Part of an operating system, there's some expectation that it will ameliorate over time. And dote any piece of technology, there comes a point where incremental improvements are no longer enough and a fresh start is required.

    Mac OS X itself was one such fresh start, albeit one derived from an existing product that was only slightly newer than the one it was replacing. But Mac OS X's file system, HFS+, was carried over from classic Mac OS directly into Mac OS X. It didn't win a fresh start when the repose of the OS did.

    Hopes were tall for a original file system back in 2006 when Apple publicly declared its interest in a port of Sun's innovative ZFS file system. The next year, Sun's CEO announced that ZFS would live Part of Mac OS X 10.5 Leopard—obviously without consulting Apple first.

    It didn't happen; Leopard shipped with HFS+. Two years after that, in 2009, Apple itself listed ZFS as a feature of Snow Leopard Server, only to later remove bar nothing references to ZFS from its Snow Leopard webpages. A few months later, Apple shut down its open-source project to port ZFS to Mac OS X.

    In the meantime, HFS+ has certainly been incrementally improved. Apple has added back for metadata journaling, case sensitivity, access control lists, and arbitrarily extensible metadata. nothing of these additions changed the basic design of the file system, however. HFS+ is thirteen years old, and is itself an extension of the HFS file system which is more than twenty-five years old. The condition of the art in file system design has advanced a lot since 1985.

    But again, most people don't expend much time thinking about the file system. They consider about files and folders, sure, but not the software that manages how the individual bytes are arranged on the storage device. My longstanding preoccupation with the nitty-gritty of file storage has often been met with indifference or even derision. "Who cares about a original file system?" hope the scoffers. "HFS+ works fine. It stores and retrieves my files just fine. What's the problem?"

    In response to this sentiment, I'd dote to proffer some concrete reasons why HFS+ is long overdue for replacement. I believe that Apple understands these problems better than anyone, but that a progression of hapless events has resulted in its next-generation operating system being hamstrung with a previous-generation file system for the past decade. Before discussing whether or not Lion makes any progress in this area, let's prefer a difficult ascertain at their aged friend, HFS+.

    What's wrong with HFS+

    Software is written with unavoidable target hardware in mind. When HFS was created, the top-of-the-line Macintosh came with an 800K floppy drive, the "high-end" storage offered by Apple was a 20MB difficult drive the size of a lunchbox, and the CPU was from the Motorola 68000 family. Thirteen years later, HFS+ replaced HFS, the floppy disks were 1.44MB, and Apple's difficult drives topped out around 6GB. retain this context in sarcasm as they consider the following details of HFS+'s implementation.

    When searching for unused nodes in a b-tree file, Apple's HFS+ implementation processes the data 16 bits at a time. Why? Presumably because Motorola's 68000 processor natively supports 16-bit operations. Modern Mac CPUs own registers that are up to 256 bits wide.

    All HFS+ file system metadata read from the disk must live byte swapped because it's stored in big-endian form. The Intel CPUs that Macs utilize today are little-endian; Motorola 68K and PowerPC processors are big-endian. (The performance cost of this is negligible; it's mostly just silly.)

    The time resolution for HFS+ file dates is only one second. That may own been enough a few decades ago when computers and disks were slower, but today, many thousands of file system operations (and many billions of CPU cycles) can live executed in a second. Modern file systems own up to nanosecond precision on their file dates.

    File system metadata structures in HFS+ own global locks. Only one process can update the file system at a time. This is an embarrassment in an age of preemptive multitasking and 16-core CPUs. Modern file systems dote ZFS allow multiple simultaneous updates, even to files that are in the very directory.

    The total number of blocks in an HFS+ volume is stored in a 32-bit value. With 4KB blocks, this allows for a maximum disk size of 17TB. That may sound huge to you now, but consider that it's only a sixfold multiply over what they own today, and today's largest difficult drives are, in turn, a sixfold multiply over what they had in 2005. (Apple can, of course, multiply the cache size from 4KB to, say, 8KB, but you can only play that game so long.)

    HFS+ lacks sparse file support, which allows space to live allocated only as needed in large files. consider about an application that creates a 1GB database file, then writes a few bytes at the start as a header and a few bytes at the conclude as a footer. On HFS+, slightly less than a gigabyte of zeros would own to live written to disk to originate that happen. On a modern file system with sparse file support, only a few bytes would live written to disk.

    Concurrency, metadata written in the amend byte order, sub-second date precision, back for massive volume sizes, and sparse file back are bar nothing common features of Unix file systems. Mac OS X, of course, is built on a Unix foundation. When HFS+ was ported from classic Mac OS to Mac OS X, it needed to live extended to back some minimum set of features that are expected from Unix file systems.

    Some of those features were an easy fit, but others were very difficult to add to the file system without breaking backwards compatibility. One particularly scary sample is the implementation of difficult links on HFS+. To retain track of difficult links, HFS+ creates a sever file for each difficult link inside a hidden directory at the root smooth of the volume. Hidden directories are kindly of creepy to start with, but the existent scare comes when you recollect that Time Machine is implemented using difficult links to avoid unnecessary data duplication.

    Listing the contents of this hidden directory (named "HFS+ Private Data", but with a bunch of non-printing characters preceding the "H") on my Time Machine backup volume reveals that it contains 573,127 files. B-trees or no b-trees, over half a million files in a unique directory makes me nervous.

    That passion is compounded by the most glaring omission in HFS+—and, to live fair, many other file systems as well. HFS+ does not concern itself with data integrity. The underlying hardware is trusted implicitly. If a few bits or bytes win flipped one artery or the other by the hardware, HFS+ won't notice. This applies to both metadata and the file data itself.

    Data corruption in file system metadata structures can render a directory or an entire disk unreadable. (For a double-whammy, consider about corruption that affects the "HFS+ Private Data" directory where every unique difficult link file on a Time Machine volume is stored.) Corruption in file data is arguably worse because it's much more likely to fade undetected. Over time, it can propagate into bar nothing your backups. When it's finally discovered, perhaps years later when looking at aged baby pictures, it's too late to finish anything about it.

    But how often does data corruption actually occur? The retort seems to live "more often than you'd think." Here's an excerpt from a 2010 academic paper on data integrity:

    In a recent study of 1.53 million disk drives over 41 months, Bairavasundaram et al. exhibit that more than 400,000 blocks had checksum mismatches, 8 percent of which were discovered during RAID reconstruction, creating the possibility of existent data loss. They furthermore institute that nearline disks develop checksum mismatches an order of magnitude more often than enterprise class disk drives.

    Read the all paper (PDF) for more detail and references. (Here's another sample [PDF] from CERN, and the data integrity section of the ZFS Wikipedia entry contains more information and links.)

    Most of these studies concern themselves with enterprise-scale deployments, but personal storage utilize today is where enterprise storage was only a few years ago (in terms of capacity, if not throughput). And retain in sarcasm that bar nothing of these issues only win worse as the data volume goes up—which it inevitably does, year after year.

    It's rapidly becoming inexcusable for the storage systems they entrust with some of their most precious possessions—something we're actively encouraged to finish by Apple itself—to prefer such a cavalier approach to data integrity. The worst Part is that there's Little a user can finish to originate up for this technological gap; backups only serve to silently spread data corruption.

    I'll cease here, but finish note that I haven't even gotten to many of the other headliner features of modern file systems: constant-time snapshots, transactional updates, data deduplication, and on and on. HFS+ has served Apple well, and probably for far longer than its designers ever imagined it would. But dote bar nothing the other Apple-related products and technologies that meet this description (e.g., classic Mac OS, Carbon, PowerPC), there comes a time when things once treasured must pass from this world.

    File system changes in Lion

    Finally, they approach to the heart of the matter. In Lion, what does Apple recount to the god of file system death? "Not today."

    That's right, the default and only file system on which you can install Lion is their aged friend, HFS+. As eminent earlier, I'm sure Apple is acutely watchful of HFS+'s shortcomings and would count its inability to territory a successor among its (rare) recent failings as steward of the platform. But it looks dote it will prefer a while longer for Apple's file system roadmap to win back on track after the ZFS near-miss.

    Nevertheless, there are some file system changes in Lion—some significant ones, in fact. The biggest is the introduction of Apple's first existent crack at creating a analytic volume manager: Core Storage.

    In earlier versions of Mac OS X (or classic Mac OS, for that matter), a unique physical disk could contain one or more volumes. That is, connecting the disk to a Mac would cause one or more original difficult drive icons to emerge in the Finder. By far, the most common case is to own just one volume on each physical difficult drive. But Mac users with more tangled needs (e.g., people who own to install many different versions of the operating system for testing or review purposes) prefer full odds of the skill to carve up a unique physical disk into multiple independent volumes.

    The role of HFS+ in this merge is revealed by Apple's nomenclature. HFS+ is a "volume format." It stands to reason that there must then live something above HFS+ answerable for managing the multiple volumes that may exist on a unique disk, in the very artery that HFS+ manages the multiple files and folders that exist within a unique volume. And so there is. Apple supports several varieties of what it calls "partition maps." ("Partitions" are the regions of a unique disk carved out for volumes, one volume per partition. Apple's currently favored partition map is the GUID flavor.)

    Logical volume management is a broad term that usually means allowing more elastic relationships between disks and volumes than traditionally provided by partition maps. In the case of Apple's Core Storage, the key original feature is the skill for a unique volume to span multiple physical disks.

    Somewhat obscuring this is a raft of original terminology to characterize the original layers of the storage stack. At the very top smooth is the analytic Volume Group, which may contain one or more Physical Volumes. A Physical Volume provides storage; it may live a unique physical disk, a disk image file, or even a RAID device. A analytic Volume Group exports zero or more analytic Volume Families. A analytic Volume Family contains one or more analytic Volumes, each of which presents a blank canvas onto which—finally!—a volume format dote HFS+ may reside.

    Got bar nothing that? Don't worry if you haven't. The only thing you exigency to understand for now is that Core Storage provides a much richer set of abstractions above the volume format. The next question is obvious: what does Lion finish with Core Storage?

    If you're entertaining visions of ZFS-style pooled storage, let me nip that in the bud. There is no friendly GUI for creating disk-spanning volumes, and the command-line tools provided are rudimentary and, in my brief testing, don't look to back bar nothing of the features ostensibly enabled by Core Storage.

    Core Storage's purpose in Lion is discreetly hidden in the analytic Volume Family tier of the layer cake. analytic Volume Families don't just export analytic Volumes, they furthermore contain properties that apply to them. One such set of properties in Lion enables full disk encryption.

    Though Apple is using the title FileVault to brand this feature, it has absolutely nothing to finish with the feature of the very title from earlier versions of Mac OS X. The earlier incarnation of FileVault encrypted an individual user's home directory by storing it in an encrypted disk image file. This presented bar nothing sorts of complications to common operations, and FileVault earned a horrible reputation for impoverished compatibility with existing software (including Apple's own, dote Time Machine).

    Lion's FileVault doesn't just encrypt users' home directories, and it doesn't utilize encrypted disk image files. Instead, it's Apple's implementation of all disk encryption. This means that every byte of data that makes up the volume is encrypted. Furthermore, this encryption is completely transparent to bar nothing software (including the implementation of HFS+ itself) because it takes plot at a layer above the volume format—a layer that application software does not behold at all.

    Having used a third-party whole-disk encryption product for years, I can divulge you that this approach works amazingly well. It really is completely transparent, and the only compatibility issues I've had involved operating system upgrades. (When stirring from Leopard to Snow Leopard, a original version of the disk encryption software was required. Presumably, this will not live a problem now that the feature is built into the OS.)

    Enabling whole-disk encryption is easy in Lion. The FileVault tab in the Security & Privacy preference pane carefully guides a user through the process, presenting limpid explanations along with an extremely generous dose of caution.

    FileVault whole-disk encryptionFileVault whole-disk encryption

    Each user who will live able to decrypt the drive must enter their password to finish so. Next, an auto-generated "recovery key" is presented, along with a suggestion to "make a copy and store it in a safe place." This is a final gyrate in case a user forgets his or her account password. More dire warnings about data loss escort this information.

    FileVault recovery key: your  final best hopeFileVault recovery key: your final best hope

    Will people really write down that long recovery key and store it in a safe place? Apple has its doubts, it seems, because the next screen asks if you'd dote Apple to store the recovery key for you. There is no default selection for this question, which is exactly right, as far as I'm concerned. Most users probably should allow Apple to store their recovery key, but making that the default might live seen as an overreach by geeks and security nerds.

    If you pick to faith Apple, you must enter answers to three personal questions of your choice. The dialog claims that no one, not even Apple itself, can access your recovery password without the answers to these questions. We've heard claims dote this before, but I'm inclined to believe that Apple has scholarly from the mistakes of others.

    Recovery key escrow:   cheer Apple   cheer youRecovery key escrow: cheer Apple cheer you

    Finally, Apple insists that a recovery partition live present on the disk that's about to live encrypted. If it isn't, and if one can't live created (e.g., because it uses the wrong kindly of partition map, or because doing so would shift a Boot Camp partition to the fourth position, making it unbootable), encryption won't live allowed to proceed. (It's kindly of annoying that this check is only made at the very conclude of the process.)

    Assuming a recovery partition exists or can live created, a restart is required to enable encryption. Upon reboot, a screen that looks a lot dote the Lion login screen (but only containing the users who are allowed to decrypt the volume) appears instantly. Select a user and enter the amend login password and the existent boot process begins. Even if auto-login is disabled, you will boot directly into the account whose password was just entered.

    Revisiting the FileVault preference pane shows an rate of the time remaining before the encryption process is complete. Encryption happens transparently in the background, which is a satisfactory thing because it takes a long time. While it's running, you can utilize applications, logout, reboot, and generally utilize your Mac as you normally would without perturbing the encryption process.

    If any users on the system are unable to decrypt the disk, they can live allowed to finish so by having them enter their login password.

    Enable more users to access the encrypted diskEnable more users to access the encrypted disk

    The output of the diskutil list command now looks a bit extraordinary (compare to earlier):

    /dev/disk1 #: nature title SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk1 1: EFI 209.7 MB disk1s1 2: Apple_CoreStorage 124.5 GB disk1s2 3: Apple_Boot Recovery HD 654.6 MB disk1s3 4: Apple_HFS Timex 124.6 GB disk1s4 /dev/disk2 #: nature title SIZE IDENTIFIER 0: Apple_HFS Lion Ex *124.2 GB disk2

    What once appeared to the OS as a unique disk device now registers as two. One contains the two non-encrypted volumes (Recovery HD and Timex) plus the original Core Storage volume, and the other contains the mounted incarnation of the newly encrypted (well, encrypting, in this case) volume. Using the special Core Storage variant of the list command (diskutil cs list) reveals more detail, most of which should now originate sense after the earlier terminology review.

    CoreStorage analytic volume groups (1 found) | +-- analytic Volume Group 19566D89-E29A-4C6C-88FA-6B845EF1DEBB ========================================================= Name: Lion Ex Sequence: 1 Free Space: 0 B (0 B) | +-< Physical Volume 1A645A01-E149-48B4-8C79-5FD3E20384F1 | ---------------------------------------------------- | Index: 0 | Disk: disk1s2 | Status: Online | Size: 124509331456 B (124.5 GB) | +-> analytic Volume Family 58B532AA-B265-4AC7-B53B-12BB039D97B2 ---------------------------------------------------------- Sequence: 9 Encryption Status: Unlocked Encryption Type: AES-XTS Encryption Context: Present Conversion Status: Converting Has Encrypted Extents: Yes Conversion Direction: forward | +-> analytic Volume 8A7ACC28-321B-4653-8E85-94CAF047D1DE --------------------------------------------------- Disk: disk2 Status: Online Sequence: 4 Size (Total): 124190560256 B (124.2 GB) Size (Converted): 2539913216 B (2.5 GB) Revertible: Yes (unlock and decryption required) LV Name: Lion Ex Volume Name: Lion Ex Content Hint: Apple_HFS

    Lion doesn't originate encrypting disks other than the boot disk particularly easy. The Disk Utility application can remove encryption from a volume, change a volume's encryption password, or reformat a volume with encryption enabled (deleting bar nothing the data currently on the volume in the process), but there is no option to transparently encrypt a volume without erasing it.

    Command-line tools to the rescue: diskutil will happily attempt to encrypt any volume you point it at, without erasing it first. Actually, the process is to transmogrify it to a Core Storage volume which may optionally comprise encryption. Let's encrypt the Timex volume, shown as disk1s4 in the earlier diskutil list output.

    % diskutil cs transmogrify disk1s4 -passphrase mysecret Started CoreStorage operation on disk1s4 Timex Resizing disk to meet Core Storage headers Creating Core Storage analytic Volume Group Attempting to unmount disk1s4 Switching disk1s4 to Core Storage Waiting for analytic Volume to appear Mounting analytic Volume Core Storage LVG UUID: B02B86AC-C487-43B3-8C2E-7918CE80ECDF Core Storage PV UUID: 76336EBE-A3B5-4E1E-98B4-8A6873746D86 Core Storage LV UUID: E1F2E293-9952-425E-A597-0954BA734102 Core Storage disk: disk3 Finished CoreStorage operation on disk1s4 Timex Encryption in progress; utilize `diskutil coreStorage list` for status

    As the command output indicates, the volume is shrunk slightly to accommodate the Core Storage headers, then the layer cake of analytic volume management components is created, at the very bottom of which is the original analytic volume. No restart is required to start the process, which happens transparently in the background just dote the one initiated from the GUI. The diskutil cs list command now shows a pair of analytic Volume Groups, each of which is declared to live in the process of encryption. The exact amount of data encrypted and remaining to live encrypted on each volume is furthermore listed.

    CoreStorage analytic volume groups (2 found) | +-- analytic Volume Group 19566D89-E29A-4C6C-88FA-6B845EF1DEBB | ========================================================= | Name: Lion Ex | Sequence: 1 | Free Space: 0 B (0 B) | | | +-< Physical Volume 1A645A01-E149-48B4-8C79-5FD3E20384F1 | | ---------------------------------------------------- | | Index: 0 | | Disk: disk1s2 | | Status: Online | | Size: 124509331456 B (124.5 GB) | | | +-> analytic Volume Family 58B532AA-B265-4AC7-B53B-12BB039D97B2 | ---------------------------------------------------------- | Sequence: 9 | Encryption Status: Unlocked | Encryption Type: AES-XTS | Encryption Context: Present | Conversion Status: Converting | Has Encrypted Extents: Yes | Conversion Direction: forward | | | +-> analytic Volume 8A7ACC28-321B-4653-8E85-94CAF047D1DE | --------------------------------------------------- | Disk: disk2 | Status: Online | Sequence: 4 | Size (Total): 124190560256 B (124.2 GB) | Size (Converted): 16999776256 B (17.0 GB) | Revertible: Yes (unlock and decryption required) | LV Name: Lion Ex | Volume Name: Lion Ex | Content Hint: Apple_HFS | +-- analytic Volume Group B02B86AC-C487-43B3-8C2E-7918CE80ECDF ========================================================= Name: Timex Sequence: 1 Free Space: 0 B (0 B) | +-< Physical Volume 76336EBE-A3B5-4E1E-98B4-8A6873746D86 | ---------------------------------------------------- | Index: 0 | Disk: disk1s4 | Status: Online | Size: 124551483392 B (124.6 GB) | +-> analytic Volume Family F02B9A32-10DE-4BDF-9697-00CE1B6F1133 ---------------------------------------------------------- Sequence: 6 Encryption Status: Unlocked Encryption Type: AES-XTS Encryption Context: Present Conversion Status: Converting Has Encrypted Extents: Yes Conversion Direction: forward | +-> analytic Volume E1F2E293-9952-425E-A597-0954BA734102 --------------------------------------------------- Disk: disk3 Status: Online Sequence: 4 Size (Total): 124232712192 B (124.2 GB) Size (Converted): 94633984 B (94.6 MB) Revertible: Yes (unlock and decryption required) LV Name: Timex Volume Name: Timex Content Hint: Apple_HFS

    At any point, the encryption process can live reversed (using Disk Utility, the FileVault tab of the Security & Privacy preference pane, or the diskutil command-line program). The decryption process furthermore happens in the background.

    Changing the encryption password for a disk does not require a lengthy decryption and re-encryption process. I assume FileVault in Lion works dote other all disk encryption solutions in that what the password actually unlocks is the existent encryption key for the volume. Changing the encryption password only requires decrypting and re-encrypting the existent encryption key, which is tiny.

    The encryption features that Apple has chosen to provide access to in the GUI betray a lot about the aim of this feature. First, it's meant to live completely transparent. The only change as far as the user is concerned is that the login screen appears to own moved to the very nascence of the startup process. There is no sever password to remember; the user's login password decrypts the disk. The very goes for every other user with an account on the system.

    Login passwords are only tied to a boot disk, however. Using login passwords to encrypt disks that may bound from one Mac to another could lead to confusion. This partly explains why there's no GUI option for encrypting non-boot disks. The other Part of that decision is likely that FileVault is focused on mobile users. nothing of Apple's laptops own more than one internal drive, and partitioning is rare and probably only done by users who furthermore know enough to ascertain up the command-line utility to enable disk encryption on their non-boot volumes.

    Transparent encryption and decryption, consummate software compatibility, a friendly GUI with ample safety nets for non-geek users—what's not to love? Ah, I'm sure you're wondering about performance. bar nothing forms of all disk encryption capitalize from the current imbalance between CPU power and disk speed. In almost bar nothing circumstances, the CPU in your Mac spends most of its time twiddling its thumbs with nothing to do. This is especially staunch for operations that involve a lot of disk access.

    Whole disk encryption takes odds of this nearly omnipresent CPU cycle glut to sneak in the tiny chunks of travail it requires to encrypt and decrypt data from the disk. Apple furthermore leverages the special-purpose AES instructions and hardware on Intel's newest CPUs, further reducing the CPU overhead. The conclude result is that regular users will live hard-pressed to notice any reduction in performance with encryption enabled. Based on my undergo with the feature in prerelease versions of Lion, I would strongly consider enabling it on any Mac laptop I aim to travel with.

    File system future

    Disk encryption that actually works, plus some basic analytic volume management features—that's bar nothing well and good. But where does this leave us on the file system front? Perhaps things are not as indecent as they seem. The following is bar nothing speculation, but given Apple's information vacuum on bar nothing things file-system-related, it's bar nothing I've got for now.

    Core Storage is probably the most significant file system change in the history of Mac OS X. Let's consider about what it does. Core Storage is answerable for managing the chunks of data that originate up the individual analytic volumes on a disk. To finish so, presumably it has a set of metadata structures for tracking allocated and free space and for remembering which chunks belong to which volumes.

    Now imagine that those chunks start to shrink until they are the size of, say, individual files. And instead of volumes, imagine those file-sized chunks belonging to directories. Okay, it's a stretch, but again, it's bar nothing they own to fade on. Assuming Apple is pleased with the artery Core Storage turned out, it has effectively fielded its first brand-new code that performs some of the very basic functions as a file system. Were Apple so inclined, it seems technically plausible, at least, that it could extend this travail into a original in-house file system project.

    With ZFS out of the picture, Btrfs presumably eliminated due to its licensing, and future development of ReiserFS uncertain, its difficult to behold where Apple will win the modern file system that it so desperately needs other than by creating one itself.

    This is something I've been anticipating for years. I would own certainly welcomed ZFS with open arms, but I was equally confident that Apple could create its own file system suited to its particular needs. That self-confidence remains, but the ZFS distraction may own added years to the timetable.

    In the meantime, a few Brave souls are soundless determined to bring ZFS to Mac OS X. I wish them luck, but I would much prefer a solution supported by the operating system vendor. Apple, the gauntlet has been thrown down; it's time to deliver.

    Document revisions

    Lion's modernized document model leans heavily on the skill to manage multiple versions of a unique document. Viewed solely through the user interface, it appears to live magic. Unlike earlier incarnations of autosave, you won't behold auto-generated files appearing and disappearing alongside the original document. But the data obviously has to live stored somewhere, so where is it?

    Despite bar nothing its flaws, the Mac OS X file system does own several features that might live useful for saving multiple versions of files. Version number metadata could live stored in an extended attribute; the file data itself could conceivably live stored in named forks; the existing invisibility metadata could live used to camouflage the multiple versions.

    Although Apple has gotten religion regarding file system metadata in recent years, leaning heavily on extended attributes in the implementation of Time Machine, downloaded file quarantines, and access control lists, metadata holdovers from classic Mac OS are soundless out of favor. If Spotlight's implementation has taught us anything, it's that today's Apple prefers to retain things simple when it comes to the file system.

    Given bar nothing of this, I wasn't surprised to find a /.DocumentRevisions-V100 directory lurking at the root smooth of my boot drive, privilege alongside the /.Spotlight-V100 directory. Inside, you'll find an SQLite database file (/.DocumentRevisions-V100/db-V1/db.sqlite) containing tables for tracking files, the individual versions of those files (which Apple calls "generations"), and the storage location of the data. Here's the schema, for the curious.

    CREATE TABLE files ( file_row_id INTEGER PRIMARY KEY ASC, file_name TEXT, file_parent_id INTEGER, file_path TEXT, file_inode INTEGER, file_last_seen INTEGER NOT NULL DEFAULT 0, file_status INTEGER NOT NULL DEFAULT 1, file_storage_id INTEGER NOT NULL ); CREATE TABLE generations ( generation_id INTEGER PRIMARY KEY ASC, generation_storage_id INTEGER NOT NULL, generation_name TEXT NOT NULL, generation_client_id TEXT NOT NULL, generation_path TEXT UNIQUE, generation_options INTEGER NOT NULL DEFAULT 1, generation_status INTEGER NOT NULL DEFAULT 1, generation_add_time INTEGER NOT NULL DEFAULT 0, generation_size INTEGER NOT NULL DEFAULT 0 ); CREATE TABLE storage ( storage_id INTEGER PRIMARY KEY ASC AUTOINCREMENT, storage_options INTEGER NOT NULL DEFAULT 1, storage_status INTEGER NOT NULL DEFAULT 1 );

    Unlike Time Machine, Apple's file version storage system is not limited to saving a complete copy of each original revision of a file. A second SQLite database (/.DocumentRevisions-V100/.cs/ChunkStoreDatabase) tracks the individual chunks that differ from one revision of a file to another. (Examining its schema is left as an exercise for the reader. Just recollect to copy the database file to a original location and hurry the sqlite3 program on the copy instead of the actual database, which will likely live locked anyway.)

    Intelligently splitting files into chunks such that only a few chunks change from one revision to another is actually quite a difficult problem. consider a 10MB file, initially split into ten 1MB chunks. Now imagine that the next revision of the file simply adds two bytes to the very nascence of the file. Were the original revision to live naïvely split into ten equal-sized chunks, every chunk would live different from bar nothing previously created chunks, defeating the entire purpose of splitting files into chunks rather than saving complete copies every time.

    One technique Apple uses to deal with this problem is called Rabin fingerprinting. Chunks of the file are selected based on their content, rather than strictly based on their offset within the file. (The title of the research paper that introduced this technique, A Low-bandwidth Network File System, suggests that it might furthermore live useful for, say, a network-based file storage system. Hmmm.)

    This algorithm is not blindly applied to every file, however. The chunk storage engine knows about the internal structure of many common file formats (e.g., JPEG images, MPEG4 video, PDFs) and can intelligently chunk them based on this knowledge, separating headers and footers, finding the borders between internal elements, and so on. Unlike Spotlight, there doesn't emerge to live a plug-in system for adding categorical back for original file types. Custom file types saved by third-party applications emerge to live left to the whims of Rabin fingerprinting.

    Very tiny files (under, say, 32KB) emerge not to live chunked at all. Chunking is not guaranteed to occur immediately when a file is saved; it may occur at a later time. Very large files are generally split into larger pieces, preventing a situation where a 2GB file produces thousands of chunks. This all exhibit is hurry by a new, private GenerationalStorage.framework which includes a daemon named revisiond.

    (There's an entertaining opportunity here for a third-party developer to create an "unauthorized" application for browsing the contents of the generation store, perhaps even hacking in a original context menu particular in the Finder for listing previous revisions of a selected file. An application dote this probably won't live allowed into the Mac App Store, and it's likely to crash in the next OS revision, but it may soundless find enough customers to live worthwhile.)

    Apple's generational storage system is an entertaining merge of tried-and-true technologies (SQLite, daemons, unpretentious files and directories) with just enough cleverness to avoid being an undue burden to the system in operation. And remember, every unique file created on the system is not automatically versioned in Lion. Generational storage is a feature that developers must explicitly use. I sure hope a lot of them finish so.

    Resolution independence

    Resolution independence has been "coming soon to Mac OS X" since 2005. The dream of drawing the very interface elements at the very visible size but with more pixels was so nearby in 2007 that they could tang it. Then Snow Leopard arrived and the Mac's interface scalability features actually regressed. Depressing.

    Meanwhile, Mac OS X's sibling operating system waltzed privilege into a high-resolution UI on its very first try. iOS's secret? Don't try to back capricious scale factors, just back one: double resolution. A 50x50-pixel square on a non-retina iPhone screen is exactly the very size as a 100x100-pixel square on a retina display. Graphics that own not been updated for the higher resolution are simply drawn with four-pixel squares in plot of each low-resolution pixel. bar nothing dimensions are nice, even, integer multiples of each other. This is a consummate meet for physical screens which, of course, own an integer number of pixels. Fractional measurements necessarily require hideous compromises.

    Lion has taken the hint from its younger brother. capricious scalability is gone. In its plot is a unique check box to enable "HiDPI" panoply modes. (This option is soundless hidden away in the Quartz Debug application, so it's clearly not an end-user feature. But unlike bar nothing previous incarnations of resolution independence, this one actually works.)

    HiDPI  panoply modes on a 15-inch MacBook Pro (native resolution: 1440x900)HiDPI panoply modes on a 15-inch MacBook Pro (native resolution: 1440x900)

    After enabling HiDPI, original panoply modes will become available. In the screenshot above, the 720x450 mode is half indigenous screen dimensions, and the 640x400 mode is half the (non-native) 1280x800 setting. After selecting a HiDPI mode, everything is drawn with twice as many pixels as its non-HiDPI equivalent. Here's a screenshot featuring TextEdit, their accustomed interface scalability workhorse.

    TextEdit running in Lion's "HiDPI" mode Enlarge / TextEdit running in Lion's "HiDPI" mode

    It looks pretty good, right? The only flaws are the bitmap graphics that haven't been updated for HiDPI (look closely at the black triangles in the ruler). Unfortunately, there are a lot of these throughout the operating system and its bundled applications. But unlike in bar nothing years past, the framework is finally there for third-party developers and Apple itself to finally win their applications ready for a world in which 300-dpi desktop and laptop displays are more than just expensive curiosities.

    Unlike iOS, Mac OS X has to contend with a much wider variety of panoply sizes. Thus far, there has been no Mac equivalent of the iPhone 4, arriving with a double-density panoply and quickly selling so many units that it represents a significant portion of the installed base. Still, the ease with which iOS developers adapted to the retina panoply gives me self-confidence that this pixel-doubling approach can travail on the Mac as well. They just own to wait a bit longer. By now, they should live used to it.

    Applications

    Thanks to the comprehensively revised user interface, most applications that ship with Lion ascertain new, but a few of them own particularly significant changes. I'm not going to cover bar nothing of them (you'll find more extensive screenshot galleries elsewhere), but here are some highlights.

    The Finder

    The Finder's transition from Carbon to Cocoa in Snow Leopard is starting to pay off in Lion. Several original APIs added to Cocoa in Lion own been adopted by the Finder. In days past, when the Finder was soundless a Carbon application, it rarely got the latest and greatest features at the very time as other bundled applications. No more.

    Cocoa in Lion gives developers more control over the image displayed when an particular is dragged from one plot to another. The Lion Finder uses this control to transform multi-item selections from the accustomed ghostly image of the source into a compressed, realigned, list-view representation. This transformation happens a minute or two after the drag begins.

    While this is a fine demonstration of a original API, the undergo is a bit off-putting. Imagine taking a dish out of the dishwasher and then having it start flopping around dote a fish in your hand. This is a rare case of Apple losing sight of what's well-known in real-time interaction design. Stability and responsiveness lead to comfort. A transformative animation (instability) that happens after a short detain (the appearance of unresponsiveness) does not originate for satisfactory experience. I wonder how many novice users will instinctively release the mouse button and inadvertently terminate the drag operation the first time this animation is triggered.

    Search tokensSearch tokens

    The Finder furthermore proudly demonstrates Lion's original capsule-style search tokens. Free text can live entered into the search territory as usual, but a pop-up menu provides options to limit the scope of the search terms typed so far. The only two options available are "Filename" and "Everything," but the interface is fun and easy to use, and the potential is there for much more sophistication. (For more tangled searches, the full-fledged Spotlight search with nested boolean logic remains in Lion.)

    By default, at the top of the Lion Finder's sidebar is the original "All My Files" item. It's a canned search that finds bar nothing documents in the user's home directory and displays the results in a flat list. The sidebar particular representing the computer as a whole, showing bar nothing attached drives and connected servers, is soundless available, but is not in the sidebar by default. The very goes for the home directory item. The other predefined saved searches (e.g., Today, Yesterday, bar nothing Images, etc.) are no longer available, though they can live recreated manually.

    All My Files combined with a secondary filter, arranged by kindAll My Files combined with a secondary filter, arranged by kind

    The addition and prominence of "All My Files" is yet another vote of no-confidence in the user's skill to understand and navigate the file system. If you've ever seen a Mac user try to navigate from the top smooth of his difficult drive down to his Documents folder, you can start to understand the challenge Apple is up against here. The "All My Files" particular is just what the doctor ordered. In the increasingly rare cases when novices utilize the Finder directly, rather than managing their data from within an application dote iTunes or iPhoto, bar nothing they want to know is, "Where are bar nothing my files?" Asked and answered.

    Expert users with thousands upon thousands of files will likely find the "All My Files" feature less useful. But if you cease thinking of it as a "location" and start thinking of it as a saved search to which you can apply additional filters with the toolbar's search field, it starts to win more interesting. The only remaining barrier is performance, which does suffer as the number of files increases.

    All of the existing Finder view styles (icon, list, column, and cover flow) back a original "Arrange By" option which sorts items into groups. Each group has a header which "sticks" to the top of the window as the view is scrolled, until the final particular belonging to that group scrolls off the top of the list. The columns in the group headers are frustratingly un-configurable and can't live individually resized. But those quibbles aside, the feature does add an entertaining original dimension to file browsing.

    A original sort order has furthermore been added to bar nothing views: Date Added. This is an exemplar order for the Downloads folder. Sorting by creation or modification date was always problematic for files that preserved their timestamps through the download process (e.g., zip-compressed Mac applications). This would cause "new" downloads to emerge in unexpected positions in the list. I'm tempted to declare Date Added sorting as best original feature in the Finder, but I'm afraid that might look dote damning with faint praise.

    Aesthetically speaking, the Finder, dote the repose of Lion, has been visited by the color vampire. The Finder sidebar doesn't even deference custom folder icons, showing them as generic gray folders instead. That seems a Little tyrannical, even for Apple.

    The only  satisfactory folder is a gray folderThe only satisfactory folder is a gray folder

    This paternalism extends to other aspects of the Finder, as well. Library folders are now invisible in the Finder, removing the temptation for novice users to fade mucking around in directories they don't understand. The "Go to Folder…" menu command soundless exists, so customer back has some way, at least, to win users there without resorting to a shell prompt. But existing back documents that comprise instructions and screenshots that hope the Library folder to live visible will own to live revised for Lion.

    View optionsView options

    The Finder's destructive merge of browser and spatial behaviors remains in Lion. The tradition of subtly changing the rules that govern when, where, and how view condition changes are applied and honored furthermore continues. Just in case anyone thought they had finally figured out how the Snow Leopard Finder decides what view to exhibit when displaying the contents of a folder in a particular window, Lion changes the rules again.

    The controls at the top of the view options palette now comprise a mysterious sub-checkbox labelled "Browse in view," where view is the window's current view style. This appears to govern the view used when opening sub-folders from a window where the toolbar is visible, but a Little experimentation will betray that the setting is overridden by any "Always open in view" setting of a sub-folder. The conclude result is the very as it has ever been: an inscrutable system that users quickly give up any hope of understanding, resigning themselves to manually correcting view styles as needed during every interaction with the Finder.

    Mail

    Apple's venerable Mail application gets a significant facelift in Lion. Once derided as one of the ugliest bundled applications, it's now been transformed into the classiest. (It doesn't torment that the competition has stumbled a bit.) The screenshot below is dominated by the glossy Apple promotional e-mail for Lion in the right-hand pane, but ascertain past it at the surrounding interface.

    Mail in Lion: a class act Enlarge / Mail in Lion: a class act

    Or rather, ascertain at how much of the surrounding interface isn't there. With the exception of the toolbar, this window is completely about the content. There are no external borders, only the barest hint of internal borders, and, as befitting a staunch Lion application, no visible scrollbars. The toolbar and quick-access button bar ensue the monochromatic Lion style while soundless looking crisp. The cheeky red flag icon is furthermore a nice touch.

    After years of unsupported hacks to add a three-pane wide-screen view to Mail, Apple has finally taken the hint and made it official. There's also, naturally, a full-screen mode.

    At last, widescreen three-pane Mail for all Enlarge / At last, widescreen three-pane Mail for all

    Like the Finder, Mail's search territory supports Apple's snazzy original search tokens. These provide the fastest artery to finish medium-complexity searches that I've ever seen in any e-mail application. It's too indecent the search territory is so narrow and doesn't expand to fill bar nothing available space in the toolbar, however.

    The main viewing pane shows entire threads by default, with each message appearing as a sever virtual piece of paper. Mail aggressively collapses quoted text within messages, displaying an adorable accordion result upon expansion.

    Mail plays an accordion animation when expanding quoted text Enlarge / Mail plays an accordion animation when expanding quoted text

    Keyboard back is excellent, allowing one-handed navigation for most common tasks. Expanding a thread and selecting a unique message causes it to fill the right-hand pane, leaving behind the amour-propre that each message is actually a Little piece of paper.

    Mail has become more capable, as well. Simple loaded text editing capabilities own finally been added. Mail is furthermore even better about automatically setting up accounts for common services. The account setup screens just hope for a name, e-mail address, and password, and will usually finish everything else for you, including (optionally) correctly configuring and integrating calendar and chat services that might live associated with the e-mail account (e.g., Google Calendar and Talk).

    Rich text editing: let your font flag flyRich text editing: let your font flag fly

    If, dote me, you never seriously considered using any of the previous incarnations of Apple's Mail application, the version in Lion is definitely worth taking for a test drive—even if only as a chance to undergo an application that so thoroughly embraces the technology and aesthetic of the original operating system.

    Safari

    Besides adding back for another crop of original Web technologies (MathML, WOFF, CSS3 enhancements), the biggest change in Safari is its aforementioned utilize of the original WebKit2 rendering engine, which moves webpage rendering into a separate, low-privilege process. (Previous versions of Safari already isolated plug-ins in sever processes.) This change is invisible to the user, but it should provide an additional layer of protection against browser-based exploits.

    Safari's downloads window has been subsumed into the toolbar and is now displayed as an iPad-style popover. (This is a measure control available to bar nothing Cocoa applications in Lion.) When starting a download, an icon leaps from the point of the click into the downloads toolbar icon, which then displays a tiny progress bar. It's cute, informative for novices, and keeps the downloads window out of the way.

    Safari downloads in a popoverSafari downloads in a popover

    A tiny eyeglasses icon in the bookmarks bar triggers Apple's original Reading List feature, which saves the currently displayed webpage for later reading. This list of webpages is (or rather, will be) synchronized with Safari in iOS 5. Saved pages emerge in the sidebar, accompanied by unattractively scaled favicons.

    Safari's Reading List:  reclaim webpages to read later. (High-resolution favicons recommended.)Safari's Reading List: reclaim webpages to read later. (High-resolution favicons recommended.)

    Reading List follows in the not much dubious footsteps of other Apple products that own clearly been "inspired," let's say, by well-liked third-party services. As was the case when Safari added rudimentary back for RSS, Reading List is unlikely to dislodge users who are already restful with their existing read-it-later service.

    But most people own never even heard of such a thing. Reading List's prominent placement in Safari will certainly spread awareness. This could translate into more customers for competing services, even as Reading List takes the lion's share (sorry) of users.

    One final note on applications. The Finder, Mail, Safari, TextEdit, and even Terminal bar nothing back full-screen mode and restore bar nothing their windows when relaunched. Apple is definitely trying to lead by example.

    Grab bag

    As this review winds down, let's relax with a Little souse into the aged grab bag, a grand tradition where the smaller features win their chance to shine. As in years past, Apple has its own, much snazzier and more complete incarnation. Check it out if you want a broader overview of Lion's original features. These are just the ones that piqued my interest.

    System Preferences

    System Preferences own been shuffled, consolidated, and renamed in every major releases of Mac OS X. Lion doesn't disappoint.

    The preference formerly known as Appearance is now called General, and it includes a checkbox to globally disable application condition restoration. The Exposé & Spaces preference is now called Mission Control. Security becomes Security & Privacy. Accounts is now Users & Groups—a welcome change because, in my experience, most people don't know what an "account" is. Universal Access moves to the top row. And on and on. Dance, icons, dance!

    Your favorite system preferences: where are they today? Enlarge / Your favorite system preferences: where are they today?

    Individual preference icons can live manually hidden by the user thanks to the original "Customize…" menu item. (They will remain accessible from the View menu and via search.)

    Hide the preferences you're not interested in Enlarge / camouflage the preferences you're not interested in

    Click and hold on the "Show All" button to quickly jump from one preference to another via a drop-down menu. The View menu provided the very functionality in Snow Leopard, but the "Show All" button is closer to where the cursor is likely to be.

    Take a direct flight to your next preference paneTake a direct flight to your next preference pane

    Perhaps surprisingly, the MobileMe preference remains. It's joined by the new, awkwardly named Mail, Contacts & Calendars preference which manages, well, mail, contacts, and calendar accounts for a variety of online services.

    Centralized online service account management Centralized online service account management

    This includes the ever-popular "Other" service, which leads to a set of more generic configuration screens for other protocols and applications.

    Manual configuration and more esoteric account typesManual configuration and more esoteric account types

    The trackpad preference pane allows some, but not bar nothing of the original gestures in Lion to live configured in limited ways. For example, the Mission Control gesture must always live an upward swipe, but it can utilize three or four fingers. bar nothing of the gestures can live disabled.

    Limited choices for gesture configurationsLimited choices for gesture configurations

    Finally, in case you needed any more evidence of Apple's newfound aversion to color in the Mac OS X interface, prefer a ascertain at the original time zone selection screen.

    Your world,  bar  nothing silvery in the moonshineYour world, bar nothing silvery in the moonshine Auto-correction

    Lion adds optional iOS-style auto-correction to the measure Mac OS X text control. It looks and works just dote the iOS incarnation from which it's so clearly derived. dote the other spelling and grammar checking options, auto-correction can live enabled on a per-document basis.

    I eagerly await the Compose Text Automatically optionI eagerly await the Compose Text Automatically option System-wide auto-correction: try to resist the  prod to tap the screenSystem-wide auto-correction: try to resist the prod to tap the screen Mobile Time Machine

    Time Machine isn't much cheer when you're on the road with your laptop. nothing of Apple's portable Macs comprise more than one internal drive, and making a Time Machine back up to another partition of the very drive kindly of defeats the purpose.

    Lion includes a new, mostly invisible feature whereby Time Machine backups continue even when the backup volume is not mounted. This feature is only vigorous for laptops, which is a shame (though you can enable it on desktops using the tmutil command-line tool).

    The implementation is strange. The mtmfs (Mobile Time Machine file system) daemon runs an NFS server on localhost which is then mounted at /Volumes/MobileBackups. In it, you'll find the accustomed Backups.backupdb directory structure that Time Machine creates for its backups. The actual copies of original and changed files—and only those files—are stored in /.MobileBackups by the mtmd daemon.

    This system provides some basic data protection for users on the go, beyond what's offered by applications that back Lion's autosave APIs. Mobile Time Machine, dote regular Time Machine, tracks bar nothing file changes, not just those made by unavoidable applications.

    There is some obvious overlap between Mobile Time Machine and the generational store used to back document versioning in Lion. Having two entirely sever storage locations and techniques for backup copies of files is suboptimal; perhaps the backends for these two features will merge in the future.

    Lock screen

    Lion's original lock screen has been restyled to match the login screen, with options to unlock or switch users, and it comes with the very subset of menu bar status icons visible in the top-right corner.

    Lion's  original lock screenLion's original lock screen Emoji

    Lion adds Emoji back to Mac OS X. So that happened.

    FACE WITH NO  satisfactory gesture (U+1F645); MOON VIEWING CEREMONY (U+1F391); PILE OF POO (U+1F4A9)FACE WITH NO satisfactory gesture (U+1F645); MOON VIEWING CEREMONY (U+1F391); PILE OF POO (U+1F4A9) Terminal

    The Terminal application gets a few more graphical frills, sporting a original parameter for window blur, with sever settings for vigorous and inert windows. The bundled Silver Aerogel theme demonstrates the effect.

    "I want to know what's behind my terminal window, but I don't want to know every detail.""I want to know what's behind my terminal window, but I don't want to know every detail."

    Terminal also—finally—supports 256 text colors with its original xterm-256color terminal type. Users of terminal-based text editors will surely approve.

    About This Mac

    The System Profiler application has been renamed System Information and now includes a comprehensive, easy to understand overview of the entire system. The copious links to back documents, pertinent preferences, and channels for feedback are fantastic. This will live the original go-to location for anyone trying to remotely diagnose a Mac problem. As before, it's most easily accessed by going to the Apple menu and selecting About This Mac, then clicking the "More Info…" button.

    Don't worry, geeks, the aged System Profiler interface with its much more detailed technical information is soundless accessible via the "System Report…" button. But it's likely that you'll rarely exigency the extra detail. prefer a ascertain at what the original screens offer.

    Tech specs never looked so goodTech specs never looked so good Did you know that your  panoply has a manual?Did you know that your panoply has a manual? There sure seems to  live a lot of "other"There sure seems to live a lot of "other" Unfilled RAM slots are sinful. I am ashamed.Unfilled RAM slots are sinful. I am ashamed. Five ways to  win supportFive ways to win support An excellent executive summary of warranty information and service optionsAn excellent executive summary of warranty information and service options Recommendations Want an eBook or PDF copy? back Ars and it's yours.

    Even at Ars Technica, a unavoidable percentage of readers just want to know the bottom line about a original operating system. Is this a satisfactory release? Is it worth the cost and the hassle of installing it? Excluding the first few dog-slow, feature-poor releases of Mac OS X, the retort to bar nothing those questions has always been a resounding "yes." Lion continues this tradition, more than earning its $29 cost with a raft of original technologies and a substantially revised interface and suite of bundled applications.

    The measure caveats apply about software and hardware compatibility. Don't just hurry out and upgrade your system as soon as you finish this review. Lion's digital distribution makes hasty upgrades even more likely. Patience! prefer a few days—weeks, even—to research bar nothing of your favorite applications and originate sure they bar nothing hurry fine on Lion. If you're soundless using some PowerPC applications, don't upgrade until you own replaced them with Intel-native alternatives. And before you upgrade, back up, back up, back up.

    All that you can't leave behind

    Though the Lion title suggests the conclude of something, the content of the operating system itself clearly marks the start of a original journey. Seemingly emboldened by the success of iOS, Apple has taken a hatchet to decades of conventional wisdom about desktop operating systems.

    The very thing happened ten years ago in an even more histrionic fashion when Apple replaced classic Mac OS with Mac OS X. The original operating system changed the rules on the desktop, wedding composited graphics, smooth animation, and photorealistic artwork to a solid Unix foundation. Apple tried to leave bar nothing vestiges of its aged operating system behind—the platinum appearance, the Apple menu, even the desktop itself—but eventually bowed to some demands of long-time Mac users. Lion's changes will no doubt meet with similar resistance from experienced Mac users, but I suspect Apple will remain unmoved this time around.

    In the very artery that Mac OS X so clearly showed the repose of the industry what user interfaces would ascertain dote in the years to come, Apple's own iOS has now done the very for its decade-old desktop operating system. iOS was less shocking to users because it appeared to approach from nothing, and the mobile operating system conventions it defied were ones that nobody liked anyway. The very is not staunch on the desktop, where users cling dote victims of Stockholm syndrome to mechanics that own torment them time and again.

    It may live many years before even half of the applications on a typical Mac behave according to the design principles introduced in Lion. The transition period could live ugly, especially compared to the effortless uniformity of iOS. In the meantime, let Apple's younger platform serve as a lighthouse in the storm. The Mac will always live more capable than its mobile brethren, but that doesn't stand for that simple tasks must furthermore live harder on the Mac. Imagine being able to stick a computer neophyte in front of an iMac with the very self-confidence that you might hand that neophyte an iPad today.

    The technical details of Apple's operating system that were once so well-known that they practically defined its being (e.g., remembrance protection, preemptive multitasking) are now taken for granted. Mainstream reviews of software and hardware alike expend far less time pondering technical specifications and implementation details than they did only a few years ago.

    This phenomenon extends even to the geekiest among us, those who didn't just skip to the conclusion of this review but actually read the entire thing. Fellow geeks, hope yourselves, finish you know the clock hurry of the CPU in the device you're reading this on? finish you know how much RAM it has? What about the remembrance bus hurry and width? Now consider what your answers might own been ten years ago.

    Over the past decade, better technology has simply reduced the number of things that they exigency to custody about. Lion is better technology. It marks the point where Mac OS X releases cease being defined by what's been added. From now on, Mac OS X should live judged by what's been removed.



    Direct Download of over 5500 Certification Exams

    3COM [8 Certification Exam(s) ]
    AccessData [1 Certification Exam(s) ]
    ACFE [1 Certification Exam(s) ]
    ACI [3 Certification Exam(s) ]
    Acme-Packet [1 Certification Exam(s) ]
    ACSM [4 Certification Exam(s) ]
    ACT [1 Certification Exam(s) ]
    Admission-Tests [13 Certification Exam(s) ]
    ADOBE [93 Certification Exam(s) ]
    AFP [1 Certification Exam(s) ]
    AICPA [2 Certification Exam(s) ]
    AIIM [1 Certification Exam(s) ]
    Alcatel-Lucent [13 Certification Exam(s) ]
    Alfresco [1 Certification Exam(s) ]
    Altiris [3 Certification Exam(s) ]
    Amazon [2 Certification Exam(s) ]
    American-College [2 Certification Exam(s) ]
    Android [4 Certification Exam(s) ]
    APA [1 Certification Exam(s) ]
    APC [2 Certification Exam(s) ]
    APICS [2 Certification Exam(s) ]
    Apple [69 Certification Exam(s) ]
    AppSense [1 Certification Exam(s) ]
    APTUSC [1 Certification Exam(s) ]
    Arizona-Education [1 Certification Exam(s) ]
    ARM [1 Certification Exam(s) ]
    Aruba [6 Certification Exam(s) ]
    ASIS [2 Certification Exam(s) ]
    ASQ [3 Certification Exam(s) ]
    ASTQB [8 Certification Exam(s) ]
    Autodesk [2 Certification Exam(s) ]
    Avaya [96 Certification Exam(s) ]
    AXELOS [1 Certification Exam(s) ]
    Axis [1 Certification Exam(s) ]
    Banking [1 Certification Exam(s) ]
    BEA [5 Certification Exam(s) ]
    BICSI [2 Certification Exam(s) ]
    BlackBerry [17 Certification Exam(s) ]
    BlueCoat [2 Certification Exam(s) ]
    Brocade [4 Certification Exam(s) ]
    Business-Objects [11 Certification Exam(s) ]
    Business-Tests [4 Certification Exam(s) ]
    CA-Technologies [21 Certification Exam(s) ]
    Certification-Board [10 Certification Exam(s) ]
    Certiport [3 Certification Exam(s) ]
    CheckPoint [41 Certification Exam(s) ]
    CIDQ [1 Certification Exam(s) ]
    CIPS [4 Certification Exam(s) ]
    Cisco [318 Certification Exam(s) ]
    Citrix [47 Certification Exam(s) ]
    CIW [18 Certification Exam(s) ]
    Cloudera [10 Certification Exam(s) ]
    Cognos [19 Certification Exam(s) ]
    College-Board [2 Certification Exam(s) ]
    CompTIA [76 Certification Exam(s) ]
    ComputerAssociates [6 Certification Exam(s) ]
    Consultant [2 Certification Exam(s) ]
    Counselor [4 Certification Exam(s) ]
    CPP-Institue [2 Certification Exam(s) ]
    CPP-Institute [1 Certification Exam(s) ]
    CSP [1 Certification Exam(s) ]
    CWNA [1 Certification Exam(s) ]
    CWNP [13 Certification Exam(s) ]
    Dassault [2 Certification Exam(s) ]
    DELL [9 Certification Exam(s) ]
    DMI [1 Certification Exam(s) ]
    DRI [1 Certification Exam(s) ]
    ECCouncil [21 Certification Exam(s) ]
    ECDL [1 Certification Exam(s) ]
    EMC [129 Certification Exam(s) ]
    Enterasys [13 Certification Exam(s) ]
    Ericsson [5 Certification Exam(s) ]
    ESPA [1 Certification Exam(s) ]
    Esri [2 Certification Exam(s) ]
    ExamExpress [15 Certification Exam(s) ]
    Exin [40 Certification Exam(s) ]
    ExtremeNetworks [3 Certification Exam(s) ]
    F5-Networks [20 Certification Exam(s) ]
    FCTC [2 Certification Exam(s) ]
    Filemaker [9 Certification Exam(s) ]
    Financial [36 Certification Exam(s) ]
    Food [4 Certification Exam(s) ]
    Fortinet [12 Certification Exam(s) ]
    Foundry [6 Certification Exam(s) ]
    FSMTB [1 Certification Exam(s) ]
    Fujitsu [2 Certification Exam(s) ]
    GAQM [9 Certification Exam(s) ]
    Genesys [4 Certification Exam(s) ]
    GIAC [15 Certification Exam(s) ]
    Google [4 Certification Exam(s) ]
    GuidanceSoftware [2 Certification Exam(s) ]
    H3C [1 Certification Exam(s) ]
    HDI [9 Certification Exam(s) ]
    Healthcare [3 Certification Exam(s) ]
    HIPAA [2 Certification Exam(s) ]
    Hitachi [30 Certification Exam(s) ]
    Hortonworks [4 Certification Exam(s) ]
    Hospitality [2 Certification Exam(s) ]
    HP [746 Certification Exam(s) ]
    HR [4 Certification Exam(s) ]
    HRCI [1 Certification Exam(s) ]
    Huawei [21 Certification Exam(s) ]
    Hyperion [10 Certification Exam(s) ]
    IAAP [1 Certification Exam(s) ]
    IAHCSMM [1 Certification Exam(s) ]
    IBM [1530 Certification Exam(s) ]
    IBQH [1 Certification Exam(s) ]
    ICAI [1 Certification Exam(s) ]
    ICDL [6 Certification Exam(s) ]
    IEEE [1 Certification Exam(s) ]
    IELTS [1 Certification Exam(s) ]
    IFPUG [1 Certification Exam(s) ]
    IIA [3 Certification Exam(s) ]
    IIBA [2 Certification Exam(s) ]
    IISFA [1 Certification Exam(s) ]
    Intel [2 Certification Exam(s) ]
    IQN [1 Certification Exam(s) ]
    IRS [1 Certification Exam(s) ]
    ISA [1 Certification Exam(s) ]
    ISACA [4 Certification Exam(s) ]
    ISC2 [6 Certification Exam(s) ]
    ISEB [24 Certification Exam(s) ]
    Isilon [4 Certification Exam(s) ]
    ISM [6 Certification Exam(s) ]
    iSQI [7 Certification Exam(s) ]
    ITEC [1 Certification Exam(s) ]
    Juniper [63 Certification Exam(s) ]
    LEED [1 Certification Exam(s) ]
    Legato [5 Certification Exam(s) ]
    Liferay [1 Certification Exam(s) ]
    Logical-Operations [1 Certification Exam(s) ]
    Lotus [66 Certification Exam(s) ]
    LPI [24 Certification Exam(s) ]
    LSI [3 Certification Exam(s) ]
    Magento [3 Certification Exam(s) ]
    Maintenance [2 Certification Exam(s) ]
    McAfee [8 Certification Exam(s) ]
    McData [3 Certification Exam(s) ]
    Medical [69 Certification Exam(s) ]
    Microsoft [368 Certification Exam(s) ]
    Mile2 [2 Certification Exam(s) ]
    Military [1 Certification Exam(s) ]
    Misc [1 Certification Exam(s) ]
    Motorola [7 Certification Exam(s) ]
    mySQL [4 Certification Exam(s) ]
    NBSTSA [1 Certification Exam(s) ]
    NCEES [2 Certification Exam(s) ]
    NCIDQ [1 Certification Exam(s) ]
    NCLEX [2 Certification Exam(s) ]
    Network-General [12 Certification Exam(s) ]
    NetworkAppliance [36 Certification Exam(s) ]
    NI [1 Certification Exam(s) ]
    NIELIT [1 Certification Exam(s) ]
    Nokia [6 Certification Exam(s) ]
    Nortel [130 Certification Exam(s) ]
    Novell [37 Certification Exam(s) ]
    OMG [10 Certification Exam(s) ]
    Oracle [269 Certification Exam(s) ]
    P&C [2 Certification Exam(s) ]
    Palo-Alto [4 Certification Exam(s) ]
    PARCC [1 Certification Exam(s) ]
    PayPal [1 Certification Exam(s) ]
    Pegasystems [11 Certification Exam(s) ]
    PEOPLECERT [4 Certification Exam(s) ]
    PMI [15 Certification Exam(s) ]
    Polycom [2 Certification Exam(s) ]
    PostgreSQL-CE [1 Certification Exam(s) ]
    Prince2 [6 Certification Exam(s) ]
    PRMIA [1 Certification Exam(s) ]
    PsychCorp [1 Certification Exam(s) ]
    PTCB [2 Certification Exam(s) ]
    QAI [1 Certification Exam(s) ]
    QlikView [1 Certification Exam(s) ]
    Quality-Assurance [7 Certification Exam(s) ]
    RACC [1 Certification Exam(s) ]
    Real-Estate [1 Certification Exam(s) ]
    RedHat [8 Certification Exam(s) ]
    RES [5 Certification Exam(s) ]
    Riverbed [8 Certification Exam(s) ]
    RSA [15 Certification Exam(s) ]
    Sair [8 Certification Exam(s) ]
    Salesforce [5 Certification Exam(s) ]
    SANS [1 Certification Exam(s) ]
    SAP [98 Certification Exam(s) ]
    SASInstitute [15 Certification Exam(s) ]
    SAT [1 Certification Exam(s) ]
    SCO [10 Certification Exam(s) ]
    SCP [6 Certification Exam(s) ]
    SDI [3 Certification Exam(s) ]
    See-Beyond [1 Certification Exam(s) ]
    Siemens [1 Certification Exam(s) ]
    Snia [7 Certification Exam(s) ]
    SOA [15 Certification Exam(s) ]
    Social-Work-Board [4 Certification Exam(s) ]
    SpringSource [1 Certification Exam(s) ]
    SUN [63 Certification Exam(s) ]
    SUSE [1 Certification Exam(s) ]
    Sybase [17 Certification Exam(s) ]
    Symantec [134 Certification Exam(s) ]
    Teacher-Certification [4 Certification Exam(s) ]
    The-Open-Group [8 Certification Exam(s) ]
    TIA [3 Certification Exam(s) ]
    Tibco [18 Certification Exam(s) ]
    Trainers [3 Certification Exam(s) ]
    Trend [1 Certification Exam(s) ]
    TruSecure [1 Certification Exam(s) ]
    USMLE [1 Certification Exam(s) ]
    VCE [6 Certification Exam(s) ]
    Veeam [2 Certification Exam(s) ]
    Veritas [33 Certification Exam(s) ]
    Vmware [58 Certification Exam(s) ]
    Wonderlic [2 Certification Exam(s) ]
    Worldatwork [2 Certification Exam(s) ]
    XML-Master [3 Certification Exam(s) ]
    Zend [6 Certification Exam(s) ]





    References :


    Dropmark : http://killexams.dropmark.com/367904/12028231
    Dropmark-Text : http://killexams.dropmark.com/367904/12916285
    Blogspot : http://killexamsbraindump.blogspot.com/2018/01/pass4sure-9l0-063-real-question-bank.html
    Blogspot : http://killexams-braindumps.blogspot.com/2018/01/kill-your-9l0-063-exam-at-first-attempt.html
    Wordpress : https://wp.me/p7SJ6L-2xM
    Box.net : https://app.box.com/s/ncrcj4fc49ymqvssz3hwrni7dooom3ld






    Back to Main Page

    www.pass4surez.com | www.killcerts.com | www.search4exams.com | http://www.jeepmansoffroad.com/