H. Sayeeduddin Dagar

Ustad Hussain Sayeeduddin Dagar (20 April 1939 – 30 July 2017), popularly known as Saeed Bhai, was an Indian classical vocalist belonging to the Dhrupad tradition, the oldest existing form of north Indian classical music (Hindustani classical music).[1][2] He was a part of the Dagar family of musicians.[3][4] He represented the 19th generation of Dagar Tradition. His cousins Nasir Moinuddin Dagar and Nasir Aminuddin Dagar were known as the Senior Dagar Brothers. Similarly, Nasir Zahiruddin and Nasir Faiyazuddin Dagar were known as the Younger Dagar Brothers. His other cousins were Zia Mohiuddin Dagar, Zia Fariduddin Dagar, and Rahim Fahimuddin Dagar.[5] He performed in the famous Bharat Ek Khoj.

Ustad Hussain Sayeeduddin Dagar
H. Sayeeduddin Dagar in 2017
Background information
Also known asSaeed Bhai
Born(1939-04-20)20 April 1939
Alwar, Rajasthan, India
OriginIndia
Died30 July 2017(2017-07-30) (aged 78)
Pune
GenresDhrupad
Occupation(s)Vocalist

Biography

Born in Alwar, Rajasthan in 1939 into the Dagar family, Hussain Sayeeduddin Khan Dagar is the son of Hussainuddin Khan Dagar who died in 1963. Among the Dagar family, also known as the 'Dagar saptak', he was the last representative of the 19th generation of the Dagar lineage. He began his training at age 6 under his father Ustad Hussainuddin Khan Dagar, and later his uncle, Ustad Rahimuddin Khan Dagar. He had been the President of Dhrupad Society Jaipur and Pune.[6]

Hussain Sayeeduddin Khan Dagar resided in Pune.[7]

gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
gollark: You could make a mechanical computer from solidified beans.

References

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