On Tue, 19 Sep 2000, Bruce Evans wrote:
> On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
>
> > I recently ran into revelant problem with /dev/stdout, while
> > working on some software under linux that expected /dev/stdout as an
> > argument instead of using stdout.
> >
> > Using the
On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote:
> I recently ran into revelant problem with /dev/stdout, while
> working on some software under linux that expected /dev/stdout as an
> argument instead of using stdout.
>
> Using the device file breaks, if the process is suid to a non
f Of Gerhard Sittig
Sent: Sunday, September 17, 2000 3:18 PM
To: [EMAIL PROTECTED]
Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs
near you!)
On Sun, Sep 17, 2000 at 20:36 +0200, Peter van Dijk wrote:
> On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote:
&g
On Sun, Sep 17, 2000 at 20:36 +0200, Peter van Dijk wrote:
> On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote:
> >
> >
> > [ ... how to find separating chars not used in filenames ... ]
> >
> > e.g.
> > superduperopen("file1&file2", "a+", SDO_TEEFILES)
> > superduperopen("file1&fi
On Thu, 14 Sep 2000, Ben Smithurst wrote:
> Poul-Henning Kamp wrote:
>
> > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> > is bogus. It looks like something which happened "because we can" more
> > than something which has a legitimate need.
>
> You think adding
On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote:
>
>
> How much sense does it make to think about implementing tee and
> select methods this way? Like "open file1 and file2 and write to
> both of them whatever I give to you" and "give me data coming in
> from whatever file is in
using Brian's post since I don't have the original around ...
On Sat, Sep 16, 2000 at 03:49 +0100, Brian Somers wrote:
>
> [ attribution missing, is it Poul-Henning Kamp's text? ]
>
> > The majority of these programs could be handled by adding
> > knowledge of "-" as a magic filename to fopen(3
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
[.]
> I would argue that the programs and the scripts that call them are
> already broken, but hey...
So (just to add fuel to the mass opposition), do this without
temporary files:
On Thu, 14 Sep 2000, Julian Elischer wrote:
> I've never thought of a use for fdescfs...
I used /dev/fd/1 just yesterday for a third-party precompiled binary
that insists on outputting to a file specified on the command line.
Slapping in /dev/fd/1 lets me stuff the command in a pipe chain. Same
On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote:
[...]
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
>
> At the same time I would really love if we implemented "|.*" to mean
> "do an popen(3)" instead.
This would
In message <[EMAIL PROTECTED]> Garrett Wollman writes:
: It's required if we ever get around to supporting secure set-id shell
: scripts. (I think this was the rationale for originally introducing
: it.) It also helps when bogus programs refuse to read from the
: standard input.
I'd like to see
On 14-Sep-00 at 05:37, Poul-Henning Kamp ([EMAIL PROTECTED]) wrote:
> >You think adding a hack to every program to support "-" to mean
> >stdout/stdin is better?
>
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
>
> At the same time
At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote:
>I must admit that I think in general that /dev/std{in,out,err}
>and /dev/fd is bogus. It looks like something which happened
>"because we can" more than something which has a legitimate need.
>
>If anything I would propose we ditch it...
I thi
On Thu, 14 Sep 2000, John Baldwin wrote:
> Poul-Henning Kamp wrote:
> > In message <[EMAIL PROTECTED]>, Peter Pentchev writes
> >
> > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> > is bogus. It looks like something which happened "because we can" more
> > than so
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Peter Pentchev writes
> :
> >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
> >> I've never thought of a use for fdescfs...
> >
> >Well.. just a trivial example - imagine a program which takes a filename
> >as an argument
Garrett Wollman wrote:
> [/dev/stdin] also helps when bogus programs refuse to read from the
> standard input.
Or if you want to read more than one file, one of which is standard input.
e.g.
gzip -dc oldlogs.*.gz | cat /dev/stdin todays-log | log-analyzer ...
Of course that will work with "-"
< said:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
It's required if we ever get around to supporting secure set-id shell
scripts. (I think th
Poul-Henning Kamp wrote:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
I strongly disagree. I actually have a script that I use daily which requi
In message <[EMAIL PROTECTED]>, Robert Withro
w writes:
>
>[EMAIL PROTECTED] said:
>:- The majority of these programs could be handled by adding knowledge of
>:- "-" as a magic filename to fopen(3).
>
>Suppose I *want* a filename called "-"? My tough luck, huh?
./-
Very few programs understand
Poul-Henning Kamp writes:
> In message <[EMAIL PROTECTED]>, Ben Smithurs
> t writes:
> >Poul-Henning Kamp wrote:
> >
> >> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> >> is bogus. It looks like something which happened "because we can" more
> >> than something whic
Johnny Eriksson wrote:
> > [EMAIL PROTECTED] said:
> > :- The majority of these programs could be handled by adding knowledge of
> > :- "-" as a magic filename to fopen(3).
> >
> > Suppose I *want* a filename called "-"? My tough luck, huh?
>
> Could you settle for "./-"?
>
I think any "magic"
> [EMAIL PROTECTED] said:
> :- The majority of these programs could be handled by adding knowledge of
> :- "-" as a magic filename to fopen(3).
>
> Suppose I *want* a filename called "-"? My tough luck, huh?
Could you settle for "./-"?
> Robert Withrow -- (+1 978 288 8256)
> [EMAIL PROTECTED]
[EMAIL PROTECTED] said:
:- The majority of these programs could be handled by adding knowledge of
:- "-" as a magic filename to fopen(3).
Suppose I *want* a filename called "-"? My tough luck, huh?
I *like* /dev/stdin. It's orthogonal!
--
Robert Withrow -- (+1 978 288 8256)
[EMAIL PROTECTE
On Thu, Sep 14, 2000 at 02:37:06PM +0200, Poul-Henning Kamp wrote:
[snip]
> The majority of these programs could be handled by adding knowledge
> of "-" as a magic filename to fopen(3).
>
> At the same time I would really love if we implemented "|.*" to mean
> "do an popen(3)" instead.
Heh, and
In message <[EMAIL PROTECTED]>, Ben Smithurs
t writes:
>Poul-Henning Kamp wrote:
>
>> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
>> is bogus. It looks like something which happened "because we can" more
>> than something which has a legitimate need.
>
>You think ad
Poul-Henning Kamp wrote:
> I must admit that I think in general that /dev/std{in,out,err} and /dev/fd
> is bogus. It looks like something which happened "because we can" more
> than something which has a legitimate need.
You think adding a hack to every program to support "-" to mean
stdout/std
In message <[EMAIL PROTECTED]>, Peter Pentchev writes
:
>On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
>> I've never thought of a use for fdescfs...
>
>Well.. just a trivial example - imagine a program which takes a filename
>as an argument; imagine yourself trying to pipe somet
On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote:
> I've never thought of a use for fdescfs...
Well.. just a trivial example - imagine a program which takes a filename
as an argument; imagine yourself trying to pipe something into it -
passing /dev/fd/0 as a filename to process wou
I've never thought of a use for fdescfs...
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ presently in: Perth
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Over the past few months, I've been working on the /dev/fd file system
("fdescfs"). After weeks of occasionally-hacking and putting it off, I've
finalized a patch for fdescfs.
What this patch changes:
+ fdesc_allocvp() becomes curproc-free as a `struct proc' pointer is passed
as the n
30 matches
Mail list logo
