<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alexander Sack</title>
    <description>The latest articles on DEV Community by Alexander Sack (@asacasa).</description>
    <link>https://dev.to/asacasa</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F417483%2F2bf2057a-b999-4beb-aae8-fd8f7b72a331.png</url>
      <title>DEV Community: Alexander Sack</title>
      <link>https://dev.to/asacasa</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/asacasa"/>
    <language>en</language>
    <item>
      <title>plymouth.splash kernel cmdline tweaks discovered</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Sat, 16 Jul 2022 21:49:00 +0000</pubDate>
      <link>https://dev.to/asacasa/plymouthsplash-kernel-cmdline-tweaks-discovered-169f</link>
      <guid>https://dev.to/asacasa/plymouthsplash-kernel-cmdline-tweaks-discovered-169f</guid>
      <description>&lt;p&gt;Was just browsing through plymouth code and found the plymouth.splash= magic switch to select a plymouth theme.... &lt;/p&gt;

&lt;p&gt;&lt;a href="https://gitlab.freedesktop.org/plymouth/plymouth/-/blob/main/src/main.c#L376"&gt;https://gitlab.freedesktop.org/plymouth/plymouth/-/blob/main/src/main.c#L376&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So in theory i can pass in &lt;code&gt;"plymouth.splash=solar"&lt;/code&gt; and see a change of behaviour .... I will keep you posted how things work out...&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Howto setup qemu-risv64-static magic for binfmt_misc on Ubuntu 20.04 Focal</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Mon, 20 Dec 2021 11:38:16 +0000</pubDate>
      <link>https://dev.to/asacasa/howto-setup-qemu-risv64-static-magic-for-binfmtmisc-on-ubuntu-2004-focal-2jp6</link>
      <guid>https://dev.to/asacasa/howto-setup-qemu-risv64-static-magic-for-binfmtmisc-on-ubuntu-2004-focal-2jp6</guid>
      <description>&lt;p&gt;Today, I tried to chroot into my beagle-v chroot experiment and realized that Ubuntu has not setup the needed binfmt_misc magic to run my RISC-V 64-bit Binaries without troubles... did some googling and digging in scripts and succeeded with this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;echo ':qemu-riscv64:M::\x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xf3\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-riscv64-static:CF
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now that it works so nice, I also added it to my /etc/binfmt.d directory so that it would automatically work after next reboot too. Haven't tested yet, will do so on next reboot (which might be many weeks away, so feel free to let me know if this does not work or what ...&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;echo ':qemu-riscv64:M::\x7f\x45\x4c\x46\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xf3\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-riscv64-static:CF &amp;gt; /etc/binfmt.d/qemu-riscv64-static.conf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Have fun!&lt;/p&gt;

</description>
      <category>howto</category>
      <category>binfmt</category>
      <category>riscv</category>
      <category>ubuntu</category>
    </item>
    <item>
      <title>REMEMBER: gitlab ci runner &amp; pipefail == ouch</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Sat, 18 Dec 2021 01:02:10 +0000</pubDate>
      <link>https://dev.to/asacasa/remember-gitlab-ci-runner-pipefail-36e</link>
      <guid>https://dev.to/asacasa/remember-gitlab-ci-runner-pipefail-36e</guid>
      <description>&lt;p&gt;Any odd failures that make no sense in gitlab-ci.yaml scripts? Maybe those are using pipes? Gotcha.&lt;/p&gt;

&lt;p&gt;Gitlab has by default the pretty 'anal' pipefail bash mode fail, which you usually dont see even if you usually use "set -e" ...&lt;/p&gt;

&lt;p&gt;So for instance we wanted to truncate certain files in CI to a certain bytesize and use this script pattern:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt; - cat /path/to/largefile | head -c 131200 &amp;gt; /path/to/truncfile
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now interestingly enough we always had this command failing our CI scripts if the largefile became substantially larger than the head cut off.&lt;/p&gt;

&lt;p&gt;Turned out that cat indeed will fail as its downstream process exits before its done &lt;code&gt;catting&lt;/code&gt; the full largefile.&lt;/p&gt;

