> >>> Problem is that you now have a 64-bit reboot binary on a 32-bit
> >>> system, and it can't be executed. Also sometimes other bits
> freak
> >>> out even if it starts the reboot process. (We try to preserve a
> >>> 32-bit reboot binary but apparently that isn't enough).
> >>> Jim
> >
> > have you figured out how to do it remotely ?
> > please share :)
> > matheus
>
> I haven't tried yet.  Since I don't have drac or ipmi or a metered
> IP capable PDU on the firewalls I want to move to x64, I think I'll
> need to go on-site to see what happens.  Luckily, it's only about
> 15 blocks from me.  I'll think about doing this in the next week or
> two.  Once it happens, I'll share my experience on here.

One possibility: create an entire duplicate of the filesystem (at least 
/sbin, /bin, /lib) under a temporary directory, and have another terminal 
logged in and chroot'ed to that set of binaries - you should be able to 
execute them from that chroot'ed session.
An open question is whether to make the copies real copies (which 
guarantees their integrity) or hard links to the originals - which might 
make running daemons happier, but I don't know if the installer truncates 
or unlinks the old files before copying in the new ones; if truncation, 
hardlinks are useless, if unlinking, then hard links might be better. 
There's no real difference in the amount of disk space consumed, 
ultimately - you'll need 2x the space at one point or another in the 
process regardless.

This is just a theory, I haven't tested it.  Feel free to let me know how 
it works :-).

-Adam Thompson
 [email protected]



_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to