Written by oencke the 21 Apr 08 at 19:58.
Category: Installation.
Related project:
Nothing/Others.
Status: New
Rationale
The i386 ISOs do not have anything to do with Intel or the 386 cpus specifically just as the amd64 are not specific to AMD processors. Additionally these descriptors are practically meaningless to non-techies.
What matters for the decision between the ISOs is the difference between 32bit and 64bit, not intel and amd, so why not just call them that way, and thus take away the burden of having to be a cpu technician to understand them?
EDIT: As a compromise, to avoid confusion of the x86/IA ISOs with those for other architectures, descriptors like PC32bit and PC64bit might also be acceptable as that is likely the maximum a home user knows about his or her computer.
Agreed, completely. For anyone without knowledge of processor history the names i386 and amd64 not only offer little explanation of the difference between them, but could even lead to serious confusion. The amd64 version could be seen as a version created for amd processors. That while the name i386 doesn't hint to anything 32bit related, but it does hint to Intel with it's i.
Even I as experienced PC user(but linux noob) checked if there weren't "amd386" and "i64" versions. That is in the few seconds before i remembered why they would be marked as "i386" and "amd64".
REALLY confusing for anyone but the hand full of people who know about intel's x86 and amd's 64bit.
I take the point about the AMD/Intel thing, however GNU/Linux, including the Ubuntu version, supports many other CPU architectures including Arm, PPC, Sparc, MIPS. Some of which are also 64bit.
Even in the Intel/AMD 32bit space there are different instruction sets, eg: i386, i486, i686, etc.. There is a whole other debate attached to this but is a bit off this topic.
With regard to the x86 based 64bit instruction set, AMD produced and released the specification. It was only after Intel realised their marketing error that they started building CPUs that emulated the AMD 64bit instruction set.
So the issue is not quite as simple as it would seem. Simply labeling ISOs as 32bit or 64bit would lead to some ambiguity. If I saw "HardyHeron-64bit.iso", I would be forced to question, is it 64bit Sparc, or 64bit x86, or ...
I hope you get the gist of what I'm saying.
Don't get me wrong, I'm not trying to put this suggestion down. I simply believe it's something that requires a little more thought.
And, yes I do have an SGI (MIPS 64bit) workstation at home. I also have an old Sun Sparc box to play with at work. A few years ago, I even had a couple of really old (circa 1988) Sparc boxes at home that I managed to get Redhat 6.2 running on.
The Ubuntu architecture labeling _is_ non-standard. The standard nomenclature is:
A. x86-32 or ia32; B. x86-64 or AMD6; C. Itanium or ia64; D. PPC-32 or power; D. PPC-64 or power2; etc...
As Triple Omega experienced it seems even experienced user might get at least a little confused when they are first presented the choice of the different linux ISO options.
The question is now, how can we ease the decision for the average human being without the knowledge of the different cpu architectures and what can we expect from someone who doesn't have one of the typical machines?
I think, anyone with anything different than the typical "IBM compatible"/x86/... Intel/AMD computer will know that he or she will have to look beyond the mainstream/standard distribution ISO and at least know his or her architecture name.
The typical home user will probably only know that he has a PC and might have read in its advertisement if it was a 64bit processor or not.
A compromised solution might thus be to change the descriptors to PC32bit and PC64bit.
Wow, thats interessting. So far I didn't know, that I can use the AMD64 on an Intel-64bit processor. Ok ok, it doesn't have any importance to me, but its good to know.
This was actually a point of minor confusion for me when I first moved to Ubuntu. I took me a bit of searching and reading before I was convinced amd64 was what I needed on my Intel-based machine.
I think x86-32 and x86-64 are the right choices here - that matches the Linux kernel use, I think.
all this crap can be resolved by Ubuntu site that should check the CPU architecture and point every mortal to its desired download ... of course afterwards, the download could be named same for all (ubuntu.iso, kubuntu.iso, xubuntu.iso ...)
how do you distinguish between a ppc and x86 iso file that landed mysteriously on your pc?
just quickly mount the iso and read some reamdme files.
Planning to move to Hardy Heron to try Linux for the first time, one of the very first stumbling blocks as a new user was figuring out which version to download!
I definitely support some sort of improvement in the way ISOs are named, or perhaps some sort of implementation of an interactive guide as to aid a new user as to which version would be most suitable for the model of processor they own.
+1
Also please do adding in GRUB conf file 'Ubuntu x.xx 64-bit' instead of 'Ubuntu x.xx'. Because having both 32 & 64-bit system in GRUB looks same and it is confusing.
I agree with lynx. If this is to avoid confusing regular people downloading incorrect builds, then it should be a matter of _directing_ them to the right one. This doesn't necessarily involve changing how ubuntu uses architecture names (although I agree using standard names makes more sense)
I think the ubuntu download site should allow the user to choose what kind of cpu the person has (using commercially known names) and direct the person to the right build.
Sad. This item is 3 years old and tonight I was confused by the same issue. All I wasted was 22 minutes to download the correct version.
The AMD download runs on my Intel chip. The "i" download runs on someone else's AMD chip. That's good enough reason to get a better name.
Nobody cares who invented the "architecture" and most live people don't even know what an "architecture" is in this context. I bought an Intel chip. It can run 64-bit stuff. It might need 64-bit stuff if I have a large memory sticks.
I should see choices that work with this world view. In fact, the normal Ubuntu download page shows reasonable titles but the files are still named the old names and the alternative download, once you find it, uses the confusing names.