DisNCord Community Wiki - User contributions [en]

How Do I Get Involved

2024-09-08T19:06:16Z

Velleda: updated to reflect current situation

Before you get involved with contributing to the DisNCord Wiki, it is recommended to create an account, because we will log public IP addresses to monitor any changes added to the Wiki. Before creating an account though, please review the [[Project:Privacy policy|Privacy Policy]] and the Wiki's rules. Any violation of the rules will result in a permanent block from the Wiki.

Please note: At this time, account creation and anonymous editing is disabled for spam protection purposes. If you're interested in creating an account, please join the [[Discord|Discord server]] and open a ticket and we'll be sure to get it sorted!

==Creating An Account==
To create an account, click on [[Special:CreateAccount|Create account]] on the top right corner of the wiki. Next you will be shown a page to enter your username and password, enter both of these into the corresponding fields. You may add an email address in case if you lose your password, the email address will also be used for communications from other users and [[Project:Administrators|Administrators]]. There is an additional field to add your name for attribution. Lastly, to prevent automated spam account creations, solve the given CAPTCHA and click "Create your account". Now you can create and edit wiki pages, but please review the [[Project:Copyrights|Copyright Policy]] as all contributions to the Wiki will be licensed under the Creative Commons Attribution-ShareAlike. If you are new user on using the wiki software, see the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide].

== Uploading and Adding Images ==
To [[Special:Upload|upload]] or add images to a page, you must have the uploadaccess permission. This is to prevent anybody upload any images that violates the Wiki's rules. Contact an [[Project:Administrators|Administrator]] for upload permission.

Discord

2024-09-08T18:58:06Z

Velleda: something is better than nothing

If you're interested in joining the DisNCord community, you can join using the Discord invite link https://discord.gg/V8esNah.

User:Velleda

2022-09-04T04:40:26Z

Velleda: Created page with "hi!"

hi!

Homebrew OS Development

2022-09-02T17:36:21Z

Velleda: slight cleanup

This is a general summary of what OSes are being developed on DisNCord.

