NSLU2-Linux
view · edit · print · history

Optware.Samba History

Hide minor edits - Show changes to markup

February 25, 2010, at 07:24 PM by RobHam -- Samba.conf example modified to give better performance
Added line 210:
	smb ports = 139
Changed lines 215-216 from:
	ldap ssl = no
to:
	kernel oplocks = No
	ldap ssl = No
December 28, 2009, at 06:34 AM by Jim DeLaHunt -- Fix monospace escape for Server comment example
Changed lines 293-294 from:

Samba recognises two special strings. %v will be replaced with the Samba version number. %h will be replaced with the hostname. Thus, a Server comment like Server v will give you basic information about what version of Samba is running on your Slug.

to:

Samba recognises two special strings. %v will be replaced with the Samba version number. %h will be replaced with the hostname. Thus, a Server comment like Server %h with Samba %v will give you basic information about what version of Samba is running on your Slug.

December 28, 2009, at 06:29 AM by Jim DeLaHunt -- Refactor troubleshooting section, add sections for server comment and file modification times
Changed lines 289-292 from:

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

to:

Using server comment to gather version information

The NSLU2 web interface lets you set a "Server comment". This corresponds to the smb.conf parameter "Server string". This string will appear in browse lists next to the machine name.

Samba recognises two special strings. %v will be replaced with the Samba version number. %h will be replaced with the hostname. Thus, a Server comment like Server v will give you basic information about what version of Samba is running on your Slug.

Resolving 'Unable to open printcap file /opt/etc/printcap for read'

Changed lines 345-346 from:

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

to:

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

Changed lines 357-361 from:

Configuring optional features

SWAT (Samba Web Administration Tool)

See the separate SWAT page.

to:

Resolving issue that file modification times aren't preserved when copying files

After a) unslinging my NSLU2 and b) upgrading my Mac OS X machine from Mac OS X 10.3 to 10.5, I noticed that when I copied files from my computer to the NSLU2's share, the modification times for the files were no longer preserved. They were reset to the current time. Also, the touch -t command from the Mac OS X command line to a file on the NSLU2's share failed to set the modtime to the specified value.

Adding a %v to my server comment, I discovered that I was running Samba 3.0.11. I upgraded Samba to the current (as of December 2009) version in ipkg, which was 3.2.15-1. After this, my Mac OS X system preserved modtimes when copying files to the NSLU2's share. Also, the touch -t command now succeeded. -- Jim DeLaHunt?, Vancouver, Canada, December 2009.

Added lines 363-374:

Testimonials

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

Configuring optional features

SWAT (Samba Web Administration Tool)

See the separate SWAT page.

December 28, 2009, at 06:15 AM by Jim DeLaHunt -- Add external link to smb.conf man page, and wikilink to Nano.
Changed lines 90-92 from:

Next, you will need to edit the smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

to:

Next, you will need to edit the smb.conf file so it will work with samba 3.0. The Samba project has a smb.conf man page which explains each of the parameters in detail. It is a useful reference to have while working on the configuration.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

December 28, 2009, at 06:12 AM by Jim DeLaHunt -- Fix external link to smb.conf manpage.
Changed lines 333-334 from:

See [http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#id2535761|the smb.conf man page on bind interfaces only] for details.

to:

See the smb.conf man page on bind interfaces only for details.

December 28, 2009, at 06:11 AM by Jim DeLaHunt -- Change \"bind interfaces =\" to correct \"bind interfaces only = yes\", and give link.
Added line 203:
	bind interfaces only = Yes
Added line 327:

bind interfaces only = Yes

Changed lines 331-334 from:

bind interfaces

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

to:

Further, it seems you MUST have "bind interfaces only = yes" in smb.conf, or else nmbd chokes. You can see the problem by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces only" line.

See [http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#id2535761|the smb.conf man page on bind interfaces only] for details.

December 28, 2009, at 06:00 AM by Jim DeLaHunt -- Remove the SWAT content, and include link in Optional Features section. More refactoring.
Changed lines 41-42 from:

No diversion script is required. However, you lose the ability to modify the configuration via the Linksys web interface. In the future, modify the Samba configuration either by directly editing /opt/etc/samba/smb.conf or via the SWAT web interface.

to:

No diversion script is required. However, you lose the ability to modify the configuration via the Linksys web interface. In the future, modify the Samba configuration either by directly editing /opt/etc/samba/smb.conf or via the SWAT web interface.

Changed line 173 from:

Another second example smb.conf file generated using the Swat utility.

to:

Another second example smb.conf file generated using the SWAT utility.

Changed lines 340-345 from:

SWAT web config tool

See SWAT.

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

to:

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

After upgrading to Samba 3, files created by user A (from a Linux client which mounted the Samba shares via CIFS) suddenly were not writable by user B, even though the configured share permissions gave write access to both users, and this worked flawlessly with Samba 2. This was caused by the following:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions (when mounting as cifs, not smbfs). To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

Changed lines 348-349 from:

ipkg install samba3-swat =]

to:

unix extensions = no =]

Changed lines 352-357 from:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

to:

Configuring optional features

SWAT (Samba Web Administration Tool)

See the separate SWAT page.

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

