[EMAIL PROTECTED] (Bob Proulx) wrote:
> * src/touch.c (usage): Improve wording of documentation regarding
> file argument handling and special handling of - argument.
> * doc/coreutils.texi (touch invocation): Likewise.
> Documentation problem reported by Vincent Lefevre.
Thanks!
Applied.
__
[EMAIL PROTECTED] wrote:
> I would like to get in touch with Colin Plumb regarding "shred".
> Recently I am trying to shred data for my company but when we try to run
> "shred" with 5 passes, it does not return after 4 days. We have a tight
> deadline to complete this exercise for all servers.
>
>
FYI, here's a snapshot, with all the latest bits:
http://meyering.net/cu/coreutils-6.9+.tar.gz
http://meyering.net/cu/coreutils-6.9+.tar.gz.sig
Aka,
http://meyering.net/cu/coreutils-6.9+-ss-2007-08-21.08.01.27+0.tar.gz
http://meyering.net/cu/coreutils-6.9+-ss-2007-08-21.08.01.27+0
diff --git a/ChangeLog b/ChangeLog
index 291b9f3..6590c15 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2007-08-21 Jim Meyering <[EMAIL PROTECTED]>
+
+ By default, do not install hostname anymore.
+ * configure.ac: Add "hostname" to the list of not-installed programs.
+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Contrast the following:
$ mkdir a b c
$ echo 1 > a/f
$ echo 2 > b/f
$ cp -v a/f b/f c --remove-destination
`a/f' -> `c/f'
cp: will not overwrite just-created `c/f' with `b/f'
with the similar:
$ rm c/f
$ ln -vf a/f b/f c
`c/f' => `a/f'
`c/f' => `b/f
On Tue, 21 Aug 2007, Eric Blake wrote:
$ ln -vf a/f b/f c
`c/f' => `a/f'
`c/f' => `b/f'
$ cat c/f
2
Oops - we overwrote the just-created c/f with a link to b/f.
But you told it to, with -f. Doesn't POSIX require this to succeed?
Cheers,
Phil
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Philip Rowlands on 8/21/2007 3:30 PM:
> On Tue, 21 Aug 2007, Eric Blake wrote:
>
>> $ ln -vf a/f b/f c
>> `c/f' => `a/f'
>> `c/f' => `b/f'
>> $ cat c/f
>> 2
>>
>> Oops - we overwrote the just-created c/f with a link to b/f.
>
> But you t
Dear Sir,
while practicing the basic unix commands, I made one unix,txt at desktop and
for the same file I changed the permission:
$ chmod 000 unix.txt
meaning that neither owner nor group and others have permission to read, write
execute.
when I deleted the unix.txt file, it simply got deleted.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Sonali Jha on 8/21/2007 8:15 PM:
> $ chmod 000 unix.txt
> meaning that neither owner nor group and others have permission to read,
> write execute.
> when I deleted the unix.txt file, it simply got deleted.
>
> Please clear when owne
