• Masanobu SAITOH talked about Developing CPE Routers based on NetBSD (P6B, PDF-Slides)

• Masanobu SAITOH also talked about Implementation and Modification for CPE Routers: Filter Rule Scan Optimization, IPsec Interface and Ethernet Switch (P7B, PDF-Slides)

• Mindaugas Rasiukevicius talked about NPF's progress and perspective (P2B, PDF-Slides)

1. The port to the NETWALKER (Cortex-A8) platform works as confirmed by Jun Ebihara, including instructions on how to set things up and dmesg output.

2. Ryota Ozaki is working on porting DTrace to ARM

3. Matt Thomas is making the ARM port ready to use multiple CPUs, see his posting, which shows a list of processes and their associated CPU.
   
   [Tags: arm, dmesg, dtrace, netwalker, smp]
   
   
   

• NetBSD Security Advisory 2014-001: Stack buffer overflow in libXfont:

  ``A stack buffer overflow in parsing of BDF font files in libXfont was found that can easily be used to crash X programs using libXfont, and likely could be exploited to run code with the privileges of the X program (most nostably, the X server, commonly running as root).

  This vulnerability has been assigned CVE-2013-6462.''

• NetBSD Security Advisory 2014-002: ntpd used as DDoS amplifier:

  ``An administrative query function is getting used by attackers to use ntp servers as traffic amplifiers. The new version no longer offers this query option.''

The interview starts with NetBSD's history and its relation to today's Unix world and how Amitai got involved with NetBSD and pkgsrc in the first case. He outlines the differences and interrelation with NetBSD as an operating system project, and with pkgsrc as a cross-platform package management project, then tells on what pkgsrc does, is and is not, and for whom pkgsrc offers a good solution. The interview goes into automation, bulk builds and also mentions my pkgsrcCon Ansible talk at one point - kudos! :) Illuminating things from a craftsman's point of view, the look goes back to NetBSD and its advantages to serve as a modern Unix platform for the business, its support of many platforms and especially today virtualization, and also NetBSD's concepts of cross-compiling and "cross-kernel" approaches of RUMP, and the importance of automated kernel tests not crashing an actual machine.

For more information, see www.NetBSD.org and www.pkgsrc.org. :-)

[Tags: schmonz]

• Embedded NetBSD on iMX233/OLinuXino
• Raspberry Pi USB HC driver change - DMA support added
• Quick bootstrap of NetBSD on Raspberry Pi and Cobalt machines
• Mercedes Benz powered by NetBSD?
• G4U Opinion Time: kernel with embedded RAMdisk vs. miniroot?

The article outlines the history of the various BSDs and tells about NetBSD's source organization and build process. It then introduces the target hardware and how NetBSD abstracts the various busses and drivers that are already there, and the few bits that needed adjusting.

``Conclusion: High portability, sufficient ease of use, as well as the necessary software packet and an open source code packets and open source make NetBSD a very attractive operating system for use in embedded systems. As seen in the example, it takes quite superficial knowledge of the system architecture and minimum change in the code to run NetBSD on the IP-Plug. At the same time, the functionality and performance of the built operating system is not inferior to that of Linux, which is used by default.''

[Tags: arm, Articles, ipplug, kirkwood, marvell]

`` I set up a dialup gateway for a company with NetBSD 1.3 in 1998 on a compaq pentium 90 desktop with 32MiB of RAM. I got a call last year (!) from the owner saying it stopped working suddenly. Pulled the disk on it and plugged it into an IDE/USB adapter and looked at the syslog as I had no ps2 keyboard and it didn't have USB.

Suspected hardware failure at that age.

Max uptime: 8 years, 122 days!''

The article goes on about what the machine was used for, and a bunch of lessons learned. Have a look and learn!

[Tags: uptime]

I'd like to push out version 2.6 within the next few weeks. Please test and let me know if there are any showstoppers!

Full list of news in g4u 2.6beta1:

• Make this build with NetBSD-current sources as of 2013-10-20
• Move back from a ramdisk that's loaded from a separate file back to a ramdisk that's part of the kernel image. This allows easier netbooting for those people who want it - added back by popular demand :-)
• Added more kernel buffer space, to hold all kernel messages for dmesg, even on machines with large ACPI tables (Hello VMware Fusion!)
• New drivers:
  • LSILogic 9x9 and 53c1030 (Fusion-MPT) PCI SCSI
  • LSI Logic Fusion-MPT II PCI SCSI
  • Atheros AR9k (802.11a/g/n) PCI Wireless
  • Marvell PCI Libertas Wireless
  • Atheros AR9k (802.11a/g/n) PC-Card Wireless
  • Broadcom BCM43xx PC-Card Wireless
  • Atheros AR9002U USB Wireless
  • Ralink Technology RT2500USB 802.11a/b/g USB Wireless
  • Ralink Technology RT(2[78]|30)00 802.11a/b/g/n USB Wireless
  • Realtek RTL8187/RTL8187B 802.11b/g USB Wireless
  • Realtek RTL8188CU/RTL8192CU 802.11b/g/n USB Wireless
  • Intel Atom E6xx PCI-LPC

• The g4u 2.6beta1 ISO CD image (zipped/uncompressed)
• The g4u 2.6beta1 source
• The g4u 2.6beta1 floppy images (zipped/ uncompressed floppy one, floppy two and floppy three)
• Some md5 checksums:

  MD5 (g4u-2.6beta1-1.fs) = 264d5b27f208f1053777774d0c2b87a7
  MD5 (g4u-2.6beta1-2.fs) = 533b37fbeeb2d537928de61b25eb2ade
  MD5 (g4u-2.6beta1-3.fs) = 5abe1327326fcdac18bf4d68566f3e9b
  MD5 (g4u-2.6beta1.iso) = 37596efb42c014eb049e0027db059bd9
  MD5 (g4u-2.6beta1.tgz) = acd5907a7fb2cc8fbd4645a1b9db5272
  MD5 (g4u-2.6beta1.fs.zip) = 9b8da62fac57dcd38a4e3376189a087d
  MD5 (g4u-2.6beta1.iso.zip) = 44cb8d01407b17f9d9839740b5a0d2d9
  

Looking forward for your opinions!''

[Tags: g4u]

This includes a number of BSD variants - original 4-clause as well as the 2- and 3-clause versions as well as company specific BSD licenses by car-supplier Continental, Acme Labs and Google. No explicit mention of NetBSD's license, but a bunch of NetBSD developers' names and mail addresses can be found. There is also an overview that the BSD license is used in about all models from A-Class over S-Class to SLK, and which also indicates that the new (2013+) S-Class includes much more BSD licensed software than all the other models. Which is not much of a surprise, as it's the most recent and also most technically advanced model (as far as I can tell).

No details are included as to what software components are under the respective licenses. Anyone got details? Please share!

[Tags: daimer, mercedesbenz]