Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under snowleopard...

Jason says...

All the cool kids are using Fish, so why can't I? BASH is so 90's. Cause it won't fracking install on my copy of Snow Leopard, dang it. I spent the greater part of this weekend trying to figure out why Fish didn't like me. Read this so you won't have to endure my pain.

port install fish

wouldn't install. ports/fish kept asking for iconv, gettext, or whatnot. 64-bit/32-bit unix apps don't play well together in Snow Leopard, and because I upgraded from Leopard and I needed to reinstall ports to deal with it. Long and painful, indeed. You, though, can do this with 60 seconds of typing:

1. Reinstall ports (via http://trac.macports.org/wiki/Migration)

a. Save the list of installed ports:

port installed > myports.txt

b. Clean any partially completed builds, and uninstall all installed ports:

sudo port clean all
watch football/do laundry/deshell next week's pistachios
sudo port -f uninstall installed

c. Browse myports.txt and install the ports that you actually want to use (as opposed to those that are only needed as dependencies) one by one, remembering to specify the appropriate variants:

sudo port install portname +variant1 +variant2 ...

2. Install fish

port install fish

3. Make it default

append "opt/local/bin/fish" to the /etc/shells file
utilize accounts.prefpane, unlock it, right click your icon, and set your shell to "opt/local/bin/fish"

4. Voila! Enjoy fish!

For a more on Fish, here's an old Ars Technica article, and a lwn.net article.

Filed under: apple, os x, snow leopard, unix

Andy says...

Windows 7 is now with us. Too early to tell whether we have received this with a bang or a whimper, but if ever there was a time to watch with interest the rivalry between Apple and Microsoft it is now.

Now I speak from a somewhat unique position. As someone working in the creative industries you would think I was a die hard Apple devotee. And in many respects you would be right. But I also use a PS regularly, and appreciate that there are certain things that they do better than Macs. Notice that I referred to things 'they do' and not ' how they do it'. Because I think that this is the key distinction between the two OS's, but one that has become a little muddied lately.

Apple, in part due to their consistently great design has all too often been seen as the only way to produce great creativity, with the ugly old beige towers of the PC's being far too monstrous to behold to produce anything of beauty. Which is nonsense. If you accept that these are just machines, the end product being constant (bear with me here!) then it is the processes that these machines make you use that really set them apart. The applications are almost all commonly available on both Windows and OS X, and so what really is left as the distinguishing differences?

Well, let's for a start look at the two most commonly used operating systems for them both at the moment. For Apple, Leopard or OS X 10.5 to give it it's pedigree name, and Windows Vista.

Both of these system were launched at approximately the same time and both were met with luke warm approval. Apple launched Leopard with a view to supporting both its native UNIX clients, but also vitally supporting those newer machines fitted with the Intel chip. A move which angered many of its followers as this has famously been the chip underpinning PC users since Windows began. Apple was seen as abandoning its roots and losing the one key differentiator between it and the beige boxes, the fact that Apple software ran on ONLY Apple parts. Vista launched with a number of key features new to this system, all of which seemed to be lifted directly from Leopard. The dashboard, widgets and the 'Aero' style of GUI all seemed remarkably similar to those of Leopard, and seemed to bring the two systems closer together in the minds of users than either party would have wished.

The negative publicity surrounding Vista was there from the start and stemmed from a bloated OS, requiring far too much RAM to run even the simplest of native applications. Driver support was scant due to a lack of faith in manufacturers that this system was (a) suitable for their ancillary products and (b) that it would even be around long enough to warrant them releasing a Vista version of the driver / plugin. The message was clear - too much time spent on making the OS look good, and not enough time spent of making it quick, responsive, and easy to use.

Leopard on the other hand ran well - the myth of the 'hackintosh' became a reality with users building 'PC's' from Intel components and installing their beloved OS X into bege towers. IT managers were startled to turn on their Dell and be met with the distinctive dock and dashbard of the enemy OS.

So neither system necessarily met with a huge fanfare. Windows had released a damp squib of a system far too sluggish for purpose, and Apple an OS that hardly made a huge difference to the previous, and moved them ever closer to their arch rivals. The OS itself didn't deliver jurassic shifts in their offerings, and so what would be needed to deliver the killer OS? The one that makes headlines and gives share prices the spike the investors want.

That would be answered by the next releases.

Apple release Snow Leopard. Same cat you might say. Not a Cougar or a Lynx? No. Because as Apple said ' It's the all new, exaclty the same operating system' Mmmmm. Sounds even duller than Leopard. But no. And here's why. They realised that the prime reason people liked their OS had nothing to do with dashboards or docks, or programmes they were offering bundled in. It was that the system was quick to respond and didn't crash. This due to the UNIX language underpinning the entire system (Windows uses BIOS) and the Finder (their equivalent if you will, of the Windows File Explorer) Nothing at all to do with programmes available, widgets, sidebars, drop shadows on windows or transparent window address bars. It was the bare bones reliability and speed of the system to respond. Snow Leopard was exactly that. A  massive system tune up to Leopard. No real additions that anyone but a developer would notice. Snow Leopard made things faster. Startup and shutdown, applications responded quicker, and gigabytes of unnecessary clutter were wiped off you hard disk on installation meaning that altogether this was a leaner, meaner system from the word go.

Windows 7, unsuprisingly promises us the same. It is slimmed down and tuned up. No great offerings that weren't in countless previous iterations of Windows, but this time the key focus is on performance, responsiveness, and just plain geting things done (something so painfully lacking in Vista, a hugely sluggish and frustrating system)

Therefore it would seem as if the main players have learnt a few lessons in the development of their respective OS's. Software nowadays is so often free and therefore licensing revenues are gone. Cloud computing has meant that so much software now isn't ever hosted on desktops, and so their futures won't lie there. Runtimes such as Adobe AIR have meant that software will run on either system. So could it be that OS's, as before need to ally with industry for their market share to soar. It's an interesting point because it seems that this, once the most powerful alliance for Apple, has now fallen by the wayside.

Take for example the sad tale of Internet Explorer. The world's most popular browser and installed as standard on all new PC's. Oh, and the bain of every web developers life. As browser numbers soar, and as Safari, Opera, Firefox, Chrome and Camino all co-exist happily, using a common rendering engine and working on creating more friendly, usable, functional interfaces, Internet Explorer has refused to benefit from this synergy, has used it's own rendering engine and kept it's code a secret. Not for them the benefits of Open Source code, with thousands of people across the web improving, bug testing and compiling 'nightly builds' of improvements. No. Developers are still building websites and HTML web applications, and then having to put in place hacks to ensure the pages work in IE. They are creating work arounds, something typically associated with redundant technologies being phased out, for the most widely used and longest standing browser technology in the world.

Compare also with the adoption of Microsoft browser, and to that extent OS technology. Dell are still shipping with XP Pro, and OS now 13 years old. An OS superceded twice now. This as a direct response from customers, many of whom will be some of the most powerful IT consumers in huge global companies, all of whom have no faith in their technology until it has been tested to breaking point in the market for, well 13 years probably. These are the same companies who refuse to upgrade the browsers on their client machines from IE6 to the current standard IE8, as they still fear the security implications this might bring. So again, there is a lag of two revisions.

And thus to our title. Apple seem to have the early adopters in the palm of their hands. Snow Leopard sales on the day of release were the highest ever. Apple users don't fear change, as they know they are using a stable, secure system and vitally one that is built on a technology that is human shaped in it's approach to user-interface. It recognises that software and hardware are interchangeable, but focusses on productivity and making actions as simple and quick as possible. So what if they never install a programme onto the machine as long as they have it, they will make it as easy to perform task as possible.

Windows on the other hand have a lot of ground to make up as successive systems remain as crash-happy as they ever were, and with the expense of the OS's and software so often incompatible with new releases, it is very expensive to be an early adopter of Microsoft software. With Dell and big business still two iterations behind, all the signs from industry are to hold off. Don't buy yet. Don't even think about buying until we do. And with Google launching their OS based on the popular Chrome browser, it would appear that before too long, even we won't ever need to pay for an OS ever again.

Filed under: Browsers, Leopard, Operating Systems, OS X, Snow Leopard, Windows 7

chak says...

After much digging through otool output and tracing Haskell code with dtrace, log messages, and gdb, I finally found the cause of the SIGBUS errors with ghci on Snow Leopard. At the end, only a tiny change was required[1]: the homegrown dynamic linker of ghci had simply ignored a relocation type that ld on Snow Leopard chose to use.

What this really shows again is that re-implementing parts of basic infrastructure in an ad hoc manner always comes back to bite you. Such infrastructure is usually full of low-level, platform-dependent details, which you are bound to get wrong once in a while and then it can be rather involved to find the problem. In this case, the relocation of the memory access of a bit of C code in GMP, reading a global variable, went wrong. As a result, the wrong memory location was accessed, which happened to contain a NULL pointer. Upon dereferencing the NULL, the program crashed.

All of this was further obscured by the fact that the homegrown linker approach of ghci implies that we have two copies of the basic libraries in memory and in use at the same time. One copy has been statically linked with the ghc executable and the second copy is dynamically loaded by ghci. The relocation in the statically linked copy was perfectly fine, but the relocation in the dynamically loaded one was broken.

[1] http://www.haskell.org/pipermail/cvs-ghc/2009-October/050863.html

Filed under: ghc, haskell, snow leopard

Roderik says...

Working with GIT on OSX is not as simple as it sounds. While there are many projects that try to deliver dmg files for various parts of my GIT workflow, not all of them are available and they don't all work together nicely. The same goes if you try to install everything from a "port" system. So this is my mix and match setup.

My GIT toolbox contains the following tools:

Working with GIT and you will need some easy way to have several Terminal windows available at all times. On Ubuntu we use a quake style drop down terminal app named yakuake. A variant is available for OSX, named Visor. Installing visor is done by:

  1. Install SIMBL and make sure you have latest SIMBL 0.9.x
  2. Place Visor.bundle into ~/Library/Application Support/SIMBL/Plugins (create this directory if it does not exist)
  3. Relaunch Terminal.app - You should now see the Visor Status Menu Item
  4. Configure your keyboard trigger by selecting the Visor Status Menu Item -> Visor Preferences ... and edit your keyboard hot-key

So, now we have a good Terminal, let's get started. I've found that the MacPorts project offers the a good way to install nog dmg applications. It works like apt-get or more like emerge on gentoo, because it compiles. (i know "port" is probably more like the "port" in FreeBSD, but who uses that one anyway :)) Installing ports is easy, just download the dmg from this page, and install it. After installing update the thing by running the following in a Terminal

