DragonFly BSD
DragonFly users List (threaded) for 2006-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Serious question: Is DragonFly's smp ISP-production-ready?


To: "Martin P. Hellwig" <mhellwig@xxxxxxxxx>
From: Tomaž Borštnar <tomaz.borstnar@xxxxxxxx>
Date: Wed, 19 Apr 2006 20:14:34 +0200

Martin P. Hellwig pravi:
walt wrote:
Tomaž Borštnar wrote:
[...]
Or should I go with FreeBSD?

It all depends on which one do you know how to administer. Both will work.

Heh. I'm an amateur so I'm incompetent on both systems ;o)


Seriously, is there much difference from a professional sysadmin's
perspective?  Can you give some examples, perhaps, of where the
admin would notice a big difference between DragonFly and FreeBSD?

One excellent value for DF over FreeBSD is that properly reported bugs gets attention and gets fixed much faster.
This has already helped me in the past - had occasional bugs and after one of them I (physically) went to server to try to provide more info for Matt and 2 hours later bug was found and fixed. It was in cvs even before I got mail from Matt and it was all very fast!


The only other thing why I would go with FreeBSD instead of DF is lack of diversity in pkgsrc compared to ports, but even that is changing towards pkgsrc - still catching diversity in ports though.

Also for new file server DF seems excellent choice, because developers are very concerned that it works great and use it for themselves. And this is even without cluster plans!


Of course migrating to another platform requires extensive testing of all required applications, which could hold you back because it's more effort then it's worth, but if you have to migrate anyway (i.e. FreeBSD 4 to 6) then you could consider other platforms too.
Exactly!


Personally my production network ( 7 FreeBSD servers, 6 virtual on MS VirtualServer and 1 on the machine direct which is a jail host server) and test network (3 FreeBBSD's, 1 DragonFlyBSD all on VMWare <Debian
no problems with timekeeping in DF? I still need to have rdate in cron in order to fix time slips with 1.4.3 under Vmware Server.

p.s.
I do not have bad experiences from FreeBSD project responsiveness generally, but you can always read ramblings from people who feel that somebody should help them fix problems faster. I know that FreeBSD is bigger project and with a lot of people you often have problem with scheduling them :)




[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]