Sorry but I'm not subscribed so I can't reply to the relevant mail, but this
mail is about the ifupdown initscript issue(s) with /run.
As best I can tell, the problem(s) with the ifupdown script boil down to the
fact that it's myreadlink() cannot handle nested symlinks. However the
attached simple patch seems to fix this by having myreadlink restart it's main
loop again if it discovers such a nested symlink.
I decided not to post it to either of the possibly relevant existing bugs in
the BTS for now (623076 & 623523) as the descriptions of both make me wonder if
they refer to other problems.
I hope this helps.
Thanks,
Niall
--- ifupdown.orig 2011-04-30 19:47:20.826097001 +0100
+++ ifupdown.new 2011-04-29 19:29:08.743097001 +0100
@@ -42,7 +42,7 @@
fi
fi
- while [ ! -e "$dest" ]; do
+ while [ ! -e "$dest" ] && [ ! -L "$dest" ]; do
extras="${dest##*/}/$extras"
if [ "${extras%%/*}" = ".." ]; then return 1; fi
destx="${dest%/*}"
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
