pcmcia statup order
Hi,
More than one person(debain-user) is having problems with the startup
sequence with
pcmcia. I thought I'd ask here as this list is very familiar with
pcmcia. Please read the messages below. It seems that
/etc/init.d/networking gets called before /etc/init.d/pcmcia.
I searched open and closed bugs for brian@debian.org and could not find
anything reported
about this.
Is this a problem that needs to be looked at for the distribution?
It sure makes the out of box experience with Debian a little rough.
Eric :-)
Eric Richardson wrote:
>
> "Stephen E. Hargrove" wrote:
> >
> > On Thu, 5 Apr 2001, Mircea Luca wrote:
> > >
> > > amm....it is.IF you browse /etc/rcS.d you'll see S40networking .So if
> > > you start pcmcia at 39(with S39 a symlink to /etc/init.d/pcmcia or
> > > wahtever the script name is) in rcS.d you'll be just fine.I don't have
> > > my laptop at home so can't tell
> > > exactly but that's the idea.
> > > rcS.d is executed first,then rc(0-6).d .Actually rc.boot is really the
> > > first one but that is deprecated and it shouldn't be used.
> > > man init
> > > will tell you more about the boot process.
> > >
> >
> > That did the trick. Thanks!
>
> I have a similar problem running stable using pcmcia and DHCP. I have
> the following in relevent files in
>
> /etc/rcS.d.
> S35mountall.sh
> S39dns-clean
> S40hostname.sh
> S40networking
> S40pump
>
> In /etc/rc0.d
> S35networking
>
> In /etc/rc1.d
> S20single
>
> In /etc/rc2.d
> S11pcmcia
> S14ppp
> S20inetd
> S50netatalk
>
> Netatalk fails but pump must keep working as eventually eth0 comes up
> but usually after the boot is complete and I have GDM running.
>
> Should I move dnsclean down towards 35 and insert pcmcia afterwords? If
> I move the pcmcia up to rcS.d then do I also need to make sure that the K
> scripts make sense as well?
>
> Thanks,
> Eric :-)
Reply to: