Re: cp: progress bar :)
On Friday 21 December 2007, Andrea Di Pasquale wrote: > Hi! I've patched coreutils 5.94/6.9 for add cp's progress bar. thanks, but didnt you just post this with a different e-mail address ? while it wont get merged, i imagine other people may find it useful. i'd point out that your usage of size_t types wont fly in a 32bit world and LFS. you should convert all of your internal size units to off_t's instead. then test copying a file that is over 2 gigs in size. -mike signature.asc Description: This is a digitally signed message part. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: LIST file names from UNIX (Remote server) to Mainframe (Local server) dataset.
Jay Kumar wrote: > Kindly let me know the UNIX list command with example which can copy the > list of remote server (UNIX) files to local server (Mainframe) dataset. You are posting a generic question but this is not truly a generic question forum. This is the GNU Coreutils mailing list. The GNU Coreutils are the basic file, shell and text manipulation utilities of the GNU Operating System. You can learn more about GNU Coreutils here: http://www.gnu.org/software/coreutils/ The GNU Coreutils are part of the GNU Operating System. You can learn more about the GNU Project here: http://www.gnu.org/ But you are asking about how to transfer files from one system to another. You probably want to look at file transfer protocols such as OpenSSH here: http://www.openssh.org/ Perhaps in conjunction with rsync here: http://rsync.samba.org/ Good luck! Bob ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
LIST file names from UNIX (Remote server) to Mainframe (Local server) dataset.
Dear Sir/Madam, Kindly let me know the UNIX list command with example which can copy the list of remote server (UNIX) files to local server (Mainframe) dataset. I will be very thankful for the same, Thanks and Regards, Nits ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: printf failure on darwin with coreutils-6.9.91
Peter Fales <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 21, 2007 at 05:06:11PM +0100, Jim Meyering wrote:
>> Peter Fales <[EMAIL PROTECTED]> wrote:
>> > I'm trying to build coreutils-6.9.91 for Mac OS/X (Darwin 10.3)
>> > and getting test failures from misc/printf. The output of make check
>> > is attached below. I believe the problem occurs around line 345 of
>> > src/printf.c which has:
>> >
>> > 342 switch (conversion)
>> > 343{
>> > 344case 'd': case 'i': case 'o': case 'u': case 'x': case 'X':
>> > 345 length_modifier = PRIdMAX;
>> > 346 length_modifier_len = sizeof PRIdMAX - 2;
>> > 347 break;
>> >
>> > On linux PRIdMAX is defined as "lld" but on darwin it is defined as "qd".
>> > Later on in the block of code around line 331 in lib/parse-printf.c, the
>> > 'q' case is not handled.
>
> I've attached lib/config.h as requested.
Hi Peter,
This line in config.h,
/* #undef HAVE_LONG_DOUBLE */
shows that the configure-time test for long double support
failed. Can you look in config.log (or send it) to see why?
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: Maybe a bug!
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Why does head accept die option -1 and tail does not, in this same > context? ... > $ LANG=C tail -1 LottoDate.txt LottoJahr.txt LottoZahl.txt > tail: option used in invalid context -- 1 Thanks for the report. What version of tail are you using? That bug has been fixed for some time. The latest test release is coreutils-6.9.91. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: typo
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > 2007-12-21 Ralf Wildenhues <[EMAIL PROTECTED]> > > * doc/coreutils.texi: Fix a typo. Avoid the term `relationals'. Hi Ralf, Applied. Thanks and Happy holidays! ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
typo
Hello Jim, all,
found a single typo in the coreutils manual. Also, I suggest to change
`relationals' as it seemed a bit odd -- is that a proper word? Even if
it is, I think `relational operators' is clearer, at least to a
non-native like me.
Cheers,
Ralf
2007-12-21 Ralf Wildenhues <[EMAIL PROTECTED]>
* doc/coreutils.texi: Fix a typo. Avoid the term `relationals'.
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 392359b..01c2edb 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -7079,7 +7079,7 @@ Preserve the times of last access and last modification,
when possible.
In general, it is not possible to preserve these attributes
when the affected file is a symbolic link.
However, FreeBSD now provides the @code{lutimes} function, which makes
-it possibile even for symbolic links. However, this implementation does
+it possible even for symbolic links. However, this implementation does
not yet take advantage of that.
@c FIXME: once we provide lutimes support, update the above.
@itemx links
@@ -10687,9 +10687,9 @@ True if the strings are not equal.
@cindex numeric tests
@cindex arithmetic tests
-Numeric relationals. The arguments must be entirely numeric (possibly
-negative), or the special expression @[EMAIL PROTECTED] @var{string}}}, which
-evaluates to the length of @var{string}.
+Numeric relational operators. The arguments must be entirely numeric
+(possibly negative), or the special expression @[EMAIL PROTECTED]
@var{string}}},
+which evaluates to the length of @var{string}.
@table @samp
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: Maybe a bug!
On Fri, 21 Dec 2007, [EMAIL PROTECTED] wrote: Why does head accept die option -1 and tail does not, in this same context? Please see this FAQ entry regarding arguments to tail: http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#Old-tail-plus-N-syntax-now-fails I'm not sure why head and tail are not behaving the same way, but generally that form of the syntax is not encouraged. Cheers, Phil ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
wcwidth failure on RedHat Linux 7.3 (coreutils-6.9.91)
I'm seeing the following gnulib test failure while building coreutils-6.9.91 on RedHat Linux 7.3. I'm not sure whether folks want to support such old systems, but just in case... I've attached the results of the verbose make check below, but the failure is at line 63 of gnulib-tests/test-wcwidth.c which says: 63 ASSERT (wcwidth (0x2060) == 0); The value that is actually being returned is -1. Here's the complete log: make check-recursive make[1]: Entering directory `/opt/exp/expmake/build/gnucoresrc/build/coreutils/gnulib-tests' make[2]: Entering directory `/opt/exp/expmake/build/gnucoresrc/build/coreutils/gnulib-tests' make libtests.a test-alloca-opt test-argmatch test-arpa_inet test-atexit test-binary-io test-c-ctype test-c-strcasecmp test-c-strncasecmp test-canonicalize test-closein test-md5 test-dirname test-fcntl test-fflush test-filenamecat test-fpending test-fpurge test-freadahead test-freading test-frexp test-frexpl test-fseeko test-fseterr test-ftello test-getaddrinfo test-getdelim test-getline test-gettimeofday test-i-ring test-iconv test-inttypes test-isnan test-isnanf test-isnanl-nolibm test-lseek test-malloca test-math test-mbscasecmp test-netinet_in test-printf-frexp test-printf-frexpl test-signbit test-snprintf test-stat-time test-stdbool test-stdint test-stdio test-stdlib test-strerror test-string test-sys_socket test-sys_stat test-sys_time test-time test-unistd test-uc_width test-vasnprintf test-vasprintf-posix test-vasprintf test-vfprintf-posix test-vprintf-posix test-wchar test-wctype test-wcwidth test-xfprintf-posix test-xprintf-posix test-xstrtoimax test-xstrtol test-xstrtoul test-xstrtoumax test-yesno make[3]: Entering directory `/opt/exp/expmake/build/gnucoresrc/build/coreutils/gnulib-tests' make[3]: `libtests.a' is up to date. make[3]: `test-alloca-opt' is up to date. make[3]: `test-argmatch' is up to date. make[3]: `test-arpa_inet' is up to date. make[3]: `test-atexit' is up to date. make[3]: `test-binary-io' is up to date. make[3]: `test-c-ctype' is up to date. make[3]: `test-c-strcasecmp' is up to date. make[3]: `test-c-strncasecmp' is up to date. make[3]: `test-canonicalize' is up to date. make[3]: `test-closein' is up to date. make[3]: `test-md5' is up to date. make[3]: `test-dirname' is up to date. make[3]: `test-fcntl' is up to date. make[3]: `test-fflush' is up to date. make[3]: `test-filenamecat' is up to date. make[3]: `test-fpending' is up to date. make[3]: `test-fpurge' is up to date. make[3]: `test-freadahead' is up to date. make[3]: `test-freading' is up to date. make[3]: `test-frexp' is up to date. make[3]: `test-frexpl' is up to date. make[3]: `test-fseeko' is up to date. make[3]: `test-fseterr' is up to date. make[3]: `test-ftello' is up to date. make[3]: `test-getaddrinfo' is up to date. make[3]: `test-getdelim' is up to date. make[3]: `test-getline' is up to date. make[3]: `test-gettimeofday' is up to date. make[3]: `test-i-ring' is up to date. make[3]: `test-iconv' is up to date. make[3]: `test-inttypes' is up to date. make[3]: `test-isnan' is up to date. make[3]: `test-isnanf' is up to date. make[3]: `test-isnanl-nolibm' is up to date. make[3]: `test-lseek' is up to date. make[3]: `test-malloca' is up to date. make[3]: `test-math' is up to date. make[3]: `test-mbscasecmp' is up to date. make[3]: `test-netinet_in' is up to date. make[3]: `test-printf-frexp' is up to date. make[3]: `test-printf-frexpl' is up to date. make[3]: `test-signbit' is up to date. make[3]: `test-snprintf' is up to date. make[3]: `test-stat-time' is up to date. make[3]: `test-stdbool' is up to date. make[3]: `test-stdint' is up to date. make[3]: `test-stdio' is up to date. make[3]: `test-stdlib' is up to date. make[3]: `test-strerror' is up to date. make[3]: `test-string' is up to date. make[3]: `test-sys_socket' is up to date. make[3]: `test-sys_stat' is up to date. make[3]: `test-sys_time' is up to date. make[3]: `test-time' is up to date. make[3]: `test-unistd' is up to date. make[3]: `test-uc_width' is up to date. make[3]: `test-vasnprintf' is up to date. make[3]: `test-vasprintf-posix' is up to date. make[3]: `test-vasprintf' is up to date. make[3]: `test-vfprintf-posix' is up to date. make[3]: `test-vprintf-posix' is up to date. make[3]: `test-wchar' is up to date. make[3]: `test-wctype' is up to date. make[3]: `test-wcwidth' is up to date. make[3]: `test-xfprintf-posix' is up to date. make[3]: `test-xprintf-posix' is up to date. make[3]: `test-xstrtoimax' is up to date. make[3]: `test-xstrtol' is up to date. make[3]: `test-xstrtoul' is up to date. make[3]: `test-xstrtoumax' is up to date. make[3]: `test-yesno' is up to date. make[3]: Leaving directory `/opt/exp/expmake/build/gnucoresrc/build/coreutils/gnulib-tests' make check-TESTS make[3]: Entering directory `/opt/exp/expmake/build/gnucoresrc/build/coreutils/gnulib-tests' FAIL: test-wcwidth == 1 of 1 tests failed Please report to bug-coreutils@gnu.org ==
Re: printf failure on darwin with coreutils-6.9.91
Peter Fales <[EMAIL PROTECTED]> wrote:
> I'm trying to build coreutils-6.9.91 for Mac OS/X (Darwin 10.3)
> and getting test failures from misc/printf. The output of make check
> is attached below. I believe the problem occurs around line 345 of
> src/printf.c which has:
>
> 342 switch (conversion)
> 343{
> 344case 'd': case 'i': case 'o': case 'u': case 'x': case 'X':
> 345 length_modifier = PRIdMAX;
> 346 length_modifier_len = sizeof PRIdMAX - 2;
> 347 break;
>
> On linux PRIdMAX is defined as "lld" but on darwin it is defined as "qd".
> Later on in the block of code around line 331 in lib/parse-printf.c, the
> 'q' case is not handled.
>
> Here's the test log:
>
> make check-TESTS
> make[1]: Entering directory
> `/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc'
> make[2]: Entering directory
> `/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc'
> FAIL: printf.log
Hi Peter,
Thanks for the report!
Would you please post the lib/config.h file that
was generated for that system?
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
printf failure on darwin with coreutils-6.9.91
I'm trying to build coreutils-6.9.91 for Mac OS/X (Darwin 10.3)
and getting test failures from misc/printf. The output of make check
is attached below. I believe the problem occurs around line 345 of
src/printf.c which has:
342 switch (conversion)
343{
344case 'd': case 'i': case 'o': case 'u': case 'x': case 'X':
345 length_modifier = PRIdMAX;
346 length_modifier_len = sizeof PRIdMAX - 2;
347 break;
On linux PRIdMAX is defined as "lld" but on darwin it is defined as "qd".
Later on in the block of code around line 331 in lib/parse-printf.c, the
'q' case is not handled.
Here's the test log:
make check-TESTS
make[1]: Entering directory
`/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc'
make[2]: Entering directory
`/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc'
FAIL: printf.log
===
1 of 1 tests failed
See tests/misc/test-suite.log
Please report it to bug-coreutils@gnu.org
===
=
GNU coreutils 6.9.91: tests/misc/test-suite.log
=
1 of 1 tests failed.
.. contents:: :depth: 2
FAIL: printf.log (exit: 1)
==
+
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/src/printf
--version
printf (GNU coreutils) 6.9.91
Copyright (C) 2007 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 David MacKenzie.
+ . ./../test-lib.sh
++ unset function_test
++ eval 'function_test() { return 11; }; function_test'
+++ function_test
+++ return 11
++ test 11 '!=' 11
+++ pwd
++
test_dir_=/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc
+++ this_test_
+++ echo ././printf
+++ sed 's,.*/,,'
++ this_test=printf
++ . ./../envvar-check
+++ as_unset=unset
+++ envvar_check_failed=0
+++ vars=
_POSIX2_VERSION
BLOCKSIZE
BLOCK_SIZE
CDPATH
COLUMNS
DF_BLOCK_SIZE
DU_BLOCK_SIZE
LS_BLOCK_SIZE
LS_COLORS
POSIXLY_CORRECT
QUOTING_STYLE
SIMPLE_BACKUP_SUFFIX
TABSIZE
TERM
TIME_STYLE
TMPDIR
VERSION_CONTROL
+++ unset _POSIX2_VERSION
+++ eval test '"${_POSIX2_VERSION+set}"' = set
test '' = set
+++ unset BLOCKSIZE
+++ eval test '"${BLOCKSIZE+set}"' = set
test '' = set
+++ unset BLOCK_SIZE
+++ eval test '"${BLOCK_SIZE+set}"' = set
test '' = set
+++ unset CDPATH
+++ eval test '"${CDPATH+set}"' = set
test '' = set
+++ unset COLUMNS
+++ eval test '"${COLUMNS+set}"' = set
test '' = set
+++ unset DF_BLOCK_SIZE
+++ eval test '"${DF_BLOCK_SIZE+set}"' = set
test '' = set
+++ unset DU_BLOCK_SIZE
+++ eval test '"${DU_BLOCK_SIZE+set}"' = set
test '' = set
+++ unset LS_BLOCK_SIZE
+++ eval test '"${LS_BLOCK_SIZE+set}"' = set
test '' = set
+++ unset LS_COLORS
+++ eval test '"${LS_COLORS+set}"' = set
test '' = set
+++ unset POSIXLY_CORRECT
+++ eval test '"${POSIXLY_CORRECT+set}"' = set
test '' = set
+++ unset QUOTING_STYLE
+++ eval test '"${QUOTING_STYLE+set}"' = set
test '' = set
+++ unset SIMPLE_BACKUP_SUFFIX
+++ eval test '"${SIMPLE_BACKUP_SUFFIX+set}"' = set
test '' = set
+++ unset TABSIZE
+++ eval test '"${TABSIZE+set}"' = set
test '' = set
+++ unset TERM
+++ eval test '"${TERM+set}"' = set
test '' = set
+++ unset TIME_STYLE
+++ eval test '"${TIME_STYLE+set}"' = set
test '' = set
+++ unset TMPDIR
+++ eval test '"${TMPDIR+set}"' = set
test '' = set
+++ unset VERSION_CONTROL
+++ eval test '"${VERSION_CONTROL+set}"' = set
test '' = set
+++ test '' = 1
+++
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/src/mktemp
-d
--tmp=/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc
cu-printf.XX
++
t_=/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc/cu-printf.BxLOnoeLaT
++ trap 'st=$?; cleanup_;
d=/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc/cu-printf.BxLOnoeLaT;
cd
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc
&& chmod -R u+rwx "$d" && rm -rf "$d" && exit $st' 0
++ trap '(exit $?); exit $?' 1 2 13 15
++ cd
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/tests/misc/cu-printf.BxLOnoeLaT
++ diff --version
++ grep GNU
+ fail=0
+
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/src/printf
-- 'foo\n'
+ cat
+ compare out exp
+ diff -u out exp
+ rm -f out exp
+
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/src/printf
'1 %*sy\n' -3 x
+ POSIXLY_CORRECT=1
+
/Volumes/UFS_exp2/exptools/expmake/build/gnucoresrc/build/coreutils/src/printf
'2 \x'
+ echo '2 failed, as expected'
+
/
Maybe a bug!
Why does head accept die option -1 and tail does not, in this same context? $ head -1 LottoDate.txt LottoJahr.txt LottoZahl.txt ==> LottoDate.txt <== 09.10.1955 3 12 13 16 23 41 ==> LottoJahr.txt <== 1955 3 12 13 16 23 41 ==> LottoZahl.txt <== 3 12 13 16 23 41 $ tail -1 LottoDate.txt LottoJahr.txt LottoZahl.txt tail: Option in ungültigen Kontext benutzt - 1 $ LANG=C tail -1 LottoDate.txt LottoJahr.txt LottoZahl.txt tail: option used in invalid context -- 1 I sayed "maybe", but actually I am sure it is a bug! Greetings! Dario Deho Jetzt neu: Der Routenplaner von Tiscali http://www.tiscali.de/trav/routenplaner.html ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
Re: [cp v5.97] --noreply erroneously depreciated
On Dec 21, 2007 4:56 PM, Brian Dessent <[EMAIL PROTECTED]> wrote: > Chris Velevitch wrote: > > > I thought rsync is meant for copying files between machines? In what > > There's no requirement that rsync can only be used between two different > machines. Then why use rsync locally and not cp? > > It did have it, > > until it got depreciated. > > No, it didn't have such an option. Go read those old threads. Brain, I'm referring to the cp command, but it sounds like cp and mv use the same mechanism and that threads you are referring to only talked mv and --reply whereas I searched for cp and --reply. > --reply=no would *only* have worked in those situations where mv would > have prompted the user. That means when -i was also specified and when > stdout was a terminal. But for example if -i wasn't given or mv was > used in a batch/cron situation with stdout redirected it would *not* > have prompted, and thus the file would be overwritten despite the user > giving --reply=no. This was the source of much confusion and the reason > why it the option was deprecated, because it did work in the manner that > people expected. I think I understand the issue. The way I understand it, the command has 2 different behaviours that depends on if it's being run in 'batch mode' or 'interactive mode', 'batch mode' being the case where stdout is redirected and 'interactive mode' where stdout is not redirected. But the problem has arisen because of a third implied mode, 'quasi-batch' mode. 'quasi-batch' mode is when a script is is being run in 'interactive mode', but the author's intention is that it behaves as if it's running in 'batch mode'. The author of a script would test it interactively and discover that it wants to interact with them because there exists a file of the same name in the destination. So, they put in options that suppresses the interaction and to get the desired effect. In this case the desired effect is to unconditionally keep the existing file. However these options are only 'interactive mode' options and understandably only make sense and only work in 'interactive mode'. There are no 'batch mode' option to unconditionally keep the existing file in the destination. So when the script is really run in 'batch mode' it fails to work the way the author intended it to work because of the missing 'batch mode' functionality. I think the confusion really arises from the fact that there is functionally that only exists in 'interactive mode' when it should have existed in both modes. As as result of depreciating the functionality, any old scripts relying on it are now broken. Chris -- Chris Velevitch Manager - Sydney Flash Platform Developers Group m: 0415 469 095 www.flashdev.org.au ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
