From: "BRAGA, Bruno" <bruno.braga@gmail.com>
To: Michal Nazarewicz <mina86@tlen.pl>
Cc: linux-console@vger.kernel.org
Subject: Re: Updates on "mv", "cp" commands
Date: Sun, 1 Nov 2009 20:47:21 +0900 [thread overview]
Message-ID: <86ca47940911010347v235b0642q140e50489c7c8259@mail.gmail.com> (raw)
In-Reply-To: <87y6mq64wn.fsf@erwin.mina86.com>
Thanks for the reply Michal.
I will look into that (I found the source in GNU's source code, but I
am still kinda lost on to whom should I ask stuff, lol). i will let
you know if/when I get things done with the team there.
Cheers,
******************************
Braga, Bruno
http://www.brunobraga.net
bruno.braga@gmail.com
*******************************
"The future belongs to people who see possibilities before they become
obvious!." -- Ted Levitt
2009/11/1 Michal Nazarewicz <mina86@tlen.pl>:
> "BRAGA, Bruno" <bruno.braga@gmail.com> writes:
>> I don't know if that's the place to post this question, but I am sure
>> someone here will be able to give me hints on how to proceed.
>>
>> I would like to propose and patch improvements on the "mv" (move) and
>> "cp" (copy) commands, by adding options for progress information.
>
> That's something I was wondering about some time ago myself.
>
>> The idea is that any GUI actions already do it graphically, and other
>> CLI applications, such as "rsync", have this as an extended option
>> "--progress". This is handy for large files processing, for instance.
>>
>> I looked for the code in the kernel source but I did not find any. I
>> could find some sources on the GNU OS, but I am not sure if that's the
>> right place (probably not).
>
> You won't find any sources of cp or mv in Linux source code because cp
> and mv commands are user space and as such they are not part of Linux
> per se.
>
> If you are using some kind of GNU/Linux distribution the place to look
> is GNU coreutils package. Consult gnu.org webpage for it's source code
> and information how to submit patches.
>
> --
> Best regards, _ _
> .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
> ..o | Computer Science, Michal "mina86" Nazarewicz (o o)
> ooo +--<mina86*tlen.pl>--<jid:mina86*jabber.org>--ooO--(_)--Ooo--
>
--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-01 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86ca47940910310550s87a6140s377a3d752979037@mail.gmail.com>
2009-11-01 0:30 ` Updates on "mv", "cp" commands BRAGA, Bruno
2009-11-01 8:11 ` Michal Nazarewicz
2009-11-01 11:47 ` BRAGA, Bruno [this message]
2009-11-02 5:26 ` Renato Callado Borges
[not found] ` <86ca47940911012308m391bada5n4e62a089e427812b@mail.gmail.com>
2009-11-02 7:39 ` BRAGA, Bruno
2009-11-01 12:20 ` renato.oferenda
2009-11-01 12:51 ` BRAGA, Bruno
2009-11-01 13:01 ` renato.oferenda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ca47940911010347v235b0642q140e50489c7c8259@mail.gmail.com \
--to=bruno.braga@gmail.com \
--cc=linux-console@vger.kernel.org \
--cc=mina86@tlen.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).