[Fwd: Re: Samba and kernel oplocks - Smbmount]

[Fwd: Re: Samba and kernel oplocks - Smbmount]

[Oscar A. Valdez]

I forgot to mention that I had to substitute the FreeDOS kernel that
comes packaged with the binary Dosemu 1.0.2.x distribution (version
2024?) with kernel.sys version 2026.

Kernel versions earlier that 2026 do not handle locks on lredir'd
drives.

-----Mensaje reenviado-----

From: Oscar A. Valdez <oscar.valdez@plastipak.com.sv>
To: Stephen Lee <splee@plexio.com>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: Samba and kernel oplocks - Smbmount
Date: 29 Aug 2002 08:39:48 -0600

I'm accessing Samba shares with Dosemu 1.0.2 and 1.0.2.1. File locking
works flawlessly and with simultaneous access by Window$ clients.

I mount the Samba share with

mount -t smbfs //SERVER/SHARE /mnt/MOUNTPOINT -o credentials=CREDENTIALS_FILE,workgroup=WORKGROUP,rw,gid=GID,fmask=770

and then, within Dosemu

lredir F: linux\fs/mnt/MOUNTPOINT

(Of course, all the stuff in capitals needs to be substituted correspondingly).

Works fine.

Oscar

El mié, 28-08-2002 a las 22:39, Stephen Lee escribió:
> On Tue, 2002-08-27 at 15:55, Stephen Lee wrote:
> > Hi,
> > 
> > I am running a Foxpro application under Dosemu 1.1.3.2 (xdosemu) with
> > the keyboard patches and things seem to be running smoothly. Problems
> > occur when some users access the same Foxpro db files via Samba 2.2.4.
> > Files locked under Dosemu/Foxpro are not locked when accessed by Samba.
> > Some of the samba config settings include:
> > 
> > kernel oplocks = yes
> > locking = Yes
> > oplocks = Yes
> > level2 oplocks = Yes
> > oplock contention limit = 2
> > posix locking = Yes
> > strict locking = No
> > 
> > This is a Redhat 7.2 systems running kernel 2.4.18. What else do I need
> > to configure to get Dosemu file locks recognized by Samba?
> 
> Just for kicks, I tried to access the Foxpro db files via an smb share
> using smbmount. Instead of pointing $_hdimage to the Drdos/Foxpro
> directory directly, I pointed it to a directory mounted to the smb share
> containing the Drdos/Foxpro files. The idea was to make Dosemu use the
> Samba file locking system. Well...Dosemu runs and Foxpro starts but the
> whole process is REALLY slow. So slow that I didn't have the patience to
> test whether the file locking problem was fixed. It's not eating up cpu
> cycles either (according to top).
> 
> Has anyone tried to access smb shares from Dosemu and if yes how did you
> do it?
> 
> Thanks,
> Stephen
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Stephen Lee]

On Thu, 2002-08-29 at 08:04, Oscar A. Valdez wrote:
> I forgot to mention that I had to substitute the FreeDOS kernel that
> comes packaged with the binary Dosemu 1.0.2.x distribution (version
> 2024?) with kernel.sys version 2026.
> 
> Kernel versions earlier that 2026 do not handle locks on lredir'd
> drives.
>

Thanks Oscar. I am using DRDOS but since the install_systemwide script
requires dosemu-freedos-bin.tgz does that mean I also need to upgrade
the FreeDOS kernel as well? Recall that I am using 1.1.3.2 with the
keyboard patches. Another point is that I"m not using lredir as
$_hdimage points directly to "C:\" and the Foxpro app must run on the C:
drive.

Stephen
 

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Oscar A. Valdez]

I don't know what version of the kernel comes with 1.1.3.2, but, like
Bart said, your $_hdimage gets converted to an lredir'd drive, and if
your kernel doesn't handle locks properly on lredir'd drives, you won't
be able to set locks on C:

Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a
higher version of kernel.sys with it?

Oscar

