On Wed, Jun 12, 2002 at 04:27:19AM +0200, Cyrille Lefevre wrote:
[...]
> already done using the NetBSD way. the problem is that they use
> LC_TIME (hugh!) to pass the format string to strftime while
> LC_TIME isn't suppose to contain any format strings but a locale
> name.
Ew! That won't work for
On Wed, Jun 12, 2002 at 03:07:45AM +0200, Bjoern Fischer wrote:
> > PS : I've finished to merge diffs from OpenBSD last week, but diffs
> > w/ NetBSD are really big... so, be patient :P
>
> What about bin/35886?
already done using the NetBSD way. the problem is that they use
LC_TIME (hugh!) to p
> PS : I've finished to merge diffs from OpenBSD last week, but diffs
> w/ NetBSD are really big... so, be patient :P
What about bin/35886?
Björn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote:
> Dan Nelson wrote:
[snip]
> According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug:
> ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess
> it qualifies as a "non-trivial program". :-)
FYI, the curren
On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote:
> On my friend's BSD/OS system, there is no tar--or rather, it's just a hard
> link to pax:
>
> % ls -li `which tar` `which pax`
> 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/pax
> 1819 -r-xr-xr-x 2 bin
>
> >
> > Hi,
> >
> > I've just noticed that something wrong with the new tar in the base
> > system (1.13.25) - when extracting some archives it creates 777 dirs,
> > while permissions in the archive itself are OK (for example GNU make
> > make-3.79.1.tar.gz - top level dir gets 777 as well as
Dan Nelson wrote:
> Tar 1.13 is 3 years old, and has many bugs (incremental backups are
> unusable, for example).
On the flip side, I hear it respects the umask when running as root...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
In the last episode (Jun 06), Trevor Johnson said:
> > I've just noticed that something wrong with the new tar in the base
> > system (1.13.25) - when extracting some archives it creates 777 dirs,
> > while permissions in the archive itself are OK (for example GNU make
> > make-3.79.1.tar.gz - top
>
> Hi,
>
> I've just noticed that something wrong with the new tar in the base
> system (1.13.25) - when extracting some archives it creates 777 dirs,
> while permissions in the archive itself are OK (for example GNU make
> make-3.79.1.tar.gz - top level dir gets 777 as well as several
> other
Hi,
I've just noticed that something wrong with the new tar in the base
system (1.13.25) - when extracting some archives it creates 777 dirs,
while permissions in the archive itself are OK (for example GNU make
make-3.79.1.tar.gz - top level dir gets 777 as well as several
other lowel level dirs)
10 matches
Mail list logo
