| To: | Russell Coker <russell@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: when do stdout, stdin, and stderr get created? |
| From: | Richard Gooch <rgooch@xxxxxxxxxxxxxxx> |
| Date: | Fri, 9 Nov 2001 15:15:40 -0700 |
| Cc: | devfs@xxxxxxxxxxx |
| In-reply-to: | <20011109211241.4F88D18E5@lyta.coker.com.au> |
| References: | <20011109211241.4F88D18E5@lyta.coker.com.au> |
| Sender: | owner-devfs@xxxxxxxxxxx |
Russell Coker writes:
> Currently on boot I see the following messages from devfsd:
> error lstat(2)ing: "stdin" No such file or directory
> error lstat(2)ing: "stdout" No such file or directory
> error lstat(2)ing: "stderr" No such file or directory
>
> Where are these links created? Why are they created in the early
> boot process? Why not just have devfsd create them (or one of the
> boot scripts)?
Those links are created by devfsd (as is "fd") early in it's
initialisation phase. But the message is wrong, it's a call to stat(2)
that is failing, not lstat(2). I don't get these messages.
Hm. Is /proc mounted at this time?
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | when do stdout, stdin, and stderr get created?, Russell Coker |
|---|---|
| Next by Date: | Patch for GNUmakefile and rpm.spec, Pavel Roskin |
| Previous by Thread: | when do stdout, stdin, and stderr get created?, Russell Coker |
| Next by Thread: | Re: when do stdout, stdin, and stderr get created?, Russell Coker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |