- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
installations.
* Modify the package to not install all of the configuration files with
the execute bit set -- only install the helper scripts that way.
* Update the block-file-nbsd script to not blindly try to configure (and
often fail to configure) every vnd(4) device until it finds one that
works. We now just determine what the next free vnd(4) device is and
configure it directly.
* Add a netbsd-nbsd script that avoids trying to do all the Linux-specific
that just filled the log files with garbage on NetBSD.
* Update the vif-bridge-nbsd script to check that the bridge device is
configured before using it.
* Add clear comments at the top of scripts that can be customized so that
the user has enough information to know how to do the customization.
* Add a xendomains rc.d script that can be used to start and stop guest
domains at system boot- or shutdown-time.
Bump the PKGREVISION to 5.
| xfrd reads from the network socket using
| fread() on an _IONBF'ed stream; under NetBSD, this results in a
| sequence of one-character reads. This behavior, as far as I can tell,
| goes back all the way to V7 Unix; i.e., it's older than me.
|
| So I've modified libxutil, which has its own IO indirection layer, to
| switch to read(2) in the "unbuffered" case"
bump PKGREVISION
| libxc change #1 is to have xfrd's forked child munmap each 4MB batch
| of foreign RAM after it's done writing it, rather than unmapping only
| the last one and letting the process's exit clean up the rest. This
| really does look like a simple mistake, and strictly speaking it's not
| that big a deal -- but on NetBSD, the foreign mappings count against
| the process's locked memory rlimit as if it were the dom0's own RAM.
|
| libxc change #2... I don't really understand the problem; it has
| something to do with live migration and the domU releasing
| pseudo-physical pages after they were sent but before it's suspended.
| Except that, for non-live mode, I think it's reporting all the holes
| in the pseudo-physical range, even though those pages haven't been
| sent. In any case, the result is that the restoring xfrd fails to
| decrease_reservation the pages away. And I distinctly recall this
| working at least once under Linux with Xen 2, but I have little idea
| what NetBSD might be doing differently.
Bump PKGREVISION. This, along with a up to date -current kernel,
make xm (save|restore) work properly for a linux domU.
as the INSTALL and DEINSTALL scripts no longer distinguish between
the two types of files. Drop SUPPORT_FILES{,_PERMS} and modify the
packages in pkgsrc accordingly.
Lots of changes, notably now it uses Linux-2.6.11.x, a NetBSD
bug was fixed.
pkgsrc changes:
* Honor PKG_SYSCONFDIR and SUPPORT_FILES for configuration files.
* xend.sh: no more python warning messages when the script is used
on non NetBSD/Xen systems.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
- set command_interpreter, so that rc.subr(8) can find the process(es).
- /usr/pkg/sbin/xend {stop,restart} don't to what we expect, to
let rc.subr do it instead.
Bump PKGREVISION.
Should fix pkg/29847.
u32, and removing the padding bits in blkif_extent_t. This way the size
of the message doesn't change, and new tools are compatible with
older kernel (I will commit this change to kernel shortly too).
This has also been commited to xen-2.0-testing by Christian, and will be
in xen-2.0.5.
While here, remove the PKG_SYSCONFSUBDIR, as nothing looks for config files
here yet.
Bump PKGREVISION.
