summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMateusz CzapliƄski <czapkofan@gmail.com>2018-10-24 13:49:33 +0200
committerGitHub <noreply@github.com>2018-10-24 13:49:33 +0200
commit3f1b9eaf227d40d13259e3fd95315c617e7c301a (patch)
tree28cd85d36ba35b7a1d1577efb7024ba30a55c269
parent3d71804b9a79b2db3f63eb3ffb0f2e683b4bca2e (diff)
raedme: add a warning about "rm"
-rw-r--r--README.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/README.md b/README.md
index 749ae69..ff54d18 100644
--- a/README.md
+++ b/README.md
@@ -38,6 +38,15 @@ then:
Wireless interface Centrino Advanced-N 6235
Ethernet interface RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
+ - **WARNING: Please think when using it!** In particular, writing "rm" or "dd"
+ into it could be like running around with a chainsaw. But you'd be careful
+ writing "rm" anywhere in Linux anyway, no? Also, why would you want to
+ pipe something into "rm"? Other than that, I don't really have good ideas
+ how to protect against cases like this. And in the other, non-dangerous
+ cases, I find the tool immensely useful. If you have some ideas how to
+ try to protect, [please share!](https://github.com/akavel/up/issues)
+ That said, a tool wouldn't be really Unixy if you couldn't hurt yourself
+ with it, right? ;P
- when you are satisfied with the result, you can **press *Ctrl-X* to exit**
the Ultimate Plumber, and the command you built will be **written into
`up1.sh` file** in the current working directory (or, if it already existed,