On 23.05.2010 20:22, Matthew Burgess wrote:
> What about `type -a ls'?
Yupp, works as advertised :-)
Forgive me for not reading the manual before replying /shame on me/
Lars
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsu
On Sun, 23 May 2010 20:07:00 +0200, Lars Bamberger
wrote:
> hermes~> type ls
> ls is aliased to `ls -F --color=auto --show-control-chars'
>
> Nope. It won't tell me about the executable /bin/ls.
What about `type -a ls'?
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-s
Lars Bamberger wrote:
> Nope. It won't tell me about the executable /bin/ls.
What you want is `ls --version`
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
On 22.05.2010 10:35, Nicolas Richard wrote:
>> Find out what command is actually executed when you type 'ls'. Do a
>> 'which ls' or 'alias ls' if which is not installed.
>
> I think 'which' will not tell you if there is an alias (maybe it depends
> on version used), so 'alias' might be a better fi
On 5/23/10, Bruce Dubbs wrote:
>
> On an LFS 6.5 system, my $LS_COLORS has hl=44;37 and it is recognized
> fine by ls. It is generated by the entry in /etc/dircolors of
>
> HARDLINK 44;37 # regular file with more than one link
>
Interesting!
On an LFS 6.6 system, instead of HARDLINK, there is
Rodolfo Perez wrote:
> On Sat, 2010-05-22 at 14:57 -0500, Bruce Dubbs wrote:
>> That doesn't make sense. Both dircolors and ls are from coreutils. If
>> you use the same version of coreutils to generate /etc/dircolors, then
>> ls should understand it.
>>
>> On a recent LFS system, /etc/dircolor
On 5/23/10, Rodolfo Perez wrote:
> Hmm ... but I do get the message:
>
> root [ /etc ]# ls
>>> ls: unrecognized prefix: hl
>>> ls: unparsable value for LS_COLORS environment variable
>
> with lfs 6.4 (coreutils-6.12).
>
> Bruce can you explain this? Is lfs 6.4 "too old"?
> Could it be an erro
