Jump to content
We owe you an explanation.
July 9: An important update for readers in Japan.

You deserve an explanation, so please don't skip this 1-minute read. It's Thursday, July 9. Our fundraiser won't last long, but fewer people are seeing our message this month and we might not hit our goal. If you've lost count of how many times you've visited Wikipedia this year, we hope that means it's given you at least ¥300 of knowledge. If everyone who finds Wikipedia useful gave ¥300, we'd hit our goal in a few hours.

It's been 25 years and Wikipedia is still free. It's still created by people, not machines, and we don't run ads or put up paywalls because we're not here to make a profit off your attention. In other words, it's still the internet we were promised.

Less than 2% of our readers donate, so if you've never given and Wikipedia has provided you with at least ¥300 worth of knowledge, donate today. If you are undecided, remember any contribution helps.

Proud host of Wikipedia and other free knowledge projects
How often would you like to donate?
Support Wikipedia year-round
Thanks for your generous support
Please select an amount (JPY)
The average donation in Japan is around ¥800.
  • Preferred Amount
Please select a payment method
Please select an amount (minimum ¥154)
We cannot accept donations greater than 3850000 JPY through our website. Please contact our major gifts staff at benefactors@wikimedia.org.
Please select a payment method
Can we follow up and let you know if we need your help again? The support and advice we get from donors in Japan is priceless, but many donors don't let us stay in touch. Will you commit today, this Thursday, to staying in touch with the Wikimedia Foundation?
Sorry to hear that. We don't email often; would you consider changing your mind?
Thanks for changing your mind! We’ll respect your inbox.
Your information is handled in accordance with our donor privacy policy, and each email you receive will include easy unsubscribe options.
Please select an email option
Almost done: Please, make it  monthly.
Monthly support is the best way to ensure that Wikipedia keeps thriving.
How would you like to be reminded?
Whether you give now or later, any contribution helps. We can send you an email or text message reminder to join the 2% of readers who donate.
🎉 Thank you for donating recently! 🎉
Your support means the world to us. We'll hide banners in this browser for the rest of our campaign.
Where your donation goes
Accountability and transparency are core values at the Wikimedia Foundation. We manage funds and resources to ensure that every contribution supports our mission. We have earned the Platinum Seal of Transparency from Candid (formerly GuideStar), and Charity Navigator awarded us its highest rating. You can read our most recent annual report for more information about our financial health.
45% $85.4M Technology 32% $60.7M Support 12% $22.8M Fundraising 11% $20.9M General $189.7M Total Funding
45% Investment in Technology

Nearly half of our budget goes toward supporting the technology that powers Wikipedia and other Wikimedia projects. We are constantly working to enhance the user experience for both contributors and readers, improve site security, and ensure reliable access to our websites globally. This infrastructure and product support sustain one of the top ten most visited websites in the world, all at a fraction of the cost of popular for-profit websites.

32% Support for Volunteers

The global reach of Wikimedia projects is made possible by the hard work of volunteers from across the globe. We provide grants, legal support, and other resources to help build vibrant volunteer communities. Additionally, we promote community engagement through outreach initiatives and advocate for the growth and protection of free knowledge.

12% Allocation to Fundraising Efforts

Donor support is crucial to sustaining Wikipedia and our other free knowledge endeavors. Our team is committed to efficient and effective fundraising throughout the year, ensuring that every contribution helps advance our mission.

11% General and Administrative Expenses

Operational costs are essential for the smooth management and governance of the Wikimedia Foundation. These expenses help us recruit top talent and support staff around the world, empowering them to carry out the mission of the Wikimedia Foundation.

Exec (Amiga)

From Wikipedia, the free encyclopedia
Exec
DeveloperCarl Sassenrath
OS familyAmigaOS
Working stateCurrent
Source modelClosed source
Initial release23 July 1985; 40 years ago (1985-07-23)
Latest release4.1 Final Edition Update 2 / 12 January 2021; 5 years ago (2021-01-12)
Marketing targetAmigaOS
Available inEnglish
Update methodCompile from source code
Supported platformsAmiga Motorola 68000 series (MC680x0, 68k)
Kernel typeMicrokernel
Default
user interface
Command-line interface
LicenseProprietary
Official websitewww.amigaos.net

Exec is the kernel of AmigaOS. It is a 13 KB multitasking microkernel which enabled pre-emptive multitasking in as little as 256 KB of memory (as supplied with the first Amiga 1000s). Exec provided functions for multitasking, memory management, and handling of interrupts and dynamic shared libraries.[1][2]

