network profile
| bio | website | |
|---|---|---|
| location | Nizhniy Novgorod, Russia | |
| age | 28 | |
| visits | member for | 1 year, 3 months |
| seen | May 15 at 12:19 | |
| stats | profile views | 10 |
|
Mar 8 |
awarded | Popular Question |
|
Feb 23 |
awarded | Yearling |
|
Jan 23 |
comment |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? @jw013 You've impressed me with "when you move a cup of coffee you don't have to move the contents separately", it really makes sense, thank you. But it's another layer of abstraction. I think you mean "treat a file as an inode" while I think of files like of bytes sequences without meta-information. |
|
Oct 25 |
awarded | Self-Learner |
|
Aug 26 |
awarded | Nice Question |
|
Aug 24 |
comment |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? That's right, I just was thinking of cp and mv as operations that they are named: 'make a copy' and 'move'. So if I want to make a copy of a cup of coffee, I'd expect to have another cup of coffee with the same filling (coffee drink). The problem is that the tools are not intended for 'usual people' but for nerds who are aware of disk and file system structure, not virtual entities like files and dirs of files. |
|
Aug 23 |
revised |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? added 18 characters in body |
|
Aug 23 |
awarded | Teacher |
|
Aug 23 |
comment |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? I have posted my explorations as an answer (it was too long for a comment). Finally I think there could be two comfortable (IMHO) behaviours: 1. make cp and mv work with files and dirs -- just do what the name of command says
2. make cp and mv work with files only and create dircp and dirmv for manipulating dirs recursively |
|
Aug 23 |
answered | Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? |
|
Aug 22 |
awarded | Editor |
|
Aug 22 |
revised |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? +additional question |
|
Aug 22 |
comment |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? so you want to say that mv tool was created just for renaming files? and later it was modified to support cross-fs moves with copy+remove? then why don't coreutils developers make cp copy dirs recursively by default? isn't it a good UX improvement too? |
|
Aug 22 |
comment |
Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? is mving from one file system to another the same "just change the name in the directory entry"? |
|
Aug 22 |
asked | Why unix mv program doesn't need -R (recursive) option for directories but cp does need it? |
|
May 5 |
comment |
Is chmod behavior wrong for symlinks? I've found Rob Pike criticizing symlinks in a document describing Plan 9 OS which lacks symlinks at all and has bind command for building user's own namespace plan9.bell-labs.com/sys/doc/lexnames.html |
|
May 5 |
comment |
Is chmod behavior wrong for symlinks? Thank you! The only question I have now: why this behaviour of chmod on symlinks was chosen? When is it useful and handy? |
|
May 5 |
answered | Deciding on a font, and determining the proper notation |
|
May 5 |
asked | Is chmod behavior wrong for symlinks? |
|
May 2 |
awarded | Scholar |
