This is an important bunch of numbers and letters. If you buy content, you should be able to play it on any system you choose, without being restricted to certain proprietary platforms that the cartels of content rights holders permit. DRM sucks. Props to EMI.
Ok, so you go to your Documents folder on your mac. There you put all your fun Word documents. You are familiar with moving around and organizing your files into folders, then opening with Word. Maybe you’ve seen Google docs, but it didn’t matter to you since you like to deal with your documents the way you’re accustomed. Enter MacFuse and DocFS. Now you can have a folder on your Mac that is sort of like a little portal into Google docs. Double click, create new files, delete files, open in Word – the difference is that when you’re at work or a friend’s house now you can get to your docs on Google. Free and easy backup.
So you have all these pictures that you organize into a folder structure and thats how you like to work with them. Picassa web and Flickr are just confusing. Enter PicassawebFS and Fuse.
RSS Feeds as a file system. Gmail as a file system. An LDAP directory as a file system. Anything as a file system. That’s what FUSE is all about. This is seriously badass and Google has released this early version of FUSE for the Mac (which has been popular on Linux for a year or two).
Watch this video and become one with MacFuse.
.gif)
So I’ve been messing with cricket a bit for monitoring interesting SNMP bits and bobs.
You’ll find some basic documentation on getting Cricket up and running, but I felt overall that it could be significantly improved. That said, I’d just like to offer a few notes that took me way too long to figure out.
If you’ve got a UCD-SNMP host and you want to build a targets file automagically, take a look at the ~/cricket/util/systemPerfConf.pl script to build that stuff for you – it’ll save you a lot of time.
You can just add folders to your heart’s content within ~/cricket-config, but the poller isn’t going to grab those top level folders i.e. router-interfaces unless they’re listed in ~/cricket/subtree-sets. I have no idea why they need to be listed here.
Expect the sample config trees in ~/cricket/sample-config to have problems – ~/cricket-logs/normal.0 is your friend.
For grapher.cgi, get a stylesheet going, because that interfaces is ugly. You’ll probably have to hack on grapher.cgi to add in some id’s or classes. Get ready to see some ugly html hard coded colors – uuuuuugly.
Speaking of hacking on grapher.cgi, the search that shows up at the bottom of the grapher is pretty useless unless you put in attribute=value pairs such as display-name=SERVER1. It really is that ghetto, but this post gives a little hint at how to fix it.
