Realm Of The Ruthless Mac OS

Realm Of The Ruthless Mac OS

Realm Of The Ruthless Mac Os X
Realm Of The Ruthless Mac Os 11
Realm Of The Ruthless Mac Os Catalina
Realm Of The Ruthless Mac Os Download
Trusted Mac download Nightmare Realm: In the End. Virus-free and 100% clean download. Get Nightmare Realm: In the End. Alternative downloads. One's a ruthless businessman turned. Er, even more ruthless businessman. Veiled threats to start offering Mac OS-based systems might seem like a cheesy way to get a better deal from.
Realm Of The Ruthless Mac Os XKerberos Preferences on Mac OS X 10.4 and 10.5 Documentation
This web page discusses the edu.mit.Kerberos (Kerberos configuration)file: what's in it, where it goes, and how to configure it for distribution atyour site.
The information on this page applies to Mac OS X 10.4 and 10.5 only. For links to preferencesdocumentation for other Mac OS versions, go here.
The edu.mit.Kerberos FileThe edu.mit.Kerberos file is where the Kerberos v4 and v5 configuration information isstored on Mac OS X. Formerly the Kerberos Login Library and Kerberos management applicationpreferences were stored in it, but they now have their own preference files: edu.mit.Kerberos.KerberosLogin.plistand edu.mit.Kerberos.KerberosApp.plist.
The edu.mit.Kerberos file stores this information in its datafork, which contains the realm and server configurationinformation (the info that would be found in the krb5.conf file onUnix). See the Kerberos Configuration File Format section for moreinformation.
On some systems there may up to three configuration files - two edu.mit.Kerberos filesin the 'system' and 'user' locations, and KfM now acceptsthe standard Unix location and name of /etc/krb5.conf for the configuration file as well.Some settings in the edu.mit.Kerberos.KerberosLogin.plist file can override settingsin the edu.mit.Kerberos as well. See the edu.mit.Kerberos FileLocations section for more information about why this is so.
Setting up a Configuration File Quick GuideWe recommend that you read this entire page. However, if you are in a hurry toget Kerberos for Macintosh up and working:
You need to create an edu.mit.Kerberos file in the /Library/Preferences directory which contains the realm and server configuration information for your site, although:
if your site supports DNS configuration of Kerberos realms, you may not need a configuration file, or at least not a complete one - see the About DNS Configuration section;
if you upgraded from a previous version of Mac OS X which was using Kerberos successfully, you probably already have a properly configured file and no changes are necessary;
if you've run the Mac OS X Kerberos Extras installer, you will already have a file in the correct place, but which contains MIT configuration information (which is provided as a guideline);
if you have a functioning Mac OS 9.x Kerberos installation, you can simply copy the Kerberos Preferences file from the Kerberos folder in Application Support from your Mac OS 9 volume to the /Library/Preferences on your Mac OS X volume, and rename it to edu.mit.Kerberos.
If you do not have an edu.mit.Kerberos file:
Launch the Kerberos application (/System/Library/CoreServices/Kerberos).
Choose Edit Realms.. from the Edit menu.
Use the edit realms dialog to enter information about your site's realm. See the Kerberos Configuration section for information on what the various fields mean.
Note - while there may also be an edu.mit.Kerberos file in your/Users/username/Library/Preferences directory, you should placeyour configuration information in the /Library/Preferenceslocation. (See edu.mit.Kerberos File Locations for moredetails.)
edu.mit.Kerberos File LocationsKerberos for Macintosh supports and looks for its configuration file in three locations -two are standard locations and the third for Unix compatibility:
/Library/Preferences/edu.mit.Kerberos - the standard 'system' location that contains the configuration to be used by all users of the computer,
/Users/username/Library/Preferences/edu.mit.Kerberos - the standard 'user' location containing additional configuration for an individual user,
/etc/krb5.conf - the Unix compatibility location. Any configuration file in this location will also apply to all users of the computer.
The typical case is to have the Kerberos configuration information inthe standard system configuration file, and no user configurationfile or Unix compatibility file.
However there may be circumstances where a user wants to have additionalrealm and server information not shared with other users on the same machine.You can add any additional realm and server configuration information to theuser configuration file, and KfM will meld the two sets of informationtogether. You should avoid duplicate realm entries - if you have the sameentry with different information in different configuration files, the behavior isnot defined and you may get unexpected results. 
If the user wants to have additional items in the [libdefaults] section,it's important to be aware of the order in which KfM reads the configuration files,because in case of conflicting [libdefaults] entries, the entry readfirst is the one that KfM will use (this is different from the situation with realmentries, which are merged). KfM first reads the configuration file in the user location, then the onein the system location, and finally the Unix compatibility location.
Similarly, if there is a configuration file in the Unix compatibility location,KfM will attempt to meld those the information in it together with any otherconfiguration files present, with behavior as described above.
Having just a user configuration file and no system configuration file is not asupported setup. For instance, getting Kerberos tickets at login time will not workif you only have a user configuration file. The Mac OS X login window will not read the user configuration file.
Note: some settings in the edu.mit.Kerberos.KerberosLogin.plist, theKerberos Login Library preferences file, can effectively override settings inthe edu.mit.Kerberos file.These settings can be modified using the Kerberos GUI management application/System/Library/Coreservices/Kerberos .
Generally, site settings go in the /Library/Preferences/edu.mit.Kerberos file, anduser settings will go into ~/Library/Preferences/edu.mit.Kerberos.KerberosLogin.plist(via changing settings in Kerberos.app). The Kerberos Login preferences exist so that the user can changetheir ticket management preferences without changing those preferences for every user on the machine.One user might always want addressless tickets, but another user might not. 
In addition, there are some options which cannot be set with the [libdefaults]section of the edu.mit.Kerberos file. For instance, there is no edu.mit.Kerberos file preference to set the default ticket lifetime - despite config files which claimthere is a 'ticket_lifetime' tag, no code actually looks for it. 
Kerberos Configuration InformationA Kerberos configuration is made up of a list of realms and a list of domain->realm mappings.
Each realm entry contains a list of servers and a default domain for the realm. Each type of server has a different purpose. 'kdc' servers are used to obtain tickets. 'admin' servers are used to perform administrator operations, such as running kadmin. At most sites there will only be one admin server per Kerberos realm. 'kpasswd' servers are used to change your password, although the admin server will be used if no kpasswd server is listed. 'krb524' servers are used to get v4 tickets from v5 tickets and are only used by v5 realms.
If the realm and site DNS domain are different, there will also be domain to realm mappings. For instance, if you have a domain-realm mapping '.mydepartment.mysite.com = MYSITE.COM' and try to contact a server such as 'myprinter.mydepartment.mysite.com', Kerberos will know to contact the realm 'MYSITE.COM' rather than the default, 'MYDEPARTMENT.MYSITE.COM'.
The Kerberos Configuration File Format The Kerberos v4 and v5 configurations are stored in the data fork of edu.mit.Kerberos.

