SUMMARY / RELATED TOPICS

Ascension of Jesus

The Ascension of Jesus is the physical departure of Christ from Earth into the presence of God in Heaven. In the Christian tradition, reflected in the major Christian creeds and confessional statements, God exalted Jesus after his death, raising Him as first of the dead, taking Him to Heaven, where Jesus took his seat at the right hand of God. In modern times a literal reading of the ascension-accounts has become problematic, as its cosmology is incompatible with the modern, scientific worldview. In Christian art, the ascending Jesus is shown blessing an earthly group below him, signifying the entire Church; the Feast of the Ascension is celebrated on the 40th day of Easter, always a Thursday. In Islam, Jesus was neither crucified nor raised from the dead, according to the Qur’an, he was rather saved by God and raised to Heaven. Luke-Acts, a single work from the same anonymous author, provides the only narrative account of the ascension. Luke chapter 24 tells how Jesus leads the eleven disciples to Bethany, a village on the Mount of Olives, where he instructs them to remain in Jerusalem until the coming of the Holy Spirit: "And it came to pass, while he blessed them, he parted from them, was carried up into heaven.

And they worshiped him, returned to Jerusalem with great joy." The biblical narrative in Chapter 1 of the Acts of the Apostles takes place 40 days after the resurrection. Acts 1 describes a meal at which Jesus commands the disciples to await the coming of the Holy Spirit. Jesus is taken up from the disciples in their sight, a cloud hides him from view, two men in white appear to tell them that he will return "in the same way you have seen him go into heaven." Luke and Acts appear to describe the same event, but present quite different chronologies, Luke placing it on the same day as the resurrection and Acts forty days afterwards. The Gospel of John has three references to ascension in Jesus' own words: "No one has ascended into heaven but he who descended from heaven, the son of man". In the first and second Jesus is claiming to be the apocalyptic "one like a son of man" of Daniel 7. Various epistles refer to an ascension, like Luke-Acts and John, to equate it with the post-resurrection "exaltation" of Jesus to the right hand of God.

There is a broad consensus among scholars that the brief ascension account in the Gospel of Mark is a addition to the original version of that gospel. In Christian theology, the death and exaltation of Jesus are the most important events, a foundation of the Christian faith; the early followers of Jesus believed that God had vindicated Jesus after his death, as reflected in the stories about his resurrection and exaltation. The early followers of Jesus soon believed that Jesus was raised as first of the dead, taken into Heaven, exaltated, taking the seat at the right hand of God in Heaven, as stated in the Apostles' Creed: "He ascended into heaven, is seated at the right hand of God the Father almighty." Psalms 110:1 played an essential role in this interpretation of Jesus' death and the resurrection appearances: "The Lord said to my Lord, "Sit at my right hand until I make your enemies your footstool." It provided an interpretative frame for Jesus' followers to make sense of his death and the resurrection appearances.

Ascension stories were common around the time of Jesus and the gospel-authors, signifying the deification of a noteworthy person, in Judaism as an indication of divine approval. Another function of heavenly ascent was as a mode of divine revelation reflected in Greco-Roman, early Jewish, early Christian literary sources, in which particular individuals with prophetic or revelatory gifts are thought to have experienced a heavenly journey during which they learned cosmic and divine secrets. Figures familiar to Jews would have included Enoch. Non-Jewish readers would have been familiar with the case of the emperor Augustus, whose ascent was witnessed by Senators; the cosmology of the author of Luke-Acts reflects the beliefs of his age, which envisioned a three-part cosmos with the heavens above, a flat Earth centered on Jerusalem in the middle, the und

Yap Day

Yap Day is a legal holiday in Yap State, one of the four states of the Federated States of Micronesia, held annually on March 1. It is a celebration of traditional Yapese culture. Common activities held during this time include traditional dances. In 1968, the Yap Islands Congress created Yap District Day to preserve Yapese culture; the date March 1 was chosen because it was considered the "most pleasant" season of the year because of its dryness. The event's name was changed to Yap Day in March 1979. In 1990, Yap Day activities included running, juggling, tug of war, coconut husking, basket weaving. Five dances were held. Most of these activities and dances were aimed at preserving the culture of Yap properly. In 1999, Yap Day was held as a three-day celebration starting on February 28; this was to accommodate for the children's school schedule, though observers noted that this coincided with Yap's tourist flight schedules. The opening ceremony was conducted entirely in Yapese. Different dances were held for the boys, girls and men, including standing dances, sitting dances, stick dances.

