Operating-Systems | 'Operating System Concepts ' - Solutions to exercises

I've finally cross-compiled and linked a binary on an Ubuntu Xenial x86_64 host to run on the Raspberry Pi 4's armhf.

My toolchain's from ARM and placed in $TOOLCHAIN.

My sysroot is a loop-mounted Raspberry OS image placed in $RASPBIAN_ROOT.

This is a sample compilation line:

I am writing a DSL using case classes with the help of the cats.free.Free Monad library. The DSL is to be interpreted by Actors receiving the message, so each actor has to first unwrap a command using Free.resume.

This worked out nicely six years ago using scalaz where we also used the resume function too, but the Functor for the free monad was easy to create as we used case classes that came with an extra function argument that could be mapped over such as k below.

I am using non-blocking IO where I simply try to write and read to a serial port. Reading of the serial port works as expected whereas writing doesn't.

This is how I've set up the serial line. As you can see, it is setup to non-blocking and canonical. Maybe some of the flags are redundant, but they are mostly taken from an example here: Serial setup example

I have just started using python and pycharm, and I have a windows laptop and a mac where I need to work from. In specific, I created a project including a venv in my windows laptop which is uploaded in one drive and works perfectly for that laptop. So my question is; can I work on that same project from my mac?

Instinctively my answer would be no, because all the virtual environment files originally created in the windows venv are .exe which are incompatible with anything mac related. Trying to open the project and load the interpreter myself has confirmed that this doesn't work.

But then I stumbled on to this post, which would suggest that this person can run a project from a windows and linux OS with the only problem being that they only have to re-select the interpreter.

So is there any way that the above can be done, or a workaround at least? (e.g. creating two venvs for each OS or something).

The python package Fire is very useful for launching python scripts from command line. One common thing is to have arguments made of multiple words, for instance name of cat that can be written in 3 commons way :

• nameofcat
• name_of_cat
• name-of-cat

While the first one is compatible with pretty much everything, the second one should be avoided in bash (Should command line options in POSIX-style operating systems be underscore style?) and the third one in python (Why does python disallow usage of hyphens within function and variable names?).

The problem here is that by default fire will take arguments name from the python code, which means that if my python code looks like this:

script.py:

I am exploring to see if we could run confluent on windows. As per the following articles, it seems windows is not supported.

https://docs.confluent.io/current/installation/versions-interoperability.html#operating-systems Confluent Platform in Windows

However, when I look at confluent CLI, windows seems to be supported

https://docs.confluent.io/current/cli/installing.html#tarball-installation

But again, there is a phrase here about windows is not being supported.

On non-Windows platforms, the Confluent CLI offers confluent local commands (designed to operate on a local install of Confluent Platform) which require Java, and JDK version 1.8 or 1.11 is recommended. If you have multiple versions of Java installed, set JAVA_HOME to the version you want Confluent Platform to use.

So, the questions are

• Is windows supported, as per latest ? ( I doubt it is not ?)
• What is the CLI that is being supported for windows ? For what it could be used for ?
• It also seems windows is NOT supported for local development perspective as well ? ( I mean is it possible to issue "confluent local" commands ?

PS : Please give inputs without referring to virtualized environments such as Docker

I am working on Linuxmint Cinnamon 19 Ubuntu 18.04, kernel version 4.15.0-20-generic

The following I see during compilation: