but if you do "file bin" you get bin: symbolic link to `usr/bin'
:-)
]]>file /bin
for example.
]]>What do you mean when you say that every file in there is linked?
/bin, /sbin and /usr/sbin should themselves be links. They should not contain links.
lrwxrwxrwx 1 root root 7 Mai 31 19:40 /bin -> usr/bin/ lrwxrwxrwx 1 root root 7 Mai 31 19:40 /sbin -> usr/bin/ lrwxrwxrwx 1 root root 3 Mai 31 19:40 /usr/sbin -> bin/
Hi- Hmmm, I think this requires an explanation... I see that /bin /sbin/ and /usr/sbin directories are symbolic links, but what I meant is that if you cd into /bin for example, and do "file filename" on any file in there, it'll show that it's "dynamically linked"... I mistook this for meaning a symbolic link.
Example:
└──╼ file mev
mev: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=24cd2c473bdaa7d951bbf9e14b2792646b6b4932, stripped
/bin, /sbin and /usr/sbin should themselves be links. They should not contain links.
lrwxrwxrwx 1 root root 7 Mai 31 19:40 /bin -> usr/bin/
lrwxrwxrwx 1 root root 7 Mai 31 19:40 /sbin -> usr/bin/
lrwxrwxrwx 1 root root 3 Mai 31 19:40 /usr/sbin -> bin/
No, ls -l / should show that those are links to /usr/bin, and you do need them.
Yeah I see that every file in there is linked. Do you know if eventually they plan on doing away with /bin and /sbin? I thought they were migrating all the files to /usr/bin and removing the other directories to make it easier for the developers.
]]>