ok.. uma duvida.. vc já tentou montar ele com o seguinte comando ou algo similar? # mount /dev/sda1 /mnt
On Wed, Jul 2, 2008 at 3:46 PM, printfroberto <[EMAIL PROTECTED]> wrote: > > > lsmod > Module Size Used by > smbfs 58744 2 > sg 26384 0 > vmnet 32180 9 > vmmon 1818508 6 > snd_seq_dummy 2820 0 > snd_seq_oss 29056 0 > snd_seq_midi_event 6272 1 snd_seq_oss > snd_seq 46800 5 > snd_seq_dummy,snd_seq_oss,snd_seq_midi_event > snd_seq_device 6540 3 snd_seq_dummy,snd_seq_oss,snd_seq > snd_pcm_oss 36896 0 > snd_mixer_oss 13824 2 snd_pcm_oss > ipv6 232420 14 > xt_limit 2304 2 > xt_tcpudp 3072 2 > ipt_MASQUERADE 2816 1 > xt_state 2048 2 > iptable_mangle 2304 0 > iptable_nat 6020 1 > nf_nat 15788 2 ipt_MASQUERADE,iptable_nat > nf_conntrack_ipv4 13192 4 iptable_nat > nf_conntrack 49728 5 > ipt_MASQUERADE,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 > iptable_filter 2432 1 > ip_tables 10316 3 > iptable_mangle,iptable_nat,iptable_filter > x_tables 11396 6 > xt_limit,xt_tcpudp,ipt_MASQUERADE,xt_state,iptable_nat,ip_tables > pcmcia 32428 0 > pcmcia_core 32532 1 pcmcia > pcspkr 2432 0 > psmouse 36240 0 > evdev 8704 3 > snd_hda_intel 278428 2 > snd_pcm 67844 2 snd_pcm_oss,snd_hda_intel > thermal 12828 0 > snd_timer 18564 2 snd_seq,snd_pcm > iTCO_wdt 10276 0 > button 6288 0 > snd 43236 10 > snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer > processor 28864 1 thermal > intel_agp 21652 1 > serio_raw 5252 0 > r8169 26372 0 > iTCO_vendor_support 3204 1 iTCO_wdt > agpgart 27208 2 intel_agp > e1000 118720 0 > soundcore 5856 2 snd > snd_page_alloc 7688 2 snd_hda_intel,snd_pcm > i2c_i801 7952 0 > > ============================================================================================= > > > On Jul 2, 12:37 am, "Sergio Luis" <[EMAIL PROTECTED]> wrote: >> certo, ele reconheceu como sda1, já é o primeiro passo. >> manda agora a saída do comando lsmod >> >> On Mon, Jun 30, 2008 at 9:35 AM, printfroberto >> >> >> >> <[EMAIL PROTECTED]> wrote: >> >> > Segue: >> >> > Sem dispositivo >> >> > root $ cat /proc/partitions >> > major minor #blocks name >> >> > 3 0 40146624 hda >> > 3 1 248976 hda1 >> > 3 2 835380 hda2 >> > 3 3 39062047 hda3 >> >> > Com pen drive mountado >> >> > root $ cat /proc/partitions >> > major minor #blocks name >> >> > 3 0 40146624 hda >> > 3 1 248976 hda1 >> > 3 2 835380 hda2 >> > 3 3 39062047 hda3 >> > 8 0 1006592 sda >> > 8 1 1006550 sda1 >> >> > Veleu!!!!!! >> >> > Att, >> >> > Printfroberto >> >> > On Jun 29, 12:53 am, "Sergio Luis" <[EMAIL PROTECTED]> wrote: >> >> cola aqui o conteudo do /proc/partitions >> >> >> On Wed, Jun 25, 2008 at 2:33 PM, printfroberto >> >> >> <[EMAIL PROTECTED]> wrote: >> >> >> > Boa tarde, uso o slack 12.1 com VMware Server 1.0.6 ambos >> >> > funcionando perfeitamente. >> >> >> > Estou apanhando para fazer funcionar o pen drive com o VM, a opção >> >> > de >> >> > "usb controller" no VM esta habilitada >> >> >> > O fstab do slack esta desta forma: >> >> >> > "none----/proc/bus/usb------usbfs------- >> >> > devgid=10,devmode=664---0-----0" >> >> >> > Como no linux um pen drive e reconhecido como um dispositivo SCSI >> >> > habilitei no VM a opção: >> >> >> > "generic scsi" e configurei o device "/dev/sda1" que é a maneira >> >> > que o meu slack reconhece o pen drive. >> >> >> > Mais nada funciona!!!! >> >> >> > Se alguem ja fez essa conf e puder ajudar agradeço >> >> >> > Valeu!!!! >> >> >> -- >> >> Sergio >> >> -- >> Sergio > > > > -- Sergio --~--~---------~--~----~------------~-------~--~----~ GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br -~----------~----~----~----~------~----~------~--~---
