Add Task 09 description
This commit is contained in:
parent
97de86ceb7
commit
b9dd72e89d
|
@ -0,0 +1,28 @@
|
|||
This is Task 09 of the Eudyptula Challenge
|
||||
------------------------------------------
|
||||
|
||||
Nice job with debugfs. That is a handy thing to remember when wanting
|
||||
to print out some debugging information. Never use /proc/ that is only
|
||||
for processes, use debugfs instead.
|
||||
|
||||
Along with debugfs, sysfs is a common place to put information that
|
||||
needs to move from the user to the kernel. So let us focus on sysfs for
|
||||
this task.
|
||||
|
||||
The tasks this time:
|
||||
|
||||
- Take the code you wrote in task 08, and move it to sysfs. Put the
|
||||
"eudyptula" directory under the /sys/kernel/ location in sysfs.
|
||||
- fix up the permissions of the files to not allow world writable
|
||||
values, but only be able to be written to by root.
|
||||
- Provide some "proof" this works.
|
||||
|
||||
That's it! Simple, right? No, you are right, it's more complex; sysfs
|
||||
is complicated. I'd recommend reading Documentation/kobject.txt as a
|
||||
primer on how to use kobjects and sysfs.
|
||||
|
||||
Feel free to ask for hints and help with this one if you have questions
|
||||
by sending in code to review if you get stuck. Many people have dropped
|
||||
out in the challenge at this point in time, so don't feel bad about
|
||||
asking. We don't want to see you go away just because sysfs is so damn
|
||||
complicated.
|
Loading…
Reference in New Issue