&lt;p&gt;Try it yourself:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ $ dd if=/dev/random of=/tmp/largefile bs=1M count=3
3+0 records in
3+0 records out
3145728 bytes (3,1 MB, 3,0 MiB) copied, 0,0467213 s, 67,3 MB/s

# here how it works nicely, with return code 0
$ cat /tmp/largefile | head 1024 &amp;gt; /tmp/truncfile
$ echo $?
0

# ... now set pipefail mode it fails ...
$ set -o pipefail
$ cat /tmp/largefile | head -c 1024 &amp;gt; /tmp/smallfile
$ echo $?
141
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>git</category>
      <category>bash</category>
      <category>pipefail</category>
      <category>gitlabci</category>
    </item>
    <item>
      <title>Ubuntu Focal 20.04 default scaling governor "powersave"</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Wed, 28 Jul 2021 16:13:01 +0000</pubDate>
      <link>https://dev.to/asacasa/ubuntu-focal-20-04-default-scaling-governor-powersave-1fp9</link>
      <guid>https://dev.to/asacasa/ubuntu-focal-20-04-default-scaling-governor-powersave-1fp9</guid>
      <description>&lt;p&gt;Just recently upgrade to Ubuntu 20.04 and was so far quite happy with a reasonable regression free experience.&lt;/p&gt;

&lt;p&gt;But then - as inevitable as it might be - I ended up going for the real stuff: building full system from source.&lt;/p&gt;

&lt;p&gt;This felt awkwardly slow ... and then i found that my CPU was running under powersave governor... i fixed this by explicitly going for performance ....&lt;/p&gt;

&lt;p&gt;For that I did:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/etc/default/cpufrequtils:GOVERNOR="performance"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Any better ideas on how to get back "ondemand" type of behaviour?&lt;/p&gt;

</description>
      <category>ubuntu</category>
      <category>powersave</category>
    </item>
    <item>
      <title>Adding a docker container to Pantavisor Linux</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Fri, 09 Jul 2021 10:16:43 +0000</pubDate>
      <link>https://dev.to/asacasa/adding-a-docker-container-to-pantavisor-linux-4i7e</link>
      <guid>https://dev.to/asacasa/adding-a-docker-container-to-pantavisor-linux-4i7e</guid>
      <description>&lt;p&gt;Adding a Pantavisor Linux system, middleware or app container from docker is done using our &lt;code&gt;pvr&lt;/code&gt; middleware tool.&lt;/p&gt;

&lt;p&gt;If you are using Pantavisor Linux with our PVBox frontend you can simply use the pvboxctl "install" command to get this done:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--BFMmgpyw--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/etrm5qt2ynry1x5fa52w.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--BFMmgpyw--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/etrm5qt2ynry1x5fa52w.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Next you select "Add from docker"&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--ttbo5zKH--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9wqt0cw3nb6lsz15sd0h.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--ttbo5zKH--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9wqt0cw3nb6lsz15sd0h.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And choose a name:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--OCEDQtcm--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vxkjaeugy1sf2bs5qq2d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--OCEDQtcm--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vxkjaeugy1sf2bs5qq2d.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And finally type the "Docker Source" ref from your preferred docker registry:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--JZZIC5tm--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ej5m543mtajlrintjlqm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--JZZIC5tm--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ej5m543mtajlrintjlqm.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And let pvr do the the rest:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--dYDcrjVR--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7zj9808tqtg798inbg5f.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--dYDcrjVR--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7zj9808tqtg798inbg5f.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Once finished you will have a chance to do some final edits to you app and commit it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;===============================
Pantabox Interactive Edit Shell
===============================

We have provisioned the following files
for the parts you have selected to edit:


You can now edit part \'mynewapp\' and change
them to your liking.

Remember to pvr commit any changes you might
want to apply to your system.

When done, you can:
1. apply committed changes: exit 0 (or Ctrl-D)
2. discard your changes: exit 1

For help visit: https://pantavisor.io

pvctlbox::mynewapp#

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Often you can just use the container using the default configuration pantavisor linux generated for you.&lt;/p&gt;

&lt;p&gt;Once happy you would run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;pvr add .
pvr commit
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and exit the interactive shell (e.g. press ctrl-D) to apply you changes and instruct pantavisor to run the new, modified system that includes your new docker container.&lt;/p&gt;

