.
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.
CISCO 5108 Blade Server Chassis N20-C6508
$200.00
DELL POWEREDGE M620 SERVER BLADE INTEL XEON E5-2670 @ 2.60GHZ 128GB RAM 2X 146GB
$399.00
HP ProLiant BL460c G9 (Gen9) 2x E5-2670V3 12 Core 3.1GHz No Ram or No Drives
$59.98
DELL PEM640 POWEREDGE M640 BLADE SERVER
$539.95
Dell PowerEdge M620 0F9HJC Blade Server 2*E5-2670 2.60GHz 192GB RAM 2*300GB SAS
$103.99
Dell M630 PowerEdge Blade Server
$700.00
DELL M630 BLADE SERVER x2 XEON E5-2660V3 @ 2.6GH H730 PERC HDD CADDIES 16GB FC
$50.00
Dell PowerEdge M630 Blade Server 1x Xeon E5-2630 v4 CPU / Motherboard P/N 0R10KG
$69.99
Dell PowerEdge M620 Blade Server
$39.99
Cisco UCS 5108 Blade Server Chassis Enclosure N20-C6508 4x PSU 8x Fans 2x Fabric
$139.99