I found this. It is a neat article explaining why.<br><br>
<a href="http://www.testingeducation.org/k04/examples/spec06s.html">http://www.testingeducation.org/k04/examples/spec06s.html</a><br>
<br><div><span class="gmail_quote">On 12/15/05, <b class="gmail_sendername">Les Mikesell</b> <<a href="mailto:lesmikesell@gmail.com">lesmikesell@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 2005-12-15 at 09:49, <a href="mailto:rengland@europa.com">rengland@europa.com</a> wrote:<br>> >><br>> >> >From the MS documetation ...<br>> >><br>> >> <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-">
http://msdn.microsoft.com/library/default.asp?url=/library/en-</a><br>> >> us/fileio/fs/naming_a_file.asp<br>> >><br>><br>><br>> The classic case is the creation of a directory called "test" in *nix.
<br><br>There is nothing magic about a directory or any other file named<br>test.  You might be surprised at what happens when you try to<br>execute a command named "test" without supplying the path to<br>it - at least if you don't already know it is a shell built-in.
<br>In *nix, connections to devices are always through filenames<br>connected by their major/minor device numbers instead of magic<br>in the name itself.  Except Linux cheats on the network devices<br>and doesn't bother with putting eth0 (etc.) in the filesystem with
<br>associated permissions.<br><br>--<br>  Les Mikesell<br>    <a href="mailto:lesmikesell@gmail.com">lesmikesell@gmail.com</a><br><br><br>--<br>fedora-list mailing list<br><a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com
</a><br>To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list">https://www.redhat.com/mailman/listinfo/fedora-list</a><br></blockquote></div><br><br clear="all"><br>-- <br>Jonathan Carpenter<br>Linux System Administrator
<br>Windows System Administrator<br><The Unix Geek>