|
ru.unix.bsd
- RU.UNIX.BSD ------------------------------------------------------------------
From : Slawa Olhovchenkov 2:5030/500 22 Jul 2004 20:22:00
To : Valentin Davydov
Subject : вести с полей
--------------------------------------------------------------------------------
22 Jul 04, Valentin Davydov writes to Slawa Olhovchenkov:
>> kientzle 2004-07-17 06:03:47 UTC
>>
>> FreeBSD src repository
>>
>> Modified files:
>> usr.bin/tar Makefile
>> gnu/usr.bin/tar Makefile
>> Log:
>> Make bsdtar the default system tar. This makes /usr/bin/tar a symlink
>> pointing to /usr/bin/bsdtar by default. To make it point to
>> /usr/bin/gtar,
>> you can define WITH_GTAR.
>>
>> Вот. Как и предсказывалось.
VD> Объяснил бы кто, зачем вообще все эти детские игры с гнутыми/негнутыми
VD> тарами,
By default, /usr/bin/tar is now a symlink pointing
to /usr/bin/bsdtar.
How will this affect you?
Most people should not notice the change. bsdtar
accepts the most popular gtar command-line options, reads
gtar files, and generally does what most people
expect from a modern tar implementation.
However, bsdtar is not a clone of gtar. If you rely
on specific gtar features, then you should be using gtar.
What are the differences?
* Command line: bsdtar implements the -l and -o
options according to the Single Unix Standard,
gtar's -l and -o options directly contradict SUS.
bsdtar warns about most mis-uses of these options,
but there is a potential for silent changes to the
behavior of existing scripts.
* File format: bsdtar can read gtar files, including
long file names, long link names, and sparse files.
bsdtar can also read many other formats that gtar
does not support.
bsdtar writes POSIX-standard ustar archives by default.
gtar can read ustar archives with no problem.
bsdtar uses POSIX "pax extended attributes" for long file
names, long link names, ACLs, file flags, and other
additional information. gtar does not understand pax
extended attributes and will warn about them. (Joerg
Schilling's "star" does support pax extended attributes
as do POSIX-compliant pax implementations on many commercial
Unix platforms.)
* Error reporting: bsdtar is more critical than gtar about
certain kinds of errors. In particular, it will exit with
an error if you provide nonsensical command-line options or
if you attempt to read an unrecognized archive. gtar does
not warn about many such problems.
* Ease of use: When reading archives, bsdtar automatically
determines compression and file format. The -j, -y, -z, and -Z
options are ignored when reading archives.
bsdtar can "interpolate" entries from existing archives when
creating new archives (see the "@archive" extension).
* Advanced tape drive support: gtar has a variety of options
for managing tape drives, including rmt support. bsdtar currently
lacks these features.
* Portability: gtar is portable to many different Unix and non-Unix
systems. bsdtar supports standard file formats that are widely
supported by other implementations. There are efforts to port
bsdtar to other platforms.
If you have any questions or concerns, feel free to address them
to me at: kientzle@freebsd.org
Tim Kientzle
* Don't forget to mention it can be faster than GNU tar, too :)
Great job!
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> green@FreeBSD.org \ The Power to Serve! \
Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
* Less known bugginess: gtar on sparc64 has sporadic problems,
e.g. attempting to use all available VM. bsdtar doesn't have obvious
problems on other FreeBSD architectures.
Kris
WoW! > shar format support
This is useful for ports committers:-). I wanted it!
Of course, I am using knu's sunshar. But...
VD> авками и проч., а? Всё равно ведь gcc.
Остальное не знаю.
ЗЫ: icc используй.
... Hет повести печальнее на свете, чем повесть о заклинившем Reset'е
--- GoldED+/BSD 1.1.5
* Origin: (2:5030/500)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
|
вести с полей 
