Joe Krahn wrote:
>> That's a generic problem of Linux distributions trying to standardize
>> file and directory locations. But the easy fix is to copy the existing
>> content to your new partition, then either mount it in the old location
>> or replace the old location with a symlink.
>>
> I disagree. You might consider it an install-time setting, but then it
> should not be a modifiable value in config.pl. Even so, why make the
> backup path a one-time install setting?
I can't really comment on what other issues are involved since I
installed from source and placed everything on /opt/backuppc which is a
separate mounted partition, and I want everything related to the
application (bin/lib/conf, etc.) there to simplify working with image
copies of this partition on other machines. If I were to move parts or
all of it to other locations without a symlink at the expected place an
assortment of things would probably break, like the 'use lib' statements
that are also substituted in the install.
You'd have to look through the configure/install script to find all
places where the location is substituted in the runtime code and the
implications of moving it. Mounting or symlinking at the expected
topdir location just seems easier (along with avoiding the FHS-style
splattering of components all over the place...).
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
