From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Ishtar.sc.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by sourceware.org (Postfix) with ESMTPS id B4969386FC22 for ; Mon, 14 Jun 2021 23:35:43 +0000 (GMT) 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 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 15ENZGap016479; Mon, 14 Jun 2021 16:35:19 -0700 Message-ID: <60C7E78B.6060200@tlinx.org> Date: Mon, 14 Jun 2021 16:34:35 -0700 From: L A Walsh User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Duncan Roe , "cygwin@cygwin.com" Subject: Re: odd prob for cygwin 'dd' from a character device on network disk References: <60C168AF.4070400@tlinx.org> <20210610022303.GA14223@dimstar.local.net> <60C2D67E.3030407@tlinx.org> <20210612013219.GC14223@dimstar.local.net> In-Reply-To: <20210612013219.GC14223@dimstar.local.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2021 23:35:45 -0000 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*