<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dzu's Blog (Posts about tcp)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/categories/tcp.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Wed, 10 Dec 2025 16:16:35 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Transferring Files Over TCP With Bash</title><link>https://blog.lazy-evaluation.net/posts/linux/bash-tcp.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;
There are times when I have Ethernet working on an embedded GNU/Linux
board, but no tool available to actually transfer files.  Latest
example is the Yocto build for an i.MX evaluation board from NXP that
I just built.  The system lives on the SD card, so adding a package
would mean to reconnect the SD card to my development machine, copy
the file(s) and put it back into the board. And I am just too lazy for
that.  The EVK has an IP address on my local network, so there must be
an easy way to transfer a file with standard tools, right?
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/posts/linux/bash-tcp.html?pk_campaign=feed"&gt;Read more…&lt;/a&gt; (5 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>bash</category><category>commandline</category><category>kermit</category><category>nc</category><category>serial</category><category>tcp</category><guid>https://blog.lazy-evaluation.net/posts/linux/bash-tcp.html</guid><pubDate>Mon, 10 Feb 2025 16:34:23 GMT</pubDate></item></channel></rss>