Browse Source

underline more links

Brennen 4 years ago
parent
commit
2110f9e5a1
2 changed files with 118 additions and 30 deletions
  1. 110
    29
      index.html
  2. 8
    1
      workings.css

+ 110
- 29
index.html View File

@@ -18,18 +18,13 @@
18 18
 <h1><a name=a-technical-notebook href=#a-technical-notebook>#</a> a technical notebook</h1>
19 19
 
20 20
 <p>I&rsquo;ve been working on <a href="https://p1k3.com/userland-book/">a short book</a> on the basics of the command
21
-line.  This one is something else altogether.  It&rsquo;s meant to be a long-form
22
-technical logbook or journal, capturing the outlines of problems and their
23
-solutions as I encounter them.  It&rsquo;ll probably be dry, incomplete, and
24
-sometimes wrong.</p>
25
-
26
-<p>This probably isn&rsquo;t very useful for the general reader.  I&rsquo;m compiling it
27
-because I want a record of the stuff I discover, and I hope that writing
28
-documentation will force me to do cleaner, more reproducible work.  If it
29
-becomes helpful to people with similar problems, so much the better.</p>
30
-
31
-<p>Former students of Laurel-Concord High School will likely remember the logbooks
32
-that inspired this one.  Go Bears.</p>
21
+line.  This one is something else altogether.  It&rsquo;s a long-form technical
22
+logbook or journal, capturing the outlines of problems and their solutions as I
23
+encounter them.  It is dry, incomplete, and sometimes wrong.  It is unlikely to
24
+be useful for the general reader.  I&rsquo;m compiling it because I want a record of
25
+what I learn, and I hope that writing documentation will help me do cleaner,
26
+more reproducible work.  If it helps people with similar problems along the
27
+way, so much the better.</p>
33 28
 
34 29
 <p>&mdash; bpb / <a href="https://p1k3.com">p1k3</a>
35 30
 / <a href="https://ello.co/brennen">@brennen</a>
@@ -145,10 +140,17 @@ that inspired this one.  Go Bears.</p>
145 140
 <li><a href="#Thursday-January-22-postscript-on-finding-bugs">postscript:  on finding bugs</a></li>
146 141
 </ul>
147 142
 </li>
148
-<li><a href="#conceptual-framing">conceptual framing</a>
143
+<li><a href="#Sunday-January-25-2015">Sunday, January 25, 2015</a>
144
+
145
+<ul>
146
+<li><a href="#Sunday-January-25-2015-background-colors-for-tmux">background colors for tmux</a></li>
147
+</ul>
148
+</li>
149
+<li><a href="#Tuesday-January-27">Tuesday, January 27</a>
149 150
 
150 151
 <ul>
151
-<li><a href="#conceptual-framing-namespaces-scope">namespaces / scope</a></li>
152
+<li><a href="#Tuesday-January-27-what-version-of-what-linux-distribution-is-this">what version of what linux distribution is this?</a></li>
153
+<li><a href="#Tuesday-January-27-armhf">armhf</a></li>
152 154
 </ul>
153 155
 </li>
154 156
 <li><a href="#tools-amp-toolchains-for-data-munging-amp-analysis">tools &amp; toolchains for data munging &amp; analysis</a>
@@ -1653,26 +1655,105 @@ also wrong about being wrong.</p>
1653 1655
 
1654 1656
 <article>
1655 1657
 
