bug#6353: cp and mv with single wild card argument acts as if multiple arguments were entered.

If you execute "cp /path/*" the command expands the wildcard, and treats the last file as the destination directory. That is at it should be, * is expanded by the shell, not by the command.

Re: diff "--git"

$ diff --git diff: unrecognized option '--git' I think diff should say at this point "real diff, at least up to year 2010, does not have a --git option, you are probably getting that idea from git output" or something. That is what it says, though not in so many words. Having an o

Re: echo -n?

A friend came up with this hack `echo -n\ '; note the space. Which is a bit of a cheat. And `echo -e --\\bn', which alas is not POSIXly.

Re: echo -n?

/bin/echo -e \\x2Dn Alas, -e is not guaranteed by POSIX.

Re: echo -n?

Ah, Bob, you're really no fun! Neither printf, piping to sed or cat are fun solutions. :-) And no, I don't have an ace up my sleeve...

echo -n?

Here is a fun one, how does one output `-n' (literal string) (or any other option that echo accepts) using echo? $ /bin/echo --version|head -n1 echo (GNU coreutils) 8.4 $ /bin/echo -- -n -- -n $ /bin/echo - "-n" - -n $ /bin/echo '-n' $ /bin/echo "-n" $

Re: expr exit status

What are all the exit statuses I need to check just after expr command? Is it only need to check 1 or 2 or 3 for fail condition and zero for success ?else pease specify You only need to check for non-zero exit codes for failure.

Re: Build a single source file under src/

The following might work: make -C src foo.o

Re: head that accepts gz files?

I'm wondering if there is a similar program to 'head' that accepts gz files. (just as zgrep to grep) You can use: zcat foo.gz | head

su.1, hostname.1, and arch.1 missing in tarball

Any program listed in --enable-no-install-program won't get its man pages generated during dist/distcheck, so currently to install those man pages on needs have perl installed to be able to run help2man. Not sure what the best way is to fix this, thoughts?

Re: Pinky command

> Why the name of command was changed from "finger" to "pinky"? I > liked new name, but there may be Some old scripts (copied from > Unix to Linux) in which finger may have used. I suggested finger > as a link to pinky. As far as I know pinky is not a replacement for finger but is

Re: Pinky command

> The list of uids are already public in the /etc/passwd file. That file > is already world readable. Therefore it isn't clear to me how using > another command makes this a vulnerability. Using fingerd, this could disclose login names to remote attackers. This, of course, does no

Re: Tail +N apparent error.

tail +n is a obsolete syntax, and was deprecate in POSIX 1003.1-2001. >From the coreutils manual: | Standards conformance | == | | In a few cases, the GNU utilities' default behavior is incompatible | with the POSIX standard. To suppress these incompatibilities, define | t

Re: (man|info) pages and --help

I'm tempted to say add a one-liner, but there are already *four* lines at the end of even the smallest --help output message, e.g., $ sync --help Usage: sync [OPTION] Force changed blocks to disk, update the super block. --help display this help and exi

Re: (man|info) pages and --help

> Is there anyone who's unaware that --help doesn't provide > complete documentation? I would not expect anyone to *not* know that help output is abridged. But I would rather have them go straight into 'info' than wasting time on 'man', only to be redirected to 'info'. Usually

Re: Problem with Hostname

This command that accepts the -f option is *not* the GNU hostname command. There is a small confusion, there are two versions of GNU hostname. One that supports -f (GNU Inetutils hostname), and one that doesn't (GNU Coreutils hostname). The one in coreutils is not installed by default. May

Re: ls manpage incomplete

>The standard for documentation has been man for longer than >that... It should be complete. > > Maybe for some old UNIX systems, but this has never been the case > for GNU. And many current ones. As for GNU, it isn't a complete system anyways... GNU became complet

Re: ls manpage incomplete

The standard for documentation has been man for longer than that... It should be complete. Maybe for some old UNIX systems, but this has never been the case for GNU. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailma

Re: ls manpage incomplete

What's the justification for putting incomplete information in the manpages that's already available to another text tool on the same package? It is a compromise for users like yourself who expect things to be in man pages (the man pages we produce as really --help formated using troff; i

Re: copyright years: mass-update every January 1

> "migration of coreutils works into the public domain" > > I know of no such plan. I'm refering to the copyright term limits which apply to all works, not a specific plan for coreutils. It doesn't affect it at all, if you use a version of coreutils from 1980, then the copyright

Re: improve INSTALL contents

can you please also read, and follow ? I'm sure you must have missed it because I failed to spam it to three mailing lists. But your repetitions are just as boring as those from everyone else. And get bug-coreutils a

Re: improve INSTALL contents

>In addition, if you use an unusual directory layout you can give >options like @option{--bind...@var{dir}} to specify different >values for particular kinds of files. Run @samp{configure --help} >for a list of the directories you can set and what kinds of files >

Re: improve INSTALL contents

Indeed - I want to be very clear in INSTALL that there are some basics that pretty much any client of this file provide (make, make install), and some options that nice packages provide but which may fail if someone borrowed this file but does follow everything checked by automake's

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

How about this? I took into account Ralf's comments as well. In addition, if you use an unusual directory layout you can give options like @option{--bind...@var{dir}} to specify different values for particular kinds of files. Run @samp{configure --help} for a list of the directories

Re: improve INSTALL contents

>+Depending on the package, the default directory layout chosen during >+...@command{configure} can be altered during subsequent execution of >+...@command{make}. > > A `make install FOO=VAL' should never alter anything in the build > directory. The problem is if y

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

