From: "BRAGA, Bruno" <bruno.braga@gmail.com>
To: renato.oferenda@gmail.com
Cc: linux-console@vger.kernel.org
Subject: Re: Updates on "mv", "cp" commands
Date: Sun, 1 Nov 2009 21:51:03 +0900 [thread overview]
Message-ID: <86ca47940911010451i66e205e8k9aecac99483b86fc@mail.gmail.com> (raw)
In-Reply-To: <20091101122046.GA5336@bio05.biowulf.net>
Wow thanks for the tip... I was pretty lost on who to contact.
Cheers,
******************************
Braga, Bruno
On Sun, Nov 1, 2009 at 9:20 PM, <renato.oferenda@gmail.com> wrote:
> Hello Bruno!
>
> On Sun, Nov 01, 2009 at 09:30:21AM +0900, BRAGA, Bruno wrote:
>> 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).
>
> A good place to start anything in linux is at the man page for the software. ("man" == shorthand for "manual").
>
> If you "man cp" and then "man mv" you'll see on the last line for each man page that they both belong to the GNU coreutils package. (http://www.gnu.org/software/coreutils/).
>
> Good luck!
>
> --
> Renato å—. []'s, RCB.
>
--
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 12:51 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
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 [this message]
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=86ca47940911010451i66e205e8k9aecac99483b86fc@mail.gmail.com \
--to=bruno.braga@gmail.com \
--cc=linux-console@vger.kernel.org \
--cc=renato.oferenda@gmail.com \
/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).