Alan Bartlett wrote: > The second reference you have quoted actually details how to obtain the > Kernel Sources and set up the build tree in a consistent fashion for > subsequent usage (covered in two other articles). And you cannot see the problem there? So it is already there - in three different articles - and has to be changed *everywhere* if some small aspect of rpm building changes. Having to change that in *one* place and let all other places link to that is a much cleaner approach. >> Basically I think that pointers to the outside are not that good >> because they not necessarily contain CentOS specific information. > > > The main link that Akemi and I currently have in Kernel Sources and Custom > Kernel is to the (maintained) CentOS specific Owl River page ( > http://www.owlriver.com/tips/non-root/). The other link, in the Custom > Kernel article, (http://howtoforge.com/kernel_compilation_centos/) is > mentioned to strongly dissuade its use. Still: People tend to go to the CentOS wiki for finding information (or they are pointed to it). And I'd like to have information like that available *in* the wiki where more than one person can change it should the need arise. Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.centos.org/pipermail/centos-docs/attachments/20080721/e8d166bc/attachment.bin
