Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #11764 > unrolled thread

Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes?

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes? Greg Wooledge <wooledg@eeg.ccf.org> - 2015-10-26 08:27 -0400

#11764 — Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes?

On Fri, Oct 23, 2015 at 04:01:37PM -0600, Bob Proulx wrote:
> The /proc/self/fd/ directory is a kernel construct.  It does not have
> normal file system semantics.

> And really what would be a sane purpose in being able to remove files
> from it?  What would that do?  Would that make any sense at all?  I
> think it wouldn't make any sense.

Well, it *could* conceivably act like close().  But that's a bit
off topic here.

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web