Bo Andresen: > On Wednesday 22 March 2006 20:26, Sergio Polini wrote: > > I'ld like to know how the sequence of init scripts is set up. > > Did you look in the Gentoo handbook? > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap= >4 > > If after reading that you still have unanswered questions then ask > again.
I had read that page (perhaps I should have said that I had ;-), but: - before() and after() functions are not mentioned (I can guess that they are "normal" functions defined only in net.*); - the arguments to after and before seem service names (f.i., "but want your service to be started before (or after) another service"), but... what kind of service is "net"? Is it net.lo, net.eth?, netmount? There is no "net" service... I'm using a notebook (HP dv5078) and an all-in-one printer (HP PSC 1510). The hplip service has not worked until I removed it from the default runlevel and executed it in local.start. I've found that hplip worked if started after iptables, didn't work if started before iptables. I've contacted HP, and their answer was: > HPLIP requires the loopback interface for TCP/IP socket > communication. I would expect the following order at boot time > for proper operation. > > iptables > loopback interface > hplip > cups My default init sequence [was] is different: - domainname - net.lo - syslog-ng - anacron - net.eth0 [- hplip, when it didn't work] - cupsd - gpm - iptables - netmount - local -> hplip I'ld like to try the sequence suggested by HP, but I can't understand what could I do. For example, how could I execute iptables (which is executed "before net", but after net.*) before net.lo? > > Moreover, I'd like to know if it's possible to verify the actual > > sequence of the init scripts. I can look at the commands that a > > make command would execute but do not execute them, or at the > > problems reported by fsck avoiding to repair them, by the -n > > option. Could I check an init sequence in a similar way? > > I don't think so. But it will check syntax of the entire script if > you run any command on it. Only syntax though. Yes, I could try: - replacing "before net" with "before net.lo" in iptables; - adding "after iptables" to cupsd; and so on, but even if some editing worked, eventually after a few booting failures, that would be a "blind workaround" ;-) Cheers Sergio -- gentoo-user@gentoo.org mailing list