It acts as a scheduler for tasks running on the system, providing pre-emptive multitasking with prioritized round-robin scheduling. Exec also provides access to other libraries and high-level inter-process communication via message passing. Other comparable microkernels have had performance problems because of the need to copy messages between address spaces. Since the Amiga has only one address space, Exec message passing is quite efficient. The only fixed memory address in the Amiga software (address 4) is a pointer to exec.library, which can then be used to access other libraries. Exec was designed and implemented by Carl Sassenrath.[3]

Exec

[edit]

Unlike newer modern operating systems, the exec kernel does not run "privileged". Contemporary operating systems for the Motorola 68000, such as Atari TOS and SunOS used trap instructions to invoke kernel functions. This made the kernel functions run in the 68000's supervisor mode, while user software ran in the unprivileged user mode. By contrast, exec function calls are made with the library jump table, and the kernel code normally executes in user mode. Whenever supervisor mode is needed, either by the kernel or user programs, the library functions Supervisor() or SuperState() are used.

One limit of the Exec kernel was that an uncooperative program could disable multitasking for a long time, or indefinitely, by invoking Exec's calls Forbid() or Disable(), with no later invocation of corresponding Permit() or Enable(), causing the environment to run as one task. Multitasking could also be disabled by programs which, by software bug or intent, modify Exec's data structures or the code stored in random-access memory (RAM), possibly due to lack of memory management unit (MMU) support.

Even with such limits, Exec satisfies the definition of a preemptive kernel, using a preemptive scheduling routine and basing its interrupt intervals on a clock[4] rather than relying on the tasks to initiate a context switch as they do with co-operative multitasking.

Linux kernel developer Linus Torvalds once described the Amiga design as cooperative,[5] even though it uses a preemptive scheduling policy. The reason for that, he argued, was because the lack of [memory] protection between tasks, meant a task could hinder the system from operating preemptively. As tasks would need to choose not to stop the preemptive mechanism this would reduce to a kind of inverted cooperative system. This kind of conflation between protection and scheduler policy is nonstandard.

ExecSG

[edit]

ExecSG (Second Generation) is the kernel used by AmigaOS 4. This kernel was licensed by Hyperion Entertainment from Thomas Frieden and Hans-Jörg Frieden.[6] It exposes the same functions and structures as the Amiga Exec kernel but runs on PowerPC processors only. The ultimate origin of ExecSG is unspecified.

References

[edit]
  1. Sassenrath, Carl; Peck, Rob; Deyl, Susan (1986). Amiga ROM Kernel Reference Manual. Exec: Commodore Electronics Ltd. ISBN 0-201-11099--7.
  2. Holloway, Tim (January 1991). "The Object-Oriented Amiga Exec: The design of the Amiga operating-system kernel follows the rules of object-oriented programming". Byte. No. January 1991. McGraw-Hill. pp. 329–332, 234. ISSN 0360-5280.
  3. "Carl Sassenrath". Archived from the original on 2020-02-25. Retrieved 2022-05-23.
  4. Stallings, William (2009). Operating Systems - Internals and Design Principles (6th ed.). Upper Saddle River, NJ: Pearson Prentice Hall. ISBN 9788120336292.
  5. Torvalds, Linus (October 17, 1996). "Jalleen mahtava uusi keksinto m$oftilta" [Again, a great new invention from M$] (in Finnish). Newsgroup: sfnet.atk.sodat. Usenet: 545idd$3fj@linux.cs.Helsinki.FI. Retrieved February 25, 2011. The Amiga is "pseudo-pre-emptive" multitasking, which Amiga people call pre-emptive, but it really is not. WinNT in this regard, is light years ahead. ... due to lack of memory protection. Any program can take possession of the machine completely and thus prevent multitasking. Multitasking in Amiga is co-operative because it requires approval and help from running applications [... muistinsuojauksen puutteen vuoksi. Mikä tahansa ohjelma voi ottaa koneen haltuunsa täysin ja estää siten moniajo. Eli Amigan moniajo on kooperatiivinen, koska se vaatii sen että ajettavat ohjelmat hyväksyvät sen moniajon ja auttavat sitä]{{cite newsgroup}}: CS1 maint: deprecated archival service (link)
  6. "Justia: Hyperion Entertainment vs. Amiga Inc". Archived from the original on 2016-06-09. Retrieved 2014-10-15.
[edit]