El jue, 29-08-2002 a las 10:30, Stephen Lee escribió:
> On Thu, 2002-08-29 at 08:04, Oscar A. Valdez wrote:
> > I forgot to mention that I had to substitute the FreeDOS kernel that
> > comes packaged with the binary Dosemu 1.0.2.x distribution (version
> > 2024?) with kernel.sys version 2026.
> > 
> > Kernel versions earlier that 2026 do not handle locks on lredir'd
> > drives.
> >
> 
> Thanks Oscar. I am using DRDOS but since the install_systemwide script
> requires dosemu-freedos-bin.tgz does that mean I also need to upgrade
> the FreeDOS kernel as well? Recall that I am using 1.1.3.2 with the
> keyboard patches. Another point is that I"m not using lredir as
> $_hdimage points directly to "C:\" and the Foxpro app must run on the C:
> drive.
> 
> Stephen
>  
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Stephen Lee]

On Thu, 2002-08-29 at 11:20, Oscar A. Valdez wrote:
> I don't know what version of the kernel comes with 1.1.3.2, but, like
> Bart said, your $_hdimage gets converted to an lredir'd drive, and if
> your kernel doesn't handle locks properly on lredir'd drives, you won't
> be able to set locks on C:
> 
> Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a
> higher version of kernel.sys with it?
> 
> Oscar

Hmmm...does that mean I should be using Freedos and not DRDOS if I want
proper kernel locking? I hope Foxpro works well with Freedos!

Stephen

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Bart Oldeman]

On 29 Aug 2002, Stephen Lee wrote:

> On Thu, 2002-08-29 at 11:20, Oscar A. Valdez wrote:
> > I don't know what version of the kernel comes with 1.1.3.2, but, like
> > Bart said, your $_hdimage gets converted to an lredir'd drive, and if
> > your kernel doesn't handle locks properly on lredir'd drives, you won't
> > be able to set locks on C:
> > 
> > Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a
> > higher version of kernel.sys with it?

There is no kernel that comes with 1.1.3.2 - it's just a development
test version of DOSEMU. In general DOSEMU is FreeDOS kernel agnostic -
though newer kernels tend to work better than older ones.

> > Oscar
> 
> Hmmm...does that mean I should be using Freedos and not DRDOS if I want
> proper kernel locking? I hope Foxpro works well with Freedos!

FreeDOS should work just like DR-DOS in this respect but it never
hurts to try FreeDOS.

In general DOS talks to DOSEMU lredir'ed drive through the redirector
interface. This is a list of calls you can find in Ralf Brown's
Interrupt List at INT2F/AX=11xx. It's a horrible interface because it
wasn't designed as such - but we have to live with it to get proprietary
DOSes to access lredir'ed drives.

The same redirector interface is what DOS uses to talk to network drives
in general and with MSCDEX/(FD/SHSUCDEX)/NWCDEX for CDROM drives too.

FreeDOS kernels before ~2026 did not translate
--------D-215C-------------------------------
INT 21 - DOS 3.0+ - "FLOCK" - RECORD LOCKING
into
--------N-2F110A-----------------------------
INT 2F CU - NETWORK REDIRECTOR (DOS 4.0+) - LOCK/UNLOCK REGION OF FILE

That was the problem - the redirector interface is a relatively recent
addition to FreeDOS. DR-DOS should not have this bug.

I suspect that the way that DOSEMU tries to implement DOS locking
techniques is not compatible with mandatory locking on the Samba Unix
side.

Bart

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Stephen Lee]

On Thu, 2002-08-29 at 11:54, Bart Oldeman wrote:
> FreeDOS kernels before ~2026 did not translate
> --------D-215C-------------------------------
> INT 21 - DOS 3.0+ - "FLOCK" - RECORD LOCKING
> into
> --------N-2F110A-----------------------------
> INT 2F CU - NETWORK REDIRECTOR (DOS 4.0+) - LOCK/UNLOCK REGION OF FILE
> 
> That was the problem - the redirector interface is a relatively recent
> addition to FreeDOS. DR-DOS should not have this bug.
> 
> I suspect that the way that DOSEMU tries to implement DOS locking
> techniques is not compatible with mandatory locking on the Samba Unix
> side.
Thanks for explaining the complexities. A few more questions:

