From owner-svn-src-head@FreeBSD.ORG Fri Mar 14 16:55:25 2014 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C5AEDE; Fri, 14 Mar 2014 16:55:25 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A0C5D25E; Fri, 14 Mar 2014 16:55:24 +0000 (UTC) Received: from dator167.onk.lu.se (dator167.onk.lu.se [130.235.5.190]) by mrelayeu.kundenserver.de (node=mreue101) with ESMTP (Nemesis) id 0MgfcV-1WkpSg0nR9-00NxCI; Fri, 14 Mar 2014 17:55:21 +0100 Message-ID: <53233477.7060400@FreeBSD.org> Date: Fri, 14 Mar 2014 17:55:19 +0100 From: Christian Brueffer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Warner Losh , John-Mark Gurney Subject: Re: svn commit: r263110 - head/share/man/man4 References: <201403131619.s2DGJax1071196@svn.freebsd.org> <4D0B04BD-4EF6-4963-941E-012B81F8DFAB@jnielsen.net> <20140314015438.GO32089@funkthat.com> <5322C83F.6060109@FreeBSD.org> <20140314164107.GS32089@funkthat.com> <933F8270-90C1-4AFE-9F39-A7ADBC05C772@bsdimp.com> In-Reply-To: <933F8270-90C1-4AFE-9F39-A7ADBC05C772@bsdimp.com> X-Enigmail-Version: 1.6 OpenPGP: id=3A67DC36; url=http://people.freebsd.org/~brueffer/brueffer.key.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ddKqq6cLAUmMJTHCPMrEjkAoSaq0VlnVd" X-Provags-ID: V02:K0:IpwOQM1Vl1VNQ/1G1xzlBylUFLf4nTCKUEW9ECHEjay HdNqsEcCvEJ7fPx8StCXwEbz9bnRf8/Z+XYaGJCCRgZ/lxm7B+ p2xkvPX9jL0V/VgECjEWr1ZD/61GA+Kl9ESq9NYIqe5XH3IIXC uyR2zUahlOpC5TDsyhfUVI9ruQPTCoutfU614QFsLcoX+DiGh1 etdPshL6FUjylfF5utrZc6gLDNrDgat9mYcllnT2/1cGqQ6j/U 7pZqI2pTNezemHWQ4ckHOH50flj2ur83N1l1Vn0kgIVgomwbIi Hxoo5ndqMCNclaPBp2jcD6xkMzuWsO3+JNVIHeuWWtguKx9Mdj JqCVH6bTLy6mKhDC5vcqkYMguPoG0aVyCbKycPV+b Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, John Nielsen , src-committers@freebsd.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Mar 2014 16:55:25 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ddKqq6cLAUmMJTHCPMrEjkAoSaq0VlnVd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 3/14/14 5:47 PM, Warner Losh wrote: >=20 > On Mar 14, 2014, at 10:41 AM, John-Mark Gurney wrote= : >=20 >> Warner Losh wrote this message on Fri, Mar 14, 2014 at 08:30 -0600: >>> On Mar 14, 2014, at 3:13 AM, Christian Brueffer wrote: >>> >>>> On 3/14/14 2:54 AM, John-Mark Gurney wrote: >>>>> John Nielsen wrote this message on Thu, Mar 13, 2014 at 16:28 -0600= : >>>>>> On Mar 13, 2014, at 10:19 AM, John-Mark Gurney w= rote: >>>>>> >>>>>>> Author: jmg >>>>>>> Date: Thu Mar 13 16:19:36 2014 >>>>>>> New Revision: 263110 >>>>>>> URL: http://svnweb.freebsd.org/changeset/base/263110 >>>>>>> >>>>>>> Log: >>>>>>> remove link to the missing AMD Geode LX SB man page... we can add= it >>>>>>> back once someone cares enough to write one.. >>>>>> >>>>>> You mean like this one? >>>>>> http://svnweb.freebsd.org/base/head/share/man/man4/man4.i386/glxsb= =2E4 >>>>> >>>>> The problems of checking on an amd64 box... :( >>>>> >>>>> Actually, how are we suppose to handle links to arch dependant man >>>>> pages in arch independant man pages? I did this check on an amd64 = box, >>>>> so the page glxsb didn't get installed... Should we just always >>>>> install these man pages on all arches then? Or are we fine w/ >>>>> references to non-existant pages (on some arches)? >>>>> >>>>> Or should glxsb.4 be moved to an arch independant dir? >>>>> >>>> >>>> I wonder if it makes sense to keep arch-dependent man directories at= >>>> all. I.e., if I prepare an ARM disk image on my amd64 laptop, I rea= lly >>>> want to have the arm manpages available on that amd64 box. >>>> >>>> Does anyone see a reason not to move man4/man4.${ARCH}/*.4 to man4? >>>> We're talking about 60 manpages here, so space is not really an issu= e. >>> >>> Historically there was the separation because xp on one platform migh= t be >>> radically different from xp on another platform. The other reason was= confusion >>> because it wasn?t always clear if device foo actually worked on platf= orm X. >> >> We have less of that issue now, but it could still be.. but issues lik= e >> that can be addressed other ways, though kernel config, release notes,= >> etc.. I doubt people use manpages as a guage if a device worked on >> their arch... Plus, if the device is shared and known not to work on >> a specific arch, that should be listed in the BUGS section of the man >> page.. :) >=20 > Yea, kinda my point :) >=20 >>> Do we have any collisions like that? If so, we need to resolve those = first. >> >> Doesn't look like it... >> $ grep ^_ Makefile | sed -e 's/.4.*//' | wc -l >> 86 >> $ grep ^_ Makefile | sed -e 's/.4.*//' | sort -u | wc -l >> 86 >> >> It's also telling that besides i386 and amd64 specific man pages, we >> only have one mips specific man page in man4=85 >=20 > True enough, I hadn=92t looked... >=20 >> This won't address the other man pages for arch specific utilities >> and libraries though, like sunlabel=85 >=20 > True, but those are niche things, so it is less important :) >=20 >>> Also, it would be good to tag the ones that are arm specific as such = somehow. >> >> Should we just tag the pages w/ a section listing relevant architectur= es, >> or break the beauty of single digit section numbers and do 4.i386? >=20 > Tag in the man page itself, either in its own unique section, or in BUG= S. >=20 We kinda maintain some of this information already (albeit I'm not sure how accurate it is) in the hardware notes. The hardware notes themselves are generated from the HARDWARE sections of the manpages, while the arch information is in src/release/doc/share/misc/dev.archlist.txt. One possibility would be to generate this file from an ARCHITECTURE (or the like) section in section 4 manpages, the same way as we to with HARDWARE sections. Chris --ddKqq6cLAUmMJTHCPMrEjkAoSaq0VlnVd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJTIzR4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5QzhCQjQ5MDgzNDUwNjkyOUM5Mjg2NDE3 OEM4MzY5ODQ3RTE2NDg3AAoJEHjINphH4WSHyogP/0SxFvQsNkTkBtijfYqNJ/3o N3C8urA90BAYFDuuBWA7YBC/B04Lrn2D5DIuZxEIF3ai3c3xLSovXN8goqrNTgaW eNrik7PbmJq4nTrGCP4HG1mrzbf/YumptoDKqz7/fm3aB6+ld09YfBrQn4kLPG0O mM6J+EQRznUxreyicu5ZKwpbMx3RwegCQj1AqkY7yoVhnFSFRBWDaoYHMbLQn7sA Mnokbi8wmd/1wg0d0WEqt4Caft57CrWijggNS9I4SVSxWdj+V41Ha1vsfNIGGqDs s6/j5Xh10lSXMLxRyInDGAIQIoHfZLH9Ef+PET1aqEpxfmcSc4EKsFILkHfwmLuJ vjRjPn2wD+GEeto4NHI4/zbwfWHC7lBz5/7H5KlvmAt1/bHvo+xOv0E1xPBBszmq 19klhoFvhZrOKmp4yvPK4gnmjUujws6s6HAZOncn5lyVSmEI1CJxidLra1feC7J5 KAaGSeCmVW2xnlBIDmvXWYAJk0N0NP3V+BmADcZPrNn2rs0kRxpcKvcRZ9zp7b5k hdDPei+IAWQvN/sHzXgK7BG/tQmJ5anb6QqhvnZevI7sFk9rZSeD06anE/Mvtye4 zorhGeWhkp8LF0b98YwFkdp1ILhmwjYhoytwjYTdM5iiE/DPChHPcg4vgKSX+o64 g9RPDmGrcesz8bvboYho =RhP/ -----END PGP SIGNATURE----- --ddKqq6cLAUmMJTHCPMrEjkAoSaq0VlnVd--