[OpenAFS-Doc] Re: [OpenAFS] Quick Start Guide updated for Kerberos v5
Derrick Brashear
shadow@gmail.com
Wed, 28 Nov 2007 23:53:59 -0500
------=_Part_5977_18700542.1196312039171
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Nov 28, 2007 11:03 PM, Russ Allbery <rra@stanford.edu> wrote:
> Jason Edgecombe <jason@rampaginggeek.com> writes:
>
> > chapter1:
> > * about upgrading OS:
> > **Should the namei fileserver be mentioned? Is namei the
> > recommended way?
>
> inode is still recommended for Solaris. namei is recommended in all other
> cases, and generally is the only possible method.
>
Actually, inode also still works on HPUX 11 and IRIX 6.5, and we only do
inode builds for IRIX.
>
> > chapter 2:
> > * getting started on solaris:
> > ** it still mentions copying files from cd-rom (grep for
> "CD-ROM")
>
> Yeah, this needs to get fixed throughout the manual, replaced with
> instructions about how to start from the downloaded binary build or to
> build from source.
>
> > **only mentions solaris 7, it should mention 8, 9 &
> > 10/opensolaris or just say 7 & later versions
>
> Yup.
>
> > ** about fsck: does solaris use inode, namei or both? Is
> > clarification needed?
>
> Solaris can use either, so yes, clarification is needed. I'm fairly sure
> you don't need the custom fsck if you use namei.
>
Correct.
>
> > "The entry for AFS server processes, called either *afs* or
> > *afs//cell/*. No user logs in under this identity, but it is used to
> > encrypt the server tickets that granted to AFS clients for presentation
> > to server processes during mutual authentication."
> >
> > should that be "...that are granted to AFS clients..."?
>
> Yup.
>
> The source for this is in DocBook in the OpenAFS CVS head, and patches are
> certainly welcome.
>
>
------=_Part_5977_18700542.1196312039171
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div class="gmail_quote">On Nov 28, 2007 11:03 PM, Russ Allbery <<a href="mailto:rra@stanford.edu">rra@stanford.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jason Edgecombe <<a href="mailto:jason@rampaginggeek.com">jason@rampaginggeek.com</a>> writes:<br><br>> chapter1:<br>> * about upgrading OS:<br>> **Should the namei fileserver be mentioned? Is namei the
<br>> recommended way?<br><br>inode is still recommended for Solaris. namei is recommended in all other<br>cases, and generally is the only possible method.<br></blockquote><div><br>Actually, inode also still works on HPUX 11 and IRIX
6.5, and we only do inode builds for IRIX.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>> chapter 2:<br>> * getting started on solaris:
<br>> ** it still mentions copying files from cd-rom (grep for "CD-ROM")<br><br>Yeah, this needs to get fixed throughout the manual, replaced with<br>instructions about how to start from the downloaded binary build or to
<br>build from source.<br><br>> **only mentions solaris 7, it should mention 8, 9 &<br>> 10/opensolaris or just say 7 & later versions<br><br>Yup.<br><br>> ** about fsck: does solaris use inode, namei or both? Is
<br>> clarification needed?<br><br>Solaris can use either, so yes, clarification is needed. I'm fairly sure<br>you don't need the custom fsck if you use namei.<br></blockquote><div><br>Correct. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> "The entry for AFS server processes, called either *afs* or<br>> *afs//cell/*. No user logs in under this identity, but it is used to<br>> encrypt the server tickets that granted to AFS clients for presentation
<br>> to server processes during mutual authentication."<br>><br>> should that be "...that are granted to AFS clients..."?<br><br>Yup.<br><br>The source for this is in DocBook in the OpenAFS CVS head, and patches are
<br>certainly welcome.<br><font color="#888888"><br></font></blockquote></div><br>
------=_Part_5977_18700542.1196312039171--