> OK, I have a package which contains a symlink: > > /var/log/iptraf -> /var/log > > Also, I am using ramlog.lrp and ram1 for /var/log . > > During bootup and initial package install, that symlink does *NOT* get > created! > > However, if I load that same package a second (2nd) time -- after bootup > is complete -- ontop of itself, then the symlink is created properly ;> > > Yes, this symlink in another package works as expected: > > /var/sh-log -> /var/log > > What is going on? Why are there bootup/initialization limitations to > symlink creation?
What's going on is that until init runs the bootstrap scripts (/etc/rcS.d), the ramdisk partition containing the contents of /var/log is not populated. When you extract the /var/sh-log symlink, it gets put into the /var directory, and all is well. When you extract the /var/log/iptraf symlink at boot-time, however, it gets created in /var/log, which subsequently "disappears" when the init scripts create and mount your /var/log partition. Actually, if you unmount /var/log, your symlink should "magically" re-appear! To get around this, you can either not put /var/log on a seperate partition, or create the symlink after the init scripts have created/mounted /var/log. You can do this either with an init script of your own as part of the package, or by installing the package manually after the system is booted. If you're really adventurous, you can write a script to load packages after the system has been configured...I keep meaning to get around to this, but have never had the time or the urgent need... 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
