CVS log for pkgsrc/sysutils/wipe/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / sysutils / wipe

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

*: Convert broken sourceforge HOMEPAGEs back to http

all: migrate several HOMEPAGEs to https

pkglint --only "https instead of http" -r -F

With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.

This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.

(sysutils/wip) Updated 2.2.0 to 2.3.1

2.3.1:
fixed Makefile bug! Running make uninstall removed target bin directory.

2.3:

DEFAULTS!
the default is now one single random pass  <-- MAJOR CHANGE
special files are no longer deleted by default

support for wiping char devices, such as tape drives

percentage reporting improved (thanks to Jason Tackaberry for patch)

cleanup and exit upon SIGINT

each wiped file prints on a seperate line

skip unnecessary fdatasync()s, unless you want the extra accuracy on the % shown (-e option)

call fsync() on the file after name wipe, in addition to fsync on the directory

if fdatasync() fails, try for O_SYNC and only complain once per file

fixed some off-by-ones
fixed percentages for non-static wipes

2.2.1:
added largefile support for linux and solaris (tested on linux)

fixed drill_down(). it was using the wrong length to null term the string

Use OPSYSVARS.

Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.

Fix build on SunOS.  Patch from Sebastian Wiedenroth.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

LICENSE=gnu-gpl-v2.

Transfer ownership to pkgsrc-users.  pancake's address is not valid any
more and he has agreed in private mail to drop maintainership.

DESTDIR support

Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

Import wipe from pkgsrc-wip.  Packaged by pancake and modified by me.

Wipe is a secure file wiping utility.

There are some low level issues that must be taken into consideration.
One of these is that there must be some sort of write barrier between
passes.  Wipe uses fdatasync(2) (or fsync(2)) as a write barrier, or
if fsync(2) isn't available, the file is opened with the O_DSYNC or
O_SYNC flag.  For wipe to be effective, each pass must be completely
written.  To ensure this, the drive must support some form of a write
barrier, write cache flush, or write cache disabling.  SCSI supports
ordered command tags, has a force media access bit for commands, and
write cache can be disable on mode page 8.  IDE/ATA drives support
write cache flushes and write cache disabling.

Unfortunately, not all drives actually disable write cache when asked
to.  Those drives are broken.  Write caching should always be
disabled, unless your system is battery backed and always powers down
cleanly.

Initial revision