<div dir="ltr">And for the record, if there is a difference, its not in the OS or kernel, but in the "ls" program, and which one is packaged or included in the particular system in question.</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Mar 1, 2014 at 4:51 PM, Dave Chiodo <span dir="ltr"><<a href="mailto:megadave@gmail.com" target="_blank">megadave@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Say /home/user/link is a symlink.<div><br></div><div>on both systems, try</div><div><br></div><div>ls -l /home/user/link</div><div><br></div><div>vs</div><div><br></div><div>ls -l /home/user/link/</div><div>
<br></div><div>(notice the / at the end) </div><div><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 1, 2014 at 4:40 PM, L. V. Lammert <span dir="ltr"><<a href="mailto:lvl@omnitec.net" target="_blank">lvl@omnitec.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If one does an ls on a symbolic link in BSD, it shows the files at the<br>
destination of that link; if one does an ls on a symbolic link on a<br>
current Linux system it shows the *link*, not the contents where the link<br>
points [assuming a directory, .. have not tried a file link].<br>
<br>
Something has changed in the Linux builds in the past few years [testing<br>
on an old CentOS box acts as expected]. What is the philosophy behind the<br>
change, and how would one show files at the target of a symlink now?<br>
<br>
Thanks!<br>
<br>
Lee<br>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org" target="_blank">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>