DBAN shouldn't nuke *itself*, however orthogonal that behavior is

[NHellFire]

Need to somehow figure out what attached device contains DBAN.
Can't just check for /dban.bzi since it could've been renamed/moved. Probably have to require a tag file is left in root.

https://sourceforge.net/p/dban/bugs/63/

[Firminator]

Shouldn't this be fixed now that you fixed 'nousb' boot option with the 20180720 release?

[Firminator]

The original changelog[1] mentioned 'nousb' is supposed to exclude USB attached devices (UFD/HDD/SSD) for all Autonuke modes. The first Autonuke menu option[2] works as designed (it's not listing and not wiping the USB Flash Drive DBAN started from). The other Autonuke options wipe my dedicated DBAN flash drive. To prevent his I suggest to add nousb/usbcore.nousb to all other Autonuke menu items or maybe split the menu into 3 submenus:
Autonuke (internal and external disks)
Autonuke (internal disks only, no USB drives)
Interactive

Reasoning here is that currently there is no Autonuke option available that wipes all drives with zeros using Defautl settings, but doesn't touch the DBAN flash drive. Instead I have to use Interactive Mode and select all drives (leaving the USB flash drive unchecked), then change the method and then F10.

[1] https://sourceforge.net/projects/dban/files/dban/dban-2.2.8/ -> "nousb" option added in autonuke mode (in auto mode USB sticks/hdds will not be erased).
[2] https://github.com/NHellFire/dban/blob/master/isoroot/i586/input/isolinux.cfg#L84 [DBAN autonuke (Automatic, Default settings, Internal disks only)]

[Firminator]

#36