Mono 2.0 allows .Net developers to use Linux, Solaris and Mac OS X. Mono comes with MeMA, a tool that allows for automated .Net to Linux migrations away from .Net. A lot is being made these days about Silverlight. Look at what our friends from NetFlix have done for Mac users with it. Well, the Mono framework was leveraged to write a Mono-based plugin compatible with Silverlight that they are calling Moonlight. This is pretty cool because it allows Silverlight developers to convert their code into Moonlight and then publish it as an actual desktop application rather than a more web-oriented widget. The open source community has provided a really great tool yet again.
krypted November 30th, 2008
Posted In: Mac OS X, Unix, Windows Server
.net, Mono, NetFlix, Silverlight
Due to the fact that I got a lot of email from the USC fans who apparently read this site I went ahead and ported my iPhone app for the UGA schedule to USC. Until my app store account is ready here’s the proof…
krypted November 29th, 2008
Posted In: iPhone
College Football, iPhone Application, Schedule, USC
iPhone applications and vacation. Funny how they can end up coming together. Another app I’ve been working on is a little football schedule for the UGA Bulldogs, which if you’ve been reading this site for awhile you’ll know is my team of choice. So here are some screenshots for the app, which should be up on the App Store once I get all the details worked out.
krypted November 28th, 2008
Posted In: iPhone
Football, iPhone, UGA
Mike Bombich is retiring NetRestore:
krypted November 24th, 2008
Posted In: Mac OS X
To Disable Spotlight for Mac OS X you can stop the Spotlight processes from being invoked by launchd. To do so use the following commands:
launchctl unload -w /System/Library/LaunchAgents/com.apple.Spotlight.plist
launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
To re-enable it you would simply load up your launchd processes again like so:
launchctl load -w /System/Library/LaunchAgents/com.apple.Spotlight.plist
launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
krypted November 23rd, 2008
Posted In: Mac OS X, Xsan
launch daemons, launchctl, launchd, Spotlight
Before you write an application, check and make sure it hasn’t already been written by someone who’s a better programmer. 😉 Either way, here’s my second go at writing an iPhone app. Still waiting for approval to get that account…
krypted November 22nd, 2008
Posted In: iPhone
iPhone Application, NetFlix
Yup, I wrote an iPhone app for my blog. If you want it let me know. Once Apple approves me for an account with the App Store I’ll post it up there.
krypted November 21st, 2008
Posted In: sites, WordPress
application, iPhone, krypted.com
Xsan and the acfs (Apple Clustered File System) volumes that Xsan controls can be utilized by Windows and Linux clients. The Windows setup is fairly straight forward, so here we’re going to cover setting up a Linux client to mount an Xsan volume using StorNext. First, buy StorNext. Second, register StorNext.
Then, go to your Metadata Controller and Backup Metadata Controller and use the cvfsid command. Copy the contents and go to this site, completing the form using the output from cvfsid:
Now put the information that Quantum sends you into the /Library/FileSystems/Xsan/config/license.dat file on your Metadata Controllers and reboot them. Now you're ready to setup your clients. To do so you will need the .auth_secret file and fsnameservers file from the Metadata Controllers and the StorNext rpm client installer.
From each client, first verify that you can ping the Metadata Controllers. Then, extract the rpm:
tar xf sn_dsm_linuxRedHat40AS_x86_64_client.tar.gz (or you could use gunzip to extract)
Next, install the rpm:
rpm -ivh sn_dsm_linuxRedHat40AS_x86_64_client.tar
Now copy the .auth_secret file and fsnameservers file to the /usr/cvfs/config directory created by the installer. Then use the cvlabel -l command to verify that you can see all of the LUNs that make up the volume. Also verify that you can ping both (or all if you have more than 2) of the Metadata Controllers by IP address. Finally, add cvfs to the list of file systems in the PRUNEFS field in the /etc/updatedb.conf file.
Now you're ready to try and mount up the volume. To do so, let's create a folder in the /mnt directory called the same thing as your volume name (for this example we'll use a volume name of Xsan). Next, open your /etc/fstab and add the following line:
Xsan /mnt/Xsan cvfs verbose=yes 0 0
Now try and mount the volume using the following command:
mount -t cvfs Xsan /mnt/Xsan
If it works then you can reboot and life will be good. If the entry in the fstab causes any problems you can put a # in front of it to disable it. Enjoy!
krypted November 20th, 2008
Posted In: Unix, Xsan
Final Cut Server is able to see files and folders that are available to a system through a variety of means. This could be an Xsan or a folder on an Xsan, an nfs mount from another host, a folder through FTP, etc. Basically, if you can see some data through the Finder reliably then you can go ahead and add it to Final Cut Server. Speeds of clients to access the data then depend on the ability of the clients to access that data either in place or through the Final Cut Server application.
Each top level folder that you will be accessing through Final Cut Server can be considered as a Device. You can have 3 or 4 folders on the root of an Xsan and define each as a device or you can make the root of an nfs volume you mount a device, or some subfolders within it. Once a device is created you can use it to store media and automate actions with the device. Previously, we created a device using the System Prefernece pane for Final Cut Server. Here, we will use the Administration utility to do so, which provides a bevy of other options.
To create a device, open Final Cut Server and open the Administration utility. Then click on the icon to create the new device, seen below:
At the next screen, you will likely choose to create a Filesystem device (although FTP Server is a common way to access media from or send media to another host, especially a remote one).
If you’re using a Filesystem device (which is basically just a folder accessible to the Final Cut Server) then you will see a screen similar to the one below. Here, type the applicable information for the path and other information. You can just type a path in the Local Directory field, or fill out relevant information for smb or nfs where authentication might be required. Once you are satisfied with those settings, you can choose whether or not to generate thumbnail images on the device using the Generate Thumbnails checkbox, as seen below.
Next you will edit the URI and URL fields. This allows you to tell a client what path to look for in order to determine whether or not the host is local and it can therefore edit content in place (eg over Xsan) or whether clients will access the data through Final Cut Servers built in caching mechanism (through Ethernet). For most environments you can leave the analyze mode as-is. If the device will be used to store archives, then you will want to check the box for Archive.
If you will be using the device as an archive location then you can assign post archive commands and pre restore commands (which can call a restore to the path from the Time Navigator or Bakbone command line utilities.
Once you’re satisfied with your settings, click on Save Settings and you’re done!
krypted November 19th, 2008
Posted In: Final Cut Server
bakbone, Device, Final Cut Server, Time Navigator, Xsan
Next Page »
We’ve been working on an application that will repair corrupted Xsan volumes. If you have a volume you wouldn’t mind potentially shredding and would like to test the app for us then please let me know.
krypted November 18th, 2008
Posted In: Xsan