All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Update to the NFS Howto
@ 2006-06-09  8:52 Chakravarthi P
  2006-06-12 11:03 ` Christopher Smith
  0 siblings, 1 reply; 11+ messages in thread
From: Chakravarthi P @ 2006-06-09  8:52 UTC (permalink / raw)
  To: csmithere, nfs

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

All- 

   we have compiled a README for setting up NFSv4 client
   and server which works well on SLES.
   Can this be inclused as part of nfs-howto
   mentioned here.
   Please look through the attached README

   thanx
   chax.

>>> On 6/5/2006 at 10:30:06 pm, in message
<6AF36215-733E-42C0-9395-B836740E50FB@gmail.com>, "Christopher M. Smith"
<csmithere@gmail.com> wrote:
> All--
> 
> I have put a draft update of the NFS-Howto up on the  
> nfs,sourceforge.net website.  It contains no new content, but  
> encompasses the following changes:
> 
> 1. A slightly different CSS style sheet to enhance its readability.
> 2. It has been updated to DocBook XML v4.2.
> 
> The draft is located here:
> 
> http://nfs.sourceforge.net/nfs-howtov4/ 
> 
> Please let me know if you have any questions or comments.  If I have  
> not heard negative feedback by the end of the week, I will migrate  
> the new content to be the primary version.
> 
> Thank you for your time.
> 
> Best,
> CMS
> --
> Christopher M. Smith
> csmithere@gmail.com 
> 
> 
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/nf 




[-- Attachment #2: README --]
[-- Type: application/octet-stream, Size: 17420 bytes --]

NFSv4 README
Last updated: 09 June 2006

0. Contents:
-----------

1. Overview.
	\___ 1.1 Purpose of this document

2. Quick start

3. Setting up NFSv4 server
	\___ 3.1 Setting up the Configuration files
	|	\___ 3.1.1 /etc/exports
	|	\___ 3.1.2 /etc/sysconfig/nfs
	|	\___ 3.1.3 Idmapd configuration on the server
	\___ 3.2 Starting the services

4.Setting up NFSv4 client
	\___ 4.1 Setting up the Configuration files
	|	\___ 4.1.1 Idmapd configuration on the client
	|	\___ 4.1.2 Mounting the remote exported directories
	\___ 4.2 Starting the services

5.Setting up kerberized NFSv4 server
	\___ 5.1 Prerequisites
	\___ 5.2 Configuring kerberized NFSv4 server
		\___ 5.2.1 Configuring kerberos on your server
		\___ 5.2.2 Create machine credentials for the server
		\___ 5.2.3 Configure /etc/gssapi_mech.conf
		\___ 5.2.4 /etc/exports
		\___ 5.2.5 Starting services

6.Configuring kerberized NFSv4 client
	\___ 6.1 Configuring kerberized NFSv4 client
		\___ 6.1.1 Configuring kerberos on your client
		\___ 6.1.2 Create machine credentials for the client
		\___ 6.1.3 Configure /etc/gssapi_mech.conf
		\___ 6.1.4 Starting services
		\___ 6.1.5 Mounting remote exported directories

7.Troubleshooting
	\___ 7.1 Checklist to ensure NFSv4 is up and running
	\___ 7.2 Checklist to ensure NFSv4 Kerberos is working properly



1. Overview:
------------

The Network File System Version 4 (NFSv4) is a new distributed file system 
similar to previous versions of NFS in its straightforward design, and 
independence of transport protocols and operating systems for file access in a 
heterogeneous network. Unlike earlier versions of NFS, the new protocol 
integrates file locking, strong security, Compound RPCs (combining relevant 
operations), and delegation capabilities to enhance client performance for 
narrow data sharing applications on high-bandwidth networks. NFSv4 
implementations are backward compatible with NFSv2 and NFSv3.
Note: NFSv4 ACLs and krb5p (Kerberos Privacy) are currently not supported

1.1 The Purpose of this document
________________________________

This document is intended as a step-by-step guide to setup NFSv4 on SLES 10. 
It discusses NFSv4 server and client configuration.


2. Quickstart
-------------

For NFSv4 server:
 
1)  Edit /etc/exports to have an entry similar to the one below: 
    /export  *(rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash)
    (i) fsid=0 is a must. 
    (ii) You may want to replace "/export" with your desired exported 
     filesystem path.

2)  Edit /etc/idmapd.conf to modify the default "Domain" to contain your
    DNS domain name.

3)  Execute the following commands to start idmapd and nfsserver
    #/etc/init.d/idmapd start
    #/etc/init.d/nfsserver start
    
For NFSv4 client:

1)  Edit /etc/idmapd.conf to modify the default "Domain" to contain your
    DNS domain name.

2)  Execute the following command to start idmapd.
    #/etc/init.d/idmapd start
	
3)  Mount the exported file system using the following command:
    #mount -t nfs4 <servername>:/ <mntpath>
    Observe that only "/" is given instead of the actual exported path 
    name.


3. Setting up NFSv4 server
--------------------------

3.1 Setting up the Configuration Files
______________________________________

There are three main configuration files you will need to edit to set up an 
NFSv4 server: 
/etc/exports, /etc/sysconfig/nfs and /etc/idmapd.conf.


3.1.1 /etc/exports
==================

This file contains a list of entries; each entry indicates a volume that is
shared and how it is shared. The /etc/exports file format is slightly 
different from previous versions. A sample exports entry looks like this.

/export  *(rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash)

Note that:

i)  NFSv4 needs a separate line for each security mode. 

ii) fsid - The value 0 has a special meaning when use with NFSv4. NFSv4 has a 
    concept of a root of the overall exported filesystem. The export point 
    exported with fsid=0 will be used as this root.
    There must be at least one entry with fsid=0. (this will be pseudo file
    system's /)

iii)The method used to mount multiple exported trees is different. NFSv4 uses 
    the concept of pseudo filesystem to give a single file system view to the 
    client with a pseudo-"/" as root of the filesystem tree. To illustrate,

    Suppose we have
 
    /path1/volume1
    /path2/volume2

    as two filesystem trees on the server that need to be exported, then 
    Firstly, these need to be bound to another name under /export directory 
    using mount command's bind option. This is done as : 
	mount --bind <old dir> /export/<new dir> 
    i.e. in our example:

    	#mount --bind /path1/volume1 /export/volume1
    	#mount --bind /path2/volume2 /export/volume2

    will bind these local filesystem trees to their local new names. 
    Then these two exported filesystems (with their newly bound paths) are 
    entered into /etc/exports with their respective independent options.
    i.e. /etc/exports would contain -

    /export/volume1 *(<options_to_be_filled>)
    /export/volume2 *(<options_to_be_filled>)
    

iv) insecure - The insecure option in this entry also allows clients with NFS 
    implementations that don't use a reserved port for NFS.

All the other export options remains the same as in earlier NFS versions.


3.2.2 /etc/sysconfig/nfs
=========================

/etc/sysconfig/nfs is another NFS server configuration file. Here the number
of kernel threads, NFSv4 support and GSS security (kerberos) for NFS can be 
configured.


3.2.3 Idmapd configuration on the server:
=========================================

idmapd.conf - configuration file for idmapd (idmapping daemon), which does
NFSV4<=>name mapping. Here dns domain (Domain) name has to be configured in 
both client and server.

Sample Configuration file:

==========================================================================

[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = mydomain.com

[Mapping]
Nobody-User = nobody
Nobody-Group = nobody

==========================================================================


3.3 Starting the services:
__________________________

We need to start idmapd and nfsserver.

	#/etc/init.d/idmapd start
	#/etc/init.d/nfsserver start


4. Setting up NFSv4 client
--------------------------

4.1 Setting up the Configuration Files
______________________________________

4.1.1 Idmapd configuration on the client:
=========================================

idmapd.conf - configuration file for idmapd (idmapping daemon), which does
NFSV4<=>name mapping. Here dns domain (Domain) name has to be configured in 
both client and server.

Sample Configuration file:

==========================================================================

[General]
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = mydomain.com

[Mapping]
Nobody-User = nobody
Nobody-Group = nobody

==========================================================================


The format for configuration file i.e. /etc/fstab remains the same.
The configuration file for idmapd remains the same as in server.

4.1.2 Mounting remote exported directories
==========================================

One main difference between previous versions of NFS and NFSv4 is the way in
which mount is invoked. With regard to the pseudofilesystem concept 
sketched above, mount is done as follows:

	#mount -t nfs4 <servername>:/  <mntpath>

	Observe that only '/' is given after the servername.


4.2 Starting the services:
__________________________

We need to start idmapd on the client.

	#/etc/init.d/idmapd start



5. Setting up kerberized NFSv4 server
-------------------------------------

5.1 Prerequisites
_________________

o Key Distribution Center (KDC) must already be set up on the network.
o krb5-1.4.x must be installed on both NFS server and NFS client.
o krb5-devel-1.4.x must be installed on both NFS server and NFS client.
o krb5-client-1.4.x must be installed on both NFS server and NFS client.
o NFS server, client and the KDC server must have their time synchronized.
o NFS_SECURITY_GSS has to be set to "yes" in /etc/sysconfig/nfs in both
  server and client.

5.2 Configuring Kerberized NFSv4 server
_______________________________________

5.2.1 Configure kerberos on your server
=======================================

Edit krb5.conf.
 
Sample configuration

==========================================================================

[libdefaults]

default_realm = MYDOMAIN.COM
dns_lookup_realm = true
dns_lookup_kdc = true

[realms]
MYDOMAIN.COM = {
        kdc = kdcserver.mydomain.com
        admin_server = adminserver.mydomain.com
	default_domain = mydomain.com
      }

[domain_realm]
mydomain.com = MYDOMAIN.COM
.mydomain.com = MYDOMAIN.COM

[logging]
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/log/krb5lib.log

==========================================================================

Replace MYDOMAIN.COM with your REALM, kdcserver.mydomain.com with your KDC 
server, adminserver.mydomain.com with your Admin server & mydomain.com with 
your DNS domain name.

5.2.2 Create machine credentials for the server 
===============================================

This means creating a Kerberos V5 principal/instance name of the form 
nfs/<servername>@REALM, and either adding a key for this principal to 
an existing /etc/krb5.keytab or creating an /etc/krb5.keytab. 

Note: only the encryption type of des-cbc-crc is functional so far in the 
kernel, so add only this type of key. 

kadmin: addprinc -e des-cbc-crc:normal nfs/<servername>@REALM
kadmin: ktadd -e des-cbc-crc:normal -k /tmp/keytab nfs/<servername>@REALM

Now copy the new keytab /tmp/keytab to /etc/krb5.keytab on the server.

5.2.3 Configure /etc/gssapi_mech.conf 
=====================================

This configuration file determines which GSS-API mechanisms the gssd code 
should use. Usually no need to modify this file in 32 bit machines because 
the libraries are installed in /usr/lib. 

Note:
In case of 64 bit machines this has to be modified to /usr/lib64.

Sample configuration

==========================================================================
# GSSAPI Mechanism Definitions
#
# This configuration file determines which GSS-API mechanisms
# the gssd code should use
#
# NOTE:
# The initialization function "mechglue_internal_krb5_init"
# is used for the MIT krb5 gssapi mechanism.  This special
# function name indicates that an internal function should
# be used to determine the entry points for the MIT gssapi
# mechanism functions.
#
# library                               initialization function
# ================================      ==========================
# The MIT K5 gssapi library, use special function for initialization.
/usr/lib/libgssapi_krb5.so     mechglue_internal_krb5_init
#
# The SPKM3 gssapi library function.  Use the function spkm3_gss_initialize.
# /usr/local/gss_mechs/spkm/spkm3/libgssapi_spkm3.so    spkm3_gss_initialize
==========================================================================

5.2.4 /etc/exports
==================

Typical entries for kerberos security mode looks like these:

/export gss/krb5(rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash)
/export gss/krb5i(rw,fsid=0,insecure,no_subtree_check,sync,no_root_squash)


5.2.5 Starting the services
===========================

We need to start svcgssd in addition to idmapd and nfsserver.

	#/etc/init.d/idmapd start
	#/etc/init.d/svcgssd start
	#/etc/init.d/nfsserver start


6. Configuring Kerberized NFSv4 client
--------------------------------------

6.1 Configuring kerberos on your client
_____________________________________

6.1.1 Edit krb5.conf
====================
 
Sample configuration

==========================================================================

[libdefaults]

default_realm = MYDOMAIN.COM
dns_lookup_realm = true
dns_lookup_kdc = true

[realms]
MYDOMAIN.COM = {
        kdc = kdcserver.mydomain.com
        admin_server = adminserver.mydomain.com
	default_domain = mydomain.com
      }

[domain_realm]
mydomain.com = MYDOMAIN.COM
.mydomain.com = MYDOMAIN.COM

[logging]
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/log/krb5lib.log

==========================================================================

Replace MYDOMAIN.COM with your REALM, kdcserver.mydomain.com with your KDC 
server, adminserver.mydomain.com with your Admin server & mydomain.com with 
your DNS domain name.

6.1.2 Create machine credentials for the client
===============================================

This means creating a Kerberos V5 principal/instance name of the form 
nfs/<clientname>@REALM, and either adding a key for this principal to 
an existing /etc/krb5.keytab or creating an /etc/krb5.keytab. 
<clientname> is dns name of the client.

Note: only the encryption type of des-cbc-crc is functional so far in the 
kernel, so add only this type of key. 

kadmin: addprinc -e des-cbc-crc:normal nfs/<clientname>@REALM
kadmin: ktadd -e des-cbc-crc:normal -k /tmp/keytab nfs/<clientname>@REALM

Now copy the new keytab /tmp/keytab to /etc/krb5.keytab on the client.

6.1.3 Configure /etc/gssapi_mech.conf 
=====================================

This configuration file determines which GSS-API mechanisms the gssd code 
should use. Usually no need to modify this file in 32 bit machines because 
the libraries are installed in /usr/lib. 

Note:
In case of 64 bit machines this has to be modified to /usr/lib64.

Sample configuration

==========================================================================
# GSSAPI Mechanism Definitions
#
# This configuration file determines which GSS-API mechanisms
# the gssd code should use
#
# NOTE:
# The initialization function "mechglue_internal_krb5_init"
# is used for the MIT krb5 gssapi mechanism.  This special
# function name indicates that an internal function should
# be used to determine the entry points for the MIT gssapi
# mechanism functions.
#
# library                               initialization function
# ================================      ==========================
# The MIT K5 gssapi library, use special function for initialization.
/usr/lib/libgssapi_krb5.so     mechglue_internal_krb5_init
#
# The SPKM3 gssapi library function.  Use the function spkm3_gss_initialize.
# /usr/local/gss_mechs/spkm/spkm3/libgssapi_spkm3.so    spkm3_gss_initialize
==========================================================================

6.1.4 Starting services
=======================

We need to start gssd in addition to idmapd.

	#/etc/init.d/idmapd start
	#/etc/init.d/gssd start


6.1.5 Mounting exported directories with kerberos
=================================================

To mount a filesystem using krb5, provide the "-osec=krb5" option to mount. 

	#mount -tnfs4 -osec=<secmode> nfsserver:/ /mntpoint

<secmode> can be krb5(Autentication) or krb5i (Integrity).

Note: krb5p (Privacy) is currently not supported.



7. Troubleshooting
-------------------

7.1 Checklist to ensure NFSV4 is up and running 
_______________________________________________

1. ps -ef | grep nfsd
   ps -ef | grep idmapd
   ps -ef | grep svcgssd 
   to check   server side daemons are up and running.

2. ps -ef | grep idmapd
   ps -ef | grep gssd 
   to check client side daemons are up and running

3. rpcinfo -p 
   to check all registered RPC programs (nfs, portmapper, mountd) & versions

4. Check firewall is enabled on server/client from YAST.
   Yast -> Security and Users -> Firewall. 
   Make sure NFS service is enabled.

5. showmount -e <server name>
   to check mount information on NFS server

6. Make sure that one and only one path is exported 
   with fsid=0. 
   Refer Pseudofilesystems (point (iii) in Section 3.2.1) for more information.
  
7. If users are not mapped properly check whether idmapd is running in both 
   server & client and dns domain name is properly configured.

8. If you unable to mount, check for the correctness of the exports file entry.


7.2 Check list to ensure kerberos is working properly 
_____________________________________________________

There are many reasons this could be failing. 

1. Verify that rpc.gssd is running on the client and rpc.svcgssd is running 
   on the server.

2. Verify that your hostnames are correct. The hostname command should return 
   a fully-qualified hostname that has a correct DNS reverse-mapping (either 
   through DNS or the /etc/hosts file). 

3. Verify there is a keytab entry for nfs/<hostname>@REALM in your keytab file 
   (/etc/krb5.keytab). 

4. Verify your Kerberos configuration file has the proper mapping from the DNS 
   hostname to the correct realm. The [domain_realm] section of the 
   /etc/krb5.conf needs to have a mapping from the DNS domain to the correct 
   REALM. 
   For example, if your nfs server's hostname is 'foo.abc.org' and your Kerberos 
   realm name is 'ALPHABET.ORG', then you need an entry like the following in 
   /etc/krb5.conf on the nfs client machine: 
   
   [domain_realm]
   .abc.org = ALPHABET.ORG

5. Verify whether your ticket is not expired or not on the client using klist. If
   it is expired renew using kinit. This must be checked when you find 
   "I/O Error" or "Permission denied" while doing file operations.

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Re: Update to the NFS Howto
@ 2006-07-14 16:43 Salo, Shaunda
  0 siblings, 0 replies; 11+ messages in thread
From: Salo, Shaunda @ 2006-07-14 16:43 UTC (permalink / raw)
  To: Kevin Coffman, Chakravarthi P; +Cc: nfs, Christopher Smith

Please take me off this email list, I believe I'm on it in error.


Thank you

Shaunda Salo
Customer Service Manager
 
 
Flood Processing Center
PO Box 2057
Kalispell, Mt 59903-2057
 
Phone: 888-888-2169 ext 247
Fax: 406-257-5709
Email: Shaunda.Salo@nfsmt.com

-----Original Message-----
From: nfs-bounces@lists.sourceforge.net
[mailto:nfs-bounces@lists.sourceforge.net] On Behalf Of Kevin Coffman
Sent: Friday, July 14, 2006 8:04 AM
To: Chakravarthi P
Cc: nfs@lists.sourceforge.net; Christopher Smith
Subject: Re: [NFS] Update to the NFS Howto

Some quick comments:

The following are more differences between suse and redhat:

suse                                 redhat
---------------------------             ------------------------------
/etc/init.d/nfsserver             /etc/init.d/nfs
/etc/init.d/gssd                   /etc/init.d/rpcgssd
/etc/init.d/svcgssd              /etc/init.d/rpcsvcgssd
/etc/init.d/idmapd               /etc/init.d/rpcidmapd

In /etc/sysconfig/nfs:

NFS_SECURITY_GSS       SECURE_NFS

Leaving off the path entirely in the /etc/gssapi_mech.conf file may be
a work-around for 32/64 compatibility:

# library                               initialization function
# =================      ==========================
# The MIT K5 gssapi library, use special function for initialization.
libgssapi_krb5.so                 mechglue_internal_krb5_init


The other idmapd mapping method is "umich_ldap", not "ldap_umich".

Thanks,
K.C.


On 7/14/06, Chakravarthi P <pchakravarthi@novell.com> wrote:
>
> Cms and all
>
>   there are 3 sections in the attached txt file for addressing 'howto'
> -
>   specific to nfsv4 and kerberos.
>   i have marked a $$$ whenever something mentioned is suse specfic
>   or if it is not specific to NFSv4 but NFS in general.
>   please get back with your comments.
>
> regards,
> chax.
>
>
>
>
> >>> On Mon, Jun 12, 2006 at  7:03 PM, in message
> <2b585fc90606120633n746a8a6ex9d6105c23a872bc3@mail.gmail.com>,
> "Christopher
> Smith" <csmithere@gmail.com> wrote:
> > Chax--
> >
> > Thank you very much for what you have submitted.  A few comments:
> >
> > a) Some of the information tin the README is general to Linux, and
> > applies to all 2.6 implementations.
> > b) Some of the information here applies to SuSE specifically.
> > c) The Kerberos configuration section applies to both NFS Version 3
> as
> > well as NFS Version 4.
> >
> > What I would suggest is we do the following:
> >
> > * Break out the portions that apply specifically to NFS Version 4
> into
> > sections 3 and 4 of the HOWTO for server and client configuration.
> > * Break out the Kerberos documentation you've generated into a
> > subsection of the Security portion of the HOWTO, since it applies to
> > all NFS versions.
> > * Add notation where specific SuSE related configuration is
> required.
> >
> > Either you or I can do this.  Its up to you.
> >
> > Is this acceptable?
> >
> > Best,
> > CMS
> >
> >
>
>
>
>
>
>
>
------------------------------------------------------------------------
-
> Using Tomcat but need to do more? Need to support web services,
security?
> Get stuff done quickly with pre-integrated technology to make your job
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
>
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
>
>
>
>


------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 11+ messages in thread
* Update to the NFS Howto
@ 2006-06-05 17:00 Christopher M. Smith
  0 siblings, 0 replies; 11+ messages in thread
From: Christopher M. Smith @ 2006-06-05 17:00 UTC (permalink / raw)
  To: nfs

All--

I have put a draft update of the NFS-Howto up on the  
nfs,sourceforge.net website.  It contains no new content, but  
encompasses the following changes:

1. A slightly different CSS style sheet to enhance its readability.
2. It has been updated to DocBook XML v4.2.

The draft is located here:

http://nfs.sourceforge.net/nfs-howtov4/

Please let me know if you have any questions or comments.  If I have  
not heard negative feedback by the end of the week, I will migrate  
the new content to be the primary version.

Thank you for your time.

Best,
CMS
--
Christopher M. Smith
csmithere@gmail.com


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-07-18 14:42 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-09  8:52 Update to the NFS Howto Chakravarthi P
2006-06-12 11:03 ` Christopher Smith
2006-06-12 13:33   ` Christopher Smith
2006-06-13 10:22     ` Chakravarthi P
2006-06-13 13:50       ` Christopher Smith
2006-07-14 11:08     ` Chakravarthi P
2006-07-14 14:03       ` Kevin Coffman
2006-07-18 14:06         ` Chakravarthi P
2006-07-18 14:40           ` Christopher Smith
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14 16:43 Salo, Shaunda
2006-06-05 17:00 Christopher M. Smith

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.