Joan Picanyol i. Puig writes:
> Hi again, I definitely think I'm getting closer now
>
> On Wed, 2 May 2001, Richard Gooch wrote:
>
> > I assume you're running glibc? In that case, talk to the glibc
> > maintainers. It sounds like their ttyname(3) implementation doesn't
> > scan /dev/pty for terminals.
> I'm running glibc-2.1.3 and you mention a 'similar fix', could you
> point to the patch for it please (I'd just like to get rid of
> MKOLDCOMPAT...)?
The patch I referred to in the FAQ is only about ttyname(3) dealing
correctly with symbolic links. It does not have anything to do with
scanning /dev/pty. That would require a separate patch. Someone would
need to write that.
Alternatively, try to get a version of your application that uses
Unix98 ptys instead.
> Well, my question wasn't precise enough (as a matter of fact nor correct I
> forgot to do this before), here's what I've done with the configuration files
> attached:
>
> 1 scsi hd & 1 ide hd already working
> root:/root # ls /dev/discs/ -l
> total 0
> lr-xr-xr-x 1 root root 30 Jan 1 1970 disc0 ->
> ../ide/host0/bus0/target0/lun0
> lr-xr-xr-x 1 root root 31 Jan 1 1970 disc1 ->
> ../scsi/host0/bus0/target6/lun0
>
> These work fine (thankfully), the problem comes with module autoloading:
>
> root:/root # cdrecord -scanbus
> Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
> cdrecord: No such file or directory. Cannot open SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
> root.
I don't know what problem you were having. I don't keep records of bug
reports with insufficient information (my mailbox isn't big enough).
So I need bug reports with a description of the problem and symptoms,
and complete debugging information. Followup messages need to keep
sufficient context so I can look at the message in isolation, and have
all the information I need.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|