Formerly known as SilverOS (previously featured on OSnews),
FireFly is a commercially supported BSD system based on DragonFlyBSD. You can read the FireFly whitepaper here.
Formerly known as SilverOS (previously featured on OSnews),
FireFly is a commercially supported BSD system based on DragonFlyBSD. You can read the FireFly whitepaper here.
I’d worry about the maturity of the DragonFly kernel given the extensive refactoring that’s been performed, but overall this seems like an awesome idea and I wish them the best of luck.
http://www.crescentanchor.com/company/clients/
List includes Netscape, Cygnus, and DEC
Do they have a time machine? Be interested to know how Netscape and DEC are using this new product.
It doesn’t exist and even ps format too.
http://www.crescentanchor.com/products/FireFly/
Do they have a time machine? Be interested to know how Netscape and DEC are using this new product.
Who uses Crescent Anchor, not FireFlyBSD. Besides, this is not just a guy out to make a fast buck off of DragonFlyBSD. Crescent Anchor is owned by David Rhodus. Check out these links:
The DragonFly team: http://www.dragonflybsd.org/main/team.cgi
DragonFly: End of Year Summary for 2003: http://www.dragonflybsd.org/status/report-2003.cgi
Are we gonna end up with a huge amount of *BSD distros like with GNU/Linux?
Just because linux or bsd have a large number of flavors doenst mean fragmentation. they can all follow a basic set of standards that make them compatible. the proliferation if bsd flavors just like linux distros is inevitable.
if people have the sense, they would adopt standards . thats it
It seems to me that this is a new kernel/system. They just started from BSD sources but redo all inside, part after part.
Do you call QNX just an other Unix just because they added the posix API ?
It seems to me that this is a new kernel/system. They just started from BSD sources but redo all inside, part after part.
Do you call QNX just an other Unix just because they added the posix API ?
However, I hope they wait contribute so that when a DragonFlyBSD is mature, they will be shipping a mature product.
As for value added, I wouldn’t mind paying a small amount if they bundled Crossover Office and Plugin with it. IMHO, that would be great value.
/// I wouldn’t mind paying a small amount…
if one needs the journaled filesystem, he’ll have to buy Firefly Platinum, 900 USD…
Geez, this thing is so premature. Not even some bloody screenshots. I’m with Carl. It’s a fast buck attempt that won’t even get out of the blocks.
And here’s what Matthew Dillon had to say about it when he heard about it (a good while after most other people in the DragonFly project knew about it ;^)
http://leaf.dragonflybsd.org/mailarchive/kernel/2004-07/msg00110.ht…
I *really* like DragonFly, but I’d personally have waited until at least version 1.1, which is supposed to have (among other things) a completely multithreaded, and BGL free network stack, metadata journalling, a good chunk of the VFS work completed, and very likely a 64 bit AMD64 port, as well as an M:N threading system, a new packaging system (that’s kind of like ports, but more apt-get like?), and a semi-stable set of kernel APIs.
Ah well. I guess it’s good that we’re starting to get distribution makers earlier rather than later…