HEADS UP: tar -l is now (intentionally) broken.

[David Gilbert]

>>>>> "Tim" == Tim Kientzle <kientzle at freebsd.org> writes:

Tim> Since POSIX and GNU violently disagree about the meaning of "tar
Tim> -l", and there seem to be strong adherents to both
Tim> interpretations, I'm preparing to commit a patch that breaks "tar
Tim> -l" for everyone:

Tim> $ tar -cl foo Error: -l has different behaviors in different
Tim> tars.  For the GNU behavior, use --one-file-system instead.  For
Tim> the POSIX behavior, use --check-links instead.

Is this in any way related to the fact that /usr/bin/bsdtar seems
unable (after a new world from yesterday) to archive any files?

[2:1:301]dgilbert at canoe:~> bsdtar -cvf temp .bashrc
a .bashrc: tar format cannot archive this: Inappropriate file type or format

... is what I get.

Dave.

-- 
============================================================================
|David Gilbert, Independent Contractor.       | Two things can only be     |
|Mail:       dave at daveg.ca                    |  equal if and only if they |
|http://daveg.ca                              |   are precisely opposite.  |
=========================================================GLO================