Hi folks, I forgot to reply to this on-list.
On 17/08/17 17:51, Geoffrey Combes wrote: > > Hello Paul, Your terminal command returned a mass of actions related > to 16.04 upgrade concluding with a statement that clearly indicates > success. I re-started and both the Upgrade and Ubuntu software apps > are working again. I then invoked an update request and received > notification of upgrades available in the usual way. I was sure that > something like this could be done via the Terminal but I lack the > knowledge to do it myself. I am grateful for your advice. Many thanks. > > You mentioned in passing 'amd64' about which I have a question that > arose when I ordered disks yesterday. I had to select either 32-bit or > 64-bit. > When it comes to image & package naming, 32-bit == i386 and 64-bit == amd64 (even though you don't need to have an AMD processor to run amd64 code). > I have always used 32-bit. I continue to do so because I expect to > reload the home directory from my external back-up disk drive after > installing from a disk.. > You should consider switching to 64-bit on your next reinstall. 32-bit will be deprecated at some point in the not-too-distant future. > Logic (?) tells me the stored data should work with either system. > True or false? > Generally-speaking, this is true. Certainly it is true for all common data formats like PDF, LibreOffice, HTML, etc. There are some applications which store their data in architecture-specific format, usually for maximum performance. RRDtool is one that comes to mind. But these are becoming less & less common. > I'll keep looking for an answer as to why the installed isos will not > boot. > Most likely a corrupt image, faulty USB stick, or something similar. These days that side of things is pretty bulletproof. Paul -- ubuntu-au mailing list ubuntu-au@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-au
