Yafran

Yafran /ˈjɑːfrən/ (Berber: ⵢⴼⵔⴰⵏ Ifran, Arabic: يفرن Yafran, Italian: Iefren), also spelled Jefren, Yefren, Yifran, Yifrin or Ifrane, is a city in northwestern Libya, in the yefren District in the western Nafusa Mountains. Before 2007, Yafran was the administrative seat of the Yafran District.[3]

Yafran

يفرن
ⵢⴼⵔⴰⵏ

Iefren
City
Top: The view from the city of Yafran; Middle Left: Yellow blossom flowers blooming in spring; Middle right: Ancient church in Yafran; Bottom left: The ancient ruin town of Yafran Bottom right: The houses in Yafran covered with snow
Yafran
Location in Libya
Coordinates: 32°03′46″N 12°31′36″E
Country Libya
RegionTripolitania
DistrictJabal al Gharbi
Elevation678 m (2,224 ft)
Population
 (2012)[2]
  Total54,573
Time zoneUTC+2 (EET)
Area code(s)+218 421

Libyan civil war

Yafran people, as in other cities of Libya, have demonstrated against Gaddafi. Subsequently, Yafran was exposed to bombardment and siege by Gaddafi forces. As of May 2011, Gaddafi's forces had shut down the water system and blocked food supplies[4] and held the western part of the town with some 500 rebels in the eastern section of Yafran still resisting.[5]

Yafran fell to Gaddafi's forces sometime in late May or early June. The centre of the town was used as a position for "government tanks, artillery guns and snipers".[6] On 2 June, rebel forces retook the city center and started to clear the area of Gaddafi's forces.[7] On 6 June, an on-site Reuters journalist reported that the pro-Gaddafi forces were nowhere to be seen in or around the town.[8]

Notes

gollark: ... no.
gollark: Thus bad.
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)?

See also

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