summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMateusz CzapliƄski <czapkofan@gmail.com>2018-10-24 12:02:26 +0000
committerGitHub <noreply@github.com>2018-10-24 12:02:26 +0000
commit5bb81d216865514df0f864d89edb04bb4906ebb5 (patch)
tree309961b6d5013e8a1dcc32656828ab5b9230cd12
parent3f1b9eaf227d40d13259e3fd95315c617e7c301a (diff)
readme: tweak the warning about "rm"
-rw-r--r--README.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/README.md b/README.md
index ff54d18..d74312f 100644
--- a/README.md
+++ b/README.md
@@ -38,12 +38,13 @@ 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
+ - **WARNING: Please be careful when using it! It could be dangerous.**
+ 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