+Depending on the package, the default directory layout chosen during +...@command{configure} can be altered during subsequent execution of +...@command{make}. A `make install FOO=VAL' should never alter anything in the build directory. The problem is if you pass --bindir=/foo to confi

Re: tail +n does not work under Linux?

I have just noticed that 'tail +n' does not seem to work under Linux. Please don't call the GNU system for Linux, Linux is a important part of the system, but it is not the name of it. Linux is the kernel of the GNU system, when people call the whole system for Linux they give none of the p

Re: inetutils ChangeLog doc/Makefile.am doc/inetuti...

After the patch I installed to inetutils [1], I think actually the only problem is that the gnulib 'fdl' module is a moving target. That doesn't really work, as Karl explained, since the main manual needs to be updated manually whenever there is a FDL version update in gnulib. Right

Re: [bug-inetutils] Re: inetutils ChangeLog doc/Makefile.am doc/inetuti...

doc/fdl.texi is removed below If I'm understanding correctly, removing fdl.texi seems wrong to me. I'm supposing it's created dynamically from a copy in gnulib or somewhere now? But the license can't be updated merely by changing that file. The @copying block has to be update

Re: Core-utils 7.2; building only 'su'

> So for maximum portability you should support this in your > package, too. BTW, why do you state that overriding just $prefix > would be "almost always wrong"? In the w32 arena, overriding $prefix at `make install' time is unilaterally *correct*. Why can your staging area not mi

Re: Core-utils 7.2; building only 'su'

>>Hmmm. Would it be worth changing autoconf to make './configure >>--help' state something like the following: >> >>| Some influential environment variables: >>| ... >>| DESTDIRleave unset during configure; allows installation

Re: Core-utils 7.2; building only 'su'

> I tend to agree that INSTALL should either mention DESTDIR (and > probably also V, which now plays a role with new enough > automake), or at least point to the GNU Coding Standards and the > Automake manual overview of the GNU build system. Does anyone > want to beat me to a patch

Re: Core-utils 7.2; building only 'su'

>packages where DESTDIR doesn't work properly. But automake >already does such a good job at providing DESTDIR support >(especially if the user remembered to run 'make distcheck'), >that I think it would be nice if using AM_INIT_AUTOMAKE did >make the ./configure

Re: Core-utils 7.2; building only 'su'

>Hmmm. Would it be worth changing autoconf to make './configure >--help' state something like the following: > >| Some influential environment variables: >| ... >| DESTDIRleave unset during configure; allows installation to >| spec

Re: Core-utils 7.2; building only 'su'

Hmmm. Would it be worth changing autoconf to make './configure --help' state something like the following: | Some influential environment variables: | ... | DESTDIRleave unset during configure; allows installation to | specify a staging area different than t

Re: Core-utils 7.2; building only 'su'

