[Android Software/Hacking General [Developers Only]] Almighty2:
In that example, the first part of the answer was exactly what I was thinking, xbin is more clean of a directory so it's easier to maintain stuff you added. I guess in my case, until something needs su that doesn't work, I wouldn't need to get the symlink in bin and ofcourse once that happens, it'll be something I'll always do.

I couldn't do with a 32 bit OS because I have over 300 tasks running and even my browser has 150+ tabs running at once so it will hit the memory limitations sooner than later, besides, only 3GB out of 4GB is usable on a 32bit OS.

Just like what I thought, Samsung and HTC are the brands which have a weird way of how things work because the OS is not stock Android but rather, they customize it so that could be a reason why things had to work a certain way. The symlink isn't a bad idea but I think the people who copy su to two places are because let's say you update the apk and it wants to install a newer su binary, you have to remember to manually update the other copy of the su binary which is easy if that was the only app that had a update. I update about 50 apps a week and then it goes to Titanium Backup for backing up so it's not exactly a easy process and time consuming too, especially with 4 devices + BS added.

In my case, I try to make all my devices identical in the apps and everything so if I do it on one, it will need to be done on another.

In any case, I think what we are trying to figure out is how to get SuperSU with a working su binary. I might be the version of SuperSU as 4.4.5 and older works on more devices than the newest version and who knows, maybe they don't have x86 support which is what BS needs instead of the ARM version which I could grab from another device.

I think it was you saying you were reading about this and that, which made it seem like you read about things rather than experiment with it since like I said warlier, it's faster for you to type "which su" in the terminal or shell.

Actually, there really is no real answer on the why 2 su's since even in the link you provided, the answer was just a person's guess and it seems like some people put it at one location while others put it at the other location and no one has complained yet. If things didn't work correctly, those who root stock roms would have been making the changes already.

You're right there are 2 Superuser apps named "SuperUser" and the ChainsDD seems to be the one people jump ship to the competitors. The one from CWM, never used it but people on droid-life said CWM has lack of support and it seems everyone likes SuperSU. I thought everyone used the ChainsDD version since doesn't the BS rooting method and the instructions you posted actually use the ChainsDD version? All I know is that updating the CWM version in Google Play to 1.0.2.3 along with a updated su binary resulted in root no longer working until one uninstalls the SuperUser updates and go back to the binary that the SuperUser 1.0.2.1 in /system/app installs so not sure why 1.0.2.3 doesn't work. I haven't used ChainsDD's Superuser in quite awhile after it was causing lags when I updated a few years ago and moved to SuperSU which does have individual app notification settings. I know people in the OBackup app thread on xda are having problems with the CWM Superuser and installing SuperSU fixed the problem for them, all of those people were on Samsung/HTC/LG devices running CM which you can see from this thread even in the latest posts:

http://xdaforums.com/showthread.php?t=2040507

I think the su question is almost like the busybox question, some people install it in /system/bin while others like myself installs it in /system/xbin because that was the location the rooted stock rom's installed it. Ofcourse unlike su, doing symlinks for all the aliases in /system/bin would be no easy task and there are some people who claim that their busybox doesn't work correctly in /system/xbin but works fine in /system/bin.