iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: Capitalize start of sentence

Browse Source 
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
Michael Witten 2012-04-02 00:49:02 +00:00 committed by Jiri Kosina
parent 88f7a642cf
commit c072c3f0e1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README
View File

@ -218,11 +218,11 @@ CONFIGURING the kernel:
NOTES on "make config": NOTES on "make config":
- having unnecessary drivers will make the kernel bigger, and can - Having unnecessary drivers will make the kernel bigger, and can
under some circumstances lead to problems: probing for a under some circumstances lead to problems: probing for a
nonexistent controller card may confuse your other controllers nonexistent controller card may confuse your other controllers
- compiling the kernel with "Processor type" set higher than 386 - Compiling the kernel with "Processor type" set higher than 386
will result in a kernel that does NOT work on a 386. The will result in a kernel that does NOT work on a 386. The
kernel will detect this on bootup, and give up. kernel will detect this on bootup, and give up.
@ -232,7 +232,7 @@ CONFIGURING the kernel:
but will work on different machines regardless of whether they but will work on different machines regardless of whether they
have a math coprocessor or not. have a math coprocessor or not.
- the "kernel hacking" configuration details usually result in a - The "kernel hacking" configuration details usually result in a
bigger or slower kernel (or both), and can even make the kernel bigger or slower kernel (or both), and can even make the kernel
less stable by configuring some routines to actively try to less stable by configuring some routines to actively try to
break bad code to find kernel problems (kmalloc()). Thus you break bad code to find kernel problems (kmalloc()). Thus you