Changed lines 365-375 from:
  [=
  1. !/bin/sh
  2. Diversion script: /unslung/rc.xinetd
  3. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

return 1

to:
 [=

unix charset = UTF-8 display charset = UTF-8 dos charset = 866

Deleted lines 371-391:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Configuring optional features

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

Deleted lines 393-403:

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

After upgrading to Samba 3, files created by user A (from a Linux client which mounted the Samba shares via CIFS) suddenly were not writable by user B, even though the configured share permissions gave write access to both users, and this worked flawlessly with Samba 2. This was caused by the following:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions (when mounting as cifs, not smbfs). To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2. (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix extensions = no 
 

(:tableend:)

December 28, 2009, at 05:49 AM by Jim DeLaHunt -- Fix wikilink to Optware/SWAT.
Changed lines 342-343 from:

See Optware/SWAT .

to:

See SWAT.

December 28, 2009, at 05:47 AM by Jim DeLaHunt -- Refactor. Prepare to move SWAT to its own page.
Changed lines 88-89 from:

Modifications for Samba 3

to:

smb.conf modifications for Samba 3

Added lines 270-271:

Starting Samba

Added lines 286-287:

Troubleshooting installation and configuration

Changed lines 305-308 from:

SWAT web config tool

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

to:

interfaces configuration (Dec 2008, od3-ripe)

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

Changed lines 312-313 from:

ipkg install samba3-swat =]

to:

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo =]

Changed lines 316-321 from:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

to:

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

interfaces configuration (Samba 3.2, July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

Changed lines 324-334 from:
  [=
  1. !/bin/sh
  2. Diversion script: /unslung/rc.xinetd
  3. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

return 1

to:
 [=

interfaces = 192.168.1.77/24, ixp0, lo

Changed lines 329-338 from:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Notes for Samba 3

interfaces configuration (Dec 2008, od3-ripe)

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

to:

bind interfaces

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

Unable to connect in Samba 3.2.1-1 (9/27/08)

After struggling for days on end to get Samba running in Unslung 6.10 with an NTFS disk on Disk 1, I ran across this: http://www.nabble.com/Can%27t-Get-Upgrade-to-Samba-3.2.x-Working-td19361476.html

Basically, ran "ipkg install gconv-modules" and now my shares are working.

SWAT web config tool

See Optware/SWAT .

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

Changed lines 349-350 from:

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo =]

to:

ipkg install samba3-swat =]

Changed lines 353-359 from:

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

to:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

Changed lines 361-364 from:
 [=

unix charset = UTF-8 display charset = UTF-8 dos charset = 866

to:
  [=
  1. !/bin/sh
  2. Diversion script: /unslung/rc.xinetd
  3. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

return 1

Added lines 375-395:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Configuring optional features

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

Changed lines 402-403 from:

File size >= 2G and remote smbfs mount

to:

File size >= 2G and remote smbfs mount

Deleted lines 428-452:

Notes for Samba 3.2

interfaces configuration (July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

bind interfaces

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

Unable to connect in Samba 3.2.1-1 (9/27/08)

After struggling for days on end to get Samba running in Unslung 6.10 with an NTFS disk on Disk 1, I ran across this: http://www.nabble.com/Can%27t-Get-Upgrade-to-Samba-3.2.x-Working-td19361476.html

Basically, ran "ipkg install gconv-modules" and now my shares are working.

December 28, 2009, at 05:27 AM by Jim DeLaHunt -- Add wikilink for xinetd.
Changed lines 312-313 from:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

to:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

May 25, 2009, at 12:07 PM by Ingo Karkat -- Addendum to note about Samba 3 wrong permissions: cifs mount only.
Changed line 393 from:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions. To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

to:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions (when mounting as cifs, not smbfs). To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

May 25, 2009, at 12:04 PM by Ingo Karkat -- Added note about Samba 3 unix extensions / wrong permissions.
Changed lines 389-394 from:

Notes for Samba 3.2

interfaces configuration (July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

to:

unix extensions / wrong share permissions (Ingo Karkat, 25-May-2009)

After upgrading to Samba 3, files created by user A (from a Linux client which mounted the Samba shares via CIFS) suddenly were not writable by user B, even though the configured share permissions gave write access to both users, and this worked flawlessly with Samba 2. This was caused by the following:

With Unix extensions enabled (by default), a Unix (not Windows!) client can set arbitrary file permissions. To prevent this, one could configure a 'force create mode' + 'force directory mode' on individual shares, but it seems clients would still be allowed to chmod() later on, so this isn't totally watertight. If you don't need these extensions, it is best to turn them off globally, restoring the plain functionality of Samba 2.

Changed line 397 from:

interfaces = 192.168.1.77/24, ixp0, lo

to:

unix extensions = no

Added lines 401-414:

Notes for Samba 3.2

interfaces configuration (July 2008)

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

May 25, 2009, at 11:55 AM by Ingo Karkat -- Restructured Samba 3 and Samba 3.2 notes.
Changed lines 338-341 from:

... Samba 3.2 ...

to:

Notes for Samba 3

interfaces configuration (Dec 2008, od3-ripe)

Changed lines 353-357 from:

Dec 2008 (od3-ripe)

International character support or Unicode support

to:

International character support or Unicode support

Changed lines 373-374 from:

File size >= 2G and remote smbfs mount

to:

File size >= 2G and remote smbfs mount

Changed lines 389-390 from:

Samba 3.2.0

to:

Notes for Samba 3.2

interfaces configuration (July 2008)

Changed lines 402-404 from:

July 2008

... Samba 3.2 ...

to:

bind interfaces

Changed lines 406-407 from:

Unable to connect in Samba 3.2.1-1 (9/27/08)

to:

Unable to connect in Samba 3.2.1-1 (9/27/08)

May 19, 2009, at 09:01 AM by Ingo Karkat -- Re-wrote and clarified Samba configuration options: Either break symlink or use diversion script.
Changed lines 32-37 from:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

 An example smb.conf file that works is:
to:

Samba configuration (smb.conf, smbpasswd)

If you've done the copying of the Samba 2 configuration to the new Samba 3 directory, you will find that /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/. After each reboot, the smb.conf and smbpasswd files in /share/hdd/conf/share/ are overwritten; files residing directly in /opt/etc/samba/ are not.

Samba 3 will read its configuration from /opt/etc/samba/, but the Linksys web interface will modify the Samba configuration in /share/hdd/conf/share/. This leaves the following options:

Option A: Remove the symlinks.

No diversion script is required. However, you lose the ability to modify the configuration via the Linksys web interface. In the future, modify the Samba configuration either by directly editing /opt/etc/samba/smb.conf or via the SWAT web interface.

To remove the symlinks, execute the following commands:

Added lines 46-75:
  
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .
 

(:tableend:)

then update the /opt/etc/samba/smb.conf for Samba 3 as shown in the next section.

Option B: Diversion script.

When rebooting the system the symlinked smb.conf and smbpasswd will be overwritten with the original Samba 2 version. To keep the Samba 3 files, you need a copy of them in a location where they will not be touched. The best spot for this is /unslung/

First, copy the original files to /unslung/: (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

  
cp /share/hdd/conf/share/smb.conf /unslung/
cp /share/hdd/conf/share/smbpasswd /unslung/
 

(:tableend:)

You will need to remove the link to the old file and point to the new file with a diversion script.

rc.samba (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

Added lines 77-98:
  1. !/bin/sh

ln -sf /unslung/smb.conf /opt/etc/samba/smb.conf ln -sf /unslung/smb.conf /etc/samba/smb.conf ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd ln -sf /unslung/smbpasswd /etc/samba/smbpasswd return 1 =] (:tableend:)

This should allow you to fully use the Linksys web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

Modifications for Samba 3

Next, you will need to edit the smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

 An example smb.conf file that works is:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
Added lines 161-172:

Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

(:tableend:)


Changed lines 301-305 from:

Diversion script

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on... You have to set a diversion script in /unslung Create a file rc.samba to include the below

to:

SWAT web config tool

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

Changed lines 308-318 from:
  1. ! /bin/sh
  2. Diversion script: customize before starting crond
  3. Make sure we have a backup copy of /etc/samba/smb.conf

if [ ! -e /etc/samba/smb.conf.orig ]; then

  cp -p /etc/samba/smb.conf  /etc/samba/smb.conf.orig 

fi

return 1

to:

ipkg install samba3-swat

Changed lines 312-318 from:

Alternate Update Method

When rebooting the system the file smb.conf will be overwritten with the original samba 2 version. To keep the version 3 file, you need a copy of it in a location where it will not be touched. The best spot for this is /unslung Once you have created your smb.conf, you will need to remove the link to the old file and and point to the new file with a diversion script.

rc.samba

to:

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

Changed line 320 from:
 [=
to:
  [=
Changed lines 322-323 from:

ln -sf /unslung/smb.conf /opt/etc/samba/smb.conf ln -sf /unslung/smb.conf /etc/samba/smb.conf

to:
  1. Diversion script: /unslung/rc.xinetd
  2. Customize for your own use, do not delete your original content!

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then

  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf

fi

Changed line 331 from:

=]

to:

=]

Changed lines 334-346 from:

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

Alternate update method 2

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

  • /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
  • links in /opt/etc/samba/ are never overwritten
  • only files in /share/hdd/conf/share/ are overwritten at each boot

No script is required (that's why I think it's easier than writing a diversion script). Just type the following commands :

to:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

... Samba 3.2 ...

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

Changed lines 343-348 from:
  [=

cd /opt/etc/samba rm smb.conf rm smbpasswd cp /share/hdd/conf/share/smb.conf . cp /share/hdd/conf/share/smbpasswd .

to:
 [=

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo

Changed lines 348-359 from:

and then only I update the /opt/etc/samba/smb.cong file as shown below.


Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.


Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

to:

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

Dec 2008 (od3-ripe)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

Changed lines 361-362 from:

host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1. =]

to:

unix charset = UTF-8 display charset = UTF-8 dos charset = 866 =]

Changed lines 367-378 from:

Alternate update method 3

I created the smb.conf file in /opt/etc/samba and started the slug. There was no need for a diversion script. Running Unslung 6.8 and samba 3.0.25a


If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

(rc.samba):

to:

I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3): unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1 I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

File size >= 2G and remote smbfs mount

When mounting smbfs the default does not include large file support, which limits files to less than 2 gigs. Using the lfs option will include large file support. Google "smbfs lfs option", since it seems to be missing from most documentation.

A better option is to use cifs, if it's supported by your kernel/distribution/version. When mounting cifs, large files are supported by default.

So either : mount -t smbfs //server/share /mountpoint -o lfs other-options or mount -t cifs //server/share /mountpoint -o options

Samba 3.2.0

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

Changed lines 396-398 from:

ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd ln -sf /unslung/smbpasswd /etc/samba/smbpasswd =]

to:

interfaces = 192.168.1.77/24, ixp0, lo =]

Changed lines 400-436 from:

SAMBA web config tool

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ipkg install samba3-swat

(:tableend:)

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

  
#!/bin/sh
# Diversion script: /unslung/rc.xinetd
# Customize for your own use, do not delete your original content!
#

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then
  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf
fi

return 1
 

(:tableend:)

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

to:

July 2008

Deleted lines 402-465:

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo
 

(:tableend:)

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

Dec 2008 (od3-ripe)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3): unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1 I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

File size >= 2G and remote smbfs mount

When mounting smbfs the default does not include large file support, which limits files to less than 2 gigs. Using the lfs option will include large file support. Google "smbfs lfs option", since it seems to be missing from most documentation.

A better option is to use cifs, if it's supported by your kernel/distribution/version. When mounting cifs, large files are supported by default.

So either : mount -t smbfs //server/share /mountpoint -o lfs other-options or mount -t cifs //server/share /mountpoint -o options

Samba 3.2.0

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

July 2008

... Samba 3.2 ...

May 19, 2009, at 08:19 AM by Ingo Karkat -- Updated SWAT instructions; now, a separate package must be installed.
Changed lines 335-340 from:

If you want to enable SWAT, the Samba web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

to:

SWAT (the Samba web config tool) used to be included in the samba package, but has been moved into a separate samba3-swat package, which has a dependency on the xinetd package:

Added lines 339-351:
 
ipkg install samba3-swat

(:tableend:)

Edit your rc.xinetd diversion script to register SWAT with xinetd. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

Changed lines 368-369 from:

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

to:

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! (To be exact, the full control depends on the SWAT user having write access to /opt/etc/samba/smb.conf, so you can grant non-root users full control by changing this file's owner or access permissions.) A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

May 19, 2009, at 08:05 AM by Ingo Karkat -- Corrected messed up table.
Added line 197:

=]

May 19, 2009, at 08:03 AM by Ingo Karkat -- Updated instructions to activate Samba in S08samba.
Changed lines 185-186 from:

Finally, edit /opt/etc/init.d/S08samba, remove comments:

to:

Finally, edit /opt/etc/init.d/S08samba to activate Samba:

Changed lines 192-210 from:
  1. please remove '#' to activate the start script.

if [ -n "`pidof smbd`" ] ; then

   echo "Stopping smbd:"
   killall smbd

fi

if [ -n "`pidof nmbd`" ] ; then

   echo "Stopping nmbd:"
   killall nmbd

fi

sleep 2

echo "Starting nmbd:"

 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;

echo "Starting smbd:"

 /opt/sbin/smbd -D --configfile=/opt/etc/samba/smb.conf;

=]

to:
  1. set samba_active=1 to activate samba

samba_active=1

[ 1 = $samba_active ] || exit 0 ...

May 19, 2009, at 07:59 AM by Ingo Karkat -- Updated assumptions. Corrected copy command.
Changed line 6 from:
  • You have unslung to the first disk drive (sda1)
to:
  • You have unslung to the first disk drive (sda1) or to a flash drive in port 2 (sda2)
Deleted lines 9-10:

I've not tested any of this on pre 4.2 releases.

Changed line 26 from:

cp -pR /etc/samba /opt/etc/samba

to:

cp -pR /etc/samba /opt/etc

Deleted lines 31-32:

[On Unslung the command should be cp -pR /etc/samba /opt/etc]

December 21, 2008, at 04:51 PM by od3-ripe -- added hint to add 127.0.0.1 to have SWAT working again
Changed lines 378-382 from:

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients

to:

... Samba 3.2 ...

For me on unslung SWAT started reporting smbd/nmbd "not running" though they actually did. Took me some time to figure out what fixes this behavior. After adding also "localhost" to:

Changed lines 384-386 from:

unix charset = UTF-8 display charset = UTF-8 dos charset = 866

to:

interfaces = 127.0.01/24, <myEth-IP>, ixp0, lo

Added lines 388-406:

it works, again. (Also see note about adding <myEth-IP> below - looks like "ipx0" and "lo" no longer get properly translated!?)

Dec 2008 (od3-ripe)

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

November 11, 2008, at 02:23 PM by lizardcry -- bind interfaces required
Added lines 427-429:

... Samba 3.2 ...

Further, it seems you MUST have "bind interfaces = ixp0" or else nmbd chokes. You can see it by starting nmbd in interactive mode: "nmbd -i -d 5". nmbd cannot find the interface unless you ALSO include the "bind interfaces" line.

October 25, 2008, at 09:19 PM by Ralph Finch --
Added line 33:
October 25, 2008, at 09:18 PM by Ralph Finch --
Changed lines 33-34 from:
to:

[On Unslung the command should be cp -pR /etc/samba /opt/etc]

October 15, 2008, at 05:11 AM by bitbucket --
Changed line 427 from:

After struggling for days on end to get Samba running in Unslung 6.10, I ran across this:

to:

After struggling for days on end to get Samba running in Unslung 6.10 with an NTFS disk on Disk 1, I ran across this:

September 28, 2008, at 07:09 AM by bitbucket --
Added lines 424-430:

Unable to connect in Samba 3.2.1-1 (9/27/08)

After struggling for days on end to get Samba running in Unslung 6.10, I ran across this: http://www.nabble.com/Can%27t-Get-Upgrade-to-Samba-3.2.x-Working-td19361476.html

Basically, ran "ipkg install gconv-modules" and now my shares are working.

September 26, 2008, at 04:14 AM by colin gebhart -- an error and some advice
Changed line 28 from:

cp -pR /etc/samba /opt/etc

to:

cp -pR /etc/samba /opt/etc/samba

Added lines 122-123:

I recommend using the below conf file, change your workgroup name, the interface IP to your NSLU2 IP, hosts allow to your client IP range, don't use the Admin1 or Disk1 sections here. Instead copy only those 2 sections out of your old version 2 smb.conf file. If you do this, you should see the same shares behavior out of your Samba 3 install as you saw from Samba 2

September 11, 2008, at 08:31 PM by RobHam -- working smb.conf file example updated - produced by Swat - including description
Changed lines 118-121 from:

Notes - for Debain firmware, change the interfaces line to interfaces = eth0, lo

For non-unslung firmware, like openwrt, you need to change guest account = nobody and force group = nobody.

to:

For non-unslung firmware, like openwrt, you need to change guest account = nobody and force group = nogroup.

September 11, 2008, at 08:10 PM by RobHam -- working smb.conf file example updated - produced by Swat - including description
Changed lines 108-109 from:

The file is configured with three accessible shares. A users 'home' folder, a 'public' folder which can be accessed by any connecting client using netbios, and 'read only' access to the full NSLU-2 directory structure.

to:

The file is configured with three accessible shares. 1. A users 'home' folder, 2. a 'public' folder which can be accessed by any connecting client using netbios, and 3. 'read only' access to the full NSLU-2 directory structure.

Changed lines 112-115 from:

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (for security they are non browseable).

Mapping example using the NSLU-2 netbios name - \\netbios_name-goes_here\ADMIN 1

to:

A users 'home' folder and read only access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (for security they are non browseable).

Mapping example using the NSLU-2 netbios name - \\netbios_name_goes_here\ADMIN 1

Changed lines 118-119 from:

Notes - for Debain firmware change the interfaces line to interfaces = eth0, lo

to:

Notes - for Debain firmware, change the interfaces line to interfaces = eth0, lo

September 11, 2008, at 08:03 PM by RobHam -- working smb.conf file example updated - produced by Swat - including description
Changed lines 112-113 from:

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browseable for security).

to:

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (for security they are non browseable).

Changed lines 118-123 from:

Note - for Debain firmware change the interfaces line to interfaces = eth0, lo

Also note - for non-unslung firmware, like openwrt, you need to change 'guest account = nobody' and 'force group = nobody'.

Note the directory /opt/var/spool/samba may need to be created and flagged chmod 755.

to:

Notes - for Debain firmware change the interfaces line to interfaces = eth0, lo

For non-unslung firmware, like openwrt, you need to change guest account = nobody and force group = nobody.

The directory /opt/var/spool/samba may need to be created and flagged chmod 755 (there may be other Samba working directories missing).

Changed line 154 from:
	comment = Home Directories
to:
	comment = Users Home Directories
Changed line 163 from:
	comment = All Printers
to:
	comment = Print Spooler Directory
September 11, 2008, at 07:52 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 108-117 from:

The file is configured with three accessible shares. A users home folder. A public folder which can be accessed by any connection using netbios. And read only access to the full NSLU-2 directory structure

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible if the user name and password are identical on both the server and client.

A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browsable).

