Not anymore. At the time, yes, that may very well have been the case, though not necessarily for all UNIX-like operating systems. It was a compatibility requirement.
Actually the FHS states specifically for AMD64, PPC64, s390x and sparc64 that native (64-bit) libraries go in/lib64 while 32-bit (31-bit for s390) libraries go in/lib because the number of 32-bit binaries/libraries are expected to far outweigh the number of 64-bit binaries/libraries. It also states specifically for IA-64 that native (64-bit) libraries go in/lib as it reflects the deprecation of 32-bit binaries (and libraries) on that architecture.(source) For any other architecture, 64-bit or not,/lib32 and/lib64 might coexist with/lib being a symlink to one of them.(source) I presume that */lib and */libXX would be expected to be similar to/lib and/libXX. After all, who wants 64-bit binaries in/lib and 32-bit binaries in/lib32 but 64-bit libraries in/usr/lib64 and 32-bit libraries in/lib? However, the last version of the FHS was completed in 2004. Some deviation should be expected, especially when you consider how many 64-bit distros are in use compared to back then. It has been seven years after all. Time for a new FHS version?:)
Right? You play a space ship pilot (who knows if the pilot is from Earth or some other celestial body?), and extraterrestrials are invading your home world. The object of the game: defeat them before they defeat you. Seriously, how do you create a plot from something as simple as that?
That's a problem with the Spanish language... Just kidding.
There is a difference between simple in theoretical usage and simple in actual usage, the latter being "intuitive." Obviously this is one example of simple in the theoretical.
Let's face it: if many people don't know what it is, they will explore just to figure it out. If someone doesn't know and won't experiment, it is probably due to the fear of the unknown. This is a result of being unable to separate "safe exploration" with "unsafe exploration" in my opinion. For example, you might try microwaving some sort of food that is meant to be put in an oven to see if it'll cook faster or whatever. However, if you hear a strange noise in your home, you most likely wouldn't go exploring without some means of protection. The phone offers no protection from the unknown, a problem for those who need some sort of security guarantee that the phone won't suddenly go bad or take you completely away from where you want to go.
Slashdot Mirror
in another universe
Not anymore. At the time, yes, that may very well have been the case, though not necessarily for all UNIX-like operating systems. It was a compatibility requirement.
Actually the FHS states specifically for AMD64, PPC64, s390x and sparc64 that native (64-bit) libraries go in /lib64 while 32-bit (31-bit for s390) libraries go in /lib because the number of 32-bit binaries/libraries are expected to far outweigh the number of 64-bit binaries/libraries. It also states specifically for IA-64 that native (64-bit) libraries go in /lib as it reflects the deprecation of 32-bit binaries (and libraries) on that architecture.(source) For any other architecture, 64-bit or not, /lib32 and /lib64 might coexist with /lib being a symlink to one of them.(source) I presume that */lib and */libXX would be expected to be similar to /lib and /libXX. After all, who wants 64-bit binaries in /lib and 32-bit binaries in /lib32 but 64-bit libraries in /usr/lib64 and 32-bit libraries in /lib? However, the last version of the FHS was completed in 2004. Some deviation should be expected, especially when you consider how many 64-bit distros are in use compared to back then. It has been seven years after all. Time for a new FHS version? :)
Right? You play a space ship pilot (who knows if the pilot is from Earth or some other celestial body?), and extraterrestrials are invading your home world. The object of the game: defeat them before they defeat you. Seriously, how do you create a plot from something as simple as that?
with her good looks
That's a problem with the Spanish language... Just kidding. There is a difference between simple in theoretical usage and simple in actual usage, the latter being "intuitive." Obviously this is one example of simple in the theoretical. Let's face it: if many people don't know what it is, they will explore just to figure it out. If someone doesn't know and won't experiment, it is probably due to the fear of the unknown. This is a result of being unable to separate "safe exploration" with "unsafe exploration" in my opinion. For example, you might try microwaving some sort of food that is meant to be put in an oven to see if it'll cook faster or whatever. However, if you hear a strange noise in your home, you most likely wouldn't go exploring without some means of protection. The phone offers no protection from the unknown, a problem for those who need some sort of security guarantee that the phone won't suddenly go bad or take you completely away from where you want to go.