Hi there, Have you ever thought what happens internally when we execute any command/executable from the command line? We will be diving in to the ocean of kernel code internals and working of the process lifecycle (creation) in OpenBSD operating system from user-space to kernel space. We will execute the ls command from the command line then trace it through the debugger to see the magic. Following are the basic lifecycle of a process,

Hi there, Today, we will be looking at the update for pledge(2) on OpenBSD and also about howto and usecase. In the previous post about pledge(2), we understood the implementation and some internal working of pledge(2) On 11 December 2017, **Theo de Raadt** said: List: openbsd-tech Subject: pledge execpromises From: Theo de Raadt Date: 2017-12-11 21:20:51 Message-ID: 6735.1513027251 () cvs ! openbsd ! org This will probably be committed in the next day or so.

Hello there, I would like to introduce you all to the pledge(2) which is used to restrict the system operations and supported only on OpenBSD at the time of writing the blog. I am learning about OpenBSD kernel internals and development and would like to share some tips on how to learn about OpenBSD kernel internals and development. Following materials I followed while learning about BSD kernel internals: the book “The design and implementation of the BSD operating system” by Kirk McKusick OpenBSD source code man pages and few presentations-papers on OpenBSD ask in mailing lists and OpenBSD Facebook group.