From the DragonFly BSD Project website, “One year after starting the project as a fork off the FreeBSD-4.x tree, the DragonFly Team is pleased to announce our 1.0 release! … We have done so much that it cannot all be listed here. Please check out the Diary for technical details.”
http://www.energyhq.es.eu.org/files/dfly-1.0REL.iso.gz.torrent
This torrent was created/provide by Miguel Mendez.
Here’s the oficial announcement: http://marc.theaimsgroup.com/?l=dragonfly-kernel&m=108965741503894&…
Are they using the ncurses FreeBSD installer or do you have to do it all manually from a LiveCD? I didn’t see it mentioned. Anyway this is exciting. There is nothing sadder than an ambitious project falling to shit… apparently this hasn’t happened here! Any word from the FreeBSD camp as to what they think of the changes and what if any do they plan on incorporating back in? That would be an interesting interview: a FreeBSD review of Dragonfly.
Are they using the ncurses FreeBSD installer or do you have to do it all manually from a LiveCD? I didn’t see it mentioned.
The CD is a Live CD, and it includes their very own installer now, currently with both a stable ncurses front-end, and an experimental web-based front-end. The DragonFly installer was designed so that one could implement any front-end they wish.
I’ve been using DragonFly since February, and it’s been fantastic.
Has anyone done a comparison between dragonfly 1.0 and freebsd 4.10? If so, was it any faster/more stable etc?
Has anyone done a comparison between dragonfly 1.0 and freebsd 4.10? If so, was it any faster/more stable etc?
Seeing as how 1.0 was released last night and announced today, it’s not too likely that too many people have had a chance to compare the two. ;^)
http://www.shiningsilence.com/dbsdlog/archives/000209.html
Anyone have any luck with the posted BitTorrent or know of any other? I get a “source cannot be read” error using Firefox 0.9.2 on XP.
http://www.livebsd.com/dfly/releases/dfly-1.0REL.iso.gz.torrent
and also
http://www.livebsd.com/dfly/releases/dfly-1.0REL.iso.gz
The installer is completely new from the FreeBSD installer.
Much more emphasis has been placed on useability. Although the installer does not currently support bizarre install methods it has shaped up very nicely.
I let a linux friend install it on one of my boxes over the internet (via the cgi frontend) and he was quite impressed.
It is definitely worth the effort to download and try out if you have a spare machine/hd/partition.
Here’s a functional torrent:
http://download.exodusmachine.net/torrents/dfly-1.0REL.iso.gz.torre…
even has a couple seeds on it.
The 1.0 release came a lot faster then I had imagined. I was very interested from the start and followed a long as well as I could. DragonFlyBSD is nice *NIX and I hope to be using it in the future.
Best of luck.
time to download & test it
DragonFlyBSD started because the FreeBSD team was afraid of innovation and change. It’s too bad, but after all, now we have DragonFly so it’s serves them right. Look, you either look forward in this ever changing world or get stepped on. Now FreeBSD gets stepped on not only by Linux but also what I would consider a close relative…DragonFly.
A close relative of… linux?
Anyway despite all the progress of Dragonfly and my faith in Matt Dillon it has yet to prove itself. Everything looks good on paper but that doesn’t always translate. Plus 1.0 is more of technology preview. Not enough of their goals are implemented to really begin whooping Linux and FreeBSD Anyway FreeBSD runs quite fast and threading and smp wise took a very similar path to Linux 2.6. I seem to remember on some benchmark that the only thing Linux 2.6 stomped FreeBSD was mmap calls.
A close relative of FreeBSD, referring to DragonFly, not Linux.
More information on the installer can be found at http://bsdinstaller.com
“DragonFlyBSD started because the FreeBSD team was afraid of innovation and change.” — ok, ill take this bait.
Huh? I thought Matt went off because he didn’t agree with most FreeBSD people on how they are taking to improve it. Isn’t that innovating (even gambling), much less changing?
Anyway, is there an upgrade path of similar procedure (make world) from a running FreeBSD to DragonFly (I hate the name, btw ) ?
[i]Plus 1.0 is more of technology preview.<i/>
Yes, I suspects (still d/l-ing) that 1.0 may not be up to snuff. I think that possibly 1.0 was rushed to helped build momentum. Or perhaps they have decided to take the Linux route and not wait till perfect but good enough and just release more often?
is that DragonflyBSD is likely already faster and more scalable then FreeBSD 4.x. Read that one more time, 4.x. I’m not sure how it would compared to 5.x let alone Linux 2.6 – but things are shaping up much faster then I ever expected. Kick ass!
just installed rel1.0 and it went very well.
now, i wanted to see how it performs using some software we commonly use. i was glad to see that most of the common base BSD libraries are there … but i ran into a problem .. packaging?
how do i install additional software? for example bash? compilers, … there is no ports tree (no one said there would be one). there is no sysinstall. pkg_add may be there but neither the website not the man pages tell you where to point it. the command “installer” is there but fails to repsond to keyboard input – but it worked duriong the actual installation.
i’ll post my thoughts on howit performs.
Anyway, is there an upgrade path of similar procedure (make world) from a running FreeBSD to DragonFly (I hate the name, btw ) ?
Yes, you can cvsup their source-tree, and do the make {build|install}{kernel|world} thing from FreeBSD. Reboot, and you’ll be in DragonFly. I tried it (a while before the 1.0 release) and it worked fine.
but does this thing run GNOME yet, I would love to try it out – since the BSDs are generally nice OSes , and DragonFly sounds like a fun and interesting concept.. But if it doesn’t run GNOME, I can’t get any work done and I only have one machine currently.
Their website doesn’t say much about the supported packages currently.
Oh and I’m happy to see so much fresh development in the BSD world, new companies popping up everywhere and fresh ideas being implemented..
Packaging is probably the less functional part of dfbsd at the moment. Right now it uses the same port tree of FreeBSD with a few overrides in /usr/dfports. Unfortunately not everything works correctly at the moment, and a few important ports are broken (gnomevfs2,qt33), so you’ll hardly be able to use a full Gnome or Kde environment. Plus, the overrides don’t behave well with portupgrade.
i’ve just run some unscientific tests – threading/networkig/throughput tests – and compared to freebsd 4.10 and freebsd 5.2.1 it performs as well (no drastic improvements).
one important observation was that it seems to perform more consistently – that is the resulting graphs (of time taken to complete transactions) is much less scattered. now that is very useful!
but if theres that much trouble with the ports system maybe i’ll wait for another release
doesnt sound like it should be 1.0 at all yet
@lovechild, others
Yes, it is possible to run KDE3 or Gnome 2.6 on DragonFly. I run Gnome 2.6 personally.
This release is not intended for your average user though, DragonFly is very much a developer project at the moment.
…out of curiousity, what hoops did you have to go through to get a working gui (gnome) system? I’d like to try it and play with it, but I definitely like a gui to play with…
Mike
…out of curiousity, what hoops did you have to go through to get a working gui (gnome) system? I’d like to try it and play with it, but I definitely like a gui to play with…
Well, the easy way is to change the remote package repository (man pkg_add) so that it get’s packages from FreeBSD.org, and then just ‘pkg_add -r’ it.
Until quite recently, FreeBSD packages were used exclusively, but now DragonFly defaults to trying to get things from the severely broken repository at http://www.gobsd.com and you’ll be lucky to get anything really big from there. GNOME and KDE aren’t even options unless you go back to the FreeBSD repositories.