On Wed, 2004-06-09 at 20:13 +0200, Oliver Bock wrote:
> Thanks guys,
> considering your answers I think my approach will be getting the 64bit kernel
> package in a few weeks and stick to 32bit userspace until I can't stand it
> anymore and reinstall with pure64... Meanwhile I certainly need a working
> biarch toolchain for (after using the initial package) compiling my own 64bit
> kernel right? If so, will there be a nice upgrade from my current 32bit-only
> gcc etc. to biarch-versions and even make-kpkg support?
That is quite conservative.
What I did for myself, was to have partitions for / /boot /var
and /pure64 (plus a few others that aren't germane here).
I installed 32-bit, and then built and installed a bi-arch kernel.
Once the kernel was installed, I debootstrapped the /pure64 partition
from the instructions in the HOWTO, and played around in there for a
while.
When I was comfortable that all of the software I wanted was available
and working, I rebooted, with /pure64 switched to / and / switchd
to /x86-32. Actually, I did this by adding a whole pile of lines to my
Grub config so that I could switch, should I desire, and I made it
non-default initially, to be conservative.
Now, things are humming just fine and dandy, and I haven't needed that
32-bit stuff for a good while. 32-bit is no longer a default for me in
Grub, and the time is coming when the options should be removed, and the
partition can be returned to the spare space.
Cheers,
Andrew.
-------------------------------------------------------------------------
Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201 MOB: +64(21)635-694 OFFICE: +64(4)499-2267
The truth is rarely pure, and never simple. -- Oscar Wilde
-------------------------------------------------------------------------
Attachment:
signature.asc
Description: This is a digitally signed message part