Here are the talks on NetBSD and/or from NetBSD developers:

• Yvan Vanhullebus: IPSec tools: past, present and future (PDF, mp3)
• Martin Schuette: Improved NetBSD Syslogd (PDF, mp3)
• Michael Dexter: Zen and the Art of Multiplicity Maintenance: An applied survey of BSD-licensed multiplicity strategies from chroot to mult (PDF, mp3)
• Hauke Fath: Managing BSD desktop clients - Fencing in the herd (PDF, mp3)
• Joerg Sonnenberger: Sleeping beauty - NetBSD on Modern Laptops (PDF, mp3)
• Antti Kantee: Converting kernel file systems to services (PDF, mp3)

• Christoph Badura: Gaols - Implementing Jails Under the kauth Frameworki (paper)
• Yuji IMAI, Takahiro KUROSAWA, Koichi SUZUKI, Eiichi MURAMOTO, Katsuomi HAMAJIMA, Hajimu UMEMOTO, and Nobuo KAWAGUTI: BSD implementations of XCAST6 (paper)
• Antti Kantee: Send and Receive of File System Protocols: Userspace Approach With puffs (paper)
• Kristaps Džonsons: Logical Resource Isolation in the NetBSD Kernel (paper)
• Alistair Crooks: A Portable iSCSI Initiator (paper)
• Jörg Sonnenberger, Jared D. McNeill: Sleeping Beauty---NetBSD on Modern Laptops(slides, paper)

• Following Wikipedia, Portability is ``the general characteristic of being readily transportable from one location to another'', and it's also a major goal of NetBSD. Things start to get interesting when looking into details, e.g. Wikipedia also states that ``Software is portable when the cost of porting it to a new platform is less than the cost of writing it from scratch. The lower the cost of porting software, relative to its implementation cost, the more portable it is said to be.'' So there's some room for interpretation when defining what is portable and what is not, and to what extent.

  Besides my essay on What makes an operating system portable, there was a posting to the netbsd-advocacy mailing-list that goes into a few details on NetBSD's current state of portability. The posting lists a number of reasons why the author considers NetBSD to be portable, including the low effort to start new projects, central maintenance in one source tree, and the efforts from machine-independent changes to all ports.

  After reading about people doing research on how to assess "security" of operating systems by counting number of exploits and how quick they are patched, I wonder if there are some metrics out there to also put "portability" into numbers.

• I've mentioned the mult project some time ago. In one of their latest recordings, there's also a interview with its creator, Kristaps Dzonsons, on it on BSDtalk, available in mp3 and ogg formats. Thanks to Mark Weinem for the hint!

• Following some discussion on NetBSD on the Freescale i.mx31 board, Matt Thomas has posted a dmesg output. Mentioned here for all the fans of dmesg pr0n. :-)

• To give new users hints on how to use NetBSD, Jeremy C. Reed has started a netbsd-tips fortune database. It's part of NetBSD-current and can be run from .login/.profile by running "fortune netbsd-tips". There's also a wiki page that allows easy submitting of new entries. Feel free to contribute your special NetBSD gems!

• NetBSD's handling of harddisks and file systems is pretty static right now - while one can add additional disks to a system, and even span them using RAIDframe and ccd(4), extending the filesystem on top of it is a problem. This is being mitigated by Juan Romero Pardines' port of growfs(8): ``I've just adapted growfs(8) from OpenBSD (they adapted the FreeBSD code), which is able to grow FFSv1 and FFSv2 filesystems.

  I tested growing a partition in FFSv1 and FFSv2 from 1GB to 4GB and the process was smooth (and fast); after this I ran 'fsck_ffs -yf /fs' and it found one error that was fixed correctly.'' For more information, including where to get the code and what to test, see Juan's posting.

  There were a few attempts to get logical volume management (LVM) onto NetBSD, which were not successful so far. This may change in the future, and when flexible handling of storage volumes, with growfs(8) will be useful to manage FFS/UFS file system sitting on top of them.

• Andrew Doran has continued his hacking to improve NetBSD on SMP machines, and he has posted about making the socket code and the Unix domain communication running fine-grained, and about speeding up device detection during booting by running device configuration in a number of concurrent kernel threads. If someone has actual numbers on boot time before/after that patch, please post them to the list!

• When needing sources for some Open Source package, I've used "make extract NO_DEPENDS=1" with pkgsrc in the past. It seems that was removed without further notice, and Obata Akio was kind enough to point out that this can be done now by using SKIP_DEPENDS=yes. Mmm, interface stability...

• Last but not least a note from the "products based on NetBSD" department: Saitoh Masanobu from IIJ, Japan, has notified us that the SEIL/X series that IIJ unveils at AsiaBSDCon 2008 is based on NetBSD. There's a brochure on SEIL/X that mentions a long list of features supported by the machine, including all state of chw art in routing, bridging, VPN, firewalling, quality of service and more. This is made possible by the "SEIL Engine", a software architecture that's based on NetBSD that allows porting the application stack to a number of hardware platforms easily, while offering flexibility to add support for custom hardware and software modules:

  

  For more information on the SEIL Engine, see IIJ/SEIL's homepage (Japanese). and PDF brochude (English).

  Also, for some impression of the SEIL/X machine on the geek level, there's dmesg output of the machine available.

For more information, see the project's website, which offers a gentle introduction to mult, documentation and downloads.

[Tags: mult]