1656
-<h1><a name=conceptual-framing href=#conceptual-framing>#</a> conceptual framing</h1>
1658
+<h1><a name=Sunday-January-25-2015 href=#Sunday-January-25-2015>#</a> Sunday, January 25, 2015</h1>
1659
+
1660
+<h2><a name=Sunday-January-25-2015-background-colors-for-tmux href=#Sunday-January-25-2015-background-colors-for-tmux>#</a> background colors for tmux</h2>
1661
+
1662
+<p>I&rsquo;m logged into too many machines.  I make an effort to have prompt colors differ
1663
+between hosts, but tmux is the same everywhere.</p>
1664
+
1665
+<p>You can do this sort of thing:</p>
1666
+
1667
+<pre><code>brennen@exuberance 11:54:43 /home/brennen/code $  cat ~/.tmux.conf 
1668
+# Set window notifications
1669
+setw -g monitor-activity on
1670
+set -g visual-activity on
1671
+set -g status-bg blue
1672
+set -g status-fg white
1673
+</code></pre>
1674
+
1675
+<p>&hellip;where <code>status-bg</code> and <code>status-fg</code> are colors for the status bar.</p>
1676
+
1677
+<p>It seems like there may be ways to conditionalize this, but at this point I&rsquo;m
1678
+tempted to just pull some simple templating system into my <a href="https://github.com/brennen/bpb-kit">dotfile
1679
+stuff</a> and generate a subset of config files on a per-host basis.</p>
1680
+
1681
+
1682
+</article>
1683
+
1684
+
1685
+
1686
+<article>
1687
+
1688
+<h1><a name=Tuesday-January-27 href=#Tuesday-January-27>#</a> Tuesday, January 27</h1>
1689
+
1690
+
1691
+<h2><a name=Tuesday-January-27-what-version-of-what-linux-distribution-is-this href=#Tuesday-January-27-what-version-of-what-linux-distribution-is-this>#</a> what version of what linux distribution is this?</h2>
1692
+
1693
+<p>Some luck <em>may</em> be had with one or more of:</p>
1694
+
1695
+<pre><code>root@beaglebone:~# uname -a
1696
+Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux
1697
+
1698
+root@beaglebone:~# lsb_release -a
1699
+No LSB modules are available.
1700
+Distributor ID: Debian
1701
+Description:    Debian GNU/Linux 7.8 (wheezy)
1702
+Release:    7.8
1703
+Codename:   wheezy
1704
+
1705
+root@beaglebone:~# cat /etc/debian_version 
1706
+7.8
1707
+
1708
+root@beaglebone:~# cat /etc/dogtag
1709
+BeagleBoard.org BeagleBone Debian Image 2014-04-23
1710
+
1711
+root@beaglebone:~# cat /etc/os-release 
1712
+PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
1713
+NAME="Debian GNU/Linux"
1714
+VERSION_ID="7"
1715
+VERSION="7 (wheezy)"
1716
+ID=debian
1717
+ANSI_COLOR="1;31"
1718
+HOME_URL="http://www.debian.org/"
1719
+SUPPORT_URL="http://www.debian.org/support/"
1720
+BUG_REPORT_URL="http://bugs.debian.org/"
1721
+</code></pre>
1722
+
1723
+<h2><a name=Tuesday-January-27-armhf href=#Tuesday-January-27-armhf>#</a> armhf</h2>
1724
+
1725
+<p><a href="https://blogs.oracle.com/jtc/entry/is_it_armhf_or_armel">Is it armhf or armel?</a>:</p>
1726
+
1727
+<blockquote><p>During diagnosis, the question becomes, how can I determine whether my Linux
1728
+distribution is based on armel or armhf?  Turns out this is not as
1729
+straightforward as one might think.  Aside from experience and anecdotal
1730
+evidence, one possible way to ascertain whether you&rsquo;re running on armel or
1731
+armhf is to run the following obscure command:</p>
1732
+
1733
+<pre><code>$ readelf -A /proc/self/exe | grep Tag_ABI_VFP_args
1734
+</code></pre>
1735
+
1736
+<p>If the Tag_ABI_VFP_args tag is found, then you&rsquo;re running on an armhf system.
1737
+If nothing is returned, then it&rsquo;s armel.  To show you an example, here&rsquo;s what
1738
+happens on a Raspberry Pi running the Raspbian distribution:</p>
1657 1739
 
1658
-<h2><a name=conceptual-framing-namespaces-scope href=#conceptual-framing-namespaces-scope>#</a> namespaces / scope</h2>
1740
+<pre><code>pi@raspberrypi:~$ readelf -A /proc/self/exe | grep Tag_ABI_VFP_args
1741
+Tag_ABI_VFP_args: VFP registers
1742
+</code></pre>
1659 1743
 
1660
-<p>I&rsquo;ve got an aversion to hierarchy, developed out of equal parts natural
1661
-contempt for authority qua authority and learned fear of certain modes of
1662
-technical complexity.</p>
1744
+<p>This indicates an armhf distro, which in fact is what Raspbian is.  On the
1745
+original, soft-float Debian Wheezy distribution, here&rsquo;s what happens:</p>
1663 1746
 
1664
-<p>Namespaces and scope, as a recurring technical concepts / motífs, have haunted
1665
-me since I got a handle on Perl.  They&rsquo;re both a necessary fundamental
1666
-abstraction and often the location of serious confusion.</p>
1747
+<pre><code>pi@raspberrypi:~$ readelf -A /proc/self/exe | grep Tag_ABI_VFP_args
1748
+</code></pre>
1667 1749
 
1668
-<p>What it comes down to is that you have to introduce separation between systems.
1669
-I think this may even be a more fundamental principle than <em>separation of
1670
-concerns</em>, as useful as that framing often is.  Eventually, you discover that
1671
-barriers between things sometimes <em>create</em> freedom more than they limit it.</p>
1750
+<p>Nothing returned indicates that this is indeed armel.</p></blockquote>
1672 1751
 
1673
-<p>Within the system of a program, it&rsquo;s possible to undertake tasks inappropriate
1674
-to the OS as a whole.  Within the system of a function it&rsquo;s possible to shape
1675
-tasks without continually reasoning about the program as a whole.</p>
1752
+<p>On a recent-ish Beaglebone Black:</p>
1753
+
1754
+<pre><code>root@beaglebone:~# readelf -A /proc/self/exe | grep Tag_ABI_VFP_args
1755
+  Tag_ABI_VFP_args: VFP registers
1756
+</code></pre>
1676 1757
 
1677 1758
 
1678 1759
 </article>

+ 8
- 1
workings.css View File

@@ -20,6 +20,13 @@ body {
20 20
   padding: 0;
21 21
 }
22 22
 
23
+.contents a {
24
+  text-decoration: none;
25
+}
26
+.contents a:hover {
27
+  text-decoration: underline;
28
+}
29
+
23 30
 ul li {
24 31
   list-style: square;
25 32
 }
@@ -90,7 +97,7 @@ h2 {
90 97
 
91 98
 a {
92 99
   font-style: none;
93
-  text-decoration: none;
100
+  text-decoration: underline;
94 101
 }
95 102
 
96 103
 pre {

Loading…
Cancel
Save