I'm not discouraging the use of 64 bit machines (mine is), nor VM's (I use both KVM and VBox), but, there is no replacement for actual hardware :)
Regards, Phill. On 26 July 2013 06:24, Jonathan Marsden <jmars...@fastmail.fm> wrote: > On 07/25/2013 08:05 AM, Phill Whiteside wrote: > > > it is to ensure there are no 64 bit instructions in the 32 bit version. > > To err is human, to mess things up completely requires a computer :) > > > > Whilst this may seem like over kill, it is a 100% sure fire way to > > ensure that should the unthinkable happen, it is not missed. > > So, in the multi-year history of Ubuntu, has this issue ever happened? > Can you point to a single LaunchPad bug of this kind? > > I think the chances are so low that it is not worth worrying about. By > all means do a quick check, such as: > > file $(echo $PATH|sed -e 's%:%/* %g') | grep 64-bit > > or similar, to check for 64bit binaries on an installed image... this > can be done on any 32bit installation, including one installed and > running on a 64-bit capable CPU, virtual or physical. > > But let's not discourage use of 64-bit capable hardware, or VMs on > 64-bit capable hardware, for testing ISOs. > > Jonathan > > -- https://wiki.ubuntu.com/phillw
-- Mailing list: https://launchpad.net/~lubuntu-qa Post to : lubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~lubuntu-qa More help : https://help.launchpad.net/ListHelp
