Argh. Yet another diff, as the prior post missed the Makefile REVISION.
diff --git a/sysutils/udfclient/Makefile b/sysutils/udfclient/Makefile index 7dc63d78d72..5a268222e62 100644 --- a/sysutils/udfclient/Makefile +++ b/sysutils/udfclient/Makefile @@ -3,6 +3,7 @@ COMMENT = userland implementation of the UDF filesystem V = 0.8.11 +REVISION= 0 DISTNAME = UDFclient.${V} PKGNAME = udfclient-${V} CATEGORIES = sysutils diff --git a/sysutils/udfclient/pkg/README b/sysutils/udfclient/pkg/README index caa00e7de1e..9f2063994d3 100644 --- a/sysutils/udfclient/pkg/README +++ b/sysutils/udfclient/pkg/README @@ -31,16 +31,19 @@ Special files and links UDF on disk drives ------------------ -Disklabels are not used, except for virtual partition "a" with -2048-byte blocksize devices. MBRs are not used, the filesystem -begins at LBA 0. Partition "c" should be used if writing directly -to a drive instead of an image file. If the drive contains prior -data, zero the leading sectors before use as shown in the first -command below. +OpenBSD disklabels are not used on storage media. OpenBSD will create +an in-memory virtual "a" partition when natively mounting UDF filesystems +read-only on 2048-byte block devices or images; see Interoperability with +mount_udf(8) below. + +MBRs are not used, the filesystem begins at LBA 0. Raw partition "c" +should be used if writing directly to a drive instead of an image file. +If the drive contains prior data, zero the leading sectors before use as +shown in the first command below. # dd if=/dev/zero of=/dev/rsd9c count=63 # newfs_udf -L shared.drive /dev/rsd9c -# ufsclient -W /dev/rsd9c +# udfclient -W /dev/rsd9c While it is possible to direct a filesystem image to a disklabel partition, there would be no interoperability with other OSes.