sudo port -v selfupdate

When this is done, install git-core and qgit by running

sudo port install git-core qgit

Now sit back, and wait... Ports will compile QT etc, so it will take a few hours

While waiting, you can continue with kdiff3. Kdiff3 is a three-way diff viewer and mergetool. You see a lt of tutorials for OSX that use FileMerge that is part of the Xtools, but this is not a three-way merge application, and i found the interface and usability not good enough. Download the OSX version of kdiff3 from the website and install it. Why not compiling it with ports? Well because when starting the commandline version, you get some strange X window icon in the dock and no kdiff3.

Working with GIT on the commandline, you will need to be able to let GIT access kdiff3 through the mergetool command. This means a commandline version needs to be available. We do this by creating an alias command in /usr/local/bin that forwards to the kdiff3.app

sudo mate /usr/local/bin/kdiff3
sudo chmod a+x /usr/local/bin/kdiff3

The content of tis file is listed below:

#!/bin/sh
exec /Applications/kdiff3.app/Contents/MacOS/kdiff3 "$1" "$2" "$3" "$4" "$5" "$6"

One more tweak is required, you need to configure git to use kdiff3. You can do this using the git commandline or take the config below. This config has a lot more useful tweaks then just the mergetool, i suggest you start from this one.

mate ~/.gitconfig
[pack]
	threads = 0
