From 7b18c00afde6085a1da19c9a70fd1a714ff7fb92 Mon Sep 17 00:00:00 2001
From: Deepak Khatri <lorforlinux@beagleboard.org>
Date: Tue, 8 Oct 2024 01:12:29 +0530
Subject: [PATCH] Update code-block directive lexers
reference: https://pygments.org/docs/lexers/#module-pygments.lexers.diff
---
books/beaglebone-cookbook/05tips/tips.rst | 86 +++++++++++------------
1 file changed, 43 insertions(+), 43 deletions(-)
diff --git a/books/beaglebone-cookbook/05tips/tips.rst b/books/beaglebone-cookbook/05tips/tips.rst
index 97f282b6..8da817b5 100644
--- a/books/beaglebone-cookbook/05tips/tips.rst
+++ b/books/beaglebone-cookbook/05tips/tips.rst
@@ -153,7 +153,7 @@ Solution
However, the Bone has Secure Shell (SSH) enabled right out of the box, so you can easily
connect by using the following command to log in as user *debian*, (note the *$* at the end of the prompt):
-.. code-block:: bash
+.. code-block:: shell-session
host$ ssh debian@192.168.7.2
Warning: Permanently added '192.168.7.2' (ED25519) to the list of known hosts.
@@ -180,7 +180,7 @@ Default password
*debian* has the default password *temppwd*. It's best to change the password:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ password
Changing password for debian.
@@ -203,7 +203,7 @@ Solution
The contents of the files `/etc/motd`, `/etc/issue` and `/etc/issue.net` are displayed
everytime you long it. You can prevent them from being displayed by moving them elsewhere.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo mv /etc/motd /etc/motd.orig
bone$ sudo mv /etc/issue /etc/issue.orig
@@ -234,7 +234,7 @@ shows a way that works even if you don't have a network working over USB, but it
First, check to ensure that the serial port is there. On the host computer, run the following command:
-.. code-block:: bash
+.. code-block:: shell-session
host$ ls -ls /dev/ttyACM0
0 crw-rw---- 1 root dialout 166, 0 Jun 19 11:47 /dev/ttyACM0
@@ -244,14 +244,14 @@ First, check to ensure that the serial port is there. On the host computer, run
The letters *crw-rw----* show that you can't access it as a normal user. However, you can
access it if you are part of *dialout* group. See if you are in the *dialout* group:
-.. code-block:: bash
+.. code-block:: shell-session
host$ groups
yoder adm tty uucp dialout cdrom sudo dip plugdev lpadmin sambashare
Looks like I'm already in the group, but if you aren't, just add yourself to the group:
-.. code-block:: bash
+.. code-block:: shell-session
host$ sudo adduser $USER dialout
@@ -259,7 +259,7 @@ Looks like I'm already in the group, but if you aren't, just add yourself to the
You have to run *adduser* only once. Your host computer will remember the next
time you boot up. Now, install and run the *screen* command:
-.. code-block:: bash
+.. code-block:: shell-session
host$ sudo apt install screen
host$ screen /dev/ttyACM0 115200
@@ -380,7 +380,7 @@ It's often connected to the black wire.
Now, run the following commands on your host computer:
-.. code-block:: bash
+.. code-block:: shell-session
host$ ls -ls /dev/ttyUSB0
0 crw-rw---- 1 root dialout 188, 0 Jun 19 12:43 /dev/ttyUSB0
@@ -413,7 +413,7 @@ Solution
Log in to your Bone and enter the following command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ cat /etc/dogtag
BeagleBoard.org Debian Bullseye IoT Image 2023-06-03
@@ -438,7 +438,7 @@ Install and run a Virtual Network Computing (VNC) server:
.. todo
Check this with desktop installed
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt update
bone$ sudo apt install tightvncserver
@@ -512,7 +512,7 @@ Click Connect to start graphical access to your Bone, as shown in :ref:`tips_vnc
.. todo
This isn't working as of 8-June-2023
-.. code-block:: bash
+.. code-block:: shell-session
bone$ bone$ sudo apt install bbb.io-xfce4-desktop
bone$ sdo cp /etc/bbb.io/templates/fbdev.xorg.conf /etc/X11/xorg.conf
@@ -624,7 +624,7 @@ Solution
The Bone comes with a number of editors. The simplest to learn is *nano*.
Just enter the following command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ nano file
@@ -681,7 +681,7 @@ it will automatically assign an IP address to the Bone.
To find the IP address, open a terminal window and run the *ip* command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
@@ -787,7 +787,7 @@ First, plug in the WiFi adapter and the 5 V external power supply and reboot.
Then run *lsusb* to ensure that your Bone found the adapter:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ lsusb
Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n
@@ -807,7 +807,7 @@ Then run *lsusb* to ensure that your Bone found the adapter:
Next, run *networkctl* to find your adapter's name. Mine is
called *wlan0*, but you might see other names, such as *ra0*.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
@@ -825,7 +825,7 @@ called *wlan0*, but you might see other names, such as *ra0*.
If no name appears, try *ip a*:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ ip a
...
@@ -848,7 +848,7 @@ If no name appears, try *ip a*:
Next edit the configuration file */etc/wpa_supplicant/wpa_supplicant-wlan0.conf*.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo nano /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
@@ -869,7 +869,7 @@ In the file you'll see:
Change the *ssid* and *psk* entries for your network. Save your file, then run:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo systemctl restart systemd-networkd
bone$ ip a
@@ -927,7 +927,7 @@ file called ``ipMasquerade.sh`` on your host computer.
Then, on your host, run the following commands:
-.. code-block:: bash
+.. code-block:: shell-session
host$ chmod +x ipMasquerade.sh
host$ ./ipMasquerade.sh eth0
@@ -950,7 +950,7 @@ in :ref:`tips_setDNS` to ``setDNS.sh`` on your host computer.
Then, on your host, run the following commands:
-.. code-block:: bash
+.. code-block:: shell-session
host$ chmod +x setDNS.sh
host$ ./setDNS.sh
@@ -979,7 +979,7 @@ Web servers typically listen to port *80*. First, look up the IP address of your
.. todo::
switch to ip address
-.. code-block:: bash
+.. code-block:: shell-session
host$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
@@ -1006,7 +1006,7 @@ Then run the following, using your host's IP address:
.. todo::
check this iptables, convert to ufw
-.. code-block:: bash
+.. code-block:: shell-session
host$ sudo iptables -t nat -A PREROUTING -p tcp -s 0/0 \
-d 172.31.43.210 --dport 1080 -j DNAT --to 192.168.7.2:80
@@ -1036,7 +1036,7 @@ I'll summarize the initial setup here.
First install and check the status:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt update
bone$ sudo apt install ufw
@@ -1046,7 +1046,7 @@ First install and check the status:
Now turn off everything coming in and leave on all outgoing.
Note, this won't take effect until *ufw* is enabled.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo ufw default deny incoming
bone$ sudo ufw default allow outgoing
@@ -1054,14 +1054,14 @@ Note, this won't take effect until *ufw* is enabled.
Don't enable yet, make sure *ssh* still has access
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo ufw allow 22
Just to be sure, you can install *nmap* on your host computer to see what ports are currently open.
-.. code-block:: bash
+.. code-block:: shell-session
host$ sudo apt update
host$ sudo apt install nmap
@@ -1080,7 +1080,7 @@ Just to be sure, you can install *nmap* on your host computer to see what ports
Currently there are three ports visible: 22, 80 and 3000 (visual studio code).
Now turn on the firewall and see what happens.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
@@ -1101,7 +1101,7 @@ Only port 22 (ssh) is accessible now.
The firewall will remain on, even after a reboot. Disable it now if you don't want it on.
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo ufw disable
Firewall stopped and disabled on system startup
@@ -1128,7 +1128,7 @@ Solution
The easiest way to install more software is to use **apt**:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt update
bone$ sudo apt install "name of software"
@@ -1141,7 +1141,7 @@ The second command fetches the software and installs it and all packages it depe
How do you find out what software you can install? Try running this:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ apt-cache pkgnames | sort > /tmp/list
bone$ wc /tmp/list
@@ -1157,7 +1157,7 @@ list, one page at a time. Press the space bar to go to the next page. Press **q*
Suppose that you would like to install an online dictionary (*dict*). Just run the following command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt install dict
@@ -1180,7 +1180,7 @@ Solution
*apt* has a *remove* option, so you can run the following command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt remove dict
Reading package lists... Done
@@ -1208,7 +1208,7 @@ Solution
First, make sure your Beagle has eMMC. Run ``lsblk``.
-.. code-block:: bash
+.. code-block:: shell-session
beagle:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
@@ -1222,7 +1222,7 @@ First, make sure your Beagle has eMMC. Run ``lsblk``.
If the results show ``mmcblk0`` and ``mmcblk1`` like above, you have eMMC and can do the
rest of this recipe. If your results are like below, you don't have eMMC.
-.. code-block:: bash
+.. code-block:: shell-session
beagle:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
@@ -1232,7 +1232,7 @@ rest of this recipe. If your results are like below, you don't have eMMC.
If you booted from the microSD card, run the following command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ df -h
Filesystem Size Used Avail Use% Mounted on
@@ -1261,7 +1261,7 @@ The *ls* command shows what devices are available to mount. Because *mmcblk0* is
.. todo::
update
-.. code-block:: bash
+.. code-block:: shell-session
bone$ cd /mnt
bone$ sudo mkdir onboard
@@ -1282,7 +1282,7 @@ These are the contents of the onboard flash, which can be copied to and from lik
This same process should also work if you have booted from the onboard flash. When you are done
with the onboard flash, you can unmount it by using this command:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo umount /mnt/onboard
@@ -1316,7 +1316,7 @@ things as OpenCV, the Chromium web browser, and some documentation.
Here's how you can remove these:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt remove bb-node-red-installer (171M)
bone$ sudo apt autoremove
@@ -1329,7 +1329,7 @@ Discovering big files
The *du* (disk usage) command offers a quick way to discover big files:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo du -shx /*
12M /bin
@@ -1372,7 +1372,7 @@ of things disappeared while the command was running and thus produced some error
The ``/var`` directory appears to be the biggest user of space at 1.9 GB. You can then run the
following command to see what's taking up the space in ``/var``:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo du -sh /var/*
4.0K /var/backups
@@ -1392,7 +1392,7 @@ following command to see what's taking up the space in ``/var``:
A more interactive way to explore your disk usage is by installing *ncdu* (ncurses disk usage):
-.. code-block:: bash
+.. code-block:: shell-session
bone$ sudo apt install ncdu
bone$ ncdu /
@@ -1400,7 +1400,7 @@ A more interactive way to explore your disk usage is by installing *ncdu* (ncurs
After a moment, you'll see the following:
-.. code-block:: bash
+.. code-block:: shell-session
ncdu 1.15.1 ~ Use the arrow keys to navigate, press ? for help
--- / ------------------------------------------------------------------
@@ -1472,7 +1472,7 @@ For this example P9_14 is used, which the table shows in gpio 50.
Compile and run the code:
-.. code-block:: bash
+.. code-block:: shell-session
bone$ gcc -o blinkLED blinkLED.c
bone$ ./blinkLED
--
GitLab