> Is there a certain method for making a new link work right when backing > it up to Eiger boot disk? > > I added a new link: > ln -s /etc/ilink.235 -> /etc/rc2.d/S40ilink.235 > > Which is to set some port forwarding rules at boot up. > Ok, I make the sym link and go to lrcfg and backup etc. > I even check the etc.lrp with tar on another machine and the link is in > the etc.lrp file. Snip of tar -tvzf output > > lrwxrwxrwx root/root 0 2002-04-19 13:23 etc/rc2.d/S10watchdog -> > ../init.d/watchdog > lrwxrwxrwx root/root 0 2002-04-19 13:26 etc/rc2.d/S40ilink.235 > -> /etc/ilink.235 > > So, it's there. But, after booting the link does not exist in the ram > disk! > So, what am I missing?
The links in the /etc/rc?.d directories are special. They are *NOT* backed up, but are re-created at boot by the RCDLINKS variable in each init script. If you want to change the init links for a package, do it in the package's /etc/init.d/ script, and backup that package. More info is in the online FAQ at the LEAF sourceforge site. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
