X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B4969386FC22
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=tlinx.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tlinx.org
Message-ID: <60C7E78B.6060200@tlinx.org>
Date: Mon, 14 Jun 2021 16:34:35 -0700
From: L A Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Duncan Roe <duncan_roe AT optusnet DOT com DOT au>,
        "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: odd prob for cygwin 'dd' from a character device on network disk
References: <60C168AF DOT 4070400 AT tlinx DOT org>
 <20210610022303 DOT GA14223 AT dimstar DOT local DOT net> <60C2D67E DOT 3030407 AT tlinx DOT org>
 <20210612013219 DOT GC14223 AT dimstar DOT local DOT net>
In-Reply-To: <20210612013219.GC14223@dimstar.local.net>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 2021/06/11 18:32, Duncan Roe wrote:
> On Thu, Jun 10, 2021 at 08:20:30PM -0700, L A Walsh wrote:
>   
>> On 2021/06/09 19:23, Duncan Roe wrote:
>>     
>>> nfs / nodev?
>>>
>>>       
>> I'm not sure what you mean or are asking.
>> I'm not using nfs...but cygwin.
>>
>> The file 'zero' is in the same dir as the file 'null'.
>> I usually read 'zero' and write to 'null, though
>> for 1-way testing, I read from file 'zero' on the remote
>> file system and write, locally to /dev/null.
>>
>> For other direction write to 'null' and read from
>> /dev/zero locally.
>>
>>
>>     
> When you said you were accessing zero over the network, you didn't say how so I
> suggested if you were using nfs then nodev might be the culprit.
>
> How are you accessing files aver the network?
>
> I suspect that whatever mechanism you are using has the equivalent of the nfs
> nodev feature (part of nfsmount, may be specified in fstab) and the nodev
> equivalent is turned on in your case.
>   
----
    Was afraid that's what you meant...don't know of such an option
with samba, not to mention using the same version of samba now,
as for ages.

    Using smb/cifs -- a mounted samba share with my home directory mounted
as drive 'H'.

The device files are created in my home directory (on linux)
as files 'zero' and 'null'.

I don't know of any equivalent 'nodev' option in samba -- but
regardless, I'm not sure what has changed.  I'm still running the
same samba that I have for over a year -- my kernel might be
different, but I don't think there's been any change
to '/dev/zero' -- but in the same directory, writing to
the file named 'null' still works.

*sigh*




-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple