skimming through coreutils’ copy.c, emit_verbose is called on line 2627 while copy_reg is called on line 3103 (in the implementation of copy_internal). at least on my machine, touch /tmp/foo && cp -v /tmp/{foo,bar/} returns an error after printing the verbose output.
this post was submitted on 07 Dec 2023
43 points (93.9% liked)
Linux
48072 readers
1 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
I think the one being currently copied? take a look at https://github.com/coreutils/coreutils/blob/master/src/cp.c :)
Another way to check is to
strace cp testfile testfile2
and the sequence in which the message is printed and operations performed can be studied.
It's perhaps a lot to read, but linux tracing tools are worth learning!