Re: [Discuss] Getting OS/HW details?
On Nov 2, 2012, at 1:09 PM, Scott Ehrlich wrote: If I wanted to write a script to obtain distro flavor (Ubuntu, CentOS, RH, Mint, BSD, Solaris, etc), major/minor version (5.3, 10.6, etc), hardware brand/make/model, at least for starters, what would be the best way to attack it? My approach would be to use something that's already available, unless there was a pressing need otherwise. I'd suggest facter by folks at the Puppet labs: http://www.puppetlabs.com/puppet/related-projects/facter/ # facter operatingsystem CentOS # facter operatingsystemrelease 6.2 # facter productname X8DTT-INF There are a lot more facts built-in: # facter | wc -l 75 ~irl ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
Re: [Discuss] Anyone tried Sparkleshare.org yet?
On Jun 22, 2011, at 5:20 PM, Jack Coats wrote: Sparkleshare is an opensource version of Dropbox. They say currently implemented for Linux and Mac. Has anyone tried it out yet? I've recently given it a go hoping to be able to provide a dropbox-like experience for some users at work that expressed a need for sharable project folders accessible from anywhere. They are looking into paying for Dropbox because it just works (can't argue there), and I'm hoping to lure them back to using our network storage in a new way. That said, I've had a few issues with Sparkleshare: * Decision to use ~/SparkleShare as a base directory - this directory isn't synced, it's just a home for synced dirs. this is confusing for end-users. * Reliance on git (currently... unison support is apparently coming) - slow and expensive commits for binaries (might be able to use git-bigfiles?) - duplicate bits stored in local git repo means nearly doubling your local storage req's * Basically no error notifications * DIY server still rough around the edges - still relies on using SparkleShare's XMPP server for notifications - initial setup of the client is weird; if you don't have the server in your ~/.ssh/known_hosts file, it fails. When it's working, it does work pretty well even with these limitations. I've synced about 5GB to a local server and have done lots of edits/additions/deletions to stress test it. There have been times where it appears to be working forever, and I have to quit and restart the app. Ultimately, it's not ready for deployment and I'd caution that it's really only ready for someone that is prepared to babysit it a bit. ~irl ___ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
