GENERAL NOTES

This is a server only  version of Samba 2.0.7 for the iPAQ.
Other utilities, documentation and SWAT tool (Samba Web Administrative Tool) 
not specific to the server are not included due to space limitations on the iPAQ.  

Also, only the basic codepage files (codepage.850 and unicode_map.850) 
are included in order to save space.



CONFIGURATION FILE

There is a  simple configuration file in /usr/local/samba/lib/smb.conf,
the purpose of which is to get Samba up and running, and does not
attempt to cover security issues, etc.  


TO GET SAMBA UP AND RUNNING WITH THE INCLUDED smb.conf FILE

1.  Change the name of the workgroup specified in smb.conf to match
whatever workgroup or domain your Windows clients use.

2.  You must run /usr/local/samba/bin/smbpasswd for a Linux username that 
matches a username on the Windows box.  This may mean adding a username
to /etc/passwd.

	/usr/local/samba/bin/smbpasswd -a smith

   This will prompt you for a password - enter the same password that
user smith has on the Windows 98/NT/2000 machine.

3.  This smb.conf file has a read/write share called home to share the /home
directory on the iPAQ.  In order to make it read/write/executable, you must 
either change the permissions on it to 777, or change the ownership of /home
to the Linux/Windows username you are using.


STARTING SAMBA

To manually start the samba server, execute /etc/init.d/samba start
To manually stop the samba server, execute /etc/init.d/samba stop

On the next reboot, the samba server will be started automatically


ADDITIONAL NOTES

If you reboot the iPAQ or restart the Samba server, it may take a while
for the Windows clients to notice as they only do a periodic refresh
of what servers are available.  You may connect successfully to the
Samba server on the iPAQ from a Windows client, reboot the iPAQ or 
restart the Samba server, and then not be able to access the Samba
server from the Windows client.  The solution is to either wait a bit
for Windows to refresh its list of available clients, or reboot the Windows
client when the Sambar server is restarted.

It also may take a minute or so once the iPAQ and Windows clients are both
booted before you can get to the shares on the Samba server, this is again
an issue on the Windows side.
