Renaming files

Tags:

Developer tools - renaming files

It sometimes happens that we need to rename files to fix a file naming convention. This happened to me as well. Last time when I followed the suggestion to mix all words in the file name without any delimiter.

This is a very fragile suggestion but I usually used to name files like: FirstSecond or first-second as that makes it visually more readable but what if in the bigger project I want to look for the file. If I search visually without any engine for the file that's better for reading but when we want manually navigate for the let's say for the key: headerbar. It's not so obvious to type headerbar header-bar or HeaderBar.

Here I want to share my perl script for renaming: rename-files.pl

The Blog Refurbished

Tags:

This is my first post on blog

For a long time I wasn't able to manage my blog and finally I forgot how to use this fancy tool named Hugo. As I am not a fan of Go at all. I decided to use kind of static generator written in the language that I like to use. So that's a Perl.

I will try to describe in this post how to configure Statocles.

I used mainly documentation from here.

Main commands:

Check the local changes, this command has no live option unfortunately. So I must restart it again and again. statocles daemon

The deployment is done by generating static HTML/CSS into build directory. The content of directory is uploaded after all onto sr.ht hosting. statocles deploy

A whole configuration is inside the site.yml file. Where I managed three statocles applications.

  • /blog Statocles::App::Blog this expects markdown files placed in the year/month/day subdirectories

  • /about Statocles::App::Basic this expects the single file index.markdown placed.

Each application has its own definition where we define: class, store directory and URL.

With the static app I defined directory to keep all images together.

The deploy script is a helper script for sr.ht hosting.

Enjoy!

Creating minimal linux test environment

Tags:

Creating minimal linux test environment

Building Kernel with default x86_64 configuration

  • create default kernel build configuration using existing defconfig make ARCH=x86 x86_64_defconfig The file .config is created in linux root directory. It can be still modified with make menuconfig
  • build kernel image make -j8 As a result we obtain a vmlinux binary which is a stand-alone monolithic ELF image. This binary contains no unresolved external refeces. Despite this file was found at the top-level kernel directory. Very few platforms boot this image directly including qemu emulator. In order to boot qemu we need to use bzImage compressed kernel file. From: arch/x86/boot/bzImage

  • preparing initramfs

I prepared a simple initramfs just to make kernel fully boot into shell. As a shell it was used busybox (just remember to check if that's a standalone version "static") The directories were created in compliance to FHS (Filesystem Hierarchy Standard). And I finally I add an init script which initializes busybox and mount pseudo-file system like sysfs procfs dev and tmp.

  • running qemu By running appropriate qemu command: qemu-system-x86_64 -kernel ./arch/x86/boot/bzImage -nographic -append "console=ttyS0" -initrd initrd

In order to exit qemu run: Ctrl-a x

Full work can be found here: test_environment