>I'd like to report that partition slices in FreeBSD 2.1.0 and NetBSD 1.1
>aren't 100% compatible.

>wd2s4: raw partition size != slice size
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4c: start 2459520, end 3169151, size 709632
>wd2s4: rejecting partition in BSD label: it isn't entirely within the slice
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4d: start 0, end 3169151, size 3169152

FreeBSD doesn't allow partitions outside the slice that contains the
label.  It deletes such partitions from the in-core label but doesn't
write anything to the disk unless you write the label.  The 'd' and
'c' partitions are handled automatically to match the DOS partition
table and/or the drive if there is no DOS partition table.

The messages could be punctuated better:

wd2s4: warning: raw partition size != slice size:
wd2s4: start 2459520, end 3173183, size 713664,
wd2s4c: start 2459520, end 3169151, size 709632

The first line is a warning and the last 2 lines describe the inconsistent
objects.  You seem to be wasting 713664 - 709632 = 4032 sectors.

wd2s4: error: rejecting partition in BSD label: it isn't entirely within the slice:
wd2s4: start 2459520, end 3173183, size 713664
wd2s4d: start 0, end 3169151, size 3169152

The first line is an error and the last 2 lines describe the inconsistent
objects.  Old 'd' partitions often cause this error.

>wd2s4: raw partition size != slice size
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4c: start 2459520, end 3169151, size 709632
>wd2s4: rejecting partition in BSD label: it isn't entirely within the slice
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4d: start 0, end 3169151, size 3169152
>wd2s4: raw partition size != slice size
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4c: start 2459520, end 3169151, size 709632
>wd2s4: rejecting partition in BSD label: it isn't entirely within the slice
>wd2s4: start 2459520, end 3173183, size 713664
>wd2s4d: start 0, end 3169151, size 3169152

>- slices created using NetBSD, when FreeBSD tries to fsck them.

The messages are repeated because fsck opens and closes the devices
several times and rebuilding the tables on first opens is a simple
way of getting them right for removable media.

Bruce