Re: [Dar-support] dar_manager -B .. -A .. with multiple slice/targets?

[Chris P. <li...@fo...>]

Denis Corbin wrote:
> Instead with dar, using -P "/*/bin" will exclude /usr/bin /bin
> /usr/local/bin /home/joe/bin /home/joe/my/other_directory/bin and so on=
=2E

I didn't realize that dar would match like this for inclusion options
like -g, which are defined as "in relation to the backup root"..  As I
understand what you're saying, if I put:

   -R / -g 'xorg.conf'

It would actually back up /etc/X11/xorg.conf?

If this is not the case (which I wouldn't expect it to be), how is it
any different than expecting:

   -R / -g 'etc/*/xorg.conf'

to only back up /etc/X11/xorg.conf and not /etc/something/else/xorg.conf?=


The "search in this path" stuff should be the same.  (I've already been
bitten by the fact that -g doesn't accept globs, and now need to find a
way around that).

> Well, for the PATH-like variable, dar could act differently, following
> what is done for by shell, this would speed up the operation.

exactly.

> I admit that I prefer the "where?" interaction that would let dar learn=

> new location when some are missing ...

I would definitely not want to group these together as the same feature.
 The "where" stuff is a user interface design addition to make dar
easier to use.  The path stuff is for power users.

> This let me wonder why one should have the slices of a given archive
> scattered in many different directories. I understand that one may have=

> some slices on removable media some others on a disk ... but the need
> for masks in the PATH-like variable (provided either on command-line or=

> through an environment variable) is not evident to me.

Well, for one, my burned media does not all share the same mountpoint.
With udev (or whatever does it these days), it comes in as
/media/diskname, where diskname could be anything.  Or I might choose to
put multiple basename/slices into separate directories on the disk to
keep things more organized.

-Chris