/explore
|
You are here 
|
blog.packagecloud.io | ||
| | | | |
venam.net
|
|
| | | | | System calls are one subject that scares many people. Actually most of the low level stuffs happening on the operating system scares a lot of people. I admit, I was a bit afraid of dealing with this subject. Not because it's hard or anything but because it's something that we're not used to dealing with every day, it's lik... | |
| | | | |
binarydebt.wordpress.com
|
|
| | | | | System call table is an array of function pointers. It is defined in kernel space as variable sys_call_table and it contains pointers to functions which implement system calls. Index of each function pointer in the array is the system call number for that syscall. These are denoted by NR_* macros in header files, such as... | |
| | | | |
nfil.dev
|
|
| | | | | This post documents my attempts to manage to jump (or return?) from kernel-space to usermode in my Rust kernel so that it can do what a kernel is supposed to actually do: give the CPU to user programs. That's pretty exciting! In the next part, we'll even take control back from the programs so that we can implement a scheduler. | |
| | | | |
xcellerator.github.io
|
|
| | | Learning about Linux rootkits is a great way to learn more about how the kernel works. What's great about it is that, unless you really understand what the kernel is doing, your rootkit is unlikely to work, so it serves as a fantasic verifier. In the FreeBSD world, you can find Joseph Kong's amazing book Designing BSD Rootkits. It was written in 2009, so is actually pretty outdated - which means that you have to do quite a bit of research to get the sample progras to work on modern FreeBSD. | ||
