hubertf's NetBSD bloghttp://www.feyrer.de/NetBSD/blog.html/
Blog about the NetBSD open source operating systemenhttp://blogs.law.harvard.edu/tech/rssblosxom/2.1.2No more Google adshttp://www.feyrer.de/NetBSD/blog.html/nb_20180119_2344.html
Fri, 19 Jan 2018 23:47:00 GMT
<table>
<tr>
<td>
I've had Google Adsense advertising for quite a while on my blog,
the <a href="http://www.feyrer.de/g4u/">g4u homepage</a> and various other pages.
In the start a little bit of money came in.
This has all dried up long since, and in light of
privacy regulations like the EU GDPR I've decided to
not give away my users' data to Google any longer.
So, there it is - my blog and other pages are free for your use now,
and you are no longer the product being sold. Enjoy! :-)
<p>
(If you find any remaining advertisement, drop me a line!)
</td>
<td> <img align="right" width="100" src="https://nikosskordilis.files.wordpress.com/2013/06/a80e0-no-adsense1.png" /></td>
</table>
NetBSD 7.1.1 releasedhttp://www.feyrer.de/NetBSD/blog.html/nb_20180104_0116.html
Thu, 04 Jan 2018 01:21:00 GMT
On December 22nd, NetBSD 7.1.1 was released as premature
christmas present, see
<a href="http://www.netbsd.org/releases/formal-7/NetBSD-7.1.1.html">the release annoucement</a>.
<p>
NetBSD 7.1.1 is the first update with security and critical
fixes for the NetBSD 7.1 branch. Those include a number of
fixes for security advisories, kernel and userland.
New year, new security advisories!http://www.feyrer.de/NetBSD/blog.html/nb_20180104_0111.html
Thu, 04 Jan 2018 01:16:00 GMT
So things have become a bit silent here, which is due
to reallife - my apologies. Still, I'd like to wish
everyone following this here a Happy New Year 2018!
And with this, a few new security advisories have
been published:
<ul>
<li> <a href="http://mail-index.netbsd.org/netbsd-announce/2018/01/02/msg000274.html">NetBSD Security Advisory 2018-001: Several vulnerabilities in context handling</a> - this affects amd64, i386 and sparc64
<li> <a href="http://mail-index.netbsd.org/netbsd-announce/2018/01/02/msg000275.html">NetBSD Security Advisory 2018-002: Local DoS in virecover</a>
</ul>
34C3 talk: Are all BSDs created equally?http://www.feyrer.de/NetBSD/blog.html/nb_20180104_0105.html
Thu, 04 Jan 2018 01:08:00 GMT
I haven't seen this mentioned on the NetBSD mailing lists,
and this may be of interest to some -
there was a talk about security bugs in the various BSDs at the 34th Chaos
Communication Congress:
<p>
<ul>
<li> <a href="https://www.youtube.com/watch?v=rRg2vuwF1hY">Video: https://www.youtube.com/watch?v=rRg2vuwF1hY</a>
<li> <a href="https://events.ccc.de/congress/2017/Fahrplan/events/8968.html">Talk: https://events.ccc.de/congress/2017/Fahrplan/events/8968.html</a>
</ul>
In summary, many reasons for bugs are shown in many areas of the kernel
(system calls, file systems, network stack, compat layer, ...), and what has
happened after they were made known to the projects.
<p>
As a hint, NetBSD still has a number of Security Advisories to publish, it
seems. Anyone wants to help out the security team? :-)
g4u 2.6 releasedhttp://www.feyrer.de/NetBSD/blog.html/nb_20170608_1558.html
Thu, 08 Jun 2017 16:19:00 GMT
After a five-year period for beta-testing and updating,
I have finally released g4u 2.6. With its origins in 1999,
I'd like to say: Happy 18th Birthday, g4u!
<p>
<b>About g4u:</b>
g4u ("ghosting for unix") is a NetBSD-based bootfloppy/CD-ROM that allows easy cloning of PC harddisks to deploy a common setup on a number of PCs using FTP. The floppy/CD offers two functions. The first is to upload the compressed image of a local harddisk to a FTP server, the other is to restore that image via FTP, uncompress it and write it back to disk. Network configuration is fetched via DHCP. As the harddisk is processed as an image, any filesystem and operating system can be deployed using g4u. Easy cloning of local disks as well as partitions is also supported.
<p>
<b>The past:</b>
When I started g4u, I had the task to install a number
of lab machines with a dual-boot of Windows NT and NetBSD.
The hype was about Microsoft's "Zero Administration Kit" (ZAK)
then, but that did barely work for the Windows part - file transfers were
slow, depended on the clients' hardware a lot (requiring fiddling with MS
DOS network driver disks), and on the ZAK server the files for
installing happened do disappear for no good reason every now and then.
Not working well, and leaving out NetBSD (and everything elase),
I created g4u. This gave me the (relative) pain of getting
things working once, but with the option to easily add network
drivers as they appeared in NetBSD (and oh they did!), plus allowed
me to install any operating system.
<p>
<b>The present:</b>
We've used g4u successfully in our labs then, booting from CDROM.
I also got many donations from public and private instituations
plus comanies from many sectors, indicating that g4u does make a
difference.
<p>
In the mean time, the world has changed, and CDROMs aren't used
that much any more. Network boot and USB sticks are today's devices
of choice, cloning of a full disk without knowing its structure
has both advantages but also disadvantages, and g4u's user interface
is still command-line based with not much space for automation.
For storage, FTP servers are nice and fast, but alternatives
like SSH/SFTP, NFS, iSCSI and SMB for remote storage plus local storage
(back to fun with filesystems, anyone? avoiding this was why g4u
was created in the first place!) should be considered these days.
Further aspects include integrity (checksums), confidentiality
(encryption).
This leaves a number of open points to address either by
future releases, or by other products.
<p>
<b>The future:</b>
At this point, my time budget for g4u is very limited.
I welcome people to contribute to g4u - g4u is Open Source
for a reason. Feel free to get back to me for any changes
that you want to contribute!
<p>
<b>The changes:</b>
Major changes in g4u 2.6 include:
<ul>
<li> Make this build with NetBSD-current sources as of 2017-04-17 (shortly before netbsd-8 release branch), binaries were cross-compiled from Mac OS X 10.10
<li> Many new drivers, bugfixes and improvements from NetBSD-current (see beta1 and beta2 announcements)
<li> Go back to keeping the disk image inside the kernel as ramdisk, do not load it as separate module. Less error prone, and allows to boot the g4u (NetBSD) kernel from a single file e.g. via PXE (Testing and documentation updates welcome!)
<li> Actually DO provide the g4u (NetBSD) kernel with the embedded g4u disk image from now on, as separate file, g4u-kernel.gz
<li> In addition to MD5, add SHA512 checksums
</ul>
<b>The software:</b>
Please see
<a href="http://www.feyrer.de/g4u/#reqs">the g4u homepage's download section</a>
on how to get and use g4u.
<p>
Enjoy!
Native Command Queuing - merging and testinghttp://www.feyrer.de/NetBSD/blog.html/nb_20170608_1404.html
Thu, 08 Jun 2017 14:13:00 GMT
<a href="https://en.wikipedia.org/wiki/Native_Command_Queuing"><img src="https://upload.wikimedia.org/wikipedia/commons/thumb/4/4a/NCQ.svg/300px-NCQ.svg.png" align="right" width="200" /></a>
Jaromir Dolecek has worked on NCQ and is looking for
testers in context of merging the development branch
into NetBSD-current.
<p>
What is NCQ? According to
<a href="https://en.wikipedia.org/wiki/Native_Command_Queuing">Wikipedia</a>,
``<i>Native Command Queuing (NCQ) is an extension of the Serial ATA protocol allowing hard disk drives to internally optimize the order in which received read and write commands are executed. This can reduce the amount of unnecessary drive head movement, resulting in increased performance (and slightly decreased wear of the drive) for workloads where multiple simultaneous read/write requests are outstanding, most often occurring in server-type applications.</i>''
<p>
Jaromir
<a href="http://mail-index.netbsd.org/tech-kern/2017/06/08/msg021960.html">writes to tech-kern</a>:
``<i>I plan to merge the branch to HEAD very soon, likely over the weekend. Eventual further fixes will be done on HEAD already, including mvsata(4) restabilization, and potential switch of siisata(4) to support NCQ.
<p>
The plan is to get this pulled up to netbsd-8 branch soon also, so that it will be part of 8.0.
<p>
Status:
<ul>
<li> ahci(4) fully working with NCQ (confirmed with qemu, and real hw)
<li> piixide(4) continues working (no NCQ support of course) (confirmed in qemu)
<li> siisata(4) continues working (without NCQ still) (confirmed with real hw)
<li> mvsata(4) not yet confirmed working after changes, mainly due the DMA not really working on Marvell 88SX6042 which I have available - I have same issue as kern/52126
<li> other ide/sata drivers received mechanical changes, should continue working as before</i>''
</ul>
Testing and feedback of success or suggestions for improvemenbt
are always welcome - please send your report!
Support for Controller Area Networks (CAN) in NetBSDhttp://www.feyrer.de/NetBSD/blog.html/nb_20170521_0113.html
Sun, 21 May 2017 01:30:00 GMT
Manuel Bouyer has worked on NetBSD CAN-support, and now he
<a href="http://mail-index.netbsd.org/tech-net/2017/05/18/msg006342.html">writes</a>:
``<i>I'd like to merge the bouyer-socketcan branch to HEAD in the next few
days (hopefully early next week, or maybe sunday), unless someone objects
to the idea of a socketcan implementation in NetBSD.
<p>
CAN stands for <a href="https://en.wikipedia.org/wiki/CAN_bus">Controller Area Network</a>, a broadcast network used
in automation and automotive fields. For example, the NMEA2000 standard
developped for marine devices uses a CAN network as the link layer.
<p>
This is an implementation of the linux socketcan API:
<a href="https://www.kernel.org/doc/Documentation/networking/can.txt">https://www.kernel.org/doc/Documentation/networking/can.txt</a>
you can also see can(4) in the branch.
<p>
This adds a new socket family (AF_CAN) and protocol (PF_CAN),
as well as the canconfig(8) utility, used to set timing parameter of
CAN hardware. The branch also includes a driver for the CAN controller
found in the allwinner A20 SoC (I tested it with an Olimex lime2 board,
connected with PIC18-based CAN devices).
<p>
There is also the canloop(4) pseudo-device, which allows to use
the socketcan API without CAN hardware.
<p>
At this time the CANFD part of the linux socketcan API is not implemented.
Error frames are not implemented either. But I could get the cansend and
canreceive utilities from the canutils package to build and run with minimal
changes. tcpdump(8) can also be used to record frames, which can be
decoded with etherreal.
<p>
A review of the code in src/sys/netcan/ is welcome, especially for possible
locking issues.</i>''
<p>
What CAN devices would you address with NetBSD? Drop me mail!
Announcing NetBSD and the Google Summer of Code Projects 2017http://www.feyrer.de/NetBSD/blog.html/nb_20170505_2121.html
Fri, 05 May 2017 21:34:00 GMT
<img src="https://developers.google.com/open-source/gsoc/resources/downloads/GSoC-icon.svg" width="80" align="right" />
The NetBSD Project <a href="https://blog.netbsd.org/tnf/entry/announcing_netbsd_and_the_google">posts</a> that
we are very happy to announce that the selection process in this year's
Summer of Code with its bargaining of slots and what student gets assigned
to which project is over. As a result, the following students will take on
their projects:
<p>
<ul>
<li> Leonardo Taccari will work add multi-packages support to pkgsrc.
<li> Maya Rashish will work on the LFS cleanup.
<li> Utkarsh Anand will make Anita support multiple virtual machine systems
and more architectures within them to improve testing coverage.
</ul>
What follows now is a community bonding period until May 30th, followed by a
coding period over the summer (it's Summer of Code, after all :-)
until August 21st, evaluations, code submission and an announcement of the
results on September 6th 2017.
<p>
Good luck to all our students and their mentors - we look forward to your
work results, and welcome you to The NetBSD Project!
Adventures in Time, part 1: Interfacing an Oven Controlled Crystal Oscillator to a Computer Running NetBSDhttp://www.feyrer.de/NetBSD/blog.html/nb_20170502_2103.html
Wed, 03 May 2017 20:16:00 GMT
<img align="right" src="https://4.bp.blogspot.com/-BW8UAcaZQvc/WPuwTmUGEoI/AAAAAAAAANA/yH06g5_qfMYL35tWzZ2qe62RY2vw7LntQCLcB/s200/DSC_6047_00002.jpg" />
I've stumbled across this article via
<a href="https://www.dragonflydigest.com">the Dragonfly BSD Digest</a>:
Tobias 'tnn' Nygren wrote about his aventurs in time,
with part one on
<a href="http://contraptnns.blogspot.de/2017/04/adventures-in-time-part-1-interfacing.html">Interfacing an Oven Controlled Crystal Oscillator to a Computer Running NetBSD</a>.
<p>
This first article in a blog series starts by
describing regular and oven ontrolled crystal oscillators,
then goes on in describing the hardware setup and how it is
connected to a computer. In this case, a Banana Pi running
NetBSD/evbarm is used which (of course) also has its own
clock. Oscilloscope measurements show differences in
quality of signals and why an adapter is needed to adjust
the system's clock frequency (including changes to the
NetBSD kernel).
<p>
In the next post Tobias will describe how to calibrate the clock with NTP.
Stay tuned and
<a href="http://contraptnns.blogspot.de/">have an eye on his blog</a>!
g4u 2.6beta2 has been released - Happy 18th Birthday, g4u!http://www.feyrer.de/NetBSD/blog.html/nb_20170421_0150.html
Fri, 21 Apr 2017 01:51:00 GMT
Just right in time for its 18th birthday, I have released
the 2nd beta version for g4u 2.6 (2.6beta2).
It took some time to get to this point, and I want to move
to 2.6 soon - please take your time to test and get back to me
soon, as I want to push out g4u version 2.6 in june 2017.
<p>
g4u ("ghosting for unix") is a NetBSD-based bootfloppy/CD-ROM that allows easy cloning of PC harddisks to deploy a common setup on a number of PCs using FTP. The floppy/CD offers two functions. The first is to upload the compressed image of a local harddisk to a FTP server, the other is to restore that image via FTP, uncompress it and write it back to disk. Network configuration is fetched via DHCP. As the harddisk is processed as an image, any filesystem and operating system can be deployed using g4u. Easy cloning of local disks as well as partitions is also supported.
<p>
For more information, see
<a href="http://www.feyrer.de/g4u/">http://www.feyrer.de/g4u/</a>.
<p>
Changes in 2.6beta2 include:
<ul>
<li> Make this build with NetBSD-current sources as of 2017-04-17,
binaries were cross-compiled from Mac OS X 10.10
<li> Go back to keeping the disk image inside the kernel as ramdisk,
do not load it as separate module. Less error prone, and allows
to boot the g4u (NetBSD) kernel from a single file e.g. via PXE
(Testing and documentation updates welcome!)
<li> Actually DO provide the g4u (NetBSD) kernel with the embedded g4u disk
image from now on, as separate file, g4u-kernel.gz
<li> Put all object files into one object directory. This may need more cleanup
in the future. Feedback from people building g4u welcome!
<li> Disable verbose device messages on Microchannel (MCA) machines
<li> New drivers:
<ul>
<li> Toshiba Dynabook hotkeys
<li> Intel S1200,C2000 (non-pch) SMBus storage controller
<li> Non-Volatile Memory Express (NVMe) storage controllers and devices
<li> Intel Wireless WiFi Link 7xxx PCI network
<li> Intel 8259x 10 gigabit PCI network
<li> Realtek 8188CE/8192CE 802.11b/g/n PCI network
<li> VMware VMXNET3
<li> Marvell Libertas PCMCIA network
<li> ASIX AX88178a/AX88179 based USB network adapters
<li> Realtek RTS5209/RTS5229 Card Reader
</ul>
<li> Happy 18th Birthday, g4u!
</ul>
Download links:
<ul>
<li> The g4u 2.6beta2 floppy images (<a href="g4u-2.6beta2.fs.zip">zipped</a>/
uncompressed
<a href="g4u-2.6beta2-1.fs">floppy one</a>,
<a href="g4u-2.6beta2-2.fs">floppy two</a>,
<a href="g4u-2.6beta2-3.fs">floppy three</a>, and
<a href="g4u-2.6beta2-4.fs">floppy four</a>)
<li> The g4u 2.6beta2 ISO CD image (<a href="g4u-2.6beta2.iso.zip">zipped</a>/<a href="g4u-2.6beta2.iso">uncompressed</a>)
<li> The <a href="g4u-kernel-2.6beta2.gz">g4u/NetBSD kernel</a> for PXE boot (gzipped)
<li> The <a href="g4u-2.6beta2.tgz">g4u 2.6beta2 source code</a>
<li> Some md5 checksums:
<pre>
MD5 (g4u-2.6beta2-1.fs) = 8214c1ded55e78aed2f34d3e318dc75d
MD5 (g4u-2.6beta2-2.fs) = 8b55f3fe6a4806c9a65a3d176463e1bc
MD5 (g4u-2.6beta2-3.fs) = 0f9629353ddd470d17c5b4fd4ec7fd8e
MD5 (g4u-2.6beta2-4.fs) = c25a955e5d876d64943fd03f957ed4c9
MD5 (g4u-2.6beta2.iso) = acabb0fb73d4a2f9062fb070b4ddd825
MD5 (g4u-2.6beta2.tgz) = f8387d5bf146f98dda040dfcc1c53e44
MD5 (g4u-2.6beta2.fs.zip) = 8ef324c71ae7b000708e69019e55ef4e
MD5 (g4u-2.6beta2.iso.zip) = 1f4bd37784405350ee3e8e6c75a6b6b6
</pre>
</ul>