Mapping example using the NSLU-2 netbios name \\netbios_name-goes_here\ADMIN 1

Another example using the NSLU-2 IP address \\192.168.1.77\user_name_goes_here

to:

The file is configured with three accessible shares. A users 'home' folder, a 'public' folder which can be accessed by any connecting client using netbios, and 'read only' access to the full NSLU-2 directory structure.

The file configures Samba in 'User' mode. In this mode, a users 'home' folder is only accessible if the 'user name' and 'password' are identical on both the server and client.

A users 'home' folder and 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browseable for security).

Mapping example using the NSLU-2 netbios name - \\netbios_name-goes_here\ADMIN 1

Mapping example using the NSLU-2 IP address - \\192.168.1.77\user_name_goes_here

Changed lines 120-121 from:

Also note - for non-unslung firmware, like openwrt, you need to change guest account=nobody from guest

to:

Also note - for non-unslung firmware, like openwrt, you need to change 'guest account = nobody' and 'force group = nobody'.

Note the directory /opt/var/spool/samba may need to be created and flagged chmod 755.

September 11, 2008, at 07:40 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 107-108 from:

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible by a named user if the user name and password are identical on both the server and client. Incorrect user names or passwords will only have access to the public folder tree. A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client - examples \\NSLU2\ADMIN 1 - \\192.168.1.77\user_name_goes_here

