.
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.
IBM CS821 20-Core 2.827GHz 128Gb 1.92Tb SSD 1U Linux Server - 8005-12N Power 8
$479.96
Red Hat Enterprise Linux 5 Server - New and Sealed
$19.99
Red Hat Enterprise Linux 5 Server RHF032US-R1 NEW Sealed
$59.95
IBM E850 Power8 2x 12C 3.02GHz 512Gb 1.8Tb SAS 10GbE 16Gb Linux Server 8408-E8E
$799.96
Asus ESC4000 G3 Barebones 0GB HDD Linux
$200.00
1U BareMetal pfsense opnsense Router Firewall DNS Server 6x 10GB Ethernet Ports
$149.00
IBM Power 9 S922 8-Core 3.4-3.9Ghz 128Gb DDR4 2U Linux Server - 9009-22a
$3439.96
IBM 8247-21L S812L 10-core 3.42 GHz 128GB 2x 300gb 12x SFF Power8 Linux Server
$649.00
IBM System X 3250 M5 Single Xeon Quad Core E3-1220 v3 @3.1GHz,8GB RAM,Linux SUSE
$199.87
POGO Linux WEBWARE 1150 Rack-Mount Server Pentium 4 2.8GHz 512MB - No Drives
$179.99