News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers by wflann on Wednesday April 22, 2015 @09:36AM (#9420269)
I think, occasionally, it's a lot easier to grok a command through googling than reading the built-in help. A fair amount of built-in *nix documentation I have run across is mediocre or unhelpful.
Re:The sad state of sysadmin in the age of containers by Gracana on Wednesday April 22, 2015 @11:01AM (#9420909)
I often find that GNU man pages are heavy on explanation of options and light on purpose and practical usage (the latter is tucked away in info pages). That's not necessarily the wrong way to do manpages, but I much prefer OpenBSD-style manpages, which seem to be better at providing practical information.
Re:The sad state of sysadmin in the age of containers by tormeh on Wednesday April 22, 2015 @10:41AM (#9420744)
Recursively searching through all files in the current folder (aka the normal use case for grep) is accomplished by using "grep -r". It's on line 270 in "man grep". And that assumes that you know what grep is at all. Would it have hurt so much to call grep "regexsearch" instead? Maybe -r could be the default?
Re:The sad state of sysadmin in the age of containers by jsight on Wednesday April 22, 2015 @11:08AM (#9420957)
I think a lot of people would hate having it be recursive by default.
Re:The sad state of sysadmin in the age of containers by Retra on Wednesday April 22, 2015 @12:36PM (#9421618)
If it were up to me it would be called `find` and it would have flags to find files or text within files.
Re:The sad state of sysadmin in the age of containers by Pxtl on Wednesday April 22, 2015 @11:46AM (#9421248)
All the core unix tools have the problem of predating the vowel generation (http://c2.com/cgi/wiki?VowelGeneration).
Re:The sad state of sysadmin in the age of containers by bcoates on Wednesday April 22, 2015 @01:38PM (#9422077)
'grep' isn't a case of disemvowelment (there's an e!), it's just a weird mnemonic that's outlived its referent.
Re:The sad state of sysadmin in the age of containers by markrages on Wednesday April 22, 2015 @11:33AM (#9421151)
Recursive is not the default use for grep. stdin-stdout filtering is.

"regexsearch" is more work to type and more space taken up everytime 'grep' appears in a command-line. And says nothing about recursion.

Re:The sad state of sysadmin in the age of containers by gnaritas on Wednesday April 22, 2015 @11:37AM (#9421183)
Recursion is caused either by -R or -r on nearly all commands and is pretty standard, and r is virtually never the default on any command because that would be a bad idea. And yes, having to type regexsearch rather than grep would have been a bad idea; while grep isn't a great name it's far preferable to someone who types constantly. Search or find would have been better names, names need to be both short and descriptive on the command line, and short comes first.
Re:The sad state of sysadmin in the age of containers by stephenr on Wednesday April 22, 2015 @11:46AM (#9421247)
Use the built-in search.

Edit: the rest of my comment (somehow submitted to soon!)

    man grep

    /recurs<enter>
Re:The sad state of sysadmin in the age of containers by markrages on Wednesday April 22, 2015 @01:25PM (#9421986)
or use 'grep':

    $ man grep | grep recursive
                  directory,  recursively,  following  symbolic links only if they
                  Exclude  directories  matching  the  pattern  DIR from recursive
           -r, --recursive
                  Read all files  under  each  directory,  recursively,  following
           -R, --dereference-recursive
                  Read all files under each directory,  recursively.   Follow  all