from the ./configure documentation it seems like --prefix=/foo would be preferred to destdir. Not at all! The correct method is to use DESTDIR, if you do: ./configure --prefix=$FOO --exec-prefix=$BAR and then do: make install prefix=$PWD/inst _ALL_ exec_prefix files (i.e. all arch. depen

Re: Core-utils 7.2; building only 'su'

However, I confirmed that "sudo make install prefix=$PWD/inst" did install su into $PWD/inst/bin. Eech, this is what DESTDIR is for... Works very well with coreutils. make install DESTDIR=$PWD/inst ___ Bug-coreutils mailing list Bug-coreutils@g

Re: Mac OS10 bug

say I want to sort on column 3, numericaly, reversed order: sort -nu +2 -3 file > files >From the Coreutils documentation, (coreutils) sort invocation: |On older systems, `sort' supports an obsolete origin-zero syntax | `+POS1 [-POS2]' for specifying sort keys. This obsolete behavior

Re: su command...

> Please, how can I execute the following idea: $ su gimp & > but really in bacground? I can not figure out what you want to do, but you might try=20 this : if [[ $(grep gimp /etc/passwd | cut -d':' -f1) == "gimp" ]]; then su - gimp; else su -; export DISPLAY=:0.0; gimp &; logout;

Re: Add redirection to "install" for package managers

I hope so. I'll creating that package, including a script named "install", and see if I don't need to patch GNU install. That'll work for many cases. (I plan to use the environment variable is REDIR_DESTDIR.) If it works EXCEPT that too many people invoke /usr/bin/install direc

Re: Feature request: gzip/bzip support for split

I would like to propose a feature that allows to gzip/bzip on its way out during the split and I am also including the patch for the same. I think a better approach would be to add a --on-output-hook=PROGRAM command, then one can call any arbitrary command when split outputs a file. __

Re: better figure out a paperless copyright assignment method

Wait a second, when making a Wikipedia editing contribution we just click on a box below some licence statement. Why can't you guys use that method? Because you don't get nice stickers that way. ___ Bug-coreutils mailing list Bug-coreutils@gnu

Re: (no subject)

I think you posted to the wrong list... Your message seems to relate to the GNU Debugger. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: installing

I am unable to install iTunes 8 with Wine. Half way through the setup "*the installer encountered errors before itunes could be configured" *any help?? Try using amarok or rythmbox. They are much nicer than iTunes, and they are free software! ___

Re: getgid --help

getgid usage is invalid, mentions FILE while really it should be NAME: $ getgid --help Usage: getgid [OPTION]... [FILE]... Prints ID of given group name. --help display this help and exit --version output version information and exit Report bugs to . $ get

Re: making GNU ls -i (--inode) work around the linux readdir bug

> > EVERY application that invokes ls -i is effected. > > Please name one. magicmirror Which nobody uses. Try again; and this time a program that is in common use. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org

Re: Coreutils binary sizes over time

> What is the drop at 9 epoch? That one looks fun; I am > guessing it is the move to glibc 2.x? Yes, it appears to be - the first one is linked against libc.so.5 and an earlier dynamic linker I don't have. This might put a different spin in the size increase, that it is glibc

Re: Coreutils binary sizes over time

Dr. David Alan Gilbert wrote on 27-01-08 01:29: > Hi, > > Out of a bit of boredom (and avoiding trying to fix a VHDL problem) > I decided to graph the sizes of a few of the binaries from coreutils, > as packaged by debian over time (I've included fileutils/shellutils). >

Re: command "ls" bug

i still want to know whether the problem i say is a bug or not!! It isn't a bug. You are telling ln to create a symbolic link that points to itself. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-core

Re: Command line parsing with genparse

FWIW, GNU tar uses argp for parsing arguments. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: Command line parsing with genparse

> Debarshi Ray <[EMAIL PROTECTED]> converted a bunch of tools in > inetutils (http://www.gnu.org/s/inetutils/, > http://sv.gnu.org/p/inetutils/) to use argp instead of > getopt/getopt_long. Some which have quite hairy parsing > semantics, for example ping which uses children parsers

Re: Command line parsing with genparse

Please ignore this message, I sent it a bit early. The correct one is the one with message ID: [EMAIL PROTECTED] ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: Command line parsing with genparse

1. It does a significant part of the work at compile time. So the generated code can be quite simple and fast. It is parsing arguments, it doesn't need to be super fast. As for simplicity, having used argp for alot of things, I all I know is that getopt/getopt_long are a pain. 2. It

Re: Command line parsing with genparse

1. It does a significant part of the work at compile time. So the generated code can be quite simple and fast. I cannot comment which is simpler, since I do not know genparse. But parsing arguments isn't a speed critical task. argp is a wrapper around getopt and getopt_long, and uses th

Re: Command line parsing with genparse

You might be interested in argp (part of glibc and gnulib) which does more or less what you wish to achive, without the need for initial parsing. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: DWIM feature request for cp

Hello, I want to ask the developers what do they think about implementing a way to do "cp -r .* target" (copy files and directories starting with dot) without copying the parent directory ".." (I think that's what the user usually intends to do) Won't work, globs is expanded by the she

Re: basename whitespace bug

when executed with file name containing spaces, basename returns only first part of file name (until space). Try quoting the string. [EMAIL PROTECTED]:~$ basename "/home/ams/frob ni.cate" frob ni.cate Space is treated as a seperator of arguments on GNU and Unixoid systems. __

Re: [PATCH] arch: new program

Oh, and I'm overlooking these: groupsis in the shadow package too idis in the shadow package too On GNU systems, like GNU/Linux, it is only appropriate to install the GNU version of these programs by default. The problem with su is that it requires root access to be

Re: [PATCH] arch: new program

--- /dev/null +++ b/man/arch.x @@ -0,0 +1,6 @@ +[NAME] +uname \- print machine hardware name (same as uname -m) That should be `arch \- print machine ...'. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailma

Re: Don't you think there are too many *sum utilities?

> Why not just: hashsum ALGORITHM [FILE]? A optional hashing > algorithm seems pointless for this. Because on decoding, 'hashsum -c FILE' could be made smart enough to auto-detect the algorithm based on the length of the hash, but only if the algorithm is optional (--md5) rather tha

Re: Don't you think there are too many *sum utilities?

> I don't see any major problem why something like `hashsum > ALGORITHM' wouldn't work though, `md5sum' could be the same as > `hashsum md5'. And then md5sum could be a shell script, or just > a simple program that calls `hashsum md5'. Except that since the *sum utilities operate o

Re: Don't you think there are too many *sum utilities?

> Current stable version of coreutils (6.9) has 8(!) utilities > which somehow compute or/and check a message digest. They are: > 'md5sum', 'sha1sum', 'sha224sum', 'sha256sum', 'sha384sum', > 'sha512sum' and finally 'sum' and 'cksum'. It's already a little > bit confusing and it seem

Re: info cp

> On the linux man page for "cp" one is directed to info cp but > this will not work because info cp describes the C/C++ > preprocessor. This is a known issue with info, aggravated by the fact that man2info insists on listing the shorter link when generating the man page whether

Re: kilo is k and not K

SI does not define what a kilo-byte is, computer scientists do, and they defined it as 1024. Being a CS, I like consistency, and I also happen to like kilo-byte == 1000 bytes. :-) ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://list

Re: kilo is k and not K

when you do ls -l -h one sometimes encounters files which have kilo size. ls -l -h then uses "K" to display this. This is wrong and unallowable. It must be "k". You don't have a choice: it is standarised by the SI system as "k". See for example http://en.wikipedia.org/wiki/SI . St

Re: enhancement bug for ls...

That's probably because you can do all these things with find(1). In any case it's very unlikely that any more single-letter options will be added to the coreutils "ls" because of the likelihood of some conflict with other ls implementations. Not to mention that all single-letter optio

Re: basename sucks

> > Regarding the original query, why not just use awk? Or just use basename with a little xargs added. This seems very readable and obvious to me. echo /home/me/foo | xargs -l basename foo And then zero terminated strings are already supported. printf "/home/me/foo\

Re: basename sucks

> Furthermore, with a --suffix option, we could also allow multiple > command line arguments, another usage case that might prove > useful: > > $ basename --suffix=.h foo.h bar.h It's always fun until somebody puts out an eye by having a file named "--suffix=.h". Handle it t

Re: basename sucks

All great ideas, but who is willing to code them? I think the OP seemed quite motivated for the task. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: basename sucks

Hmm - making basename (and also dirname) a filter is compatible with POSIX: since POSIX requires a single argument, we can define operation with a missing argument however we want (or in other words, our current definition of issuing an error is not mandated). If we do that, then we

Re: include dos2unix/unix2dos in coreutils ?

>For example: > http://www.google.com/search?hl=en&q=miscutils&btnI=I'm+Feeling+Lucky&meta= > > Could you explain what that contains? I don't have access to a > webbrowser. The first hit in google is Miscutils-1.0.0 in CPAN. There are 92,700 hits in google for miscu

Re: include dos2unix/unix2dos in coreutils ?

> > I'm somewhat positive about the idea, but this particular name has > > the problem that it's already used for other projects (or at least > > that is what searching for the name on the web would imply). > > What project is that? I'm quite fond of the name, maybe etcutils > wo

Re: include dos2unix/unix2dos in coreutils ?

What about coreutils-extra? (Would that be acceptable to the coreutils folks?) These are not extra utilities for coreutils, so this name is not suitable. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/b

Re: include dos2unix/unix2dos in coreutils ?

> How about we create a miscutils project where these silly things > can be included? Coreutils is after all not the dumping point > for every imaginable utility one can come up with, it is for core > system utilities, and dos2unix certainly does not fit into > coreutils. I'm so

Re: What is the opposite of 'printf'?

I should note that I'm still waiting for the someone to step up as miscutils maintainer, [EMAIL PROTECTED] never got back to me about it. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: shred command. Autodetect file type

if --remove (-u) is specified. The default is not to remove the files because it is common to operate on device files like /dev/hda, and those files usually should not be removed. When operating on regular files, most people use the --remove option. Why not use the stat system cal

Re: include dos2unix/unix2dos in coreutils ?

Since this is a GNU project, it should have a GNUish name, and miscutils fits that. Names like not-so-coreutils would only raise the question why the programs are not included in coreutils. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://li

Re: miscutils

I think miscutils could depend on coreutils, and hence also include generally useful scripts? I'm either way. What might be the danger with including "useful" scripts is that every Dick, Jane and Joe will want to have their one-liner included. Remeber that most probobly many people will us

Re: include dos2unix/unix2dos in coreutils ?

Would anyone like to take care of the miscutils project? ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: include dos2unix/unix2dos in coreutils ?

Huh, never new about '--in-place' (sure wish I did!). But what is 'recode'? I don't seem to have a "recode", nor do I see anything about "recode" in sed. Did you mean iconv? (Maybe the real answer is 'coreutils already has d2u and friends, they just aren't obvious'?) www.gnu.org/s/r

Re: include dos2unix/unix2dos in coreutils ?

How about we create a miscutils project where these silly things can be included? Coreutils is after all not the dumping point for every imaginable utility one can come up with, it is for core system utilities, and dos2unix certainly does not fit into coreutils. I can create such a project in the

Re: include dos2unix/unix2dos in coreutils ?

Actually, dos2unix (the one I have, anyway) *does* do a few things that aren't so trivially done with sed. For one, it is in-place (unless told otherwise), and has --keepdate. In-place is awkward to do with sed. It is very easy to do with sed, just pass --in-place to sed. Wow, that

Re: include dos2unix/unix2dos in coreutils ?

Personally, I think dos2unix is such a simple and seldomly used hack to write in one line of sed that I don't see the point of it being included[0]. Now that sentence doesn't make any sense... What I meant to write was: | Personally, I think dos2unix is such a simple and seldomly used h

Re: include dos2unix/unix2dos in coreutils ?

Well, then, whichever way. We're drifting off the original topic, which was 'should d2u-and-friends (or equivalents) be added to coreutils?'. Can we address Mike's original question now, before he gets completely discouraged by this side-track? :-) Personally, I think dos2unix is such

Re: du feature request

> I would like to request a feature to be added to the 'du' > command: > > a command line switch to sort output by directory name or by size > of directory Why? What can we add to du that can't already be done by pipelining du output into sort? Because it is useful. As ano

Re: du feature request

Maybe you should read up on the de-facto UNIX philosophy in documents such as http://www.faqs.org/docs/artu/ch01s06.html GNU's Not UNIX. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: [Culture] When were the gnu coreutils written?

Check the ChangeLog's in coreutils, they are quite detailed. Specially the ones in [coreutils]/old. They don't got back to the start of each program, but they go quite far back. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/

Re: basename for directories containing space

[EMAIL PROTECTED] NZ PostSep06]$ echo `pwd` /home/corrin/NZ PostSep06 [EMAIL PROTECTED] NZ PostSep06]$ basename `pwd` NZ [EMAIL PROTECTED] NZ PostSep06]$ basename --version basename (GNU coreutils) 5.2.1 Written by FIXME unknown. Surely the correct output is "NZ PostSep06"?

