=== Lcawte is now known as Lcawte|Away [05:58] hi; [05:58] morning;] === Lcawte is now known as Lcawte|Away [10:20] morning boys and girls. [11:44] is there any point in running shred on ssd's? [17:13] Myrtti: it would probably either be straight no-op or lessen the lifespan a teeny bit over just removing the file and using trim [17:14] either way it wouldn’t actually “shred” a file [17:15] we ended up using hdparms secure clear whatever thing [17:18] I think that just forces trim commands to be atomic rather than queued [17:18] IANAL tho :-p [17:18] queued/batched [17:20] secure clear is the only way I'd trust for actually wiping [17:20] I think trim on it’s own just tells the drive to remove the data during a maintenance cycle that it schedules internally [17:20] or more that it's available if it needs to reuse it later sometime [17:21] whereas I think secure clear makes the drive actually do the job immediately [17:22] and again, IANAL [17:25] aah, secure erase kills the entire drive rather than just bits [17:25] https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase === svea_ is now known as \s === \s is now known as \sv [18:14] i thought the way ssd's worked there was no absolute guaranteed way to securely erase a file as wear balancing might write the overwritten variant in a different location on the drive? [18:17] Yes, that was my understanding also [18:18] your only real way to do it was to bung in it woodchipper fargo style... :-) [18:19] Or make sure you never put unencrypted data on it [18:20] Question : does anyone have a reliable recipe for getting 4oD and Demand5 to work on Wily? === \sv is now known as sve [18:21] * penguin42 has never managed Demand5 === sve is now known as sv === sv is now known as Guest35318 === Guest35318 is now known as \sv [18:55] woo, so I've unknowingly been doing right on my laptop just out of the old Nokia subcontractor habit, while husband did it wrong [18:55] whaddaya know [18:56] :) === Lcawte|Away is now known as Lcawte === Lcawte is now known as Lcawte|Away