Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by FreakyT on Tuesday June 25, 2013 @11:52PM
(#5944091)
I never understood why this hasn't been modernized. The three-letter nearly-meaningless directory names seem so obsolete.
[ Parent
| on HN ]
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by vacri on Wednesday June 26, 2013 @01:19AM
(#5944343)
Long path names are an annoyance everywhere, from the commandline to the file browser. Use long names where appropriate ('aunt sally photos 2011' is better than 'asp11'), but for the dozen things in the root directory, there's not much effort involved.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by e3pi on Wednesday June 26, 2013 @12:21AM
(#5944174)
I gather you're also not versed in the unix command line? Piping and redirecting long dir paths thru commands and arguments welcomes everything abbreviated. The mnemonics is just engineered happiness sugar-on-top of all the intrinsic greatness.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by trafficlight on Tuesday June 25, 2013 @11:55PM
(#5944100)
They are easy to type and do have meaning in and of themselves.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by eru on Wednesday June 26, 2013 @05:14AM
(#5944933)
> [...] have meaning in and of themselves.
Mostly because of long usage.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by quackerhacker on Wednesday June 26, 2013 @12:40AM
(#5944241)
Unless your ssh'd into a machine, it's annoying to type long dir's. What's worse is compensating for spaces in filenames.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by freework on Wednesday June 26, 2013 @12:45AM
(#5944252)
Thats what tab completion is for.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by quackerhacker on Wednesday June 26, 2013 @01:01AM
(#5944288)
Thank you freework, didn't know about that one (embarrassing as it is to admit).
Still sucks dealing with spaces when it comes to command processes like ffmpeg -i <no_tab>...but awesome for cd'ing or ls'ing!
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by kanemathers on Wednesday June 26, 2013 @01:15AM
(#5944331)
Just prefix the space with a backslash. Eg: ``$ ls /foo/bar/my\ directory/``. With that backslash in place, you can continue your tab-completion.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by iSnow on Wednesday June 26, 2013 @01:55AM
(#5944418)
Still, on some international keyboards, backspace is hard to reach, eg. on a German Mac keyboard, is it <alt><shift>7.
So don't put spaces in path names, it's a bitch to work with.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by emillon on Wednesday June 26, 2013 @03:46AM
(#5944692)
You can quote the space:
mkdir x\ y
cd x' 'y
(or the entire part: cd 'x y')
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by quackerhacker on Wednesday June 26, 2013 @04:17AM
(#5944770)
Yup, that's what I do too, or %20 if its a url
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by J_Darnley on Wednesday June 26, 2013 @09:14AM
(#5945748)
Unix/Linux/whatever should have just forbidden spaces in filenames in the first place since none of the basic tools make it easy iterate over a list of filenames with spaces correctly.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by gizmo686 on Wednesday June 26, 2013 @12:05PM
(#5946898)
At least UNIX doesn't have a space in the path of the main programs directory (I'm looking at you Windows).
Also, many of the basic tools have a -0 option which uses the null character to replace many uses of space. Still far from an adequate solution though.
Re:Understanding the linux filesystem (/etc, /var, /bin, /op...
by quackerhacker on Wednesday June 26, 2013 @12:23PM
(#5946996)
Ohh yeah! This is where my initial frustrations have always been for spaces...mounting an NTFS-3G or URL encodings.