2010/4/17 Guilherme Raymo Longo <[email protected]>: > Desculpa.. esse foi o procedimento usado .. as versoes não foram essas. Eu > apenas copiei e colei o procedimento > > o procedimento correto foi esse: > > make menuconfig > make > make modules_install > cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.29.6 > ln vmlinuz-2.6.29.6 vmlinuz -sf > ln System.map-2.6.29.6 System.map -sf > ln config-2.6.29.6 config -sf > depmod -ae > > image = /boot/vmlinuz-2.6.29.6 > label = Linux > root = /dev/sda2 > read-only > lilo > > Agora esta certo > > 2010/4/17 Ellington Santos <[email protected]> >> >> 2010/4/17 Guilherme Raymo Longo <[email protected]>: >> > Pessoal, desculpe o ultimo e-mail. >> > Achei que meu problema havia sido sanado, mas não foi. Acidentalmente >> > acabou >> > funcionando mas repeti a dose e não funcionou denovo. >> > >> > Só estou registrando isso pois outra pessoas podem tentar fazer e dar >> > errado >> > tb. >> > Eu não preciso usar o initrd, e segui as seguintes configuração para >> > recompilar o kernel aprós feita uma novo nstalação do sistema e >> > simplesmente >> > não funcionou. Eu não alterei um parametro se quer da configuração >> > apenas >> > segui esses procedimentos: >> > >> > make menuconfig >> > make >> > make modules_install >> > cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.17 >> > mkinitrd -o /boot/initrd.img-2.6.17 2.6.17 >> > ln vmlinuz-2.6.17 vmlinuz -sf >> > ln System.map-2.6.17 System.map -sf >> > ln config-2.6.17 config -sf >> > depmod -ae >> > >> > image = /boot/vmlinuz-2.6.17 >> > label = Linux >> > initrd = /boot/initrd.img-2.6.17 >> > root = /dev/ram0 >> > append = >> > read-only >> > >> > lilo >> > >> > >> > * O mesmo erro acontece: >> > >> > No filesystem could mount root, tried: romfs >> > Kernel Panic - Not syncing: VFS Unable to mount root fs on >> > unknown-block(8,2) >> > >> > Eu estava utilizando o kernel HUGE... >> > >> > O que será que falta...... >> > Só pode estar faltando algo no procedimento de recompilação pois eu não >> > fiz >> > nenhuma alteração nas opções do kernel. >> > >> > >> > >> > 2010/4/17 Guilherme Raymo Longo <[email protected]> >> >> >> >> Pessoal, gostaria de concluir essa thread... >> >> Não consegui arrumar o sistema apenas recompilando um novo kernel. >> >> Provavelmente estraguei alguma coisa nas mnhas indas e vindas tentando >> >> arruma-lo. >> >> Reinstalei o sistema e para teste recompilei o kernel sem alterar, e >> >> funcionou numa boa. Ou seja, o procedimento básico estava certo.... >> >> >> >> Muito obrigado pela atenção de todos. >> >> >> >> >> >> 2010/4/16 max <[email protected]> >> >>> >> >>> Então tu concorda que o CONFIG_MODULE_FORCE_LOAD=y não vai "carregar >> >>> automaticamente todos os módulos"? Porque pelo que tu disse antes, deu >> >>> a entender que ao ativar essa opção automagicamente o problema de >> >>> módulos não carregarem é removido... ;) >> >>> >> >>> On 4/16/10, Daniel <[email protected]> wrote: >> >>> > Só é ter conhecmiento de todo o teu hardware (tem como saber via >> >>> > shell >> >>> > ou >> >>> > usa o hardinfo (gui) que ajuda bastante) e saber qual filesystem >> >>> > você >> >>> > usa, >> >>> > quais quer ter suporte e etc..., e ter cuidado quando for >> >>> > compilar/recompilar o kernel de marcar como build o filesystem e >> >>> > tudo >> >>> > necessário. :) >> >>> > >> >>> > Em 16 de abril de 2010 12:51, max <[email protected]> escreveu: >> >>> > >> >>> >> Se ele não conseguir montar o filesystem pq não tem o módulo p/ o >> >>> >> mesmo ou para a controladora de disco, de onde o módulo é >> >>> >> carregado? >> >>> >> >> >>> >> 2010/4/16 Daniel <[email protected]>: >> >>> >> > Cara marca em Enable Loadable modules suport -> [*] Forced module >> >>> >> loading, >> >>> >> > assim ele vai carregar automaticamente todos os modulos sem >> >>> >> > precisar >> >>> >> > de >> >>> >> > initrd. =) >> >>> >> > >> >>> >> > Em 15 de abril de 2010 09:40, Guilherme Raymo Longo >> >>> >> > <[email protected]> escreveu: >> >>> >> >> >> >>> >> >> Obrigado Hudson, essa semana ando meio atarefado. Assim que >> >>> >> >> testar >> >>> >> >> as >> >>> >> >> opções volto pra agradecer denovo >> >>> >> >> >> >>> >> >> ;O) >> >>> >> >> >> >>> >> >> 2010/4/14 Hudson Figueredo <[email protected]> >> >>> >> >>> >> >>> >> >>> Guilherme Raymo! >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >>> >> >> >>> >> http://kynder.pquilinux.org/index.php?option=com_content&task=view&id=15&Itemid=37 >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >>> >> >> >>> >> http://kynder.pquilinux.org/index.php?option=com_content&task=view&id=18&Itemid=37 >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> e também pode baixar o pQui :) >> >>> >> >>> >> >>> >> >>> www.pquilinux.org >> >>> >> >>> >> >>> >> >>> Powered by Slackware - 100% compatible >> >>> >> >>> >> >>> >> >>> Abraço >> >>> >> >>> >> >>> >> >>> 2010/4/13 Renato Bonfanti <[email protected]> >> >>> >> >>>> >> >>> >> >>>> vga=normal no lilo.conf elimina esse problema do VESA, qto ao >> >>> >> >>>> initrd >> >>> >> >>>> ele parece bem usado nas distros "debian like", eles quase >> >>> >> >>>> sempre >> >>> >> >>>> usam >> >>> >> >>>> initrd. >> >>> >> >>>> No slackware sempre compilei o essencial dentro do kernel >> >>> >> >>>> (tudo >> >>> >> >>>> que é >> >>> >> >>>> essencial pra minha maquina) e o que talvez um dia use , como >> >>> >> >>>> modulo >> >>> >> >>>> e >> >>> >> >>>> nunca usei o initrd mesmo. >> >>> >> >>>> Muito boa a dica do make localmodconfig, não conhecia essa vai >> >>> >> >>>> me >> >>> >> >>>> adiantar um bom lado da proxima vez :) >> >>> >> >>>> >> >>> >> >>>> Em 13 de abril de 2010 12:29, max <[email protected]> >> >>> >> >>>> escreveu: >> >>> >> >>>> > -o bind e --bind são equivalentes, não precisa dos dois, usa >> >>> >> >>>> > um >> >>> >> >>>> > ou >> >>> >> >>>> > outro. >> >>> >> >>>> > >> >>> >> >>>> > Eu uso o -o bind por algum motivo, acho que eu peguei um >> >>> >> >>>> > Solaris ou >> >>> >> >>>> > BSD que não tinha o --bind e acabou ficando o vício... >> >>> >> >>>> > >> >>> >> >>>> > 2010/4/13 Helber Maciel Guerra <[email protected]>: >> >>> >> >>>> >> A melhor maneira de fazer o chroot é montar via bind os >> >>> >> >>>> >> devices >> >>> >> >>>> >> tb. >> >>> >> >>>> >> >> >>> >> >>>> >> Depois de montar a partição, montar o diretório de devices >> >>> >> >>>> >> tb, >> >>> >> >>>> >> pois >> >>> >> >>>> >> com ele >> >>> >> >>>> >> vica "visível" os dispositivos dentro do chroot. >> >>> >> >>>> >> Só assim, "dentro" do chroot vc vai ter acesso ao seu >> >>> >> >>>> >> hardware. >> >>> >> >>>> >> >> >>> >> >>>> >> mkdir /chroot >> >>> >> >>>> >> mount /dev/sda1 /chroot >> >>> >> >>>> >> mount --bind /dev /chroot/dev >> >>> >> >>>> >> mount -t proc proc /chroot/proc >> >>> >> >>>> >> mount -o bind /dev/ /chroot/dev >> >>> >> >>>> >> chroot /chroot /bin/bash >> >>> >> >>>> >> source /etc/profile >> >>> >> >>>> >> >> >>> >> >>>> >> Depois não esqueça de desmontar tudo que foi montado antes. >> >>> >> >>>> >> >> >>> >> >>>> >> Outra coisa, nos fontes dos kernels mais novos tem 2 opções >> >>> >> >>>> >> muito >> >>> >> >>>> >> interessantes: >> >>> >> >>>> >> make localmodconfig >> >>> >> >>>> >> make localyesconfig >> >>> >> >>>> >> >> >>> >> >>>> >> O que eles fazem é inspecionar os módulos carregados pelo >> >>> >> >>>> >> seu >> >>> >> sistema >> >>> >> >>>> >> atual >> >>> >> >>>> >> (kernel que está rodando) e coloca eles como módulos ou >> >>> >> >>>> >> embutidos >> >>> >> na >> >>> >> >>>> >> sua >> >>> >> >>>> >> configuração. >> >>> >> >>>> >> Sobre as opções de compilação do kernel use o "make help". >> >>> >> >>>> >> >> >>> >> >>>> >> Abraços, Helber Maciel Guerra. >> >>> >> >>>> >> >> >>> >> >>>> >> Em 13-04-2010 12:09, max escreveu: >> >>> >> >>>> >> >> >>> >> >>>> >> Isso não é um problema propriamente dito, o teu chroot não >> >>> >> >>>> >> foi >> >>> >> feito >> >>> >> >>>> >> da "forma ideal" e ele só deu uns avisos. >> >>> >> >>>> >> >> >>> >> >>>> >> O "ideal" neste tipo de situação é fazer o seguinte: >> >>> >> >>>> >> >> >>> >> >>>> >> mkdir /chroot >> >>> >> >>>> >> mount /dev/sda1 /chroot >> >>> >> >>>> >> mount -t proc proc /chroot/proc >> >>> >> >>>> >> mount -o bind /dev/ /chroot/dev >> >>> >> >>>> >> chroot /chroot /bin/bash >> >>> >> >>>> >> source /etc/profile >> >>> >> >>>> >> >> >>> >> >>>> >> Quem já instalou um gentoo deve estar acostumado com isso. >> >>> >> >>>> >> >> >>> >> >>>> >> O aviso sobre o video é porque tu usa um vga=algumacoisa >> >>> >> >>>> >> que >> >>> >> >>>> >> não é >> >>> >> >>>> >> suportado pela placa de video (geralmente porque falta o >> >>> >> >>>> >> módulo >> >>> >> dela >> >>> >> >>>> >> no livecd, em alguns casos porque a placa é porca e não >> >>> >> >>>> >> suporta >> >>> >> >>>> >> mesmo). Se tiver algum problema, a tela fica preta e um >> >>> >> >>>> >> vga=normal >> >>> >> >>>> >> resolve temporariamente. >> >>> >> >>>> >> >> >>> >> >>>> >> 2010/4/13 Guilherme Raymo Longo >> >>> >> >>>> >> <[email protected]>: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> Fui salvar as confs do Lilo e tive os seguintes problemas: >> >>> >> >>>> >> >> >>> >> >>>> >> warning: `/proc/partitions` does not exist, disk scan >> >>> >> >>>> >> bypassed >> >>> >> >>>> >> warning: Unable to determine video adapter in use by >> >>> >> >>>> >> present >> >>> >> >>>> >> System >> >>> >> >>>> >> Video adapter does not support VESA BIOS extensions needed >> >>> >> >>>> >> for >> >>> >> >>>> >> display 256 >> >>> >> >>>> >> color. >> >>> >> >>>> >> Boot loader will fall back to text only operation >> >>> >> >>>> >> >> >>> >> >>>> >> realmente devo ter feito algo de muito errado.. rs, nunca >> >>> >> >>>> >> tinha >> >>> >> >>>> >> recebido >> >>> >> >>>> >> essas msgs! >> >>> >> >>>> >> >> >>> >> >>>> >> 010/4/13 Guilherme Raymo Longo <[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> Como vocë disse Max, eu nunca cheguei a configurar ele >> >>> >> >>>> >> antes. >> >>> >> >>>> >> Por padráo o initrd é usado ou náo? Pq se náo for, eu tb >> >>> >> >>>> >> náo >> >>> >> >>>> >> utilizava >> >>> >> >>>> >> ele. >> >>> >> >>>> >> >> >>> >> >>>> >> Vou ler o readme agora. >> >>> >> >>>> >> >> >>> >> >>>> >> Se nao der certo vou fazer o download do kernel e >> >>> >> >>>> >> recompila-lo. >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> On Tue, Apr 13, 2010 at 11:50 AM, max <[email protected]> >> >>> >> >>>> >> wrote: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> O initrd serve pra carregar módulos importantes antes do >> >>> >> >>>> >> sistema >> >>> >> >>>> >> propriamente dito, o /boot/README.initrd explica bem pra >> >>> >> >>>> >> que >> >>> >> >>>> >> serve >> >>> >> e >> >>> >> >>>> >> como criar um. >> >>> >> >>>> >> >> >>> >> >>>> >> On Tue, Apr 13, 2010 at 11:45 AM, Guilherme Raymo Longo >> >>> >> >>>> >> <[email protected]> wrote: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> Pois [é... vi em alguns post sobre o initrd. >> >>> >> >>>> >> É nescessario recrialo? >> >>> >> >>>> >> >> >>> >> >>>> >> Náo achei exatamente a esplicacao de como fazer, mas vi que >> >>> >> >>>> >> em >> >>> >> alguns >> >>> >> >>>> >> casos >> >>> >> >>>> >> era nescessario. >> >>> >> >>>> >> >> >>> >> >>>> >> 2010/4/13 Yucatan "Kenjiro" Costa <[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> Ou só ficou faltando ele recriar o initrd né ;) >> >>> >> >>>> >> Kenjiro >> >>> >> >>>> >> >> >>> >> >>>> >> -- >> >>> >> >>>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> >> http://www.slackwarebrasil.org/ >> >>> >> >>>> >> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >> >>> >> >>>> >> Antes de perguntar: >> >>> >> >>>> >> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >> >>> >> >>>> >> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> -- >> >>> >> >>>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> >> http://www.slackwarebrasil.org/ >> >>> >> >>>> >> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >> >>> >> >>>> >> Antes de perguntar: >> >>> >> >>>> >> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >> >>> >> >>>> >> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> -- >> >>> >> >>>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> >> http://www.slackwarebrasil.org/ >> >>> >> >>>> >> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >> >>> >> >>>> >> Antes de perguntar: >> >>> >> >>>> >> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >> >>> >> >>>> >> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> To unsubscribe, reply using "remove me" as the subject. >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> -- >> >>> >> >>>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> >> http://www.slackwarebrasil.org/ >> >>> >> >>>> >> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >> >>> >> >>>> >> Antes de perguntar: >> >>> >> >>>> >> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >> >>> >> >>>> >> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> -- >> >>> >> >>>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> >> http://www.slackwarebrasil.org/ >> >>> >> >>>> >> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >> >>> >> >>>> >> Antes de perguntar: >> >>> >> >>>> >> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >> >>> >> >>>> >> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >> >>> >> >>>> >> >> >>> >> >>>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> > >> >>> >> >>>> > -- >> >>> >> >>>> > GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> > http://www.slackwarebrasil.org/ >> >>> >> >>>> > http://groups.google.com/group/slack-users-br >> >>> >> >>>> > >> >>> >> >>>> > Antes de perguntar: >> >>> >> >>>> > http://www.istf.com.br/perguntas/ >> >>> >> >>>> > >> >>> >> >>>> > Para sair da lista envie um e-mail para: >> >>> >> >>>> > >> >>> >> >>>> > >> >>> >> >>>> > [email protected]<slack-users-br%[email protected]> >> >>> >> >>>> >> >>> >> >>>> >> >>> >> >>>> >> >>> >> >>>> -- >> >>> >> >>>> “Nos mesmos pagamos por todas essas coisas, então deus, >> >>> >> >>>> obrigado >> >>> >> >>>> por >> >>> >> >>>> nada” >> >>> >> >>>> Bart Simpson >> >>> >> >>>> >> >>> >> >>>> -- >> >>> >> >>>> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>>> http://www.slackwarebrasil.org/ >> >>> >> >>>> http://groups.google.com/group/slack-users-br >> >>> >> >>>> >> >>> >> >>>> Antes de perguntar: >> >>> >> >>>> http://www.istf.com.br/perguntas/ >> >>> >> >>>> >> >>> >> >>>> Para sair da lista envie um e-mail para: >> >>> >> >>>> >> >>> >> >>>> >> >>> >> >>>> [email protected]<slack-users-br%[email protected]> >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> -- >> >>> >> >>> http://www.pquilinux.org >> >>> >> >>> segurança e liberdade no seu desktop >> >>> >> >>> >> >>> >> >>> -- >> >>> >> >>> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >>> http://www.slackwarebrasil.org/ >> >>> >> >>> http://groups.google.com/group/slack-users-br >> >>> >> >>> >> >>> >> >>> Antes de perguntar: >> >>> >> >>> http://www.istf.com.br/perguntas/ >> >>> >> >>> >> >>> >> >>> Para sair da lista envie um e-mail para: >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> [email protected]<slack-users-br%[email protected]> >> >>> >> >> >> >>> >> >> -- >> >>> >> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> >> http://www.slackwarebrasil.org/ >> >>> >> >> http://groups.google.com/group/slack-users-br >> >>> >> >> >> >>> >> >> Antes de perguntar: >> >>> >> >> http://www.istf.com.br/perguntas/ >> >>> >> >> >> >>> >> >> Para sair da lista envie um e-mail para: >> >>> >> >> >> >>> >> >> >> >>> >> >> [email protected]<slack-users-br%[email protected]> >> >>> >> > >> >>> >> > >> >>> >> > -- >> >>> >> > K33p 17 s1mpl3 stup1d >> >>> >> > >> >>> >> > -- >> >>> >> > GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> > http://www.slackwarebrasil.org/ >> >>> >> > http://groups.google.com/group/slack-users-br >> >>> >> > >> >>> >> > Antes de perguntar: >> >>> >> > http://www.istf.com.br/perguntas/ >> >>> >> > >> >>> >> > Para sair da lista envie um e-mail para: >> >>> >> > >> >>> >> > >> >>> >> > [email protected]<slack-users-br%[email protected]> >> >>> >> >> >>> >> -- >> >>> >> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> >> http://www.slackwarebrasil.org/ >> >>> >> http://groups.google.com/group/slack-users-br >> >>> >> >> >>> >> Antes de perguntar: >> >>> >> http://www.istf.com.br/perguntas/ >> >>> >> >> >>> >> Para sair da lista envie um e-mail para: >> >>> >> >> >>> >> >> >>> >> [email protected]<slack-users-br%[email protected]> >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > K33p 17 s1mpl3 stup1d >> >>> > >> >>> > -- >> >>> > GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> > http://www.slackwarebrasil.org/ >> >>> > http://groups.google.com/group/slack-users-br >> >>> > >> >>> > Antes de perguntar: >> >>> > http://www.istf.com.br/perguntas/ >> >>> > >> >>> > Para sair da lista envie um e-mail para: >> >>> > [email protected] >> >>> >> >>> -- >> >>> GUS-BR - Grupo de Usuários de Slackware Brasil >> >>> http://www.slackwarebrasil.org/ >> >>> http://groups.google.com/group/slack-users-br >> >>> >> >>> Antes de perguntar: >> >>> http://www.istf.com.br/perguntas/ >> >>> >> >>> Para sair da lista envie um e-mail para: >> >>> [email protected] >> > >> > -- >> > GUS-BR - Grupo de Usuários de Slackware Brasil >> > http://www.slackwarebrasil.org/ >> > http://groups.google.com/group/slack-users-br >> > >> > Antes de perguntar: >> > http://www.istf.com.br/perguntas/ >> > >> > Para sair da lista envie um e-mail para: >> > [email protected] >> >> kernel 2.6.17????? root=/dev/ram0???? >> Que loucura eh essa? >> >> -- >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >> necropresto - Slackware User << >> >> [email protected] << >> >> [email protected] << >> >> -- >> GUS-BR - Grupo de Usuários de Slackware Brasil >> http://www.slackwarebrasil.org/ >> http://groups.google.com/group/slack-users-br >> >> Antes de perguntar: >> http://www.istf.com.br/perguntas/ >> >> Para sair da lista envie um e-mail para: >> [email protected] > > -- > GUS-BR - Grupo de Usuários de Slackware Brasil > http://www.slackwarebrasil.org/ > http://groups.google.com/group/slack-users-br > > Antes de perguntar: > http://www.istf.com.br/perguntas/ > > Para sair da lista envie um e-mail para: > [email protected]
vc executou isso como comando??? image = /boot/vmlinuz-2.6.29.6 label = Linux root = /dev/sda2 read-only -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> necropresto - Slackware User << >> [email protected] << >> [email protected] << -- GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.istf.com.br/perguntas/ Para sair da lista envie um e-mail para: [email protected]
