On 8/5/24 00:14, Mouse wrote:
I think it would make more sense to reclassify it as a PR against pax
rather than a PR against tar. (Especially if pax exhibits a similar
insistence on getcwd() working even when run as pax. I don't know
whether it does; I don't run anything recent enough to useful
Hello,
PR 44498 is regarding tar(1)'s dependence on getcwd(3).
This only exists when /bin/pax is called as "tar", which is only true of
/bin/tar when building with MKBSDTAR set to "no" in order to not use
bsdtar from libarchive. The default setting of MKBSDTAR has been "yes"
since 2019:
--
re
Hello,
PR 39254, regarding the inability to read a single key from from a hash
DB with db(1), appears to've been resolved at some point; this does not
replicate on -current, either with or without the NULL byte:
--
$ db -w -C -N hash test.db key1 val1
Added key `key1'
$ db -N hash test.db key1
Hello,
I noticed that the functionality requested in PR 57069, which is for
date(1) to support -f to define the input format, already exists;
according to "cvs log", it has existed for about as long as the PR:
--
revision 1.63
date: 2022-10-22 15:11:43 -0500; author: christos; state: Exp; li
Hello,
Here is a fix for PR 56138, in which it is observed that chpass(1) and
friends should not allow breaking the passwd databases by editing the
username.
The problem:
--
# grep 1005 /etc/passwd
testuser:*:1005:0:,,,:/home/testuser:/bin/sh
# chpass testuser
# grep 1005 /etc/passwd
testus
On 2013-01-23 09:01, Matteo Bernardini wrote:
Hi J,
I tried to adapt the line to take in account Eric's advices
SLKCFLAGS=${SLKCFLAGS:--O2}
LIBDIRSUFFIX=""
[ "$(uname -m)" = "x86_64" ] && [ ! "$(echo $PATH | grep
^/usr/bin/32)" ] && SLKCFLAGS="$SLKCFLAGS -fPIC" LIBDIRSUFFIX="64"
[ "$ARCH" = "i
from receiving unwanted mail (spam).
- Original Message -
From: "Anne Wilson" <>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 04, 2003 2:16 AM
Subject: Re: M J Pipkin [Fwd: Re: [newbie] Given Up (was Who uses AC97?)]
> On Friday 03 Oct 2003 9:15 pm, Heather/F
