Separating WSL (Linux) path and Window path

I often find myself hacking the Linux kernel for fun and profit. This time I was trying out Buildroot Embedded Linux build system and the first stumbling block using WSL was the fact that Windows path containing spaces were appended to the WSL path which the Linux file system has issues with. Running make for the Buildroot gives the error below:

Your PATH contains spaces, TABs, and/or newline (\n) characters

Follow the steps below for the solution:

  1. Create a config file for WSL interop in the WSL distro you are using. sudo nano /etc/wsl.conf
  2. Copy and paste the config below in the file:
  1. Save then restart the WSL distro in the Windows shell (not the WSL distro).
wsl -d [distribution name] --shutdown
wsl -d [distribution name]
  1. Check the path to echo $PATH to ensure all is well, only the Linux path should remain.
  2. And we are done! Finally we can build our kernel without worries.

If you forget your Windows Subsystem for Linux (WSL) password, try this.

I have been using Windows Subsystem for Linux (WSL) for a while now and sometimes I create a distribution and forget the password. If you find your self in the same situation, just follow these steps:

  1. Open the Windows Shell.
  2. Type in wsl -l to get the list of WSL Distributions you have on your system.
  3. Login to the distribution using wsl -d [Distribution Name].
  4. Type in whoami to get your default user name. Note this down.
  5. Logout of the distribution, by typing exit.
  6. Log in as root: wsl -d [Distribution Name] -u root.
  7. Change the password for the user by running this passwd [User Name] and follow the instructions.
  8. If all goes well you should get a “passwd: password updated successfully” message.
  9. Logout again using exit .
  10. Now you can use the new password for your WSL Distribution default user.

Hope this was helpful to you. Thanks for reading.

System statistics reporting using Laravel

The Laravel web framework comes with a lot of powerful tools and one of them it the Task Scheduler. This allows you to create and manage all your automated – Cron Jobs – tasks within the framework. If you do not write Cron jobs often, going through documentation or memorizing the Crontab syntax and expression can be extra work (I usually use to simplify this ). Laravel uses functions such as everyTwoMinutes() which is simple to remember and implement. There is also per second scheduling which is not available by default on crontab.

First, you have to open the app/Console/Kernel.php file. Your scheduled task will be added in the schedule(Schedule $schedule) function, by calling the $schedule object. There four main types of calls you can make using the $schedule object:

  1. A closure function containing Laravel/PHP code you wish to run.
  2. A command which runs an Artisan command.
  3. A queued Job.
  4. Command line scripts which can run external scripts.

I will be running an external script (using exec ) to get my systems stats and then send them to myself every 5 minutes. To use an already setup docker environment you can clone this repo and follow the setup instructions (If you choose to use the docker environment. Run your commands in the ‘web’ container) . Copy the code block below in the schedule function:

$command = 'echo "------------------" >> out.txt &&';
        $command .= 'top -b -n 1 >> out.txt &&';
        $command .= 'echo "------------------" >> out.txt &&';
        $command .= 'cat /proc/meminfo >> out.txt &&';
        $command .= 'echo "------------------"';
            ->name('System Stats')

Then first test using php artisan schedule:test select the number associated with this task and click enter. if there are no errors, run php artisan schedule:work to start the scheduler if you are on a development environment. For production, add this to your Crontab :

* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1


  1. Ensure email sender (mailer) of choice is configured on the .env file.
  2. If you choose to use the docker environment. Run your commands in the ‘web’ container.

That’s it, you can include other server stats you want to send through email in the exec function of the scheduler.


  1. Laravel Documentation:

Setting up Raspberry Pi Zero W without a monitor, mouse or keyboard :

Setting up a Raspberry Pi Zero W board is quiet simple. All you need are:

  1. A Raspberry Pi Zero W board
  2. MicroSD Card Reader
  3. SD Card with a minimum of 8GB memory size
  4. A power supply for the board ( a USB cord will do if you do not have a power supply)

The items listed above are illustrated from left to right in the image below:

You will also need a computer ( I am running mine on a Windows operating system). Now that we are ready, The steps to follow are:

  1. We plug in our micro SD card reader with our microSD inserted into our computer and wait for it to show up on computer.
  2. We get the “Raspberry Pi Imager” on the Raspberry Pi website. Check out this link. This app will help us with installing and setting up our operating system for the Raspberry Pi Board on the microSD card.
  3. After installing the “Raspberry Pi Imager”. Run it, you should get the window below. Click on the button in the blue circle.
  1. You will get a window to select the operation system you want to install. Select the “Raspberry Pi OS (32-bit)”. This option gives us a Desktop we will be connecting to later in this tutorial.
  1. After selecting your OS of choice, you are taken back to the home screen where you choose the storage device – in this case the MicroSD card you inserted. CAUTION: Ensure the storage you selected is the microSD card you want to use for your Raspberry Pi board.
  1. Before you click ‘write’. Select the Gear icon button at the lower right corner of the window. This is the ‘advanced options’ and this is where you setup the board to connect your network on boot and setup login credentials. Do the following:
    • Enable ‘Set hostname’ and enter a name of your choosing.
      • Enable SSH, select use ‘password authentication’
      • Enable ‘Set username and password’. Enter values of your choosing. Don’t forget both, note them down, you need them to login.
      • Enable ‘Configure wireless LAN’. Enter ‘SSID’ which is the name of the WIFI network you want to connect to. Enter the WIFI password. Select ‘Wireless LAN country’ from the dropdown.
      • Click Save
  1. Click Write then wait for the app to download and install the OS with the option you added.
  1. After the installation process. Connect the board to the power supply and wait for it to boot – the green LED indicates the board is booting . Then check your network to ensure you can find a device with the hostname you added in step 6.
  1. First ensure your computer is connected to the same network as the board. Open your command line,[ enter wsl if on a windows system,] then type in ssh <username>@<hostname> where username and hostname are the ones set in step 6. You are prompted for your password, type it in and press Enter. If all is correct you are logged in as shown below. Notice the change from ‘sheunl@sheunz’ to ‘numnum@tarantula’.

  1. Now you are connected to the command line for the Raspberry, It time to enable the Remote Desktop feature, run sudo raspi-config you will get a command line menu for the Raspberry Configuration Tool
    • Select ‘Interface Options’ using the arrow button then Enter. Then select ‘VNC’. You will get asked ‘Would you like the VNC Server to be enabled?’ press Tab and press Enter on <yes>.
    • VNC server gets enabled and your get a box indicating that.
    • Download RealVNC viewer.
    • Setup the RealVNC viewer and open the app.
    • Connect using the hostname you added at step 6. You will be prompted to confirm SSH key fingerprint, click yes. Then prompted for your SSH username and password. Enter both and click okay.
    • Your should now see the Raspberry Pi OS Desktop in a new window.

Results should be a window like below.

Finally ! You have set up your Raspberry Pi board, have fun.