You are not logged in.
I want to run a 64bit kernel on 32bit userspace. I know there are some out there who claim it's only bad and slowing down the transition to full blown 64bit systems. That may be, but for me and for this particular computer, I need to do this.
I have tried it on my work laptop and there are no problems whatsoever: On my plain vanilla 32bit install I downloaded and installed the current 64bit kernel (after carefully backing up the current one). No problems anywhere, so far.
However, for this other machine, I need to have a sane solution for the long run. What about kernel updates? When a new kernel is released, pacman is going to want to install the 32bit one instead of the 64bit version I want to use. I don't suppose there is a way to "tag" the kernel package to be x86_64 instead of i686, or something to that effect?
I'd be happy to hear your thoughts on this.
Offline
64bit arch has 32bit library packages.
Offline
I am aware of this. What I want to do is run a 64bit kernel on the regular 32bit userland.
Offline
put kernel26 in HoldPkg and each time it wants to be updated, install the 64bit one.
Offline
make a custom repo and add it above core. there you can have kernel26 and other package that depends on it, like nvidia
Last edited by wonder (2009-08-24 20:30:22)
Give what you have. To someone, it may be better than you dare to think.
Offline
Thanks for your suggestions. I'll look into them. flamelab's solution was very simple so it's likely that I go with that.
Offline
Maybe Allan's blog post on the subject will help:
Offline
put kernel26 in HoldPkg and each time it wants to be updated, install the 64bit one.
According to pacman.conf(5), HoldPkg only seems to have any effect when attempting to remove a package:
HoldPkg = package ...
If a user tries to --remove a package that's listed in HoldPkg, pacman will ask for confirmation before proceeding.
I'll go with the local repository route.
Offline
Use IgnorePkg, not HoldPkg.
Offline
flamelab wrote:put kernel26 in HoldPkg and each time it wants to be updated, install the 64bit one.
According to pacman.conf(5), HoldPkg only seems to have any effect when attempting to remove a package:
pacman.conf(5) wrote:HoldPkg = package ...
If a user tries to --remove a package that's listed in HoldPkg, pacman will ask for confirmation before proceeding.I'll go with the local repository route.
Well, I have pacman on HoldPkg, and I thought that HoldPkg makes the package manager to ask for a package to be installed before the others. It seems that I'm wrong
Offline