Date: Sat, 11 Feb 2012 01:58:30 -0800 From: Randy Bush <randy@psg.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: 9-stable from i386 to amd64 Message-ID: <m2zkcppu7t.wl%randy@psg.com> In-Reply-To: <20120211073527.GQ3283@deviant.kiev.zoral.com.ua> References: <m2y5sa7yt0.wl%randy@psg.com> <20120211060207.GK5775@dan.emsphone.com> <20120211073527.GQ3283@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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? randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2zkcppu7t.wl%randy>