OT: RE: Unix Help re Samba - for filePro

[Brian K. White]

On Tue, 2010-04-13 at 17:38 -0400, Fairlight wrote:
> Only Rodney Kerrick would say something like:
> > On 4/13/2010 3:38 PM, Rodney Kerrick wrote:
> > > We are migrating to a new Unix server. We are currently on a Unix 
> > > SCO_SV release 3.2v5.0.4 and are moving to a new Unix server SCO_SV 
> > > release 5v6.0.0. All I want to do is map a drive letter from Windows 
> > > to a Unix directory.
> 
> Your need is ambiguously stated.  Do you want to:
> 
> 1) Mount a Windows share onto a Unix mount point
> 
> or
> 
> 2) Export a Unix directory for use under Windows on a particular drive
> letter?
> 
> The first is not possible on SCO, based on everything I've read; mounting a
> samba share requires kernel support.  Nothing I've read indicates SCO has
> such support.
> 
> The second simply requires editing smb.conf and [re]starting smbd.  If you
> need this option, `man smb.conf` for options, or borrow from the sample
> shares (or both).  Once exported, map in Windows as you would any UNC.
> 
> Why are you moving to 5.0.6 as "new", when 5.0.7 has been out for years,
> anyway?

He's going to OSR 6.0.0 not OSR 5.0.6

6.0.0 is the newest, but in my opinion worst thing he could do even
though it's a major technical advance in many ways.

[This is for Rodney's or others' sake more than yours Mark]
The problem is it's too big of an overhaul from previous versions, what
with replacing the entire kernel with unixware's and grafting the OSR5
userspace onto the Unixware kernel. That's major brain surgery and did
not go 100% smoothly. It was a great idea for providing a product that
lets people move ahead while still being backwards compatible. The
problem is it was created just as the company was going down the tubes,
and even though it's at least a couple years old by now, they have been
useless years. Too few people ever used this version and the company
lost all their customers and all their good engineers and so it's hardly
improved at all since day one and there is hardly any self-help in the
form of experience from other people, and nor will there be.

This problem is the perfect example. I do not know any of the details of
samba on osr6. What version of samba comes stock? What versions are
available? where? how do you install/upgrade them? where does the vendor
put smb.conf? what init script(s) starts & stops it? is SWAT installed
by default? is there a vendor-supplied configurator like scoadmin or
yast? If that configurator exists, will it overwrite smb.conf if you
edit it directly or must you locate some other config file and edit that
instead? I don't know any of that stuff for OSR6, but I DO for both OSR5
and for openSUSE Linux, Ubuntu Linux, and FreeBSD. Also it's easy to
look it up for any other Linux. And, whatever I didn't just happen to
know, and was not well described in docs, I can and would also just spot
check with a little direct experiment on OSR5 and Linux and FreeBSD, but
not OSR6, because I have boxes running those others but not OSR6.

He made a logical purchase, just an unlucky one due, I'm guessing, to
not being aware of issues like this.

I can say for certain that it is not possible to mount windows shares on
any version of osr5 using any version of Samba (or FacetWin, it was
possible with VisionFS). I'm only 99% sure that it's not possible on
OSR6 or Unixware either. It is possible to _access_ windows shares on
all versions of all products on all versions of all OS's that even could
run those products, using an ftp-like utility vs mounting as a
filesystem.
But I don't think that's what he wanted so it's probably not an issue.

-- 
bkw