| 1 |
> |
| 2 |
> I think the main point to the discussion is new users. I, too, have never used |
| 3 |
> genkernel so don't know how viable the idea of using it in its current state |
| 4 |
> would be. Nor am I admonishing that it should be the "only way to go". |
| 5 |
> However, everything in Gentoo is configured, compiled and installed through |
| 6 |
> the single emerge command. It would make most sense to me to choose what |
| 7 |
> classes of drivers/functionality I wanted through USE flags and then do |
| 8 |
> post-installation configuration through /etc/modules.autoload*. Can anyone |
| 9 |
> say why the kernel is special and should be done differently? - other than if |
| 10 |
> it ain't broke don't fix it! |
| 11 |
|
| 12 |
Because the kernel is much more than that. Linux as a whole has never |
| 13 |
setup kernel building for new users, and probably never will. You |
| 14 |
actually need to know a lot about your hardware to build an optimized |
| 15 |
kernel for it. |
| 16 |
|
| 17 |
To put into basic perspective, if you want to have USE flags for kernel |
| 18 |
building, would you know to use something like: |
| 19 |
|
| 20 |
USE="pnp network pci radeon 16550 tulip ohci ps2 ipv4 ext3 idecd ata100 |
| 21 |
dma |
| 22 |
|
| 23 |
The list goes on and on. There are somethings as a user your going to |
| 24 |
just have to decide to learn how to do. If not you can always use the rh |
| 25 |
sources, and thier config to have a kernel that will boot almost |
| 26 |
anything. Using use flags as you suggested, still requires you to know a |
| 27 |
lot about your hardware, which wouldn't help you from using the current |
| 28 |
kernel configuration system, which is not gentoo specific. |
| 29 |
> |
| 30 |
> I'm with almost all other people in that it would not be a high priority for |
| 31 |
> some time to come. On the other hand, I'm against people who are putting |
| 32 |
> forward arguments that the kernel is somehow special. Almost every other |
| 33 |
> package is installed with extra cruft so that can't be used as an excuse. |
| 34 |
> Gentoo is about making things easier for everyone which means safe defaults |
| 35 |
> and easily accessible complete customisation, so Luke-Jr's idea at least |
| 36 |
> deserves consideration rather than instant dismissal. |
| 37 |
|
| 38 |
I don't think anyone has an argument with making things easier, but we |
| 39 |
shouldn't make things easier for new users to the detriment of making |
| 40 |
things more difficult for everyone else. There is a point where Gentoo |
| 41 |
just might be more advanced than a new user is skill wise, and accept |
| 42 |
that. |
| 43 |
|
| 44 |
trance |
Archives