This text is similar to that of krb5.conf on Unix machines or krb5.ini on Windows machines. The configuration tells Kerberos for Macintosh what realms exist,what Kerberos versions are supported by them, and where to find the servers. You shouldedit this file for your site by opening the edu.mit.Kerberos file in a text editor that will save the file as pure text again, ie: BBEdit, emacs, or CodeWarrior; but not TextEdit (unlessyou use the 'Make Plain Text' command) or Microsoft Word.
Once you are done editing the edu.mit.Kerberos file, you should log out,and then you may want to use the Edit Favorite Realmsfeature of the Kerberos management application to add your realms to the pop-up menu in the Login dialog. 
 Here is an example Kerberos configuration: 
The [libdefaults] section describes what the default behavior of the Kerberos libraries should be. You should always fill in the default realm. If you have Kerberos v5 at your site, you should also copy any other [libdefaults] from your site'skrb5.conf or krb5.ini.
Kerberos for Macintosh 5.5 now honors ticket_lifetime entries in[libdefaults] . However, if you have set a ticket lifetime default in the GUI Kerberos managementapplication preferences, it will override this value.
The [realms] and [domain_realm] sections refer to Kerberos v5 realms.If your site is v4-only you should omit these sections. Otherwise just copy these sections fromyour site's krb5.conf or krb5.ini.
The [v4 realms] and [v4 domain_realm] sections refer to Kerberos v4 realms. If your site is v5-only you should omit these sections. Otherwise you will need tocreate entries for each of the Kerberos v4 realms at your site. You should not specify astring_to_key_type for v4 realms anymore, because that information will be ignored - KfMwill automatically determine the correct one to use.
DNS ConfigurationSome sites have configured their DNS servers to provide information about local Kerberos realmconfiguration, such that users need only a minimum configuration file and instead can getthe rest of the Kerberos configuration information over the network.For more information about DNS, see the Using DNSsection of the Kerberos V5 System Administrator's Guide.
You should always have a configuration file that has a [libdefaults] sectionwith a default_realm specified. Otherwise, getting Kerberos tickets at logintime may fail.
If your Kerberos realm is named the same as your domain name, e.g. your domain name = foo.bar.edu andyour Kerberos realm = FOO.BAR.EDU, you do not need any more information in your local configurationfile, assuming all the realms you need to access have DNS records.
Otherwise, you also need a [domain_realm] section, mapping your domain to the appropriaterealms. You can omit the [realms] sections of the configuration file.
DNS configuration of realms only applies to Kerberos v5, so unless your site does krb524 on the server,you will need to include v4 information in a local configuration file.
If you want to disable DNS lookup of Kerberos realms on your Macintosh, uncheck the 'Configure additional realms automatically using DNS' checkbox in the Kerberos application's edit realms dialog or add the line:
to the [libdefaults] section of your Kerberos configuration file.
Palm had started as a software company that decided to make its own PDA because nobody else saw what Palm's founders did. Palm dominated the PDA world and was one of the strongest players in the smartphone realm as well. So what went wrong?
Palm Lost Its WayTo put it simply, Palm got it right when it went into the PDA business, because it's very nice Graffiti software was not at its best when running on other people's hardware (see Part 1). Besides, all the early PDAs were huge compared with the pocketable device Palm founder Jeff Hawkins wanted to make.
Hawkins did it, and the original PalmPilot redefined the entire PDA industry in 1996 (see Part 2). In 1997, Palm introduced improved models and Palm OS 2.0. In 1998, the Palm III and Palm OS 3.0.
Then Palm got stuck. Palm OS 4.0 didn't arrive until March 2001. Palm OS 5 arrived with the Palm Tungsten in October 2003, which also marking a switch from Motorola DragonBall CPUs to ARM processors and the complete separation of PalmSource (the Palm OS company) from Palm (the hardware company), which we'll discuss below.
HandspringPalm introduced the Palm III and Palm OS 3.0 in 1998, and then most of its founders left to form Handspring, a new company that would license the Palm OS and do what Palm wouldn't (see Part 3). If they'd stuck around, maybe Palm OS 4.0 would have come about in 1999 – or at least 2000.
In 1999, we got the Handspring Visor, which used a tweaked version of Palm OS 3.1. While Palm was slowly improving its hardware, Handspring was inventing its first smartphone, the Treo 180, which debuted in 2002.
Palm Acquires BeOSAfter he left Apple in 1990, Jean Louis Gassée founded Be Inc. with the dream of creating a next generation operating system. A number of Apple employees followed him.
BeOS was optimized for multiple processors, pervasive multithreading, and preemptive multitasking. BeOS was written from the ground up to be a multimedia operating system that would keep the sound and video going no matter what else the computer was doing.
BeOS was initially designed for a dual-processor computer Be planned to build around a pair of AT&T Hobbit processors. Instead, Be chose the PowerPC 603 as its CPU for the BeBox. The BeBox debuted on October 1996 at 66 MHz, and in August 1997, speed was doubled to 133 MHz.
BeOS was ported to the Mac, and in January 1998, BeBox production was halted so the company could focus on its OS and software for BeOS. From all I've heard, BeOS succeeded in being remarkably stable and resilient, although little software was written for it. Power Computing licensed BeOS and began bundling it with its Mac clones in 1997. I know that Motorola looked into licensing BeOS for its StarMax clones, but I don't know if anything ever came of it.
Also in 1997, Apple was looking for a new operating system to replace the Classic Mac OS. Apple's Copland project was a bust, and it was down to BeOS and NeXTstep – both companies founded by former Apple executives. Apple was strongly interested in BeOS but thought Gassée's asking price was too high. In the end, Apple acquired NeXT, Steve Jobs returned to Apple, and Mac OS X eventually emerged.
This soured things between Be and Apple, and by March 1998, BeOS was ported to Intel x86 architecture. BeOS for Macs was never updated to support the PowerPC G3 or later CPUs. Regardless, they Be couldn't interest enough people in BeOS to sustain development, and in 2001 Be was acquired by Palm.
Realm Of The Ruthless Mac Os 11BeOS went to PalmSource, along with the Palm OS, when Palm separated its hardware and OS divisions permanently in October 2003. PalmSource hoped to use BeOS as the foundation of its next generation operating system, Palm OS 6.
PalmSource: ARMed and DangerousCoordinating the efforts of theoretically separate hardware and software companies became something of a challenge when Palm decided that DragonBall, topping out at 33 MHz, no longer had the power to remain competitive, so it chose to migrate its hardware to ARM processors. The hardware switch by Palm meant that PalmSource had to port or rewrite the Palm OS for ARM chips.
On the technical side, the original Palm OS had been built with the AMX Real Time Operating System (RTOS) as its core. Kadak had its AMX RTOS available for several different CPU families at the time – Intel 8086 and 384/466, PowerPC, MIPS, and Motorola 68000, which was used for Palm OS 1-4.
As Thom Holwerda explains on osNews, Palm customized AMX 68000, removing any feature it didn't deem necessary, and preemptive multitasking was one of them. Palm never saw the need to make Palm OS on DragonBall a multitasking operating system, which is part of the reason Palm OS 1-4 are so responsive – it only runs one program at a time.
When Palm moved to ARM and Palm OS 5, it could have switched to the AMX 4-ARM kernel but instead chose to create its own kernel. The new kernel provided 'more or less the same functionality' as the old one, but this time with hopes of extending it in the future. Palm OS 5 was first used on the Palm Tungsten T, released in November 2002.
Yes, There Really was a Palm OS 6PalmSource announced its plans to release Palm OS 6 Cobalt in Late 2003, but it wasn't available until January 2004. Many features in Cobalt were derived from BeOS. Palm OS 6 was available to Palm OS licensees, but not a single one adopted it for a shipping product.
PalmSource officially became a subsidiary of Palm in January 2002, and in October 2003, it became a completely separate entity.
The Founders Have Returned!The best thing that happened to Palm after losing its founders to Handspring was the merger of the two companies starting in June 2003 and taking the rest of the year to complete. This brought back Jeff Hawkins, Donna Dubinski, and Ed Colligan, the trio behind the first PalmPilot who had left Palm (then a division of 3Com) in June 1998 to found Handspring.
Unfortunately, it was already too late. Let's take a look at the sequence of events:
March 1998. Palm OS 3 released.
July 1998. Hawkins, Dubinski, and Colligan leave Palm.
March 2001. Palm OS 4 released three years after Palm OS 3.
July 2001: Palm publicly announces plans to switch to ARM processors.
August 2001: PalmSource acquires BeOS.
January 2002: PalmSource created as a subsidiary of Palm.
November 2002: ARM-based Palm Tungsten T ships with a 144 MHz TI OMAP ARM processor and Palm OS 5.
June 2003: The founders return to Palm.
October 2003: PalmSource becomes independent
January 2004: PalmSource makes Palm OS 6 cobalt available. No takers.
By the time the founders returned, the handwriting was on the wall. Palm had already committed to the separation of hardware and OS, and PalmSource was working to deliver Palm OS 6 by the end of 2003.
Sony Kills the CliéThe Sony Clié PEG-UX50 was very un-Palm-like.
Sony became a Palm licensee in 2000, and its Clié line of PDAs stood apart from the pack with a focus on multimedia. During Summer 2004, Sony pulled back its marketing, selling Clié products only in Japan. In Spring 2005, Sony pulled the plug on the Palm OS its Clié hardware.
For an overview of the Clié line, see Looking Back at Sony's Clié Series: An iPhone for an iPhone-less World, Damien McFerran, Know Your Mobile, 2015.02.23.
From PDA Maker to Smartphone MakerPalm switched its focus from PDAs to smartphones, which it saw was going to be a much bigger market. The last two PDAs released by Palm were the US$99 Palm Z22 and the tope-end Palm TX, both introduced in October 2005. Going forward, it would just be smartphones. The handwriting was on the wall; the PDA market was going to disappear as smartphones grew in number.
In reality, if not for its Treo smartphones, Palm probably would have been long gone by 2005.
Windows on a Treo?Palm did something thoroughly inconceivable in September 2005. It announced Palm hardware without the Palm OS. Specifically, Treos build around Windows Mobile.
It must have been to prove that they were a hardware company that was not wed to the Palm OS exclusively. I don't know what it said to Palm OS users, but I imagine they shook their collective heads.
The Palm 700w with CDMA, available in January 2006, ran Windows Mobile 5.0 on a lower resolution 240 x 240 pixel display – because Windows couldn't keep up at 320 x 320. The 700w was a Verizon exclusive in the US and a Vodaphone exclusive in the UK.
Palm also made the Treo 750v, a quad-band Windows Mobile 5.0 device sold exclusively in Europe.
In October 2006, Palm rolled out the CDMA Treo 700wx pretty much the same thing, but not a Verizon exclusive.
The next Windows Mobile model was the Treo 500v, which had the same size and styling as the Palm Centro, but with a 320 x 240 pix screen. It ran Windows Mobile 6.0 and shipped in February 2008.
The fourth Windows Mobile Treo, the 800w in Mid 2008, which was also CDMA-only and a Sprint exclusive in the US. It was the first Windows-based Palm with a 320 x 320 pixel display. It shipped with Windows Mobile 6.0.
On January 5, 2009, Palm introduced the Treo Pro, available in GSM and CDMA versions with Windows Mobile 6.1.
Was selling Treo smartphones with Windows Mobile a good idea? The world may never know, because in June 2009, Palm moved to a new operating system.
Palm Pre and webOSThe new Palm Pre (June 2009) ran webOS. Both the smartphone and the OS broke with Palm tradition.
The Palm Pre was Palm's first slider phone. The keyboard was out of sight until you slid it open. With the keyboard hidden, it looked a lot like an iPhone – it even had a 320 x 480 pixel display like the early iPhones, although a bit smaller at 3.1″ to the iPhone's 3.5″. The Pre was also a little smaller than the iPhone 3G. Many consider the Pre the first real competitor to Apple's iPhone.
The base model had 8 GB of storage, the later Pre Plus doubled that to 16 GB. There is no memory card slot.
At first, the Pre was a Sprint exclusive, and it became the best selling smartphone Sprint had carried to date. Estimates are that maybe 500,000 units were sold during the June-August quarter – along with 325,000 Palm OS 5 smartphones.
Brakes optional mac os. The Pre was the first device to use webOS, a new operating system from Palm (not PalmSource, which had been acquired by ACCESS in 2005 after the Palm OS 6 debacle). Where Palm OS 1-4 used AMX RTOS as its kernel, Palm OS 5 had been built upon a Palm-made kernel for ARM processors, and Palm OS 6 Cobalt had borrowed technologies from BeOS, Palm built webO on Linux. (That should sound familiar – Android is also build on Linux.)
As with BeOS, multitasking was built into webOS from the start (contrast this to the iPhone, which only has one truly active app at a time).
There were three major versions of webOS released:
webOS 1 in 2009 for the Pre, updated to 1.2.9.1 for Pixi, last version was 1.4.5.1
webOS 2 in 2010 for the Pre 2, udpated to 2.1.1 for HP Veer, to 2.2 for HP Pre 3, last version was 2.2.4
webOS 3 in 2011 for the HP TouchPad, last version was 3.0.5 on 2012.01.12, also used by LG on smart TVs
The second webOS smartphone from Palm was the Pixi, which had a candybar form factor rather than a slide-out keyboard. When it was launched on November 2009, it was the smallest smartphone on the market.
On April 28, 2010, HP announced that it would acquire Palm. The takeover was completed on July 1, 2010, and soon HP started rebranding devices. The Pixi was renamed the HP Veer in 2011, and the Pre3 was also an HP release. HP had big plans for webOS.
HP released its TouchPad tablet in July 2011 with a 9.7″ 1024 x 768 pixel display and webOS 3.0. It was aimed at the Apple iPad 2, which had the same screen size and pixel dimensions. Pricing was the same for both lines' non-cellular devices: $499 with 16 GB, $599 with 32 GB, and $699 with 64 GB. The TouchPad has a faster CPU and twice as much RAM.
webOS smartphones and tabletsRealm Of The Ruthless Mac Os CatalinaPalm Pre: 500 MHz ARM Cortex 8+ processor, 3.1″ screen, 3.2 MP camera, 256 KB RAM, 8 GB storage, 802.11g WiFi, webOS 1.0.2, launched 2009.06.06
Palm Pixi: same as Pre, but with 2.6″ 320 x 400 pixel display, 2.0 MP camera, no WiFi, launched 2009.11.15
Palm Pixi Plus: same as Pixi, but with 802.11g WiFi
Palm Pre Plus: 512 KB RAM, 16 GB storage, webOS 2010.01.25
Palm Pre 2: 1 GHz processor, 5 MP camera, webOS 2.0, Flash Player 10.1 Beta, first released 2010.10.22 in France
HP Veer: 800 MHz Scorpion processor, 5 MP camera, 8 GB storage, webOS 2.1.2, released 2011.05.15 at US$99 with 2-year mobile contract
HP TouchPad: 1.2 GHz or 1.5 GHz dual-core Scorpion processor, 1 MB RAM, 16/32/64 GB storage, 9.7″ 1024 x 768 pixel screen, webOS 3.0, launched 2011.07.01
HP Pre3: 1.4 GHz Qualcomm Snapdragon processor, 3.6″ screen, 8 or 16 GB storage, 802.11n WiFi, webOS 2.2.4, launched 2011.08.17 in UK.
HP TouchPad Go: 1.5 GHz dual-core Scorpion processor, 32 GB storage, 7″ display, never officially released
But webOS never took off. It was a good operating system, but there was only one company using it until LG adopted it for smart TVs.
On August 18, 2011, HP announced it was discontinuing all webOS devices including the Pre3. Yes, one day after it had been released.
On October 22, 2011, HP made Android 2.3 Gingerbread available for the TouchPad; users could select which operating system to run at startup. On January 17, 2012, a beta of Android 4.0 Ice Cream Sandwich became available.
After HP abandoned webOS, it was given to the Open Source community and relaunched as Open webOS.
What Killed Palm?A whole series of unfortunate events. 3Com was too slow in letting Palm become independent, and the formation of Handspring cost Palm leadership and direction. Licensing the Palm OS actually worked to Palm's benefit, but once PalmSource became a separate entity, its next generation Palm OS 6 Cobalt operating system was a dud.
Palm, the hardware company, developed webOS, and Palm was so confident that webOS was the future that it never released another Palm OS device. Palm needed that to be true, because its sales revenues had peaked in 2006 and had been falling almost continuously since mid 2007.
By the time the Pre shipped, Palm was a sinking ship. Not only was income low, but the year-over-year numbers were negative for most of 2007 and 2008 – and all of 2009. If HP hadn't acquired Palm in 2010, it may not have lasted out the calendar year. Even with HP's deep pockets, webOS was a bust. In August 2011, HP stopped trying to turn it into a success. They had to stem the blood loss.
Palm had bet the company on webOS and the Pre. It lost that bet.
Rest in peace, Palm, you made some great products that will long be remembered.
If you're a Palm user, consider joining our Palm OS Users group on Facebook.
Realm Of The Ruthless Mac Os DownloadIndex to A History of PalmIf you're a Palm user, please consider joining our new Palm OS Users group on Facebook to share your knowledge and provide user-to-user support.
Further ReadingPalm: I'm Ready to Wallow Now, Thom Holwerda, osNews, 2013.03.11
Six Months with the Pre: Real Review, Jonathan I Ezor#im, webOS Nationl, 2009.12.28
Ars Reviews the Palm Pre, Part 2: The webOS Experience, Jon Stokes, Ars Technica, 2009.06.24
Palm Pulls Back the Curtain on webOS Technical Details, Ryan Paul, Ars Technica, 2009.02.17
The Short, Sad, and Painful Story of the Palm Pre, Ellis Hamburger, Business Insider, 2011.08.18
The Egregious Incompetence of Palm, Daniel Eran, Roughly Drafted, 2007.01.31
Palm: The Rise and Fall of a Legend, Chris Dunphy, Maximum PC, TechnoBuffalo, 2011.03.31
Pre to Post Mortem: The Inside Story of the Death of Palm and webOS, Chris Ziegler, The Verge, 2012.06.05
The Palm Timeline, webOS Nation, Derek Kessler, 2013.02.28
RIP Palm: It's Over, and Here's Why, Jon Stokes, Ars Technica, 2010.03.22
Palm Post Mortem: What Could Have Been, Simple Solutions Computing
BeOS and Palm Tragedy, Sedrick, JustAcademic, 2011.08.26
R.I.P. Palm: A History of the Smartphone/PDA Pioneer (slideshow), PCMag.com
A Brief History of Palm, James Niccolai and Nancy Gohring, PC World, 2010.04.28
Crash of the Mobile Titans: What Happened to Palm, BlackBerry, Nokia, and HTC?, Matthew Miller, ZDNet, 2013.09.26
Keywords: #webos #palmpre #palmos
Short link: http://goo.gl/Xn0gXt
Related