175,938 Wikipedia Articles Preserved

Mohsin Esufally (1925-2000) was a Sri Lankan businessman.
Shaykh Mohsinali Shaykh Hassanaali Yusfali (Mohsinallu Hassanally Esufally) was born in Colombo, Sri lanka to Shk Hassanali Esufally (yusufali) and Asma bai Adamali (Wsufally). He was born on 27 December 1925 and was the second of 4 sons and 1 daughter to the above mentioned couple, Bohras ling in then Ceylon and later Sri Lanka. He was married to Sherebanu daughter of Kurbanhusain Attarwalla from Mumbai. He was a investor, businessman who was very active in his business and instrumental in help build Hemas group to new heights before he retired from active business life. He was a philanthropist and a supporter of religious and temporal causes. He was given the titles of Shaykh and Mullah and NKD by his holiness Syedna Moulana Mohammed Burhanuddin TUS Dai al Mutlaq of Dawoodi Bohras. He studied in Royal College. He travelled world wide and passed away Colombo on 25 January 2000 19 Shawal 1420 month after the Nikah of his 2 sons and months before his 75 birthday. The memory of Mr. Mohsin Esufally who passed away nearly a year ago will be cherished by many who looked upon him not merely as a kindly gentleman but as an entrepreneur who through his exceptional business skills made a significant contribution to the commercial life of our country.

Ritter von Krauss is the pen name of a former German army officer who was the author of a large number of novels based on his experiences as a tank man in the first and second world wars. There are at least 40 surviving von Krauss novels in manuscript form all of which were written between 1954 and 1968 during the time when the author lived in Argentina .
THE LEGAL ISSUES
As a result of extensive legal and contractual disputes involving the author’s family, the novels went unpublished until the first volume "Tiger Battalion" finally appeared in 2010 following the death of the last of von Krauss’ children. In legal terms this was the condition precedent event which finally paved the way for publication. The film "Twilight Of The Gods" which was based on von Krauss’ experiences in Normandy also appeared in 2011 with the author properly credited for the first time .
The main barrier to publication during the author’s life time was a legal challenge by the author’s estranged children based on the legitimate fear that the family might be identified and associated with von Krauss who was active in the campaign to restore pension and other legal rights to Waffen SS veterans. The publishing contracts contain strong non-disclosure clauses preventing the publishers from identifying the author. The von Krauss novels in manuscript form all were written between 1954 and 1968 during the time when the author lived in Argentina .
During the 1990’s during the negotiations for the sale of the rights to the novels the manuscripts and the supporting documentation as part of a legal due diligence exercise were studied and approved by Professor John Erickson author of "The Road To Stalingrad" and "The Road To Berlin" . Professor Erickson confirmed the authenticity of the manuscripts allowing the sale to proceed with the stipulation that the author could not be identified and that no publication could take place during the lifetime of any of the author’s children.
THE GREAT WAR
Originally von Krauss served in the great war where he was briefly part of the unit which drove the A7V, the first of German tanks, into battle . During the early years of the war von Krauss served as a motorcyle despatch rider and was an associate of Kurt Ludecke who was later to emerge as a member of Hitler’s inner circle .
THE 1920’s
From an aristocratic family von Krauss suffered the humiliation of being reduced to poverty in the 1920’s when hyper inflation wiped out the fortunes of both von Krauss personally and the entire family. Following the war von Krauss is known to have served in the Freikorps and to have spent time in Russia working on tank development . It is thought that his failure to find a place in the 100,000 man army of the Weimar Republic was the spur which led to his joining the Nazi party . It is known that von Krauss spent time in the SA where he knew Ernst Röhm as a result of an introduction by Ludecke. Both Ludecke and Röhm appear in fictionalised form in the von Krauss novel "Freikorps!"
POLITICAL VIEWS
As a result of his experiences in the hungry twenties von Krauss had become a committed socialist and undoubtedly harboured life long nationalist aspirations . He was well known as a strong supporter of the Grossdeutschland vision which led to the creation of The Third Reich. He was therefore an obvious and easy convert to National Socialism . However von Krauss was not an anti-semite and his novels display no trace of this aspect of national socialist policy. In common with Ludecke and many others von Krauss appears to assumed that the anti-semitic aspects of the party manifesto were a side show to the main event which was the unification of the German speaking peoples into a socialist state.
In the 1920’s Von Krauss came to a breach with Ludecke when a number of business ventures designed to revive the von Krauss family fortunes also came to grief leaving von Krauss penniless. It was this event which drove von Krauss to seek employment by joining the fledgling SS although he was initially highly disparaging describing himself as nothing more than “a glorified advertising sales man. “
In 1933 von Krauss joined Hitler’s regiment of body guards which later became the 1st SS Division Leibstandarte SS Adolf Hitler. It is known that von Krauss served throughout the war initially as an armoured car commander and later as a Tiger tank commander.
In 1945 von Krauss escaped capture by the Russians and also slipped out of a Britsh POW camp . As a result he was never officially de-nazified. Lacking the appropriate papers he was and unable to work in Germany and he began a game of cat and mouse with the German authorities which saw him serve briefly in the ranks of The French Foreign Legion from which he was invalided out suffering from malaria; an illness from which he ever fully recovered.

