Are There Any Difference In Directories Or Filenames In The The Ubuntu Root Filesystem Of A Linux Ubuntu v.11.10 Between A 32-Bit And A 64-Bit Operating System Platforms?

Bazingeroo
Bazingeroo used Ask the Experts™
on
I have a question regarding the Linux Ubuntu Root Filesystem within my Linux Ubuntu v.11.40 64-bit operating system platforms.

Are there any difference in directories or filenames in the The Ubuntu Root Filesystem between a Linux Ubuntu v.11.10 32-bit and a 64-bit operating system platforms? If you just missed it, I addressing the computing processes here – 32-bit and 64-bit applicable to/comparing within the Ubuntu Root Filesystem. Please explain.

Please explain their differences in terms of their directories and filenames, their similarities in their directories and filenames, their purposes of each directory type, how each directory type functions, and their full and complete directory path name for each directory type. Regarding the last part “and their full and complete directory path name for each directory type” weblink(s) might be useful here since there 'so many' of them I would presume. If you have any weblink(s) regarding informative resources/references for this question/thread as well, please provide them.  

Please reply.

Thank you!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Directory structure and file names (excluding kernel files etc that are specific to the 64 bit architecture) are the same.

Both the 32 bit and 64 bit versions will follow this basic directory structure:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/

As for "Full and complete directory path name for each directory type" I'm not certain I understand what you are looking for.  If the above link doesn't answer that can you expand on the question a bit or give me an example?
Distinguished Expert 2017
Commented:
There will be. /lib64 /usr/lib64

What in particular are you looking for.
Using the file command, you can determine if an program is 32 or 64 bit.

Author

Commented:
@ arnold & atechnicnate:

Hello. Nice to see you again, arnold. Nice to meet you atechnicnate.

Thank you for your both for your comments.

Okay, arnold, so you are saying that there is differences then? You're in contrast to atechnicnate's answer that indicates there are 'none'. So, to answer you question ("What in particular are you looking for."), I am looking for 'ALL' 32&64-bit file directory distinctions of them relative to the very Linux filesystem structures starting from individual high-level directories (starting from the top or the root or /).

Now, please don't think I am crazy to ask you to list ALL of them IF I there are 'MANY" of them in Linux 64-bit operating systems. Please let me explain...
 
Now if you say there is one file type or structure distinction between 32&64-bit, then there 'usually' is more than one, right? (I assume so.) Then I assume there are too many to list here or not? If so, then, please send me a webpage link to this very issue (I do not expect you to give me ALL of them if there are indeed too many.) that describes the full directory listings (MAYBE NOT ALL THEM LISTED 'IF" the list is TOO BIG and NOT COMPLIED), but at least describes the top level or high-level directories starting from the top or the root or / with at least 2-3 sublevels in the hierarchy filesystem with these 32&64-bit distinctions. Is this doable? I need to understand this. Like I said, a VERY GOOD webpage link that addresses this with a listing in itself is just fine.  

Please reply.

Thank you!
Distinguished Expert 2017
Commented:
usually, the file structure remains the same as pointed out by the link atechnicnate provided with the exclusion of the extra lib64 in the various location.
In linux it is common to install packages of the same bit even though 32bit programs can and will work.

I know that on a Solaris based system there was a application that effectively was a determinant when ran to open the correct binary/program on a 64 bit system.
I.e. /usr/bin/programname would be this special application, when executed it will determine the system type and the bit of the OS, then it will check the paths for 64 bit binaries to see if there was an existing command for programname, if not it will check the 32 bit which will then run.  As far as the user is concerned, it was transparent.
Thouch this required that when one compiles the system they make sure to separate the 64bit binary install from the 32 bit binary install.

AIX might be similar to its structure setup for mixed 32/64 paths though I am not certain.

I think the answer you are looking for deals with a condition where there are a mix of 32bit and 64bit programs compiled and installed on the system and you would like to find out what the convention would be to distinguish between them.

i.e. if you are compiling the programs/servers yourself or you are planing on creating your own packages and would like to have info on how the 32bit package will vary from the 64 bit?


usually, the configure auto detects the type of system.
You could use a 64bit system to build packages for a 32bit system provided you have the 32bit libraries installed. For the reverse, you have to have the 64bit libraries as well as a compiler that can perform the 64bit compilation like gcc.

http://www.cyberciti.biz/tips/compile-32bit-application-using-gcc-64-bit-linux.html
Here's the two root directory setups.  One is from a 64 bit install (debian) and one is from a 32 bit install (Ubuntu, which is a child of debian so to speak).  arnold was correct I mis-spoke sorry.  There is a minor lib difference (see below) but other than that it's the same.  Does this provide what you were looking for?

slog:/$ uname -a
Linux syslog 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux
slog:/$ ls
bin   etc         lib    lost+found  opt   sbin     sys  var
boot  home        lib32  media       proc  selinux  tmp  vmlinuz
dev   initrd.img  lib64  mnt         root  srv      usr

desktop:/$ uname -a
Linux nate-desktop 2.6.38-13-generic #56-Ubuntu SMP Tue Feb 14 12:40:40 UTC 2012 i686 i686 i386 GNU/Linux
nate@nate-desktop:/$ ls
bin    etc             lib         opt   sbin     tmp    
boot   home            lost+found  proc  selinux  usr
cdrom  initrd.img      media       root  srv      var
dev      mnt         run   sys      vmlinuz
desktop:/$

Author

Commented:
@ atechnicnate & arnold:

Hello again.

Thank you for your latest comments.

Regarding the latest comment for arnold, thank you for the extra knowledge you have extended to me. However, I was just curious as the Linux Ubuntu filesystem structure differences only between the 32-bit and 64-bit versions that you have provided me that in his first response. I was only reiterating in my second comment of this question/thread of this post for this question/thread in different terms so atechnicnate could understand my question at the time atechnicnate responded with conflicting response from arnold's comment. I see it worked since atechnicnate provided me a different means with the same answer as arnold's where atechnicate 'detailed specifically' through means testing the differences in filesystem structure in his last comment in order to support his claim. Thank you for that.

So the answer is: /usr/lib32  and /usr/lib64 .

Thank you.

So I am going to close this question/thread now.

Since arnold gave me the answer FIRST and reiterated it in his second comment; and atechnicnate detailed the answer through testing in his last comment – these are the comments that will get rewarded  for points. Arnold will get the Accepted Solution with 375 points for his first comment and first correct answer. atechnicnate will receive 100 points (as a Assisted Solution) for his last correct comment as a supported and researched comment. arnold will get 25 points for his second comment as a factually true reiterated comment.  

Oh, I forgot to mention. I truly like the weblink in atechnicnate's first comment. It is so visual and so simplified with compromising applicable, factual, and principled information that this was printed in hard copy and stored in my records for future reference. Thank you for that!  

Again, thank you both very much!!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial