rerender with pandoc

author: Akshay <[email protected]> 2020-04-16 09:10:50 +0100
committer: Akshay <[email protected]> 2020-04-16 09:10:50 +0100
commit: 2a778912251874f9b808f82e61244efcd12210aa (patch)
tree: 72cd692749c36f068fe22a32ede51a88a65bc759 /docs/posts/WPA_woes/index.html
parent: d71a288d944959057064d64ce03cad759a42ba06 (diff)
1 files changed, 36 insertions, 32 deletions
diff --git a/docs/posts/WPA_woes/index.html b/docs/posts/WPA_woes/index.html
index e329df6..f3fcfcf 100644
--- a/docs/posts/WPA_woes/index.html
+++ b/docs/posts/WPA_woes/index.html
@@ -37,48 +37,52 @@
            WPA Woes
          </h1>
          <div class="post-text">
-            <p>I finally got around to installing Void GNU&#47;Linux on my main
+            <!DOCTYPE html>
-computer. Rolling release, non-systemd, need I say more?</p>
+<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
+<head>
-<p>As with all GNU&#47;Linux distributions, wireless networks had
+  <meta charset="utf-8" />
-me in a fix. If you can see this post, it means I&#39;ve managed
+  <meta name="generator" content="pandoc" />
-to get online. It turns out, <code>wpa_supplicant</code> was detecting the
+  <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
-wrong interface by default (does it ever select the right
+  <title>WPA_woes</title>
-one?). Let us fix that:</p>
+  <style>
+    code{white-space: pre-wrap;}
-<pre><code>$ sudo rm -r &#47;var&#47;service&#47;wpa_supplicant
+    span.smallcaps{font-variant: small-caps;}
-$ sudo killall dhcpcd
+    span.underline{text-decoration: underline;}
-</code></pre>
+    div.column{display: inline-block; vertical-align: top; width: 50%;}
+    div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+    ul.task-list{list-style: none;}
+  </style>
+  <!--[if lt IE 9]>
+    <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
+  <![endif]-->
+</head>
+<body>
+<p>I finally got around to installing Void GNU/Linux on my main computer. Rolling release, non-systemd, need I say more?</p>
+<p>As with all GNU/Linux distributions, wireless networks had me in a fix. If you can see this post, it means I’ve managed to get online. It turns out, <code>wpa_supplicant</code> was detecting the wrong interface by default (does it ever select the right one?). Let us fix that:</p>
+<pre><code>$ sudo rm -r /var/service/wpa_supplicant
+$ sudo killall dhcpcd</code></pre>
 <p>What is the right interface though?</p>
 <pre><code>$ iw dev
   ...
   Interface wlp2s0
-   ...
+   ...</code></pre>
-</code></pre>
+<p>Aha! Let us run <code>wpa_supplicant</code> on that interface, as a background process:</p>
+<pre><code>$ sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
-<p>Aha! Let us run <code>wpa_supplicant</code> on that interface, as a
-background process:</p>
-<pre><code>$ sudo wpa_supplicant -B -i wlp2s0 -c &#47;etc&#47;wpa_supplicant&#47;wpa_supplicant.conf
 $ sudo dhcpcd -B wlp2s0
 $ ping google.com
-PING ...
+PING ...</code></pre>
-</code></pre>
 <p>Yay! Make those changes perpetual by enabling the service:</p>
 <pre><code>------------------------------------------------------
-# Add these to &#47;etc&#47;wpa_supplicant&#47;wpa_supplicant.conf
+# Add these to /etc/wpa_supplicant/wpa_supplicant.conf
-OPTS=&#34;-B&#34;
+OPTS=&quot;-B&quot;
-WPA_INTERFACE=&#34;wlp2s0&#34;
+WPA_INTERFACE=&quot;wlp2s0&quot;
 ------------------------------------------------------
-$ sudo ln -s &#47;etc&#47;sv&#47;wpa_supplicant &#47;var&#47;service&#47;
+$ sudo ln -s /etc/sv/wpa_supplicant /var/service/
-$ sudo ln -s &#47;etc&#47;sv&#47;dhcpcd &#47;var&#47;service&#47;
+$ sudo ln -s /etc/sv/dhcpcd /var/service/
 $ sudo sv restart wpa_supplicant
-$ sudo sv restart dhcpcd
+$ sudo sv restart dhcpcd</code></pre>
-</code></pre>
+</body>
+</html>
          </div>
