[Nova izdanja] DragonFly BSD

Citat:DragonFly 2.2.1 Release Notes

Kernel changes

• Fixes for libthread_xu: MAP_STACK and an errno leak.

Hardware changes

• Bug fixes for sppp(4), and i4b(4).
  
• Fixed recursive lock in detached close of /dev/tty.

HAMMER changes

• HAMMER VFS: Added missing hammer_rel_volume() call in deadlock/retry case.

Networking changes

• Allowed the IP_MINTTL socket option to be set to zero.

Release improvements

• Fixed an installworld failure due to kernel fixes and a libthread_xu issue.
  
• nstaller now works correctly in the console, and properly creates device files if they don't exist.

Userland changes

• Updates for msdosfs, pax(1), and magic(3)
  
• Allowed uid/gid/flags changes to fail if running cpdup as a user

Contributed software

• Synced zoneinfo database with tzdata2009f from elsie.

Security updates

*]FreeBSD-SA-09:05.telnet - fix environment based code execution vulnerability

Three release options are now available: Our bare-bones CD ISO, a DVD ISO which includes a fully operational X environment, and a bare-bones bootable USB disk-key image (less than 512M).

Release Announcement: http://www.dragonflybsd.org/release22/
Download mirror-i: http://www.dragonflybsd.org/mirrors/

Za sve one koji prate DragonFly BSD, izdato je 2.6 (zapravo 2.6.1) izdanje. Evo novina koje ovo izdanje donosi:


DragonFly 2.6.1 Release Notes

Release Improvements

Kernel changes

• Ported tmpfs (efficient memory filesystem) from NetBSD
  
• Added support for minidumps
  
• Added swapcache support for SSDs
  
• Ported POSIX Message Queues from NetBSD (Google Summer of Code Project).
  
• Updated Linuxulator (now runs java, flash,...) for i386
  
• fixed vinum root mounts
  
• Added watchdog framework (compatible with watchdogd( 8 ))
  
• Added gpio framework
  
• Ported minidumps from FreeBSD (enabled by default)
  
• Added vkernel64 (64-bit vkernels - experimental)
  
• Added hotplug pseudo-device
  
• Removed msfbufs and reimplemented sfbufs as a consumer of the newly added lwbufs (lightweight buffers)
  
• fixed checkpointing
  
• Updated opencrypto from FreeBSD-current
  
• Updated ACPI from FreeBSD 7.2
  
• Updated CPU initialization code From FreeBSD
  
• Serious reduction in KVM use for i386
  
• KVM expanded to 8GB for x86_64
  
• Major performance fixes for random I/O
  

HAMMER changes

• Updated to HAMMER version 4
  
• snapshot settings and snapstops moved out of /snapshots and into meta-data
  
• REDO generation and recovery added to support fast fsync
  
• Extended 'hammer snapls' output to print mountpoints and snapshot notes.
  
• 'hammer viconfig' takes editor preference into account now
  
• Numerous low-memory deadlocks fixed
  

Hardware changes (non-networking)

• uchcom(4): The driver for WinChipHead CH341/CH340 is now working stable
  
• glxsb(4): The driver has been imported from FreeBSD
  
• hifn(4): The driver has been fixed to work with updated opencrypto
  
• cs5536: Added support for watchdog and gpio on this chip
  
• nsclpcsio(4): The driver has been imported from OpenBSD
  
• Geode LX: Enable identification and features of this CPU
  
• New aibs(4) driver for ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensors
  
• New kate(4) and km(4) drivers for AMD Family 0Fh, 10h and 11h AMD64 temperature sensors
  
• New aps(4) driver for ThinkPad Active Protection System accelerometer
  
• New wbsio(4) driver for Winbond LPC Super I/O attachment of lm(4) on any ISA port
  

Hardware changes (networking)

• Imported the alc(4) driver for Atheros AR8131/AR8132 NICs
  
• Imported the e1000(4) driver from FreeBSD for Intel Pro/1000 NICs
  

Userland changes

• null mounts now accept -o update
  