=== Open Computing Kit (OCK) ===
A joint project between Elisia, Sadmac356, Griffin, Europa, and others, [https://github.com/open-computing-kit Open Computing Kit] is an operating system that aims to be as GNU-independent as possible, including a [https://github.com/open-computing-kit/ockernel kernel written in Rust] and its [https://github.com/open-computing-kit/OCKcore own set of coreutils]. It is presently in the very early stages of active development.

=== SeshOS ===
Written by Mineman, SeshOS is one of the more esoteric OSes on DisNCord. It has the beginnings of a GUI and shell in the kernel, but no memory management.

SeshOS has support for one filesystem: tar ramfs.

Its source code is located at https://github.com/mine-man3000/SeshOS.
[[File:SeshOS2.png|thumb|SeshOS in its current state as of September 1st, 2022]]

=== Pics Of Bread Awful scRipting Interpreter System for Neat Architectures (POBARISNA) ===
Written by Krabs, POBARISNA is an operating system with a JavaScript-based microkernel design that currently only runs on PowerPC macs. There are prospective plans for ports to other "Neat Architectures" (which Krabs defines as "not a PC/BIOS/UEFI x86 system"), such as SPARC variants and ARM.

The project can be found on [https://gitlab.com/christiancrowle/pobarisna GitLab].

=== picotalk ===
Written by Waterpear, picotalk is an operating system written in embedded Smalltalk.

=== Rotom OS ===
Written by SED, Rotom OS is an operating system with little information to glean from anything except for its code and a few images.
It attempts to be as simple as possible, with ring 3 not being implemented.
[[File:RotomOS.png|thumb|Rotom OS]]

=== styx ===
Written by Sirocyl and others, styx is an operating system with many ideas, some of which will be listed here:
* Applications will be double-click to run, much like Windows or macOS.
* Libraries should live with their application in packaging, similar to Windows.
* Installation will be done through drag-and-drop, taken from macOS.
* The system will be as (trans)portable as possible, similar to Classic macOS.
* The word "styx" is not an acronym, nor will the operating system's governing body ever be comprised of one member.
* The system will be consent-first, something that flies in the face of traditional operating systems like Windows and macOS.
There are many more than are stated here in their Discord server, due to there being too many to list here effectively.

=== Astral ===
Written by Mathewnd, [https://github.com/Mathewnd/Astral Astral] is a monolithic kernel written in C. It is still at its early stages of development and has the beginnings of a userland (namely, mlibc with proper runtime dynamic loading support has been ported).

It is capable of running Bash, however all it can currently do is display the Bash prompt since it has no keyboard driver yet.

AIX on Itanium

2022-09-02T17:10:07Z

Velleda: tried to somewhat clean up clunky writing and excessive commas

[[File:Aix_ia64_cd_bootup.jpeg|600px|thumb|right|AIX/ia64 attempting to boot on a zx6000]]

AIX, IBM's own flavor of UNIX, has long been relegated to a portion of IBM's own hardware, most of which has been built around the PowerPC processor architecture. However, IBM worked in combination with SCO to create a port of AIX to Intel's Itanium architecture. This page documents current known information, attempts to boot, historical context, and more combining everything we known up to this point.

Right now, the dumped images do not boot on any available hardware or emulator. The only supported hardware is Intel's original Merced Software Development Vehicle, and unspecified "Itanium-based OEM systems"<ref>http://ibmfiles.com/ibmfiles/aix/itanium/aixia64_release_notes.pdf</ref> presumed to include the HP i2000; all early Itanium (Merced) hardware is very rare. Similar hardware is emulated by Simics<ref>https://www2.cs.sfu.ca/CourseCentral/886/fedorova/Tools/Simics-solaris/simics-3.0.25/doc/simics-target-guide-ia64/topic1.html</ref>, but the emulator was primarily intended to boot Linux and doesn't contain necessary firmware for booting AIX. However, there's some hope it might be possible to boot it on something else...

== Project Monterey ==
[[File:Project monterey summary.png|200|thumb|right|Project Monterey Summary]]

In the mid to late 90s, IBM alongside SCO looked at creating a new version of UNIX to act as a common base for UNIX on Intel's new 64-bit platform<ref>http://www.csee.umbc.edu/help/architecture/idfmontereylab.pdf</ref>. The idea was that there would be a common core creating the basis of the next System V release, which would then be licensed and branded by any interested parties.

With Itanium slated to be the successor of DEC Alpha, PA-RISC, and POWER, there was hope that UNIX would be successful on the new platform. For their part, HP-UX was ported to Itanium, and it's known that Sun also looked at porting Solaris to Itanium<ref>https://www.zdnet.com/article/sun-boots-solaris-on-itanium-hardware-5000103621/</ref>. However, the unexpected success of Linux displaced most of these plans, with IBM itself eventually embracing Linux<ref>https://www.cnet.com/tech/tech-industry/ibm-to-spend-1-billion-on-linux-in-2001/</ref>.

This set up the group for the later IBM vs SCO lawsuits, which partially alleged that IBM included components from Project Monterey in Linux. What is known from the case files is that there was very little demand for Project Monterey<ref>http://www.groklaw.net/article.php?story=2005082506163768</ref>, although it's not entirely clear if that's due to the relatively low adoption of Itanium in general, or due to the availability of HP-UX and Linux on the platform.

In mid-2022, a 2001 archive of the Project Monterey disks was uploaded to the Internet Archive which NCommander did initial explorations of, forming the initial basis of knowledge.

== NCommander's Initial Explorations ==

== Current Boot Status ==
Booting was attempted on several Itanium machines, mostly servers from the HP Integrity line featuring the zx1 chipset and Itanium 2 CPUs<ref>https://www.openpa.net/systems</ref>, and Compaq ProLiant DL590/64 featuring Itanium 1 CPUs and the Intel 82460GX chipset<ref>https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c00409158</ref> (the latter being shared with the aforementioned HP i2000<ref>https://www.openpa.net/systems/hp_i2000.html</ref>).

From the Integrity line, rx1620 and rx2620 were tested. Both go through the bootloader menu and start to load the kernel, but hang on a message referencing changing pProcLocalAPIC->len. Surprisingly, the closely related HP workstation zx6000, which is the predecessor of rx2600<ref>https://www.openpa.net/systems/hp_rx2600_rx2620.html</ref>, hangs before displaying the bootloader menu at a message saying "Booting from CDROM drive".

Booting on Compaq ProLiant DL590/64 gets further, likely thanks to it sharing its chipset with the HP i2000. However, the kernel fails to start, displaying various errors onto the serial console, including one about ID_SALCB_GETMEDIAINFO callback error (Could not load UNDI. Status = Not Found) and several console-IO-related variables missing (ConInDev, ConOutDev, ErrOutDev, ConOut, ConIn, ErrOut).

== Get Involved ==

==References==
<references />

[[Category:Software Preservation]]
[[Category:Itanium]]