Date: Fri, 20 Jun 2003 01:26:51 +0200 From: "Simon L. Nielsen" <simon@nitro.dk> To: Tom Rhodes <trhodes@FreeBSD.org> Cc: jim@FreeBSD.org Subject: Re: RFC: New section for the Unix Basics chapter. Message-ID: <20030619232651.GM408@nitro.dk> In-Reply-To: <20030619180845.157676ec.trhodes@FreeBSD.org> References: <20030619144421.4edd2826.trhodes@FreeBSD.org> <20030619213857.GC408@nitro.dk> <20030619173038.27a8c4fc.trhodes@FreeBSD.org> <20030619215357.GE408@nitro.dk> <20030619180845.157676ec.trhodes@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 2003.06.19 18:08:45 -0400, Tom Rhodes wrote: > On Thu, 19 Jun 2003 23:53:57 +0200 > "Simon L. Nielsen" <simon@nitro.dk> wrote: > > > Just something simple like : > > > > <para>These values are used with the <command>chmod</command> command > > just like before, but with letters. For an example, you could use > > the following command to block other users from accessing <replaceable>FILE</replaceable>: > > > > <screen>&prompt.user;<userinput>chmod go= <replaceable>FILE</replaceable></userinput></screen> > > > > Or something along those lines. > > I usually end with </para> even if I wish to show an example. Last > time I didn't there was a huge gap between the text and example. Yes there should be a close para tag. I was just a bit to fast on the send button. > Gotcha. This is done. I don't see the use in the patch you > sent. The one with spaces after the &prompt.user;, as on the > screen there is no space. That was mainly for consitency, since thats how it's written in all the other examples I have seen in the handbook. -- Simon L. Nielsen [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+8ka78kocFXgPTRwRAh+GAKCV56b0bZ4sQZR4RnYk2fLUIZRXAwCgrzwk BrK4mBZMVEprpocNEXc58CA= =hOfx -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030619232651.GM408>