[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ProgSoc] Debian policy question - opinions sought
If I do a recursive scp of a debian box's /etc directory, it gets into
a really ugly loop when it reaches /etc/apache. The /etc/apache/conf
symlink (which points to . ) causes it to dig deeper and deeper into
the same directory, until it carks it. Which takes a surprisingly long
I checked with the debian maintainer of the package, and he simply
said that I should fix my program (in this case openssh's scp binary),
and that it would break policy, and referred me to :
But on reading that, I'm not sure that the suggestion to effectively do :
ln -s /etc/apache conf
.. is somehow unacceptable in the policy, as compared to the current :
ln -s . conf
I'm not going to win a battle I don't want to fight with a Debian
maintainer, and I'm equally as unlikely to go tell the nice openSSH
people that their software is broken. But I'm nonetheless unconvinced.
I'm thinking that the other approach that isn't *too* ugly (for my
original problem) is to ssh a tar cvf call, then scp that file back,
then untar it locally. I'm less interested in reasons why I wouldn't
want to keep a local copy of configuration files from a set of machines
on a single box.
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to email@example.com.
If you are having trouble, ask firstname.lastname@example.org for help.