Not much to report lately… Spend some time reading up on a question about documentation in PDF form that strangely turned into a thread about things like the relative quality of ext3fs, reiserfs, and ufs.
Month: March 2005
Joerg Sonnenberger has removed all the old sound support that dates back to before NEWPCM was added in FreeBSD-4. This probably does not affect anyone, as this is all for old, rare equipment, usually ISA.
Stable has slipped.
If that doesn’t make sense to you, this means that the current “bleeding edge” code has been moved to “Stable” status, as there’s no outstanding problems with it. If you’re using the “DragonFly_Stable” tag in your CVSup file, you’ll have some new things to download.
The Stable tag has not yet been moved forward, because of a new error found. Matthew Dillon posted another summary.
Devon H. O’Dell’s girlfriend happens to do dragonfly jewelry. That’s based on the bug, not BSD.
Paul Grunwald is selling his IBM laptop, which happens to run DragonFly just fine.
Matthew Dillon found this interesting collection of quotes from FreeBSD users who have purchased amd64 hardware.
John Leimon saw that DragonFly gathered some attention on the “fox-toolkit” mailing list.
Historically, access to devices by anyone other than root has been a slight hassle under BSD. Joerg Anslik’s changes to MAKEDEV have been committed, which, among other things, allows for a /etc/devices.conf that controls individual permissions for different devices, such as the CD drive.
The upcoming DragonFly release (1.5, probably) will be good, but the next release will be huge.
Matthew Dillon has committed changes to the DragonFly CD image, put together by Eduardo Tongson, so that if one is inserted in a computer running Windows, it will autorun a web page with information and links about DragonFly BSD.
As part of a longer thread about making your computer configure itself appropriately to available networks, Freddie Cash pointed at the profile.sh work in FreeBSD. This may be convertible to FreeBSD…
Matthew Dillon listed remaining bugs before the next move of the Stable tag, and also plans for the next release, which will probably be “1.5”.
YONETANI Tomokazu has already moved on to the next version of Intel’s ACPI code, and committed it.
Joerg Sonnenberger has added firmware support, put together by he and Johannes Hofmann. Does this mean DragonFly could work on specialized hardware? Boot from an EEPROM? I don’t know, but it’s fun to pretend.
Matthew Dillon detailed some of the issues he wants to be resolved before the next release, and also mentioned that the next release will be the switch to using GCC3 as the default compiler, isntead of GCC 2.95 as now. Chris Pressey followed up with news of some installer improvements he wants to include.
bsdcertification.org is now available. As you may guess from the name, it’s an organization for creating a standard measurement of BSD skills, and it’s also a very good idea. Some very clever people are behind it. There’s a mailing list available, which looks like the best way to see what happens when it happens.
If you’re looking to install DragonFly to something small, like, say, a USB memory stick, Gary Allan has some links for you.
David Rhodus posted some initial results with using a 3Ware 9500 RAID controller on DragonFly. The summarized version of the thread is this: transfer rates were 30 MB/s with FreeBSD 5.3, and 152 MB/s with DragonFly.
Rongsheng Fang suggested on users@ that the easy way to track working hardware would be to emulate an OpenBSD trick: sending a dmesg.
New at UnixReview.com: tips on find, that most useful and obfusticated of utilities.
The Donations page on dragonflybsd.org has a number of new entries. Take a look, and help out if you can.
A semi-milestone: This is news item 1001. That works out to an average of 2 posts per day over the last 18 months.
Simon ‘corecode’ Schubert has committed code from Steve O’Hara-Smith adding improvements to the bktr (TV input) driver, similar to those in FreeBSD, and adding support for newer cards.
In the ongoing discussion about journaling, Dan Melomedman linked to Paul Jarc’s “/fs“.
leaf.dragonflybsd.org is apparently down or unreachable, at least from where I’m standing.
Update: Working, now – thanks, Hiten!.
shiningsilence.com was down for a good chunk of yesterday; a construction worker tripped a fuse in my house, and my UPS only kept going for so long… It’s obviously better now.
Matthew Dillon gave a further update on the journaling work, plus he noted (as many had hoped) that there would be no background fsck in DragonFly.
While talking about how to implement “undo” for disk journaling, Matthew Dillon also included some data on the relative effect of his journaling work on disk speed so far. (Look at the end of the post.)
Thomas Petazzoni posted a request on the kernel@ list for contributions to the Libre Software Meeting in July, in France.
Matthew Dillon is looking for someone with lots of time and know-how who can take on the userland side of his journaling work. Just read it, and you’ll see.
Matthew Dillon has checked in a large update to msfbufs, produced by him and by Hiten Pandya.
If you’re looking for a task to fill a rainy day, Joerg Sonnenberger suggested that moving over bits of smbfs from FreeBSD 5/6 would be good.
Matthew Dillon issued this warning to folks with accounts on leaf: Due to an increase in automated ssh scans, he’s implemented a security policy that may lock you out if you goof up your login. Mail him if that does happen.
I’ve seen these same ssh scans with some frequency for at least a few months; these scans appear to be looking for poorly configured machines. Not a huge threat, but enough to warrant a closer eye.
It appears to be similar to FreeSBIE, though more oriented towards system maintenance. Once compressed filesystems are possible under DragonFly, a DragonFly version of these sorts of products should be easier to do.