</description>
      <category>pantavisor</category>
      <category>linux</category>
      <category>docker</category>
    </item>
    <item>
      <title>HowTo: Recovery Mode for NVIDIA Jetson NANO Developer Kit</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Thu, 08 Jul 2021 13:36:11 +0000</pubDate>
      <link>https://dev.to/asacasa/howto-recovery-mode-for-nvidia-jetson-nano-developer-kit-ceo</link>
      <guid>https://dev.to/asacasa/howto-recovery-mode-for-nvidia-jetson-nano-developer-kit-ceo</guid>
      <description>&lt;p&gt;Its easy, but hard to find online, hence here for myself:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Connect Pins: &lt;em&gt;GND &amp;lt;-&amp;gt; FC REC&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;Power On&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Observe how your host can see the device connected via its USB gadget as below in dmesg:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;

[85283.237504] usb 1-6.2: new high-speed USB device number 84 using xhci_hcd
[85283.366258] usb 1-6.2: New USB device found, idVendor=0955, idProduct=7f21, bcdDevice= 1.02
[85283.366279] usb 1-6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[85283.366288] usb 1-6.2: Product: APX
[85283.366294] usb 1-6.2: Manufacturer: NVIDIA Corp.


&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Here the jumper cable and how I connected it for Recovery Mode (check the blue one):&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fz4c25j5vix74zzjz6iht.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fz4c25j5vix74zzjz6iht.png" alt="image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Best wishes!&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Howto fix a "MISSING TORADEX CONFIG BLOCK"</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Tue, 29 Sep 2020 11:48:50 +0000</pubDate>
      <link>https://dev.to/asacasa/fix-broken-configblock-for-your-toradex-colibri-module-ihl</link>
      <guid>https://dev.to/asacasa/fix-broken-configblock-for-your-toradex-colibri-module-ihl</guid>
      <description>&lt;p&gt;Yes, I bricked my Tora board... not sure how, but at some point when trying to run tezi it started to complain about&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   MISSING TORADEX CONFIG BLOCK
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Unfortunately, Toradex documentation is not very clear and forum/stackoverflow questions are not giving a clear answer either.&lt;/p&gt;

&lt;p&gt;Hence after some poking here how I resolved this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Go to Uboot Prompt&lt;/li&gt;
&lt;li&gt;run &lt;code&gt;cfgblock create&lt;/code&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Fill in the fields that you are asked to fill in. The info you can find on the label you will find on your module.&lt;/p&gt;

&lt;p&gt;Afterwards all worked fine again for me!&lt;/p&gt;

&lt;p&gt;Have fun!&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>toradex</category>
      <category>unbricking</category>
    </item>
    <item>
      <title>Banana Pi R64 + MTK 7615</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Mon, 07 Sep 2020 16:40:56 +0000</pubDate>
      <link>https://dev.to/asacasa/banana-pi-r64-mtk-7615-411</link>
      <guid>https://dev.to/asacasa/banana-pi-r64-mtk-7615-411</guid>
      <description>&lt;p&gt;With Banana Pi R64 another real beauty came on our plate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--_gP9I-aF--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/pag7zpi3vdhhd391j5x2.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--_gP9I-aF--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/pag7zpi3vdhhd391j5x2.jpg" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Can't wait to see this one in action ...&lt;/p&gt;

</description>
      <category>bananapi</category>
      <category>pantavisor</category>
    </item>
    <item>
      <title>A Tora Tower (TT)</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Thu, 03 Sep 2020 09:45:16 +0000</pubDate>
      <link>https://dev.to/asacasa/a-tora-tower-tt-3an1</link>
      <guid>https://dev.to/asacasa/a-tora-tower-tt-3an1</guid>
      <description>&lt;p&gt;My Toradex Tower is almost complete... I have now everything colibri from imx6ull to imx8 bleeding edge.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--__O1LAX1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/n5x1ndog0ibxjf7ez3my.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--__O1LAX1--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/n5x1ndog0ibxjf7ez3my.jpg" alt="My Toradex Colibri Tower"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A real beauty? WDYT?&lt;/p&gt;

