If you have an existing DragonFly system, and want to use rm -I, it’s explained here.
Matthew Dillon changed the download page to note that dfly-stable-20041009.iso.gz is the best recent release to start with.
Matthew Dillon wrote a little more about how the VFS work is set up, and he posted a patch with his first day of work on the issue. (11,000 lines of code!) Don’t try it unless you feel really lucky.
Matthew Dillon has added (partial) support for devices such as the Logitech Desktop Pro, as suggested by Roland Hammerle from what he found in a FreeBSD patch.
Matthew Dillon has seen some problems on his test machines for DragonFly_Stable, so he’s pushing the tag back to the Sept. 13th point, for reasons he detailed in a separate message. Make sure to be using this if you have a production machine.
Joerg Anslik pointed out that dreamsticker.de now has specific DragonFly case badges available. No image needed, no minimum order, and shipping outside of Germany is possible.
The DragonFly_Stable tag has been slipped up to correct a memory leak and incorporate the ‘rm -I’ fix. This does place the stble code right smack in the middle of the VFS changes, but those appear to be at a stable point right now.
Giorgos Keramidas, after reading an article about how rm -rf / (i.e. accidentally deleting your operating system) is avoided by Sun, suggested on the hackers@freebsd.org mailing list some changes to protect from that. An extensive discussion (bikeshed) ensued. See “Protection from the dreaded “rm -fr /” thread on the former link, if you are curious. It’s still not resolved.
On the other hand, this has been quickly fixed in DragonFly, without changing the basic function of rm. New installs will have this safer behavior by default, though the old unsafe setup can be restored if desired.
In a recent post to kernel about adding devices, Matthew Dillon describes how and why device adding on DragonFly deviated from FreeBSD-4, and how it could (eventually) lead to a different sort of devfs.
The Installer is spreading – look at livebsd.com. Specifically, the 5th item down mentions using the Installer with FreeBSD 5.3b7.
Matthew Dillon found that his recent VFS changes made linux_base-8 work again. Be warned that these changes are in the not-necessarily-completely-stable current version of code, not stable.
Joerg Anslik sent along a note that dreamsticker.de took a supplied image and turned it into a 2.5 sq.cm case badge for him.
Joerg Anslik wrote: “Just order “3D-Wunschsticker” (5 is minimum) and send him a 300 dpi picture (or whatever) in a separate mail refering to the order number
you’ll receive.”
This should work for any Germany residents; the dreamsticker.de is in German so I can’t identify if they ship outside of the country.
OffMyServer.com has apparently donated an Intel-based blade server for general use in developing DragonFly. It’s being set up today by Devon H. O’Dell, as far as I know… Thanks, OffMyServer!
Update: Pictures!
Some problems have been reported now that the new code is in; this sort of trouble was anticpated, so stick to the DragonFly_Stable tag if you want to avoid this trouble.
Matthew Dillon described his ‘stage 7b’ in a commit message, which includes a description of an upcoming improvemwnt to NFS.
George Georgalis found The C Book from 1991, which he said was helpful with learning.
Matthew Dillon pointed out just why the complete BSD license is reprinted in a file, instead of a reference to another location as is usually done with GNU.
Matthew Dillon has posted his 5th VFS patch; included is some backstory on just how the old and new APIs work.
Update: and it begins. This is going to be unique to DragonFly, probably.
Matthew Dillon wrote that the DragonFly_Stable tag is being moved up to the current code, as his potentially destabilizing VFS work is going to be going into the tree, starting tomorrow.
The moral: if you have production or near-production machines, stick with the stable tag, for now.
If your buildworld chokes on a nonexistent authpf group, read this note from Matthew Dillon.