| 1 |
Mark Knecht posted |
| 2 |
<5bdc1c8b0603111127l3caf70f8q754e5d4b8ddefd97@××××××××××.com>, excerpted |
| 3 |
below, on Sat, 11 Mar 2006 11:27:50 -0800: |
| 4 |
|
| 5 |
> QUESTION: Should I not (somehow) be able to boot my chrooted 32-bit |
| 6 |
> environment instead of 64-bit as a grub option? I've not tried to do |
| 7 |
> that on this machine. It's always run 64-bit from day 1. |
| 8 |
|
| 9 |
Yes, you should, provided you have built an entire 32-bit system, kernel |
| 10 |
and all included. The 32-bit system will need to be on its own partition |
| 11 |
as well, I believe, or at least that would be simplest. |
| 12 |
|
| 13 |
You /should/ be able to boot a 64-bit kernel with a 32-bit userland, as |
| 14 |
well, given of course that you've opted for 32-bit executable support, |
| 15 |
which I assume you have if you are running a 32-bit chroot. Just point |
| 16 |
root at your 32-bit root partition, but load a 64-bit kernel. |
| 17 |
|
| 18 |
As for the parallels problem... It's apparently trying to install a |
| 19 |
32-bit module (binary-only slaveryware I assume) in a 64-bit kernel. |
| 20 |
That's not going to work for the same reason 32-bit libraries won't work |
| 21 |
in 64-bit executables. You'll need a 32-bit kernel, the first option |
| 22 |
above. Of course, that means you won't be able to do 64-bit at all until |
| 23 |
you reboot to 64-bit. |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman in |
| 29 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-amd64@g.o mailing list |
Archives