Ibragimkhalil Daudov

Ibragimkhalil Daudov (11 November 1960 – 14 February 2012),[1] also known as Emir Salikh, was the leader of the militant Vilayat Dagestan in Dagestan after the death of Israpil Velijanov.

Ibragimkhalil Daudov
Emir of the Dagestani Front
In office
9 May 2011  14 February 2012
Preceded byIsrapil Velijanov
Succeeded byRustam Asildarov
Personal details
Born(1960-11-11)11 November 1960
Dagestan RSFSR USSR
Died14 February 2012(2012-02-14) (aged 51)
Dagestan Russia
Military service
AllegianceCaucasus Emirate
CommandsVilayat Dagestan
Battles/warsInsurgency in the North Caucasus

Biography

Ibragimkhalil reportedly joined Vilayat Dagestan in 2008. After serving time in Azerbaijan for possession of weapons, Daudov returned to his native village of Gubden where he was placed under police surveillance. After his house caught fire, the villagers found a hidden weapons cache on the premises, Ibragimkhalil took with him his three sons and joined the militant group led by Magomed Vagabov. He eventually became the leader of the group from 9 May 2011 until his death. [2]

Russian investigators say Daudov brought his wife and another woman to Moscow in 2009 to carry out a suicide attack on people celebrating New Year's Eve near the Kremlin, but their bomb exploded hours earlier in a Moscow suburb. Daudov's wife was killed in the explosion and several people were arrested.[3]

On 10 February 2012 Russian security forces attacked a house that contained a number of militants including Ibragimkhalil. On 14 February 2012 Ibragimkhalil Daudov was found dead in a river near the village of Gurbuki. He had apparently escaped from the scene of the earlier operation but died of his wounds and exposure.[4] All three of his sons were killed fighting the security forces; Mohammed Daudov in the summer of 2009, Magomedshapi Daudov in April 2010 and Magamedhabib Daudov in February 2012 in the same operation that resulted in the death of their father.[4]

gollark: Go is kind of like YAML with the whole "simple" thing - it kind of *looks* simple and easy, but it's a minefield of special cases and weirdness and problems and all the special cases make it more complex than something actually designed to be simple would be.
gollark: In cleaner and more typesafe ways.
gollark: You can use codegen to generate code for repetitive tasks of some sort if they don't need to generalize much or go outside your project, but it's much better to just... not have to do those repetitive tasks, or have the compiler/macros handle them.
gollark: Also, you end up with a mess of fragile infrastructure which operates on stringy representations of the code.
gollark: I can either:- use `interface{}` - lose type safety and performance- codegen a different `Tree` type for every use of it - now I can't really put it in its own library and it's generally inelegant and unpleasant

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.