KiwiDrop lets you transfer files between Windows and Linux over a local network. It also has an Android app for phones running Android 10 or later, with device pairing and a desktop widget for sending files. Say you’ve built an application on the Windows PC and want to send its archive to a KiwiPi. Select the paired board, drop the archive onto the kiwi widget, and accept it on the board. The repository’s screenshots show that setup with a Windows desktop and a KiwiPi 5 running Linux. KiwiDrop is still a test version. The screenshots below show desktop version 0.7.8; download the current package from the project’s releases rather than looking for that particular version. Send a file from the desktop The floating kiwi widget gives you a small drop target without keeping the main window in front of your work. Once you’ve selected a recipient, drag a file onto it to send it to that device. For a build archive or a few saved frames, that’s a useful bit of interface to have within reach. Its context menu opens the transfer list, recipients, devices, settings, and downloads folder. You can also hide the widget when you don’t need it.

Run df -h / to check free space on the filesystem containing the Linux root directory. The Avail column shows how much space remains available for ordinary users. On a KiwiPi running Ubuntu 24.04.3 LTS, you can run it in a local terminal or connect to Linux from macOS and check over SSH. If you’re about to copy files with SCP, check the destination first. An archive needs room for the download and, if you’re extracting it on the board, the extracted files too. Check free space with df df -h / Read Size, Used, Avail, and Use% together. Mounted on identifies the mountpoint, which is / for this check. The -h option gives you readable units such as M and G; you don’t have to work through a long block count to see whether another model or disk image will fit. You can also give df a directory. For example, this checks the filesystem holding your home directory, then a possible data directory: df -h “$HOME” df -h /mnt/data That second command requires an existing /mnt/data directory. And the number belongs to its containing filesystem. It doesn’t tell you how much data sits inside the folder—use du for that.

In the previous article, we covered how to transfer files from Mac to Linux with SCP. This time, the computer on your desk is a Chromebook, and the first terminal you will probably find is Crosh. Press Ctrl + Alt + T on a Chromebook and Crosh opens in a browser tab. Start with help. It prints the commands available on that Chromebook, which is more useful than copying a list written for a different ChromeOS release. The official Crosh command reference makes the same point: the available tools vary by release, channel, device policy, and Developer Mode. Crosh is a small troubleshooting console, not Bash or a Chromebook version of Windows Command Prompt. Many online lists mix standard Crosh, the Developer Mode shell, and Linux Terminal. A copied command may return unknown command simply because it does not exist on your build. Start With Your Crosh Commands List Open Crosh and run: help help_advanced The first shows common commands; the second includes less frequently used ones. ChromeOS releases, device policies, channels, and hardware can change the result, so the list on the screen wins. Tab completion works, while help battery_test shows the syntax for one command. Network Commands Worth

Open Terminal on the Mac and enter: ssh alex@192.168.1.50 Replace alex with the Linux account name and 192.168.1.50 with the address of the machine you want to reach. There is no SSH client to install on the Mac. macOS already includes OpenSSH, although Apple’s Terminal connection guide also describes a menu-based connection method. For a KiwiPi 5 Linux board, the easiest setup is to put the Mac and the board on the same local network. Ethernet removes a few variables during the first boot. Wi-Fi is fine once the board has joined the correct network. Prepare the Linux Machine Install the SSH server The Mac already has an SSH client. The Linux machine needs the server half. Debian and Ubuntu images use the openssh-server package. Some board images include it; others don’t. Run this on the Linux machine: sudo apt update sudo apt install openssh-server sudo systemctl enable –now ssh Then check the service instead of assuming the package installer started it: systemctl status ssh –no-pager Look for: Active: active (running) Other distributions may call the service sshd. That difference is worth checking before spending half an hour debugging the network. The Ubuntu OpenSSH server documentation uses ssh.service for current

chmod u+x deploy.sh is probably the command you need when a copied script returns Permission denied. It gives the file’s owner execute permission and leaves the other mode bits alone. This often happens after copying files to a Linux machine with SCP, since SCP preserves the original file mode. That’s the easy case. Before changing anything, run ls -l and check whether the problem is actually the mode, the owner, or the filesystem. Throwing 777 at all three is how a small permissions issue turns into a weird security issue. Check the File First Start with the file itself: Bashls -l deploy.sh Output-rw-r–r– 1 user user 842 Sep 10 10:20 deploy.sh Here’s the useful part. The first character says what the entry is (- means a regular file), and the next nine characters come in three groups: rw- for the owner, r– for the group, and r– for everyone else. So the owner can read and edit this file. Nobody can execute it. The letters are exactly what they look like: r is read, w is write, and x is execute. The selectors are nearly as simple. u means owner, g means group, o means other users, and a means