Re: ls and chmod broken on Solaris 9 - ACL problem?

Tim Bishop <[EMAIL PROTECTED]> writes: > We've discovered a bug in the ACL handling on Solaris 9. It noticably > breaks ls and chmod. Thanks for reporting it. I can't reproduce the bug with Solaris 9 if I used coreutils test version 5.3.0

Re: [bug-gnulib] Re: nit in strftime.c

rately. Come to think of it, perhas the "return 0" below should be an abort()? 2005-03-15 Paul Eggert <[EMAIL PROTECTED]> * strftime.c (my_strftime): Prepend space to format so that we can reliably distinguish strftime failure from empty output on POSIX

Re: 'cp -lL' behaviour conflicts with documentation

Eric Blake <[EMAIL PROTECTED]> writes: > $ touch a > $ ln -s a b > $ ln b c # Bug: c should be a hard link to a, not b > $ ls -l a b c > -rw-r--r-- 1 eblake None 0 Mar 15 19:04 a > lrwxrwxrwx 2 eblake None 1 Mar 15 19:04 b -> a > lrwxrwxrwx 2 eblake None 1 Mar 15 19:04 c -> a I agree that

Re: ls and chmod broken on Solaris 9 - ACL problem?

Tim Bishop <[EMAIL PROTECTED]> writes: > That's rather strange. I wonder would could make it different on my > system compared to yours? I looked at it again, and it appears that the problem was that I ran my test on an NFS file system (served by a Solaris 8 box). When I reran the test on a loca

Re: [Patch] Adding examples to the man pages

"Dave Gilbert (Home)" <[EMAIL PROTECTED]> writes: >> My kneejerk reaction is that I like the idea of adding examples, but >> I'd rather see them added to the output of "--help" >> We should also add them to doc/coreutils.texi. > > Hmm - if you can suggest a good way to do this then I'd be happ

Re: [Patch] Adding examples to the man pages

"Dr. David Alan Gilbert" <[EMAIL PROTECTED]> writes: > the issue is how to include examples in the help text > and let them be formatted appropriately for the man page (e.g. > highlighting the fixed text and user supplied text). You can see an example (ahem :-) of that here: http://www.gnu.org/s

nohup patches for POSIX conformance and manual clarification

nd the implementation, I found a couple of deviations from POSIX in this area, and a file descriptor leak, and a couple of very minor internal coding infelicities, so this patch fixes them as well. Thanks for reporting the problem. 2005-03-18 Paul Eggert <[EMAIL PROTECTED]> * NEWS: noh

Re: nit in strftime.c

In <http://lists.gnu.org/archive/html/bug-gnulib/2005-03/msg00136.html> I wrote: > Come to think of it, perhas the "return 0" below should be an abort()? On further thought it's probably better just to ignore the bogus format, so I installed this (in both gnulib and coreu

"pr -D FORMAT" fixes, to match "date +FORMAT"

