|
[20091014]
|
Catching up: Webfwlog, git, vnd and sparse disk images, acpismbus
Here are two news items from the past few days:
-
Web-based firewall log reporting and analysis tool Webfwlog 0.94 released:
``Webfwlog is a flexible web-based firewall log analyzer and reporting tool. It supports standard system logs for linux, FreeBSD, OpenBSD, NetBSD, Solaris, Irix, OS X, etc. as well as Windows XP. Supported log file formats are netfilter, ipfilter, ipfw, ipchains and Windows XP. [...]
With Webfwlog you can design reports to use on your logged data in whatever configuration you desire. Included are example reports as a starting point. You can sort a report with a single click, "drill-down" on the reports all the way to the packet level, and save your reports for later use. You can also create a link directly to any saved report.''
See the webfwlog homepage
for more information.
- Git copies of cvs modules available -
spz@ writes that ``htdocs, othersrc, pkgsrc, src and xsrc are now available as
(bare) git repository copies at
http://ftp.netbsd.org/pub/NetBSD/misc/repositories/git.
These repositories are currently updated every 30 minutes.
They are not authoritative and are not meant to replace cvs,
but if you want to track your development that is not yet fit
for committing into cvs head or sending in as a PR, and want to
use git for that, they may serve as a convenient starting point
or reference.''
- Support for writing file systems on sparse disk images -
File system hacker Antti Kantee writes:
``Yesterday I wanted to write to a file system which was on a sparse
disk image. Normally I would have just used a rump mount, but since the
file system was not at offset = 0 in the file, this failed. vnd wasn't
helpful either: it allowed me to mount the image and then I got weird
errors when writing.
I just finished adding disklabel support to the various rump_fs utilities.
Due to them using the option parsing code of the real mount_fs utilities,
I decided to signal the label number with a magic parameter at the end
of the device (yes, this really simplifies things currently).
Let's assume you're looking at wd0.img. Here's how it works:
=== SNIP ===
golem> disklabel wd0.img
[...]
16 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 719712 63 4.2BSD 1024 8192 0 # (Cyl. 0*- 714*)
b: 66657 719775 swap # (Cyl. 714*- 780*)
c: 786369 63 unused 0 0 # (Cyl. 0*- 780*)
d: 786432 0 unused 0 0 # (Cyl. 0 - 780*)
golem> rump_ffs wd0.img%PART:a% /puffs
rump_ffs: "wd0.img" is a non-resolved or relative path.
rump_ffs: using "/usr/home/pooka/wd0.img" instead.
golem> df /puffs
Filesystem 1K-blocks Used Avail %Cap Mounted on
/usr/home/pooka/wd0.img%PART:a% 338471 256211 65337 79% /puffs
=== SNIP ===
So you specify the partition number as %PART:n%, where is n is obviously
the partition number. Other than that, things work as usual. No vnconfig
etc. necessary. ''
- New ACPI driver: acpismbus(4) - call for testers -
Paul Goyette writes that
``At the request of some folks off-list, I have created a driver for ACPI's
SMBus Control Method Interface. Basically, this is an acpi-based wrapper to
provide device-independant access to i2c/SMBus controllers.
(See spec at http://smbus.org/specs/smbus_cmi10.pdf for further info.)
To see if your system can use this driver, check the output of acpidump for
the existence of a Device(SMB0). If you have an SMB device, I'd appreciate
it if you could help test this driver!''
Continue with Paul's mail to learn on how to test the
driver, and what limitations there are currently.
[Tags: acpi, git, puffs, rump, smbus, webfwlog]
|
|
