And it works if instead of 'su' you use 'sux', but you have to create the 'sux' symlink first.
I fail to understand why a symlink may change a command behavior?? is there some alias working?
It's a common thing that lots of programs do. They look at the name they were called by and behave differently, accordingly. It's as old as the hills and not unique to unix. A simple and old example is vi / view vi and view are the same program, vi, view is a symlink to vi. When you run vi you get the normal full vi. When you run view, you get a read-only mode of vi. There are tons of similar things. gzip/gunzip, bzip2/bunzip2, mc/mcedit/mcview, some programs have several modes. star recognizes and behaves differently in reaction to being called as, star, tar, gtar, pax, ustar, and I think a few others besides. Probably the most extreme example is busybox. One binary that replaces most of /bin and /usr/bin -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org