On Sun, May 24, 2009 at 10:07 AM, vega_yaa at hotmail.com <mail at belenix.org> wrote: > Hello, > > Network and everything is up now. > Able to access Belenix via SSH using PuTTy.
Hurrah ! :) > > Time to configure samba. to map home dir of mine accesible from Windows. > I've not used either samba or cifs yet. You should try both, preferably CIFS, since there's some ZFS level integration with that. > Imp tip for newbies: Do not try to telnet to your Belenix box. It's disabled > I think by default. Also 1 more thing do not log in as root it wont allow you > to do that by default. Log in using user name and then do su to switch to > root via SSH. And telnet is not secure so dont use it. > Other tips: - use pfexec to execute commands that require you to be root. - investigate RBAC > Now it's time to put Belenix on WAN ip to set up ftp and other misc stuff to > test ZFS's access speed. :-) ?I am having Fujitsu 5200 RPM SATA drive in my > ThinkPad and Intel gigabyte ethernet. > Once you upgrade to the latest 111 release, you'll have new goodies as well as crossbow. Your ethernet card can be put to good use by crossbow :) > Any1 can suggest me free CVS server? I want to set up for demo and will ask > developers to access it and do check-in/out. Do they require Belenix at there > end for fast/speedy check-out? Most of them currently use Tortoise SVN. > Please check if the CVS that comes with Belenix is useful enough for you (in terms of revision numbers, bug fixes, etc). If your team mates use TortoiseSVN, then that's what you need. The Belenix team has not yet built the 1.5.x SVN binaries, and I recommend that you use the SVN binaries from the Collabnet site rather than from tigris.org You may want to read my blog post on SVN mirroring and get that working on ZFS. I recommend that you create a separate file system for the SVN mirror, and that you investigate marking a ZFS snapshot via the post-commit hook. You could have a cron job that deletes snapshots such that only the most 50 recent snapshots are retained. This way, you'll have a way to remove commits that should not have been made in the first place (I'm an SVN admin, and this one scenario always gives me nightmares!). Disk I/O at the server side will definitely be much faster since that is ZFS. At work, here are the disk I/O speeds that I've seen for a checkout of a particular SVN folder: - Belenix on a Dell 630 (5400 RPM drive) - under 5 mins - OSX on Mac Book Pro - 6 to 8 mins - Windows 2008 on a Dell 630 (5400 RPM drive) - 17 minutes - Windows XP on a Dell 630 (5400 RPM drive) - 30 mins + I haven't bothered testing with Vista. As you can see, disk I/O with Belenix is extremely fast. > I want to export existing CVS from my Sun Enterprise 250 box to Belenix which > I'll set up in office. I am not sure about compatibility but hopefuly it'll > work. Any suggesions? :-) That enterprise 250 box consumes lot of electricity > and space too. I am going to exchange that box soon while purchasing new 2U > Nehelam based Sun server. > I decided some time ago to move from Belenix to Solaris 10 U6 for my proposed SVN server. This is because I was using an untested version of Belenix at that time. Today, I'd go with b101 for SVN because I've used that as my OS for the past six months without facing any problems whatsoever. I can't myself say the same for b111 or the soon-to-come b114, because I've not run those yet. For server side mission critical file system related tasks, I'd recommend Solaris rather than Belenix because the ZFS on Solaris 10 is much more tested and you could even get commercial support on that in a pinch. An ideal scenario would be to snapshot each commit and to use svnsync to mirror each commit to another ZFS RAIDZ based server. > Regards, > Amey. > > > _______________________________________________ > belenix-discuss mailing list > http://mail.opensolaris.org/mailman/listinfo/belenix-discuss > http://groups.google.com/group/belenix-discuss >
