Kernel name suggestions?

I’m terrible at coming up with names for things, has anyone got any name suggestions for a multi-processing kernel?

I’m leaning towards MPKernel. The SWIs are currently prefixed OSTask_. I could change that, too.

Just call it Steve.

K2

We could maybe draw inspiration from the names of existing systems. For example let’s consider “FreeBSD” and “Linux”, from those patterns you could get a name like “WillCOCKS”, or maybe “KernelWILLCOCKS”, or “Willcix”, etc.
Or taking inspiration from “Windows” you could get “Willcocks” (pronouncing the ‘o’ as you would in ‘windows’)
Or maybe taking the pattern “RISC OS” you could come up with “WillCOCKS OS”

Or TYTL – Thirty Years Too Late.

BartOS? (With the logo being a beard.)

K2 – I do feel a bit like I’ve been climbing a high mountain.

Patrick – for some reason I’ve never been too keen on emphasising the last syllable of my surname.

I think I’ll request K2, unless someone’s got a good reason not to.

The kernel names I could think of were Hydra, Medusa, Nucleus, PolyCore, MC (multi-core), SWMC, and SWMP (Multi-Processor).

K2 – seems fine.

K2 good name not quite the tallest but still a very hard mountain climb but do able with the right attitude.

On the mountain theme, how about Annapurna, which actually comprises 3 eponymous summits (Annapurna I, II and III): seems appropriate for what Simon’s kernel is intended to achieve.

Annapurna_SpawnTask? K2_SpawnTask.

I’m assuming I’m supposed to use the name of the chunk in the SWI names?

Not helpful for compact code, certainly :-(

Hydra, Medusa, Nucleus, PolyCore, MC (multi-core), SWMC, and SWMP (Multi-Processor)

All the good names, especially based upon classical stories and the like, have been used multiple times.

Hydra – was once a multi-processor add-on for the RiscPC, is now supposedly (quick Google) a battery-preserving version of Linux.

Medusa – a Python package to do with the brain-computer interface. Wake me up when it can handle us neurodiverse people, because humans have enough trouble, I don’t expect a machine to cope.

Nucleus – something to do with Linux and NTFS? Was also some sort of networking thing a while back.

PolyCore – is an American software outfit; is also some sort of multi-threaded thing for RISC-V.

Annapurna… Annapurna Labs (a software/hardware company) and AnnapuRNA (note the capitals) does something with “RNA-ligand complex structures”, whatever that means.

Still, I like Annapurna. It rolls off the tongue nicely. But, then, so does Steve. ;)

I’m assuming I’m supposed to use the name of the chunk in the SWI names?

Yes – it would be “Annapurna_SpawnTask”, however if you have a useful language that allows for definitions, you could simply define it as something useful to you, such as _SWISPAWN or whatever.
Or write it once in a function and call the function, so one doesn’t need to keep on typing out, for instance, TaskManager_TaskNameFromHandle which is even more of a mouthful.

Not helpful for compact code, certainly :-(

Not sure one should be writing such a thing these days, it isn’t the 1980s any more, whitespace and clarity are your friends. ;)

Well since “OS” is the prefix for the single core SWIs, here’s my suggest: for dual core it would be “DOS”, for multi core obviouslY “MOS”; AFAIK Amiga fans might hope for the triple core :-)

Nucleus – something to do with Linux and NTFS? Was also some sort of networking thing a while back.

There was also the RISC OS Nucleus

So, I’m picking up from this thread that something brief and distinct needs to be chosen rather than a project name.

K2 is good, with some pleasant mountain connotations. Alternatively, K2 could be thought of as Kernel version 2.

MC or MP are other options defined as Multi-Core and Multi-Processor.

Pick one, Simon.

K2 could be thought of as Kernel version 2

Glad someone picked up on this ;-)

Glad someone picked up on this ;-)

I did! Honest!