--- Dan Nicholson <[EMAIL PROTECTED]> wrote:

> On 7/31/06, Ken Moffat <[EMAIL PROTECTED]>
> wrote:
> >  Hi Alexander, Go,
> [snip]
> > -bash_cv_dev_fd=absent
> > +bash_cv_dev_fd=standard
> [snip]
> > +#define HAVE_DEV_FD 1
> > +#define DEV_FD_PREFIX "/dev/fd/"
> [snip]
> > -/* #undef HAVE_DEV_FD */
> > +#define HAVE_DEV_FD 1
> >
> >  /* Defined to /dev/fd or /proc/self/fd (linux).
> */
> > -/* #undef DEV_FD_PREFIX */
> > +#define DEV_FD_PREFIX "/dev/fd/"
> 
> Looks like the /dev/fd issue is the culprit. Nice
> job, fellas. Now,
> can anyone look at the configure macro to see how
> this issue is
> decided? There might be an easy workaround. I don't
> have the source
> handy.

Ok, some more stuff.

I've looked at the configure code, and the error
(/dev/fd absent) comes from the test:
test -r /dev/fd/0
which returns 1.
So I checked all the rights of these files and links,
and I found that it was /dev/tty1 (file pointed by
/proc/self/fd/0) that have not the good rights:
crw-------  1 root tty     4,   1 Jul 31 18:29
/dev/tty1

I checked the others /dev/tty* files, and I found that
their rights were all:
crw-rw-rw-
but as soon as I do a login, it becames crw-------.

So I tried to change the rights, from root: chmod +rw
/dev/tty1
A "ls -l" gave the good rights:
crw-rw-rw-
but as soon as I tried the test above, it failed and
the rights came again crw-------.

Strange, but I'm not very familiar with tty and login.

Last but not least, I change the owner of tty1:
chown clfs /dev/tty1
After doing that, all was ok. The test was right, the
configure no more complained about /dev/fd absent, and
the bash was good.

However, it doesn't seem very clean. Perhaps someone
who knows exactly how tty and login work can have a
better solution.

Regards
G. Moko


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev

Reply via email to