similar to: Shredding instead of deleting

Hopefully someone here could help. I need to debug, but I don't know much about perl. I bought a cheap USB thermometer: http://www.amazon.com/dp/B002VA813U?tag=grepular02-20 And found directions for use (for Linux) here: https://grepular.com/Using_Linux_to_Monitor_Room_Temperature_Remotely_and_Cheaply On a CentOS 6 machine, I have connected the USB device (it shows here as

On Wed, 31 May 2017, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the > RAID has 12 drives, for a total RAID size of 9.1TB, I think. I > started shred /dev/sda the Friday before last... and it's still > running. Is this reasonable for it to be taking this long...? Unless you specified non-default options, shred overwrites each

On 5/31/2017 8:04 AM, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the RAID has > 12 drives, for a total RAID size of 9.1TB, I think. I started shred > /dev/sda the Friday before last... and it's still running. Is this > reasonable for it to be taking this long...? not at all surprising, as that raid sounds like its built with

On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: > If I had realized it would run this long, I would have used DBAN.... For > single drives, I do, and choose DoD 5220.22-M (seven passes), which is > *way* overkill these days... but I sign my name to a certificate that gets > stuck on the outside of the server, meaning I, personally, am responsible > for the sanitization of the

On 5/31/2017 12:46 PM, m.roth at 5-cent.us wrote: > Not dealing with "secret", dealing with HIPAA and PII data. And*sigh* > Homeland Security Theater dictates.... We run all used disks through a shredder before surplusing any systems, and we are just a manufacturing company dealing with internal corporate IT stuff. the shredder is a truck from a 'data destruction'

On 31/05/17 21:23, John R Pierce wrote: > On 5/31/2017 12:46 PM, m.roth at 5-cent.us wrote: >> Not dealing with "secret", dealing with HIPAA and PII data. And*sigh* >> Homeland Security Theater dictates.... > > We run all used disks through a shredder before surplusing any systems, > and we are just a manufacturing company dealing with internal corporate > IT

On 05/31/2017 08:04 AM, m.roth at 5-cent.us wrote: > I've got an old RAID that I attached to a box. LSI card, and the RAID has > 12 drives, for a total RAID size of 9.1TB, I think. I started shred > /dev/sda the Friday before last... and it's still running. Is this > reasonable for it to be taking this long...? Was the system booting from /dev/sda, or were you running any

John R Pierce wrote: > On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: >> If I had realized it would run this long, I would have used DBAN.... For >> single drives, I do, and choose DoD 5220.22-M (seven passes), which is >> *way* overkill these days... but I sign my name to a certificate that >> gets stuck on the outside of the server, meaning I, personally, am

John R Pierce wrote: > On 5/31/2017 8:04 AM, m.roth at 5-cent.us wrote: >> I've got an old RAID that I attached to a box. LSI card, and the RAID >> has 12 drives, for a total RAID size of 9.1TB, I think. I started shred >> /dev/sda the Friday before last... and it's still running. Is this >> reasonable for it to be taking this long...? > > not at all

I've got an old RAID that I attached to a box. LSI card, and the RAID has 12 drives, for a total RAID size of 9.1TB, I think. I started shred /dev/sda the Friday before last... and it's still running. Is this reasonable for it to be taking this long...? mark

Have tried to install R.app several times (6, in fact: versions 2.12, 13 & 14, both 32 and 64 bit versions), using packages freshly downloaded from the official project page, and failed every time, given exception reports such as the following (appended below, the 2 reports arising out of my 1st & 6th attempts). Machine & software version specifics are all contained therein. What

On 10/30/2016 07:33 AM, FrancisM wrote: > Any error in your host logs? Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu, /var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc & /var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a log file of interest Outgoing-CentOS-7-VM.log but nothing in it that tells me anything obvious.

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Hi, if we were to use shred to delete a file on a gluster volume, will the correct blocks be overwritten on the bricks? (still using Gluster 3.6.3 as have been too cautious to upgrade a mission critical live system). Cheers, Kingsley.

On 11/08/2017 11:36 PM, Kingsley Tart wrote: > Hi, > > if we were to use shred to delete a file on a gluster volume, will the > correct blocks be overwritten on the bricks? > > (still using Gluster 3.6.3 as have been too cautious to upgrade a > mission critical live system). When I strace `shred filename`, it just seems to write + fsync random values into the file based on

> Am 08.05.2018 um 21:46 schrieb Stephen John Smoogen <smooge at gmail.com>: > > On 8 May 2018 at 15:34, <m.roth at 5-cent.us> wrote: >> Anyone have any clues about how to sanitize a dead SSD? We haven't had it >> yet, but we're sure it's coming. Esp. since I'm a federal contractor, a >> dead disk gets deGaussed, but what the hell do you do

Anyone have any clues about how to sanitize a dead SSD? We haven't had it yet, but we're sure it's coming. Esp. since I'm a federal contractor, a dead disk gets deGaussed, but what the hell do you do with a SSD?

On 9 May 2018 at 07:18, Pete Biggs <pete at biggs.org.uk> wrote: > On Wed, 2018-05-09 at 13:00 +0200, Leon Fauster wrote: >> > Am 08.05.2018 um 21:46 schrieb Stephen John Smoogen <smooge at gmail.com>: >> > >> > On 8 May 2018 at 15:34, <m.roth at 5-cent.us> wrote: >> > > Anyone have any clues about how to sanitize a dead SSD? We

On Tue, 2018-05-08 at 15:46 -0400, Stephen John Smoogen wrote: > SSD disks must be shredded as the data has been written over multiple > sectors many times to 'even the writes'. This allows for even a 'dead' > disk to be disassembled with 'off-the-shelf' equipment to extract > items from the dead places. Depending on the data involved, there may > be

On 4/25/07, Michael D. Kralka <michael.kralka at kvs.com> wrote: > > I am going to regret answering this, because it is not the right place > for such questions. However... True, but thank you for the post. > I suspect you are misusing printk and the KERN_XXX prefixes (KERN_DEBUG, > KERN_ERR, KERN_INFO, etc.) defined in include/linux/kernel.h. Try > dropping the comma