Note: The goal was to take a un-popular kernel then build a very user friendly, functional, versatile, and generally easy to use system off of it
Design
Baboon os was a project thought up by Timothy Charles McDermott, Marcus Neil Dessek, and Nathan "no one actually knows his middle name" Micheals. The original idea was that ALL other kinds of kernels were popular except the exokernel witch you don't really ever hear about so Nathan did some studying into the subject and found that not only was it a mildly lean kernel in general but it could be sized to accommodate most systems, which was one of our main concerns because when something isn't popular theres usually a reason.
Features
1. User friendly
2. Simple
3. Diverse
4. Flexible to fit the consumers needs
5. Developing viruses for it is on the brink of impossible ( no viruses )
6. popular software available Firefox,Google Chrome,Gimp, ect.
7. file conversion and transfer C.T.F or convert traceable files (if your mac breaks down you can transfer all the files to your baboon brand computer and it will automatically convert the files to a format that the computer can read.)
Opening view on exokernels
On traditional operating systems only trusted software such as privileged servers or the kernel can manage resources.
This thesis proposes a new approach, the exokernel architecture, which makes resource management unprivileged but
safe by separating management from protection: an exokernel protects resources, while untrusted applicationlevel
software manages them. As a result, in an exokernel system, untrusted software (e.g., library operating systems) can
implement abstractions such as virtual memory, file systems, and networking.
The main thrusts of this thesis are: (1) how to build an exokernel system; (2) whether it is possible to build a real
one; and (3) whether doing so a good idea. Our results, drawn from two exokernel systems , show that the
approach yields dramatic benefits. For example, Xok, an exokernel, runs a web server an order of magnitude faster
than the closest equivalent on the same hardware, common unaltered Unix applications up to three times faster, and
improves global system performance up to a factor of five.
The thesis also discusses some of the unusual techniques we have used to remove the overhead of protection. The
most unusual technique, untrusted deterministic functions, enables an exokernel to verify that applications correctly
track the resources they own, eliminating the need for it to do so. Additionally, the thesis reflects on the subtle issues in
using downloaded code for extensibility and the sometimes painful lessons learned in building three exokernelbased
systems.
Press
there hasn't been very much press for this Operating System because its kind of been kept secret until recently whe the information and the screenshots were posted on a linux forum with the original screenshots
Development
1.Multiplexing Storage
goal: allow each app to have its own file system, but on the same disk, and share file
systems when needed. challenge: have to figure out which blocks would go with which file system
Actual solution: UDFs: untrusted deterministic functions. idea: don’t try to understand the metadata -- just make the file system tell you in a
consistent way what the references are. Usage: file system author writes a function for each template type, owns-udfT, and gives
it to the kernel, which verifies that it is deterministic. The kernel then uses this function
to verify every proposed change to a block, so that libOS can’t change references
without the kernels permission.
o owns-udfT(block) -> list of (block #, template type) pairs
This returns the (deterministic) set of pointers in the input block
o Example: to add a data block, d, to an i-node, i, you call something like:
XN_allocate(i, d, changes to i)
XN would create i’ by applying the changes to i, and would confirm that:
owns-udfT(i’) = owns-udfT(i) + d
Access control for pages:
done when a block is mapped into an address space -- which means you don’t need to
check it on every access (bind + fast access)
Must also deal with write ordering for persistence (read the paper for this)
root list keeps the root block for each file system, from which XN can build the whole
tree (using owns-udfT recursively)
Splitting was one solution for the task problem the idea of keeping a un-editable copy of the original and then within that copy of the original split it into two the active copy and the non active copy "a small price to pay for better performance, yes an intelligent idea, no."
splitting
idea copy all of the pages that are not the active data/stack pages via copy-on-write, but
handle the hard ones directly
Thought overview
Principles: Separate protection and management: use the lowest level required for protection,
ideally the hardware level (e.g. disk blocks). Types of calls: allocation/revocation,
sharing, tracking/changing ownership
Explicit allocation and revocation
Use physical names: avoid translation from virtual names (and its consistency problem)
Expose information: typically read-only access to kernel state for making decisions in
the libOS
Four basic tools: [slightly different than written in the paper!]
software regions: like Multics segments -- sub-page protection and fault isolation
hierarchical capabilities, which must be passed on most system calls
bind hardware resources together (e.g. disk block and page frame that holds it)
download code (that can be verified) to control some policies. E.g. wakeup predicates
determine if a process is ready to run (without waking it up)