On Mon, 20 Sep 1999, Matthew Fairley wrote:
> Sounds like that might be a possibility but how would I know. Are we talking
> about the files in my /etc/rc.d/rc* directories? If we are then, again, I'm
> pretty sure that they are all symbolic links to ordinary scripts for starting
> the various services etc. Or, are we talking about some script calling
> 'setserial' from within itself? If we're talking about someting else, I need
> another clue. I'm at work at the moment so can't check - feedback later.
Sounds like you have sysv init scripts ie a Redhat system, ( i have
not followed this thread). why not do;
cd /etc/rc.d/rc3.d (presuming you boot into init level 3 and do;
'grep setserial *' and see what files show setserial.
Then you can look at the files one by one and see whats happening.
And possably find the problem.
Just my thoughts.
> Ray Olszewski <[EMAIL PROTECTED]> wrote:
> OK. Second guess -- one of your rc* files is running setserial, and that
> causes the second round of serial-port detection. Also check if one of the
> rc* files is adding a module that detects serial ports (I suspect this is
> what Mike actually had in mind in making his suggestion).
>
> At 04:53 PM 9/19/99 BST, Matthew Fairley wrote [in part]:
> >Good try Mike but I'm certain that I compiled my kernel only for standard
> >serial ports - no added extras were compiled in. Next? :-)
> >
> >Mike <[EMAIL PROTECTED]> wrote:
> >>On 17 Sep 1999, Matthew Fairley wrote:
> >>
> >>> Can anyone tell me why my serial driver gets configured twice during
> >bootup?.
> [rest deleted]
>
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
>
> ____________________________________________________________________
> Get your own FREE, personal Netscape WebMail account today at
>http://webmail.netscape.com.
--
Regards Richard
[EMAIL PROTECTED]
