Nasir of Sennar

Nasir (reigned 1762–1769) was a Hamaj regent under the Funj Sultanate of Sennar. He was the son of Badi IV, the previous ruler.

Sword of Nasir ibn Badi IV, National Corporation for Antiquities and Museums of Sudan

He deposed his father Badi, with the help of the vizer Sheikh Adelan and his brother Abu Kalec the governor of Kordofan. Badi fled to sanctuary in Ethiopia, where Emperor Iyoas I appointed the deposed king governor of the province of Ras al-Fil, near the border with Sennar. However envoys from Sennar convinced Badi to return to Sennar where he was quietly murdered after an imprisonment of two years.[1]

He was ritually executed in 1769 and succeeded by his brother Isma'il[2]

Notes
  1. James Bruce, Travels to Discover the Source of the Nile (1805 edition), vol. 4 pp. 155f
  2. J.M. Reid, Traveller Extraordinary: The Life of James Bruce of Kinnaird (New York: Norton, 1968), p. 246
Preceded by
Badi IV		 King of Sennar Succeeded by
Isma'il
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.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.