to:

The file is configured with three accessible shares. A users home folder. A public folder which can be accessed by any connection using netbios. And read only access to the full NSLU-2 directory structure

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible if the user name and password are identical on both the server and client.

A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client (they are non browsable).

Mapping example using the NSLU-2 netbios name \\netbios_name-goes_here\ADMIN 1

Another example using the NSLU-2 IP address \\192.168.1.77\user_name_goes_here

September 11, 2008, at 07:27 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 107-108 from:
to:

The file configures Samba in 'User' mode. In this mode, a users home folder is only accessible by a named user if the user name and password are identical on both the server and client. Incorrect user names or passwords will only have access to the public folder tree. A users home folder and also 'read only' access to the full Linux directory tree 'ADMIN 1' are only accessible by using mapping on the client - examples \\NSLU2\ADMIN 1 - \\192.168.1.77\user_name_goes_here

Changed line 167 from:
	path = /public/
to:
	path = /public
September 11, 2008, at 04:40 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 148-149 from:
to:
	browseable = No
Added line 169:
	force group = everyone
September 10, 2008, at 11:39 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 148-149 from:
	browseable = No
to:
September 10, 2008, at 11:30 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed lines 162-163 from:
to:
	browseable = No
September 10, 2008, at 11:18 PM by RobHam -- working smb.conf file example updated - produced by Swat
Added line 145:
	read only = No
September 10, 2008, at 10:59 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed line 123 from:
        security = SHARE
to:
        security = USER
September 10, 2008, at 10:00 PM by RobHam -- working smb.conf file example updated - produced by Swat
Changed line 143 from:
	path = /%u
to:
	path = /%S
September 10, 2008, at 09:38 PM by RobHam -- working smb.conf file example updated - produced by Swat
Added line 143:
	path = /%u
September 10, 2008, at 09:00 PM by RobHam -- working smb.conf file example updated - produced by Swat
Added line 135:
	invalid users = root
September 10, 2008, at 08:13 PM by RobHam -- working smb.conf file example produced by Swat updated
Changed lines 106-107 from:

Optimised for Unslung firmware (added by RobHam Sept 2007).

to:

Optimised for Unslung firmware (added by RobHam Sept 2007 + Mod Sept 2008).

Changed lines 116-118 from:
  1. from 192.168.2.50 (192.168.2.50)
  2. Date: 2007/09/25 20:35:19
to:
  1. from 192.168.1.50 (192.168.1.50)
  2. Date: 2008/09/10 21:01:20
Changed lines 123-124 from:
	map to guest = Bad User
to:
        security = SHARE
	map to guest = Bad Password
Deleted line 131:
	printcap name = /opt/etc/printcap
Deleted lines 134-135:
	lock directory = /var/samba3
	pid directory = /var/samba3
Added lines 140-153:

[homes]

	comment = Home Directories
	valid users = %S
	create mask = 0700
	directory mask = 0700
	browseable = No

[printers]

	comment = All Printers
	path = /opt/var/spool/samba
	create mask = 0700
	printable = Yes
	browseable = No
July 10, 2008, at 09:47 PM by RobHam -- Note added regarding the missing printcap file
Changed line 121 from:
	server string = Samba %v Network Drive
to:
	server string = %h Server
Deleted line 122:
	bind interfaces only = Yes
Changed lines 140-141 from:
	hosts allow = 192.168., 172., 10., localhost
to:
	hosts allow = 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8, localhost
Changed line 394 from:

RobHam July 2008

to:

July 2008

July 10, 2008, at 06:51 PM by RobHam -- Note added regarding the missing printcap file
Changed line 122 from:
	interfaces = ixp0, lo
to:
	interfaces = 192.168.1.77/24, ixp0, lo
Changed lines 203-204 from:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

to:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

Note that some users have reported seeing messages in the Samba error logs similar to 'Unable to open printcap file /opt/etc/printcap for read'. This is probably because Samba is trying to open a nonexistant file. Easily fixed by logging in as user 'root' at a console screen and then check if the file exists. If not, create a blank file using the two commands:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
touch /opt/etc/printcap
chmod 0644 /opt/etc/printcap

(:tableend:)

July 06, 2008, at 06:33 PM by RobHam -- Note regarding Samba 3.2.0 added
Changed lines 372-385 from:

