Adventure Of HeyO Mac OS
For System 7.0 - 7.6 - Mac OS 9 Emulation This game works with. (I have another Titanic adventure made in 2009 taking up 1GB space) but this story description up here on this page is so out there! The most valuable object is a book called the 'Rubaiyat of Omar Khayyam'? I own a copy that was printed in the 1960s or 1970s. Apple's Mac OS X (Version 1.0) hit the market last month, while a final beta of Microsoft's Windows XP recently made it to the PC faithful. Both operating systems – to be installed on all new Macs and PCs later this year – promise to make the personal computing experience easier and far more reliable.
I recently decided to make the leap from Yellow Dog Linux to Mac OS X on myTitanium PowerBook. Getting everything to work the way I wanted proved to be achallenge, but well worth it. This document outlines all that I learned, so thatneither you nor I will have to experience such pain again. The overall goal wasto get Bricolage up and running, figuring that if it worked, then just aboutany mod_perl based solution would run. I’m happy to say that I was ultimatelysuccessful. You can be, too.
Download Alto's Adventure for macOS 10.9.0 or later and enjoy it on your Mac. Above the placid ivory snow lies a sleepy mountain village, brimming with the promise of adventure. 'A piece of interactive art' – WIRED 'Best of 2015' and '15 Most Beautiful Games' – Apple 'Favorite Apps of 2015' – The New York Times 'One of the best mobile. Mac OS X: Let the Adventure Begin. By Frank Beacham 02 May 2001. Tis the season of new personal computer operating systems. Apple's Mac OS X (Version 1.0) hit the market last month, while a final beta of Microsoft's Windows XP recently made it to the PC faithful. Both operating systems – to be installed on all new Macs and PCs later this year.
In the descriptions below, I provide links to download the software you’ll need,as well as the shell commands I used to compile and install each package. In allcases (except for the installation of the Developer Tools), I saved eachpackage’s sources to /usr/local/src and gunzipped and untarred them there. Ialso carried out each step as root, by running sudo -s. If you’re notcomfortable using a Unix shell, you might want to read up on it, first. All ofmy examples also assume a sh-compatible shell, such as bash or zsh. Fortunately,zsh comes with OS X, so you can just enable it for yourself in NetInfo Managerby setting users -> <username> -> shell to “/bin/zsh”, where <username> isyour user name.
Developer Tools
All of the software that I describe installing below must be compiled. Tocompile software on Mac OS X, you need to install the Mac OS X Developer Tools.These provide the cc compiler and many required libraries. Conveniently, thesecome on a CD-ROM with the Mac OS X Version 10.1 upgrade kit. I just popped inthe CD and installed them like you’d install any other OS X software. I neededadministrative access to OS X to install the Developer Tools (or, indeed, toinstall any of the other software I describe below), but otherwise it posed noproblems.
The best time to install the Developer Tools is immediately after upgrading toOS X version 10.1. Then run the Software Update applet in the System preferencesto get your system completely up-to-date. By the time I was done, I had thesystem updated to version 10.1.3.
Emacs
The first step I took in the process of moving to OS X was to get working thetools I needed most. Essentially, what this meant was GNU Emacs. Now I happento be a fan of the X version of Emacs – not XEmacs, but GNU Emacs with Xsupport built in. I wasn’t relishing the idea of having to install X on OS X(although there are XFree86 ports that do this), so I was really pleased todiscover the Mac-Emacs project. All I had to do was patch the GNU Emacs 21.1sources and compile them, and I was ready to go! GNU Emacs works beautifullywith the OS X Aqua interface.
There were a few configuration issues for me to work out, however. I have becomeaddicted to the green background that an old RedHat .XConfig file had set, and Iwanted this feature in OS X, too. Plus, the default font was really ugly (well,too big, really – anyone know how to make it smaller in Emacs?) and the Maccommand key was working as the Emacs META key, rather than the option key. So Ipoked around the net until I found the settings I needed and put them into my.emacs file:
Installing Emacs is not required for installing any of the other packagesdescribed below – it just happens to be my favorite text editor and IDE. So Idon’t provide the instructions here; the Mac-Emacs project does a plenty goodjob. If you’re not comfortable with Unix editors, you can use whatever editoryou like. BBEdit is a good choice.
GDBM
Mac OS X doesn’t come with a DBM! But since mod_ssl needs it, we have toinstall it. Fortunately, I found this PDF detailing someone else’s adventureswith mod_ssl on OS X, and it provided decent instructions for installing GDBM.First, I created a new user for GDBM. In NetInfoManager, I created a duplicateof the “unknown” user and named it “bin”. Then, I downloaded GDBM from theFSF, and installed it like this:
That did the trick. Nothing else was involved, fortunately.
Expat
Who doesn’t do something with XML these days? If your answer is, “not me!”, thenyou’ll need to install the Expat library in order to work with XML::Parser inPerl. Fortunately it’s relatively easy to install, although support for the-static flag appears to be broken in cc on OS X, so it needs to be stripped out.I downloaded it from its project bpage, and then did this:
Perl
Although Mac OS X ships with Perl (Yay!), it’s the older 5.6.0 version.There have been many bug fixes included in 5.6.1, so I wanted to make sure I gotthe latest stable version before I built anything else around it (mod_perl,modules, etc.).
Being a Unix program, Perl doesn’t expect to run into the problems associatedwith a case-insensitive file system like that Mac OS X’s HFS Plus. So there area couple of tweaks to the install process that make it slightly more complicatedthan you would typically expect. Fortunately, many have preceded us in doingthis, and the work-arounds are well-known. Basically, it comes down to this:
There were a few errors during make test, but none of them seems to besignificant. Hopefully, in the next version of Perl, the build will work just asit does on other platforms.
Downloads
Before installing Open SSL, mod_ssl, mod_perl, and Apache, I needed to get allthe right pieces in place. The mod_ssl and mod_perl configure processes patchthe Apache sources, so the Apache sources have to be downloaded and gunzippedand untarred into an adjacent directory. Furthermore, the mod_ssl versionnumber corresponds to the Apache version number, so you have to be sure thatthey match up. Normally, I would just download the latest versions of all ofthese pieces and run with it.
However, Bricolage requires the libapreq library and its supporting Perlmodules to run, and these libraries have not yet been successfully ported toMac OS X. But worry not; fearless mod_perl hackers are working on the problemeven as we speak, and there is an interim solution to get everything working.
As of this writing, the latest version of Apache is 1.3.24. But because I neededlibapreq, I had to use an experimental version of Apache modified tostatically compile in libapreq. Currently, only version 1.3.23 has been patchedfor libapreq, so that’s what I had to use. I discovered this experimental paththanks to a discussion on the Mac OS X Perl mail list.
So essentially what I did was download the experimental apache.tar.gz and theexperimental lightweight apreq.tar.gz packages and gunzip and untar them into/usr/local/src. Then I was ready to move on to Open SSL, mod_ssl, andmod_perl.
Open SSL
Compiling Open SSL was pretty painless. One of the tests fails, but it all seemsto work out, anyway. I download the sources from the Open SSL site, and didthis:
mod_ssl
The mod_ssl Apache module poses no problems whatsoever. I simply downloadedmod_ssl-2.8.7-1.3.23 from the mod_ssl site (note that the “1.3.23” at theend matches the version of Apache I downloaded) and gunzipped and untarred itinto /usr/local/src/. Then I simply excuted:
mod_perl
Configuring and installing mod_ssl was, fortunately, a relativelystraight-forward process. Getting Apache compiled with mod_perl and mod_ssl,however, was quite tricky, as you’ll see below. A number of braver folks than Ihave preceded me in installing mod_perl, so I was able to rely on theirhard-earned knowledge to get the job done. For example, Randal Schwartz postedinstructions to the mod_perl mail list, and his instructions worked well forme. So I downloaded the sources from the mod_perl site, and did this:
Apache
Getting Apache compiled just right was the most time-consuming part of thisprocess for me. Although many had gone before me in this task, everybody seemsto do it differently. I had become accustomed to just allowing Apache to usemost of its defaults when I compiled under Linux, but now I was getting allkinds of errors while following different instructions from differentauthorities from around the web. Sometimes Apache wouldn’t compile at all, andI’d get strange errors. Other times it would compile, pass all of its tests, andinstall, only to offer up errors such as
when I tried to start it. It turns out that the problem there was that I had anumber of modules compiled as DSOs – that is, libraries that can be loaded intoApache dynamically – but wasn’t loading them properly in my httpd.conf. Thiswas mainly because I’ve grown accustomed to Apache having all the libraries Ineeded compiled in statically, so I simply didn’t have to worry about them.
But I finally hit on the right incantation to get Apache to compile witheverything I need added statically, but still with support for DSOs by compilingin mod_so. I present it here for your viewing pleasure:
This series of commands successfully compiled Apache with mod_perl and mod_sslsupport statically compiled in, along with most of the other default modulesthat come with Apache. In short, everything is there that you need to run amajor application with security such as Bricolage.
Note that make certificate will lead you through the process of creating anSSL certificate. I like to use the “custom” type so that it reflects the name ofmy organization. But you can use whatever approach you’re most comfortable with.Consult the mod_ssl INSTALL file for more information.
libapreq
Once Apache is installed with mod_perl and mod_ssl, the rest is gravy! Theexperimental libapreq library I downloaded installed without a hitch:
PostgreSQL
PostgreSQL is a sophisticated open-source Object-Relational DBMS. I use it alot in my application development, and it, too, is required by Bricolage. I wasa bit concerned about how well it would compile and work on Mac OS X, but Ineedn’t have worried. First of all, Apple has provided some pretty decentinstructions. Although they mainly document how to install MySQL, acompeting open-source RDBMS, many of the same concepts apply to PostgreSQL.
The first thing I had to do was to create the “postgres” user. This is thesystem user that PostgreSQL typically runs as. I followed Apple’s instructions,using NetInfo Manager to duplicate the default “www” group and “www” user andgive the copies the name “postgres” and a new gid and uid, respectively.
Next I downloaded the PostgreSQL version 7.2.1 sources. Version 7.2 is the firstto specifically support Mac OS X, so going about the install was as simple as itis on any Unix system:
That was it! PostgreSQL was now installed. Next I had to initialize thePostgreSQL database directory. Again, this works much the same as it does on anyUnix system:
The final step was to start PostgreSQL and try to connect to it:
If you follow the above steps and find yourself at a psql prompt, you’re inbusiness! Because I tend to use PostgreSQL over TCP, I also enabled TCPconnectivity by enabling the “tcpip_socket” option in the postgresql.conf filein the data directory created by initdb:
If you’re like me, you like to have servers such as PostgreSQL start when yourcomputer starts. I enabled this by creating a Mac OS X PostgreSQL startupbundle. It may or may not be included in a future version of PostgreSQL, but inthe meantime, you can download it from here. Simply download it, gunzip anduntar it into /Library/StartupItems, restart OS X, and you’ll see it start upduring the normal Mac OS X startup sequence. I built this startup bundle byborrowing from the existing FreeBSD PostgreSQL startup script, the Apachestartup script that ships with OS X, and by reading the Creating SystemStarterStartup Item Bundles HOWTO.
XML::Parser
At this point, I had most
of the major pieces in place, and it was time for me to install the Perl modulesI needed. First up was XML::Parser. For some reason, XML::Parser can’t findthe expat libraries, even though the location in which I installed them ispretty common. I got around this by installing XML::Parser like this:
Text::Iconv
In Bricolage, Text::Iconv does all the work of converting text betweencharacter sets. This is because all of the data is stored in the database inUnicode, but we wanted to allow users to use the character set with whichthey’re accustomed in the UI. So I needed to install Text::Iconv. Naturally, MacOS X doesn’t come with libiconv – a library on which Text::Iconv depends – soI had to install it. Fortunately, it was a simple process to download it anddo a normal build:
Now, Text::Iconv itself was a little more problematic. You have to tell it tolook for libiconv by adding the -liconv option to the LIBS key in Makefile.PL.I’ve simplified doing this with the usual Perl magic:
DBD::Pg
Although the DBI installed via the CPAN module without problem, DBD::Pgwanted to play a little less nice. Of course I specified the proper environmentvariables to install it (anyone know why DBD::Pg’s Makefile.PL script can’t tryto figure those out on its own?), but still I got this error during make:
But this was one of those unusual situations in which the error message washelpful. So I took the error message’s advice, and successfully compiled andinstalled DBD::Pg like this:
LWP
The last piece I needed to worry about customizing when I installed it wasLWP. Before installing, back up /usr/bin/head. The reason for this is that LWPwill install /usr/bin/HEAD, and because HFS Plus is a case-insensitive filesystem, it’ll overwrite /usr/bin/head! This is a pretty significant issue, sincemany configure scripts use /usr/bin/head. So after installing LWP, move/usr/bin/HEAD, GET, & POST to /usr/local/bin. Also move /usr/bin/lwp* to/usr/local/bin. Then move your backed-up copy of head back to /usr/bin.
Naturally, I didn’t realize that this was necessary until it was too late. Iinstalled LWP with the CPAN module, and it wiped out /usr/bin/head. Fortunately,all was not lost (though it took me a while to figure out why my Apache compileswere failing!): I was able to restore head by copying it from the Mac OS Xinstaller CD. I Just popped it in an executed the command:
And then everything was happy again.
Bricolage
And finally, the pièce de résistance: Bricolage! All of the otherrequired Perl modules installed fine from Bundle::Bricolage:
Then I simply followed the directions in Bricolage’s INSTALL file, and started‘er up! I would document those steps here, but the install process is currentlyin flux and likely to change soon. The INSTALL file should always be current,however – check it out!
To Be Continued
No doubt my adventures with Unix tools on Mac OS X are far from over. I’vereported to various authors on the issues I’ve described above, and most willsoon be releasing new versions to address those issues. As they do, I’llendeavor to keep this page up-to-date. In the meantime, I am thoroughly enjoyingworking with the first really solid OS that Apple has released in years, andthrilled that I can finally have the best of both worlds: a good, reliable, andelegant UI, and all the Unix power tools I can stand! I hope you do, too.
Looking for the comments? Try the old layout.
On March 24, 2001, the iMac was less than three years old, the iPod was still more than six months away, and Macs ran at astounding speeds of up to 733MHz. But most importantly, Apple on that day released the first official version of Mac OS X, changing the future of its platform forever.
Though nobody knew it at the time, the release, codenamed Cheetah, was the first step in transforming Apple from a company poised on the verge of disaster into the second most valuable company in the world.
Were you to engage in a flight of fancy, you might call Mac OS X the deliverance for the tenacious few that had held onto Apple in the dark times, through the era when the Mac product line had proliferated into a writhing, seething mass of cryptic models in a seeming attempt to out-PC the PC makers. Mac OS X was a sign that the direction of the company had really and truly changed, after years of failed attempts to modernize the Mac OS.
The coup of Mac OS X, more than anything else, is that it shipped. The road to a new version of the Mac OS was littered with the unmarked graves of projects that had gone before: Taligent. Copland. Gershwin.
Despite the early release of a public beta with its own radical changes, that first shipping version of Mac OS X was far from perfect: It couldn’t play DVDs or burn CDs; performance was often sluggish; and the interface was distinctly different—and in many ways cruder—than its predecessor. But Apple does as it always does: it rolls. And over the following years, the company issued update after update, both minor and major, improving the system in a multitude of ways while slowly winning over converts from both the PC and the classic Mac OS.
Ten years later, Mac OS X is still by no means perfect. Ask any Mac user, and I guarantee that, without hesitation, they’ll draw up a list of things that annoy them about the operating system they use every day. But were you to plot the satisfaction of most Mac users on an entirely unscientific graph, I’d boldly wager you’d find it trended upward over time.
Adventure Of Heyo Mac Os 11
To me, there’s no greater testament of Mac OS X’s success than my own friends and family. In the ’90s, the majority were PC users and even those few that had stuck by the Mac soon moved to what they saw as the greener pastures of PCs—if for no other reason than they were far more affordable than the Macs of that age. But now, ten years after the release of Mac OS X, they’re far more likely to be packing an aluminum MacBook than a cheap plastic Dell. Though that might not be a feat to lay solely at the feet of the operating system—Apple’s emphasis on hardware design, Microsoft’s numerous missteps, and my own repeated entreaties probably contributed—it’s hard to argue that Mac OS X didn’t play a major role.
Not just because it dragged Macs into the modern era, with long-awaited features like preemptive multitasking and protected memory, previously the domain of its competitors. After all, the vast majority of computer users probably couldn’t tell you what either of those even means. No, they came to the Mac because as Apple improved Mac OS X, it stuck to an underlying philosophy: the operating system isn’t an end unto itself; it’s about making it as easy as possible to use computers to do things.
Adventure Of Heyo Mac Os X
That’s the same philosophy that Apple has taken with the iPhone and the iPad, and to my mind it’s the reason that those products have met with such overwhelming success. Frankly, it’s hard not to see the impact of Mac OS X on most of the major decisions Apple has made in the past decade, whether it be the importance of iTunes, the transition to Intel processors, or the development of iOS devices—which, after all, are based on the same OS X underpinnings as the Mac.
As we embark upon Mac OS X’s second decade, the Mac’s operating system is about to undergo another major shift, perhaps no less significant than that from the classic Mac OS. In the forthcoming Mac OS X Lion, the student becomes the teacher: Apple is beginning to fold features from its iOS devices back into the Mac OS, taking its desktop computer software down a new and very different path.
While those changes have worried some—especially those who have long been invested in Mac OS X—progress, good or bad, is inevitable. The Mac OS X of ten years hence is going to be as different from today’s Snow Leopard as Snow Leopard is from Mac OS X 10.0, but at its core, that future Mac OS X is going to be rooted in those same fundamentals of getting technology out of our way so we can get on with our lives.
As always, the proof will be in the using. But if I may return to my thoroughly unscientific hypothetical graph from above, I’d pose an estimated guess that a decade down the road, that line of satisfaction will continue to trend upwards, and we’ll all be looking back on the Mac OS of 2011 and shaking our heads at what we were missing.
[Dan Moren is a senior associate editor at Macworld, and a Mac OS X user since the year 2000.]