say when comm separator disappears

2009-05-12 Thread jidanni 
In (info "(coreutils)comm invocation"), after:

  With no options, `comm' produces three-column output.  Column one
   contains lines unique to FILE1, column two contains lines unique to
   FILE2, and column three contains lines common to both files.  Columns
   are separated by a single TAB character.

  The options `-1', `-2', and `-3' suppress printing of the
   corresponding columns.  Also see *note Common options::.

Please add: If two of them are used, the separator is no longer needed
and will not be printed.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

bug report---mv running as root

2009-05-12 Thread JohnT 
Hello. I ran the 7.2 test suite as root to get the results for the tests
required to be run as root, and got one error or failure. The following
is the console log produced by the failure. May 12, 2009. system:
Mandriva Powerpack 2007, i686, gcc 4.1.1, glibc 2.4, binutils 2.19.

John T
j...@worldlinc.net


===
 1 of 370 tests failed
 (72 tests were not run)
 See tests/test-suite.log
 Please report it to bug-coreutils@gnu.org
===

=
   GNU coreutils 7.2: tests/test-suite.log
=

1 of 370 tests failed.  (72 tests were not run).

.. contents:: :depth: 2


FAIL: mv/sticky-to-xpart.log (exit: 1)
==

+ mv --version
mv (GNU coreutils) 7.2
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Parker, David MacKenzie, and Jim Meyering.
+ . ./test-lib.sh
++ unset function_test
++ eval 'function_test() { return 11; }; function_test'
+++ function_test
+++ return 11
++ test 11 '!=' 11
+++ pwd
++ test_dir_=/home/dilbert/Download/utils/coreutils-7.2/tests
+++ this_test_
+++ echo ././mv/sticky-to-xpart
+++ sed 's,.*/,,'
++ this_test=sticky-to-xpart
+++ /home/dilbert/Download/utils/coreutils-7.2/src/mktemp -d
--tmp=/home/dilbert/Download/utils/coreutils-7.2/tests
cu-sticky-to-xpart.XX
++
t_=/home/dilbert/Download/utils/coreutils-7.2/tests/cu-sticky-to-xpart.DFSw7FGii2
++ trap remove_tmp_ 0
++ trap 'Exit $?' 1 2 13 15
++ cd
/home/dilbert/Download/utils/coreutils-7.2/tests/cu-sticky-to-xpart.DFSw7FGii2
++ diff --version
++ grep GNU
+ require_root_
+ uid_is_privileged_
++ id -u
+ my_uid=0
+ case $my_uid in
+ NON_ROOT_USERNAME=nobody
+ . /home/dilbert/Download/utils/coreutils-7.2/tests/other-fs-tmpdir
++ test '' = set
++ CANDIDATE_TMP_DIRS='/root/tmp /tmp /dev/shm /var/tmp /usr/tmp /root'
++ other_partition_tmpdir=
+++ stat -c %d .
++ dot_mount_point=833
++ for d in '$CANDIDATE_TMP_DIRS'
++ test -d /root/tmp
+++ stat -L -c %d /root/tmp
++ d_mount_point=774
++ test x774 = x833
++ mkdir /root/tmp/tmp2552
++ other_partition_tmpdir=/root/tmp/tmp2552
++ break
++ test -z /root/tmp/tmp2552
++ test yes = yes
++ set -x
+ mkdir t
+ chmod a=rwx,o+t t
+ echo
+ chmod a+r t/root-owned
+ chown nobody /root/tmp/tmp2552
+ chmod go+x .
++ setuidgid nobody env
PATH=/home/dilbert/Download/utils/coreutils-7.2/src:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/qt3//bin
mv --version
++ sed -n '1s/.* //p'
+ version=7.2
+ case $version in
+ setuidgid nobody env
PATH=/home/dilbert/Download/utils/coreutils-7.2/src:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/qt3//bin
mv t/root-owned /root/tmp/tmp2552
+ onp='Operation not permitted'
+ sed 's/Not owner/Operation not permitted/;s/Permission
denied/Operation not permitted/' out-t
+ cat
+ compare out exp
+ diff -u out exp
--- out 2009-05-12 16:34:32.0 -0500
+++ exp 2009-05-12 16:34:32.0 -0500
@@ -1 +1 @@
-mv: accessing `/root/tmp/tmp2552': Operation not permitted
+mv: cannot remove `t/root-owned': Operation not permitted
+ fail=1
+ Exit 1
+ set +e
+ exit 1
+ exit 1
+ remove_tmp_
+ __st=1
+ cleanup_
+ rm -rf /root/tmp/tmp2552
+ cd /home/dilbert/Download/utils/coreutils-7.2/tests
+ chmod -R u+rwx
/home/dilbert/Download/utils/coreutils-7.2/tests/cu-sticky-to-xpart.DFSw7FGii2
+ rm -rf
/home/dilbert/Download/utils/coreutils-7.2/tests/cu-sticky-to-xpart.DFSw7FGii2
+ exit 1
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory
`/home/dilbert/Download/utils/coreutils-7.2/tests'
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory
`/home/dilbert/Download/utils/coreutils-7.2/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/home/dilbert/Download/utils/coreutils-7.2/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/dilbert/Download/utils/coreutils-7.2'
make: *** [check] Error 2
[r...@localhost coreutils-7.2]# 
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

mandriva flash

2009-05-12 Thread Bernard Munoz 


Bonjour
Depuis hier alors que je naviguais Internet sous wifi, ma clé a un 
fonctionnement erratique.
Elle a planté le système, il m'a fallu tout arêter avec le bouton ON/OFF
Plus d'accès aux paquetages, Open Office ne fonctionne plus
A travers certaines manipulations (hasardeuses)  j'obtiens ce message d'erreur:
couldn't open RPM DB() at /usr/lib/perl5/vendor_perl/5.10/Rpmdrake/open_db.pan 
line 64
 ou encore
centre réseau-->  instllation des paquetages--> impossibble d'ouvrir la base de 
données rpm --> impossible d'installer le paquetage dhcp-client
Grâce à Internet en liaison ethernet, j'ai parcouru des pages et des pages, 
j'ai signalé ce bug au service Mandriva... dont j'attends une réponse.
J'ai fini par trouver ceci
Signaler un bug à .

Voici donc une copie d'écran:
[r...@localhost /]# cd /
[r...@localhost /]# du -bs * sort -n
du : option invalide -- n
Pour en savoir davantage, faites: « du --help ».
[r...@localhost /]# cd /
[r...@localhost /]# du -bs * | sort -n
du: ne peut accéder `etc/modprobe.preload': Panne d'accès au fichier NFS
du: ne peut accéder `etc/modprobe.conf': Panne d'accès au fichier NFS
du: ne peut accéder 
`etc/sysconfig/network-scripts/wireless.d/00:14:a4:71:d1:73': Panne d'accès au 
fichier NFS
du: ne peut accéder `etc/sysconfig/network-scripts/wireless.d/WANADOO-82B0': 
Panne d'accès au fichier NFS
du: ne peut accéder `live/system/root/tmp/.wh..drakx-stdout.5141': Panne 
d'accès au fichier NFS
du: ne peut accéder `live/system/var/lib/rpm/.wh.__db.001': Panne d'accès au 
fichier NFS
du: ne peut accéder `live/system/var/lib/rpm/.wh.__db.002': Panne d'accès au 
fichier NFS
du: ne peut accéder `live/system/var/lib/rpm/.wh.__db.003': Panne d'accès au 
fichier NFS
du: ne peut accéder `live/system/var/lib/rpm/.wh.__db.004': Panne d'accès au 
fichier NFS
du: ne peut accéder `live/system/etc/modprobe.preload': Panne d'accès au 
fichier NFS
du: ne peut accéder `live/system/etc/modprobe.conf': Panne d'accès au fichier 
NFS
du: ne peut accéder 
`live/system/etc/sysconfig/network-scripts/wireless.d/00:14:a4:71:d1:73': 
Panned'accès au fichier NFS
du: ne peut accéder 
`live/system/etc/sysconfig/network-scripts/wireless.d/WANADOO-82B0': Panne 
d'accès au fichier NFS

