-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Samuel GRANJEAUD - IR/IFR137 wrote:
> Hello,
>
> I thank you very much for devolopping coreutils that allows quick and
> simple replacement of SQL queries and check. What I would appreciate is
> a tool that does head and tail in one command, giving th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pádraig, thanks for this.
I know that I, at least, would have benefitted from such a tool while
testing certain filesize-related issues for Wget. I wrote a quick
ten-liner for the purpose on those occasions, but of course it's great
to have a proper t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Note abbreviated Cc list.)
Paul Eggert wrote:
> "Bo Borgerson" <[EMAIL PROTECTED]> writes:
>
>> Is it
>> possible to maintain an English translation with only LC_TIME info?
>
> Yes. I maintain an English translation by hand for GNU diffutils.
> Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philip Rowlands wrote:
> On Thu, 1 May 2008, Kenneth Koym wrote:
>
>> Attn: Bug-coreutils@gnu.org
>> Repeatedly, OO 2.2 has froze while saving a document; often this
>> happens just as I open and select a line or two for placing in another
>> documen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
> According to huma fouladi on 6/4/2008 12:02 AM:
> | Dear sir
> |
> | I am facing problem using update manager,it only shows updates but cant
> | download.
> | Kindly sort out the problem and let me know what to do.
>
> You reached
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Panin wrote:
> Hi!
>
> I can't make echo to show \n and \r symbols. According to 'man echo',
> there's a way to do this by using '-e' option.
>
> However, this doesn't help. Doesn't even matter which option I choose
> (even 'echo -e \015'), it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phillip Susi wrote:
> Jim Meyering wrote:
>> When I say "not affected" I mean it.
>> Turning off the readdir optimization affects ls -i only
>> when it reads directory entries.
>
> You mean you are only disabling the optimization and calling stat()
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering wrote:
> Benno Schulenberg <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> While updating the Dutch translation for coreutils, I came across a
>> few small inconsistencies. Attached patches fix those.
>
> Hi Benno,
>
> Thanks for all the patche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabien Carmagnac wrote:
> Hello,
Hi. Your question (and its potential solution) isn't really topical for
this forum (which is for discussion of the GNU coreutils software
package). It involves the use of a part of that software (rm, and
apparently bas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ahmad Hussein wrote:
> Hi ,, Unknown man ;) ,,
>
> OK i have problem in the terminal when i write this command sudo
> apt-get install * it's appear this message "E: dpkg was interrupted,
> you must manually run 'dpkg --configure -a' to correct t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Wright wrote:
> I hope this is the right place to post this question.I'm running
> Puppy Linux 4.0 and have run into a problem with their version of
> tail not supporting the --byte option. I have to use -c instead. Is
> this because it's not a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Hey there,
>
> I have some folders on my eeepc, which I cannot modify (wanted to delete them)
>
>
> Think it is a Virus.
> am not able to run the usual Llinux Desktop. Instead there is
> a black screen with the Taskbar un
Matthew Woehlke wrote:
> Pedro Henrique Marques wrote:
>> But the output shows the verification only from the 3� to last file:
>
> To clarify, the problem is that the first and last file were apparently
> ignored?
And second, I think.
It would've been helpful to see the exact invocation of md5su
Follow-up Comment #1, bug #25946 (project coreutils):
cd -- "- test -"
should also work fine.
This is not only expected behavior for cd and ls, but for virtually any
command on a Unix-style system. Arguments that begin with a "-" are
interpreted as strings of options (think of "ls -ltc"), so cd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
> [please keep replies on the list, so that others may chime in]
>
> According to Robin McAdam on 3/21/2009 7:26 PM:
>>> That warning was in place to warn of a future change in behavior. The
>>> change has now been completed, and yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
> According to ratnaveni k on 7/6/2009 4:49 AM:
>
> Hello Ratnaveni,
>
>> Dear Developer,
>
>> I installed ubuntu 8.04 in laptop.i tried to install
>> some crystallographic programs.
>> for o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C de-Avillez wrote:
> So. Would it be an acceptable idea to add, to the '--help', a warning
> that this is *not* the full documentation?
>
> Say, like:
>
> "This is an abridged documentation. The full documentation for blahblah
> is maintained as a T
In the Ubuntu bugtracker, Malone, we've been getting several submissions
of an issue, usually phrased along the lines of "cp dumps core on copy
of > 4GB file to vfat (or usb)", etc. See
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/75574
I'd like to see a handler installed for SIGXF
Philip Rowlands wrote:
On Mon, 9 Apr 2007, Micah Cowan wrote:
In the Ubuntu bugtracker, Malone, we've been getting several
submissions of an issue, usually phrased along the lines of "cp dumps
core on copy of > 4GB file to vfat (or usb)", etc. See
https://bugs.launchpad.
Philip Rowlands wrote:
> On Mon, 9 Apr 2007, Micah Cowan wrote:
>
>> Users report having this problem when they copy to (e.g.) vfat
>> systems, but not ext3, so it seems to be FS-related. Even if it did
>> turn out to be usage limit, I would think the problem would be the
Dr. Douglas Lyon wrote:
Hi All,
uname does not work on the debian port to a mips based
asus router...
uname -p
unknown
but:
uname -a
Linux asus-debian 2.6.19.2 #9 Tue Apr 3 21:30:54 CEST 2007 mips GNU/Linux
is correct.
Actually, I'm getting the same behavior on my i686 Ubuntu 6.10.1 install.
Eric Blake wrote:
>> #$ echo - e "\015\033[- 1Cxxx" starts string "xxx" at position 0, ok
>
> Using "\015" as the argument to echo is not portable shell; you should use
> "\\015" or '\015' instead.
Using -e isn't portable shell either, as POSIX requires echo to
recognize no options, but inste
Karl Berry wrote:
> It already supports -MM-DD HH:MM:SS (also with TZ).
>
> I know, and I am glad, but as I wrote in my original message, the forms
> without punctuation would also be useful (to me anyway) to support.
The punctuation is already optional:
$ date -d 20070508\ 1406
Tue May
Andreas Schwab wrote:
> [EMAIL PROTECTED] (Bob Proulx) writes:
>
>> Alexander Schestag wrote:
>>> So, is there a way to tell "who" to list the users logged in via su
>>> as well?
>> Not with who. AFAIK you would need to walk the process list for that
>> information. There is really nothing speci
James Youngman wrote:
> On 5/25/07, Eric Blake <[EMAIL PROTECTED]> wrote:
>
>> 'yes' is not specified by any standards, so it is not portable to begin
>> with.
In the spirit of "I'm going to replace you with a very small shell
script... :)
( while :; do printf '%s\n' -v; done ) | head -n3
--
Patrick Amstutz wrote:
> Hi,
>
> I've the following behavior with the seq function on:
>
> Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version
> 4.1.220061115 (prerelease) (SUSE Linux)) #1
>
> $ echo `seq 0.0 0.1 0.8`
> 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8
> $ echo `seq 0.0 0.1 0.9`
Pádraig Brady wrote:
> Another thing I just noticed. I would expect the precision
> of all output in the following command to be to 2 decimal places not 1:
>
> $ seq 0.00 0.01 0.90 | grep "\.[0-9]$"
> 0.1
> 0.2
> 0.3
> 0.4
> 0.5
> 0.6
> 0.7
> 0.8
> 0.9
I wouldn't. The documentation is fairly cle
Bob Proulx wrote:
> Lenny Domnitser wrote:
>> It works fine, but it seems that it's a workaround for behavior ls
>> could have.
>
> Since ls already has so very many features adding more features
> requires a higher "activation energy" than adding features for other
> commands. For something conc
Phillip Susi wrote:
>> trap "" 1 15
>> if test -t 2>&1 ; then
>> echo "Sending output to 'nohup.out'"
>> exec nice -5 $* >>nohup.out 2>&1
>> else
>> exec nice -5 $* 2>&1
>> fi
>>
>> All that nohup does is to ignore SIGHUP and SIGTERM and redirect the
>> output if it is no
Johannes Findeisen wrote:
> Hi,
>
> On Wed, 2007-06-13 at 16:47 -0400, Dhruv Rangoonwala wrote:
>> Hi,
>>
>> I have tried to use the following command:
>>
>> cat -b
>>
>> If the file have blank lines, this command does not eliminate it. It still
>> gives number to that blank line. Please check it
Andreas Schwab wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> Untrue, actually: _handling_ the signals would not handle them in the
>> exec'd child (for obvious reasons), but POSIX requires blocked signals
>> to remain blocked after an exec.
>
> tr
Lenny Domnitser wrote:
> On 6/13/07, Bob Proulx <[EMAIL PROTECTED]> wrote:
>> Improving this seems like a reasonable enhancement.
>
> If you think changing the behavior of --color=auto will break things,
> I can do --color=smart, i.e. the TERMinal is not dumb.
Given that "dumb" isn't the only ter
f making seq act as if it were counting in decimal for fractions,
instead of binary floating-point, is really something we want to
consider, then why don't we actually have seq represent fractions in
decimal, internally? Isn't that the only real way we could possibly
expect seq to "do what the user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joost Brands wrote:
> Unknown Error: '' (E: The package skype
> needs to be reinstalled, but I can't find an archive for it)*
>
> This error line appeared after I tried to install a beta version of
> Skype software. Since then it is impossible to i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> John Cowan ccil.org> writes:
>
>> Are you saying that an O_TEXT open under Cygwin, given a binary mount,
>> will cause newline translation? I had assumed that O_TEXT would be
>> ignored under Cygwin just as it is under Linux.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Cowan wrote:
> Indeed, I'd like to see all text tools accept all six known line ending
> conventions: CR+LF, CR alone, LF alone, NEL alone, CR+NEL, LS.
> (NEL is U+0085, LS is U+2028.)
> That said, I believe it is good for portability to us
熊途 wrote:
> hello:
> when I used "su" command to get into Linux by root in terminal
> windows, I can not input password. Another user name too.How can I resolve
> my problem.thank you!
It may be that you're confused by the fact that the "su" command hides
its input. That is, the characte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bob Proulx wrote:
> A scan is made left to right across the argument list looking for
> options. Traditional behavior and POSIX require options before
> non-option arguments. As a GNU extension options may appear anywhere
> in the argument list. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael Gorbovitski wrote:
> chmod --help
> results in :
> help for chmod
> ..
> Each MODE is of the form `[ugoa]*([-+=]([rwxXst]*|[ugo]))+'.
>
> Report bugs to .
>
>
> The above regular expression is unparsable by most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
wisdom helegbe wrote:
> [EMAIL PROTECTED] ~]# ./configure --help
> -bash: ./configure: No such file or directory
According to the prompt you show, it looks like you're trying to run
./configure from within your home directory, rather than from the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reuben Thomas wrote:
> The man pages wisely direct the reader to the info documentation, but
> since coreutils's documentation is now in one big info file, "info cat",
> for example, doesn't work (it gives me the man page again on my system);
> you h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cutler, David wrote:
> Hello,
>
> My execution environment is
>CYGWIN_NT-5.1 DCUTLER 1.5.24(0.156/4/2) 2007-01-31 10:57 i686 Cygwin
>(dual core, 2.0 GHz cpu with 2GB ram Compaq NW8440 Laptop)
>
> When I downloaded Cygwin, I specified the us
cvs.savannah.gnu.org is no longer kept up-to-date, and should not be
used to obtain the latest gnulib sources; the CVS interface to the git
repo, at pserver.git.sv.gnu.org, should be used instead (or else just
use git).
* bootstrap: updated CVS path for gnulib sources.
---
bootstrap |2 +-
1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
> cvs.savannah.gnu.org is no longer kept up-to-date, and should not be
> used to obtain the latest gnulib sources; the CVS interface to the git
> repo, at pserver.git.sv.gnu.org, should be used instead (or else just
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Meyering wrote:
> Micah Cowan <[EMAIL PROTECTED]> wrote:
>> Micah Cowan wrote:
>>> cvs.savannah.gnu.org is no longer kept up-to-date, and should not be
>>> used to obtain the latest gnulib sources; the CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Meyering wrote:
> Eric Blake <[EMAIL PROTECTED]> wrote:
>> According to Clytie Siddall on 10/24/2007 2:37 AM:
>>> Hi :)
>>>
>>> I recently reviewed our translation of coreutils for the Translation
>>> Project. I noticed the following errors, whic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andreas Schwab wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> Yes, it used to be a format string; however, does xgettext know this?
>> That is, the generated coreutils.pot file itself has #, c-format in it
>
---
ChangeLog |5 +
bootstrap | 23 +--
2 files changed, 6 insertions(+), 22 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 9377791..33ec517 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2007-10-24 Micah Cowan <[EMAIL PROTEC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> According to Bruno Haible on 10/24/2007 4:44 PM:
" ARG1 % ARG2 arithmetic remainder of ARG1 divided by ARG2\n"
>> xgettext marks it as c-format, because it looks like a C format string,
>> and the possible negativ
0644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2007-10-24 Micah Cowan <[EMAIL PROTECTED]>
+
+ * src/expr.c (usage): Mark the string describing "ARG1 % ARG2"
+ as not being a fprintf-style format string, for xgettext.
+
2007-10-24 Jim Meyering <[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Meyering wrote:
> Micah Cowan <[EMAIL PROTECTED]> wrote:
>> +* bootstrap: Remove --cvs-user, CVS_USER, CVS_RSH; and "test -d
>> +CVS" from version_controlled_file function.
> ...
>> - if test -d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Meyering wrote:
> I'm sure you've already heard it, but I have to say it:
> You shouldn't use csh-based shells.
> If you ask anyone or google, you'll find many good reasons.
> Lack of a decent signal-handling mechanism is one of them.
Jim,
Usua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> Jim Meyering meyering.net> writes:
>
>>> ./bootstrap: cp ._bootmp/lib/alloca.c lib/alloca.c # with edits
>>> mv: cannot move `lib/alloca.c-t' to `lib/alloca.c': No such file or
> directory
>> That's odd.
>> I've been unable to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ginis.com wrote:
> hello,
>
> how I can correct the time in RedHat Linux? with command "time" or "date" and
> how?
Yes, date can do that. To make the change persistent, you probably also
need the hwclock commands. Both will require root privileges
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Manickam Muthuraman wrote:
> Hello
> when i tried the following command, i get this error. May i know whats going
> wrong.
>
> [EMAIL PROTECTED]:~/HHpred/scop_hmm> cat *.hhm > scop70_1.72.hhm
> bash: /bin/cat: Argument list too long
Hi Manickam,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Proulx wrote:
> Vitaly V. Ch wrote:
>> As I understand ls require null-separated format of output stream which
>> will suitable for xargs.
>>
>> in this case I systematically use find instead of ls.
>
> Your message seems to be garbled and I, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joseph Piche wrote:
> Hello.
>
> I am trying to get to the center of Ubuntu Bug #7560 and Gnome Bug
> #108307. This "bug" is over 4 years old. This relates to how gnome-vfs
> treats files moved to the trash, but I believe it boils down to how
> coreut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering wrote:
> Here's a tentative patch that also avoids repeated
> (and wasteful) initialization of the xlate array.
I note that POSIX requires that, in the case that the arguments are
exactly '[:lower:]' and '[:upper:]' (or the reverse of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jari Aalto wrote:
>> Thanks, but "File exists" is just the English version of the
>> strerror(EEXIST) string from the C library.
>
> "Target exists" would be more generic if message is based on the EEXIST
> error code.
Considering that, as Jim points
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pádraig Brady wrote:
> Bob van Loosen wrote:
>> Hi everyone,
>>
>> Whenever I do this:
>>
>> tail -f /var/log/kern.log | cut -f 8- -d " " | dd bs=1
>>
>> I get no output, but when I do this:
>>
>> tail -f /var/log/kern.log | cut -f 8- -d " "
>>
>> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering wrote:
>> PATH is a personal preference. Many people set it like I do. Don't expect
>> that PATH is set like you prefer it.
>
> I'd argue that few people put "." anywhere in PATH, since
> doing so constitutes a well-known security risk.
>
61 matches
Mail list logo
