Como compilo meu kernel?

Iniciado por rafael###, 27 de Maio de 2007, 13:04

tópico anterior - próximo tópico

rafael###

Galera a um tempinho baixei o kernel 2.6.21.1 no www.kernel.org ai fui compila-lo e foi belezinha, agora vem minha dúvida... o novo kernel não suporta o devfs e quando eu inicio pelo kernel que eu compilei ele dá erro e fala que não tem suporte ao devfs (até aí jah sei hehehehe kernel burro), e logo em seguida vem a mensagem q é o terror das pessoas que compilam kernel "Kernel Panic", agora vem a pergunta, o que é o devfs em sí? E como posso livrar meu sistema da dependência dele e usar o novo kernel compilado??

obrigado   ;D



GNU/Linux e SL um novo estilo de vida!!!!!!!!!!

chlferreira

Rafael.
segue testo estraido do site do devfs:
"Devfs is an alternative to "real" character and block special devices on your root filesystem. Kernel device drivers can register devices by name rather than major and minor numbers. These devices will appear in devfs automatically, with whatever default ownership and protection the driver specified. A daemon (devfsd) can be used to override these defaults. Devfs has been in the kernel since 2.3.46.

NOTE that devfs is entirely optional. If you prefer the old disc-based device nodes, then simply leave CONFIG_DEVFS_FS=n (the default). In this case, nothing will change. ALSO NOTE that if you do enable devfs, the defaults are such that full compatibility is maintained with the old devices names.

There are two aspects to devfs: one is the underlying device namespace, which is a namespace just like any mounted filesystem. The other aspect is the filesystem code which provides a view of the device namespace. The reason I make a distinction is because devfs can be mounted many times, with each mount showing the same device namespace. Changes made are global to all mounted devfs filesystems. Also, because the devfs namespace exists without any devfs mounts, you can easily mount the root filesystem by referring to an entry in the devfs namespace.

The cost of devfs is a small increase in kernel code size and memory usage. About 7 pages of code (some of that in __init sections) and 72 bytes for each entry in the namespace. A modest system has only a couple of hundred device entries, so this costs a few more pages. Compare this with the suggestion to put /dev on a ramdisc.
On a typical machine, the cost is under 0.2 percent. On a modest system with 64 MBytes of RAM, the cost is under 0.1 percent. The accusations of "bloatware" levelled at devfs are not justified. "
fonte: http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html

Para vc não usar o devfs vc deve recompilar novamente seu kernel e na compilação desativar ele.

[]s

Carlos Ferreira

rafael###

Obrigado chlferreira mas que opção do make menuconfig eu faço isso?? Não acho!

vlws



GNU/Linux e SL um novo estilo de vida!!!!!!!!!!