Why are there non-i386 packages in the i386 directory?
Like Fedora, we decided not to use the method of splitting sub-architecture packages up like Red Hat Linux did. We separate by base architecture, not sub-architecture. Examples of base architectures are i386, x86_64, sparc, etc. Examples of sub-architectures of i386 are i486, i586, i686, and athlon. RPM, yum, and apt are all capable of sorting them out and using the appropriate.
Related Questions
- On current systems, however, you can simply copy the zImage or bzImage file (in arch/i386/boot/ to the /boot/ directory on the root file system, or to a floppy using the dd command. Refer also to the question, How do I get LILO to boot the kernel image?
- How do I set the base directory for creating the packages created by assembly?
- Why are there non-i386 packages in the i386 directory?