author	Akshay <[email protected]>	2020-04-16 09:10:50 +0100
committer	Akshay <[email protected]>	2020-04-16 09:10:50 +0100
commit	2a778912251874f9b808f82e61244efcd12210aa (patch)
tree	72cd692749c36f068fe22a32ede51a88a65bc759 /docs/posts/WPA_woes/index.html
parent	d71a288d944959057064d64ce03cad759a42ba06 (diff)

diff --git a/docs/posts/WPA_woes/index.html b/docs/posts/WPA_woes/index.html index e329df6..f3fcfcf 100644 --- a/docs/posts/WPA_woes/index.html +++ b/docs/posts/WPA_woes/index.html
@@ -37,48 +37,52 @@
37	WPA Woes	37	WPA Woes
38	</h1>	38	</h1>
39	<div class="post-text">	39	<div class="post-text">
40	<p>I finally got around to installing Void GNU/Linux on my main	40	<!DOCTYPE html>
41	computer. Rolling release, non-systemd, need I say more?</p>	41	<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
42		42	<head>
43	<p>As with all GNU/Linux distributions, wireless networks had	43	<meta charset="utf-8" />
44	me in a fix. If you can see this post, it means I've managed	44	<meta name="generator" content="pandoc" />
45	to get online. It turns out, <code>wpa_supplicant</code> was detecting the	45	<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
46	wrong interface by default (does it ever select the right	46	<title>WPA_woes</title>
47	one?). Let us fix that:</p>	47	<style>
48		48	code{white-space: pre-wrap;}
49	<pre><code>$ sudo rm -r /var/service/wpa_supplicant	49	span.smallcaps{font-variant: small-caps;}
50	$ sudo killall dhcpcd	50	span.underline{text-decoration: underline;}
51	</code></pre>	51	div.column{display: inline-block; vertical-align: top; width: 50%;}
52		52	div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
		53	ul.task-list{list-style: none;}
		54	</style>
		55	<!--[if lt IE 9]>
		56	<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
		57	<![endif]-->
		58	</head>
		59	<body>
		60	<p>I finally got around to installing Void GNU/Linux on my main computer. Rolling release, non-systemd, need I say more?</p>
		61	<p>As with all GNU/Linux distributions, wireless networks had me in a fix. If you can see this post, it means I’ve managed to get online. It turns out, <code>wpa_supplicant</code> was detecting the wrong interface by default (does it ever select the right one?). Let us fix that:</p>
		62	<pre><code>$ sudo rm -r /var/service/wpa_supplicant
		63	$ sudo killall dhcpcd</code></pre>
53	<p>What is the right interface though?</p>	64	<p>What is the right interface though?</p>
54
55	<pre><code>$ iw dev	65	<pre><code>$ iw dev
56	...	66	...
57	Interface wlp2s0	67	Interface wlp2s0
58	...	68	...</code></pre>
59	</code></pre>	69	<p>Aha! Let us run <code>wpa_supplicant</code> on that interface, as a background process:</p>
60		70	<pre><code>$ sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
61	<p>Aha! Let us run <code>wpa_supplicant</code> on that interface, as a
62	background process:</p>
63
64	<pre><code>$ sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
65	$ sudo dhcpcd -B wlp2s0	71	$ sudo dhcpcd -B wlp2s0
66	$ ping google.com	72	$ ping google.com
67	PING ...	73	PING ...</code></pre>
68	</code></pre>
69
70	<p>Yay! Make those changes perpetual by enabling the service:</p>	74	<p>Yay! Make those changes perpetual by enabling the service:</p>
71
72	<pre><code>------------------------------------------------------	75	<pre><code>------------------------------------------------------
73	# Add these to /etc/wpa_supplicant/wpa_supplicant.conf	76	# Add these to /etc/wpa_supplicant/wpa_supplicant.conf
74	OPTS="-B"	77	OPTS="-B"
75	WPA_INTERFACE="wlp2s0"	78	WPA_INTERFACE="wlp2s0"
76	------------------------------------------------------	79	------------------------------------------------------
77	$ sudo ln -s /etc/sv/wpa_supplicant /var/service/	80	$ sudo ln -s /etc/sv/wpa_supplicant /var/service/
78	$ sudo ln -s /etc/sv/dhcpcd /var/service/	81	$ sudo ln -s /etc/sv/dhcpcd /var/service/
79	$ sudo sv restart wpa_supplicant	82	$ sudo sv restart wpa_supplicant
80	$ sudo sv restart dhcpcd	83	$ sudo sv restart dhcpcd</code></pre>
81	</code></pre>	84	</body>
		85	</html>
82		86
83	</div>	87	</div>
84		88