summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/HACKING21
-rw-r--r--docs/README7
2 files changed, 15 insertions, 13 deletions
diff --git a/docs/HACKING b/docs/HACKING
index b35825449..313866401 100644
--- a/docs/HACKING
+++ b/docs/HACKING
@@ -61,20 +61,21 @@ gc ALL=(root) NOPASSWD:/usr/bin/patch,NOPASSWD:/bin/rpm,NOPASSWD:/bin/mount,NOPA
(4) boot kernel
-you need a boot kernel and some kind of modules for each boot floppy. it's
-located in subdirectory "kernel" in DrakX-*.src.rpm ; if you ever grab (or
-build) another boot kernel, re-do following step (c).
+you need one or more kernels and (all?) their modules. it's located in
+subdirectory "all.kernels" in DrakX-*.src.rpm ; if you ever grab (or
+build) another boot kernel, replace or add an entry in "all.kernels" as:
- (a) build the packager software for stage1 (read README file to know what's stage1)
- [gc@obiwan ~/cvs/gi] cd mdk-stage1/mar
- [gc@obiwan ~/cvs/gi/mdk-stage1/mar] make
+ (a) create your modules subdir (useful to describe the
+ VERSION_RELEASE) and untar your kernel
- (b) build the perl stuff for stage2
- [gc@obiwan ~/cvs/gi] cd perl-install
- [gc@obiwan ~/cvs/gi/perl-install] make
+[gc@obiwan ~/cvs/gi/all.kernels] mkdir 2.4.1-BOOTcustom
+[gc@obiwan ~/cvs/gi/all.kernels] cd 2.4.1-BOOTcustom
+[gc@obiwan ~/cvs/gi/all.kernels/2.4.1-BOOTcustom] tar jxvf ~/mycustomkernel.tar.bz2
+[gc@obiwan ~/cvs/gi/all.kernels/2.4.1-BOOTcustom] ls
+boot/ cardmgr/ lib/
(c) build kernel/modules stuff for stage1 and stage2
- [gc@obiwan ~/cvs/gi] ./update_kernel
+[gc@obiwan ~/cvs/gi] ./update_kernel
(5) pray
diff --git a/docs/README b/docs/README
index 7cbdd66c0..71b23c84d 100644
--- a/docs/README
+++ b/docs/README
@@ -193,7 +193,7 @@ For pcmcia, it depends on the type of install.
********************************************************************************
Modules can be found in at least 2 places:
- in /modules/modules.mar
-- in /lib/modules.cz2
+- in /lib/modules.cz<KERNEL_VERSION_RELEASE>
/modules/modules.mar is used in mdk-stage1. It contains only modules
interesting for one kind of install. For example in an hd install, it
@@ -202,7 +202,8 @@ modules. (To create, extract or view files in a ``mar'' archive, please
use gi/mdk-stage1/mar/mar; this is basically an archive format meant to
be minimalistic)
-/lib/modules.cz2 contains every module, it is used in stage2.
+/lib/modules.cz<KERNEL_VERSION_RELEASE> contains all modules, it is used
+in stage2.
To install a module, use modprobe which is in /usr/bin. It's a perl wrapper
@@ -210,7 +211,7 @@ around /usr/bin/insmod. It uses the dependencies found in
/modules/modules.dep (stage1).
/usr/bin/insmod is a wrapper around /usr/bin/insmod_. It just extracts the
-module out of /lib/modules.cz2 in /tmp. Then it calls insmod_.
+module out of /lib/modules.cz in /tmp. Then it calls insmod_.
/usr/bin/insmod_ is the real prog (which you usually find in /sbin/). You need
to give it the complete path.