summarylogtreecommitdiffstats
path: root/bitcoin-qt.install
diff options
context:
space:
mode:
Diffstat (limited to 'bitcoin-qt.install')
-rw-r--r--bitcoin-qt.install25
1 files changed, 0 insertions, 25 deletions
diff --git a/bitcoin-qt.install b/bitcoin-qt.install
index edec8b45c6a4..8f20cf484d13 100644
--- a/bitcoin-qt.install
+++ b/bitcoin-qt.install
@@ -1,36 +1,11 @@
post_install() {
update-desktop-database -q
- printf "%b\n" "$bitcoin"
}
post_upgrade() {
update-desktop-database -q
- printf "%b\n" "$bitcoin"
}
post_remove() {
update-desktop-database -q
}
-
-read -d '' bitcoin <<'EOF'
-########################################################################
-########################################################################
-## ##
-## Bitcoin Classic ##
-## ____________ ##
-## ##
-## New to 0.12, when no -rpcpassword is specified, the daemon now ##
-## uses a special 'cookie' file for authentication. This file is ##
-## generated with random content when the daemon starts, and deleted ##
-## when it exits. Its contents are used as authentication token. ##
-## Read access to this file controls who can access through RPC. By ##
-## default it is stored in the data directory but its location can ##
-## be overridden with the option -rpccookiefile. This is similar to ##
-## Tor's CookieAuthentication. ##
-## see: https://www.torproject.org/docs/tor-manual.html.en ##
-## This allows running bitcoind without having to do any manual ##
-## configuration. ##
-## ##
-########################################################################
-########################################################################
-EOF