thinstation-portuguese Mailing List for Thinstation
Brought to you by:
doncuppjr
You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(17) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(1) |
Feb
(2) |
Mar
(10) |
Apr
(10) |
May
(12) |
Jun
(9) |
Jul
(25) |
Aug
(11) |
Sep
(2) |
Oct
(6) |
Nov
(4) |
Dec
(3) |
2011 |
Jan
(1) |
Feb
(49) |
Mar
(1) |
Apr
(5) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2012 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Marinaldo R. <mar...@gm...> - 2015-12-14 16:37:55
|
estou com dificuldades para instalar impressora, usb, paralela e de rede. |
From: Luís T. <ta...@ta...> - 2013-10-07 13:41:45
|
Olá, pessoal! Sou novo na lista e em thinstation. Clonei o repositório git da versão 5.1 e tentei gerar minha própria imagem, mas sempre trava no boot. Logo, pensei em tentar uma imagem live prebuilt, mas não consigo encontrar para a versão 5.x. Existem imagens live prontas para essa versão? Aproveitando: existe algum tutorial detalhado (passo-a-passo) para criação de minha própria imagem? Obrigado! Luís Talora |
From: Danilo - I. do C. <da...@im...> - 2013-03-01 07:04:09
|
Pessoal, estou tentando montar um ambiente 2008 server r2 + Thinstation Bom configureis meu DHCP, fiz a imagem com as configurações, instalei o FTPD, direcionei o diretório onde esta a imagem. Configurei na estação para dar boot via pxe, a estação recebe o ip do DHCP, mas fica com o erro abaixo PCi_init: no BIOS32 detected Proibing isa nic.... <sleep> PCi_init: no BIOS32 detected Proibing pci nic.... <sleep> Alguém sabe o que pode ser? Grato Danilo Imperio do Computador 011-27713995 <mailto:da...@im...> da...@im... <mailto:da...@lo...> da...@lo... |
From: Danilo - I. do C. <da...@im...> - 2013-02-27 16:38:02
|
Olá Pessoal, sou novo na lista e me desculpe se isso já foi questionado. Bom estou com um ambiente 2008 server r2 e preciso transformar as estações em terminal burro, tentei fazer a imagem do thinstation e dar boot por ele mas não tive êxito. Alguém tem algum tutorial ? Grato Danilo Imperio do Computador 011-27713995 <mailto:da...@im...> da...@im... <mailto:da...@lo...> da...@lo... |
From: Joao P. <joa...@li...> - 2012-02-07 17:26:50
|
Boa tarde a todos ! Preciso da ajuda de vcs ... deve ser bem facil de resolver: Tenho um servidor TS 2008 R2 e 1 ThinStation no cliente. Preciso fazer funcionar a matricial e a laser no cliente ... lembrando que as impressoras estão fisicamente no Thinclient. Matricial: LX 300 + IILaser: Samsung ML-1860 A laser consegui configurar adicionando no Windows Server uma nova impressora por uma porta TCP/IP. E a matricial como fazer ? Desde já agradeço a todos. |
From: Ezequiel G. <eze...@be...> - 2012-02-03 13:33:07
|
Bom dia, Eu peguei a imagem pronta do site, pois não sei quais pacotes marcar para montar a minha personalizada. Se eu entrar na montagem e ir avançando sem mudar nada, ele vai puxar tudo que tem na pré-montada?? Como você disse para remover o pacote, eu terei que montar uma imagem personalizada sem este pacote, certo?? Grato, Ezequiel From: Fernando Ulisses dos Santos Sent: Wednesday, December 14, 2011 2:37 PM To: Ezequiel Gonzaga Subject: Re: [Thinstation-portuguese] Tecla /? não funciona Retira o pacote freerdp do teu build e coloca o layout de teclado pt_br. Fernando Ulisses dos Santos Blue Solutions - Soluções em TI 19-3321-9068 / 19-3551-3898 Em 14-12-2011 10:49, Ezequiel Gonzaga escreveu: Bom dia, TEm alguma forma de fazer a tecla “/?” funcionar?? Grato, Ezequiel ------------------------------------------------------------------------------ Cloud Computing - Latest Buzzword or a Glimpse of the Future? This paper surveys cloud computing today: What are the benefits? Why are businesses embracing it? What are its payoffs and pitfalls? http://www.accelacomm.com/jaw/sdnl/114/51425149/ _______________________________________________ Thinstation-portuguese mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese |
From: FellipeMAX <fel...@gm...> - 2012-01-26 13:28:42
|
Prezados, preciso instalar o thinstation em alguns modelos de thinclient com wireless e sem. teriam algum procedimento documentado de instalação e configuração? usarei o citrix. George Fellipe |
From: Joao P. <joa...@li...> - 2012-01-26 13:25:22
|
Bom dia a todos ! Resolvido meu problema de novato ! rs Exatamente como o Oliveiros me passou... Agradeço a toda comunidade pela ajuda. Obrigado a todos ! Joao Paulo. |
From: Joao P. <joa...@li...> - 2012-01-25 13:16:45
|
Bom dia a todos ! Sou novato aqui no forum e tambem no mundo linux ! Estou iniciando um projeto com o Thinstation + TS Windows Server 2008 R2. Tenho 3 terminais com o Thinstation ... mas tenho varias dúvidas de novato: Como configuro uma impressora matricial (lx-300) na LPT onboard do terminal ? Como configuro uma impressora laser (hp p1005) na usb no terminal ? Como utilizar pendrive no terminal ? Todos esse dispositivos precisam ser utilizados do terminal ... eu não tenho ideia de como posso fazer isso. oO Ja revirei os forum e não achei nada. Ja configurei o acesso ao TS normal ... não tive nenhum problema. Estou usando a versão 2.2.2h do site http://www.thinstation.net/TSoM/. Boot por CD. Se alguma alma caridosa poder me ajudar ... Desde já muito obrigado. |
From: Ezequiel G. <eze...@be...> - 2011-12-14 13:09:06
|
Bom dia, TEm alguma forma de fazer a tecla “/?” funcionar?? Grato, Ezequiel |
From: Daian C. <da...@op...> - 2011-05-25 12:00:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bom dia Dimitri, Em 24-05-2011 08:14, Dimitri Dittrich escreveu: > Bom dia senhores(a)! > Alguém poderia me informar qual a função BÁSICA destes arquivos de PXE > booting: Cada um tem uma funcao, vou tentar resumir ok > build.conf.network Este arquivo trata de configuracoes apos a inicializacao do kernel e da imagem initrd > initrd Esta eh uma imagem do raiz do sistema basico, no caso do thinstation, esta imagem tem o "/" . > pxelinux.0 Este arquivo eh um binario que eh fornecido para clientes PXE , para os clientes da rede iniciarem a busca pelo tftp > vmlinux Esta eh a imagem do kernel > default (o qual, por padrão, deve ser colocado em um diretório chamado > pxelinux.cfg) Este arquivo eh a configuracao que eh lida apos o cliente pegar o arquivo pxelinux.0, diz qual o kernel, initrd ou opcoes especiais que a maquina deve iniciar, deve ficar neste sub-diretorio. > > > O build.conf.network fica com as configurações que podem ser alteradas.... > mas e os outros 4 arquivos... precisaria saber qual mais ou menos é a função > de cada um dentro dessa estrutura... Se alguem souber fico agradecido. > > o build.conf eh o arquivo que eh verificado antes de iniciarem os scripts de criacao do ambiente que sera disponibilizado para os clientes, no caso, as opcoes que voce adicionar nele, serao adicionadas tanto no vmlinuz quanto no initrd. []s > > Muito obrigado. > Atenciosamente, > > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > > > > _______________________________________________ > Thinstation-portuguese mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese - -- ================ **Daian Conrad** E-mail: da...@op... * Suporte e Implantação * OpenS Tecnologia - OpenS Team (DaCoD) +55 48 3954 8000 Linux user: #248912 == PGP/GPG: 0x7E25E948 http://www.opens.com.br Faça parte da comunidade SNEP Livre __>> http://www.sneplivre.com.br -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJN3PASAAoJEKPh7Uh+JelI5lMH/jJgQcFQbl2NeVKtluVjSiqp CRK73mKA9RaCKiFGFPCfrVPWQ4xIH4fkIlYbRnJQYzbRUggdoz7pB42St9w9Uq2T cWBXXQrjMBrJXk3yLvQNod6Ge97Fr6Ya0HmeYT5MmXm8dRCMyKRb5zCb/sbRxScm PXcK/2Po/xG0PmgV0nGWRmfads5zRKOADBr3pkFBzhY6U8IVTIV/j68ECnUHuibU V+n8FUJuPryNgFCFjy6PxpHvta138lDBRn83T3AAkEEOlGFYW1zhbRPRtykKsTT7 ZMHwGVPvQRPFw/2Vtreui0HdRJPf+Pb2dWoG0dLX12o24MZxmtSMmVl56IiyWSY= =7c/6 -----END PGP SIGNATURE----- |
From: Dimitri D. <dit...@gm...> - 2011-05-24 11:14:34
|
Bom dia senhores(a)! Alguém poderia me informar qual a função BÁSICA destes arquivos de PXE booting: build.conf.network initrd pxelinux.0 vmlinux default (o qual, por padrão, deve ser colocado em um diretório chamado pxelinux.cfg) O build.conf.network fica com as configurações que podem ser alteradas.... mas e os outros 4 arquivos... precisaria saber qual mais ou menos é a função de cada um dentro dessa estrutura... Se alguem souber fico agradecido. Muito obrigado. Atenciosamente, -- Dimitri Dittrich dit...@gm... |
From: Fernando U. d. S. <fer...@bl...> - 2011-05-20 13:08:28
|
Dimitri, No teu servidor TFTP, cria um arquivo chamado thinstation.conf.network com a configuração que você precisa, basicamente: SESSION_0_TITLE="Terminal Server" SESSION_0_TYPE=rdesktop SESSION_0_RDESKTOP_SERVER=192.168.1.1 SESSION_0_RDESKTOP_OPTIONS="-z -a 16 -d DOMINIO -u ''" SESSION_0_AUTOSTART=On RECONNECT_PROMPT=On Fernando Ulisses dos Santos Blue Solutions - Soluções em TI 19-3321-9068 / 19-3551-3898 Em 18-05-2011 23:47, Dimitri Dittrich escreveu: > Boa noite !!! > > Implementei o Thinstation PXE booting com Windows server 2003. Gostei > muito do Thinstation e resolvi efetuar o boot PXE utilizando > Thinstation... Porém, estou com um probleminha: > > Já pesquisei muito mas não consegui resolver este impecílho.. quem > sabe você(s) possa(m) me ajudar... > > Preciso saber como fazer para o RDESKTOP inicializar no IP do meu > servidor automaticamente na inicialização do Thinstation... Pois > sempre que ele inicializa cai no desktop.. e tenho que abrir o > rdesktop e setar o ip do servidor.. e isso não é viável para os > usários finais.. > > > Deve ser algo simples.. mas não estou dando jeito de resolver... > > > > Eu efetuei a configuração num server 2003, igualzinho exemplifica este > artigo: > http://dicasavancadas.blogspot.com/2010/09/usando-o-thinstation-como-cliente-do.html > > > > > > Ficaria extremamente feliz se pudessem me ajudar neste problema... > > > > Desde ja agradeco... > -- > Dimitri Dittrich > dit...@gm... <mailto:dit...@gm...> > > > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > > > _______________________________________________ > Thinstation-portuguese mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese |
From: Badoo <no...@ba...> - 2011-05-19 05:43:03
|
Leia as mensagens deixadas por Rogerio Sampaio antes que sejam deletadas! Para ler sua mensagem, siga este link: http://us1.badoo.com/01144751286/in/uAkCxyVjGr0/?lang_id=61 Mais gente que espera pacientemente por você: Dudu (São Paulo, Brasil) Dani (São Paulo, Brasil) Jackeline (São Paulo, Brasil) http://us1.badoo.com/01144751286/in/uAkCxyVjGr0/?lang_id=61 Se os links desta mensagem não funcionarem, copie e cole-os na barra de endereços do seu browser. Este email e parte do procedimento de entrega de mensagens enviadas por Rogerio Sampaio. Caso tenha recebido este email por engano, apenas ignore. Em breve esta mensagem será removida do sistema. Divirta-se! A Equipe Badoo Você recebeu este email, porque um membro do Badoo deixou uma mensagem para você no Badoo. Esta é uma mensagem de somente envio. Respostas a esta mensagem não são monitoradas ou respondidas. Se você não quer receber mais mensagens do Badoo, por favor nos notifique: http://us1.badoo.com/impersonation.phtml?lang_id=61&mail_code=65&email=thinstation-portuguese%40lists.sourceforge.net&secret=&invite_id=680273&user_id=1144751286 |
From: Dimitri D. <dit...@gm...> - 2011-05-19 02:47:49
|
Boa noite !!! Implementei o Thinstation PXE booting com Windows server 2003. Gostei muito do Thinstation e resolvi efetuar o boot PXE utilizando Thinstation... Porém, estou com um probleminha: Já pesquisei muito mas não consegui resolver este impecílho.. quem sabe você(s) possa(m) me ajudar... Preciso saber como fazer para o RDESKTOP inicializar no IP do meu servidor automaticamente na inicialização do Thinstation... Pois sempre que ele inicializa cai no desktop.. e tenho que abrir o rdesktop e setar o ip do servidor.. e isso não é viável para os usários finais.. Deve ser algo simples.. mas não estou dando jeito de resolver... Eu efetuei a configuração num server 2003, igualzinho exemplifica este artigo: http://dicasavancadas.blogspot.com/2010/09/usando-o-thinstation-como-cliente-do.html Ficaria extremamente feliz se pudessem me ajudar neste problema... Desde ja agradeco... -- Dimitri Dittrich dit...@gm... |
From: Badoo <no...@ba...> - 2011-05-11 00:56:00
|
Rogerio Sampaio deixou uma mensagem para você... O remetente e o conteúdo serão mostrados apenas para você e poderá excluir a qualquer tempo. Podes responder instantaneamente, usando o sistema de troca de mensagsns. Para descobrir o que lhe foi escrito, apenas siga este link: http://us1.badoo.com/01144751286/in/uAkCxyVjGr0/?lang_id=61 Mais gente que espera pacientemente por você: Superman (São Paulo, Brasil) Dani (São Paulo, Brasil) Fernanda (São Paulo, Brasil) http://us1.badoo.com/01144751286/in/uAkCxyVjGr0/?lang_id=61 Se os links desta mensagem não funcionam, copie e cole-os na barra de endereços do seu navegador. Este email é uma parte da entrega da mensagem enviada por Rogerio Sampaio no sistema. Se você recebeu este email por engano, por favor apenas ignore-o. Após um tempo a mensagem será removida do sistema. Divirta-se! A Equipe Badoo Você recebeu este email, porque um membro do Badoo deixou uma mensagem para você no Badoo. Esta é uma mensagem de somente envio. Respostas a esta mensagem não são monitoradas ou respondidas. Se você não quer receber mais mensagens do Badoo, por favor nos notifique: http://us1.badoo.com/impersonation.phtml?lang_id=61&mail_code=63&email=thinstation-portuguese%40lists.sourceforge.net&secret=&invite_id=680273&user_id=1144751286 |
From: Fernando U. d. S. <fer...@bl...> - 2011-04-26 18:09:13
|
Daian, obrigado pelas dicas. Consegui resolver, depois de tentar quase todas as versões de 2.1. pra cima. Percebi que começou a dar defeito depois que o pacote "freerdp" passou a fazer parte do build.conf padrão. Ele era o culpado de tudo. Então, fica a dica, pra consertar o problema das teclas "/" e "?" das versões 2.2.2f e 2.2.2g, comente a linha no build.conf: # package freerdp Estou com uma imagem 2.2.2g estável e funcional. Fernando Ulisses dos Santos Blue Solutions - Soluções em TI 19-3321-9068 / 19-3551-3898 Em 25-04-2011 09:59, Daian Conrad escreveu: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bom dia Fernando, > > Ja tive problemas com mapas de teclado ABNT2, porem , o que > corrigiu(assim acredito :-D ), foi adicionar na configuração da sessão > alguns itens específicos, conforme exemplo abaixo . . . > > > KEYBOARD_MAP=pt_br > USB_ENABLED=On > RECONNECT_PROMPT=On > SCREEN_RESOLUTION="1024x768 | 800x600 | 640x480 | *" > MOUSE_RESOLUTION=100 > MOUSE_PROTOCOL="Microsoft" > MOUSE_DEVICE="/dev/ttyS0" > > > Boa sorte ;-) > > []s > > > Em 23-04-2011 19:41, Fernando escreveu: >> Boa noite!! >> >> Estou fazendo alguns testes com o Thinstation a várias semanas, estou >> com a versão 2.2.2g (já testei também na versão 2.2.2f), mas não consigo >> funcionar corretamente um teclado ABNT2. Tenho compilado minha própria >> imagem. >> >> Quase todas as teclas funcionam normalmente, exceto a tecla com a barra >> "/" e o interrogação "?". No console em modo texto até funciona, mas me >> interessaria numa sessão Linux ou Rdesktop. O teste mais básico que >> tenho feito é iniciar uma sessão com o icewm, abrir algum programa e >> tentar digitar, tudo funciona, só falta essa tecla. >> >> Já procurei muito, esse problema era conhecido nas versões anteriores, >> mas foi corrigido em versões anteriores (versão 2.1beta5), apliquei >> diversos patches encontrados, mas nada de funcionar. >> >> Vocês conseguiram funcionar com sucesso essa tecla? Tem alguma >> configuração especial? Talvez no build.conf? Ou estão usando outra versão? >> >> No build.conf estou usando: >> package keymaps-pt_br >> >> __ >> Fernando >> >> >> ------------------------------------------------------------------------------ >> Fulfilling the Lean Software Promise >> Lean software platforms are now widely adopted and the benefits have been >> demonstrated beyond question. Learn why your peers are replacing JEE >> containers with lightweight application servers - and what you can gain >> from the move. http://p.sf.net/sfu/vmware-sfemails >> _______________________________________________ >> Thinstation-portuguese mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >> > - -- > ================ > **Daian Conrad** > E-mail: da...@op... > * Suporte e Implantação > * OpenS Tecnologia - OpenS Team (DaCoD) > +55 48 3954 8000 > Linux user: #248912 == PGP/GPG: 0x7E25E948 > > http://www.opens.com.br > Faça parte da comunidade SNEP Livre > __>> http://www.sneplivre.com.br > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJNtXAxAAoJEKPh7Uh+JelIXsAH/A6RNFAphreMfRBS1rg0rjHS > JezyXHNpfwbrOYZ1y7ZVCroJh/Am8yJiqVa1G+jCbAnlgjxTRCQH7z6vvRNiDvG4 > 7/CBlNGN6ZOGGwupcoZfi97oPzGNoKpE5tPEKYX6hfsKR/nXbNuxhUaRmdX85Qa5 > etRwEsqoYhOkR6JaaIx8z3edJ/3RIK9yVrZaFIrf0TDCd0ng5Vvort3l0jBo+/+/ > HBGXVOxNCsJdnxpFjZ8pduI6nx9QV+DPdHgNkipUb+0sIVyg4cK4M/ZUkEcjg87M > D+TYbCdogmfI4wzmdgbc3jRXBu10AVAII3VPoVN7iOD9KVIC+rVSWbFLMz+vRzU= > =+iBm > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Fulfilling the Lean Software Promise > Lean software platforms are now widely adopted and the benefits have been > demonstrated beyond question. Learn why your peers are replacing JEE > containers with lightweight application servers - and what you can gain > from the move. http://p.sf.net/sfu/vmware-sfemails > _______________________________________________ > Thinstation-portuguese mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese |
From: Daian C. <da...@op...> - 2011-04-25 13:15:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bom dia Fernando, Ja tive problemas com mapas de teclado ABNT2, porem , o que corrigiu(assim acredito :-D ), foi adicionar na configuração da sessão alguns itens específicos, conforme exemplo abaixo . . . KEYBOARD_MAP=pt_br USB_ENABLED=On RECONNECT_PROMPT=On SCREEN_RESOLUTION="1024x768 | 800x600 | 640x480 | *" MOUSE_RESOLUTION=100 MOUSE_PROTOCOL="Microsoft" MOUSE_DEVICE="/dev/ttyS0" Boa sorte ;-) []s Em 23-04-2011 19:41, Fernando escreveu: > Boa noite!! > > Estou fazendo alguns testes com o Thinstation a várias semanas, estou > com a versão 2.2.2g (já testei também na versão 2.2.2f), mas não consigo > funcionar corretamente um teclado ABNT2. Tenho compilado minha própria > imagem. > > Quase todas as teclas funcionam normalmente, exceto a tecla com a barra > "/" e o interrogação "?". No console em modo texto até funciona, mas me > interessaria numa sessão Linux ou Rdesktop. O teste mais básico que > tenho feito é iniciar uma sessão com o icewm, abrir algum programa e > tentar digitar, tudo funciona, só falta essa tecla. > > Já procurei muito, esse problema era conhecido nas versões anteriores, > mas foi corrigido em versões anteriores (versão 2.1beta5), apliquei > diversos patches encontrados, mas nada de funcionar. > > Vocês conseguiram funcionar com sucesso essa tecla? Tem alguma > configuração especial? Talvez no build.conf? Ou estão usando outra versão? > > No build.conf estou usando: > package keymaps-pt_br > > __ > Fernando > > > ------------------------------------------------------------------------------ > Fulfilling the Lean Software Promise > Lean software platforms are now widely adopted and the benefits have been > demonstrated beyond question. Learn why your peers are replacing JEE > containers with lightweight application servers - and what you can gain > from the move. http://p.sf.net/sfu/vmware-sfemails > _______________________________________________ > Thinstation-portuguese mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese > - -- ================ **Daian Conrad** E-mail: da...@op... * Suporte e Implantação * OpenS Tecnologia - OpenS Team (DaCoD) +55 48 3954 8000 Linux user: #248912 == PGP/GPG: 0x7E25E948 http://www.opens.com.br Faça parte da comunidade SNEP Livre __>> http://www.sneplivre.com.br -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNtXAxAAoJEKPh7Uh+JelIXsAH/A6RNFAphreMfRBS1rg0rjHS JezyXHNpfwbrOYZ1y7ZVCroJh/Am8yJiqVa1G+jCbAnlgjxTRCQH7z6vvRNiDvG4 7/CBlNGN6ZOGGwupcoZfi97oPzGNoKpE5tPEKYX6hfsKR/nXbNuxhUaRmdX85Qa5 etRwEsqoYhOkR6JaaIx8z3edJ/3RIK9yVrZaFIrf0TDCd0ng5Vvort3l0jBo+/+/ HBGXVOxNCsJdnxpFjZ8pduI6nx9QV+DPdHgNkipUb+0sIVyg4cK4M/ZUkEcjg87M D+TYbCdogmfI4wzmdgbc3jRXBu10AVAII3VPoVN7iOD9KVIC+rVSWbFLMz+vRzU= =+iBm -----END PGP SIGNATURE----- |
From: Fernando <fer...@gm...> - 2011-04-23 22:41:31
|
Boa noite!! Estou fazendo alguns testes com o Thinstation a várias semanas, estou com a versão 2.2.2g (já testei também na versão 2.2.2f), mas não consigo funcionar corretamente um teclado ABNT2. Tenho compilado minha própria imagem. Quase todas as teclas funcionam normalmente, exceto a tecla com a barra "/" e o interrogação "?". No console em modo texto até funciona, mas me interessaria numa sessão Linux ou Rdesktop. O teste mais básico que tenho feito é iniciar uma sessão com o icewm, abrir algum programa e tentar digitar, tudo funciona, só falta essa tecla. Já procurei muito, esse problema era conhecido nas versões anteriores, mas foi corrigido em versões anteriores (versão 2.1beta5), apliquei diversos patches encontrados, mas nada de funcionar. Vocês conseguiram funcionar com sucesso essa tecla? Tem alguma configuração especial? Talvez no build.conf? Ou estão usando outra versão? No build.conf estou usando: package keymaps-pt_br __ Fernando |
From: Haroldo F. <har...@ne...> - 2011-04-04 14:15:31
|
Bom Dia Existe a possibilidade de configurar o Thinstation 2.2 para funcionar em resolução 1600x900 ? Att -- Haroldo Franzin |
From: Luiz H. <lui...@ya...> - 2011-04-01 06:39:58
|
Estou pesquisando sobre o thinstation e encontrei um site que relatou alguns problemas, http://abdenego.ithub.com.br/tag/thinstation/, como irei precisar da maioria dos recursos que foram descritos, gostaria de saber os que estão disponíveis e quais não estão. Obrigado! |
From: Myke L. <cm...@gm...> - 2011-03-02 12:54:33
|
seguinte meu arquivo ficou da seguinte forma: KEYBOARD_MAP=pt_br DAILY_REBOOT=On RECONNECT_PROMPT=ON SCREEN=0 WORKSPACE=1 AUTOSTART=On ICONMODE=AUTO SESSION_0_TYPE=freerdp SESSION_0_AUTOSTART=ON SESSION_0_SCREEN=1 SESSION_0_FREERDP_SERVER=10.10.1.20 SESSION_0_FREERDP_OPTIONS="-d DOMINIO" ele carrega meu ts 2008 r2 normal com o dominio ja escolhido, mas não loga, fica travado na tela de bem vindo pra funcionar tenho que digitar DOMINIO\nome do usuario ai loga normalmente, ou seja dominio automatico não funciona.. e só consegui fazer funcionar satisfatóriamente com o FREERDP os demais rdesktop e rdesktopsvn sem chance. bem eu estava testando o boot pxe com uma vm com o vitualbox até chegar a esse resultado, fui testar em um thinclient e achou o dhcp começou a carregar os pacotes e qnd esta na tela do splash aperto f2 ele para com um erro dizendo q nao encontrou o dhcp que a rede não foi ativada algo do tipo.. seria isso mesmo o drive da rede q nao ta certo? Em 28 de fevereiro de 2011 14:29, Myke Lima <cm...@gm...> escreveu: > Sim ja tentei sem e com a opção -u mas não muda nada... > fica do mesmo jeito.. > > > > Em 28 de fevereiro de 2011 13:48, Daian Conrad <da...@op...>escreveu: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Tentou remover a opção -u ?? >> >> []s >> >> Em 28-02-2011 11:36, Myke Lima escreveu: >> > bom dia pessoal, >> > estou ainda apanhando aqui, meu thinstation.conf.buildtime esta da >> seguinte >> > forma: >> > >> > >> > KEYBOARD_MAP=pt_br >> > DAILY_REBOOT=On >> > RECONNECT_PROMPT=ON >> > SCREEN=0 >> > WORKSPACE=1 >> > AUTOSTART=On >> > ICONMODE=AUTO >> > SESSION_0_TYPE=freerdp >> > SESSION_0_AUTOSTART=ON >> > SESSION_0_SCREEN=1 >> > SESSION_0_FREERDP_SERVER=10.10.1.20 >> > SESSION_0_FREERDP_OPTIONS="-u ' ' -a 15 -d meudominio" >> > SCREEN_RESOLUTION="1024x768" >> > SCREEN_COLOR_DEPTH="15" >> > >> > >> > o que esta acontecendo é o seguinte, ele carrega o ts do 2008 mas sempre >> > tenho que digitar meudominio\ antes do nome do usuario pois ele carrega >> > direto nomedamaquina\root ja cai direto pra digitar a senha, alguem sabe >> > como alterar isso? quero apenas ter q digitar o usuario e senha. >> > >> > >> > >> > >> > >> > >> > >> > >> > > |
From: Myke L. <cm...@gm...> - 2011-02-28 17:29:46
|
Sim ja tentei sem e com a opção -u mas não muda nada... fica do mesmo jeito.. Em 28 de fevereiro de 2011 13:48, Daian Conrad <da...@op...>escreveu: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tentou remover a opção -u ?? > > []s > > Em 28-02-2011 11:36, Myke Lima escreveu: > > bom dia pessoal, > > estou ainda apanhando aqui, meu thinstation.conf.buildtime esta da > seguinte > > forma: > > > > > > KEYBOARD_MAP=pt_br > > DAILY_REBOOT=On > > RECONNECT_PROMPT=ON > > SCREEN=0 > > WORKSPACE=1 > > AUTOSTART=On > > ICONMODE=AUTO > > SESSION_0_TYPE=freerdp > > SESSION_0_AUTOSTART=ON > > SESSION_0_SCREEN=1 > > SESSION_0_FREERDP_SERVER=10.10.1.20 > > SESSION_0_FREERDP_OPTIONS="-u ' ' -a 15 -d meudominio" > > SCREEN_RESOLUTION="1024x768" > > SCREEN_COLOR_DEPTH="15" > > > > > > o que esta acontecendo é o seguinte, ele carrega o ts do 2008 mas sempre > > tenho que digitar meudominio\ antes do nome do usuario pois ele carrega > > direto nomedamaquina\root ja cai direto pra digitar a senha, alguem sabe > > como alterar isso? quero apenas ter q digitar o usuario e senha. > > > > > > > > > > > > > > > > > |
From: Daian C. <da...@op...> - 2011-02-28 16:45:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tentou remover a opção -u ?? []s Em 28-02-2011 11:36, Myke Lima escreveu: > bom dia pessoal, > estou ainda apanhando aqui, meu thinstation.conf.buildtime esta da seguinte > forma: > > > KEYBOARD_MAP=pt_br > DAILY_REBOOT=On > RECONNECT_PROMPT=ON > SCREEN=0 > WORKSPACE=1 > AUTOSTART=On > ICONMODE=AUTO > SESSION_0_TYPE=freerdp > SESSION_0_AUTOSTART=ON > SESSION_0_SCREEN=1 > SESSION_0_FREERDP_SERVER=10.10.1.20 > SESSION_0_FREERDP_OPTIONS="-u ' ' -a 15 -d meudominio" > SCREEN_RESOLUTION="1024x768" > SCREEN_COLOR_DEPTH="15" > > > o que esta acontecendo é o seguinte, ele carrega o ts do 2008 mas sempre > tenho que digitar meudominio\ antes do nome do usuario pois ele carrega > direto nomedamaquina\root ja cai direto pra digitar a senha, alguem sabe > como alterar isso? quero apenas ter q digitar o usuario e senha. > > > > > > > > > Em 26 de fevereiro de 2011 10:58, Myke Lima <cm...@gm...> escreveu: > >> só para esclarecer, formatei a maquina denovo configurei tudo do 0, >> >> gerei a imagem no site e joguei na pasta ai sim deu certo deu o boot, mas >> como estava em teste mandei logar numa maquina XP, agora vou fazer as >> mudanças necessárias para logar no ip do 2008 r2 >> >> >> >> até então deu tudo certo qualquer dúvida posto aqui novamente.. >> >> >> >> >> >> >> Em 25 de fevereiro de 2011 18:14, Daian Conrad <da...@op...>escreveu: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Estes logs servem sim ............ >>> vamos destrinchar um pouco :D >>> >>> >>> Esta é a sequencia que o cliente busca no server >>> >>> 10.1.1.164 <10.1.1.3> pxelinux.0 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/56424f58-0000-0000-0000-080027af0 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/01-08-00-27-af-01-a5 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A4 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A010 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A01 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/0 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/default >>> 10.1.1.164 <10.1.1.3> diag/vesamenu.c32 >>> 10.1.1.164 <10.1.1.3> pxelinux.cfg/default >>> 10.1.1.164 <10.1.1.3> ts_bg.jpg >>> 10.1.1.164 <10.1.1.3> vmlinuz >>> 10.1.1.164 <10.1.1.3> initrd >>> >>> >>> Aparentemente ele não esta passando do initrd, deve ter alguma coisa >>> ainda na sua imagem que não esta legal, não consegui ver o modelo dos >>> thinclients que esta usando, o link não abre :-( . . . pode ser tmb >>> algum parâmetro que esta configurado em "pxelinux.cfg/default" , outro >>> teste que pode fazer , é gerar uma imagem on-line e salvar o VMLINUZ e o >>> INITRD sobrescrevendo os atuais. >>> >>> Tlvz resolva seu problema com a imagem ;-) >>> >>> >>> Em 25-02-2011 14:23, Myke Lima escreveu: >>>> não sei se serve de alguma coisa mas procurei na net e dei esse comando >>> o >>>> resultado ta abaixo >>>> >>>> >>>> root@SRVDHCP:/etc# tcpdump port 69 -v >>>> >>>> tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 >>>> bytes >>>> 13:22:04.115738 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 60) >>>> 10.1.1.164.2001 > 10.1.1.3.tftp: 32 RRQ "pxelinux.0" octet blksize >>> 1432 >>>> 13:22:04.232202 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 107) >>>> 10.1.1.164.57089 > 10.1.1.3.tftp: 79 RRQ >>>> "pxelinux.cfg/56424f58-0000-0000-0000-080027af0" [|tftp] >>>> 13:22:04.238420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 91) >>>> 10.1.1.164.57090 > 10.1.1.3.tftp: 63 RRQ >>>> "pxelinux.cfg/01-08-00-27-af-01-a5" octet tsize >>>> 13:22:04.243420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 79) >>>> 10.1.1.164.57091 > 10.1.1.3.tftp: 51 RRQ "pxelinux.cfg/0A0101A4" >>> octet >>>> tsize 0 blksize 14 >>>> 13:22:04.248400 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 78) >>>> 10.1.1.164.57092 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/0A0101A" >>> octet >>>> tsize 0 blksize 140 >>>> 13:22:04.253273 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 77) >>>> 10.1.1.164.57093 > 10.1.1.3.tftp: 49 RRQ "pxelinux.cfg/0A0101" >>> octet >>>> tsize 0 blksize 1408 >>>> 13:22:04.258139 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 76) >>>> 10.1.1.164.57094 > 10.1.1.3.tftp: 48 RRQ "pxelinux.cfg/0A010" octet >>>> tsize 0 blksize 1408 >>>> 13:22:04.262880 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 75) >>>> 10.1.1.164.57095 > 10.1.1.3.tftp: 47 RRQ "pxelinux.cfg/0A01" octet >>>> tsize 0 blksize 1408 >>>> 13:22:04.267505 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 74) >>>> 10.1.1.164.57096 > 10.1.1.3.tftp: 46 RRQ "pxelinux.cfg/0A0" octet >>> tsize >>>> 0 blksize 1408 >>>> 13:22:04.272007 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 73) >>>> 10.1.1.164.57097 > 10.1.1.3.tftp: 45 RRQ "pxelinux.cfg/0A" octet >>> tsize >>>> 0 blksize 1408 >>>> 13:22:04.276514 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 72) >>>> 10.1.1.164.57098 > 10.1.1.3.tftp: 44 RRQ "pxelinux.cfg/0" octet >>> tsize 0 >>>> blksize 1408 >>>> 13:22:04.281526 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 78) >>>> 10.1.1.164.57099 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" >>> octet >>>> tsize 0 blksize 140 >>>> 13:22:04.293463 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 75) >>>> 10.1.1.164.57100 > 10.1.1.3.tftp: 47 RRQ "diag/vesamenu.c32" octet >>>> tsize 0 blksize 1408 >>>> 13:22:04.394604 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 78) >>>> 10.1.1.164.57101 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" >>> octet >>>> tsize 0 blksize 140 >>>> 13:22:04.460384 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 67) >>>> 10.1.1.164.57102 > 10.1.1.3.tftp: 39 RRQ "ts_bg.jpg" octet tsize 0 >>>> blksize 1408 >>>> 13:22:07.410224 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 65) >>>> 10.1.1.164.57103 > 10.1.1.3.tftp: 37 RRQ "vmlinuz" octet tsize 0 >>>> blksize 1408 >>>> 13:22:08.174756 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto >>> UDP >>>> (17), length 64) >>>> 10.1.1.164.57104 > 10.1.1.3.tftp: 36 RRQ "initrd" octet tsize 0 >>> blksize >>>> 1408 >>>> >>>> >>>> Em 25 de fevereiro de 2011 14:11, Myke Lima <cm...@gm...> >>> escreveu: >>>> >>>>> achei somente isso... não achei nada referente a tftp >>>>> >>>>> >>>>> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.167 (10.1.1.2) >>> from >>>>> 00:40:ca:a8:cc:84 via eth1: lease 10.1.1.167 unavailable. >>>>> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPNAK on 10.1.1.167 to >>> 00:40:ca:a8:cc:84 >>>>> via eth1 >>>>> Feb 25 13:05:30 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via >>> eth1 >>>>> Feb 25 13:05:31 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to >>> 08:00:27:af:01:a5 >>>>> via eth1 >>>>> Feb 25 13:05:33 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) >>> from >>>>> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >>>>> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via >>> eth1 >>>>> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to >>> 08:00:27:af:01:a5 >>>>> via eth1 >>>>> Feb 25 13:05:45 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) >>> from >>>>> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >>>>> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via >>> eth1 >>>>> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to >>> 08:00:27:af:01:a5 >>>>> via eth1 >>>>> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.164 (10.1.1.3) >>> from >>>>> 08:00:27:af:01:a5 via eth1 >>>>> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPACK on 10.1.1.164 to >>> 08:00:27:af:01:a5 >>>>> via eth1 >>>>> Feb 25 13:06:45 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via >>> eth1 >>>>> Feb 25 13:06:45 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.163 >>>>> valid. >>>>> Feb 25 13:06:45 SRVDHCP dhcpd: Abandoning IP address 10.1.1.163: >>> pinged >>>>> before offer >>>>> Feb 25 13:06:47 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) >>> from >>>>> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >>>>> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via >>> eth1 >>>>> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) >>> from >>>>> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >>>>> Feb 25 13:07:03 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.169 to >>> 00:40:ca:a8:d8:4c >>>>> via eth1 >>>>> Feb 25 13:07:09 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via >>> eth1 >>>>> Feb 25 13:07:09 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.168 >>>>> valid. >>>>> Feb 25 13:07:09 SRVDHCP dhcpd: Abandoning IP address 10.1.1.168: >>> pinged >>>>> before offer >>>>> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) >>> from >>>>> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >>>>> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to >>> 00:40:ca:a8:cf:f5 >>>>> via eth1 >>>>> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via >>> eth1 >>>>> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) >>> from >>>>> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >>>>> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to >>> 00:40:ca:a8:cf:f5 >>>>> via eth1 >>>>> Feb 25 13:07:28 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.165 to >>> 00:40:ca:a8:cf:f5 >>>>> via eth1 >>>>> root@SRVDHCP:/var/log# >>>>> >>>>> >>>>> >>>>> Em 25 de fevereiro de 2011 12:15, Daian Conrad <da...@op... >>>> escreveu: >>>>> >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA1 >>>>>> >>>>>> todos os logs, em LSB, ficam em /var/log/(syslog,daemon.log,messages) >>>>>> >>>>>> []s >>>>>> >>>>>> >>>>>> Em 25-02-2011 12:07, Myke Lima escreveu: >>>>>>> desculpe a ignorancia, mas onde ficam os logs do tftp? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Em 25 de fevereiro de 2011 11:02, Daian Conrad <da...@op... >>>>>>> escreveu: >>>>>>> >>>>>>> Myke, >>>>>>> >>>>>>> Voce consegue verificar nos logs do tftp alguma informação quando a >>>>>>> maquina cliente inicia ??? >>>>>>> >>>>>>> Tem alguma informação que ainda esta faltando, ficar simplesmente >>> parado >>>>>>> no boot, não explica muita coisa . . . >>>>>>> >>>>>>> Look inside the logs dude ;-) >>>>>>> >>>>>>> >>>>>>> []s >>>>>>> >>>>>>> >>>>>>> Em 25-02-2011 09:51, Myke Lima escreveu: >>>>>>>>>> alguém mais tem idéia do que pode estar acontecendo??? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Em 24 de fevereiro de 2011 15:26, Myke Lima <cm...@gm...> >>>>>>> escreveu: >>>>>>>>>> >>>>>>>>>>> alterei recriei a imagem e mesma coisa >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Em 24 de fevereiro de 2011 15:23, Daian Conrad < >>> da...@op... >>>>>>>>>> escreveu: >>>>>>>>>>> >>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>>>>> Hash: SHA1 >>>>>>>>>>>> >>>>>>>>>>>> pode ser sim, tem que estar igual >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Se esta diferente fui eu que errei :) >>>>>>>>>>>> >>>>>>>>>>>> []s >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Em 24-02-2011 14:41, Myke Lima escreveu: >>>>>>>>>>>>> fiz o procedimento mas esta do mesmo jeito fica parada no >>>>>>>>>>>> pinguinzinhu.... >>>>>>>>>>>>> >>>>>>>>>>>>> uma coisa q eu achei estranha e dei uma olhada no >>>>>>>>>>>> thinstation.conf.buildtime >>>>>>>>>>>>> >>>>>>>>>>>>> esta como sessao rdesktop e no build.conf esta seleciona o >>>>>> rdesktopsvn >>>>>>>>>>>>> >>>>>>>>>>>>> esta certo isso é a mesma coisa? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Em 24 de fevereiro de 2011 13:00, Myke Lima <cm...@gm... >>>> >>>>>>>>>>>> escreveu: >>>>>>>>>>>>> >>>>>>>>>>>>>> ok, vou testar e posto aqui a principio eu não sei qual a >>> placa >>>>>> de >>>>>>> rede >>>>>>>>>>>> e >>>>>>>>>>>>>> video, mas no servidor antigo de ltsp estava tudo como vesa >>> por >>>>>> isso >>>>>>>>>>>> ate >>>>>>>>>>>>>> deixei o vesa habilitado mas o modelo do thinclient é esse >>>>>>>>>>>>>> http://www.connec.com.br/site/p01b1.asp >>>>>>>>>>>>>> >>>>>>>>>>>>>> <http://www.connec.com.br/site/p01b1.asp> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Em 24 de fevereiro de 2011 11:56, Daian Conrad < >>>>>> da...@op... >>>>>>>>>>>>> escreveu: >>>>>>>>>>>>>> >>>>>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>>>>>>>> Hash: SHA1 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> è possivel que tenha algum problema na configuração da sua >>>>>> imagem de >>>>>>>>>>>>>>> boot(initrd), faltando algum modulo e coisas do tipo. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> os problemas com modulos são comuns em thinclient's muito >>> novos, >>>>>>> pois >>>>>>>>>>>>>>> ainda estão atualizando o core para versões de kernel mais >>> novos >>>>>> e >>>>>>>>>>>> etc. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Qual o modelo do thinclient ou maquina(rede e video) . . . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Por via das duvidas dei uma revisada nos seus arquivos e acho >>>>>> que >>>>>>>>>>>> seria >>>>>>>>>>>>>>> interessante testar o RDP com o rdesktop. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Deixei a principio prontosó copiar para a pasta , renomear e >>>>>>>>>>>>>>> compilar(./build) . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Em 24-02-2011 11:39, Myke Lima escreveu: >>>>>>>>>>>>>>>> Ele fica parado na tela toda preta com a seguinte mensagem: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Loading vmlinuz...................... >>>>>>>>>>>>>>>> Loading initrd..........ready >>>>>>>>>>>>>>>> Uncompressing Linux... Ok, booting the kernel. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> e não sai disso... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> sera que tem algo errado na minha imagem meu arquivo >>> build.conf >>>>>> ta >>>>>>>>>>>>>>> certo? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Em 24 de fevereiro de 2011 11:25, Daian Conrad < >>>>>> da...@op... >>>>>>>>>>>>>>>> escreveu: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Parece que ele não achou o kernel indicado (vmlinuz ou o >>>>>> initrd), >>>>>>> nos >>>>>>>>>>>>>>>> logs do tftp, não aparece o caminho ou arquivos que a >>> estação >>>>>> esta >>>>>>>>>>>>>>>> procurando ?? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Em 24-02-2011 08:54, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>> Bom dia, tenho alguma novidades.. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> consegui fazer o boot mas ainda to com um errinho fiz o >>>>>>> seguinte: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> criei um diretorio na raiz chamado /tftpboot >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> copiei todo conteudo de >>>>>>>>>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe >>>>>>>>>>>>>>>>>>> para dentro de /tftpboot >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> depois dei o seguinte comando chmod 777 /tftpboot >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> alterei o dhcpd.conf para seguintes configurações >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>> filename "pxelinux.0"; >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> certo fui testar ele encontrou o arquivo e começou a dar >>> o >>>>>> boot >>>>>>>>>>>> mas >>>>>>>>>>>>>>> parou >>>>>>>>>>>>>>>> na >>>>>>>>>>>>>>>>>>> seguinte mensagem >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Could not find kernel image: diag/vesamenu.c32 >>>>>>>>>>>>>>>>>>> boot: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> essa mensagem fica aparecendo mais ou menos de uns 5 em 5 >>>>>>> segundos >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> eu olhei e esse arquivo existe na pasta >>>>>>>>>>>>>>>>>>> /tftpboot/pxelinux.cfg/diag/vesamenu.c32 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> será que eu teria que mover essa pasta diag para >>>>>> /tftpboot/diag >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> alguém tem idéia??? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> o arquivo que precisa ser pego pelo cliente PXE é o >>>>>> pxelinux.0, >>>>>>>>>>>> deve >>>>>>>>>>>>>>>>>>> colocar o caminho pra esse arquivo >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Em 23-02-2011 17:23, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>> Em 23 de fevereiro de 2011 17:21, Myke Lima < >>>>>>> cm...@gm... >>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> escreveu: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> correto entendi, meu arquivo pxelinux.0 esta no >>> seguinte >>>>>>>>>>>>>>> diretorio >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe/pxelinux.0 >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> então minha config ficou: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>> filename >>>>>> "Thinstation-2.2.2f/boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> mas continua com o mesmo erro não encontra o arquivo >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> o que mais poderia estar errado? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Foi mal cara, não percebi a linha do PXE, tem um >>> caminho >>>>>>> errado >>>>>>>>>>>>>>> ali no >>>>>>>>>>>>>>>>>>>>>> dhcp mesmo. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> filename "boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> esse caminho é para o binario do PXE, voce deve >>> colocar o >>>>>>>>>>>> caminho >>>>>>>>>>>>>>> onde >>>>>>>>>>>>>>>>>>>>>> se encontra o seu, partindo do /var/lib/tftpboot. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> EX.: se o arquivo estiver em >>>>>>>>>>>>>>> /var/lib/tftpboot/pxelinuc.cfg/pxelinux.0 >>>>>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>>>>> caminho correto seria . . . >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> filename "pxelinux.cfg/pxelinux.0"; >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 17:07, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>> *se for o arquivo esse arquivo >>>>>> /etc/default/tftpd-hpa* >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> a conf dele ta do seguinte maneira: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> RUN_DAEMON= yes >>>>>>>>>>>>>>>>>>>>>>>>>> TFTP_USERNAME= tftp >>>>>>>>>>>>>>>>>>>>>>>>>> TFTP_DIRECTORY= /var/lib/tftpboot >>>>>>>>>>>>>>>>>>>>>>>>>> TFTP_ADDRESS= 10.1.1.3:69 >>>>>>>>>>>>>>>>>>>>>>>>>> TFTP_OPTION= secure >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> se não for esse arquivo qual seria? >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> provavelmente as configurações do seu tftp devem >>>>>> estar >>>>>>>>>>>>>>> apontando >>>>>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>>>>> outro diretorio, jah conferiu isso ? >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 16:34, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> hum.. estranho fiz isso e não deu certo >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> ele achou o servidor dhcp atribuiu ip achou o >>>>>> servidor >>>>>>>>>>>> tftp >>>>>>>>>>>>>>> mas >>>>>>>>>>>>>>>>>>> não >>>>>>>>>>>>>>>>>>>>>> achou >>>>>>>>>>>>>>>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>>>>>>>>>>>> arquivo >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> apareceu as seguintes mensagens: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> file not foun >>>>>>>>>>>>>>>>>>>>>>>>>>>>> tftp error - file not found >>>>>>>>>>>>>>>>>>>>>>>>>>>>> exiting bootmanage pxe rom >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> e agora? >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Só mude a linha abaixo para o diretório correto >>> . >>>>>> . . >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> e reiniciar o serviço do dhcp3-server . . . >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> e testar é claro :) >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 15:41, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze >>> Logs >>>>>> and >>>>>>>>>>>> other >>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness >>> all >>>>>> the >>>>>>>>>>>> fast >>>>>>>>>>>>>>>> moving >>>>>>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>>>>>>>>> generated by your applications, servers and >>> devices >>>>>>> whether >>>>>>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost >>> and >>>>>>> gain >>>>>>>>>>>> new >>>>>>>>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs >>> and >>>>>>> other >>>>>>>>>>>> IT >>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all >>> the >>>>>>> fast >>>>>>>>>>>>>>> moving >>>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>>>>> whether >>>>>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>>>>> gain >>>>>>> new >>>>>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>>>>> other >>>>>>> IT >>>>>>>>>>>>>>> data in >>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>>>>> fast >>>>>>>>>>>> moving >>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>> whether >>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>> gain >>>>>> new >>>>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>> other >>>>>> IT >>>>>>>>>>>> data >>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>> fast >>>>>>> moving >>>>>>>>>>>> IT >>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>> generated by your applications, servers and devices whether >>>>>>> physical, >>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain >>> new >>>>>>>>>>>> business >>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>> >>>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - - >>>>>>>>>>>>>>> - >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>> >>>>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>> other >>>>>> IT >>>>>>> data >>>>>>>>>>>> in >>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>> fast >>>>>>> moving >>>>>>>>>>>> IT >>>>>>>>>>>>>>> data >>>>>>>>>>>>>>> generated by your applications, servers and devices whether >>>>>>> physical, >>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain >>> new >>>>>>>>>>>> business >>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>> >>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - -- >>>>>>>>>>>>>>> ======================= >>>>>>>>>>>>>>> *** Daian Conrad >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Linux user: #248912 >>>>>>>>>>>>>>> PGP/GPG: 0x7E25E948 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ** OpenS Team (DaCoD) >>>>>>>>>>>>>>> E-mail: da...@op... >>>>>>>>>>>>>>> Fone: +55 48 3954-8000 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>> >>>>>>>> >>>>>> >>>>>> - -- >>>>>> ======================= >>>>>> *** Daian Conrad >>>>>> >>>>>> Linux user: #248912 >>>>>> PGP/GPG: 0x7E25E948 >>>>>> >>>>>> ** OpenS Team (DaCoD) >>>>>> E-mail: da...@op... >>>>>> Fone: +55 48 3954-8000 >>>>>> >>>>>> -----BEGIN PGP SIGNATURE----- >>>>>> Version: GnuPG v1.4.10 (GNU/Linux) >>>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>>>>> >>>>>> iQEcBAEBAgAGBQJNZ8eTAAoJEKPh7Uh+JelIQacH/jLX7pVSLXe06gJamgmEN7Bp >>>>>> QKXaJJqBlkdnfJu+GuiNt+f/AL/Ihl8xtvaknk+Lxdx28ia8PPprQHaUyjUP61vK >>>>>> jmPTgFDH1UxlFKWEf6A0HnNI/RcqjbH77a17GGBzR5rbzIzEyxk7/YpMDyqZLdvo >>>>>> LVqej1gNbcaCIeDQoTSkgiVSzzqEG+lGU7V4SPd4jKteif5I5G2gAhjTHzI1iAcn >>>>>> Lg6mrrorf5gLjMOH7oUUzESGiQCg29NYCtwVy0GzPknM6xM7yaANFa+9OqZM4lVj >>>>>> VBiw5biL4u66ulocFooHsMb1GSZsz+uKpBQXXo6tKHoSeOAX70nQvzmhDR1Id8o= >>>>>> =9z8j >>>>>> -----END PGP SIGNATURE----- >>>>>> >>>>> >>>>> >>>> >>> >>> - -- >>> ======================= >>> *** Daian Conrad >>> >>> Linux user: #248912 >>> PGP/GPG: 0x7E25E948 >>> >>> ** OpenS Team (DaCoD) >>> E-mail: da...@op... >>> Fone: +55 48 3954-8000 >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.10 (GNU/Linux) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iQEcBAEBAgAGBQJNaBuoAAoJEKPh7Uh+JelI42cIAJbTQpXt4RVzqsGj+9giybxd >>> Wobl8g7m0K7yB6VbFbqFC0+FOtdhIeR0P6URQt4rko0WXYSOhOpCZOzts1LICAlD >>> LZ/62mxXhlmpW9XzuMDpxQhDvCM4maGjERnSzUVMhrzG+90MxBzkdp3OisxXzht+ >>> Th+uI21zXtA9RJU30td9KXzBJP9hDMbNFetczKDoUCcg7fVBbtQnk9Vj2ObRQ+Wr >>> P8eaQGEc7I3OtUgoJq0XyL1bU9aJeX88VsFPePq+Phh8ugmJr1M70Eoew1Z19Cbb >>> lYWg6NZzGrzjtt/bkLI8qR4bggzLBKhsAsoF87Mu6Giu1Vpp1EgsTEYU/RKM+WI= >>> =k/DC >>> -----END PGP SIGNATURE----- >>> >> >> > - -- ======================= *** Daian Conrad Linux user: #248912 PGP/GPG: 0x7E25E948 ** OpenS Team (DaCoD) E-mail: da...@op... Fone: +55 48 3954-8000 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNa9HrAAoJEKPh7Uh+JelI4q4IAKypdR2qBEvxiSoV4BkO7W4i 1n1RjSLC9z0oBDK8NohRnAglOFHaLiLCwDS0sWNFLymqy4A49Wo2BDnMBXrW1lov W56duNuQQkHnqd0+DUyY89TzEvF0OBe18fXidWlV9Hnk5VxeOD6ws+07/lhFIh2s 1h5ZhDmQL9MthjIo27ytr+baxxH9xJ89jn1F21hXu7X19oTcdmvcwRI4FCe/s6iY H8AD1uRBXyKJ8GO89c5R0IiqJJgb6CTgZl2IbezYFZdkHvHqBycPAkiBjXlUT9+c w8ivagnnxe9qRJT4bd71G0CbuS6vyRg/m7gLRL5OxBNEEVuVIzwfGKhxKMW/yi0= =tyrW -----END PGP SIGNATURE----- |
From: Daian C. <da...@op...> - 2011-02-25 21:11:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Estes logs servem sim ............ vamos destrinchar um pouco :D Esta é a sequencia que o cliente busca no server 10.1.1.164 <10.1.1.3> pxelinux.0 10.1.1.164 <10.1.1.3> pxelinux.cfg/56424f58-0000-0000-0000-080027af0 10.1.1.164 <10.1.1.3> pxelinux.cfg/01-08-00-27-af-01-a5 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A4 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101A 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0101 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A010 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A01 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A0 10.1.1.164 <10.1.1.3> pxelinux.cfg/0A 10.1.1.164 <10.1.1.3> pxelinux.cfg/0 10.1.1.164 <10.1.1.3> pxelinux.cfg/default 10.1.1.164 <10.1.1.3> diag/vesamenu.c32 10.1.1.164 <10.1.1.3> pxelinux.cfg/default 10.1.1.164 <10.1.1.3> ts_bg.jpg 10.1.1.164 <10.1.1.3> vmlinuz 10.1.1.164 <10.1.1.3> initrd Aparentemente ele não esta passando do initrd, deve ter alguma coisa ainda na sua imagem que não esta legal, não consegui ver o modelo dos thinclients que esta usando, o link não abre :-( . . . pode ser tmb algum parâmetro que esta configurado em "pxelinux.cfg/default" , outro teste que pode fazer , é gerar uma imagem on-line e salvar o VMLINUZ e o INITRD sobrescrevendo os atuais. Tlvz resolva seu problema com a imagem ;-) Em 25-02-2011 14:23, Myke Lima escreveu: > não sei se serve de alguma coisa mas procurei na net e dei esse comando o > resultado ta abaixo > > > root@SRVDHCP:/etc# tcpdump port 69 -v > > tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 > bytes > 13:22:04.115738 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 60) > 10.1.1.164.2001 > 10.1.1.3.tftp: 32 RRQ "pxelinux.0" octet blksize 1432 > 13:22:04.232202 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 107) > 10.1.1.164.57089 > 10.1.1.3.tftp: 79 RRQ > "pxelinux.cfg/56424f58-0000-0000-0000-080027af0" [|tftp] > 13:22:04.238420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 91) > 10.1.1.164.57090 > 10.1.1.3.tftp: 63 RRQ > "pxelinux.cfg/01-08-00-27-af-01-a5" octet tsize > 13:22:04.243420 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 79) > 10.1.1.164.57091 > 10.1.1.3.tftp: 51 RRQ "pxelinux.cfg/0A0101A4" octet > tsize 0 blksize 14 > 13:22:04.248400 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57092 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/0A0101A" octet > tsize 0 blksize 140 > 13:22:04.253273 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 77) > 10.1.1.164.57093 > 10.1.1.3.tftp: 49 RRQ "pxelinux.cfg/0A0101" octet > tsize 0 blksize 1408 > 13:22:04.258139 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 76) > 10.1.1.164.57094 > 10.1.1.3.tftp: 48 RRQ "pxelinux.cfg/0A010" octet > tsize 0 blksize 1408 > 13:22:04.262880 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 75) > 10.1.1.164.57095 > 10.1.1.3.tftp: 47 RRQ "pxelinux.cfg/0A01" octet > tsize 0 blksize 1408 > 13:22:04.267505 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 74) > 10.1.1.164.57096 > 10.1.1.3.tftp: 46 RRQ "pxelinux.cfg/0A0" octet tsize > 0 blksize 1408 > 13:22:04.272007 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 73) > 10.1.1.164.57097 > 10.1.1.3.tftp: 45 RRQ "pxelinux.cfg/0A" octet tsize > 0 blksize 1408 > 13:22:04.276514 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 72) > 10.1.1.164.57098 > 10.1.1.3.tftp: 44 RRQ "pxelinux.cfg/0" octet tsize 0 > blksize 1408 > 13:22:04.281526 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57099 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" octet > tsize 0 blksize 140 > 13:22:04.293463 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 75) > 10.1.1.164.57100 > 10.1.1.3.tftp: 47 RRQ "diag/vesamenu.c32" octet > tsize 0 blksize 1408 > 13:22:04.394604 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 78) > 10.1.1.164.57101 > 10.1.1.3.tftp: 50 RRQ "pxelinux.cfg/default" octet > tsize 0 blksize 140 > 13:22:04.460384 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 67) > 10.1.1.164.57102 > 10.1.1.3.tftp: 39 RRQ "ts_bg.jpg" octet tsize 0 > blksize 1408 > 13:22:07.410224 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 65) > 10.1.1.164.57103 > 10.1.1.3.tftp: 37 RRQ "vmlinuz" octet tsize 0 > blksize 1408 > 13:22:08.174756 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto UDP > (17), length 64) > 10.1.1.164.57104 > 10.1.1.3.tftp: 36 RRQ "initrd" octet tsize 0 blksize > 1408 > > > Em 25 de fevereiro de 2011 14:11, Myke Lima <cm...@gm...> escreveu: > >> achei somente isso... não achei nada referente a tftp >> >> >> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.167 (10.1.1.2) from >> 00:40:ca:a8:cc:84 via eth1: lease 10.1.1.167 unavailable. >> Feb 25 13:03:41 SRVDHCP dhcpd: DHCPNAK on 10.1.1.167 to 00:40:ca:a8:cc:84 >> via eth1 >> Feb 25 13:05:30 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:05:31 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:05:33 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) from >> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:05:43 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:05:45 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.150 (10.1.1.135) from >> 08:00:27:af:01:a5 via eth1: unknown lease 10.1.1.150. >> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPDISCOVER from 08:00:27:af:01:a5 via eth1 >> Feb 25 13:06:00 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.164 (10.1.1.3) from >> 08:00:27:af:01:a5 via eth1 >> Feb 25 13:06:02 SRVDHCP dhcpd: DHCPACK on 10.1.1.164 to 08:00:27:af:01:a5 >> via eth1 >> Feb 25 13:06:45 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via eth1 >> Feb 25 13:06:45 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.163 >> valid. >> Feb 25 13:06:45 SRVDHCP dhcpd: Abandoning IP address 10.1.1.163: pinged >> before offer >> Feb 25 13:06:47 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) from >> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:d8:4c via eth1 >> Feb 25 13:07:02 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.234 (10.1.1.2) from >> 00:40:ca:a8:d8:4c via eth1: unknown lease 10.1.1.234. >> Feb 25 13:07:03 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.169 to 00:40:ca:a8:d8:4c >> via eth1 >> Feb 25 13:07:09 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via eth1 >> Feb 25 13:07:09 SRVDHCP dhcpd: ICMP Echo reply while lease 10.1.1.168 >> valid. >> Feb 25 13:07:09 SRVDHCP dhcpd: Abandoning IP address 10.1.1.168: pinged >> before offer >> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) from >> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >> Feb 25 13:07:12 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to 00:40:ca:a8:cf:f5 >> via eth1 >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPDISCOVER from 00:40:ca:a8:cf:f5 via eth1 >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPREQUEST for 10.1.1.166 (10.1.1.2) from >> 00:40:ca:a8:cf:f5 via eth1: lease 10.1.1.166 unavailable. >> Feb 25 13:07:27 SRVDHCP dhcpd: DHCPNAK on 10.1.1.166 to 00:40:ca:a8:cf:f5 >> via eth1 >> Feb 25 13:07:28 SRVDHCP dhcpd: DHCPOFFER on 10.1.1.165 to 00:40:ca:a8:cf:f5 >> via eth1 >> root@SRVDHCP:/var/log# >> >> >> >> Em 25 de fevereiro de 2011 12:15, Daian Conrad <da...@op...>escreveu: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> todos os logs, em LSB, ficam em /var/log/(syslog,daemon.log,messages) >>> >>> []s >>> >>> >>> Em 25-02-2011 12:07, Myke Lima escreveu: >>>> desculpe a ignorancia, mas onde ficam os logs do tftp? >>>> >>>> >>>> >>>> >>>> >>>> Em 25 de fevereiro de 2011 11:02, Daian Conrad <da...@op... >>>> escreveu: >>>> >>>> Myke, >>>> >>>> Voce consegue verificar nos logs do tftp alguma informação quando a >>>> maquina cliente inicia ??? >>>> >>>> Tem alguma informação que ainda esta faltando, ficar simplesmente parado >>>> no boot, não explica muita coisa . . . >>>> >>>> Look inside the logs dude ;-) >>>> >>>> >>>> []s >>>> >>>> >>>> Em 25-02-2011 09:51, Myke Lima escreveu: >>>>>>> alguém mais tem idéia do que pode estar acontecendo??? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Em 24 de fevereiro de 2011 15:26, Myke Lima <cm...@gm...> >>>> escreveu: >>>>>>> >>>>>>>> alterei recriei a imagem e mesma coisa >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Em 24 de fevereiro de 2011 15:23, Daian Conrad <da...@op... >>>>>>> escreveu: >>>>>>>> >>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>> Hash: SHA1 >>>>>>>>> >>>>>>>>> pode ser sim, tem que estar igual >>>>>>>>> >>>>>>>>> >>>>>>>>> Se esta diferente fui eu que errei :) >>>>>>>>> >>>>>>>>> []s >>>>>>>>> >>>>>>>>> >>>>>>>>> Em 24-02-2011 14:41, Myke Lima escreveu: >>>>>>>>>> fiz o procedimento mas esta do mesmo jeito fica parada no >>>>>>>>> pinguinzinhu.... >>>>>>>>>> >>>>>>>>>> uma coisa q eu achei estranha e dei uma olhada no >>>>>>>>> thinstation.conf.buildtime >>>>>>>>>> >>>>>>>>>> esta como sessao rdesktop e no build.conf esta seleciona o >>> rdesktopsvn >>>>>>>>>> >>>>>>>>>> esta certo isso é a mesma coisa? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Em 24 de fevereiro de 2011 13:00, Myke Lima <cm...@gm...> >>>>>>>>> escreveu: >>>>>>>>>> >>>>>>>>>>> ok, vou testar e posto aqui a principio eu não sei qual a placa >>> de >>>> rede >>>>>>>>> e >>>>>>>>>>> video, mas no servidor antigo de ltsp estava tudo como vesa por >>> isso >>>>>>>>> ate >>>>>>>>>>> deixei o vesa habilitado mas o modelo do thinclient é esse >>>>>>>>>>> http://www.connec.com.br/site/p01b1.asp >>>>>>>>>>> >>>>>>>>>>> <http://www.connec.com.br/site/p01b1.asp> >>>>>>>>>>> >>>>>>>>>>> Em 24 de fevereiro de 2011 11:56, Daian Conrad < >>> da...@op... >>>>>>>>>> escreveu: >>>>>>>>>>> >>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>>>>>> Hash: SHA1 >>>>>>>>>>>> >>>>>>>>>>>> è possivel que tenha algum problema na configuração da sua >>> imagem de >>>>>>>>>>>> boot(initrd), faltando algum modulo e coisas do tipo. >>>>>>>>>>>> >>>>>>>>>>>> os problemas com modulos são comuns em thinclient's muito novos, >>>> pois >>>>>>>>>>>> ainda estão atualizando o core para versões de kernel mais novos >>> e >>>>>>>>> etc. >>>>>>>>>>>> >>>>>>>>>>>> Qual o modelo do thinclient ou maquina(rede e video) . . . >>>>>>>>>>>> >>>>>>>>>>>> Por via das duvidas dei uma revisada nos seus arquivos e acho >>> que >>>>>>>>> seria >>>>>>>>>>>> interessante testar o RDP com o rdesktop. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Deixei a principio prontosó copiar para a pasta , renomear e >>>>>>>>>>>> compilar(./build) . >>>>>>>>>>>> >>>>>>>>>>>> []s >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Em 24-02-2011 11:39, Myke Lima escreveu: >>>>>>>>>>>>> Ele fica parado na tela toda preta com a seguinte mensagem: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Loading vmlinuz...................... >>>>>>>>>>>>> Loading initrd..........ready >>>>>>>>>>>>> Uncompressing Linux... Ok, booting the kernel. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> e não sai disso... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> sera que tem algo errado na minha imagem meu arquivo build.conf >>> ta >>>>>>>>>>>> certo? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Em 24 de fevereiro de 2011 11:25, Daian Conrad < >>> da...@op... >>>>>>>>>>>>> escreveu: >>>>>>>>>>>>> >>>>>>>>>>>>> Parece que ele não achou o kernel indicado (vmlinuz ou o >>> initrd), >>>> nos >>>>>>>>>>>>> logs do tftp, não aparece o caminho ou arquivos que a estação >>> esta >>>>>>>>>>>>> procurando ?? >>>>>>>>>>>>> >>>>>>>>>>>>> []s >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Em 24-02-2011 08:54, Myke Lima escreveu: >>>>>>>>>>>>>>>> Bom dia, tenho alguma novidades.. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> consegui fazer o boot mas ainda to com um errinho fiz o >>>> seguinte: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> criei um diretorio na raiz chamado /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> copiei todo conteudo de >>>>>>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe >>>>>>>>>>>>>>>> para dentro de /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> depois dei o seguinte comando chmod 777 /tftpboot >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> alterei o dhcpd.conf para seguintes configurações >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>> filename "pxelinux.0"; >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> certo fui testar ele encontrou o arquivo e começou a dar o >>> boot >>>>>>>>> mas >>>>>>>>>>>> parou >>>>>>>>>>>>> na >>>>>>>>>>>>>>>> seguinte mensagem >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Could not find kernel image: diag/vesamenu.c32 >>>>>>>>>>>>>>>> boot: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> essa mensagem fica aparecendo mais ou menos de uns 5 em 5 >>>> segundos >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> eu olhei e esse arquivo existe na pasta >>>>>>>>>>>>>>>> /tftpboot/pxelinux.cfg/diag/vesamenu.c32 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> será que eu teria que mover essa pasta diag para >>> /tftpboot/diag >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> alguém tem idéia??? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> o arquivo que precisa ser pego pelo cliente PXE é o >>> pxelinux.0, >>>>>>>>> deve >>>>>>>>>>>>>>>> colocar o caminho pra esse arquivo >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Em 23-02-2011 17:23, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>> Em 23 de fevereiro de 2011 17:21, Myke Lima < >>>> cm...@gm... >>>>>>>>>> >>>>>>>>>>>>>>>> escreveu: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> correto entendi, meu arquivo pxelinux.0 esta no seguinte >>>>>>>>>>>> diretorio >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>> /var/lib/tftpboot/Thinstation-2.2.2f/boot-images/pxe/pxelinux.0 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> então minha config ficou: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>> filename >>> "Thinstation-2.2.2f/boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> mas continua com o mesmo erro não encontra o arquivo >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> o que mais poderia estar errado? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Foi mal cara, não percebi a linha do PXE, tem um caminho >>>> errado >>>>>>>>>>>> ali no >>>>>>>>>>>>>>>>>>> dhcp mesmo. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> filename "boot-images/pxe/pxelinux.0"; >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> esse caminho é para o binario do PXE, voce deve colocar o >>>>>>>>> caminho >>>>>>>>>>>> onde >>>>>>>>>>>>>>>>>>> se encontra o seu, partindo do /var/lib/tftpboot. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> EX.: se o arquivo estiver em >>>>>>>>>>>> /var/lib/tftpboot/pxelinuc.cfg/pxelinux.0 >>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>> caminho correto seria . . . >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> filename "pxelinux.cfg/pxelinux.0"; >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Em 23-02-2011 17:07, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>> *se for o arquivo esse arquivo >>> /etc/default/tftpd-hpa* >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> a conf dele ta do seguinte maneira: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> RUN_DAEMON= yes >>>>>>>>>>>>>>>>>>>>>>> TFTP_USERNAME= tftp >>>>>>>>>>>>>>>>>>>>>>> TFTP_DIRECTORY= /var/lib/tftpboot >>>>>>>>>>>>>>>>>>>>>>> TFTP_ADDRESS= 10.1.1.3:69 >>>>>>>>>>>>>>>>>>>>>>> TFTP_OPTION= secure >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> se não for esse arquivo qual seria? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> provavelmente as configurações do seu tftp devem >>> estar >>>>>>>>>>>> apontando >>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>> outro diretorio, jah conferiu isso ? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 16:34, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>> hum.. estranho fiz isso e não deu certo >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> ele achou o servidor dhcp atribuiu ip achou o >>> servidor >>>>>>>>> tftp >>>>>>>>>>>> mas >>>>>>>>>>>>>>>> não >>>>>>>>>>>>>>>>>>> achou >>>>>>>>>>>>>>>>>>>>>>> o >>>>>>>>>>>>>>>>>>>>>>>>>> arquivo >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> apareceu as seguintes mensagens: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> file not foun >>>>>>>>>>>>>>>>>>>>>>>>>> tftp error - file not found >>>>>>>>>>>>>>>>>>>>>>>>>> exiting bootmanage pxe rom >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e agora? >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> 2011/2/23 Daian Conrad <da...@op...> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Só mude a linha abaixo para o diretório correto . >>> . . >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> para >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/var/lib/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e reiniciar o serviço do dhcp3-server . . . >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> e testar é claro :) >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> []s >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Em 23-02-2011 15:41, Myke Lima escreveu: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> option root-path "/tftpboot"; >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs >>> and >>>>>>>>> other >>>>>>>>>>>> IT >>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all >>> the >>>>>>>>> fast >>>>>>>>>>>>> moving >>>>>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>>> whether >>>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>>> gain >>>>>>>>> new >>>>>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>>> other >>>>>>>>> IT >>>>>>>>>>>> data >>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>>> fast >>>>>>>>>>>> moving >>>>>>>>>>>>> IT >>>>>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>>>>> generated by your applications, servers and devices >>> whether >>>>>>>>>>>> physical, >>>>>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and >>> gain >>>> new >>>>>>>>>>>>> business >>>>>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> - >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and >>> other >>>> IT >>>>>>>>>>>> data in >>>>>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the >>> fast >>>>>>>>> moving >>>>>>>>>>>> IT >>>>>>>>>>>>>>>> data >>>>>>>>>>>>>>>> generated by your applications, servers and devices whether >>>>>>>>> physical, >>>>>>>>>>>>>>>> virtual >>>>>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain >>> new >>>>>>>>>>>> business >>>>>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>>>>> >>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>> - >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and other >>> IT >>>>>>>>> data >>>>>>>>>>>> in >>>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the fast >>>> moving >>>>>>>>> IT >>>>>>>>>>>>> data >>>>>>>>>>>>> generated by your applications, servers and devices whether >>>> physical, >>>>>>>>>>>>> virtual >>>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain new >>>>>>>>> business >>>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>>> Thi...@li... >>>>>>>>>>>>> >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> - - >>>>>>>>>>>> - >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>> >>>> >>> ------------------------------------------------------------------------------ >>>>>>>>>>>> Free Software Download: Index, Search & Analyze Logs and other >>> IT >>>> data >>>>>>>>> in >>>>>>>>>>>> Real-Time with Splunk. Collect, index and harness all the fast >>>> moving >>>>>>>>> IT >>>>>>>>>>>> data >>>>>>>>>>>> generated by your applications, servers and devices whether >>>> physical, >>>>>>>>>>>> virtual >>>>>>>>>>>> or in the cloud. Deliver compliance at lower cost and gain new >>>>>>>>> business >>>>>>>>>>>> insights. http://p.sf.net/sfu/splunk-dev2dev >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Thinstation-portuguese mailing list >>>>>>>>>>>> Thi...@li... >>>>>>>>>>>> >>> https://lists.sourceforge.net/lists/listinfo/thinstation-portuguese >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> - -- >>>>>>>>>>>> ======================= >>>>>>>>>>>> *** Daian Conrad >>>>>>>>>>>> >>>>>>>>>>>> Linux user: #248912 >>>>>>>>>>>> PGP/GPG: 0x7E25E948 >>>>>>>>>>>> >>>>>>>>>>>> ** OpenS Team (DaCoD) >>>>>>>>>>>> E-mail: da...@op... >>>>>>>>>>>> Fone: +55 48 3954-8000 >>>>>>>>>>>> >>>>>>>>>>>> >>> >>>>> >>> >>> - -- >>> ======================= >>> *** Daian Conrad >>> >>> Linux user: #248912 >>> PGP/GPG: 0x7E25E948 >>> >>> ** OpenS Team (DaCoD) >>> E-mail: da...@op... >>> Fone: +55 48 3954-8000 >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.10 (GNU/Linux) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >>> >>> iQEcBAEBAgAGBQJNZ8eTAAoJEKPh7Uh+JelIQacH/jLX7pVSLXe06gJamgmEN7Bp >>> QKXaJJqBlkdnfJu+GuiNt+f/AL/Ihl8xtvaknk+Lxdx28ia8PPprQHaUyjUP61vK >>> jmPTgFDH1UxlFKWEf6A0HnNI/RcqjbH77a17GGBzR5rbzIzEyxk7/YpMDyqZLdvo >>> LVqej1gNbcaCIeDQoTSkgiVSzzqEG+lGU7V4SPd4jKteif5I5G2gAhjTHzI1iAcn >>> Lg6mrrorf5gLjMOH7oUUzESGiQCg29NYCtwVy0GzPknM6xM7yaANFa+9OqZM4lVj >>> VBiw5biL4u66ulocFooHsMb1GSZsz+uKpBQXXo6tKHoSeOAX70nQvzmhDR1Id8o= >>> =9z8j >>> -----END PGP SIGNATURE----- >>> >> >> > - -- ======================= *** Daian Conrad Linux user: #248912 PGP/GPG: 0x7E25E948 ** OpenS Team (DaCoD) E-mail: da...@op... Fone: +55 48 3954-8000 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNaBuoAAoJEKPh7Uh+JelI42cIAJbTQpXt4RVzqsGj+9giybxd Wobl8g7m0K7yB6VbFbqFC0+FOtdhIeR0P6URQt4rko0WXYSOhOpCZOzts1LICAlD LZ/62mxXhlmpW9XzuMDpxQhDvCM4maGjERnSzUVMhrzG+90MxBzkdp3OisxXzht+ Th+uI21zXtA9RJU30td9KXzBJP9hDMbNFetczKDoUCcg7fVBbtQnk9Vj2ObRQ+Wr P8eaQGEc7I3OtUgoJq0XyL1bU9aJeX88VsFPePq+Phh8ugmJr1M70Eoew1Z19Cbb lYWg6NZzGrzjtt/bkLI8qR4bggzLBKhsAsoF87Mu6Giu1Vpp1EgsTEYU/RKM+WI= =k/DC -----END PGP SIGNATURE----- |