Thanks for all the input.
I've found that the program puts most of its files in one location and only a
few in one other. I don't actually need to worry about this anymore as the tar
command isn't as long as I thought it would be.
Mathew
Mathew Snyder wrote:
> I have been given a task of instal
I think Rodrick's idea is best. But if the
installation process doesn't let you specify an
installation directory, and if it doesn't document
where it's putting the binaries and config files, then
perhaps right after the install you could use the find
command in a manner such as the following:
# f
On Thu, 2007-05-03 at 22:40 -0400, Mathew Snyder wrote:
> I have been given a task of installing a piece of backup software, then
> tarring
> up all of the associated files in order to automate the installation onto
> other
> machines. The only way I can think of doing this is to do an ls -l on
unfortunately, no. It has predetermined file locations spread across the drive
Mathew
Rodrick Brown wrote:
> On 5/3/07, Mathew Snyder <[EMAIL PROTECTED]> wrote:
>> I have been given a task of installing a piece of backup software,
>> then tarring
>> up all of the associated files in order to aut
On 5/3/07, Mathew Snyder <[EMAIL PROTECTED]> wrote:
I have been given a task of installing a piece of backup software, then tarring
up all of the associated files in order to automate the installation onto other
machines. The only way I can think of doing this is to do an ls -l on / and
then doi
I have been given a task of installing a piece of backup software, then tarring
up all of the associated files in order to automate the installation onto other
machines. The only way I can think of doing this is to do an ls -l on / and
then doing a diff after the installation and manually adding t