mount -t cifs //server/share /mountpoint -o options

to:

mount -t cifs //server/share /mountpoint -o options

Samba 3.2.0

This version of Samba seems to need an IP/mask pair added to the 'interfaces' config line in the 'Global' section to work properly with Unslung firmware. A typical config line (assuming the default NSLU2 IP address) is:-

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
interfaces = 192.168.1.77/24, ixp0, lo
 

(:tableend:)

RobHam July 2008

May 21, 2008, at 01:50 PM by Søren Bech Christensen -- Removed statement posted earlier
Deleted lines 357-358:

I found that using one charset for unix and another for display messes things up. If you access the same files from windows as you publish e.g. on your web server, they look differently. I now use ISO-8859-1 for unix charset as well as display charset. Works fine for danish characters.

May 21, 2008, at 12:02 PM by Søren Bech Christensen -- Same national filenames on windows and web
Changed lines 358-359 from:
to:

I found that using one charset for unix and another for display messes things up. If you access the same files from windows as you publish e.g. on your web server, they look differently. I now use ISO-8859-1 for unix charset as well as display charset. Works fine for danish characters.

March 05, 2008, at 12:42 AM by hzheng --
Added line 109:
March 05, 2008, at 12:41 AM by hzheng --
Changed lines 109-110 from:
to:

Also note - for non-unslung firmware, like openwrt, you need to change guest account=nobody from guest

September 25, 2007, at 07:53 PM by RobHam -- A Second example smb.conf file added
Changed line 143 from:
	path = /share/hdd/data/
to:
	path = /
Changed line 149 from:
	path = /share/hdd/data/public/
to:
	path = /public/
September 25, 2007, at 07:45 PM by RobHam -- A Second example smb.conf file added
Changed lines 105-107 from:
 Another second example smb.conf file generated using the Swat utility.

Optimised for Unslung firmware (added by RobHam? Sept 2007).

to:

Another second example smb.conf file generated using the Swat utility. Optimised for Unslung firmware (added by RobHam Sept 2007).

Note - for Debain firmware change the interfaces line to interfaces = eth0, lo

September 25, 2007, at 07:42 PM by RobHam -- A Second example smb.conf file added
Changed lines 105-106 from:
 Another example smb.conf file generated using the Swat utility,  optimised for Unslung firmware (added by RobHam? Sept 2007).
to:
 Another second example smb.conf file generated using the Swat utility.

Optimised for Unslung firmware (added by RobHam? Sept 2007).

Changed line 269 from:

to:

Changed line 274 from:

to:

Changed line 292 from:

to:

September 25, 2007, at 07:39 PM by RobHam -- A Second example smb.conf file added
Changed lines 105-106 from:

Finally, edit /opt/etc/init.d/S08samba, remove comments:

to:
 Another example smb.conf file generated using the Swat utility,  optimised for Unslung firmware (added by RobHam? Sept 2007).
Added lines 110-158:
  1. Samba config file created using SWAT
  2. from 192.168.2.50 (192.168.2.50)
  3. Date: 2007/09/25 20:35:19

[global]

	workgroup = MSHOME
	server string = Samba %v Network Drive
	interfaces = ixp0, lo
	bind interfaces only = Yes
	map to guest = Bad User
	null passwords = Yes
	guest account = guest
	log file = /opt/var/samba/log.%m
	max log size = 10
	name resolve order = wins bcast
	socket options = SO_SNDBUF=8192 SO_RCVBUF=8192
	load printers = No
	printcap name = /opt/etc/printcap
	dns proxy = No
	ldap ssl = no
	config file = /opt/etc/samba/smb.conf
	lock directory = /var/samba3
	pid directory = /var/samba3
	create mask = 0771
	force create mode = 0660
	force directory mode = 0771
	hosts allow = 192.168., 172., 10., localhost

[ADMIN 1]

	comment = Full Data Partition
	path = /share/hdd/data/
	valid users = @administrators
	write list = @administrators

[DISK 1]

	comment = Public Folder Tree For Everyone
	path = /share/hdd/data/public/
	valid users = @administrators, @everyone
	write list = @administrators, @everyone
	read only = No
	guest ok = Yes

=] (:tableend:)

Finally, edit /opt/etc/init.d/S08samba, remove comments:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
August 17, 2007, at 06:29 PM by Jeffrey Gao -- delete incorrect comment of myself
Changed lines 304-307 from:

<added on Aug 17 2007> I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipkg upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8 display charset = UTF-8 dos charset = UTF-8)

to:
August 17, 2007, at 05:55 PM by Jeffrey Gao --
Changed line 305 from:

I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipke upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8

to:

I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipkg upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8

August 17, 2007, at 05:53 PM by Jeffrey Gao --
Added line 304:

<added on Aug 17 2007>

August 17, 2007, at 05:51 PM by Jeffrey Gao -- Samba 3.0.25b-1 can not show UTF-8 code
Changed lines 304-306 from:
to:

I use UTF-8 showing file's name in Chinese and it works fine until today. After I did the "ipke upgrade" my samba become version 3.0.25b-1. All the shares are works but it can not show Chinese char! I checked smb.conf and it was the same as before(i.e. unix charset = UTF-8 display charset = UTF-8 dos charset = UTF-8)

June 16, 2007, at 08:04 PM by amichelf --
Changed lines 236-241 from:
to:

Alternate update method 3

I created the smb.conf file in /opt/etc/samba and started the slug. There was no need for a diversion script. Running Unslung 6.8 and samba 3.0.25a

May 28, 2007, at 09:58 AM by xypron -- !!! Alternate Update Method: Return 1
Changed line 189 from:

return 0

to:

return 1

March 27, 2007, at 10:27 PM by RobHam -- References to S80samba changed to S08samba to match optware package
Changed lines 287-288 from:

unix charset = UTF-8 display charset = UTF-8

to:

unix charset = UTF-8 display charset = UTF-8

March 27, 2007, at 10:25 PM by RobHam -- References to S80samba changed to S08samba to match optware package
Changed lines 32-33 from:

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

to:

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

Changed line 36 from:

If you're new to Linux editors, the vi editor which comes standard with UnSlung? is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

to:

If you're new to Linux editors, the vi editor which comes standard with UnSlung is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

Changed lines 287-288 from:

unix charset = UTF-8 display charset = UTF-8

to:

unix charset = UTF-8 display charset = UTF-8

Changed lines 294-296 from:

unix charset = UTF-8 dos charset = CP850? display charset = ISO-8859-1

to:

unix charset = UTF-8 dos charset = CP850 display charset = ISO-8859-1

March 27, 2007, at 10:19 PM by RobHam -- References to S80samba changed to S08samba to match optware package
Changed lines 105-106 from:

Finally, edit /opt/etc/init.d/S80samba, remove comments:

to:

Finally, edit /opt/etc/init.d/S08samba, remove comments:

Added lines 126-127:

echo "Starting nmbd:"

 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;
Deleted lines 129-130:

echo "Starting nmbd:"

 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;
Changed line 139 from:

./S80samba

to:

./S08samba

Changed lines 149-150 from:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. Then restart. That's all.

to:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S08samba. Then restart. That's all.

March 17, 2007, at 07:08 AM by vatachnio -- Add mention of nano editor as alternative to vi
Changed lines 34-36 from:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics.

Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2 - being a non-*nix user I found vi to be extremely unfriendly and a steep learning curve for a "one off job".

to:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0.

If you're new to Linux editors, the vi editor which comes standard with UnSlung? is very unfriendly (google "vi" to learn the basics). The nano editor ("ipkg install nano") is much more intuitive. Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2.

