4 ms·
As much as I'd agree with the symptoms you guys are describing when it comes to my parents and grandparents, I don't think this is much of an age problem at all
by dahart 8y ago
As much as I'd agree with the symptoms you guys are describing when it comes to my parents and grandparents, I don't think this is much of an age problem at all.
The same thing happens to my kids when I present them with a bash shell. They don't understand how to read the instructions, and they're uncomfortable with text commands. They don't want to type 'man' or 'help', and they give up very quickly. Everything they use on computers and game consoles are GUIs, most of them extremely easy to use by the standards of text interfaces like bash & vi.
This is a familiarity problem. You have years and years of experience with your OSes, which is what allows you to see outside the 2-inch window when you use a new application. You know exactly what you can ignore, and exactly what you need to pay attention to. They don't. Being unfamiliar with all of it and not having any idea how any of it works is what makes it seem like they're not learning quickly, but it's more because they're trying to learn everything at once, and are overwhelmed, not because they're not learning at all.
- hobs 8y agoWhen talking with people who struggle, I talk about the that the difference between being able to see a footprint to track a new animal in the forest and you being able to use a somewhat novel computer interface are based on the same principles of experience and ignoring the piles of useless information.
- x404 8y agoAgree, they just not familiar the computer as us.
- mehrdadn 8y ago> The same thing happens to my kids when I present them with a bash shell. They don't understand how to read the instructions Uhm, the issue here is squarely on Bash's end, not your kid's. Even the Windows command prompt is far more intuitive to learn. I know because I vividly remember how much more confused I got when learning the former. In Windows, when you type "help", it actually gives you helpful commands: COPY, MOVE, DEL, REN/RENAME, etc. and at least the basic commands are actually what you'd expect. At least you have a foothold somewhere that you can ground yourself, and you start learning a bit more every time. Try that in Bash, and good luck learning out how to do anything in Bash on your own. Oh, you want help? I gotchu! I'm guessing you're looking for job_spec, bg, compopt, coproc, disown, shopt, or trap? Oh I'm so sorry, you said all you wanted was to just copy a file? Haha I'm just a shell! You can't expect me to know how know what it means to "copy" a file! I can't even find that command! But if you need help, type "man -k" (what kind of a name is that??) to find out more about other commands. Oh, so you typed "man -k"? Okay, "apropos what?"??? (You, thinking to yourself: is 'apropos' even an English word?? I literally just typed in man -k like they told me to, and I got back a question I don't understand...) And on and on and on, until weeks later you realize the darn command was helpfully named 'cp' and not 'copy'...
- kazinator 8y agoOnly problem is, those commands are useless. COPY won't back up a directory tree. You need XCOPY. Oops, XCOPY chokes for weird reasons and terminates with a strange error message because a path was more than 255 bytes. It needs a bazillion options to do the equivalent of GNU's "cp -a". If you go online to get help with this, the best advice you get is to download and install something called RoboCopy. Yes, MS-DOS was easy to learn. XCOPY worked in MS-DOS.
- deleted 8y ago[deleted]
- jodrellblank 8y agohttps://unix.stackexchange.com/a/87128 https://unix.stackexchange.com/a/87128 "copy doesn't copy directory structures, it will only copy the files, hence the error message you're encountering. To do a deep copy such as this you can enlist either the tar command and use the construct tar cvf - --files-from=... | (cd /home/tmp/test/files/; tar xvf -) or you can just use rsync." That's so much better..
- kazinator 8y agocp most certainly does copy directory structures. Just not filtered ones whereby just certain entries are arbitrarily selected from the source tree and only those are replicated in the destination tree. The issue in the question is that the person has expanded, into the cp command line, a bunch of full paths, effectively like "cp a/b/c/file1 a/b/d/file2 .... dest" and wants those relative paths to be re-created under dest as dest/a/b/c/file1 and so on. Indeed, cp does not do that; it simply puts the specified objects file1 file2 ... into dest. An option to create each object's relative path under dest would be useful, but it would be a pretty awful default behavior. GNU cp has this option: `--parents' Form the name of each destination file by appending to the target directory a slash and the specified name of the source file. The last argument given to `cp' must be the name of an existing directory. For example, the command: cp --parents a/b/c existing_dir copies the file `a/b/c' to `existing_dir/a/b/c', creating any missing intermediate directories. GNU Coreutils is in active development, unlike the Windows command line which is basically abandonware (as, to be even-handed, is the Unix (tm) command line.)