</description>
      <category>toradex</category>
      <category>colibri</category>
    </item>
    <item>
      <title>alpinelinux for armel and mips anyone?</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Thu, 27 Aug 2020 16:24:21 +0000</pubDate>
      <link>https://dev.to/asacasa/alpine-for-armel-and-mips-anybody-else-1p51</link>
      <guid>https://dev.to/asacasa/alpine-for-armel-and-mips-anybody-else-1p51</guid>
      <description>&lt;p&gt;We love alpine a lot: it's lean, it's nice, apk does its job very well and is lightweight and lightning fast to use even on low spec systems....&lt;/p&gt;

&lt;p&gt;Unfortunately, we have devices that would benefit from these alpinelinux properties in the router and CPE segment that currently cannot benefit from it's awesomeness :(.&lt;/p&gt;

&lt;p&gt;Hence, I am looking for interested folks that would be keen to help bootstrapping and maintaining an unofficial ports repo for armel and mips (and maybe more?) architectures.&lt;/p&gt;

&lt;p&gt;If you like the idea and want to help ping me and we can see how we can work together.&lt;/p&gt;

</description>
      <category>help</category>
      <category>alpinelinux</category>
      <category>armel</category>
      <category>mips</category>
    </item>
    <item>
      <title>libsctp-dev with sctp.h on alpine ... where is it?</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Fri, 21 Aug 2020 11:17:24 +0000</pubDate>
      <link>https://dev.to/asacasa/libsctp-dev-with-sctp-h-on-alpine-where-is-it-591h</link>
      <guid>https://dev.to/asacasa/libsctp-dev-with-sctp-h-on-alpine-where-is-it-591h</guid>
      <description>&lt;p&gt;Took me more than 10 seconds to find on google, hence this note to myself thingy...&lt;/p&gt;

&lt;p&gt;If you need &lt;code&gt;libsctp-dev&lt;/code&gt; to build some stuff on debian distros, you probably want &lt;code&gt;lksctp-tools-dev&lt;/code&gt; package on alpine ...&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;apk info -L lksctp-tools-dev
lksctp-tools-dev-1.0.18-r1 contains:
usr/include/netinet/sctp.h
usr/lib/libsctp.so
usr/lib/pkgconfig/libsctp.pc
usr/share/lksctp-tools/checksctp.c
usr/share/lksctp-tools/sctp_bind.c
usr/share/lksctp-tools/sctp_darn.c
usr/share/lksctp-tools/sctp_darn.h
usr/share/lksctp-tools/sctp_load_libs.c
usr/share/lksctp-tools/sctp_socket.c
usr/share/lksctp-tools/sctp_socket.h
usr/share/lksctp-tools/sctp_sockopt.c
usr/share/lksctp-tools/sctp_status.c
usr/share/lksctp-tools/sctp_test.c
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



</description>
      <category>alpine</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Branding your Toradex TEZI install experience</title>
      <dc:creator>Alexander Sack</dc:creator>
      <pubDate>Fri, 14 Aug 2020 10:53:58 +0000</pubDate>
      <link>https://dev.to/asacasa/branding-your-toradex-tezi-install-experience-4kpd</link>
      <guid>https://dev.to/asacasa/branding-your-toradex-tezi-install-experience-4kpd</guid>
      <description>&lt;p&gt;Once you have managed to produce a nice TEZI installer image, you will have the option to do some branding:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;logo&lt;/strong&gt;: a 32x32 log shown next to your image entry in the TEZI installer view&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;marketing.tar&lt;/strong&gt;: in this tarball you find folder called &lt;code&gt;slides_vga&lt;/code&gt;. Here you can place your slideshow as a sequence of png files, e.g. A.png, B.png, ...&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;image.json&lt;/strong&gt;: this one has description and name and other fields that TEZI installer will surface in human readable areas (aka brand)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Remember the png's in marketing.tar are not getting auto scaled by TEZI installer; instead you have to ensure they are sized 640x400 pixel. I used the following command on linux to do that:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# this will replace A.png with the resized version
convert slides_vga/A.png -resize 640x400\&amp;gt; slides_vga/A.png
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;Happy Branding!&lt;/p&gt;

</description>
      <category>toradex</category>
      <category>linux</category>
      <category>tutorial</category>
      <category>tezi</category>
    </item>
  </channel>
</rss>
