On Sat, 11 Feb 2012 10:58:30 +0100, Randy Bush <ra...@psg.com> wrote:
These statements are false, esp. worrying is that they are
interwinned with some facts that get tilted to support false
presumption.
Kernel do not care about which interpreter is /libexec/ld-elf.so.
The path to the interpreter is specified in the binary itself. So if you
have 32bit binary that put '/libexec/ld-elf.so.1' into PH_INTERP,
and /libexec/ld-elf.so.1 is 32bit, then amd64 kernel properly executes
that combination.
Kernel has a hack that falls back to try to use /libexec/ld-elf32.so.1
for some 'brands' of ELF images, in particular, for 32bit binaries. This
is done to help in situation when 32bit binaries also specified the
same path for interpreter.
If you have 32bit world installed and booted 64bit kernel, it will boot.
It is the same as running 32bit world in the jail.
The management functions, like configuring network interfaces, ZFS
and many other system setup functionality does not work, indeed.
as the system in this case is half the planet away and without console
access, it might be helpful to have network interfaces working.
so do you have direct suggestion(s) on how to hack the system (while the
32-bit kernel is running) so that i can boot the 64-bit kernel and get
the 64-bit world up?
Do you have a spare partition? Probably use the swap partition temporarily.
Install the 64 bits stuff into it. Boot from it and than install the 64
bits stuff over the (now unused) 32 bits stuff and reboot into that. If
something fails you can always go back to a bootable system.
NB: disclaimer: I have never done this.
Ronald.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
