cat /dev/mem | strings | grep -i llama
cat: /dev/mem: Operation not permitted
Edit: even as root11–20 of 48 posts
cat /dev/mem | strings | grep -i llama
cat: /dev/mem: Operation not permitted
Edit: even as rootWhatever happened to backups?
To help prevent this problem...
KEEP A BACKUP.
#man shred SHRED(1) User Commands SHRED(1)
NAME shred - overwrite a file to hide its contents, and optionally delete it
I especially like the -n option!
(From afar, I understand my Colonial cousins' struggle with these two words.)
(Grepping your hard drive for file fragments is suggested in the ext3 FAQ - http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html)
Excellent Linux hack. I hadn't ever heard this before.
Or, if you want to really delete a file, use #shred filename command #man shred SHRED(1) User Commands SHRED(1) NAME shred - overwrite a file to hide its contents, and optionally delete it I especially like the -n option!
CAUTION: Note that shred relies on a very important assumption: that
the file system overwrites data in place. This is the traditional way
to do things, but many modern file system designs do not satisfy this
assumption. The following are examples of file systems on which shred
is not effective, or is not guaranteed to be effective in all file sys‐
tem modes:
* log-structured or journaled file systems, such as those supplied with
AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
* file systems that write redundant data and carry on even if some
writes fail, such as RAID-based file systems
* file systems that make snapshots, such as Network Appliance's NFS
server
* file systems that cache in temporary locations, such as NFS version 3
clientsExcellent Linux hack. I hadn't ever heard this before.
It works on all systems where you have raw access to the disk. And it isn't really that fancy if you think about how it works and how file systems work.
the last part, about using an alias for rm is something that I've never thought about it and now I'm gonna use always on my servers.