I'm glad to review your course. My question deals with your GNU GENERAL PUBLIC LICENSE. Speaking honestly, if I had known your course was licensed, I would not have taken it. There are many other free courses offered over the Internet that is not shackled with a license agreement; but your course meets all of my needs (particularly, your OS runs on a real computer instead of a VM). After taking your course, I'm going to code my own OS in risc-v, write my own assembler, and translate my own compiler into my assembly intermediate language. My software will be proprietary. My question is: Should your license agreement be a concern? If not, my next question is: now that I paid for your course, how and when do I begin to code?
Hi Albert,
I am a some-what confused about what you mean when you say how and when do you begin to code?
The coding begins from the moment we write a hello world bootloader, by the end of the course you will have a fully functioning multi-threaded kernel.
As for your licensing concerns, licenses are indeed very important to prevent abuses, when you purchased my course you are purchasing a license to watch the video content the source code was always free under GPL license. Of course the video content is very handy because it actually teaches you kernel development, we end up with the same result upon completing the course.
If you can tell me a little more why you believe my license to be a concern I can answer you. The information I teach in my course are ideas and concepts so are not under my intellectual property (the video content is however and the Dragon Zap license allows only you to watch the course that you purchased and not redistribute it), the source code repository on Github is however my code and work and therefore under the GPL license and all code used from the repository should be under the GPL license.
The GPL license allows you freedoms and keeps software free, you can still sell GPL software but you must follow the licence terms provided.
If you want to reach out to me for a more formal communication please email daniel@dragonzap.com and if you can tell me more about what you plan to do I might be able to issue you an additional license for your needs.
Thanks !
This course is designed to teach you how to create your very own multitasking operating system and kernel from scratch. It is assumed you have no experience in programming kernels and you are taught from the ground up.
Real Mode Development
Real mode is a legacy mode in all Intel processors that causes the processor to start in a legacy state, it performs like the old 8086 Intel processors did back in the way.
In the "Real Mode Development" section of the course we start by learning about the boot process and how memory works, we then move on to creating our very own boot loader that we test on our real machine! This boot loader will output a simple "Hello World!" message to the screen and we write this boot loader in purely assembly language.
In this section we also read a sector(512 bytes) from the hard disk and learn all about interrupts in real mode and how to create them.
This section gives you a nice taster into kernel development, without over whelming you with information. You are taught the basics and enough about the legacy processors to be able to move forward to more modern kernel development further into this course.
Protected Mode Development
In this section we create a 32 bit multi-tasking kernel that has the FAT16 filesystem. Our kernel will use Intel's built in memory protection and security mechanisms that allow us to instruct the processor to protect our kernel and prevent user programs from damaging it.
This section is very in depth, you are taught all about paging and virtual memory. We take advantage of clever instructions in Intel processors to allow all processes to share the same memory addresses, this is known as memory virtualization. We map memory addresses to point to different physical memory addresses to create the illusion that every process that is running is loaded at the same address. This is a very common technique in kernel development and is also how swap files work (Those files that are used to compensate for when you run out of usable RAM).
We create our own virtual filesystem layer that uses a design that is similar to the Linux kernel. This clever abstraction that will be taught to you was inspired by the instructors knowledge of writing Linux kernel drivers in his past.
You are taught about the design of the FAT16 filesystem and how the FAT16 filesystem is broken down into clusters and that they can chain together. We then implement our very own FAT16 filesystem driver allowing files to be born!
We implement functionality for tasks and processes and write our own keyboard drivers.
In this course you also get to learn how memory management works, we implement the "malloc" and "free" functions creating our very own heap that's designed to keep track of what memory is being used. Memory management is essential in any operating system and kernel.
Let us not forget that we even create an ELF file loader, we will compile all our operating systems programs into ELF files and allow the loading of binary programs or ELF programs. ELF files contain a lot of information that describes our program for example where our program should be loaded into memory and the different sections of the program.
By the end of this course you will have a fully functioning 32 bit multi-tasking kernel that can have many processes and tasks running at the same time. You will have a working shell that we can use as well.
Assembly language bonus
This is a bonus section designed to bring your assembly skills up to scratch should you struggle a little bit with the assembly language in this course. It's however advised you come to this course with experience in assembly language, we do use it and its important. Never the less if you want to take a chance on this course with no assembly experience then this section will help point you in the right direction so your able to take what you learned and apply it to the kernel.
Taught by an expert that has created Linux kernel modules professionally in the work place.
Requirements
Understanding the C programming language
Understanding Assembly Language
Who This Course is For
People who want to develop a kernel from scratch
What You Will be Learn
How to create a kernel from scratch
How to create a multi-tasking kernel
How to handle malicious or problematic programs in your operating system. Terminating them if they misbehave.
How memory works in computers
The difference between kernel land, user land and the protection rings that make up modern computing
Kernel design patterns used by the Linux kernel its self
You will learn all about virtual memory and how to map virtual addresses to physical addresses
You will learn how to make the kernel understand processes and tasks
You will learn how to load ELF files
You will learn how to debug disassembled machine code
You will learn how to debug your kernel in an emulator with GDB.
Daniel McCarthy is a seasoned software engineer, boasting an impressive career spanning over 14 years in the industry. Holding a Master's Degree in Advanced Computer Science from Cardiff Metropolitan University, his broad spectrum of experience encompasses everything from web development to complex compiler and interpreter development.
Daniel has honed his skills in bootloader and kernel development. In testament to his proficiency in the field, he has designed two proprietary programming languages: Craft, a general-purpose language, and Marble, a web-focused language akin to PHP. Moreover, he has successfully developed compilers for the C programming language.
A testament to his versatility, Daniel demonstrates proficiency in an extensive list of programming languages that includes C, C++, Java, x86 Assembly language, PIC assembly, SQL, PHP, HTML5, JavaScript, CSS, and of course, his own creations, Craft and Marble.
His professional portfolio also includes the development of Linux kernel modules, a task he has executed with proficiency in a professional context. Currently, Daniel is channeling his wealth of experience and expertise into the education sector, with the aim of nurturing the next generation of professional software engineers.
Ask a question
Questions (1)
Albert Ford
2 years ago
I'm glad to review your course. My question deals with your GNU GENERAL PUBLIC LICENSE. Speaking honestly, if I had known your course was licensed, I would not have taken it. There are many other free courses offered over the Internet that is not shackled with a license agreement; but your course meets all of my needs (particularly, your OS runs on a real computer instead of a VM). After taking your course, I'm going to code my own OS in risc-v, write my own assembler, and translate my own compiler into my assembly intermediate language. My software will be proprietary. My question is: Should your license agreement be a concern? If not, my next question is: now that I paid for your course, how and when do I begin to code?
Daniel McCarthy
2 years ago
Hi Albert, I am a some-what confused about what you mean when you say how and when do you begin to code? The coding begins from the moment we write a hello world bootloader, by the end of the course you will have a fully functioning multi-threaded kernel. As for your licensing concerns, licenses are indeed very important to prevent abuses, when you purchased my course you are purchasing a license to watch the video content the source code was always free under GPL license. Of course the video content is very handy because it actually teaches you kernel development, we end up with the same result upon completing the course. If you can tell me a little more why you believe my license to be a concern I can answer you. The information I teach in my course are ideas and concepts so are not under my intellectual property (the video content is however and the Dragon Zap license allows only you to watch the course that you purchased and not redistribute it), the source code repository on Github is however my code and work and therefore under the GPL license and all code used from the repository should be under the GPL license. The GPL license allows you freedoms and keeps software free, you can still sell GPL software but you must follow the licence terms provided. If you want to reach out to me for a more formal communication please email daniel@dragonzap.com and if you can tell me more about what you plan to do I might be able to issue you an additional license for your needs. Thanks !