• awk(1): increased input field separator width to handle extended regexps.
  
• cpdup(1): added -VV option to verify file's contents and ignore mtime entirely.
  
• mount_nfs( 8 ): rdirplus is now the default
  
• periodic( 8 ) security now also reports pkgsrc vulnerabilities
  
• watchdogd: import from OpenBSD
  
• hotplugd( 8 ): import from OpenBSD
  
• amd64 related changes
  
• amd64 has been renamed to x86_64
  
• 64-bit vkernels now work on 64-bit boxes
  

Removals

• The T/TCP extension is no longer supported
  

Contributed Software

• Updated BIND to 9.5.2-P3 incl. DNSSEC support available by default
  
• Updated SENDMAIL to 8.14.4
  
• Updated wpa_supplicant to 0.6.10
  
• Updated hostapd to 0.6.10
  
• Updated groff to 1.20.1
  
• Updated file to 5.04
  
• Updated ncurses to 5.7
  
• Updated top to 3.8beta1 including DragonFly specific patches
  
• Updated less to 436
  
• Updated openssh to 5.3p1 (with HPN patch)
  
• Updated gcc 4.4 to 4.4.2
  
• Added binutils 2.20
  
• Added cryptodev support to OpenSSL
  

Security related

• ssh server: change defaults for new installations to disallow plain text passwords and allow root login via public key
  

Big-ticket items

swapcache - This is a mechanism which allows an attached solid state drive to be used to cache data and/or meta-data for other filesystems. The meta-data caching feature is particularly useful for machines which manage millions of files. About 2 million inodes and their related blockmaps can be cached per gigabyte of SSD. DragonFly supports up to 32GB of swap, per swap device (up to four) on i386, and up to 512GB of swap, per swap device, on 64-bit, so a very large number of inodes can be cached. Please see the swapcache( 8 ) manual page for more information.

HAMMER - Our filesystem now supports a REDO log on top of the UNDO log it already had. The filesystem will use the REDO log forward-log write and file-extend operations which allows fsync to accomplish its goals with only REDO log writes. This greatly improves the speed of fsync without weakening HAMMER's fast-recovery feature.

tmpfs - The tmpfs port we did from NetBSD is able to fully utilize the VM page cache on the system as well as swap space, with no duplication of data (unlike MFS) and very good cache characteristics which reduce or eliminate disk activity under nominal operation.


Preuzimanje: http://www.dragonflybsd.org/mirrors/

A evo i linka do stranice sa objasnjenjem kako preci na 2.6 izdanje sa 2.4: http://www.shiningsilence.com/dbsdlog/2010/04/10/5729.html



DragonFly Release 2.10

Najnovije izdanje iz DragonFly BSD kuce, sa mnogo novina, najvaznije su izlistane dole:
Citat:
Big-ticket items

Hardware and multiprocessor support - This release supports a much larger variety of hardware and multiprocessor systems than previous releases, thanks to updates of ACPI and APIC and ACPI interrupt routing support.

Hammer Deduplication - Hammer volumes can now deduplicate volumes overnight in a batch process and during live operation. The 'hammer dedup-simulate' command can be used to estimate space savings for existing data.

Packet Filter (pf) - Pf was updated to a version based upon OpenBSD 4.4. The previous version of pf in DragonFly was based on OpenBSD 4.2.

Compiler updates - DragonFly now uses gcc 4.4 as the default system compiler, and is the first BSD to take that step.

New bridging functionality - The bridging system has been rewritten. Multiple interfaces on a single system can be bound together transparently under a single virtual MAC address, and bandwidth aggregated to that new interface.

MP Performance - The MPLOCK (the primary lock, that when held ensures only a single cpu is operating within the kernel) has been removed from every area except the VM system. DragonFly is one of the few non-academic operating systems to use a primary sychronization mechanism that is not a blocking mutex

