Package: coreutils
Version: 5.2.1-2
Severity: normal

I noticed today some weird behavior with ls. After years and years of using
UNIX-type systems, I have become pretty accustomed to 'ls -a' displaying all
files beginning with a . first, and then "regular" files. today, I noticed
that the files were being sorted alphabetically, and the . seemed to be
getting ignored. 

I also just noticed that a filename starting with a capital letter is not
being sorted before filenames beginning with lowercase letters, which is
also not the "normal" behavior that I am used to. 

here's a sample: 

(11:14:13) [EMAIL PROTECTED]:~> ls -al ~test 
total 10 
drwxr-xr-x  2 test test  2048 2007-02-08 11:14 .
drwxrwsr-x  8 root staff 2048 2007-02-08 10:01 ..
-rw-r--r--  1 test test     0 2007-02-08 11:13 Alpha 
-rw-------  1 test test   221 2007-02-08 11:14 .bash_history 
-rw-r--r--  1 test test   567 2007-02-08 09:52 .bash_profile 
-rw-r--r--  1 test test  1834 2007-02-08 09:52 .bashrc 
-rw-r--r--  1 test test     0 2007-02-08 11:13 beta 
-rw-r--r--  1 test test     0 2007-02-08 09:52 moo 
-rw-r--r--  1 test test     0 2007-02-08 11:14 Sigma 
-rw-r--r--  1 test test     0 2007-02-08 09:53 .test

this happens for any normal user, regardless of the shell. 

what makes this extra strange is that if I su, or log into the console as
root, the "correct" behavior occurs: 

badger:~# ls -al ~test 
total 10 
drwxr-xr-x  2 test test  2048 Feb  8 11:14 . 
drwxrwsr-x  8 root staff 2048 Feb  8 10:01 ..
-rw-------  1 test test   221 Feb  8 11:14 .bash_history 
-rw-r--r--  1 test test   567 Feb  8 09:52 .bash_profile 
-rw-r--r--  1 test test  1834 Feb  8 09:52 .bashrc 
-rw-r--r--  1 test test     0 Feb  8 09:53 .test 
-rw-r--r--  1 test test     0 Feb  8 11:13 Alpha 
-rw-r--r--  1 test test     0 Feb  8 11:14 Sigma 
-rw-r--r--  1 test test     0 Feb  8 11:13 beta 
-rw-r--r--  1 test test     0 Feb  8 09:52 moo


I am using etch (testing), and the coreutils version reported by 'ls
--version' is 5.2.1. there is no ls option I can find that modifies this
behavior, nor can I find any documentation about it anywhere. two friends of
mine are running sarge, one with ls 5.97, and one with ls 5.2.1. neither
demonstrates this issue. 


-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.8
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages coreutils depends on:
ii  libacl1               2.2.23-1           Access control list shared library
ii  libc6                 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to