<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>stonesweep</author><text>trivia: `which` is not the &lt;i&gt;same&lt;/i&gt; which on all distros - on Ubuntu for example it&amp;#x27;s a super simple shell script named `which` which supports one single param (-a), not the compiled binary that you have on say Arch - and the features are different between them - I can&amp;#x27;t for example run `which --skip-tilde which` on Ubuntu, invalid usage.&lt;p&gt;Many scripters who need wide compatibility of &amp;quot;which&amp;quot; fall back to the builtins `type` and `command` as they resolve any bash aliases set and give you a more truthful (sic) output than relying on `which` and bash is bash on all platforms:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    # command -v which
    &amp;#x2F;usr&amp;#x2F;bin&amp;#x2F;which

    # type which
    which is hashed (&amp;#x2F;usr&amp;#x2F;bin&amp;#x2F;which)
&lt;/code&gt;&lt;/pre&gt;
$0.02 for your next adventure down the `which` rabbit hole. :)</text><parent_chain><item><author>freedomben</author><text>FHS and distros that follow it aren&amp;#x27;t perfect, but it &lt;i&gt;does&lt;/i&gt; make a big difference.  I prefer Fedora-based and Arch-based flavors for that reason.  It&amp;#x27;s usually pretty easy to find stuff.&lt;p&gt;Backtrack used to do something like this and while it was easier compared to a lot of other debian&amp;#x2F;ubuntu based things, I still ran into some pain points.&lt;p&gt;A great command to keep handy is&lt;p&gt;&lt;pre&gt;&lt;code&gt;    ls -la `which &amp;lt;program&amp;gt;`
&lt;/code&gt;&lt;/pre&gt;
That will usually find you the binary right away, and if it&amp;#x27;s a symlink or something you&amp;#x27;ll see it in the ls output.  It&amp;#x27;s especially useful to me because (generally speaking) I put stuff I build myself in ~&amp;#x2F;bin rather than `&amp;#x2F;usr&amp;#x2F;local&amp;#x2F;bin` so I can quickly tell if I&amp;#x27;m using my own build or the package manager&amp;#x27;s.&lt;p&gt;Edit:  FHS == Filesystem Hierarchy Standard - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Filesystem_Hierarchy_Standard&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Filesystem_Hierarchy_Standard&lt;/a&gt;</text></item><item><author>foxyv</author><text>Wow, this model addresses a lot of the issues I have with different Linux distributions. Mainly, finding where the heck it installed that program in the maze of file&amp;#x2F;folder locations. Sometimes it&amp;#x27;s etc, opt, var&amp;#x2F;lib, bin, usr&amp;#x2F;bin, apps... Gwahhhhh!&lt;p&gt;Then, you go to modify the configuration, and it turns out that the configuration file is being copied and generated from a different location. It&amp;#x27;s endless misdirection which changes in each distribution based on the package manager.&lt;p&gt;I think I may try out Gobo the next chance I get. This is pretty cool.</text></item></parent_chain></comment><story><title>GoboLinux</title><url>https://www.gobolinux.org/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>voidfunc</author><text>The FHS really only makes sense when you use Linux as traditionally intended as a multi-user system.&lt;p&gt;Most uses of Linux are single-user, running as a server, or even more just a container.</text><parent_chain><item><author>freedomben</author><text>FHS and distros that follow it aren&amp;#x27;t perfect, but it &lt;i&gt;does&lt;/i&gt; make a big difference.  I prefer Fedora-based and Arch-based flavors for that reason.  It&amp;#x27;s usually pretty easy to find stuff.&lt;p&gt;Backtrack used to do something like this and while it was easier compared to a lot of other debian&amp;#x2F;ubuntu based things, I still ran into some pain points.&lt;p&gt;A great command to keep handy is&lt;p&gt;&lt;pre&gt;&lt;code&gt;    ls -la `which &amp;lt;program&amp;gt;`
&lt;/code&gt;&lt;/pre&gt;
That will usually find you the binary right away, and if it&amp;#x27;s a symlink or something you&amp;#x27;ll see it in the ls output.  It&amp;#x27;s especially useful to me because (generally speaking) I put stuff I build myself in ~&amp;#x2F;bin rather than `&amp;#x2F;usr&amp;#x2F;local&amp;#x2F;bin` so I can quickly tell if I&amp;#x27;m using my own build or the package manager&amp;#x27;s.&lt;p&gt;Edit:  FHS == Filesystem Hierarchy Standard - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Filesystem_Hierarchy_Standard&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Filesystem_Hierarchy_Standard&lt;/a&gt;</text></item><item><author>foxyv</author><text>Wow, this model addresses a lot of the issues I have with different Linux distributions. Mainly, finding where the heck it installed that program in the maze of file&amp;#x2F;folder locations. Sometimes it&amp;#x27;s etc, opt, var&amp;#x2F;lib, bin, usr&amp;#x2F;bin, apps... Gwahhhhh!&lt;p&gt;Then, you go to modify the configuration, and it turns out that the configuration file is being copied and generated from a different location. It&amp;#x27;s endless misdirection which changes in each distribution based on the package manager.&lt;p&gt;I think I may try out Gobo the next chance I get. This is pretty cool.</text></item></parent_chain></comment><story><title>GoboLinux</title><url>https://www.gobolinux.org/</url></story>