If both '''.iso''' files already exist the '''f15-live.ks''' file is not used at all. '''f15-live.bin''' is a 2GB image suitable for flash disk (like '''/dev/sdX''' where '''X''' is for example '''d''', CHECK THE MEDIA NAME IN YOUR CASE). You should never use the partition names (like '''/dev/sdX1'''). Example command is:

If both '''.iso''' files already exist the '''f15-live.ks''' file is not used at all. '''f15-live.bin''' is a 2GB image suitable for flash disk (like '''/dev/sdX''' where '''X''' is for example '''d''', CHECK THE MEDIA NAME IN YOUR CASE). You should never use the partition names (like '''/dev/sdX1'''). Example command is:

Line 51:

Line 53:

One should test it both with x86_64 hardware CPU (equivalent to '''qemu-kvm -cpu qemu64''') and also with i686 hardware CPU ('''qemu-kvm -cpu qemu32''') to verify '''ifcpu64.c32''' boots the right distro variant. Real iron can be also used.

One should test it both with x86_64 hardware CPU (equivalent to '''qemu-kvm -cpu qemu64''') and also with i686 hardware CPU ('''qemu-kvm -cpu qemu32''') to verify '''ifcpu64.c32''' boots the right distro variant. Real iron can be also used.

+

+

== Similar projects ==

+

+

None of the projects below provides the primarily/sole purpose of [[Biarch Spin]] (see Summary). I do not mind porting the '''ifcpu64.c32''' support to any of the scripts below but they have other deficiencies compared to the '''f15-live.sh''' build script provided here. I can port '''f15-live.sh''' to Perl-5 upon request.

Most installations can benefit from x86_64 increased performance thanks to twice the more available registers together with better new ABI resulting in less memory swapping, also thanks to 64bit calculations without registers pairing, more efficient addressing modes used for example in shared libraies and wider data management capabilities thanks to the unlimited addressing space. Still many installations are present in 32bit mode as people are not sure whether they have 64bit capable hardware. This installation can autodetect the best installation mode for their system.

Software developers can benefit from easier code thanks to the new addressing modes. Users can also benefit from the simplicity of a single kernel variant (no longer need for PAE and/or regular kernel variants).

If both .iso files already exist the f15-live.ks file is not used at all. f15-live.bin is a 2GB image suitable for flash disk (like /dev/sdX where X is for example d, CHECK THE MEDIA NAME IN YOUR CASE). You should never use the partition names (like /dev/sdX1). Example command is:

cat f15-live.bin >/dev/sdX

As the biarch image is provided as a flash disk image including partition table for one 2GB FAT partition the ISO label is not applicable. FAT image has label LIVE, both ext3fs.img files have label _f14-live. The images get found by UUID such as: root=live:UUID=7404-2829

The provided .ks file is not essential for this Spin, the .ks' file can be dropped. Just the default CD size times 2 is not much useful as the nearest higher available flash disks are 2GB. Therefore I have provided some additional packages in the supplied .ks file. I changed there some personal boot defaults but those can be either also dropped or imported to the system .ks files.

One should test it both with x86_64 hardware CPU (equivalent to qemu-kvm -cpu qemu64) and also with i686 hardware CPU (qemu-kvm -cpu qemu32) to verify ifcpu64.c32 boots the right distro variant. Real iron can be also used.

None of the projects below provides the primarily/sole purpose of Biarch Spin (see Summary). I do not mind porting the ifcpu64.c32 support to any of the scripts below but they have other deficiencies compared to the f15-live.sh build script provided here. I can port f15-live.sh to Perl-5 upon request.