apt-get install grub mdadm initramfs-tools

fdisk -l
Disque /dev/sda: 250.0 Go, 250059350016 octets
255 heads, 63 sectors/track, 30401 cylinders
Units = cylindres of 16065 * 512 = 8225280 bytes
Identifiant disque: 0×0cf1421a

Périphérique Amorce    Début         Fin      Blocs    Id  Système
/dev/sda1   *           1         392     3148708+  83  Linux
/dev/sda2             393       30336   240525180   83  Linux
/dev/sda3           30337       30401      522112+  82  Linux swap / Solaris

grub-install –recheck /dev/sda



grub
>root (hd0,0)
>find /boot/grub/stage2 # si pas trouvé, essayer find grub/stage2
>       hd(0,0)
>       hd(1,0) # vous obtenez ceci si vous êtes en RAID

# on utilise le résultat du find
>setup (hd0)
>setup (hd1) # uniquement si vous êtes en RAID
>quit

apt-get install xen-tools

reboot

Syntaxe de Wiki

Les vidéos sur Google Video ont une IDENTITÉ unique. On trouve facilement cette IDENTITÉ sur le site Google Video car elle est composée d’une série de chiffres et apparaît dans l’URL lorsque vous consultez la vidéo.

Affichage direct des vidéos

Syntaxe Wiki

{{googlevideo>small:ID_VIDEO_GOOGLE}}

{{googlevideo>large:ID_VIDEO_GOOGLE}}

Code Source

1. Créez un répertoire ’googlevideo’ dans le répertoire ‘/lib/plugins’.
2. Copiez le code suivant et collez le dans un fichier nommé syntax.php.
3. Mettez le fichier syntax.php dans le répertoire ‘googlevideo’.

http://flap.free.fr/google_video/syntaxphp.txt

http://www.routerboard.com/

http://www.mikrotik.com/

Matériel radio

http://www.wirelesslan.gr/

http://www.interprojekt.pl/

http://www.diswire.com/

http://eshop.cznet.cz/

La source

http://www.routerboard.com/sales.html

http://www.voipstunt.com/

http://www.voipcheap.co.uk/

http://www.netappel.fr/

http://www.sipdiscount.com/

http://doulos.wordpress.com/technical-information/finarea/

http://doulos.wordpress.com/technical-information/finarea-asterisk/

Hi Karl,

You might want to try setting the HelloValidityTime parameter to a
higher than default value. In your case, with links there are two
mechanisms at work - (1) link detection and (2) link quality. The link
quality case is what you care for with the large window size. However,
in your configuration file you do not change the link detection
parameters. By default, every two seconds a node broadcasts a HELLO
message to announce its existence to its neighbours. The corresponding
configuration line would be “HelloInterval 2.0″. In its HELLO messages
it also says “if you do not hear a HELLO message for six seconds,
consider me dead”. The corresponding configuration line would be
“HelloValidityTime 6.0″. So, if three HELLOs in a row are lost, then the
link is considered down, irrespective of the link quality window size.

So, what this all boils down to is that we recommend setting the
“HelloValidityTime” to “HelloInterval x LinkQualityWinSize”, i.e. to use
“HelloValidityTime 120.0″ on *all* nodes in your mesh. (Remember that
setting this value on node X influences the behaviour of X’s neighbours,
i.e. if you set the validity time to 120 seconds on node X, all of X’s
neighbours will consider the link to X existent as long as there’s at
least one HELLO from X every 120 seconds.)

In this way, we guarantee that link detection will not remove a link
before link quality has had a chance to let it’s link quality decay to
the worst possible case, which is that LinkQualityWinSize x
HelloInterval packets have been lost. So, basically, what we do is, we
switch off link detection and leave it all to link quality.

So, I’d recommend adding “HelloValidityTime 120.0″ to your interface
configuration.

BTW, “HelloInterval x LinkQualityWinSize” is the default setting for
HelloValidityTime in 0.4.10, which is used if the user doesn’t specify
anything else. So for 0.4.10 your configuration will work as is.

-Thomas

C’est un service intéressant qui permet de remonter des alertes afin de ne pas passer à cotés de problèmes d’accès…

Ce site est hébergé chez ovh sur un 90plan (le même que www.mynetmemo.com).