About Me

Software / Cloud DevSecOps Engineer

For the past five years I've been hooked on Linux from Scratch (LFS) and Beyond Linux from Scratch (BLFS). At first, the goal was to manually build my own Linux distribution by following the LFS and BLFS documentation. That project evolved over time — I now have Jenkins pipelines that automate the build of my distribution in a few hours, featuring a Hyprland frontend. I run this LFS/BLFS-based system natively and plan to use it as my main platform for future Linux kernel development.

Goals

I'm currently focused on gaining a deeper understanding of the Linux kernel — not only the code itself, but also the community workflow, review process, and contribution practices that surround it. My long-term goal is to start contributing meaningfully to the Linux kernel project while documenting what I learn along the way.

System Details

• Base/Native: LFS w/pieces of BLFS

• Window Manager: Hyprland

• Tools: GDB, QEMU, Vim, Git, Mutt, and Sendmail

Interests

• Linux: LFS/BLFS; Hyprland; Linux Kernel: development, process/workflow, debugging, internals, security

• Cloud: Infrastructure, security

• DevSecOps: practices

• Other: Automated build systems, Opensource

Contact

• Email: <wg21908 AT SPAMFREE gmail DOT com>

Learning Journal

• First Linux Kernel related ticket: I found a ticket that looked like an easy one, for a first attempt at contributing to something that would be included in a future Linux kernel release. The goal here was just to get more familiar with the workflow/process for getting something included in a future Linux kernel release. I found ticket https://bugzilla.kernel.org/show_bug.cgi?id=220489. It looked to be an easier ticket since it was a man-pages documentation-related ticket. I basically did an advanced search with a Severity: low, Status: NEW, ASSIGNED, REOPENED, and Creation date: (is greater than) -3M. At the time of my search, there were only 4 results. I could see that the ticket was still assigned to the general group email and that it didn't appear that anyone started looking at it yet. To play it safe though, I still emailed the maintainer email address to give them a heads up of my interest and plan to work on the ticket, email archived at https://lore.kernel.org/linux-man/aP0T3yZ0jflUtliV@secra.localdomain/T/#u. The steps I followed to carry out the fix are listed below. This is still a work in progress, I need to wait for the peer review. More updates may come out of the peer review.

  • git clone https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git

  • cd man-pages
  • git checkout master
  • git pull origin master
  • git checkout -b fix-copy_file_range-fallback-doc
  • Fix applied to man2/copy_file_range.2 man-page file
  • make -R check
  • More fixes applied to man2/copy_file_range.2 man-page file due to found issue from check make cmd
  • git add man2/copy_file_range.2
  • git commit --amend -s
  • git format-patch origin/master
  • git log --oneline origin/master..

  • git send-email --to=linux-man@vger.kernel.org --cc=mtk.manpages@gmail.com 0001-Subject-copy_file_range.2-glibc-no-longer-provides-f.patch

  • The archive showing the emailed patch can be seen at https://lore.kernel.org/linux-man/20251025221258.45073-1-wg21908@gmail.com/T/#u

CategoryHomepage