NetBSD News Beat
— You heard it here —
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2008-08-19
(German language) guide on installing a CF-card and
NetBSD on your EeePC hubertf's
NetBSD blog 2008-08-19
14:35 UTC
Issue 5/2008 of the German FreeX magazine has an article by Ulrich Habel titled "Festspeicher statt Festplatte" ("hard storage instead of hard disk"). It illustrates how to replace your EeePC's 1.8" harddisk with a CF-card adapter, and install NetBSD on it. BTW, FreeX is always looking for (german language) authors, too! AFS is a distributed filesystem which offers a client-server architecture, transparent data migration abilities, scalability, a single namespace, and integrated ancillary subsystems. License: IBM Public License Changes: There are many changes on Windows. On NetBSD, broken sigwait() has been worked around to allow the fileserver to shut down correctly pre NetBSD 5.0. On all platforms, potential corruption of directories during salvage is avoided. 2008-08-18
Bluetooth documentation update for Personal Area
Networking hubertf's
NetBSD blog 2008-08-18
16:07 UTC
The daemon for handing bluetooth PAN that was proposed last week is imported in NetBSD-current now, and will be part of the upcoming NetBSD 5.0 release. Ian Hibbert has also updated the Bluetooth chapter in the NetBSD Guide with examples of a PANU (Personal Area Networking User) client. Ian will also continue to work on NAP (Network Access Protocol) and/or GN (Group ad-hoc Network), but that's some work todo. If anyone wants to help Ian out, feel free to contact him - see his posting for more details on the basic setup. NTFS-3G is a stable read/write NTFS driver. It is available for over 170 Linux distributions and the default read/write NTFS driver for most major ones. It has been ported to many other operating systems like FreeBSD, NetBSD, Solaris, Haiku, and Mac OS X, and to big-endian, 64-bit, and MMU-less computer architectures. License: GNU General Public License (GPL) Changes: This release includes improvements and fixes for reliability, usability, and portability. New features are libtool-2 and Solaris support. 2008-08-16After a few days of offline-experience, here's a short summary of what happens that I haven't seen mentioned widely:
2008-08-15Mathias Schler has an interesting blog posting about the difference of using journaling on file system performance. The test he did was extracting NetBSD 4.0 sources.
!NetBSD: Books for sale (german language, no computer
stuff) hubertf's
NetBSD blog 2008-08-15
14:13 UTC
Spam: I've got a bunch of german-language books that I'd like to get rid of. Novels, some comics/mangas, no computer-stuff. For more information, click here. 2008-08-13I got some feedback about my fink blaming inside
the blastwave article. Fink is a software project on
Sourceforge (Link)
which ported the debian apt mechanism to MacOS X in
order to provide an easy way to install packages.
Christoph Pfisterer was the main maintainer in 2001
who did alot of the porting work and who maintained
alot of packages. When he stepped down many of the
Fink packages became unmaintained for a certain
period. 2008-08-11Blastwave is a
project which builds Solaris comaptible pkgs out of
GNU software for Solaris 8 - 11. I wasn't that sure
about project structures, security and so on when I
installed their packages. I looked for a better
project and found NetBSD pkgsrc that time. We run
NetBSD pkgsrc on Solaris 8/Solaris 9 and Linux at my
company and we are quite happy with it - there is no
need for such projects as blastwave. Hoever, there is
something interesting - when a single person has
founded a project and is in power of everything, this
project is likely about to explode one day. Do you
remember fink? The package manager for MacOS X? For
every of my readers, I suggest to switch to NetBSD
pkgsrc, for your freedom and your security and
software needs. Maybe I should set up a small article
how to get started on Solaris. Links about the blastwave troublesSome of you already asked for it, get the sources
for the accu data collecting script here on this
page. If you are just want to use it or if you would
like to have a short look into the sourcecode, feel
free to download it here. 2008-08-09I own a small IBM Thinkpad X40 and I am quite
happy with it, it's close to 4 yrs old now and the
stamina of the accumulator failed over the time down
to about 2.5 hours (from about 5-6 hours). This is
still a fair time for mobile usage, however I decided
to buy a new accu these days. It's about 179 Euro
which is quite expensive.
The red line shows the current charge, right now the charge proccess is still running, please note how long it takes for a full charge and how slow the proccess is when it climbs up to 100%. Right now I won't post the script here, there is some cleanup work to be done, however I think I might finish it by tomorrow and I will post it here. There is still some documentation missing. The script is monitoring my laptop for the next 3 years, I wonder what the new accu will look alike - what about the curves, etc. 2008-08-04Well, just to give you some numbers and a quick
idea how it will look like: rhaen@arkanum.pkgbox.org:Soekris $ time -p perl -MDBI -e 'print "$DBI::VERSION\n"' 1.601 real 1.56 user 1.38 sys 0.19That's just 1.5 seconds for loading a Perl module to detect it's version. I thought the Soekris 4801 might be able to run a small blog with MovableType - but without a chance. It's perfect to run a small webserver which only serves static html pages but it's horrible slow if you decide to run dynamic cgis. However I haven't tested it with PHP but the results might be similar. In the next days I will work on a small workshop how to setup a blog on a Soekris running blogtools and such. Stay tuned :) Oh, and all you need is NetBSD, that's nice, eh? 2008-07-31A wish came true: NetBSD finally has a journaling file system. Simon Burge added support for WAPBL, Write Ahead Physical Block Logging file system journaling, to NetBSD-current’s main branch today. The main purpose of a journaling file system is to avoid a time consuming file system checks after a power failure, system crash or similar problem. But it can also help to improve performance considerably depending on the design. As I was curious about WAPBL’s performance impact I ran my usual benchmark (extracting the NetBSD 4.0 source tar archives). And the result is very encouraging: FFS required 15:19 minutes to finish the benchmark without logging and only 3:24 minutes to finish it with logging. It seems that WAPBL provides similar speed improvements as soft dependencies and keeps your file system safe at the same time. A big thank you to Wasabi Systems for donating the code and to Simon Burge and all the other developers for integrating WAPBL into NetBSD! 2008-07-25The last time I tested software RAID 1 under NetBSD I wasn’t really satisfied with the performance. Especially file system operations were much slower than I expected. Resulting from that my current home server uses an Intel SRCS14L RAID Controller instead of software RAID. I had considered also buying a new RAID controller for my future home server. Areca’s ARC-1210 looked like the best candidate. But the ARC-1210 is not exactly cheap (as expected) and unfortunately has a fan. As reducing the noise level was one of the main goals to buy new server hardware I was put off. After some consideration I decided to give RAIDframe another try. Encouraged by David Brownlee’s benchmark results I ran a similar benchmark on my hardware. To do that I wrote a shell script which consecutively creates RAID 1 volumes and FFSv1 file systems with all the combinations of parameters listed in the table below. Each of the file systems is mounted (not using soft dependences) and benchmarked by extracting the tar archives with the NetBSD 4.0 sources to it. The time required to complete each of the benchmark runs is recorded afterwards. Below are the averages of the results of two runs of my test script, smaller time values imply better performance of course.
Unsurprisingly I’m now using a RAID 1 volume with 128 sectors per stripe unit and file systems with a block size of 16KB and a fragment size of 2KB. I’m not sure whether these values always result in the best possible performance but they seem to work for David Brownlee and me. Feeds
|
Hosted by Global Wire Oy
|