Question, comment dépanner et/ou  restaurer la clé à partir du CD fourni?


Bernard Munoz

http://bernardino.over-blog.net 

"Histoires de modélistes" et "Chroniques des années 50"



_
Découvrez toutes les possibilités de communication avec vos proches
http://www.microsoft.com/windows/windowslive/default.aspx___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: tail +n does not work under Linux?

2009-05-12 Thread Christophe LYON 

Thank you Bob for your clarification.


On 11.05.2009 20:28, Bob Proulx wrote:

It is only because 'n' and 'N' are different cases of the same letter
that people's minds play tricks on them.


Indeed.
Maybe a slight rewording of the man page could highlight this?
(eg add another reference to the info page for this trick)


But I still don't see where '-3' is documented?

Matthew quoted the section of the documentation that describes this in
his mail.  Please read that section again.

Oh, you are right. Sorry for having overlooked this.

After reading those 2 paragraphs several times, there are still a few 
things not completely clear:
- tail -COUNT is described as obsolete, but supported when it does not 
conflict with the new standard. But has _POSIX2_VERSION any influence on 
this support?
- tail +COUNT is supported on "older systems". Older than what? How do I 
know whether I am using a "older system" or not?


Is there a way to know which default POSIX version is used by coreutils? 
I have check the build logs, and saw nothing.



The -COUNT style is different from the +COUNT style.  Those are two
different and independent issues.  For a while the -COUNT style was
removed but now it has returned.

As additional information on this please read the FAQ entry on it here.
  http://www.gnu.org/software/coreutils/faq/#Old-tail-plus-N-syntax-now-fails


This for this additional, which actually helped me understand the 
problem better.


Christophe.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils