Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
The grand plan with gnome-mount is to get the appropriate GNOME
software (such as gnome-volume-manager and gnome-vfs) to use this
instead of invoking mount(1)/umount(1)/eject(1) / invoking methods on
HAL directly.
Included in gnome-mount is also gnome-umount and gnome-eject. All
programs utilize the methods on HAL and as such run unprivileged. The
rationale for gnome-mount is to have a centralized place (in gconf)
where settings (e.g. mount options, mount location) are
maintained.