Thank-you.
I stand corrected in reference to mount points. When running live, the device
list changes after each resume from suspend. I specified "do-nothing" under
system power options when closing lid, but system goes into suspend
nevertheless. Device UUID's remain unchanged.
With the built-in hardrive physically removed and BIOS device list specifying
"none" for it, am now running a Winchster usb device (/dev/sdb) with an ext4
partition number at (/dev/sdb7) that is manually mounted to a manually
specified subdirectory made with a simplified name under /media. I/O errors
occur and the automatically assigned swap partition to /dev/sdb6 becomes
/dev/sdc6! I will clearly run out of device letters from each resume from
suspend this way. Another, new, non-internet machine running Trisquel 6.0
live has an uptime exceeding 368 days where my usb drives remain unchanged
and active during and after many suspends.
Regarding Memtest 86+ it worked repeatedly before first installing Trisquel
6.0 on this Gateway MX4310 Windows-only home machine, after shrinking a
defragmented ntfs factory installed partition on addresses following the
FAT32 recovery partition. After nearly a hundred Kernel panics, and
occasional lockouts preventing me from even getting to grub, I could coax the
Windows system to life just to see if it still worked and existed. First with
startup errors, later with a few blue screens and now with a black text
screen complaining about a missing or corrupted Windows file! Before blaming
the hard drive, am seeking live performance consistency, without kernel
panics, that still have a tendency to occur even when leaving everything
switched on overnight...
