I added all information needed to reformat 520e disks and remove FTTH.
I took the liberty to link to my guides and replaced systemrescue in my guide with ShredOS, now that there's parallel preinstalled it makes more sense.
When nwipe has completed erasing the drives and the user
hits return to exit which then creates the PDF certificates,
the PDF and log files are then either automatically transferred
to a USB stick, assuming that's where you booted ShredOS from
or the files are transferred to a network server, if the ShredOS
grub.cfg files were configured to do that.
However, say there was a network failure or somebody inadvertently
removed the USB drive, the PDF files & logs would not get saved.
Previously you would have had to manually copy the files using the
command line.
Now when you get to the stage where ShredOS asks whether you want
to reboot, shutdown or restart nwipe, if there are any PDF files
that have not been saved a new options 'a' archive to USB will
be available. This option will only show up if there are PDFs that
have not been saved. So the message will read:
r=reboot, s=shutdown, a=archive to USB, spacebar=restart nwipe
Apart from the above scenario, this feature may also prove useful
to somebody, wiping many computers while using a single USB stick.
For those that don't know, it's not necessary to keep the USB stick
plugged into the computer. Once nwipe has appeared you can pull
the USB stick out and use it to boot another computer. Returning it
to the first computer when the wipes have completed and you want to
save the PDFs to USB.
This patch also standardises the date format used in the ShredOS
logs so it matches the nwipe format.
Updated the information that shows the command line options that can be used with nwipe and therefore used with ShredOS's nwipe_options"...." string that can be placed on the kernel command line.
Merge pull request #255 from PartialVolume/Ping_server_and_wait.
Various fixes to do with tftp/ftp transfers.
Fixes#242 Pauses for upto 30 seconds before launching nwipe if ftp/tftp transfers are being used. This is because if the user specified shredos_config="..." on the kernel command line in order to retrieve the nwipe.conf and nwipe_customers.csv files from a local ftp/tftp server, the server needs to be online before nwipe is launched. On some systems/networks the ethernet hardware initialisation and then DHCP requests can be slower than nwipe launching hence why we now ping the server to makesure it's online before launching nwipe.
Lots of improvements to error detection and handling for tftp
Improvments to the "shredos_autoreboot=enable" option. When this option is placed on the kernel command line shredos will reboot upon completion of wipes. --nowait option is appled by the scipt to nwipe so nwipe doesn't wait for user interaction before exiting. If the shredos_config="..." or shredos_output="..." kernel command line options have been added by the user, autoreboot and also autoshutdown will wait after exiting nwipe if any ftp/tftp errors occurred so the user can review the transfer log and decide on a course of action if necessary.
Various fixes to do with tftp/ftp transfers.
Fixes#242 Pauses for upto 30 seconds before launching nwipe
if ftp/tftp transfers are being used. This is because if the
user specified shredos_config="..." on the kernel command line
in order to retrieve the nwipe.conf and nwipe_customers.csv
files from a local ftp/tftp server, the server needs to be
online before nwipe is launched. On some systems/networks the
ethernet hardware initialisation and then DHCP requests can be
slower than nwipe launching hence why we now ping the server
to makesure it's online before launching nwipe.
Lots of improvements to error detection and handling for tftp
Improvments to the "shredos_autoreboot=enable" option. When this
option is placed on the kernel command line shredos will reboot
upon completion of wipes. --nowait option is appled by the scipt
to nwipe so nwipe doesn't wait for user interaction before exiting.
If the shredos_config="..." or shredos_output="..." kernel command
line options have been added by the user, autoreboot and also
autoshutdown will wait after exiting nwipe if any ftp/tftp errors
occurred so the user can review the transfer log and decide on a
course of action if necessary.
1. Debug tftp transfers for restoring config files and outputing
pdfs and logs.
2. Added a ping status delay for the ftp/tftp that only proceeds
with launching nwipe if ftp/tftp servers have been configured on
the kernel command line. The delay has a 30 second timeout upon
which nwipe will launch. This fixes a problem where nwipe launches
before the ethernet hardware is active and a IP address had not
been obtained. This caused nwipe to not be able to read the
config files from the ftp/tftp server.
3. Removed 4 second countdown on restarting nwipe.
