~bryanb/eudyptula

2a8cb713e283940615b8a2bba7ba0331c52740b3 — Bryan Brattlof 3 years ago 468898c
task 7: add task readme
2 files changed, 28 insertions(+), 1 deletions(-)

M readme.rst
A tasks/07/readme
M readme.rst => readme.rst +2 -1
@@ 24,4 24,5 @@ Here are the links to each task's readme:
5. Module Loading Macros: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/05/readme>`__

6. Miscellaneous Character Drivers: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/06/readme>`__
   

7. Building Linux-Next: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/07/readme>`__

A tasks/07/readme => tasks/07/readme +26 -0
@@ 0,0 1,26 @@
Task 07
=======

Great work with that misc device driver.  Isn't that a nice and simple
way to write a character driver?

Just when you think this challenge is all about writing kernel code,
this task is a throwback to your second one.  Yes, that's right,
building kernels.  Turns out that's what most developers end up doing,
tons and tons of rebuilds, not writing new code.  Sad, but it is a good
skill to know.

The tasks this round are:

  - Download the linux-next kernel for today.  Or tomorrow, just use
    the latest one.  It changes every day so there is no specific one
    you need to pick.  Build it.  Boot it.  Provide proof that you built
    and booted it.

What is the linux-next kernel?  Ah, that's part of the challenge.

For a hint, you should read the excellent documentation about how the
Linux kernel is developed in Documentation/development-process/ in the
kernel source itself.  It's a great read, and should tell you all you
never wanted to know about what Linux kernel developers do and how they
do it.
\ No newline at end of file