Re: Troubleshooting with ln

[Jim Meyering]

Luc Anderbourg <address@hidden> wrote:
> I've encountered problems with compiling kismet... In fact, the makefile 
> routin is trying to make a symbolic link of a directory but this message
> appears and close unapproprietly the make of the application :
>
> make[1]: Entre dans le répertoire `/mnt/win_e/kismet-2.8.1/libpcap-2002.12.23'
> rm -f bpf_filter.c
> ln -s /mnt/win_e/kismet-2.8.1/libpcap-2002.12.23/bpf/net/bpf_filter.c 
> bpf_filter.c
> ln: création d'un lien symbolique `bpf_filter.c' vers 
> `/mnt/win_e/kismet-2.8.1/libpcap-2002.12.23/bpf/net/bpf_filter.c': Opération 
> non permise
> make[1]: *** [bpf_filter.c] Erreur 1
> make[1]: Quitte le répertoire `/mnt/win_e/kismet-2.8.1/libpcap-2002.12.23'
>
> I've the right to execute ln (I'm superuser) but I don't understand why this 
> an unappropried way to manage with ln -s. May you help me??

Since your current directory is /mnt/win_e/kismet-2.8.1/libpcap-2002.12.23
and the `/mnt' prefix suggests that it's not a local file system,
one possibility is that `root' doesn't have write permission in that
directory.  It could be that that file, the containing directory, or the
entire destination file system are marked as read-only (and you wouldn't
see that via `ls -l') or covered by a restrictive ACL.