[arch-general] ls -qla lists some files twice

[Mauro Santos]

On 27-02-2015 20:44, Marcel Kleinfeller wrote:
> Hello.
> 
> I'm a bit confused because I don't know what happened here:
> 
> [root at oompf boot]# ls -qla
> total 31318
> drwxr-xr-x  3 root root   16384 27. Feb 21:38 .
> drwxr-xr-x 20 root root    4096 27. Feb 21:31 ..
> -rwxr-xr-x  1 root root    4423 27. Feb 04:04 bcm2708-rpi-b.dtb
> -rwxr-xr-x  1 root root    4702 27. Feb 04:04 bcm2708-rpi-b-plus.dtb
> -rwxr-xr-x  1 root root   17856 27. Feb 03:59 bootcode.bin
> -rwxr-xr-x  1 root root     175  6. Feb 03:16 cmdline.txt
> -rwxr-xr-x  1 root root    6967 27. Feb 04:18 config.txt
> -rwxr-xr-x  1 root root       0 22. Jan 04:17 config.txt.pacnew
> -rwxr-xr-x  1 root root    1669 15. Okt 23:15 config.txt.pacsave
> -rwxr-xr-x  1 root root    1669 15. Okt 23:15 config.txt.pacsave
> -rwxr-xr-x  1 root root   18693 23. Feb 2014  COPYING.linux
> -rwxr-xr-x  1 root root   18693 23. Feb 2014  COPYING.linux
> -rwxr-xr-x  1 root root    2353 27. Feb 03:59 fixup_cd.dat
> -rwxr-xr-x  1 root root    6150 27. Feb 03:59 fixup.dat
> -rwxr-xr-x  1 root root    9202 27. Feb 03:59 fixup_x.dat
> -rwxr-xr-x  1 root root    2048  1. Jan 1980  FSCK0000.REC
> -rwxr-xr-x  1 root root 9790472 23. Feb 2014  kernel_emergency.img
> -rwxr-xr-x  1 root root 9790472 23. Feb 2014  kernel_emergency.img
> -rwxr-xr-x  1 root root 5528968 27. Feb 04:17 kernel.img
> -rwxr-xr-x  1 root root    1447 19. Jan 17:33 LICENCE.broadcom
> -rwxr-xr-x  1 root root    1447 19. Jan 17:33 LICENCE.broadcom
> drwxr-xr-x  2 root root    2048 27. Feb 21:31 overlays
> -rwxr-xr-x  1 root root  555672 27. Feb 03:59 start_cd.elf
> -rwxr-xr-x  1 root root 2651256 27. Feb 03:59 start.elf
> -rwxr-xr-x  1 root root 3608936 27. Feb 03:59 start_x.elf
> 
> Is it save to reboot and if not, how can I rebuild my /boot directory?
> 

You should ask the archlinuxarm guys, archlinux does not support the
raspberry pi or any other arm board.

That said it works fine for me on the rpi, so I suspect you might have a
problem with the filesystem and you should do a fsck.

-- 
Mauro Santos