NetBSD installation ISO.
Further information can be found here:
http://genericzero.wordpress.com/2009/08/01/install-netbsd-from-a-usb-memory-stick-the-easy-way/
memory stick the easy way
I got tired of having to jump through hoops to install NetBSD on my
Eee PC, so I wrote a simple script to take a NetBSD release ISO and
convert it to an image that can be written to a USB memory stick.
To use the script, simply feed it an ISO and tell it where to write
the resulting image:
$ sh mkmemstick.sh i386cd-5.0.1.iso i386memstick-5.0.1.img
The resulting image can be written to a memory stick using dd(1):
$ dd if=i386memstick-5.0.1.img of=/dev/sd0d
Please note that this script depends on the sysutils/cdrtools package
for extracting the contents of the release ISO.
Hopefully this will be integrated with the build process so these
images are available for those who cannot prepare an image due to lack
of access to a NetBSD machine.
New in Version 0.2 (released 2011-04-15):
* Bug fixes:
+ extract-account:
- account extraction left temp files if authorized_keys had
the uchg flag set
- if the user didn't actually exist, a bogus tarball would be
created anyway
+ install-account:
- the home directory was assumed to be /home/${USER}, which
meant that root's files weren't installed properly
- If the user already existed, the order of entries in the
passwd database wasn't preserved. This caused problems with
root accounts because getpwuid(0) started returning the
passwd entry for the 'toor' user (breaking "are you root?"
tests in various scripts).
+ sudo-add:
- if sudo-add couldn't find the sudoers file or couldn't read
it, it didn't remove existing entries when adding or
removing a user (adding duplicate entries if adding a user
that was already there, and silently failing when removing a
user)
- if sudo-add could find and read the sudoers file:
* it would remove the wrong existing entry if the username
of the user being added/removed started with the same
characters as another user higher in the sudoers file
(e.g., adding or removing foo would remove user foobar if
foobar was higher in the sudoers file)
* 'sudo-add -r' would only remove the first instance of a
user from sudoers (a particular problem given the above
bug)
- sudo-add wasn't preserving order if the user was already in
sudoers (order can be significant in sudoers)
* Less verbose output.
Libfind:
- New flag WALK_STRIPLDOT to strip leading "./" like star does
Cdrecord:
- cdrecord now warns about the correct max. CD-Text size
for a single language that is permitted by the standard.
Mkisofs (Maintained/enhanced by Jörg Schilling since 1997, originated by Eric Youngdale):
- Fixed several typos in the mkisofs man page and in mkisofs
Upstream changes:
Bugfixes
* #301: Fixed a bug in local?s behavior when capture=False and output.stdout
(or .stderr) was also False. Thanks to Chris Rose for the catch.
* #310: Update edge case in put where using the mode kwarg alongside
use_sudo=True runs a hidden sudo command. The mode kwarg needs to be octal but
was being interpolated in the sudo call as a string/integer. Thanks to Adam
Ernst for the catch and suggested fix.
* #311: append was supposed to have its partial kwarg's default flipped from
True to False. However, only the documentation was altered. This has been fixed.
Thanks to Adam Ernst for bringing it to our attention.
* #312: Tweak internal I/O related loops to prevent high CPU usage and poor
screen-printing behavior on some systems. Thanks to Kirill Pinchuk for the
initial patch.
* #320: Some users reported problems with dropped input, particularly while
entering sudo passwords. This was fixed via the same change as for #312.
Documentation
* Added a missing entry for env.path in the usage documentation.
Upstream changes:
## 2.5.21 / April 6 2011
* Fixed to follow best-practice guidelines from Bundler (Ben Langfeld)
* No longer force a gemset for Capistrano development. (Ben Langfeld)
## 2.5.20 / March 16 2011
* `deploy:migrations` will now always operate on the latest_release, not
current_release (Mike Vincent)
* Adds a check for the presence of `rsync` when using the copy strategy with
`rsync`. (Chris Griego)
* Do not try to look up the `:release_path` on servers which are defined
`:no_release` (Chris Griego)
* Tiny patch to the `CVS` SCM code to be Ruby 1.9 compatible (Martin Carpenter)
* Changed the default `Git` submodule behaviour to use `--recursive`
Lighthouse Issue #176. (Lee Hambley)
* `:public_children` can now be `set()`, the default is unchanged, thanks
(Chris Griego)
* Fixing the load path in the default `Capfile` to search vendored/unpacked
Gems. Lighthouse Issue #174 (Mari Carmen/Rafael García)
* Adds a `maintenance_basename` variable (default value is `maintenance`) to
allow you to set the maintenance page name (Celestino Gomes)
* Spelling fixes in inline-documentation (Tom Copeland)
* Make `zip` and `tar` handle symlinks the same way (zip follows symlinks by
default, tar needs the option `-h`) (Ross Cooperman)
on a single physical machine. The xentools41 package contains the
tools to create, destroy and control the virtual machines.
This package contains the tools for Xen 4.1.x
Release notes:
The Xen team is pleased to announce the release of Xen 4.1.
The result of nearly 12 months of development, new features include:
* A re-architected and improved XL toolstack replacing XM/XEND
* Prototype credit2 scheduler designed for latency-sensitive workloads and
very large systems.
* CPU Pools for advanced partitioning.
* Support for large systems (>255 processors)
* Support for x86 Advanced Vector eXtension (AVX).
* New Memory Access API enabling integration of 3rd party security
solutions into Xen virtualized environments.
* Many IOMMU fixes (both Intel VT-d IOMMU and AMD IOMMU).
* Many toolstack and buildsystem fixes for Linux and NetBSD hosts.
* Thirdparty libs: libvirt driver for libxl has been merged to upstream
libvirt.
* HVM guest PXE boot enhancements, replacing gPXE with iPXE.
* Even better stability through our new automated regression tests.
Detailed release notes, including a more extensive feature list:
http://wiki.xen.org/xenwiki/Xen4.1
To download tarballs:
http://xen.org/products/xen_source.html
Or the Mercurial source repository (tag 'RELEASE-4.1.0'):
http://xenbits.xen.org/xen-unstable.hg
And the announcement on the Xen blog:
http://blog.xen.org/index.php/2011/03/25/xen-4-1-releases/
Thanks to the many people who have contributed to this release!
Regards,
The Xen Team
guests operating systems on a single machine. Guest OSes (also called "domains"
)
require a modified kernel which supports Xen hypercalls in replacement
to access to the physical hardware. At boot, the xen kernel is loaded
along with the guest kernel for the first domain (called domain0).
domain0 has privileges to access the physical hardware (PCI
and ISA devices), administrate other domains and provide virtual
devices (disks and network) to other domains.
This package contains the Xen4 kernel itself.
Release notes:
The Xen team is pleased to announce the release of Xen 4.1.
The result of nearly 12 months of development, new features include:
* A re-architected and improved XL toolstack replacing XM/XEND
* Prototype credit2 scheduler designed for latency-sensitive workloads and
very large systems.
* CPU Pools for advanced partitioning.
* Support for large systems (>255 processors)
* Support for x86 Advanced Vector eXtension (AVX).
* New Memory Access API enabling integration of 3rd party security
solutions into Xen virtualized environments.
* Many IOMMU fixes (both Intel VT-d IOMMU and AMD IOMMU).
* Many toolstack and buildsystem fixes for Linux and NetBSD hosts.
* Thirdparty libs: libvirt driver for libxl has been merged to upstream
libvirt.
* HVM guest PXE boot enhancements, replacing gPXE with iPXE.
* Even better stability through our new automated regression tests.
Detailed release notes, including a more extensive feature list:
http://wiki.xen.org/xenwiki/Xen4.1
To download tarballs:
http://xen.org/products/xen_source.html
Or the Mercurial source repository (tag 'RELEASE-4.1.0'):
http://xenbits.xen.org/xen-unstable.hg
And the announcement on the Xen blog:
http://blog.xen.org/index.php/2011/03/25/xen-4-1-releases/
Thanks to the many people who have contributed to this release!
Regards,
The Xen Team
must be propagated in its bl3.mk file.
Do that, and depend on that version; recursive PKGREVISION bump
since a few dependencies might link against jpeg now.
Set LICENSE.
Major changes in upstream
Temporary file names now include digits in addition to letters.
mktemp will now terminate after 2*N^62 attempts, where N
is the number of Xs in the template. Previously it would try
forever.
Fixed UTF8 formatting of the grave accent character in the manual.
an array of pointer (in struct fdtab) rather than a pointer of pointers.
Sadly for us, no, arrays and pointers are not equivalent from a memory
perspective: while pointers from/to another address space can
be consumed by kvm(3) to query for data in kernel space, arrays
are more tricky, especially when their content is copied in userland:
they are part of the copied struct.
Address of array members are only valid in their own address space,
in our case userland, which is (fortunately?) different from kernel space.
This breaks the various kvm_read() calls that query for file descriptor
information. Consequence: lsof(1) cannot print filedescriptor information
(starting from 5.99.14), and silently ignores the errors, as using
the userland fdtab (``dt'' variable) is not valid for kernel.
Fix that by using the ``fd_dt'' member of struct filedes, which stores
the address of the fdtab struct in kernel address space. Took a few hours
to understand what was going on with lsof(1), hmmm.
Luckily, fstat(1) uses the proper model (checked about 5min ago). Why
lsof(1) decided not to log an error on kvm_read() is... a good question.
Bump rev.