Re: bug report

This is a bug in your GNU/Linux system, you should report it to the people who maintain it. The behaviour you see probobly happens because your shell initialision file doesn't do: eval "`dircolors /etc/DIR_COLORS`" or similar. Happy hacking. ___ Bu

Re: coreutils-6.0 on BeOS (9)

Btw, the "#ifdef __GLIBC__" in m4/fsusage.m4 looks wrong also for the Hurd, because glibc/sysdeps/mach/hurd/statfs64.c does not appear to access /proc. /proc doesn't exist on GNU, never did. Cheers. ___ Bug-coreutils mailing list Bug-coreutil

Re: Getting a file_t from a file descriptor

> I haven't had time (or a machine) to test the patch, but I don't > see any real reasons why it shouldn't. OK, thanks, I installed it. Thank you. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-

Re: Getting a file_t from a file descriptor

> While I'm not that proficient in these issues, Nor am i. But I am. > /* Return the io server port for file descriptor FD. This adds a >Mach user reference to the returned port. On error, sets >`errno' and returns MACH_PORT_NULL. */ Thanks, that looks quite promisi

Re: tail claims "tail +n" is deprecated

Breaking backward compatibility is so bad -- I've been bitten many times by autoconf-generated scripts that many GNU packages use and insist on remaking locally (why?) and that could not work because my local autoconf was newer than the version used by the package author. autoconf/a

