Date: Thu, 19 Jun 2003 18:08:45 -0400 From: Tom Rhodes <trhodes@FreeBSD.org> To: "Simon L. Nielsen" <simon@nitro.dk> Cc: jim@FreeBSD.org Subject: Re: RFC: New section for the Unix Basics chapter. Message-ID: <20030619180845.157676ec.trhodes@FreeBSD.org> In-Reply-To: <20030619215357.GE408@nitro.dk> References: <20030619144421.4edd2826.trhodes@FreeBSD.org> <20030619213857.GC408@nitro.dk> <20030619173038.27a8c4fc.trhodes@FreeBSD.org> <20030619215357.GE408@nitro.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Jun 2003 23:53:57 +0200 "Simon L. Nielsen" <simon@nitro.dk> wrote: > On 2003.06.19 17:30:38 -0400, Tom Rhodes wrote: > > On Thu, 19 Jun 2003 23:38:58 +0200 > > "Simon L. Nielsen" <simon@nitro.dk> wrote: > > > > > On 2003.06.19 14:44:21 -0400, Tom Rhodes wrote: > > > > > > [CUT] > > > > + <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 the files > > > > + in your home directory:</para> > > > > + > > > > + <screen>&prompt.user;<userinput>chmod go= *</userinput></screen> > > > > > > I think this is a bad example since it really doesn't prevent others > > > from reading e.g. dotfiles and the directory content. This section is > > > targeting newbies I think it's better not to let them think they can > > > "secure" a directory this way. I think a simple example with some > > > random file would be fine - like the next example. > > > > Have a better one I could use? > > 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. Done. Thanks! > > > > > + <para>A comma separated list can be provided when more than one set > > > > + of changes to a file must be made. For example the following command > > > > + will remove the groups and <quote>world</quote> write permission > > > > > > When referencing world here (which I think is OK) I think "(World)" or > > > something like that should be added group option in the table. > > > > At the time of writing, I couldn't think of a way to phrase it. Help > > on this would be great! > > I think it would be fine if you changed the "All" description in the > table to something like : > > <row> > <entry>(who)</entry> > <entry>a</entry> > <entry>All (<quote>World</quote>)</entry> > </row> > 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. However, I changed the last example to &prompt.user; in place of &prompt.root; for consistency. Thank you! -- Tom Rhodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030619180845.157676ec.trhodes>