1. Does that mean Sergey's hack to mfs.c is not a permanent solution?
I've made the changes but am waiting for my Foxpro users to test it.

2. Is using smbmount to access the Foxpro files from Dosemu a valid way
to get around the locking problem? I suspect it will be slower but
anything else?

Thanks again.
Stephen

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Oscar A. Valdez]

On my Samba server, the shares accessed via Dosemu are configured with 'oplocks = no' and 'level2 oplocks = no', because of particularitites of the shared application.

I haven't tried Dosemu on shares without those two options, but since
oplocks are a NetBios feature, I don't see why it shouldn't work.

Oscar

El jue, 29-08-2002 a las 12:54, Bart Oldeman escribió:
> On 29 Aug 2002, Stephen Lee wrote:
> 
> > On Thu, 2002-08-29 at 11:20, Oscar A. Valdez wrote:
> > > I don't know what version of the kernel comes with 1.1.3.2, but, like
> > > Bart said, your $_hdimage gets converted to an lredir'd drive, and if
> > > your kernel doesn't handle locks properly on lredir'd drives, you won't
> > > be able to set locks on C:
> > > 
> > > Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a
> > > higher version of kernel.sys with it?
> 
> There is no kernel that comes with 1.1.3.2 - it's just a development
> test version of DOSEMU. In general DOSEMU is FreeDOS kernel agnostic -
> though newer kernels tend to work better than older ones.
> 
> > > Oscar
> > 
> > Hmmm...does that mean I should be using Freedos and not DRDOS if I want
> > proper kernel locking? I hope Foxpro works well with Freedos!
> 
> FreeDOS should work just like DR-DOS in this respect but it never
> hurts to try FreeDOS.
> 
> In general DOS talks to DOSEMU lredir'ed drive through the redirector
> interface. This is a list of calls you can find in Ralf Brown's
> Interrupt List at INT2F/AX=11xx. It's a horrible interface because it
> wasn't designed as such - but we have to live with it to get proprietary
> DOSes to access lredir'ed drives.
> 
> The same redirector interface is what DOS uses to talk to network drives
> in general and with MSCDEX/(FD/SHSUCDEX)/NWCDEX for CDROM drives too.
> 
> FreeDOS kernels before ~2026 did not translate
> --------D-215C-------------------------------
> INT 21 - DOS 3.0+ - "FLOCK" - RECORD LOCKING
> into
> --------N-2F110A-----------------------------
> INT 2F CU - NETWORK REDIRECTOR (DOS 4.0+) - LOCK/UNLOCK REGION OF FILE
> 
> That was the problem - the redirector interface is a relatively recent
> addition to FreeDOS. DR-DOS should not have this bug.
> 
> I suspect that the way that DOSEMU tries to implement DOS locking
> techniques is not compatible with mandatory locking on the Samba Unix
> side.
> 
> Bart


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]

[Oscar A. Valdez]

I've had no problems with FreeDOS.

Maybe you should give it a try, and let the list know if FoxPro works.

Oscar

El jue, 29-08-2002 a las 12:41, Stephen Lee escribió:
> On Thu, 2002-08-29 at 11:20, Oscar A. Valdez wrote:
> > I don't know what version of the kernel comes with 1.1.3.2, but, like
> > Bart said, your $_hdimage gets converted to an lredir'd drive, and if
> > your kernel doesn't handle locks properly on lredir'd drives, you won't
> > be able to set locks on C:
> > 
> > Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a
> > higher version of kernel.sys with it?
> > 
> > Oscar
> 
> Hmmm...does that mean I should be using Freedos and not DRDOS if I want
> proper kernel locking? I hope Foxpro works well with Freedos!
> 
> Stephen
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html