You have just received a gift card from us
Untitled Document Direct Home If you do not want to receive any more messages from us, check the bottom of this message for unsubscribe button, you will be removed from our mailing list instantly. Thank you ASDA Direct is calling you to become a mistery shopper ! Become a Mystery Shopper and if selected receive £100 of Asda Vouchers to shop in store. Tell us about your shopping experiences with Asda, one of the largest food retailers in the UK. The vouchers are yours to spend on whatever you like, all we require is a short review, detailing how you found your shop! All you have to do is to click here and apply www.asda.com/direct _ ___ COPYRIGHT (c) MG eMail Marketing for ASDA DIRECT UK , 2012 __ _ To unsubscribe from our mailing list please click here Your email will be removed immediately, we respect your privacy. MG eMail Marketing, Lemon Ave #6333 Walnut, CA 91789.
TenisPT.com - Os melhores momentos do ténis mundial.
TENISPT.COM OS MELHORES MOMENTOS DO TÉNIS MUNDIAL O nosso url: www.tenispt.com Temos também uma comunidade no facebook: www.facebook.com/pages/TenisPt Fundado em Julho de 2012, este website tem como objectivo divulgar o melhor ténis através da visualização de vídeos de jogos, dos melhores pontos, de treinos, de entrevistas e de tudo o que seja de interesse. O jogo actual de tênis inicou-se no século XIX, em Inglaterra. Porém, muitos historiadores acreditam que a origem do desporto data o século XII, na França, contudo usava-se a mão para bater na bola. No final do século XVI começou-se a usar raquetes para bater na bola e o jogo passou a ser chamado de ténis, do francês antigo Tenez, que pode ser traduzido como segure ou receba. O jogo era popular em França e em Inglaterra, onde era praticado em locais cobertos, onde a bola não batesse em uma parede. O torneio mais antigo de tênis no mundo, o Torneio de Wimbledon, foi realizado pela primeira vez em Londres em 1877. Essa primeira edição gerou um debate sobre a padronização das regras do desporto. Em 21 de Maio de 1881, a United States National Lawn Tennis Association foi fundada para padronizar as regras e organizar as competições. O U.S. National Men's Singles Championship, hoje o US Open de ténis, foi realizado pela primeira vez em 1881, em Newport, Rhode Island. O torneio feminino se estabeleceu em 1887. O desporto também era popular em França, com o Open da França datando de 1891. Assim, Wimbledon, o US Open, o Open de França e o Open da Austrália (de 1905) tornaram-se os eventos de maior prestígio no ténis, algo que se mantém até hoje. Juntos, esses torneios são chamados de Majors ou Slams (termo retirado do basebol). As regras mais abrangentes foram promulgadas em 1924, pela Federação Internacional das Regras de Ténis, hoje conhecida como Federação Internacional de Tênis, e se mantém até o dias atuais, com a principal alteração sendo a adição do tie-break, desenvolvido por Jimmy Van Alen. No mesmo ano, o desporto se retirou dos Jogos Olímpicos, tendo retornado somente em 1984, como um evento promocional. O sucesso do evento foi tão grande que o COI decidiu reintroduzir o ténis como um desporto olímpico na edição de 1988, em Seul. A Copa Davis, a principal competição internacional entre as federações nacionais, existe desde 1900. A versão análoga para as mulheres é a Fed Cup, iniciada em 1963 Em 1968, após denúncias de lavagem de dinheiro envolvendo tenistas menos expressivos, iniciou-se a era open, onde todos os jogadores poderiam competir em todos os torneios. Com o estabelecimento da era open, também iniciou-se o circuito profissional internacional, aumentando a receita e a popularidade do desporto pelo mundo. Temos actualmente cerca de 50 utilizadores constantemente online durante todo o dia. Milhares de utilizadores visitam tenispt.com por dia. Poderá visualizar todas as estatísticas na página inicial. Somos uma equipa que prima pelo trabalho e dedicação, e é por isso que conseguimos ser uma referência nos websites de ténis em Portugal e no Brasil. TenisPT.com todos os direitos reservados © 2012 Este email foi enviado porque se registou numa das páginas da nossa rede. Se pretender anular a informação que a nossa empresa envia dirija-se aqui. (Directiva 2000/31/CE do Parlamento Europeu; Relatório A5-0270/2001 do Parlamento Europeu) This email was sent because you registered in one of our websites. To Unsubscribe from this list please follow this link.
Re: duplicate code
Question: Why is there duplicate code in bus.h that says its not implemented? This was added by mistake in 1.44 by accident, and noone had noticed so far. Thanks for reporting this. Miod
Re: ospfd network
On Sat, Sep 29, 2012 at 03:22:58PM +0300, Kapeatanakis Giannis wrote:
Hi,
I have two questions regarding ospfd.
a) is there an equivalent to Cisco's or Quagga's network definition
network 10.0.0.0/24 area 0.0.0.1
in order to define that a certain network belongs to a certain area?
No. The redistribute foo in ospfd will generate AS-ext LSA and those are
not bound to an area.
From my understanding of ospfd.conf(5) the only way to do this is to
put the interface definition in area {}.
Maybe I'm missing something.
No that is correct.
b) quagga support ACLs on areas like import-list
Is there a way for filtering out certain route announcements from
remote routers?
No, it is no possible to filter between areas.
--
:wq Claudio
Re: ospfd network
On 30/09/12 14:24, Claudio Jeker wrote:
On Sat, Sep 29, 2012 at 03:22:58PM +0300, Kapeatanakis Giannis wrote:
Hi,
I have two questions regarding ospfd.
a) is there an equivalent to Cisco's or Quagga's network definition
network 10.0.0.0/24 area 0.0.0.1
in order to define that a certain network belongs to a certain area?
No. The redistribute foo in ospfd will generate AS-ext LSA and those are
not bound to an area.
From my understanding of ospfd.conf(5) the only way to do this is to
put the interface definition in area {}.
Maybe I'm missing something.
No that is correct.
b) quagga support ACLs on areas like import-list
Is there a way for filtering out certain route announcements from
remote routers?
No, it is no possible to filter between areas.
Thanks for the clarifications Claudio.
Giannis
Atheros driver.
Hi. I'm trying to find a PCI wireless card and bought one of these: http://www.tp-link.com/en/products/details/?categoryid=246model=TL-WN350GD dmesg shows: vendor Atheros, unknown product 0x001d (class network subclass ethernet, rev 0x01) at pci1 dev 1 function 0 not configured Does this mean point blank this is an un-supported chipset or are there things to check, etcetera? Best wishes.
Re: Atheros driver.
On Sun, Sep 30, 2012 at 10:42:55PM +0930, David Walker wrote: Hi. I'm trying to find a PCI wireless card and bought one of these: http://www.tp-link.com/en/products/details/?categoryid=246model=TL-WN350GD dmesg shows: vendor Atheros, unknown product 0x001d (class network subclass ethernet, rev 0x01) at pci1 dev 1 function 0 not configured Does this mean point blank this is an un-supported chipset or are there things to check, etcetera? That means it is unclaimed by all drivers in the kernel. In this case it seems to be an AR2417, which would be covered by ath(4) if ath was updated to support it. So it is unsupported for now.
Re: Atheros driver.
It looks like you're probably out of luck, see http://madwifi-project.org/wiki/Compatibility/TP-Link TL-WN350GD is AR2417 / AR5007G, neither of which are listed either in athn(4) or ath(4), or the CVS commits if openbsd src is searched. I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Which relates to http://www.tp-link.com/en/products/details/?categoryid=240model=TL-WN951N http://www.wikidevi.com/wiki/TP-LINK_TL-WN951N_v1 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. On 30 September 2012 14:12, David Walker davidianwal...@gmail.com wrote: Hi. I'm trying to find a PCI wireless card and bought one of these: http://www.tp-link.com/en/products/details/?categoryid=246model=TL-WN350GD dmesg shows: vendor Atheros, unknown product 0x001d (class network subclass ethernet, rev 0x01) at pci1 dev 1 function 0 not configured Does this mean point blank this is an un-supported chipset or are there things to check, etcetera? Best wishes.
Re: Atheros driver.
On Sun, Sep 30, 2012 at 04:39:16PM +0100, Peter Kay wrote: I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. Android might require power management support which was recently added to athn(4) in -current. So try -current on the AP, it might fix problems with the Android device.
tmux and current directory
On current/i386, tmux seems to open a new shell with the current
directory being the same as in the window I am opening from.
What that means in particular is that if I run 'man whatever'
in a tmux window, and open a new windowd ('ctrl-b c' in my case),
the news shell is opened in /usr/local/man. Is that inteded?
Jan
Re: tmux and current directory
more of a case of man gratuitously changing cwd
shells spawned by $PAGER also have a cwd of the base of the man path
On Sun, Sep 30, 2012 at 12:38 PM, Jan Stary h...@stare.cz wrote:
On current/i386, tmux seems to open a new shell with the current
directory being the same as in the window I am opening from.
What that means in particular is that if I run 'man whatever'
in a tmux window, and open a new windowd ('ctrl-b c' in my case),
the news shell is opened in /usr/local/man. Is that inteded?
Jan
Re: tmux and current directory
This seems like intended behavior. If you want to change this you might
investigate the default-path option.
On Sep 30, 2012 1:11 PM, Jan Stary h...@stare.cz wrote:
On current/i386, tmux seems to open a new shell with the current
directory being the same as in the window I am opening from.
What that means in particular is that if I run 'man whatever'
in a tmux window, and open a new windowd ('ctrl-b c' in my case),
the news shell is opened in /usr/local/man. Is that inteded?
Jan
RAID hardware
Hello, I would like to know which hardware you'd recommend for use with softraid for at least 4 HD ? I am looking for hardware which would suipport plug live change of a failed drive. If you have good experiences with some hardware, I would be interested in your experience. Thank you J-F.
Re: tmux and current directory
On 2012-09-30, Jan Stary h...@stare.cz wrote:
On current/i386, tmux seems to open a new shell with the current
directory being the same as in the window I am opening from.
What that means in particular is that if I run 'man whatever'
in a tmux window, and open a new windowd ('ctrl-b c' in my case),
the news shell is opened in /usr/local/man. Is that inteded?
Yes. I dislike this behaviour by default but I do find it useful
on occasion, so I use this:
set -g default-path .
bind C new-window -c
this lets me do prefix-c to open a new window normally (working
directory being the same as tmux was started in) and prefix-C for
the new behaviour (i.e. if I'm somewhere in a deep path and don't
want to cd manually), which works well for me.
Re: tmux and current directory
On Sun, Sep 30, 2012 at 06:24:08PM +, Stuart Henderson wrote:
On 2012-09-30, Jan Stary h...@stare.cz wrote:
On current/i386, tmux seems to open a new shell with the current
directory being the same as in the window I am opening from.
What that means in particular is that if I run 'man whatever'
in a tmux window, and open a new windowd ('ctrl-b c' in my case),
the news shell is opened in /usr/local/man. Is that inteded?
Yes. I dislike this behaviour by default but I do find it useful
on occasion, so I use this:
set -g default-path .
bind C new-window -c
this lets me do prefix-c to open a new window normally (working
directory being the same as tmux was started in) and prefix-C for
the new behaviour (i.e. if I'm somewhere in a deep path and don't
want to cd manually), which works well for me.
Thanks!
j.
Re: Atheros driver.
This is post the -current fix with athn(4) power saving. Without it Android devices don't really work at all, with it they work for a bit and then stop working claiming the access point isn't within range. It's a problem that's not specific to OpenBSD - some access points suffer the same issue, but I've not seen a definite solution so far. On 30 September 2012 17:38, Stefan Sperling s...@openbsd.org wrote: On Sun, Sep 30, 2012 at 04:39:16PM +0100, Peter Kay wrote: I've got this if it helps : athn0 at pci0 dev 15 function 0 Atheros AR5416 rev 0x01: irq 3 athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5 Works fine with OpenBSD with Windows devices, but there's a problem establishing a connection with Android, cause unknown. Android might require power management support which was recently added to athn(4) in -current. So try -current on the AP, it might fix problems with the Android device.