Re: tail claims "tail +n" is deprecated

There's a bug in recent tail: it claims "tail +20" is deprecated and I should use "tail -n +20". It isn't a bug, it is intended. (coreutils)Standards conformance: |Newer versions of POSIX are occasionally incompatible with older | versions. For example, older versions of POSIX require

Re: GNU coding standards clash with POSIX for "... | tail -f"

> (2) I don't think many people are relying on this behavior. (Why > would you want to run "tail -f" on a pipe?) Agreed. That does seem freaky. I can't think of a useful case for it. I can't think of a specific or concrete case right now, but `tail -f' on a pipe could be used o

Re: expr --> problem with product functionality

GNU/Linux_box:/ # expr 10 / 2 5 GNU/Linux_box:/ # expr 10 * 2 expr: syntax error You need to escape the multiplication sign. Try: expr 10 \* 2 And try: echo expr 10 * 2 to see why it doesn't work (shell expansion) Cheers. ___ Bug-co

Re: (GNU/)Linux filereading

I am trying to open a file called "-2.xml" through VI editor/cat from command prompt. But unable to read the file as it is taking "-" as one option. I am getting the following error - cat: invalid option -- 2 Try: COMMAND ./-2.xml where COMMAND is vi/cat/... Cheers. __

Re: Test Failed

I compiled without problem coreutils 5.93, but when I executed "make check" there was one failed test. The failed test was close-stdout You haven't given any information about the system you compiled GNU coreutils 5.93 on, so it is hard to figure out what might have gone wrong. The co

Re: [ program

Except that '[' is a built-in with most shells today. But for older shells it was an external command. I think it is important to note that GNU [ supports more fancy things than the default GNU bash builtin; or atleast, used too... ___ Bug-coreu

Re: [ program

I was wondering if that [ program is supposed to be there, or if it's a typo. If I run info [ I get the info page for test, so I wasn't certain if they were related. They are the same, [ is for systems that don't have [ builtin into the shell. Consider the following shell expresion: if

  1   2   3   >