effect of removing a portability assumption when strftime returns zero. 2005-03-18 Paul Eggert <[EMAIL PROTECTED]> * NEWS: pr -D "FORMAT" now accepts the same formats that date +"FORMAT" does. * src/pr.c: Include strftime.h, timespec.h. (init_h

Re: "pr -D FORMAT" fixes, to match "date +FORMAT"

Jim Meyering <[EMAIL PROTECTED]> writes: > I've made this additional change so pr builds once again. Thanks. I had forgotten to check src/Makefile.am in. Sorry about that. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mai

Re: [Patch] Adding examples to the man pages

"Dr. David Alan Gilbert" <[EMAIL PROTECTED]> writes: > help2man hasn;t done any bold/italicising of the parameters; > I guess that is OK, but it is not particularly nice and doesn't > follow the recommendations for man pages. Is there something > I'm missing to get help2man to do a nicer job? So

Re: "pr -D FORMAT" fixes, to match "date +FORMAT"

Jim Meyering <[EMAIL PROTECTED]> writes: > - sprintf (buf, "%ld.9d", (long int) s, ns); > + sprintf (buf, "%ld.%09d", (long int) s, ns); Ouch. Thanks for catching this. > do you know how to create a file with > e.g. 64-bit st_mtime "touch -d @9223372036854775807 /tmp/foo" should do i

sync from gnulib to coreutils

ne them? 2005-03-20 Paul Eggert <[EMAIL PROTECTED]> * config/config.rpath, lib/gettext.h, lib/regex.c, lib/setenv.c, lib/vasprintf.c: m4/gettext.m4, m4/inttypes.m4, m4/isc-posix.m4, m4/lib-link.m4, m4/nls.m4, m4/onceonly.m4, m4/po.m4: Sync from gnulib.

memcasecmp change imported from gnulib

I installed this into coreutils. Somehow I missed it in my previous pass comparing gnulib to coreutils. 2005-03-21 Paul Eggert <[EMAIL PROTECTED]> Another change imported from gnulib. * memcasecmp.m4 (gl_MEMCASECMP): Renamed from gl_FUNC_MEMCASECMP. All uses c

replacing m4/onceonly.m4 with m4/onceonly_2_57.m4

27;t anticipate here please let me know and I'll undo the change. Here's the patch. Only the ChangeLog entry is new; everything else is simply a copy of gnulib. 2005-03-21 Paul Eggert <[EMAIL PROTECTED]> * onceonly.m4: Remove. * onceonly_2_57.m4: Add. Thi

Re: date zh_TW.Big5 +%P

Abel Cheung <[EMAIL PROTECTED]> writes: > If you can provide me any info about the problem (such as link or > discussion), I'd be glad to fix it; Here's the original bug report: http://lists.gnu.org/archive/html/bug-coreutils/2005-03/msg00010.html > I guess I won't submit patch; I'd want to su

Re: ls -l column alignment RHEL (4.5.3)

"Rob" <[EMAIL PROTECTED]> writes: > Is the output of ls -l supposed to be aligned as far as the timestamp and > filenames columns are concerned Yes. This is fixed in a different way, starting with coreutils 5.1.0. ___ Bug-coreutils mailing list Bug-

Re: [patch] who and stale utmp entries

Tim Waugh <[EMAIL PROTECTED]> writes: > Here is a patch to prevent the who(1) command showing stale utmp > entries of user logins. That patch has a problem when process-IDs are reused. Can you please explain more what is going on here? As I understand it, "users" and "pinky" do not suffer from

Re: md5sum

"Wilson, Jessica" <[EMAIL PROTECTED]> writes: > Is there an updated version to the code I can download? When executing > on a 2GB or larger file the checksum does not work. Do you know where I > could possibly get a later version of this code? ftp://ftp.gnu.org/gnu/coreutils/coreutils-5.2.1.tar

Re: file size listings in GnuWin32 coreutils 5.2.1 doesn't seem right

Thanks for your very detailed bug report. I can't reproduce the problems you mentioned with coreutils 5.3.0 (a test version) on Debian GNU/Linux 3.0, so for now I'll assume that the bugs are either fixed, or are specific to your platform. Have you contacted the people who ported the package to yo

Re: [patch] who and stale utmp entries

Tim Waugh <[EMAIL PROTECTED]> writes: > However, perhaps the extra check should be omitted if FILE is > specified. OK, thanks for explaining it. Can you please try the following patch instead? It tries to do the right thing in that case. It also checks for bogus signal numbers (i.e., nonpositi

Re: color support for TERM=cygwin

glish. Jim, what do you think? Is the following minor patch worth the hassle? It does save a couple of hundred bytes in the dircolors executable, but its main advantage to my mind is that it shortens the code by about 30 lines and removes some casts. 2005-03-25 Paul Eggert <[EMAIL PROTECTED]>

clarification of NUL in coreutils documentation

I installed the following to try to clarify terminology about NUL versus null bytes versus null characters in the coreutils documentation. 2005-03-26 Paul Eggert <[EMAIL PROTECTED]> * coreutils.texi: Clarify NUL vs null byte vs null character. --- coreutils.texi.~1.245.~ 2

Re: Tail not accepting -c 123 anymore?

have done? Could be a bit of both. If Novell has changed the default _POSIX2_VERSION in , this will cause the default coreutils behavior to change. Another possibility is that you've run afoul of this change: 2004-09-23 Paul Eggert <[EMAIL PROTECTED]> * src/tail.c (parse

Re: Tail not accepting -c 123 anymore?

Mike Hearn <[EMAIL PROTECTED]> writes: > That sounds like the one, yes. Though 5.3.0 doesn't seem to show it. Odd; it shows it for me. $ _POSIX2_VERSION=199209 tail -c 123 tail: cannot open `123' for reading: No such file or directory $ tail --version | head -n 1 tail (GNU coreutils) 5.3.0 > I

Re: color support for TERM=cygwin

Eric Blake <[EMAIL PROTECTED]> writes: > Any reason the terminal names aren't sorted in any particular order? I think the "popular" ones are first, then the rest alphabetized. But I'm guessing. > This fact adds all the more impetus to improving the info pages to > describe the dircolors input f

Re: [patch] who and stale utmp entries

Tim Waugh <[EMAIL PROTECTED]> writes: > Yes, this works very well. Thanks! You're welcome. I installed the following slightly-modified patch: it updates m4/readutmp.m4 as well, and it adds another check for size_t overflow. 2005-03-30 Paul Eggert <[EMAIL PROTECTED

readutmp patch for hosts without UTMP_NAME_FUNCTION

The previous patch I installed was incomplete: it didn't handle ancient hosts without any UTMP_NAME_FUNCTION. I installed the following to fix this. While I was at it, I noticed that the code won't work if the utmp file is not a regular file, so I fixed that as well. 2005-03-30 P

Re: date in core utils

Rene de Zwart <[EMAIL PROTECTED]> writes: > 1)date --date="19370701" +"%Y%m%d" > gives 19370630 I can't reproduce this bug in my environment (GNU coreutils 5.3.0, Debian GNU/Linux 3.0r1). Perhaps the bug has been fixed in 5.3.0? You can check this by building 5.3.0 and running its "date

Re: mktexpk: non-POSIX compliant use of "tail"

[EMAIL PROTECTED] (Karl Berry) writes: > tail -1 works for me with coreutils 5.3.0. Whether that works depends on (1) _POSIX2_VERSION in the environment, (2) explicit configuration options by the installer, and (3) _POSIX2_VERSION in , in descending order of importance. On my coreutils 5.3.0 inst

Re: bug in the unix join command or maybe in the sort command

Robert Castelo <[EMAIL PROTECTED]> writes: > if i followed this right, xmemcoll is called at line 1536 of sort.c > which calls memcoll at line 45 of xmemcoll.c which calls strcoll at line > 47 of memcoll.c. I assume we're talking about coreutils 5.2.1 here? I don't remember. Two things. First,

Re: date in core utils

Rene de Zwart <[EMAIL PROTECTED]> writes: > I debbuged date from coreutils 5.3.0 and got > get_date (&when, datestr, NULL); > with datestr="19370701" > returned invalid date > > So it is at a different level than date. But get_date is shipped as part of coreutils 5.3.0, so if it is a bug in

Re: coreutils-5.2.1 and coreutils-5.0

Warren L Dodge <[EMAIL PROTECTED]> writes: > I am using coreutils-5.0 and found that uname -a has unknown in two of the > fields where /bin/uname -a has proper information Can you find out how /bin/uname does it, on your host? You may need to look at its source code, or strace it. My /bin/uname

Re: coreutils-5.2.1 and coreutils-5.0

Warren L Dodge <[EMAIL PROTECTED]> writes: > Here is an strace. I don't have access to the sources. If you know who generated the software distribution operating on your servers, then you should be able to get the sources from them. The strace output says /bin/uname read /proc/cpuinfo, but I do

Re: date in core utils

Rene de Zwart <[EMAIL PROTECTED]> writes: > Probably the time in the Netherlands was adjusted from one standard to > another standard in 1937. Yes, that's it. The time stamp 1937-07-01 00:00:00 is not valid in the Netherlands, since the clocks gained 27.87 seconds then, and jumped fr

Re: Multiple field sort bug

Jane Marie Lin <[EMAIL PROTECTED]> writes: > Do you know if there is any depencies with sort that might have gone > wrong when I installed things? Usually with this sort of thing it's a locale issue. What is the output of the "locale" command on both hosts? What happens if you set LC_ALL="C" in

Re: coreutils-5.2.1 and coreutils-5.0

Warren L Dodge <[EMAIL PROTECTED]> writes: > Here is uname.c from the redhat release we use. That uname.c is identical from that of coreutils 4.5.3. Your /bin/uname evidently comes from different sources; to fix GNU uname to behave like it, you'll have to find out exactly how it works. ___

Re: bug in the unix join command or maybe in the sort command

Robert Castelo <[EMAIL PROTECTED]> writes: > q.txt==(tab-separated columns) > aa value-aa > a value-a > === > both versions 5.2.1 and 5.3.0 output > > aa value-aa > a value-a > > when sorting over the entire line: > > sort q.txt > > or more specifically: > > sort

Re: dd hangs with SIGINT

Guillaume Chazarain <[EMAIL PROTECTED]> writes: > With recent linux distributions (using NPTL), dd can hang waiting on > a futex when being killed. I'm not quite sure how to parse that, but it sounds like a problem with some part of the system other than "dd", not with "dd" itself. When "dd" get

Re: install(1) man page

Rene Kapeller <[EMAIL PROTECTED]> writes: > Too bad, it's realy useful. No way to make that a standard option of > install(1)? If someone contributes a clean patch to implement it, I'd volunteer to review it. The final decision would be Jim's, though. __

Re: mktexpk: non-POSIX compliant use of "tail"

[EMAIL PROTECTED] (Karl Berry) writes: > What harm can there be in *GNU* tail always accepting tail -10? I am becoming more inclined to agree with you. I don't know about Jim, though. Part of the motivation for removing support for usages not allowed by POSIX was conformance. But part of it, t

Re: [Patch] Adding examples to the man pages

it before (since "ln invocation" already does this), but after might make sense too. Here is a proposed patch illustrating the sort of format I was thinking of. Jim, is this worth installing as-is as an "example of how to do examples", or do you want some more changes to the

Re: Command "Who" does not work properly in Linux console

Amir Marani <[EMAIL PROTECTED]> writes: > I am using Mandrake Linux 10. I have a problem when I am using > command 'who' in comsole it does not gives any out put. But when I > gives command: "prompt>who -a" it gives out put. Possibly your /var/run/utmp file (or whatever it is called on your syste

Re: bug in date(1)

ug. Thanks for reporting that. The empty string is supposed to stand for the start of the current day -- that's in the documentation. I installed this patch, to both coreutils and gnulib. 2005-04-04 Paul Eggert <[EMAIL PROTECTED]> * lib/getdate.y (parser_control): rels_se

Re: chmod +++++++++x file

Dan Jacobson <[EMAIL PROTECTED]> writes: > I found I could get away with chmod +x file. Perhaps catch it. POSIX requires support for that. It's weird, but it's probably not worth diagnosing. ___ Bug-coreutils mailing list Bug-coreutils@gnu.or

Re: nice: error in help-text about new format

Thanks for your bug report. That hint is removed in coreutils 5.3.0, which you can get here: ftp://alpha.gnu.org/gnu/coreutils/coreutils-5.3.0.tar.gz so the confusion shouldn't occur. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.

Re: [Patch] Adding examples to the man pages

Jim Meyering <[EMAIL PROTECTED]> writes: > I could go either way when the single sentence of exit-status > documentation is all that follows the option descriptions. > But when there's more than that one sentence, I have a slight > preference for putting the examples at the end. Then let's do the

Re: dd hangs with SIGINT

There is a similar problem in csplit.c. The simplest fix there is to not print an error message when an interrupt occurs and a file can't be removed afterwards, and I've prepared a draft patch to do that, which I'd like to test a bit more before installing. The resulting csplit program still call

Re: bug in chown --dereference

G&RV <[EMAIL PROTECTED]> writes: > I run into the same kind of bug today trying to change the ownership > of a directory by running "chmod" on a symlink refering to it. > The problem is a bit different from the one reported by MÃller, Folkhard > but still very close. > > If the referenced file ALR

adding bulletproofing for cases where stdin, stdout, stderr are closed

they often rely on a weird scenario like an I/O error causing a diagnostic to be put into a file unexpectedly. I can't promise that I caught all the troublesome scenarios, but I patched all the ones I found. 2005-04-11 Paul Eggert <[EMAIL PROTECTED]> Add bulletproofing for c

Re: chown man page: colon vs. dot

. I also noticed that the code and documentation doesn't use consistent terminology ("user ID" or "UID" or "uid" or "user id"?) so I standardized on "user ID" (the POSIX terminology) and installed this: 2005-04-11 Paul Eggert <[EMAIL PROTE

Re: Command "Who" does not work properly in Linux console

Amir Marani <[EMAIL PROTECTED]> writes: > The attached file is the one you asked me to send you. Thanks. That file does not show anybody logged in, which is why "who" reports nothing. If someone is actually logged in, you need to find out what this information isn't reflected in the file. ___

Re: Command "Who" does not work properly in Linux console

Amir Marani <[EMAIL PROTECTED]> writes: > I am logged in as a user say" amir".It has to show amir has logged in > ,but it doesn't show.MY question was that this > problem related to system file are not,but you didn't give me proper > or very clear answer. The file that you sent doesn't say "amir"

Re: [bug-gnulib] problem with getdate

ccur even with the UTC time stamps in the test cases. I installed this further patch. 2005-04-13 Paul Eggert <[EMAIL PROTECTED]> * getdate.y (zone): Allow relunit_snumber after tZONE, so that "UTC +1 second" continues to work. Problem reported by Dmi

Re: cygwin failing tests/mv/mv-special-1

Thanks for that bug report. I installed this patch: does it fix both your problems? 2005-04-14 Paul Eggert <[EMAIL PROTECTED]> Fix test suite problems reported by Eric Blake on Cygwin. * tests/mv/mv-special-1: Ignore chatter about when files are removed, since

Re: Bug#304556: file permissions race in mkdir, mknod, mkfifo (CAN-2005-1039)

My kneejerk reaction is that it's not worth making this change. The attack in question will work against almost any program that is operated in an insecure directory, including the "chmod" program itself. It'd be a real pain to work around this problem in all applications, one at a time, and it's

Re: testsuite portability nit

I installed the following patch, in the hopes that it'd be relatively simple and easy to maintain. It skip the tests on the platforms with the contrary-to-POSIX glitches. 2005-04-17 Paul Eggert <[EMAIL PROTECTED]> Work around a couple of "make check" failure

Re: chown man page: colon vs. dot

Dan Jacobson <[EMAIL PROTECTED]> writes: > P> I think it's better not to mention dot insted. Dot is no longer > P> portable (as per POSIX-2001). > > Well, mention that dot is deprecated, or else users can't tell if it > is too old, or too new, when encountering it. That issue is already covered

Re: testsuite portability nit

t(2) succeeded Sorry, I wasn't aware of the complexity of this particular problem. I installed the following patch to work around this glitch. 2005-04-18 Paul Eggert <[EMAIL PROTECTED]> * tests/install/basic-1: Use "cat", not "test", to test for .

renamed fetish to coreutils in a few more places

I installed the following patch to remove fetish to coreutils in a few more places. The only nontrivial bit here is removing fetish.sf.net from some URL lists; I assume that's obsolete now? 2005-04-18 Paul Eggert <[EMAIL PROTECTED]> "fetish" -> "

Re: Failed tests for gnu coreutils 5.2.1

"J.D. Baldwin" <[EMAIL PROTECTED]> writes: > Note that neither -n or -G works with Solaris /usr/bin/id Thanks for your bug report. However, that shell script actually tries this command: (id -nG || /usr/xpg4/bin/id -nG) 2>/dev/null Does this not work, when run as root on your host? It works fo

another "id -n" -> plain "id" change

I installed this: 2005-04-19 Paul Eggert <[EMAIL PROTECTED]> * tests/chmod/setgid: Use numeric group ids, not symbolic group names, since the latter can have shell metacharacters in them (e.g., spaces). This follows up to the 2005-01-17 patch, which misse

Re: cygwin failing tests/mv/mv-special-1

es, even while preserving the inode if the > rename did not cross devices, as shown below). So mv/mv-special-1 > should probably also add a check that mv-null is still a fifo in its new > home. Thanks for reporting that; I installed the following patch to try to fix this. 2005-04-19 Pa

Re: cygwin failing tests/mv/mv-special-1

I installed the following slightly-more-conservative patch: 2005-04-19 Paul Eggert <[EMAIL PROTECTED]> * tests/mv/setup (dot_mount_point): Use stat -L, in case the directory is actually a symbolic link. Problem reported by Eric Blake. --- setup 14 Apr 2005 20

removal of the last vestiges of "fetish" from coreutils

I installed this patch. I think it removes the last instances of the word "fetish" from coreutils CVS, except for ChangeLog entries. 2005-04-20 Paul Eggert <[EMAIL PROTECTED]> "fetish" -> "coreutils" in more places. * tests/Cor

Re: testsuite portability nit

UILD_SRC_DIR. It shouldn't be needed here, though, right? The code is already using $pwd/../../src for that purpose. 2005-04-20 Paul Eggert <[EMAIL PROTECTED]> Port test cases to Microsoft-Windows-related environments, following suggestions from Eric Blake.

Re: update: chown fails to ignore symbolic links during recursive directory traversals

Mark Brand <[EMAIL PROTECTED]> writes: > In case anybody was following this issuse (original subject line "chown > fails to ignore symbolic links during recursive directory > transversals[sic]"), SuSE has released a fix for their coreutils RPM: Has this problem (whatever it is) been fixed in core

fixed obscure mkdir, mkfifo, mknod permissions problem

gument is immaterial since "install" runs with umask(0). So I'm inclined to remove the second argument, since I think its presence contributed to this permissions bug. I'll ask about this on bug-gnulib first, though. 2005-04-22 Paul Eggert <[EMAIL PROTECTED]> * NE

Re: Bug and feature request in nice

That's perfectly possible as many > tools already do that. OK, but is there any precedent for that? I thought this was renice's job. 2005-04-22 Paul Eggert <[EMAIL PROTECTED]> * src/nice.c (main): Report proper program name when getopt finds trouble.

fix for yet another minor nohup POSIX glitch

I installed this: 2005-04-22 Paul Eggert <[EMAIL PROTECTED]> * src/nohup.c (main): If getopt fails, exit with status 127, not status 1. POSIX requires this. * NEWS: Document this. --- NEWS22 Apr 2005 23:51:34 - 1.277 +++ NEWS23 Apr 2005

Re: touch -d 20000000

Dan Jacobson <[EMAIL PROTECTED]> writes: > $ touch -d 2000 k > $ ls -og k > -rw-r--r-- 1 0 1999-11-30 00:00 k Thanks, but that bug is fixed in coreutils 5.3.0. ftp://alpha.gnu.org/gnu/coreutils/coreutils-5.3.0.tar.gz ___ Bug-coreutils mailing li

documentation fix to match recent mkdir, mkfifo, mknod fixes

I installed this to fix the documentation to match the recent code fixes. The "install invocation" fixes are just to make it more regular 2005-04-23 Paul Eggert <[EMAIL PROTECTED]> * doc/coreutils.texi (install invocation): Use a= instead of 0 for the point of

Support for `tail -10', etc. even when conforming to POSIX.1-2001

esolved to everyone's satisfaction. Thanks to everyone who pushed the POSIX committee (and me :-) to get this matter clarified and resolved. 2005-04-26 Paul Eggert <[EMAIL PROTECTED]> Restore support for usages like "head -1" and "tail -1",

Re: Support for `tail -10', etc. even when conforming to POSIX.1-2001

Thanks for your review. Eric Blake <[EMAIL PROTECTED]> writes: > Hmm - if coreutils ever supplies renice, that would also be a candidate > for supporting obsolescent usages. Yes, I suppose so. > Also, the Austin group minutes mention that uniq could support '+' > as an option separator That is

Re: [bug]rm.c pwd.c getcwd.c don't work correctly in MSYS

heromyth <[EMAIL PROTECTED]> writes: heromyth <[EMAIL PROTECTED]> writes: > I have compiled a copy of coreutils CVS with msysDVLPR-1.0.0-alpha of > MSYS. After I run 'rm -r *' to delete a directory with subdirectory, I > deleted everything in the directory except for itself. > > When I trace into

chmod etc. documentation patch

While I was in the chmod-fixing business, I discovered some minor glitches in the documentation, and fixed them as follows. Most of this is about modernization of the sticky bit, and clarification of which things are POSIX and which are GNU extensions. 2005-04-28 Paul Eggert <[EMAIL PROTEC

including file-type.h first

I installed this minor cleanup to allow programs to include file-type.h first: 2005-04-28 Paul Eggert <[EMAIL PROTECTED]> * file-type.c: Include file-type.h first. * filetype.h: Don't assume was included first. Index: lib/

more fixes for symbolic permissions string bugs

k goodness. :-) I installed this patch. 2005-04-28 Paul Eggert <[EMAIL PROTECTED]> * NEWS: Document fixes described below. * src/chmod.c (change, umask_value): New static vars. (reference_file): Move this static var to inside "main". (process_file, proc

Re: Additional feature for the seq command

Axel Liljencrantz <[EMAIL PROTECTED]> writes: > seq a 3 h > > should output > > a > d > g Hmm, suppose someone wants the characters from '9' through ';'? What about non-ASCII locales? What order should the characters appear? ___ Bug-coreutils mailin

Re: date zh_TW.Big5 +%P

Abel Cheung <[EMAIL PROTECTED]> writes: > So if coreutils maintainers think this is not a bug, or "this is your own > business", then please tell me so that I can ask localization teams > to think about other way to work around it. No, it's definitely a bug in strftime: it should not be using tol

modechange improvements to catch "chmod +1", etc.

I installed this as a minor simplification to modechange. The only change visible to coreutils users is that a few invalid usages like "chmod +1 file" and "chmod ' 1' file" are now caught. 2005-05-01 Paul Eggert <[EMAIL PROTECTED]> * NE

update test cases to match new _POSIX2_VERSION behavior

I installed this: 2005-04-29 Paul Eggert <[EMAIL PROTECTED]> * tests/head/Test.pm: Don't set _POSIX2_VERSION; no longer needed. * tests/misc/split-fail: Likewise. * tests/pr/Test.pm: Likewise. * tests/sort/Test.pm: Fix comment to match new behavi

Re: Additional feature for the seq command

Axel Liljencrantz <[EMAIL PROTECTED]> writes: > I did this since the way I want to use this feature is for doing > things with sets of data that is split in multiple files with names > like sampa.asc, sampb.asc, sampc.asc, etc.. Aha! That helps to explain things. In that case, why not make this

Re: ls -F indicators

Eric Blake <[EMAIL PROTECTED]> writes: > bash TAB-completion with readline's `set visible-stats on' uses '%' > for character-special devices and '#' for block-special devices. Aack. FreeBSD "ls" uses "%" for whiteouts, and nothing for special files. I'd rather not have gratuitous incompatibilit

Re: Another testsuite nit: `set -'

CLs propagates ACLs to the new directory (as a > byproduct of how Windows NTFS permissions are mapped to POSIX > semantics). Thanks for catching these. I installed the following somewhat-different patch: 2005-04-29 Paul Eggert <[EMAIL PROTECTED]> The following was partly

Re: date zh_TW.Big5 +%P

Abel Cheung <[EMAIL PROTECTED]> writes: > About detection of multibyte string, is there any > better method than retrieving LC_TIME and > lookup the charset inside a predefined array > containing known multibyte charset? Sorry, I don't quite follow, but I was assuming that we could do something s

sync from gnulib to coreutils

I installed this into coreutils: 2005-05-01 Paul Eggert <[EMAIL PROTECTED]> * build-aux/config.guess, build-aux/config.sub, build-auxtexinfo.tex, lib/mbswidth.c, lib/regex.c, lib/strtol.c, m4/getpass.m4, m4/gettext.m4: Sync from gnulib. Index: build-aux/config

Re: ls -F indicators

also be confused by that. We're talking about a rarely used option here so I don't think it's that important to name it (other than avoiding confusion with other options). How about --indicator-style='slash'? I installed this: 2005-05-02 Paul Eggert <[EMAIL PROTECTED

"chmod -w file" now complains if file is still writable afterwards

le" to silently adjust itself to behave like "chmod a-w file"; POSIX allows that too. If you think that's better I could install a patch along those lines instead. 2005-05-04 Paul Eggert <[EMAIL PROTECTED]> * NEWS: chmod -w now complains if it differs from chmod

Re: "chmod -w file" now complains if file is still writable afterwards

[EMAIL PROTECTED] (Eric Blake) writes: > Other questions, though - with our extension options, should we interpret > `chmod -w a+x foo' the same as `chmod -- -w ./a+x ./foo' or like > `chmod -- -w,a+x ./foo'? It's been the former for a while; I guess that's OK. > POSIX allows modes that look lik

Re: mkdir -p and network drives

ain it.) That being said, it can't hurt to add the following minor workaround, (which would work on Domain OS anyway :-), so I installed it. 2005-05-05 Paul Eggert <[EMAIL PROTECTED]> * makepath.c (make_path): chdir to "//", not "/", if the file name

Re: mkdir -p and network drives

Eric Blake <[EMAIL PROTECTED]> writes: > //MACHINE currently generates ENOENT, whether or not there is a > server on the network with that name, and mkdir(2), stat(2), and > chdir(2) with an argument of "//MACHINE" fail. That's certainly a hassle. Let's not worry about going through zillions of

Re: [bug-gnulib] Re: getopt and Solaris 10

Derek Price <[EMAIL PROTECTED]> writes: > I prefer door #2. Trivial patch attached: Thanks, but I'd rather use AC_CHECK_DECL, so I installed this instead, into both coreutils and gnulib. Does it work? 2005-05-05 Paul Eggert <[EMAIL PROTECTED]> * lib/getopt.m4 (g

Re: mkdir -p and network drives

Eric Blake <[EMAIL PROTECTED]> writes: >> + if (do_chdir && dirpath[0] == '/') >> +{ >> + /* POSIX says "//" might be special, so chdir to "//" if the >> + file name starts with exactly two slashes. */ >> + char const *root = "//" + (dirpath[1] != '/' || dirpath[2] == '

Re: mv -f may remove the destination file

Urs Thuermann <[EMAIL PROTECTED]> writes: > $ strace mv foo bar Hmm, your email's "Subject:" line says "mv -f" but this strace doesn't. I'll assume for now that you meant to write about plain "mv", not "mv -f". > lstat64("bar", 0xb904) = -1 ENOENT (No such file or directory) >

Re: date zh_TW.Big5 +%P

Abel Cheung <[EMAIL PROTECTED]> writes: > This means determining the value of mblen() or mbrlen() > 1 > for all chars in am_pm, if this is true then the string is multibyte > and don't impose tolower/toupper on it? Yes, though you'd need to impose the equivalent of tolower. (And this could change

Re: mv -f may remove the destination file

[EMAIL PROTECTED] (Bob Proulx) writes: > I think the reason for the question might be for what purpose is the > lstat() call there? It is there to tell if the destination is a > directory and if so then it converts the rename to a rename to a > file in the subdirectory, also as required by POSIX.

Re: DD converts LF -> CR / LF

That looks pretty complicated. How about if we just rely on "open" and "fcntl" to do the work? If they don't work, they should. I installed this into coreutils: 2005-05-06 Paul Eggert <[EMAIL PROTECTED]> * NEWS: dd has new iflag= and oflag= flags &qu

Re: mkdir -p and network drives

Igor Pechtchanski <[EMAIL PROTECTED]> writes: > There's always Pierre's solution of doing minimal support for stat()ing > '//' and '//MACHINE', though... Yes, that's the basic idea. That's the only thing that makes sense here. ___ Bug-coreutils maili

Re: mkdir -p and network drives

Christopher Faylor <[EMAIL PROTECTED]> writes: > Except that it can't be made to work correctly due to a bash bug. Which Bash bug is that? Bash bugs can be fixed. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listi

<    1   2   3   4   5   6   7   8   9   10   >