From owner-freebsd-bugs Mon Feb 11 15:40: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8FD6637B404 for ; Mon, 11 Feb 2002 15:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g1BNe2o16952; Mon, 11 Feb 2002 15:40:02 -0800 (PST) (envelope-from gnats) Date: Mon, 11 Feb 2002 15:40:02 -0800 (PST) Message-Id: <200202112340.g1BNe2o16952@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: bin/34832: /usr/share/man/cat3/setkey.3.gz linked to crypt.3.gz, not cipher.3.gz Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34832; it has been noted by GNATS. From: "Crist J. Clark" To: Alan Eldridge Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/34832: /usr/share/man/cat3/setkey.3.gz linked to crypt.3.gz, not cipher.3.gz Date: Mon, 11 Feb 2002 15:30:44 -0800 On Mon, Feb 11, 2002 at 09:42:35AM -0500, Alan Eldridge wrote: [snip] > >Description: > > On a fresh 4.5-RELEASE installation, /usr/share/man/cat3/setkey.3.gz is the > same file as crypt.3.gz. > > It should be hard-linked to cipher.3.gz. > > Note: It's correct in /usr/share/man/man3. Only cat3 has the error. > > [blank lines inserted for readability] > [alane ~]$ ls -l /usr/share/man/{man,cat}3/{setkey,cipher,crypt}.3* > > -rw-r--r-- 1 man wheel 1389 Feb 11 08:37 /usr/share/man/cat3/cipher.3.gz > -rw-r--r-- 7 man wheel 2799 Jan 28 09:35 /usr/share/man/cat3/crypt.3.gz > -rw-r--r-- 7 man wheel 2799 Jan 28 09:35 /usr/share/man/cat3/setkey.3.gz > > -r--r--r-- 5 root wheel 2019 Jan 28 08:13 /usr/share/man/man3/cipher.3.gz > -r--r--r-- 3 root wheel 3402 Jan 28 08:11 /usr/share/man/man3/crypt.3.gz > -r--r--r-- 5 root wheel 2019 Jan 28 08:13 /usr/share/man/man3/setkey.3.gz This is a problem with the way the catpages are distributed. Right now, they are a separate distro. They are built for a "default" install. In such a default install, the des_cipher(3), des_setkey(3), encrypt(3), and setkey(3) are all linked to crypt(3). When you add the 'crypto' distribution, it correctly clobbers the manpages as you have seen, but it does not do the catpages (since catpages are a separate distro and other distros do not contain catpages). The workaround for this is not as easy as it could be; catman(1) won't see the current inconsistencies in your man and catpages, # cd /usr/share/man/cat3 # rm cipher.3.gz des_cipher.3.gz des_setkey.3.gz encrypt.3.gz setkey.3.gz # echo /usr/bin/catman | su -m man There may be other inconsistencies between your catpages and manpages. I'd actually recommend that instead of the above, you rebuild them all, # find /usr/share/man/cat* -type f -delete # echo /usr/bin/catman | su -m man It takes a few minutes, but it is a one time cost. As for a fix, too late for 4.5-RELEASE, obviously. Off the top of my head, I cannot really think of an easy way to do this. We do not want the crypto, or other distros, adding catpages unconditionally. There is no good way to let the catman distro know which other distros were chosen and add the appropriate catpages; that's not how the distros work. The only reasonable possibility I can think of that fits the current distro model is to have a separate crypto-catpages (like there is already a separate crypto-src) sub-distro. OTOH, IMHO, probably the best thing to do would be to do away with the catman distro all together and have sysinstall run catman(1) after all manpages are installed and guarantee that the two are in sync. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message