Archive for ‘osx Server’ Category
Posted on 13:51, February 5th, 2010 by Many Ayromlou
The answer to that is maybe, we’ll see. But all that aside if you’re interested in a minimalistic video player that can handle more codecs than VLC and is generally faster then give Movist a try.
The unique thing about the player is that it allows you to switch codec engines between ffmpeg and quicktime based on file extensions. Oh and did I say it’s FREE aswell :-).
Posted on 23:36, January 29th, 2010 by Many Ayromlou
Well the title is a bit misleading…..here are the details. I found out that if you have a NTFS native shared directory on your server, everything works fine as long as you’re using OSX 10.5 (Leopard) or below as a client. You can move files from Leopard and/or Tiger clients to the share and as long as you don’t mind the ._ files everything works.
Well something new has been introduced in Snow Leopard that kinda breaks this. If you have a Snow Leopard client machine accessing a NTFS native shared directory (via smb), by default the shares are mounted with the new xattr (Extended Attribute) feature, instead of those “old” ._ files. This messes everything up if you’re in a mixed environment with 10.4, 10.5, and 10.6 clients all accessing files in a NTFS native smb share.
Snow Leopards version of samba will read those old resource fork files, but files uploaded or modified by the Snow Leopard client will be unrecognizable by the older samba clients (10.5-) as far as the resource fork goes. This introduces some problems with programs that use the resource fork to store information.
All this headache is related to the ‘NTFS Streams’ feature of SMB mounts, so if we disable that, everything goes back to normal. To do this you have to create a file named /etc/nsmb.conf on all your 10.6 clients with the following contents:
Posted on 20:52, January 29th, 2010 by Many Ayromlou
If you ever have a need to simply hide extraneous files and/or folder entries in Finder you can use the following command:
Posted on 18:00, January 15th, 2010 by Many Ayromlou
I just picked one of these babies up from the apple store and after testing it a bit for the past hour, I have one word for it: WOW. This little guy is no gimmick, it’s zippy as hell and it does exactly what they say it would. The details for the device are on Elgato’s Website, but this is just a mini review of the tests I ran against a couple of software encoders.
Here is my setup:
– Mac OSX 10.5.8 with latest updates running on a 2.16Ghz Intel Core 2 Duo Black MacBook w/ 2 GB 667Mhz DDR2 SDRAM.
– Output was done through the Elgato Turbo stick, Mpeg Streamclip encoder and ffmpegX.
– In all cases I’ve tried to produce a single pass h264/x264 file with the same dimensions and settings as the Elgato software preset for ipod best (640×360 @ 24 fps @ 1500 kbps at 80-90% quality).
The results blew my mind:
Here are a couple of full size frames (640×360 px) blown up to 1920×1200 to exaggerate imperfections (click on the pics to see them full size):
– Mpeg Streamclip
– And last but not least all three at the original size (left to right): Elgato Turbo Stick, Mpeg Streamclip, ffmpegX
Best C$179 I’ve spent in a while. It just works.
Posted on 14:17, January 7th, 2010 by Many Ayromlou
Let’s be clear on this, Wine, which is what WineBottler uses, lets you run Windows software on other operating systems. With Wine, you can install and run these applications just like you would in Windows without the need for a emulator or virtual machine. Not every program works yet, however there are already several million people using Wine to run their software.
WineBottler makes it really simple to create a application bundle out of Windows programs that will run on OSX. WineBottler is a tool similar to codeweavers Crossover, where separate prefixes — like runtime environments — are created per app. However, WineBottler ‘wraps’ or ‘bottles’ a separate prefix in each application bundle. WineBottler allows standalone (i.e. not requiring wine to be installed) applications to be created as well, by including the wine bundle inside the standalone application bundle.
Additionally unlike Wine which installs files in “standard” unix directories (/opt, /usr/local, etc.), WineBottler has two OSX application bundles that you copy to your Application directory. Very clean install/uninstall. Oh and did I mention that it’s free/opensource. The only catch, OSX for Intel only.
Posted on 17:34, November 25th, 2009 by Many Ayromlou
Someone must have screwed up something in the freshclam plist as part of the update for Leopard (2009-05). I was getting this error constantly in my system.log which was not only annoying as hell, but also kept clam from downloading new virus definitions. Anyways, here is how you fix it.
Posted on 21:56, November 10th, 2009 by Many Ayromlou
I’ve been using Synergy for about 3 years now and never really thought about writing about it. Tonight I came across Synergy+ which is a maintenance fork of the original Synergy. So I thought about writing a small note about it since it’s now maintained again.
Synergy+ (synergy-plus) lets you easily share a single mouse and keyboard between multiple computers with different operating systems, without special hardware. All you need is a LAN connection. It’s intended for users with multiple computers, where each system uses its own display. It’s a little like having a 2nd or a 3rd desktop. It’s not a KVM or VNC tool, but it does achieve similar results (but with added convenience). No need to press any buttons when you want to change desktops, and your keyboard input goes to the same screen that your mouse cursor is on.
So head over to Synergy+’s home over at Google Code and grab your copy. Synergy+ is free open source software.
Posted on 14:27, June 27th, 2009 by Many Ayromlou
I’ve had this problem ever since Safari 4.0 came out a little while ago. The symptoms are simple, when you close a Safari window it crashes. I reported it the first couple of times to Apple using crash reporter, then I started to look around for a solution, but to no avail. I gave up for a while and used firefox again. Today I got fed up with this and started to debug the issue from command line and finally found the problem.
A little while back I had purchased a QNAP NAS device, which I absolutely love. At the time I was impressed by the fact that it supported both XP and OSX. There is a piece of software you install on your machine called QGET which allows you to pass all sorts of downloading commands to the NAS (so it can download things in the background). This program has a Safari plugin that turned out to be the culprit. The QGET program is actually fine and by itself doesn’t cause any issues. All you need to do is delete QGET plugin folder from /Library/InputManagers and restart your machine…….No more crashes…..yeaaaaa :-)
Posted on 12:39, June 11th, 2009 by Many Ayromlou
This problem has been around (I think) ever since the introduction of POSIX permissions. In pre-10.5 versions you could sorta do something like this by changing the default umask on the system, but that was system wide and applied to all folders/files a user created on the entire filesystem…..not nice. The real question is how do you create a directory that is totally public without mucking around with system/user wide settings. A folder that anyone on the system in question can read/write/modify/delete anything anyone else has put in there. A true shared directory with share permission inheritence. We call it “pub” directory at my place of work.
The old trick in OSX (in case someone is interested) was to write a small script that you ran via cron every 5-10 minutes that would “chmod” all the entries in a folder to be open to a specific POSIX group….something like the script below:
Well those were the old days and now with the help of ACL’s we can do this a lot nicer/cleaner. The procedure below is for OSX 10.5+ (it should also work on 10.4, although I haven’t tried it).
You now have a true public folder where all members of the group public can read, write and delete files, as well as read, write to and create new sub folders. The ACL rule takes precedence over standard UNIX file permissions and is automatically inherited. It’s this automatic inheritance that is really important.
IMPORTANT: You must copy (hold down Option in Finder prior to dragging), and not merely move, items. This is particularly important with bundles, such as the Aperture library bundle for example. Moving items doesn’t inherit/change the permissions/ACL’s. Copying ensures that the files are actually created in the shared folder, thereby forcing the ACL rules to be inherited. If you have moved files into this directory and the permissions are a bit messed up you can quickly fix that by issuing the following recursive command which will set the ACL’s and POSIX permissions to the “right” ones so that everyone can do anything in that directory:
Posted on 11:34, June 11th, 2009 by Many Ayromlou
I ran into this problem a little while back and thought I should document it. It’s kinda similar to the “How to get Admin rights in OSX Leopard using single user mode…” document from earlier this year. Here is the procedure:
Nice and squeaky clean…..