Date: Sun, 3 Sep 1995 20:30:30 +1000 From: Bruce Evans <bde@zeta.org.au> To: freebsd-current@FreeBSD.ORG, jdli@linux.csie.nctu.edu.tw Subject: Re: Making a release problem : bootfd Message-ID: <199509031030.UAA07015@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> I tried to make a release myself, I had finished release.0 to release.7, > when making release.8 (bootfd), it died due to disklabel failure. > How to solve it ? (I am using 2.2-CURRENT, kernel supports MFS) > Thanks. >cd /usr/src/release && make doFS FSSIZE=1075 FSPROTO=/R/stage/mfsfd FSLABEL=mfs1075 FSINODE=80000 >rm -f fs-image >if [ ! -b /dev/vn0 -o ! -c /dev/rvn0 ] ; then cd /dev && sh MAKEDEV vn0 ; fi >dd of=fs-image if=/dev/zero count=1075 bs=1k 2>/dev/null >vnconfig -c /dev/rvn0 fs-image >disklabel -w -r -B -b /R/stage/trees/bin/usr/mdec/fdboot -s /R/stage/trees/bin/usr/mdec/bootfd /dev/rvn0 mfs1075 >ioctl DIOCWLABEL: Inappropriate ioctl for device >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This part of the Makefile seems to be old and broken. Disk labels are only available on vn devices if vnconfig is invoked with the undocumented `labels' option. Running disklabel on /dev/rvn0 would be bogus even if labels were enabled. It is bogus for all disk devices /dev/rxxN but happens to work for floppies due to nonstandard device names for floppies. disklabel should normally be invoked on the device xxN or xxNsM, e.g., on vn0 or vn0s3. Then then disklabel will build the correct device, e.g., /dev/rvn0c. /dev/rvn0 is a completely different device from /dev/rvn0c. >cd /R/stage/mfsfd && find . -print | cpio -dump /mnt >cpio: write error: No space left on device The kernel and/or utilities are now slightlty too large. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509031030.UAA07015>