Adding thunderbolt devices in Fedora server 30

I recently purchased a thunderbolt 3 to 10GbE adapter ( QNA-T310G1S ) for my homelab NUC ( NUC7i5BNH ) running Fedora server 30. The network interface was not showing up when I connected the adapter. Some googling later and I figured out what I was not doing. Thunderbolt devices need to be authorized and added to the thunderbolt device manager before they can be used. This requirement can be changed in the BIOS if desired....

<span title='2019-06-29 21:04:52 +0000 UTC'>Published on 2019-06-29</span>&nbsp;·&nbsp;<span title='2024-04-28 12:04:12 -0500 -0500'>Updated on 2024-04-28</span>&nbsp;·&nbsp;2 min&nbsp;·&nbsp;Danesh Manoharan

Error in option spec: “long|!”

Installed mytop on a CentOS 6.2 box and ran into a bug. The fix was simple. Comment out the problem line in the perl file. [root@dbserver local]# mytop Error in option spec: "long|!" [root@dbserver local]# which mytop /usr/bin/mytop [root@dbserver local]# vi /usr/bin/mytop From "long|!" => \$config{long_nums}, To # "long|!" => \$config{long_nums},

<span title='2019-06-27 00:09:28 +0000 UTC'>Published on 2019-06-27</span>&nbsp;·&nbsp;<span title='2024-04-28 12:04:12 -0500 -0500'>Updated on 2024-04-28</span>&nbsp;·&nbsp;1 min&nbsp;·&nbsp;Danesh Manoharan

Extract .xz file

I generally just use the tar utility to extract files from a .xz archive. >_ file tsetup.1.7.7.tar.xz tsetup.1.7.7.tar.xz: XZ compressed data >_ tar -tvf tsetup.1.7.7.tar.xz drwxrwxr-x preston/preston 0 2019-06-10 05:25 Telegram/ -rwxrwxr-x preston/preston 97436648 2019-06-10 05:24 Telegram/Telegram -rwxrwxr-x preston/preston 1400643 2019-06-10 04:52 Telegram/Updater >_ tar -xvf tsetup.1.7.7.tar.xz Telegram/ Telegram/Telegram Telegram/Updater >_ ls -l Telegram/ total 96524 -rwxrwxr-x. 1 user1 user1 97436648 Jun 10 05:24 Telegram -rwxrwxr-x. 1 user1 user1 1400643 Jun 10 04:52 Updater

<span title='2019-06-10 22:20:49 +0000 UTC'>Published on 2019-06-10</span>&nbsp;·&nbsp;<span title='2024-04-28 12:04:12 -0500 -0500'>Updated on 2024-04-28</span>&nbsp;·&nbsp;1 min&nbsp;·&nbsp;Danesh Manoharan

cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied

Installed kernel 4.18 on my Ubuntu recently, since then snap packages broke with the following error. It has something to do with the AppArmor exception rule for ptrace for what I could gather. danesh@hades:$ spotify cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied The workaround for now is to upgrade your snap core to the beta channel. danesh@hades:~/kernel$ sudo snap refresh --channel=beta core

<span title='2018-08-18 19:00:48 +0000 UTC'>Published on 2018-08-18</span>&nbsp;·&nbsp;<span title='2024-04-28 12:04:12 -0500 -0500'>Updated on 2024-04-28</span>&nbsp;·&nbsp;1 min&nbsp;·&nbsp;Danesh Manoharan

N: Skipping acquire of configured file ‘contrib/binary-i386/Packages’ as repository ‘https://download.virtualbox.org/virtualbox/debian bionic InRelease’ doesn’t support architecture ‘i386’

N: Skipping acquire of configured file ‘contrib/binary-i386/Packages’ as repository ‘https://download.virtualbox.org/virtualbox/debian bionic InRelease’ doesn’t support architecture ‘i386’ There’s no 32bit support now so update the source list file to get rid of the warning. In my case, /etc/apt/sources.list.d/virtualbox.list Change deb https://download.virtualbox.org/virtualbox/debian bionic contrib to deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian bionic contrib

<span title='2018-08-15 05:07:51 +0000 UTC'>Published on 2018-08-15</span>&nbsp;·&nbsp;<span title='2024-04-28 12:04:12 -0500 -0500'>Updated on 2024-04-28</span>&nbsp;·&nbsp;1 min&nbsp;·&nbsp;Danesh Manoharan