1 |
Hi, |
2 |
We do use binary packages, but some things like kernel modules are |
3 |
better created on the fly - for example when we roll out a new kernel |
4 |
and the client reboots on the new kernel it will build the appropriate |
5 |
display modules. This can be done using binary packages, but creates |
6 |
more work as new binary packages have to be created every time the |
7 |
kernel is upgraded. |
8 |
|
9 |
We have documented the initial setup of our installer, but havent had |
10 |
time to document the maintenance side of it. It will be posted up when |
11 |
we finish the docs. |
12 |
|
13 |
The docs that exist so far are here: |
14 |
<http://dev.gentoo.org/~baz/binpkgmain/> |
15 |
This goes as far as explaining the installation process only. |
16 |
|
17 |
Cheers |
18 |
Dax |
19 |
|
20 |
Stefan Schweizer wrote: |
21 |
|
22 |
>On Sun, 28 Nov 2004 22:07:53 +0100, Sven Köhler <skoehler@×××.de> wrote: |
23 |
> |
24 |
> |
25 |
>>What kind of automated installer is this? I thought about writing one |
26 |
>>myself, but that might not be necessary if there is one already that i |
27 |
>>haven't found yet. |
28 |
>> |
29 |
>> |
30 |
> |
31 |
>You could help with the gentoo-installer project, if you like writing |
32 |
>installers. |
33 |
> |
34 |
>Dax Bunce: you can just tell your installer to |
35 |
>echo "media-video/nvidia-kernel -*" >> /etc/portage/package.keywords |
36 |
> |
37 |
> |
38 |
It looks like we will have to at this point! Cheers. |
39 |
|
40 |
>That should be possible on an automated install :) |
41 |
> |
42 |
> |
43 |
>Stefan |
44 |
> |
45 |
>-- |
46 |
>gentoo-dev@g.o mailing list |
47 |
> |
48 |
> |
49 |
> |
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |