/dev/fd/62: No such file or directory

[Linda Walsh]

When a system is not fully up or limping, various
services like udevd may not be mounted yet -- proc may not be
mounted yet.  But it appears there are features in bash that
try to use external paths to access process descriptors in
itself (rather than just using them directly).

If there is a need to pick up those fd's, I think it would
be prudent if bash, **internally**,
did not rely on os-mechanisms that may not be there ...

Note -- I'm not saying bash should attempt to do something
about a user's use of /dev/stdin or whatever in a script.

but specifically I've seen above error message /dev/fd/62 (not sure
if it was just 62, maybe 63 as well?) a fair amount after,
I think, 4.3.

I certainly wouldn't be against a builtin that would return
the same thing as /dev/fd/62 -- just one that doesn't try to
walk an external path to perform internal functions (have looked
several times at scripts that have shown such messages, and
have yet to see any mention of /dev/fd/xx in the script, so I'm
/presuming/ (sigh) that it is something internal to bash?