[color]
	ui = auto
[apply]
	whitespace = nowarn
[alias]
	cp = cherry-pick
  	co = checkout
  	ci = commit
  	di = diff
  	st = status
  	br = branch
  	mg = merge
[mirror]
  	summary = true
[apply]
  	whitespace = strip
[pager]
  	color = true
[status]
  	color = auto
[color]
  	branch = auto
  	diff = auto
  	status = auto
[color "branch"]
  	current = yellow reverse
  	local = yellow
  	remote = green
[color "diff"]
  	meta = yellow bold
  	frag = magenta bold
  	old = red bold
  	new = blue bold
[color "status"]
  	added = yellow
  	changed = green
  	untracked = cyan
[gc]
    auto = 1
[merge]
	keepBackup = false;
	tool = kdiff3
	log = true
[diff]
  	color = auto
  	renamelimit = 0

Filed under: git, kdiff3, osx, qgit, snowleopard

bowas says...

Mac OS-X Snow Leopard Vs Windows 7

Mac OS X - Dienstag, der 27.10.2009 um 01:35 Uhr

windows vs AplleDas sogenannte „Deathmatch“ zwischen Windows 7 und dem Mac OS X ist immer noch voll im Gang. Was ist für mich das bessere Betriebssystem ? Ist die Frage, die sich viele mehr denn je stellen. Der durchschnittliche Nutzeranspruch, an das neue Betriebssystem, begrenzt sich auf folgende Voraussetzungen. Dies sind neben einer leichten Bedienung, Schnelligkeit sowie Stabilität. Einfachheit und Innovation sind klare Pros bezüglich des Mac OS X. Ein immer wachsender Zulauf an neuen Nutzern ist der Beweis. Jedoch kann auch Windows mit der siebten Version sich sehen lassen. Während Windows mehr Wert auf das Arbeiten mit den Menüs legt, ist Snow Leopard im Bereich Drag&Drop führend.

 

