From: Claudia Neumann <dr.claudia.neumann@gmx.de>
To: "Alain M." <alainm@pobox.com>
Cc: dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: cifs 1.50 and dosemu 1.4 great combination
Date: Fri, 12 Oct 2007 13:58:24 +0200 [thread overview]
Message-ID: <200710121358.24303.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <470F06AB.2000200@pobox.com>
Hi Alain!
Yes, the newest samba and the newest cifs-code together with kernel > (I
think) 2.6.18 solves the samba locking problem. I just forgot to tell you.
At last my work and mails to Jeremy Allison were successful. Now even clipper
locks are recognized and reported to the clients. Nevertheless samba is very
slow. During my investigations about the samba locking problem I got the
advice to turn my network concept around. Now all my clients log in on the
server via ssh and start a dosemu or other session on the server. Network
trafic is very much reduced and the work on the clients is quicker than ever.
Working on Windows-servers/-clients can not keep up with that.
CU
Claudia Neumann
Am Freitag, 12. Oktober 2007 07:31 schrieb Alain M.:
> kemas escreveu:
> >> A clipper program runs on dosemu (I supose withe FreeDOS), dosemu runs
> >> on centos. But dosemu uses either an image (where lock work) or the
> >> linux fle system, I supose then that cifs is replacing samba and that
> >> lock work between doemu and cifs...
> >
> > cifs does not replace samba, samba still the file server.
> >
> > cifs is use as the filesystem to mount samba share, then dosemu would run
> > our program on lredired drive.
> > the lock here means file locking between multiuser apps that use the same
> > file.
>
> Could you give setup commands? This may interest more people, so I am
> bringing it back to the list...
>
> I am not sure that I understand: You have a samba server, maybe even on
> the same machine; cifs then replaces samba-client, on every machine;
> then dosemu relays the file-locks correctly. Are you using freeDOS?
>
> Sorry if I may seam a little dumb, but some time ago Bart said that lock
> did NOT work... and I googled about cifs and could not really understand
> the details.
>
> Thanks,
> Alain
>
> -
> 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
next prev parent reply other threads:[~2007-10-12 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 14:30 cifs 1.50 and dosemu 1.4 great combination kemas
[not found] ` <470E52D1.5040406@pobox.com>
[not found] ` <1192159242.2490.10.camel@localhost>
2007-10-12 5:31 ` Alain M.
2007-10-12 6:19 ` Bart Oldeman
2007-10-12 11:58 ` Claudia Neumann [this message]
2007-10-15 3:23 ` kemas
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 14:39 Tarquin Adams
2007-11-14 16:03 ` Claudia Neumann
2007-11-15 10:26 Tarquin Adams
2007-11-21 4:04 ` kemas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710121358.24303.dr.claudia.neumann@gmx.de \
--to=dr.claudia.neumann@gmx.de \
--cc=alainm@pobox.com \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox