From owner-freebsd-questions Wed Jul 30 08:43:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA09948 for questions-outgoing; Wed, 30 Jul 1997 08:43:00 -0700 (PDT) Received: from citadel.cdsec.com (gram.aztec.co.za [196.3.254.235]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA09927 for ; Wed, 30 Jul 1997 08:42:53 -0700 (PDT) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.5/8.6.9) id RAA12224 for ; Wed, 30 Jul 1997 17:44:07 +0200 (SAT) Received: by citadel via recvmail id 12168; Wed Jul 30 17:43:16 1997 From: Graham Wheeler Message-Id: <199707301523.RAA09409@cdsec.com> Subject: Problems making a release To: support@freebsd.org Date: Wed, 30 Jul 1997 17:23:12 +0200 (SAT) Cc: gram@gram.cdsec.com (Graham Wheeler) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi guys I'm having some hassles with doing a `make release' in /usr/src/release with FreeBSD 2.2.2 (I used to do this regularly with FreeBSD 2.1.0, but I did hack the Makefile in that case as well, I remember - but that was a long time ago and I don't remember what the problems were that I experienced at that stage). The first problem is that cvs doesn't like the order in which arguments are given in the Makefile. There is a "-P" argument in the Makefile *after* the "co" argument - so this is passed to co instead of cvs, and co barfs with an invalid argument error. So it beats me how you can do a "make release" with this Makefile as it stands! Anyway, I decided to try to skip this target, as I don't want all the sources checked out; I already have a source tree in /usr/src that I want to use. So I've been doing "make release.1", "make release.2", etc, one after the other by hand. All went well up until release.8, and the building of the floppy image using /dev/vn0c. It seems from the invocation of doFS.sh that the virtual file system should by 1440kb in size. However, I see the following sequence in the output: -------- ... sh -e /usr/src/release/doFS.sh /R/stage /mnt 1440 /R/stage/mfsfd 8000 mimumum ioctl DIOCWLABEL: operation not supported by device Warning: block size restricts cylinders per group to 10 /dev/rvn0c: 2400 sectors in 1 cylinders of 1 tracks, 2400 sectors 1.2MB in 1 cyl groups (10 c/g, 11.72MB/g, 1408i/g) super-block backups (for fsck -b #) at: 32, /mnt: write failed, file system is full cpio: write error: No space left on device *** Error code 1 Stop. -------- Okay, the first thing I don't understand is why 1.2MB is reported above (unless this is the space left after creating the superblocks, but is does seem a bit coincidental that it comes out at 1.2Mb, the size of a HD 5" floppy). Even stranger is the result of a "df -k"; for this I see: /dev/vn0c 1K-blocks 995 used 991 Avail 4 100% /mnt The root file system has about 12Mb free - so why should the vn device report 995kb of space, when it should be 1.44Mb (or 1.2Mb??). Just in case you're wondering, I'm trying to do this to get a new release of our FreeBSD-based Citadel firewall out. Any assistance would be much appreciated - I'm afraid I find the process of building these release floppies pretty obscure, and don't have much of a clue as to what the problem is. Thanks Graham -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/