diff options
author | Eric Hameleers <alien@slackware.com> | 2016-06-15 10:44:06 +0200 |
---|---|---|
committer | Eric Hameleers <alien@slackware.com> | 2016-06-15 10:44:06 +0200 |
commit | a4a87869b08723a3d784bec866e53939d9579d1d (patch) | |
tree | a2429341b24b202fafcc8341f4b259d5a470dd77 /syslinux/f5.txt | |
parent | ee32cb1ffb96484dd23ade86ac45c12aa8833bbb (diff) | |
download | liveslak-a4a87869b08723a3d784bec866e53939d9579d1d.tar.gz liveslak-a4a87869b08723a3d784bec866e53939d9579d1d.tar.xz |
liveinit: use boot parameter "nop=wipe" to erase existing persistent data.
Sometimes your Slackware Live develops issues because the persistent data
storage is conflicting with new packages or data which you added to the
Live OS. This can be fixed by erasing persistent data, thereby reverting
the Live OS to its initial state - i.e. when the USB stick was booted
for the first time.
For this purpose the functionality of the existing "nop" boot parameter
was extended to allow the '=' and specifying a value of 'wipe'.
Note that the persistent data will be wiped before the Live OS boots, and
it does not matter if you are using a persistence directory or a container
file for storing persistent data.
This wipe includes all your persistent personal data in /home/
unless you have moved your /home into a container file on the USB stick.
Diffstat (limited to 'syslinux/f5.txt')
0 files changed, 0 insertions, 0 deletions