ou boot from a CD install of Xenialpup.
The save is on the computers hard drive.
The hard drive partition, the save is on, is formatted NTFS.
Is all this correct?
Yes.
In /tmp, I found bootkernel.log, bootsysinit.log, and udevtrace.log which have useful stuff, I am sure, but only if you know what to look for. For instance, the bootsysinit says "No touchscreens detected", but this must be because it will be recognized as a mouse later?
The "/tmp/sfs_load" file doesn't mention any errors (now), but if there was a CD or hard disk (when saved to HD) problem, would errors show up in this log? What about errors in pupsave...2fs on HD?
There is a "/tmp/ntfsmnterr7294.txt" 0 byte file. Not clear whether there was an NTFS error or just the potential for an error, or what the number means. There are actually two NTFS partitions that are mounted during boot, but my data one is unmounted a second after the Xscreen comes up. Google implies "ntfs mount error" messaes should say more. Right now, there is no Windows available to exercise or fix the NTFS.
There is also a "/tmp/xerrs.log" with about 23,000 lines of "(ROX-Filer:6134): WARNING **: Attempt to paste empty selection!". Is this file an accumulation of all the errors since I created the new pupsave in the last week, or just this last boot of a few hours? Seems excessive. Web search was no help in explaining.
In /etc/rc.d/ I found rc.sysinit. This is where the screen messages like "echo -n "Making the filesystem usable..." >/dev/console" come from. So the answer to my question is those particular messages are not saved to a file? Would there be a way to create a log file for everything written to the screen by changing (and then unchanging after bootup is finished) the properties of /dev/console?
rc.sysinit also does the creation of fsckme.flg on the /mnt/home NTFS volume (not the linux filesystem), and a comment that it is deleted after successful shutdown. The actual call to fsck is somewhere in /initrd/init but the script is very complicated and I cannot find where the fsckme flag is used. In any case, the selected fsck program must be doing its own screen writes- to /dev/console?
Could there be a PUPMODE that pauses between operations?
Well, just had my first system hang (from Palemoon) and a power-off shutdown. Upon reboot, screen said e2fsck... recovering journal ...2 things about inodes, etc but it was all gone in a flash.
Now there is only a 0 byte file "ntfsmnterr7460.txt" instead of the other one, and xerrs.log only has 24 lines with no errors noted.
Sfs_load, again, doesn't mention anything about problems with the pupsave load.