least minimal comments to all patches and tidy up some (but by no
means all) pkglint.
I have no idea if this works. It spews warnings about "packed", which
lead me to suspect it may not run correctly, but I don't have the
facilities to test it. It does, however, now build ok on LP64 and if
someone can test it may be reasonable to remove the restriction on that.
- use the correct way to get the size of a disk device or partition (from
haad@NetBSD.org)
- if given a block device, use the character device instead (the block device
is already in use by the backend driver).
With this I could succeffully boot a HVMPV FreeBSD kernel using a phy:
virtual disk.
bup is a program that backs things up. bup has a few advantages
over other backup software:
It uses a rolling checksum algorithm (similar to rsync) to split
large files into chunks. The most useful result of this is you can
backup huge virtual machine (VM) disk images, databases, and XML
files incrementally, even though they're typically all in one huge
file, and not use tons of disk space for multiple versions.
It uses the packfile format from git (the open source version
control system), so you can access the stored data even if you
don't like bup's user interface.
Unlike git, it writes packfiles directly (instead of having a
separate garbage collection / repacking stage) so it's fast even
with gratuitously huge amounts of data. bup's improved index formats
also allow you to track far more filenames than git (millions) and
keep track of far more objects (hundreds or thousands of gigabytes).
Data is "automagically" shared between incremental backups without
having to know which backup is based on which other one - even if
the backups are made from two different computers that don't even
know about each other. You just tell bup to back stuff up, and it
saves only the minimum amount of data needed.
You can back up directly to a remote bup server, without needing
tons of temporary disk space on the computer being backed up. And
if your backup is interrupted halfway through, the next run will
pick up where you left off. And it's easy to set up a bup server:
just install bup on any machine where you have ssh access.
Bup can use "par2" redundancy to recover corrupted backups even if
your disk has undetected bad sectors.
Even when a backup is incremental, you don't have to worry about
restoring the full backup, then each of the incrementals in turn;
an incremental backup acts as if it's a full backup, it just takes
less disk space.
You can mount your bup repository as a FUSE filesystem and access
the content that way, and even export it over Samba.
Upstream changes:
## 2.6.0 / May 3 2011
A rather large release, feature-version bump because of the new
multiple-gateways feature as implemented by Ryan Duryea (way to go!)
Please also note from this release that if you use Git submodules, the
Git-version requirement for the new implementation is now >= 1.5.6, from
previously un-documented. (1.5.6 is new-enough that I think this is
acceptable)
* Upgrade Net::SSH-gateway dependency to 1.1 (fixes a thread-deadlocking bug on
MRI 1.9)
* Respect "dry-run" on transfer methods (Florian Frank)
* Add support for multiple gateways: (Ryan Duryea)
set :gateway, {
'gate1.example.com' => 'server1.example.com',
[ 'gate2.example.com', 'gate3.example.com' ] =>
[ 'server5.example.com', 'server6.example.com' ]
}
* Properly support nested Git submodules, moves Git requirement to >= 1.5.6 [if
you rely upon submodules] (Ken Miller)
* Fetch tags into the remote cache, allows deploying a tag when using Git, with
the remote_cache strategy (Florian Frank)
* Various fixes to path handling bugs in the copt strategy. (Philippe Rathé)
ocsinventory-agent creates inventory data. This agent is the
successor of the former linux_agent which was released with OCS
1.01 and prior. It also replaces the Solaris/AIX/BSD unofficial
agents. The detailed list of supported Operating System is available
in the OCS Inventory Wiki.
Based on PR#44884 by YAMAMOTO Takeshi.
Additionaly, some improvements by me.
Active Management Technology (AMT) tools
descriptions from man pages:
amttool - remotely control Intel AMT managed machines.
amtterm - Intel AMT serial-over-lan (sol) client.
from amt-howto(7):
What is AMT and why I should care?
AMT stands for "Active Management Technology". It provides some remote
management facilities. They are handled by the hardware and firmware,
thus they work independant from the operation system. Means: It works
before Linux bootet up to the point where it activated the network
interface. It works even when your most recent test kernel deadlocked
the machine. Which makes it quite useful for development machines ...
Intel AMT is part of the vPro Platform. Recent intel-chipset based
business machines should have it. My fairly new Intel SDV machine has
it too.
