mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Cc: linux-kernel@vger.kernel.org, Al Piszcz <apiszcz@solarrain.com>
Subject: Re: How come dd if=/dev/zero of=/nfs/dev/null does not send packets over the network?
Date: Wed, 2 Jun 2004 08:39:15 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0406020828060.2685@chaos> (raw)
In-Reply-To: <5D3C2276FD64424297729EB733ED1F7606243695@email1.mitretek.org>

On Wed, 2 Jun 2004, Piszcz, Justin Michael wrote:

> root@jpiszcz:~# mkdir /p500/dev
> root@jpiszcz:~# mount 192.168.0.253:/dev /p500/dev
> root@jpiszcz:~# echo blah > /p500/dev/null
> root@jpiszcz:~# ls -l /p500/dev/null
> crw-rw-rw-  1 root sys 1, 3 Jul 17  1994 /p500/dev/null
> root@jpiszcz:~# dd if=/dev/zero of=/p500/dev/null
>
> 6179737+0 records in
> 6179736+0 records out
>
> Instead it treats it as a local block device?
>
> Kernel 2.6.5.
>

First, /dev/null is a device file. Can you access a remote
device over nfs? ... like

		mount chaos:/dev/ttyS0  /mnt
		cat "foo" >/mnt

I think not. Yes it's the exact same thing; /dev/null is a
character device just like /dev/ttyS0, but a bit dumber.
The above used the network to make the essential equivalent
of a sym-link. The open of the device-file, the connection
of the major-minor numbers to the resulting file descriptor
occurred on your local system.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



  parent reply	other threads:[~2004-06-02 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 12:04 Piszcz, Justin Michael
2004-06-02 12:13 ` Christoph Hellwig
2004-06-02 12:19 ` Grzegorz Kulewski
2004-06-02 12:20 ` Måns Rullgård
2004-06-02 12:39 ` Richard B. Johnson [this message]
2004-06-02 20:37 ` Horst von Brand
2004-06-02 20:46 ` Arthur Perry
2004-06-02 12:27 Piszcz, Justin Michael

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=Pine.LNX.4.53.0406020828060.2685@chaos \
    --to=root@chaos.analogic.com \
    --cc=apiszcz@solarrain.com \
    --cc=justin.piszcz@mitretek.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®