Overall Performance - DragonFly now offers significant performance gains over previous releases, especially for machines using AHCI or implementing swapcache(.

ACPI Support - Major update to DragonFly's ACPI support have been made, particularly for interrupt routing.

Pored toga jos i OpenBSD pf iz 4.4, kriptovanje root i swap particije prilikom instaliranja sistema, podrska do 63 procesora i ukupno 512 GB RAM-a na 64-bitnoj platformi, pkgsrc-2011Q1 paketi, GCC 4.4.5...

DraognFly BSD dolazi u formi .iso imidza za 32-bitne i 64-bitne platforme, kao butabilni usb imidz, ili butabilni usb imidz sa X okruzenjem.
Preuzimanje na sledecim mirorima: http://www.dragonflybsd.org/mirrors/

DragonFly BSD 3.0.1

Citat:DragonFly 3.0.1 is now available! This release has superior multiprocessor support compared to previous versions. Speed has improved significantly. Big-ticket items: previously the majority of the VM was under a single token, the vm_token, now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall is improved; a new time domain multiplexing method has been added to balance storage operation types over long time periods; ACPI + interrupt routing have been upgraded, an SMP kernel will work on all machines and is installed by default; DragonFly now has tcplay(, a tool for creating and managing encrypted disk volumes.

What's new:
http://www.dragonflybsd.org/release30/

Screenshot:


Home Page:
http://www.dragonflybsd.org/

Documentation:
http://www.dragonflybsd.org/docs/handbook/

Download:
32bit GUI
http://ftp.df.lth.se/pub/DragonflyBSD/iso-images/dfly-i386-gui-3.0.1_REL.iso.bz2

32bit
ftp://dragonflybsd.mirrorcatalogs.com/dragonflybsd.....EL.iso.bz2

64bit GUI
http://mirror.optusnet.com.au/dragonflybsd/iso-ima.....EL.iso.bz2

64bit
http://mirror.optusnet.com.au/dragonflybsd/iso-ima.....EL.iso.bz2

Download Mirrors:
http://www.dragonflybsd.org/download/

DragonFly Release 3.2

Najsvezije izdanje DflyBSD sistema, dolazi sa USB stekom druge generacije (podrska za USB 3.0 izmedju ostalog), poboljsanja u scheduleru koja omogucavaju bolje iskoriscenje Intelove hyperthreading tehnilogije, kao i ponovo napisani delovi schedulera koji omogucavaju da PostgreSQL ima performanse slicne ili iste Linux kernelu, i bolje od svih ostalih BSD sistema (pogledati: http://lists.dragonflybsd.org/pipermail/users/2012-October/017536.html)
Citat:DragonFly Release 3.2

Big-ticket items

Performance improvements under database load
Significant work has gone into the scheduler to improve performance, using postgres benchmarking as a measure. See the PDF of graphed results to see the improvements. DragonFly should be now one of the best selections for Postgres and other databases.

New USB stack

USB4BSD has been incorporated into this release. More USB devices are compatible with DragonFly, and xhci (USB 3.0) users may be able to take full advantage of their newer hardware. Since this is a new feature, it is available in 3.2 but not built by default. See the original announcement for how to do so.

Availability

Four release options are now available for 32-bit as well as for 64-bit. 64-bit installations are recommended if you do not need the linux emulation layer.

• An ISO, to be burned to a physical CD or used as an image to install a virtual machine.
  
• A bootable USB disk-key image. (minimum 2G USB stick needed)
  
• A GUI bootable ISO image with a full X environment. DVD disc required.
  
• A GUI bootable USB disk-key image with a full X environment. (minimum 4G USB stick needed)
  
• The GUI images also include a snapshot of our git repos in /usr/src/.git and /usr/pkgsrc/.git which can be incrementally updated after the installation.

The release ISO images should be available on most of the mirrors. If the ISO is not available on a certain mirror, please try another one or download it from the DragonFly master site. Each image is in the "Live CD" format, meaning that it boots into a running and fully functional DragonFly system, which can be used for testing or system recovery tasks as well as installation. Check the hardware page or boot a Live CD to check for compatibility.

The GUI bootable USB image also contains the DragonFly git repo in /usr/src and the pkgsrc git repo in /usr/pkgsrc. The code can be trivially checked out using these repos and can be incrementally updated from master sites, post-install. See below for methods to obtain this code using the other images.

...
Neke stvari koje treba imati na umu prilikom instalacije"
Citat:...
DragonFly 3.2 Special Installation and Upgrade Notes

Disk size warning - GUI disk installs and installations using HAMMER should be to disks over 50G in size. HAMMER history will consume disk space quickly. Either use UFS on smaller disks, or prune your file history carefully.

Virtual PC users - Virtual PC does not supply serial numbers for the virtual disks. The system may need to be manually directed in the boot loader if the disk identifier changes. (Hit ? in the boot loader for a list of available volumes.)

Qemu users - If you see a large number of error messages on the console when booting, you may need to boot DragonFly with ACPI disabled. This can be done in the menu presented at initial boot. If that doesn't help, try placing hw.ioapic_enable=0 in /boot/loader.conf.

Installer Crypt Options - The installer can encrypt the root volume and the swap volume. It will not work properly for other volumes despite any additional check-boxes you might see. Installer and boot-time support works but is still a bit rough around the edges. Performance will be relatively high on multi-core machines.

Objava: http://www.dragonflybsd.org/release32/

Lista mirror-a za preuzimanje: http://www.dragonflybsd.org/mirrors/



DragonFly Release 3.4



Citat:Big-ticket items


Experimental packaging system: dports

John Marino has created a system, DPorts, that uses the FreeBSD ports system to build ports for DragonFly, and uses pkgng to manage the binary packages produced from those ports.

The default packaging system on DragonFly is pkgsrc. To use DPorts, you must remove or disable pkgsrc packages. Pkgsrc and DPorts cannot be used at the same time, or have packages mixed together. See the DPorts Howto page for details on installing and using DPorts. Note: this is the first release with DPorts, and this is still experimental.

The DragonFly snapshots are built using dports. (and also have XFCE for the desktop)

Performance improvements under extreme load

The process of testing poudriere, a tool for mass-producing binary dports packages, exposed stability issues when repeatedly mounting and unmounting many tmpfs systems on large multicore (48) systems. These issues have been fixed. In addition to stability, several changes were made to improve performance in situations with heavy processor and disk usage.

Improvements in poudriere performance, tmpfs performance, and CPU usage (graphs are linked in those message) were graphed by Francois Tigeot and posted on the kernel@dragonflybsd.org mailing list.

New default compiler

The two base compilers have swapped roles. GCC 4.7, introduced as an alternative compiler with Release 3.2, is now the primary compiler used to build DragonFly. GCC 4.4 remains on the system and still has an important role as the primary DPorts compiler. GCC 4.7 brings OpenMP (parallel programming) support to DragonFly via libgomp as well as stack smashing protection via libssp, neither of which was supported by GCC 4.4. The newer compiler also offers improved C++ and Objective-C support, and introduces Link-Time Optimization (LTO) support.

New USB stack

USB4BSD is available this release, though not by default. More USB devices are compatible with DragonFly, and xhci (USB 3.0) users may be able to take full advantage of their newer hardware. Since this is a new feature, it is available in 3.4 but not built by default. See the original announcement for how to do so. This feature was available in DragonFly 3.2 but is still experimental.

Zvanicna objava: http://www.dragonflybsd.org/release34/

Preuzimanje:
Citat:Availability

Two release options are now available for 32-bit as well as for 64-bit. 64-bit installations are recommended if you do not need the Linux emulation layer.

• An ISO, to be burned to a physical CD or used as an image to install a virtual machine.
  
• A bootable USB disk-key image. (minimum 2G USB stick needed)

The release ISO images should be available on most of the mirrors. If the ISO is not available on a certain mirror, please try another one or download it from the DragonFly master site. Each image is in the "Live CD" format, meaning that it boots into a running and fully functional DragonFly system, which can be used for testing or system recovery tasks as well as installation. Check the hardware page or boot a Live CD to check for compatibility.