projects
/
hdw-linux
/
hdw-linux.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
adaptions: new all-stable target
[hdw-linux/hdw-linux.git]
/
doc
/
FAI
diff --git
a/doc/FAI
b/doc/FAI
index
bbceab0
..
9917e62
100644
(file)
--- a/
doc/FAI
+++ b/
doc/FAI
@@
-20,10
+20,11
@@
procedure
vi Config [specify arch* variables]
vi Config [specify arch* variables]
- note: default target is enough. you dont need to specify fai-server.
- we are just going to install the nfsroot which will automate
- the install process. fai-server is actually the target you will
- need as a running system to have pxeboot/nfsutils and stuff.
+ note: you dont need to specify fai-server as a target. we are just
+ going to install the nfsroot which will automate the install
+ process. the packages of the fai-server target have to be running
+ on the computer on which you are right now following these
+ instructions.
note: you might want to fetch hdw binaries from a mirror.
edit your /etc/hdw-get.conf file.
note: you might want to fetch hdw binaries from a mirror.
edit your /etc/hdw-get.conf file.
@@
-32,7
+33,12
@@
procedure
where <nfsroot> is the directory to install the fairoot.
where <nfsroot> is the directory to install the fairoot.
- 2) edit the following files to match your needs, and restart services
+ 2) adapt the hdw-get.conf file in the fai nfsroot tree
+
+ note: again you might want to use a mirror. edit hdw-get.conf, but make
+ sure it is the one from fairoot.
+
+ 3) edit the following files to match your needs, and restart services
/etc/dhcpd.conf
/etc/inetd.conf
/etc/dhcpd.conf
/etc/inetd.conf
@@
-41,12
+47,9
@@
procedure
(have a look at chapter "fai server configuration")
(have a look at chapter "fai server configuration")
- note: again you might want to use a mirror. edit hdw-get.conf, but make
- sure it is the one from fairoot.
-
- 3) adapt configs in ./fai (see chapter "fai config files")
+ 4) adapt configs in ./fai (see chapter "fai config files")
-
4
) pxeboot your install candidates. this is actually not fully
+
5
) pxeboot your install candidates. this is actually not fully
automated. have a look athe bootdisk section if your client does
not support pxeboot.
automated. have a look athe bootdisk section if your client does
not support pxeboot.
@@
-56,7
+59,7
@@
procedure
(after using cfdisk, sync to disk file!)
- reboot and finaly wathc your target system to get hdw'ed :)
(after using cfdisk, sync to disk file!)
- reboot and finaly wathc your target system to get hdw'ed :)
-
5
) optional: login, build a new kernel or do other modifications.
+
6
) optional: login, build a new kernel or do other modifications.
fai config files
fai config files
@@
-162,7
+165,7
@@
for computers old enough to not support pxe but having installed a piece
of hardware called floppy disk, you may create a bootdisk containing the
install kernel (the pxe stuff is replaced by the bootdisk).
of hardware called floppy disk, you may create a bootdisk containing the
install kernel (the pxe stuff is replaced by the bootdisk).
-- compile a customized kernel <= 1.
1
mb. do not unset needed features!
+- compile a customized kernel <= 1.
3
mb. do not unset needed features!
(use ./misc/arch/${hdw_arch}/linux.config as .config + modify)
(use ./misc/arch/${hdw_arch}/linux.config as .config + modify)