Software-update: DragonFly BSD 5.0

Bij een BSD-besturingssysteem denken de meesten aan een van de drie varianten FreeBSD, OpenBSD of NetBSD. Er zijn echter nog diverse andere BSD-versies, zoals TrueOS en DragonFly BSD. Deze laatste is een afsplitsing van FreeBSD 4.8, dat rond juni 2003 is ontstaan. Dit gebeurde omdat Matthew Dillon, de projectleider van DragonFly BSD, het destijds oneens was met de gekozen ontwikkelstrategie en de aandachtsgebieden van FreeBSD 5. Voor een overzicht van de ontwikkelingen met betrekking tot DragonFly BSD sinds die tijd kun je deze pagina doorspitten. Versie 5.0 is sinds kort beschikbaar en werd met de volgende aankondiging uitgebracht:


DragonFly version 5.0 brings the first bootable release of HAMMER2, DragonFly's next generation file system. The details of all commits between the 4.8 and 5.0 branches are available in the associated commit messages for 5.0.0rc1, 5.0.0rc2, and 5.0.0.

Big-ticket items

Preliminary HAMMER2 support has been released into the wild as-of the 5.0 release. This support is considered EXPERIMENTAL and should generally not yet be used for production machines and important data. The boot loader will support both UFS and HAMMER2 /boot. The installer will still use a UFS /boot even for a HAMMER2 installation because the /boot partition is typically very small and HAMMER2, like HAMMER1, does not instantly free space when files are deleted or replaced.