Activities included children's cultural games such as target shooting or basket weaving. Booths around the dance arena represented the outer islands of Yap, international organizations such as the Peace Corps. Other booths sold food. In 2002, Yap Day was broadcast throughout the Federated States of Micronesia on radio and throughout Yap proper on television; each year a different village provides both traditional and Western food. Before Yap Day, the villages rehearse traditional dances. Outer islanders are prohibited from participating in dances. Competitions include traditional tattooing, fresh produce contests, traditional games; the Yap Tradition Navigation Society hold an event where participants build and sail traditional canoes. On the last day, the Yap Visitors Bureau hosts a welcome reception to honor guests who traveled to the island. Micronesian Games Yap Day on Visit Yap Yap Day Festival, Micronesia on Pilot Guides

OpenZFS

OpenZFS is an umbrella project aimed at bringing together individuals and companies that use the ZFS file system and work on its improvements, aiming as well at making ZFS more used and developed in an open-source manner. OpenZFS brings together developers from the illumos, FreeBSD, macOS platforms, a wide range of companies. High-level goals of the project include raising awareness of the quality and availability of open-source implementations of ZFS, encouraging open communication about ongoing efforts toward improving open-source variants of ZFS, ensuring consistent reliability and performance of all distributions of ZFS. Illumos, derived from OpenSolaris, provides upstream source code for other ZFS implementations. While there are various differences between the illumos ZFS codebase and other open-source implementations of ZFS, OpenZFS is strategically reducing existing platform-related differences in order to ease sharing of the source code. Founding members of OpenZFS include Matt Ahrens, one of the main architects of ZFS.

The ZFS file system was developed by Sun Microsystems for the Solaris operating system. The ZFS source code was released in 2005 under the Common Development and Distribution License as part of the OpenSolaris operating system, it was ported to other operating systems and environments; as the FSF claimed a CDDL and GPL legal incompatibility in 2005, Sun's implementation of the ZFS file system wasn't used as a basis for the development of a Linux kernel module. As a workaround, FUSE, a framework that allows file systems to run in userspace, was used on Linux as a separation layer for which the licensing issues are not in effect, although with a set of its own issues that include a performance penalty. However, the April 2016 release of Ubuntu 16.04 LTS includes CDDL-licensed ZFS on Linux as a kernel module, maintained as a separate project, outside the Linux kernel mainline, claiming license compatibility. The following is a list of key events to the development of ZFS and its various implementations, leading to the creation of OpenZFS as an umbrella project: 2001: Closed-source development of ZFS started with two engineers at Sun Microsystems.

2005: ZFS source code was released as part of OpenSolaris. 2006: Development of a FUSE ZFS port for Linux started. 2007: Apple started porting of ZFS to Mac OS X. 2008: A port to FreeBSD was released as part of FreeBSD 7.0. 2008: Development of a native ZFS Linux port started, known as ZFS on Linux. 2009: Apple's ZFS project closed, the MacZFS project continued to develop the code. 2010: OpenSolaris was discontinued, resulting in the further development of ZFS on Solaris being no longer open-source. 2010: illumos was forked from OpenSolaris as its open-source successor, continued to develop ZFS in the open. Ports of ZFS to other platforms continued pulling in upstream changes from illumos. 2012: Feature flags were introduced to replace legacy on-disk version numbers, enabling easier distributed evolution of the ZFS on-disk format to support new features. 2013: Coexisting with the stable version of MacZFS, its prototype generation uses ZFS on Linux as the new upstream codebase. 2013: The first stable release of ZFS on Linux.

2013: Official announcement of the OpenZFS as an umbrella project. New features and fixes are pulled into OpenZFS from illumos and pushed into all ports to other platforms, vice versa. 2016: Ubuntu 16.04 includes the open-source ZFS file system variant by default Originally, version numbers of the pool and file system were incremented as new features were introduced, in order to designate the on-disk file system format and available features. This worked well when a single entity controlled the development of ZFS, this versioning scheme is still in use with the ZFS in Oracle Solaris. In a more distributed development model, having a single version number is far from ideal as all implementations of OpenZFS would need to agree on all changes to the on-disk file system format; the solution selected by OpenZFS was to introduce feature flags as a new versioning system that tags on-disk format changes with unique names, supports both independent format changes and format changes that depend on each other.

A pool can be moved and used between OpenZFS implementations as long as all feature flags in use by the pool are supported by both implementations. OpenZFS uses pool version 5000 to indicate the use of feature flags. Legacy version numbers still exist for pool versions 1–28, are implied by the pool version 5000. Future on-disk format changes are disabled independently via feature flags. Feature flags are exposed as pool properties, following these naming scheme rules: Format of the property name is feature@<org-name>:<feature-name> <org-name> is the reverse DNS name of the organization that developed the feature, ensuring unique property names. Property names can be shortened to feature @ <feature-name>. For example, feature@com.foocompany:async_destroy is a valid property name, it could be shortened to feature@async_destroy. Each pool feature can be in either enabled, or active state. Disabled features are those that will not be used, no on-disk format changes will be made. Enabled features are those that will be used, no on-disk format changes have been made yet, but the software may make the changes at any time.