On Sat, 2020-05-02 at 15:35 +0800, Kevin Buckley via blfs-dev wrote: > On Wed, 29 Apr 2020 at 13:21, Pierre Labastie via blfs-dev > <blfs-dev@lists.linuxfromscratch.org> wrote: > > What you propose in V2 is what is used in the lfs book. It looks > > slightly better when rendered, but is much less readable when > > editing. > > Yes, it was inspired by the LFS Book. > > > Now, from my POV, command explanations in blfs are rationales > > explaining why they are there, not really full explanations of the > > commands themselves. The user is supposed to be able to find those > > details by him/herself. So the explanations can be sketchy. But > > explanations don't hurt OTOH... I've applied the first version at > > r23041. Thanks. > > I do think that Bruce had a point, when he said that the BLFS book > doesn't need to explain the "%p" because a reader can just go and > read the man page, however, I'd rather see the Book explain the > "%p" AND point them in the direction of the man page, in respect > of other "placeholder" parameters in the prompt, so something akin > to > > --with-passprompt: > This switch sets the password prompt. > The %p will be expanded to the name of the user whose password is > being requested. > See the manual page for details of other ways to in which to > customise > the Sudo prompt.
I think people building blfs should know that the manual pages should be consulted for details... Note that referring to the manual page in the command explanations is not timely if the package is not installed yet. And we refer to the sudoers manual page in the configuration section. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