March 09, 2007, at 01:30 PM by Vegard HB --
Changed line 293 from:

I use these settings for support of Norwegian and Portugeese characters in filenames:

to:

I use these settings for support of Norwegian and Portugeese characters in filenames under Unslung 6.8 (samba 3):

Changed lines 297-300 from:

I wanted support for the Norwegian ø/Ø and Portugese characters under Unslung 6.8 (samba 3). So I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

to:

I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

March 09, 2007, at 01:29 PM by Vegard HB -- Norwegian and other international characters
Added lines 293-300:

I use these settings for support of Norwegian and Portugeese characters in filenames: unix charset = UTF-8 dos charset = CP850? display charset = ISO-8859-1

I wanted support for the Norwegian ø/Ø and Portugese characters under Unslung 6.8 (samba 3). So I put these settings into /unslung/smb.conf and put the rc.samba in the same directory (comment away the first line). You also have to change the config file name in /unslung/smb.conf.

October 22, 2006, at 03:00 PM by EgorKobylkincom -- Cyrillic Russian support for Windows XP clients
Added lines 283-292:

Here is what you should add to [global] section of the smb.conf for Samba 3.X.X to enable Cyrillic (Russian) support for Windows XP clients (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
unix charset = UTF-8
display charset = UTF-8
dos charset = 866
 

(:tableend:)

September 12, 2006, at 08:55 PM by BrianZhou -- LFS
Changed lines 1-2 from:

Installing Samba 3.0.14a-4 on Unslung 4.2x beta or later

to:

Installing Samba >=3.0.14a-4 on Unslung 4.2x beta or later

Changed lines 283-284 from:

---

to:

File size >= 2G and remote smbfs mount

September 12, 2006, at 08:42 PM by BrianZhou -- Added smbfs -o lfs
Changed lines 281-296 from:

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

to:

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

--- When mounting smbfs the default does not include large file support, which limits files to less than 2 gigs. Using the lfs option will include large file support. Google "smbfs lfs option", since it seems to be missing from most documentation.

A better option is to use cifs, if it's supported by your kernel/distribution/version. When mounting cifs, large files are supported by default.

So either : mount -t smbfs //server/share /mountpoint -o lfs other-options or mount -t cifs //server/share /mountpoint -o options

May 21, 2006, at 02:26 PM by Peter Brown --
Changed lines 34-35 from:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics. An example smb.conf file that works is:

to:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics.

Alternatively use your favourite editor on your favourite operating system and ftp the resulting file to the nslu2 - being a non-*nix user I found vi to be extremely unfriendly and a steep learning curve for a "one off job".

 An example smb.conf file that works is:
February 28, 2006, at 04:59 AM by frankvh -- spelling
Changed lines 145-146 from:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. That's all.

to:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. Then restart. That's all.

February 28, 2006, at 04:56 AM by frankvh -- Diversion scripts etc no longer required
Changed lines 34-35 from:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

to:

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. If you're new to Linux editors the vi editor comes standard with UnSlung?; google "vi" to learn the basics. An example smb.conf file that works is:

Changed lines 139-140 from:

If all goes well, the stock samba will stop and your new samba will start.

to:

If all goes well, the stock samba will stop and your new samba will start. Don't be suprised if running a "ps" shows two smbd & nmbd tasks, compared to one each previously. This is normal.

Added lines 145-146:

From FVH: On my setup (Unslung 5.5 with Samba 3.0.21) the following diversion scripts / update tricks were not required. Samba 3 functions correctly after reboots. Getting Samba 3 running was literally as simple as: ipkg update ; ipkg install samba ; create /opt/etc/samba/smb.conf ; edit /opt/etc/init.d/S80samba. That's all.

Changed lines 150-152 from:

Diversion sript

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

to:

Diversion script

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

December 11, 2005, at 03:13 AM by ST -- smb.conf: corrected usermap entry (default: username map = )
Changed line 72 from:

username map = no

to:

username map =

December 10, 2005, at 03:36 PM by Eiffel -- added --configfile=/opt/etc/samba/smb.conf; (Tip from CapLink
Changed line 123 from:
 /opt/sbin/smbd -D;
to:
 /opt/sbin/smbd -D --configfile=/opt/etc/samba/smb.conf;
Changed line 125 from:
 /opt/sbin/nmbd -D;
to:
 /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf;
October 22, 2005, at 02:56 PM by JNC --
Changed lines 198-199 from:

That's why I used the following commands that brought me satisfaction :

to:

No script is required (that's why I think it's easier than writing a diversion script). Just type the following commands :

October 22, 2005, at 02:54 PM by JNC --
Changed lines 147-150 from:

If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

to:

Diversion sript

You will find that the smb.conf file does stick and revert to orginal during a turn off/turn on...

Changed lines 190-191 from:

Alternate and simplier method

to:

Alternate update method 2

October 22, 2005, at 02:51 PM by JNC --
Changed lines 186-195 from:

Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.


Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

to:

Alternate and simplier method

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

  • /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
  • links in /opt/etc/samba/ are never overwritten
  • only files in /share/hdd/conf/share/ are overwritten at each boot

That's why I used the following commands that brought me satisfaction :

Changed lines 198-200 from:
 
host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

to:
  
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .
 
Changed lines 207-213 from:

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

(rc.samba):

to:

and then only I update the /opt/etc/samba/smb.cong file as shown below.


Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.


Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

Changed lines 222-223 from:

ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd ln -sf /unslung/smbpasswd /etc/samba/smbpasswd

to:

host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

Added lines 226-240:

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

(rc.samba): (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd
ln -sf /unslung/smbpasswd /etc/samba/smbpasswd

(:tableend:)

Changed lines 271-291 from:

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

Alternate and simplier method

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

  • /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
  • links in /opt/etc/samba/ are never overwritten
  • only files in /share/hdd/conf/share/ are overwritten at each boot

That's why I used the following commands that brought me satisfaction : (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:) cd /opt/etc/samba rm smb.conf rm smbpasswd cp /share/hdd/conf/share/smb.conf . cp /share/hdd/conf/share/smbpasswd . (:tableend:)

and then only I update the /opt/etc/samba/smb.cong file as shown below.

to:

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

October 22, 2005, at 02:49 PM by JNC --
Changed line 258 from:

That's why I used the following commands thqt brought satisfaction :

to:

That's why I used the following commands that brought me satisfaction :

Deleted line 260:
 [=
Deleted lines 265-267:

=]

and then only I update the /opt/etc/samba/smb.cong file as shown below.

Added line 268:

and then only I update the /opt/etc/samba/smb.cong file as shown below.

October 22, 2005, at 02:48 PM by JNC -- Alternate and simplier method
Added lines 249-271:

Alternate and simplier method

After each reboot, the smb.conf and smbpasswd files in /opt/etc/samba directory are overwritten. Having a look closer, you can see that :

  • /opt/etc/samba/smb.conf and /opt/etc/samba/smbpasswd are just links to /share/hdd/conf/share/
  • links in /opt/etc/samba/ are never overwritten
  • only files in /share/hdd/conf/share/ are overwritten at each boot

That's why I used the following commands thqt brought satisfaction : (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
cd /opt/etc/samba
rm smb.conf
rm smbpasswd
cp /share/hdd/conf/share/smb.conf .
cp /share/hdd/conf/share/smbpasswd .

and then only I update the /opt/etc/samba/smb.cong file as shown below. (:tableend:)

August 27, 2005, at 04:15 PM by tman --
Added line 2:
Changed lines 4-8 from:
  • you have installed unslung 4.20 or later
  • you are unslung to the first disk drive (sda1)
  • you have your user permissions set up for drive access working in the linksys web interface
  • your ipkg is current (ipkg update)
to:
  • You have installed unslung 4.20 or later
  • You have unslung to the first disk drive (sda1)
  • You have your user permissions set up for drive access working in the Linksys web interface
  • Your ipkg is current (ipkg update)
Changed lines 14-15 from:
 ipkg install samba
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ipkg install samba

(:tableend:)

Deleted lines 24-29:
 cp -pR /etc/samba /opt/etc

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

Added lines 28-38:

cp -pR /etc/samba /opt/etc =] (:tableend:)

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
Changed lines 131-133 from:
 cd /opt/etc/init.d
 ./S80samba
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
cd /opt/etc/init.d
./S80samba

(:tableend:)

Added lines 196-198:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
Changed lines 200-201 from:
to:

=] (:tableend:)

Changed lines 220-225 from:

If you want to enable SWAT, the SAMBA web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in dissabled services, which for example could dissable your telnet access.

If you add the following content, SWAT should work out off the box:

to:

If you want to enable SWAT, the Samba web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in disabled services, which for example could disable your telnet access.

If you add the following content, SWAT should work out of the box:

Changed lines 242-245 from:

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buutons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

to:

Once that is done just point your browser to http://IP-address-of-your-slug:901, and enjoy. More info on Samba 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buttons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

Deleted line 248:
August 26, 2005, at 03:25 PM by Mark -- Explained: only root account has full SWAT control + Unicode Support
Changed lines 220-227 from:

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: us3.samba.org/samba/docs/man/

to:

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: http://us3.samba.org/samba/docs/man/

Full control off SWAT is only given if you logon as root, otherwise functionality will be limited! A normal user only get the buutons: Home, Status, View and Password. The root users also gets the buttons to manage shares.

International character support or Unicode support

If you want to store files from Windows using foreign characters from languages like Chinese, Japanese, Korean, etc you definitely need Samba 3, as it supports this out of the box.

August 11, 2005, at 09:25 AM by Dan Scott -- Updated for OpenSlug
Added lines 124-125:

(On OpenSlug, you need to use /etc/init.d/samba restart)

Changed lines 185-186 from:

Please note that on OpenSlug, the log file is on /var/log.smbd.

to:

Please note that on OpenSlug, the log file is on /var/log/log.smbd.

July 20, 2005, at 07:38 PM by Mark --
Added line 40:

hosts deny = 0.0.0.0/0

July 20, 2005, at 07:37 PM by Mark --
Changed line 1 from:

Installing Samba 3.0.14a-4 on Unslung 4.2x beta

to:

Installing Samba 3.0.14a-4 on Unslung 4.2x beta or later

Changed line 3 from:
  • you have installed unslung 4.20
to:
  • you have installed unslung 4.20 or later
July 20, 2005, at 07:36 PM by Mark --
Changed lines 191-217 from:

(:tableend:)

to:

(:tableend:)

SAMBA web config tool

If you want to enable SWAT, the SAMBA web config tool included in the package, you should edit your rc.xinetd diversion script. The diversion script should be in your Unslung directory.

Warning : If you already created a rc.xinetd diversion script, you should only add the part from 'if' to 'fi' and insert it before the 'return 1' in your orginal script. Deleting or editing the other content may result in dissabled services, which for example could dissable your telnet access.

If you add the following content, SWAT should work out off the box:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

  
#!/bin/sh
# Diversion script: /unslung/rc.xinetd
# Customize for your own use, do not delete your original content!
#

if ( [ ! -f /etc/inetd.conf ] || !(grep swat /etc/inetd.conf -q) ) then
  echo "swat stream tcp nowait root /opt/sbin/swat swat" >>/etc/inetd.conf
fi

return 1
 

(:tableend:)

Once that is done just point your browser to <slug IP Address>:901, and enjoy. More info on SAMBA 3 (inclusing SWAT) can be found on the web at: us3.samba.org/samba/docs/man/

July 10, 2005, at 01:01 PM by KGP --
Changed lines 20-21 from:

(Please note that on OpenSlug, the config file must be on /usr/lib/smb.conf)

to:

(Please note that on OpenSlug, the config file is on /usr/lib/smb.conf (old) or /etc/samba (new))

July 07, 2005, at 06:51 AM by KGP --
Changed lines 180-184 from:

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script (rc.samba):

to:

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script

Please note that on OpenSlug, the log file is on /var/log.smbd.

(rc.samba):

July 07, 2005, at 06:45 AM by KGP --
Added lines 20-21:

(Please note that on OpenSlug, the config file must be on /usr/lib/smb.conf)

June 19, 2005, at 04:44 PM by tman --
Added lines 123-127:

Update: Thanks to Inge Bjørnvall Arnesen
Reference links: AddPrinter EnableWinsServer
If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on... You have to set a diversion script in /unslung Create a file rc.samba to include the below

Deleted lines 130-136:
  1. update. Thanks to Inge Bjørnvall Arnesen

Reference links http://www.nslu2-linux.org/wiki/HowTo/AddPrinter http://www.nslu2-linux.org/wiki/HowTo/EnableWinsServer If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on... You have to set a diversion script in /unslung Create a file rc.samba to include the below

Deleted lines 146-149:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
Changed lines 152-154 from:
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
Deleted lines 158-160:

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

Added lines 162-163:

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.

June 19, 2005, at 09:28 AM by marvin_ii -- Workaround for \\\"Can\\
Added lines 182-190:

If your users can´t connect to their shares and you see errors like "Can't become connected user!" in the log-file (/opt/var/samba/log.smbd) and you use the alternate update method: copy /etc/smbpasswd to /unslung/ and add the following lines to your diversion script (rc.samba): (:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
ln -sf /unslung/smbpasswd /opt/etc/samba/smbpasswd
ln -sf /unslung/smbpasswd /etc/samba/smbpasswd

(:tableend:)

June 18, 2005, at 02:35 AM by James --
Changed lines 171-181 from:

samba configuration and make files unsharable.

to:

samba configuration and make files unsharable.


Make sure you edit the "hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2." section to include your network.

sample:

host allow: 127.0.0.1 10.0.0. 10.0.1. 10.0.2. 192.168.0. 192.168.1.

June 04, 2005, at 09:18 PM by Joe USer -- Alternate update
Added lines 147-168:

Alternate Update Method

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 

When rebooting the system the file smb.conf will be overwritten with the original samba 2 version. 
To keep the version 3 file, you need a copy of it in a location where it will not be touched. The best spot for this is /unslung
Once you have created your smb.conf, you will need to remove the link to the old file and and point to the new file with a diversion script.

rc.samba

#!/bin/sh
ln -sf /unslung/smb.conf /opt/etc/samba/smb.conf
ln -sf /unslung/smb.conf /etc/samba/smb.conf
return 0

This should allow you to fully use the web interface, keep both file locations intact and not have to start the v2 server before starting the v3.


(:tableend:)

June 04, 2005, at 08:13 AM by J --
Changed lines 145-149 from:

(:tableend:)

to:

(:tableend:)


Be aware of ipkg upgrade of samba package to 3.0.14a-5. It may break your existing samba configuration and make files unsharable.

May 27, 2005, at 01:27 AM by J -- smb.conf problem fix
Changed lines 121-145 from:

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

to:

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#update. Thanks to Inge Bjørnvall Arnesen
Reference links 
http://www.nslu2-linux.org/wiki/HowTo/AddPrinter
http://www.nslu2-linux.org/wiki/HowTo/EnableWinsServer
If you find that the smb.conf file does stick and revert to orginal during a turn off/turn on...
You have to set a diversion script in /unslung  Create a file rc.samba to include the below

#! /bin/sh
# Diversion script: customize before starting crond
#
#

# Make sure we have a backup copy of /etc/samba/smb.conf
if [ ! -e /etc/samba/smb.conf.orig ]; then 
  cp -p /etc/samba/smb.conf  /etc/samba/smb.conf.orig 
fi

return 1

(:tableend:)

May 23, 2005, at 04:54 PM by RobHam -- Page format improved - script sections now enclosed in tables
Changed lines 22-80 from:
 # sample samba 3.0 conf file
 [global]
 log level = 1

 # CHANGE these settings to match your network/workgroup setup
 # ------------------
 workgroup = WORKGROUP
 server string = NSLU Network Drive
 netbios name = usbdrive
 # your wins server ip address
 wins server = 10.0.0.1
 # the networks you want to allow connections from
 hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2.
 # ------------------

 config file=/opt/etc/samba/smb.conf
 os level = 8
 load printers = no
 max log size = 10
 security = user
 encrypt passwords = yes
 smb passwd file = /opt/etc/samba/smbpasswd
 socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
 preferred master = no
 local master = yes
 dns proxy = no 
 preserve case = yes
 short preserve case = yes
 default case = upper
 case sensitive = no
 mangled names = yes 
 null passwords = yes
 username map = no
 dos filetimes = yes
 force directory mode=771
 force create mode=660
 create mask=771
 map system=yes
 map to guest=Bad User
 guest account=guest
 guest ok = yes
 bind interfaces only = yes
 interfaces = ixp0 lo
 winbind use default domain = no

 [ADMIN 1]
 valid users=@"administrators"
 comment=
 path=/share/hdd/data/
 read only=yes
 write list=@"administrators"
 [DISK 1]
 valid users=@"administrators",@"everyone",@"linux"
 comment=For everyone
 path=/share/hdd/data/public/
 browseable = yes
 read only=yes
 write list=@"administrators",@"everyone",@"linux"
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
# sample samba 3.0 conf file
[global]
log level = 1

# CHANGE these settings to match your network/workgroup setup
# ------------------
workgroup = WORKGROUP
server string = NSLU Network Drive
netbios name = usbdrive
# your wins server ip address
wins server = 10.0.0.1
# the networks you want to allow connections from
hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2.
# ------------------

config file=/opt/etc/samba/smb.conf
os level = 8
load printers = no
max log size = 10
security = user
encrypt passwords = yes
smb passwd file = /opt/etc/samba/smbpasswd
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
preferred master = no
local master = yes
dns proxy = no 
preserve case = yes
short preserve case = yes
default case = upper
case sensitive = no
mangled names = yes 
null passwords = yes
username map = no
dos filetimes = yes
force directory mode=771
force create mode=660
create mask=771
map system=yes
map to guest=Bad User
guest account=guest
guest ok = yes
bind interfaces only = yes
interfaces = ixp0 lo
winbind use default domain = no

[ADMIN 1]
valid users=@"administrators"
comment=
path=/share/hdd/data/
read only=yes
write list=@"administrators"
[DISK 1]
valid users=@"administrators",@"everyone",@"linux"
comment=For everyone
path=/share/hdd/data/public/
browseable = yes
read only=yes
write list=@"administrators",@"everyone",@"linux"

(:tableend:)

Changed lines 88-108 from:
 #!/bin/sh

 # please remove '#' to activate the start script.

 if [ -n "`pidof smbd`" ] ; then
    echo "Stopping smbd:"
    killall smbd
 fi

 if [ -n "`pidof nmbd`" ] ; then
    echo "Stopping nmbd:"
    killall nmbd
 fi

 sleep 2

 echo "Starting smbd:"
  /opt/sbin/smbd -D;
 echo "Starting nmbd:"
  /opt/sbin/nmbd -D;
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#!/bin/sh

# please remove '#' to activate the start script.

if [ -n "`pidof smbd`" ] ; then
   echo "Stopping smbd:"
   killall smbd
fi

if [ -n "`pidof nmbd`" ] ; then
   echo "Stopping nmbd:"
   killall nmbd
fi

sleep 2

echo "Starting smbd:"
 /opt/sbin/smbd -D;
echo "Starting nmbd:"
 /opt/sbin/nmbd -D;

(:tableend:)

May 23, 2005, at 07:24 AM by J -- wrong command
Changed lines 18-19 from:
 cp -pR /etc/samba /opt/etc/samba
to:
 cp -pR /etc/samba /opt/etc
May 19, 2005, at 06:06 PM by John -- Samba
Added lines 1-111:

Installing Samba 3.0.14a-4 on Unslung 4.2x beta

Assumptions for these instructions

  • you have installed unslung 4.20
  • you are unslung to the first disk drive (sda1)
  • you have your user permissions set up for drive access working in the linksys web interface
  • your ipkg is current (ipkg update)

I've not tested any of this on pre 4.2 releases.

Install

 ipkg install samba

Post-install setup

First, copy the default samba config files over to the new samba directory:

 cp -pR /etc/samba /opt/etc/samba

Next, you will need to edit the /opt/etc/samba/smb.conf file so it will work with samba 3.0. An example smb.conf file that works is:

 # sample samba 3.0 conf file
 [global]
 log level = 1

 # CHANGE these settings to match your network/workgroup setup
 # ------------------
 workgroup = WORKGROUP
 server string = NSLU Network Drive
 netbios name = usbdrive
 # your wins server ip address
 wins server = 10.0.0.1
 # the networks you want to allow connections from
 hosts allow = 127.0.0.1 10.0.0. 10.0.1. 10.0.2.
 # ------------------

 config file=/opt/etc/samba/smb.conf
 os level = 8
 load printers = no
 max log size = 10
 security = user
 encrypt passwords = yes
 smb passwd file = /opt/etc/samba/smbpasswd
 socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
 preferred master = no
 local master = yes
 dns proxy = no 
 preserve case = yes
 short preserve case = yes
 default case = upper
 case sensitive = no
 mangled names = yes 
 null passwords = yes
 username map = no
 dos filetimes = yes
 force directory mode=771
 force create mode=660
 create mask=771
 map system=yes
 map to guest=Bad User
 guest account=guest
 guest ok = yes
 bind interfaces only = yes
 interfaces = ixp0 lo
 winbind use default domain = no

 [ADMIN 1]
 valid users=@"administrators"
 comment=
 path=/share/hdd/data/
 read only=yes
 write list=@"administrators"
 [DISK 1]
 valid users=@"administrators",@"everyone",@"linux"
 comment=For everyone
 path=/share/hdd/data/public/
 browseable = yes
 read only=yes
 write list=@"administrators",@"everyone",@"linux"

Finally, edit /opt/etc/init.d/S80samba, remove comments:

 #!/bin/sh

 # please remove '#' to activate the start script.

 if [ -n "`pidof smbd`" ] ; then
    echo "Stopping smbd:"
    killall smbd
 fi

 if [ -n "`pidof nmbd`" ] ; then
    echo "Stopping nmbd:"
    killall nmbd
 fi

 sleep 2

 echo "Starting smbd:"
  /opt/sbin/smbd -D;
 echo "Starting nmbd:"
  /opt/sbin/nmbd -D;

Now you are ready to restart

 cd /opt/etc/init.d
 ./S80samba

If all goes well, the stock samba will stop and your new samba will start.

I've tested this setup, it seems to work correctly and maintain compatibility with the Linksys web interface and the Storage Link windows tray app that mounts USB Memory sticks when inserted into slot 2.