FS#44672 - [linux] Add 64 bit kernel package to 32 bit arch

Attached to Project: Arch Linux
Opened by Tomas Mudrunka (harvie) - Tuesday, 21 April 2015, 02:09 GMT
Last edited by Allan McRae (Allan) - Tuesday, 21 April 2015, 11:40 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Hello, i have good reasons to use 32 bit userspace, however i would profit from using 64 bit kernel on arch.

Can you please make linux and linux-lts packages from arch64 installable on arch32 by adding arch=('x86_64' 'i686') to pkgbuild. and "symlink" these to arch32 repo as (eg.) linux-64 and linux-64-lts?
so i can use it on 32b arch too...

Thanks
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 21 April 2015, 11:40 GMT
Reason for closing:  Won't implement
Comment by Doug Newgard (Scimmia) - Tuesday, 21 April 2015, 02:43 GMT
I don't think you understand how the "arch" array works. Nor conflicting files.

There are a number of ways to do this now, although I can think of very few "good" reasons to.
Comment by Allan McRae (Allan) - Tuesday, 21 April 2015, 03:52 GMT
"pacman -S --arch x86_64 linux" then add linux to NoUpgrade in pacman.conf so it does not update to the 32 bit version. Then you need to deal with all your modules... and remember to use linux32 in your kernel line for your bootloader.
Comment by Paul Bredbury (brebs) - Tuesday, 21 April 2015, 09:26 GMT
"good reasons to use 32 bit userspace" - more info required.

Probably less hassle (and certainly more future-proof) to go multi-lib, i.e. primarily 64-bit.
Comment by Tomas Mudrunka (harvie) - Tuesday, 21 April 2015, 11:32 GMT
"then add linux to NoUpgrade in pacman.conf"

But that will prevent me from upgrading kernel automatically using pacman -Syu

"good reasons to use 32 bit userspace" =

1.) i need to quickly migrate my system between 64b and 32b machines and virtual machines. Eg. so i can run my system on 32b machine when needed just by selecting 32b kernel in grub.
2.) 64b is not well supported by some vendors, binary software, etc... Also i don't like multilib setup. Just don't want to have libraries twice when i don't need real 64b userspace.
Comment by Tomas Mudrunka (harvie) - Tuesday, 21 April 2015, 11:35 GMT
"I don't think you understand how the "arch" array works. Nor conflicting files."

I think that 64b kernel can be easily installed on 32b system under different name. Well maybe you can't simply copy package from arch64. But it can be done somehow. After all in debian it works without any problems as expected. You just install another kernel same way you install eg. linux-lts. There's no conflict with linux package.

Loading...