This appears to be a simple omission in the ebuild, if I understand correctly. I updated to net-dialup/rp-pppoe-3.7 , which changes the names of the programs /usr/sbin/adsl-start (etc) to /usr/sbin/pppoe-start (etc). The script /etc/init.d/adsl , which used to start my Internet connection at boot, no longer worked, as it used the previous program name (adsl-start). There is also a script /etc/init.d/rp-pppoe , which also uses adsl-start : in order to start the Internet at boot using rp-pppoe-3.7 , one has to change the name of the program in this script to pppoe-start , which I have done by hand & got the connection to start properly as a result. The other scripts in /etc/init.d are created by packages, eg local belongs to baselayout, cupsd to cups. This appears to be an oversight in creating the ebuild for rp-pppoe-3.7 , which should offer a revised version of /etc/init.d/rp-pppoe .
No, there's no ommision, adsl baselayout module handles this.
Ok, in that case, the rp-pppoe ebuild should inform users of the fact & advise them to re-emerge baselayout (which it doesn't do). This is an exception to the general rule that packages provide such scripts. It's a very simple change, after all.
(In reply to comment #2) > Ok, in that case, the rp-pppoe ebuild should inform users of the fact > & advise them to re-emerge baselayout (which it doesn't do). > This is an exception to the general rule that packages provide such scripts. > It's a very simple change, after all. I suggest that your read the Changelog and basic documentation provided by us. It's been removed 9 months ago, good morning. 21 Jun 2005; Alin Nastac <mrness@gentoo.org> -files/rp-pppoe.rc, rp-pppoe-3.5-r11.ebuild: Remove the rp-pppoe init script. The new way of using rp-pppoe is through adsl net module of the baselayout-1.11.12-r4. http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=3#doc_chap4
Sorry, I always appreciate devs' volunteer efforts & do yours, but you are not responding to the bug I have reported. I have just gone thro' the following exercise (not all steps seem necessary, but I wanted to show I've been thorough): (1) rename scripts 'adsl' & 'rp-pppoe' in /etc/init.d so they aren't recognised; (2) 'rc-update del rp-pppoe default'; (3) 'emerge baselayout' (1.11.14-r6); (4) 'etc-update' (nothing to do); (5) reboot : Internet connection doesn't start; (6) 'emerge rp-pppoe' (3.7); (7) 'pppoe-setup' (fill in entries or follow defaults); (8) 'pppoe-start' (Internet connection starts as normal); (9) reboot : Internet connection doesn't start; (10) restore the script 'rp-pppoe' in /etc/init.d as previously; (11) reboot : Internet connection starts correctly & all's well. The emerge of baselayout makes no change in the contents of /etc/init.d ; there are scripts there 'net.lo' & 'net.ppp0' & a symlink 'net.eth0 -> net.lo', but alone they do not enough; I tried adding them to /etc/runlevels/default with rc.update, but the connection still didn't start at boot. The connection starts only when there is a symlink in /etc/runlevels/default to a script in /etc/init.d which calls /usr/sbin/pppoe-start . The only script I have which does that is rp-pppoe . However, no package provides that script (I checked with equery) & emerging baselayout didn't restore it to /etc/init.d . Simply referring to a changelog in an earlier ebuild doesn't explain this. How exactly is baselayout supposed to be now ensuring that pppoe-start is executed at boot time ? Which script in /etc/init.d does that ? If it's done otherwise, how ? I will leave your 'resolved invalid' status, as it's taken enough of my day, but really would appreciate an explanation how the new system works.
