1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
Well here is a little description of what panoramix needs to work in comparison
to the standard newt install.
********************************************************************************
* CVS **************************************************************************
********************************************************************************
Like all good free software, panoramix is in CVS :)
You can access it using:
% export CVSROOT=:pserver:anoncvs@linux-mandrake.com:/home/cvs/cooker
% cvs login
% Passwd: cvs
% cvs checkout gi
This is only read-only access. If you want more, tell me (pixel@mandrakesoft.com)
Alas, all is not in CVS as a lot of things are binary files.
For the other things, take cooker-contrib others/src/gi.tar.bz2
Please note that redoing *all* the stuff is not for the faint of heart. I myself
sometimes wonder what the whole make does :-%
Instead, changing some .pm files is quite easy (nice interpreted language)
********************************************************************************
* FILES ************************************************************************
********************************************************************************
First he are the different things needed :
Mandrake/base/hdlist
table of rpm's headers.
! Need to be remade when Mandrake/RPMS changes !
Mandrake/base/depslist
for each packages, tell which package it depends on. Also contains the
size for some (obscure) bloody reasons.
! Need to be remade when Mandrake/RPMS changes !
Mandrake/base/compss
obsoletes comps. It store packages in different categories, a bit like
the %{GROUP} field
Mandrake/base/compssList
for each packages, it gives the appreciation for each type of user.
used to preselect packages
used to decide to show or hide packages.
Mandrake/mdkinst
live system used on certain installs. See ``Ramdisk or not'' below for
more.
Mandrake/base/mdkinst_stage2.gz
for the ramdisk.
live sytem in ext2 filesystem gzipped. See ``Ramdisk or not'' below for
more.
images/gi_*.img
boot images to use with panoramix. Use:
- gi_hd for hard-disk install
- gi_cdrom for cdrom install
- gi_network for ftp/nfs install
- gi_pcmcia for pcmcia install (see ``PCMCIA install'' below for more)
Some optional files :
Mandrake/base/depslist.html
html formatted depslist
********************************************************************************
* po translation files *********************************************************
********************************************************************************
Panoramix uses .po files for its translation. A script takes the different
strings out of the .pm files. It generates the panoramix.pot file which contains
all the english strings to translate.
To add a new language, you just have to add it to lang.pm (if it's not there
already) and put the .po in the perl-install/po directory (see ``Ramdisk or
not'' to know if you have to regenerate the mdkinst_stage2.gz)
********************************************************************************
* PCMCIA install ***************************************************************
********************************************************************************
If the media you use to install is a pcmcia device, you have two choices:
- use the gi_pcmcia boot disk
- use another boot disk and it will ask you a supplementary disk. Give it the
gi_pcmcia disk.
********************************************************************************
* Ramdisk or not ***************************************************************
********************************************************************************
The panoramix install is much bigger than the newt one. So the ramdisk which was
used is getting big, and costs a lot in memory
(eg: the mdkinst_stage2 is 14MB - 23/09/99)
| | newt | panoramix
|-------+---------+----------------------------------------------------------
| nfs | live | live
| ftp | ramdisk | ramdisk
| http | ramdisk | not yet :(
| hd | ramdisk | live if Mandrake/mdkinst/usr/bin/runinstall2 is a link,
| | | ramdisk otherwise
| cdrom | ramdisk | live if memory < 40MB, ramdisk otherwise
When i say live, it means that the install1 stage will *mount* the
Mandrake/mdkinst and use it that way.
The ramdisk is used in place of the live in some cases. This ramdisk is filled
with mdkinst_stage2.gz
For cdrom install, the ramdisk is used to speed up things (access time is quite
high on cdrom drives)
For pcmcia, it depends on the type of install.
********************************************************************************
* modules **********************************************************************
********************************************************************************
Modules can be found in at least 3 places:
- in /modules/modules.cgz
- in /lib/modules/
- in /lib/modules/modules.cpio.bz2
/modules/modules.cgz is used in stage1. It contains only modules interesting for
one kind of install. For example in an gi_hd install, it contains scsi modules.
For an gi_network install, it contains network card modules.
/lib/modules/ contains modules that should be in /lib/modules/modules.cpio.bz2
but are not for speed up. The serial.o module is there to speed up mouseconfig.
/lib/modules/modules.cpio.bz2 contains every module except those of
/lib/modules/
To install a module, use modprobe which is in /usr/bin. It's a perl wrapper
around /usr/bin/insmod. It uses the dependencies found in
/lib/modules/modules.dep (stage1).
/usr/bin/insmod is a wrapper around /usr/bin/insmod_. It just extracts the
module out of /lib/modules/modules.cpio.bz2 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.
|