DragonFly 5.0 has single-image HAMMER2 support, with live dedup (for cp's), compression, fast recovery, snapshot, and boot support. HAMMER2 does not yet support multi-volume or clustering, though commands for it exist. Please use non-clustered single images for now.

ipfw Updates
IPFW has gone through a number of updates in DragonFly and now offers better performance. pf and ipfw3 are also still supported.

Improved graphics support
  • The i915 driver has been brought up to match what's in the Linux 4.7.10 kernel. Intel GPUs are supported up to the Kabylake generation.
  • vga_switcheroo(4) module added, allowing the use of Intel GPUs on hybrid-graphics systems.
  • The new apple_gmux driver enables switching to the Intel video chipset on dual Intel/NVIDIA and Intel/Radeon Macbook computers.
Other user-affecting changes
  • efisetup(8) added.
  • DragonFly can now support over 900,000 processes on a single machine.
All changes since DragonFly 4.8

  • if_sl, if_ppp, and if_faith are now built as modules and can be removed from kernel configs.
  • NX (no-execute) pmap support has been added.
  • Use 64-bit serials for poll/select's kevent.udata. This fixes an issue where serial cycling could cause spurious events to be reported.
  • Fix several issues for encrypted installations.
  • Fix a blocked-lock issue in procfs
  • Fix a serious permissions bug for sticky directories
  • Fix event preset bug
  • Fix an ACPI initialization ordering issue
  • Fix a CAM shutdown ordering issue
  • NX support added to kernel, but does not work with some interpreted or JIT languages so disabled by default.
  • Fix a crypto subsystem stall.
  • Ryzen CPUs can lockup when the instruction pre-fetcher (which can be speculative) transitions from a canonical to a non-canonical address. This can happen if the top of the user stack is mapped. Unmap the top of the user stack, and the top of the user stack is no longer considered to be part of userspace.
  • Longer stir in arc4random(), make arc4random per-cpu to reduce contention.
  • Fix a zget() panic which can occur during heavy paging
  • Fix clustering inefficiencies
  • tmpfs and vn can't handle certain swapoff situations. Be sure to fail a swapoff attempt under such conditions so not corruption occurs.
  • Fix a gcc code reordering problem related to td_critcount operations. This fixes a lockmgr() race.
  • Significantly reduce tsleep()/wakeup() queue collisions.
  • Do many more NUMA-localized allocations for per-cpu structures.
  • Add better AMD topology detection.
  • Restrict kill(-1, ...) to the current reaper group. This fixes issues during bulk builds via synth where third-party programs erroneously signal process -1 after a fork() failure.
  • Fix broken cpu rotator in lwkt_alloc_thread().
  • Fix a rare allproc scan vs p_ucred race
  • Fix unnecessary ucred duplication which led to potentially as many ucred allocations as vnodes.
  • Fix a memory ordering race in the shared lock mutex code.
  • Fix an ordering issue with coincident systimer interrupts. This improves user/sys/idle percentage reporting.
  • Change our MBR partition type from 0xA5 (which we shared with FreeBSD) to 0x6C
  • Fix a callout_stop()/callout_reset() rearming race
  • Improve flushing during low-memory situations
  • Add an emergency pager. The normal pager can pageout vnode-backed pages, but the complexity of the filesystem VFS can cause low-memory deadlocks during such flushes. The emergency pager only pages out anonymous memory and can recover these situations.
  • Fix the panic() code for AMD cpus that assumed mwait hinting support when there might not be any.
  • Improve TSC handling.
  • Fix a SMP tsleep_interlock() vs wakeup() race.
  • Validate the kernel up to 1 million processes (since PIDs are restricted to 6 digits, this is the max). Fix numerous issues that crop up under high-process-count conditions. Yes, it actually does work.
  • Increase the default posix-lock limit.
  • Remove a performance bottleneck related to large numbers of pipe() close() operations.
  • Scale tsleep() performance to hundreds of thousands of processes.
  • Refactor the maxproc calculation, allowing maxproc to be higher without improperly scaling maxvnodes and other resources to insane levels.
  • Refactor the load calculation code to not stall cpu 0 when a large number of processes are present (aka a million procsses).
  • Fix excessive call stack depth for stuck interrupts.
  • Refactor IPI vector assignments and reformulate INVLTLB IPIs
  • Direct input support for polling, on by default for ix(4).
  • Allow up to 64 TX and RX rings for X550 chipsets
  • Do not pad if_re chips which do not require explicit padding. This fixes UDP checksum generation on these chipsets.
  • Limit the number of accepted sockets that kevent() reports. Defaults to 32. Does not effect accept() calls. This deconfuses some third party applications.
  • Bring in vmx (VMWare virtual network driver, aka vmxnet3).
  • Add Kabylake support (add Kabylake PCI IDs)
  • Improve syncache performance.
  • Add an interface network filter to IPFW.
  • Add an ipfrag filter to IPFW.
  • Rework IPFW's states and tracks.
  • Reduce unnecessary IPIs by using sendmsg_oncpu() when possible.
  • Improve ipflow code.
  • Improve polling code.
  • Fix issue with accelerated IPv4/IPv6 fragment draining.
  • Randomize the local port.
  • MSI enabled by default for if_em devices which support it.
Other drivers
  • virtio_scsi(4) added
  • ig4(4) devices are now recognized.
  • internal updates to the isp(4) SCSI adapter driver.
  • ADMA2 mode is now supported for SD card data transfer.
  • UHS1 SD card disk format is now supported.
  • Properly delete /dev/dsp and /dev/mixer on sound module unload.
  • NVMe now handles devices without MSI-X support (aka virtualized NVMe).
  • vtnet and virtio_blk improvements.
  • HAMMER1 now is at an internal version of 7, reflecting a new, faster checksum operation.
  • kcollect(8) has been added for automatic data gathering on a running DragonFly system.
  • sshlockout(8) will now lock out based on number of attempts.
  • Fix a static buffer overflow in mfiutil
  • Fix a graphics compatibility enable test in 'window'
  • Fix several sscanf bugs in userland
  • usched now allows a process to change its own cpu affinity
  • Fix a bug in ceill()
  • Fix a seg-fault on crypt failure.
  • Many namespace cleanups to improve dports compatibility.
  • OpenSSH updated to 7.6p1
Various tools have been upgraded in the base system:

Hammer Changes
  • Improve concurrent dedup stability under heavy concurrent loads.
  • HAMMER to version 7. This version changes the CRC mechanic from an older slower CRC API to the ISCSI CRC code, which is 6x faster. Improves HAMMER performance. HAMMER supports both old and new CRC methods and is backwards compatible, but only files created after this change will use the new mechanism.
Clang status
  • A starting framework has been added for using clang as the alternate base compiler in DragonFly, to replace gcc 4.7. It's not yet complete. Clang can of course be added as a package.
Package updates
  • Many package updates but I think most notably we need to point to chrome60 finally getting into dports with accelerated video and graphics support.
64-bit status
  • Note that DragonFly is a 64-bit-only operating system as of 4.6, and will not run on 32-bit hardware.
  • AMD Ryzen is supported and DragonFly 5.0 has a workaround for a hardware bug.
Versienummer 5.0
Releasestatus Final
Besturingssystemen BSD
Website DragonFly BSD
Licentietype Voorwaarden (GNU/BSD/etc.)

Door Japke Rosink


17-10-2017 • 17:22

1 Linkedin

Bron: DragonFly BSD


Reacties (1)

Wijzig sortering
Matt Dillon lijkt de kar wel aardig te trekken, maar een complete BSD vooruitwerken is natuurlijk niet makkelijk, en onder opensource-besturingssystemen is Dragonfly uiteindelijk toch een van de kleinen. Maar HAMMER2 lijkt nu ook langzaam maar zeker wat vooruit te komen en een bestandssysteem met moderne features en een BSD-licentie is ook voor de andere BSDs interessant.

Op dit item kan niet meer gereageerd worden.

Kies score Let op: Beoordeel reacties objectief. De kwaliteit van de argumentatie is leidend voor de beoordeling van een reactie, niet of een mening overeenkomt met die van jou.

Een uitgebreider overzicht van de werking van het moderatiesysteem vind je in de Moderatie FAQ

Rapporteer misbruik van moderaties in Frontpagemoderatie.

Google Pixel 7 Sony WH-1000XM5 Apple iPhone 14 Samsung Galaxy Watch5, 44mm Sonic Frontiers Samsung Galaxy Z Fold4 Insta360 X3 Nintendo Switch Lite

Tweakers vormt samen met Hardware Info, AutoTrack,, Nationale Vacaturebank, Intermediair en Independer DPG Online Services B.V.
Alle rechten voorbehouden © 1998 - 2022 Hosting door True

Tweakers maakt gebruik van cookies

Tweakers plaatst functionele en analytische cookies voor het functioneren van de website en het verbeteren van de website-ervaring. Deze cookies zijn noodzakelijk. Om op Tweakers relevantere advertenties te tonen en om ingesloten content van derden te tonen (bijvoorbeeld video's), vragen we je toestemming. Via ingesloten content kunnen derde partijen diensten leveren en verbeteren, bezoekersstatistieken bijhouden, gepersonaliseerde content tonen, gerichte advertenties tonen en gebruikersprofielen opbouwen. Hiervoor worden apparaatgegevens, IP-adres, geolocatie en surfgedrag vastgelegd.

Meer informatie vind je in ons cookiebeleid.


Toestemming beheren

Hieronder kun je per doeleinde of partij toestemming geven of intrekken. Meer informatie vind je in ons cookiebeleid.

Functioneel en analytisch

Deze cookies zijn noodzakelijk voor het functioneren van de website en het verbeteren van de website-ervaring. Klik op het informatie-icoon voor meer informatie. Meer details


    Relevantere advertenties

    Dit beperkt het aantal keer dat dezelfde advertentie getoond wordt (frequency capping) en maakt het mogelijk om binnen Tweakers contextuele advertenties te tonen op basis van pagina's die je hebt bezocht. Meer details

    Tweakers genereert een willekeurige unieke code als identifier. Deze data wordt niet gedeeld met adverteerders of andere derde partijen en je kunt niet buiten Tweakers gevolgd worden. Indien je bent ingelogd, wordt deze identifier gekoppeld aan je account. Indien je niet bent ingelogd, wordt deze identifier gekoppeld aan je sessie die maximaal 4 maanden actief blijft. Je kunt deze toestemming te allen tijde intrekken.

    Ingesloten content van derden

    Deze cookies kunnen door derde partijen geplaatst worden via ingesloten content. Klik op het informatie-icoon voor meer informatie over de verwerkingsdoeleinden. Meer details