From owner-freebsd-doc Sat May 11 2:50:26 2002 Delivered-To: freebsd-doc@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4298C37B40C for ; Sat, 11 May 2002 02:50:08 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g4B9o8x33378; Sat, 11 May 2002 02:50:08 -0700 (PDT) (envelope-from gnats) Date: Sat, 11 May 2002 02:50:08 -0700 (PDT) Message-Id: <200205110950.g4B9o8x33378@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Giorgos Keramidas Subject: Re: docs/36773: Unclear/inconsistent instructions in Handbook section 19.4.3 Reply-To: Giorgos Keramidas Sender: owner-freebsd-doc@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 docs/36773; it has been noted by GNATS. From: Giorgos Keramidas To: Gregory Neil Shapiro Cc: bug-followup@freebsd.org Subject: Re: docs/36773: Unclear/inconsistent instructions in Handbook section 19.4.3 Date: Sat, 11 May 2002 12:17:47 +0300 On 2002-04-04 19:44, Gregory Neil Shapiro wrote: > > >Description: > > Here are excerpts and my commentary (indented) on section 19.4.3 of the > handbook: > 19.4.3 Update /etc/group > > : The title of the section is "Update /etc/group". However, the > : section describes the need for certain usernames and groups to > : exist for a make world to succeed. The title of the section is > : misleading as it only mentions the group file. How about? Update the files of <filename>/etc</filename> > There have been occasions when the installation part of ``make world'' > has expected certain usernames or groups to exist. When performing > an upgrade it is likely that these groups did not exist. This caused > problems when upgrading. > > : Not only ``make world'', but also ``make installworld'' That's what it says. The ``installation part of "make world"'' is the same as ``installworld''. I have left this unchanged but if there is someone that has an idea of a better wording I won't object to changing it. > : The first sentence says "usernames or groups". The second sentence > : only mentions "groups". Missing usernames cause just as many > : problems as missing groups. See below. > The most recent example of this is when the ``ppp'' group (later renamed > ``network'') was added. Users had the installation process fail for them > when parts of the ppp subsystem were installed using a non-existent (for > them) group name. > > : The new most recent example is the ``smmsp'' username > : and group, both of which are needed for mtree to create > : /var/spool/clientmqueue/. > > The solution is to examine /usr/src/etc/group and compare its list of > groups with your own. If there are any groups in the new file that are > not in your file then copy them over. Similarly, you should rename any > groups in /etc/group which have the same GID but a different name to > those in /usr/src/etc/group. > > : You should also document merging /usr/src/etc/master.passwd using > : vipw (so the database files are regenerated properly after the > : users manually merge the new accounts). How does this look? %%% Index: chapter.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v retrieving revision 1.120 diff -u -r1.120 chapter.sgml --- chapter.sgml 4 May 2002 14:22:34 -0000 1.120 +++ chapter.sgml 11 May 2002 09:16:22 -0000 @@ -683,7 +683,7 @@ - Update <filename>/etc/group</filename> + Update the files of <filename>/etc</filename> The /etc directory contains a large part of your system's configuration information, as well as scripts @@ -697,13 +697,13 @@ There have been occasions when the installation part of make world has expected certain usernames or groups to exist. When performing an upgrade it is likely that these - groups did not exist. This caused problems when upgrading. + users or groups did not exist. This caused problems when upgrading. - The most recent example of this is when the ppp subsystem were installed using a - non-existent (for them) group name. + The most recent example of this is when the + smmsp user was added. Users had the + installation process fail for them when + mtree was trying to create + /var/spool/clientmqueue. The solution is to examine /usr/src/etc/group and compare its list of @@ -711,7 +711,14 @@ are not in your file then copy them over. Similarly, you should rename any groups in /etc/group which have the same GID but a different name to those in - /usr/src/etc/group. + /usr/src/etc/group. You should also + merge any changes from + /usr/src/etc/master.passwd into your + existing /etc/master.passwd with + &man.vipw.8;. Always use &man.vipw.8; to make the merge to + /etc/master.passwd, since &man.vipw.8; + makes sure that the proper database files are rebuilt after + the merge. If you are feeling particularly paranoid, you can check your %%% Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message