Filed under: mac, snow leopard, windows 7

Outsanity says...

Filed under: Kanye West, Outsanity, Snow Leopard, Windows 7

janmichael says...

Heute bin ich in die Verlegenheit gekommen eine Matroska-Datei mit der Endung mkv abspielen zu wollen. Von Haus aus kann das der von mir präferierte QuickTime Player X aus Snow Leopard leider nicht. Es sollte zumindest einmal Perian installiert sein, damit sich annähernd etwas tut.

Unter Umständen stellt sich aber auch dann noch kein Erfolg ein und der Player verweigert den Dienst. Abhilfe schafft folgender Forumeintrag auf den ich heute zufällig gestoßen bin:

http://forums.whirlpool.net.au/forum-replies-archive.cfm/1271991.html

Dort kann man unter diesem Link eine kleiner Helfer-App herunter laden. Diese wird in den Ordner "Anwendungen" kopiert und schon lassen sich die mkv-Dateien öffnen.

Einziger Haken. Nach dem öffnen ruckelt der QuickTime X noch ein bisschen, weil er QuickTime X wohl mit nicht vorhandenen Indexen nicht so richtig umgehen kann. Aber nach ein paar Sekunden ist das Ruckeln weg und man kann ganz normal weiterschauen.

Filed under: apple, matroska, mkv, os x, quicktime, snow leopard

Art says...

I've got an ElGato EyeTV Hybrid TV Tuner Stick hooked up to my October 2009 Mac Mini running OS X Snow Leopard 10.6.1. My Mac Mini is hooked up to my Yamaha RX-V863 receiver with an HDMI Male to DVI Male Cable, a generic optical digital out cable  with a toslink to optical mini adapter.

To enable 5.1 audio on the Mac Mini:

1. Go to Applications > Utilities > Audio MIDI Setup
2. Clock source: Default
3. Source: Digital Out
4. Format: 48000.0 Hz and Encoded Digital Audio

Should look like this:

From what I understand, for most folks it should work at this point but for me it was a little different. On the bottom left side of the screen, click the little "+" in the corner. In the box above, something called "Aggregate Device 0 in / 0 out" will appear. As soon as I clicked the +, I had 5.1 audio. Should look something like this:


Not sure what that Aggregate Device thing is but that's what it took. I've since been able to remove that and I'm still getting 5.1. Your mileage may vary, etc. If anyone out there can explain these settings, drop me a line or leave a comment. 

Also, if you're using your Mac Mini as a DVD player, you'll need to flip the following:

1. Applications > DVD Player > Preferences
2. Under Disc Setup, set Audio output to "System Sound Output"
3. Check "Disable Dolby dynamic range compression"
4. Click OK

Filed under: apple, audio, dolby 5.1, elgato, eyetv, hybrid, mac, mini, os x, snow leopard, sound, stick, surround, tuner

Dead Simple says...

Funny that with the release of Windows 7 this week Gizmodo finds it is better not to bother with it but instead stick Snow Leopard onto a Dell Mini 10v. Full step by step instructions given. I'm definitely getting one when they start sticking Tegra chips on these.

Link

Filed under: Dell, Gizmodo, Hackintosh, netbook, Snow Leopard, Windows 7

molecule says...

user-interface:

disable spotlight


snow-leopard Dock:

development:

install XCode, System Tools, X11 from Snow-Leopard DVD
install macports via dmg

install via ports
  • sudo port install  wget emacs subversion mysql5-server mysql5 python24 libxml2 libxslt py-libxml2 py-geoip postgresql83 postgresql83-server

python libs, manual install:

  • cd /opt/local/bin/
  • sudo ln -s mysql_config5 mysql_config


  • python2.4 setup.py build && sudo python2.4 setup.py install
  • python libs, easy_install-2.4:

    • datetime
    • python-dateutil
    • ftputil
    • hashlib
    • lxml
    • cython
    • pygresql
    • sqlalchemy

    Filed under: dock, install, mac, python, snow-leopard, user-interface