How to configure Static Local IP Address in Ubuntu

In Linux, if you were working on networking, you may be came to a point when you need to assign static IP to your system over the local network. There may be any reason. If you want to communicate with a PC on the network, then whenever your system restarts, local IP changes based on the subnet mask. To avoid this, you need to fix your preferred local IP in the network configuration.

today's leftovers

• X.Org Foundation Bows Out For Google Summer of Code 2021

  Over the years Google Summer of Code (GSoC) has resulted in some really great projects in the X.Org ecosystem from work in the early days on the open-source Radeon graphics driver stack to VKMS more recently to many other improvements especially as it pertains to open-source graphics drivers / Mesa. But for Google Summer of Code 2021 at least, the organization will not be participating.  With rare exceptions, the X.Org Foundation has been a regular fixture of GSoC for as long as Google has been putting it on for more than one decade. It's resulted in many great contributions not only about the X.Org Server but the X.Org Foundation / FreeDesktop.org ecosystem to the likes of Mesa, Wayland, input, and more. 

• KDE Code Formatting

  Short history of the ‘KDELIBS’ coding style Once upon a time, in the monolithic KDELIBS world, we had some document describing the KDELIBS coding style. Over the years, that evolved a bit and ended up here as Frameworks Coding Style. As noted there, it is more or less the same stuff Qt does style wise. How was that coding style handled in practice? Actually, this styling was really never enforced on a global scale. During the “we split KDELIBS up into Frameworks” time, on the initial import, the code was once run through astyle to ensure that coding style was kept. But after the initial import, nothing of that sort happened anymore (at least not in some coordinated fashion). Beside, for non-Frameworks, such a mandatory style application never happened. Actually, it was never be agreed that this style is mandatory beside for KDELIBS itself, anyways. Naturally, individual sub-projects/maintainers started to enforce either the stuff linked above or individual similar styles through different means. e.g. in kate.git we noted in the README that we wanted to follow that style. That was it ;=)

 

• oneAPI Level Zero 1.2.3 Released For Intel's Low-Level Interface

  With oneAPI Level Zero 1.2.3 they now support the Level Zero 1.1 specification, which is just a minor update over last year's official Level Zero 1.0 specification. The original oneAPI Level Zero specification was tentatively published back at the end of 2019 as Intel's direct-to-metal interfaces with a focus on offload accelerators. This is not to be confused with the oneAPI specification itself, which is working towards its v1.1 release later this calendar year, but is solely about the "Level Zero" specification. Yes, the oneAPI versioning scheme has become rather convoluted across its many different software components and specifications.  [...] The new release does require an updated Intel Compute Runtime stack for hardware support. On that front yesterday marked the Intel Compute Runtime 21.09.19150 release that updates the Intel Graphics Compiler as its only listed change. The Intel Compute Runtime continues to list its Level Zero support as 1.0 in a pre-release stage, while also enjoying OpenCL 3.0 production support)

   

• Five good reasons to try NextCloud in 2021

  I said so because I thought, and still think, that NextCloud is the most promising self-hosted, Free/Open Source alternative for the services that companies like Dropbox, Google, Facebook or Skype provide in exchange for users’ data, privacy and more. There were already plenty of good reasons to use NextCloud for those services in 2019, and there are many, many more in 2021. But don’t take my word for it. In case you missed NextCloud so far, here are X reasons to try NextCloud now, both personally, and for your company.

Raspberry Pi and Yocto

• Track your family calendar with a Raspberry Pi and a low-power display

  The calendar started as a holiday project, so I tried to reuse as much as I could. This included a Raspberry Pi 2 that had been unused for too long. I did not have an E Ink display, so I had to buy it. Fortunately, I found a vendor that provided open source drivers and examples for its Raspberry Pi-ready screen, which is connected using some GPIO ports. My family also wanted to switch between different calendars, and that required some form of input. Instead of adding a USB keyboard, I opted for a simpler solution and bought a 1x4 matrix keypad, similar to the one described in this article. This allowed me to connect the keypad to some GPIO ports in the Raspberry Pi. Finally, I needed a photo frame to house the whole setup. It looks a bit messy on the back, but it gets the job done.

• That Yocto Thing

  Many hardware vendors use Yocto as a way to provide a version of the Linux Kernel and board bring up package. This is a very Linux-from-scratch type approach that grew out of GenToo. My current work is on closing the gap between these vendors and the RPM based code management approach in Fedora etc.