From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alain M." Subject: Re: tcp/ip + samba + dosemu Date: Wed, 21 Jun 2006 16:06:44 -0300 Message-ID: <449998C4.1050706@pobox.com> References: <200606201508.12819.rafi@pers.pl> <200606202041.38210.zswi@pers.pl> <44985F59.80605@pobox.com> <200606210915.15248.zswi@pers.pl> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <200606210915.15248.zswi@pers.pl> Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="windows-1252"; format="flowed" To: dosEmu-list Rafa=C5=82 Cygnarowski escreveu: >>> It's not so simple :( I just catn't do this that way. Shared resour= ces >>> are databases witch require file locking. Samba resources are not >>> redistributable so I can't eg. "lredir" mounted by linux directorie= s... >> I don't undertand this > What's unclear for you? =46WIK, locks work with samba and dosemu. Have you tested it? I remembe= r=20 that it worked ;-) >=20 >> FWIK, there is no driver for MS client that uses packet driver, AND = you >> only have one pkt in doemu. > That's why I'm looking for help. it is just my opinion: try to get it working as above and use the packe= t=20 driver for wattcp >> That is not all of it, you have to install a bridge, ebtables and tu= ntap :( > Can you point me some good resource describing this? Google returns n= othing=20 > useful for 'tuntap ebtables dosemu'... In dosemu's manual:=20 http://dosemu.sourceforge.net/docs/README/1.1.3.7/x991.html But this is a bit better: http://www.cs.iitm.ernet.in/~raturi/final/README.html The problem in fact is not dosemu, you need to have a functional tap0,=20 that is part of one thing called tuntap. And then to make it work you=20 will need a bridge, which is closesely related to ebtables. It took me a long time to learn it, and I lost all of it when all my=20 machines were stolen... BTW, use the list for discussion so more people may help ;-) 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