.
I think there is a need for some built-in protection in Knoppix 6.7
to prevent the ruination of LiveUSBs that have been given a task that
turns out to be catastrophic.
What I have in mind is the bad result which occurs after starting a
download that proves ultimately too large for the LiveUSB to accommodate.
This ultimately fails, but also renders the LiveUSB inoperable without
extensive repairs or re-installation.
Couldn't there be some built-in surveillance to monitor for this
condition and head it off with some timely warning or corrective action?
Training the operator and/or using a larger USB are not solutions of interest.
@ vkrishn
For example:
I now have about 400 MB unused on my LiveUSB with persistence.
If I were to initiate a 700 MB download, that would proceed
until the device was 'full' at which time I would get a
warning 'no more room on the device'.
At this point the LiveUSB is corrupted and will not reboot
after shutdown. I think some some protection against this condition
is in order.
The few work-arounds I've tried are all harder than simply
re-installing from a previously arranged clone copy of the LiveUSB.
I guess that means using the space on disk directly and not inside the persistent storage.
The reason I asked, I have few usb installation wanted to be careful.
Did you try installing Knoppix in one partition of the disk and persistent/downloads on another partition, to see if the problem still exists?
Here are two ideas:
1. One could change IceWeasel's Edit>Preferences>General>Downloads
FROM: 'Save files to {/home/knoppix/Downloads}'
TO: 'Always ask always ask me where ...'
2. If there is a 'good' answer to 'where' then one might change the
default to that, instead of 'ask me where'.
Leaving IceWeasel set to its download default is asking for trouble
for those downloading into OS media of relatively limited size.
And you cannot reboot with cheatcode "knoppix noimage"? Of course your persistent memory is damaged, but you can use your backup.At this point the LiveUSB is corrupted and will not reboot
after shutdown.
Thanks, Werner.
The 'noimage' approach is one means of RECOVERY that I've used.
What I was searching for here is a means of PREVENTION.
What with the cost of USBs coming down, there's not much
justification anymore for 2 Gb installs like I've championed up to now.
My favorite current configuration is a 16 Gb USB with 2 GB partition
and the remainder formatted ext3 with kn-recombine on it.
I can just as well shift downloads to that partition and not run
into the 'disasters' anymore.
Cheers.
Supermicro 4U 36 Bay Storage Server 2.2Ghz 16-C 128GB 1x1280W Rails TrueNAS ZFS
$725.06
CSE-118 Supermicro 1U GPU Server 2.6Ghz 28-C 128GB 2x Nvidia K40 GPU 2x1600W PSU
$580.03
Dell PowerEdge R630 8SFF 2.6Ghz 20-Core 128GB Mem 2x10G+2x1G NIC 2x750W PSU
$399.04
Supermicro 4U 4x Nvidia GPU AI Server 2.1Ghz 16-Core 192GB 2x10G SFP+ 2x2200W
$1250.00
Intel Xeon E5-2680 v4 2.4GHz 35MB 14-Core 120W LGA2011-3 SR2N7
$17.99
Intel Xeon Gold 6140 SR3AX 2.3GHz 18-Core Processor CPU
$44.99
INTEL XEON GOLD 6148 2.40 GHz SR3B6 CPU
$98.99
Intel Xeon E5-2697 v2 2.7GHz 30M 12-Core LGA2011 CPU Processor SR19H
$27.99
HP ProLiant DL380 Gen9 16SFF 2x E5-2680v4 2.4GHz =28 Cores 64GB P840 4xRJ45
$353.00
DELL PowerEdge R730 Server 2x E5-2690v3 2.6GHz =24 Cores 32GB H730 4xRJ45
$274.00