Supporting Warpstock 2012, Portland, Oregon, USA
I'm updating this page. I now have SAMBA reasonably working on my server. It's a little easier to install a working SAMBA now, in November 2012. I'm leaving the December 2010 post to show why SAMBA is catching on slowly in the eCS world.
I installed the Samba Server for OS/2. The OS/2 version is 1.1.2, but it is based on Linux version 3.3.16
Samba depends on klibc 0.6.5. The Samba installer depends on Warp-IN.
The web page for SAMBA is http://samba.netlabs.org/
The installation files for SAMBA are
Setting up SAMBA to start every time. I prefer to set up SAMBA to start from the Workplace Shell Startup Folder. The script I use is shown below. I create an object of the script, with the SAMBA installation directory as the working directory, and place it in the Startup Folder.
/* Script to start Samba on Blonde Guy server */ say "wait 10 seconds before starting SAMBA" 'sleep 10' say "starting SAMBA" call smb 'start' say "SAMBA started" return
SAMBA is configured using the smb.conf file located in the %ETC% directory. I will not try to explain how every part of this file is set, but that global settings, home directories and printer and directory shares are set in this file.
I have created users and shared directories with SAMBA Server. The clients seem to browse all shares and have read/write permission regardless of what it says in smb.conf. Shares work with SAMBA Client on eCS and Mac OS X 10.7. Printer shares do not appear to work.
If a SAMBA client copies a file to the server, then the last write date is the date of the copy operation. This is wrong, and will wreck any version control system over SAMBA. The solution for now is to keep any version control system on the server.
In our December 10, 2010 BayWarp meeting at Jim's house, we tried to make SAMBA work. We had success with the client to access both shares from Windows XP, Windows 7 and OS/2 File and Print. The SAMBA Client built into eCS 2.0 works just fine for this, although it can be a bit confusing to use.
Unfortuntately, we didn't know about Herwig Bauernfeind's Samba for eComStation (OS/2) webpage.
The next step is to see if we can get the server to work. Just installing is a bit of a problem. First, here is the web page for SAMBA.
Even finding SAMBA server is not simple. The links on the above page are broken, so we wind up browsing the Netlabs ftp site.
There we find two packages of interest:
But the first link, the supporting REXX libraries for SAMBA server, are scripted incorrectly. They will not install correctly unless you change the installation directory to be the root.
There are six packages included in REXX libraries for SAMBA server. The first one, VX-REXX Runtime, is correct and greyed out. For each of the remaining five packages, change the path to the root of the installation drive.
Two of the files installed conflict with files on the eCS 2.0 system.
Once the REXX libraries are installed, the server can be installed. The installer warns about setting UNIXROOT to E:\MPTN. But the installation is successful, and a GUI runs that asks for a root password, some basic configuration information and sets up root and guest accounts. The Default user should be set up later. A Samba Server folder is set up on the desktop.
The GUI is running without error.
Open a command prompt, and go to the directory where you installed SAMBA. Run
SMB.cmd start. Possible errors at this point:
After addressing these errors, my Samba server is running and a Samba client on another machine is able to see my Samba server shares.