From 640255572c30658ad75a7ed7948617dd56fdeaa4 Mon Sep 17 00:00:00 2001 From: Pascal Rigaux Date: Mon, 10 Jul 2000 16:33:21 +0000 Subject: no_comment --- docs/README | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) (limited to 'docs/README') diff --git a/docs/README b/docs/README index ea0f7fe74..93143a4a4 100644 --- a/docs/README +++ b/docs/README @@ -227,3 +227,32 @@ sub selectAlawindows { case, except for auto_install) sub selectAlawindows {} + + +******************************************************************************** +* Miscellaneous **************************************************************** +******************************************************************************** +> o Media access methods: nfs, ftp, http, hd, cdrom +> o Stages: install1, stage1, stage2 +> - What exactly each stage does + +the stage1 takes care of loading the stage2 :) +the stage2 is too big to fit on a floppy, that's why stage1 exists. + +> - How each stage relates to the various media access methods + +stage1 knows only how to access to the media is compiled for. It contains only +the kernel modules needed for that media. For eg, the nfs/ftp/http stage1 +doesn't contain scsi modules nor ide. + +> - How one stage terminates and another begins. i.e., How does +> stage1 find, mount, and launch stage2? + +/sbin/init just starts /sbin/install +/sbin/install takes care of mounting stage2 (in ramdisk if necessary) + then it runs /usr/bin/runinstall2 + +> o Text and Graphic mode installers +> - Architectural overview of each + +have a look at gi/install.fig -- cgit v1.2.1