1 |
On Wed, Aug 01, 2001 at 10:29:07PM +0300, Dan Armak wrote: |
2 |
|
3 |
> > OK; please use sys-kernel/linux-sources-2.4.6 as your model for creating |
4 |
> > this new ebuild. (Remove all the patches, but keep everything else) |
5 |
|
6 |
> I was going to, but there are so many if these patches and configs I think |
7 |
> maybe I'll be better off writing from scratch. After all it only has to |
8 |
> extract an archive and little else. |
9 |
|
10 |
Please follow my instructions. That's an order :) When you strip out all |
11 |
those patches you'll realize that there are several important commands that |
12 |
you probably would not think of adding if you didn't use linux-sources as |
13 |
a base. |
14 |
|
15 |
> > /usr/src/linux-vanilla-x.y.z should be good. |
16 |
|
17 |
> The problem is: when there are several linux-sources and |
18 |
> linux-sources-vanilla emerged together, in /usr/src there are the links |
19 |
> 'linux' and 'linux-2.4' ehich must point to either sources or vanilla. How do |
20 |
> we decide? Do we create a link to ourselves (i.e. vanilla) if there is no |
21 |
> other link? A worse problem is /lib/modules. Here each kernel's modules dir |
22 |
> is only identified by the version number, and each has a link back to its |
23 |
> kernel sources! What do we do? |
24 |
|
25 |
Well, normally, I'd say "patch linux-sources-vanilla so the kernel name is |
26 |
linux-vanilla-x.y.z". But this goes against the no-patch concept of the |
27 |
vanilla sources. Therefore, we should patch our already-patched kernels so |
28 |
they show up as linux-gentoo-x.y.z. Please place all your work in the |
29 |
package.mask for the time being, since they will conflict with our patched |
30 |
kernel. I'll get our official kernel patched before 1.0_rc6 is released; add a |
31 |
wiki item for the system team to remind me. |
32 |
|
33 |
Best Regards, |
34 |
|
35 |
-- |
36 |
Daniel Robbins <drobbins@g.o> |
37 |
Chief Architect/President http://www.gentoo.org |
38 |
Gentoo Technologies, Inc. |