Difference between revisions 627380842 and 627382192 on enwiki

< previous diff
next diff >
9front
{{multiple issues|
{{original research|date=March 2013}}
{{notability|date=March 2013}}
{{cite check|date=March 2013}}
{{unreliable sources|date=March 2013}}
}}
{{Infobox OS
|name                   = 9front
(contracted; show full) not support [[dynamic linking]], like Plan 9, which considering dynamic linking harmful. Plan 9 uses a nonstandard [[x86 calling conventions|x86 calling convention]], in which the caller saves, parameters are pushed onto the stack, and return values are placed in EAX, except for 64bit values and structs, which are written to a pointer that is passed as the first value. It is unknown whether it uses the [[X86_calling_conventions#System_V_AMD64_ABI|System V ADM64 ABI]] for [[x86-64]] like other platforms.


Like Plan 9, 9front does not have symbolic links. Although it has a full-featured kernel, 9front has less than 40 [[system call]]s.<ref name=plan9-syscalls>{{cite web|title=Plan 9 System Calls|url=http://aiju.de/misc/plan9-syscalls|website=aiju.de|accessdate=28 September 2014}}</ref>⏎
⏎
== History ==
Work on the [[fork (software development)|fork]] began in March 2011.<ref name="began" /> The project was announced under the name "Plan 9 from The People's Front of Cat-v.org",<ref name="nt-init" /> though subsequently it was referred to by the name "9front".<ref name="osnews-init" />

== Development ==
(contracted; show full)*[https://wiki.archlinux.org/index.php/9vx 9vx on ArchWiki]

[[Category:2011 software]]
[[Category:Computing platforms]]
[[Category:Embedded operating systems]]
[[Category:Plan 9 from Bell Labs]]
[[Category:Real-time operating systems]]
[[Category:Software forks]]