<div dir="ltr">Wojciech,<br><div>1. Any Oberon implementation or application coming from a university has been by definition a research project. Just to see how far the boundaries could be pushed in a certain direction.</div><div>So I guess that is perpendicular on standardised easy portable application software.</div><div><br></div><div>2. The boundary between OS and application is non existent in Oberon. It is rather a spiderweb of modules. The web will over time extend itself into any direction depending on the need of the user / prograrmmer. So there is no OS API, but there are Module interfaces everywhere for you to use if you find a use for them.</div><div><br></div><div>3. So it follows that you hardly can port Modules, but you certainly can port brilliant ideas from the one system into any other.</div><div><br></div><div>("To be led up the garden-path" is an expression that describes Oberon very well.)</div><div><br></div><div>j.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 31, 2018 at 4:01 AM, Skulski, Wojciech <span dir="ltr"><<a href="mailto:skulski@pas.rochester.edu" target="_blank">skulski@pas.rochester.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Joerg:<br>
<br>
I agree with you that both V4 and S3 are not applications. I also agree that Oberon System is unique in that the distinction is blurry. Not "a little", but very much.<br>
<br>
Looking at Windows, MS Word is an application. Under Linux, nano is an application. Under Oberon System, is Edit an application or part of an OS? On one hand, it is a wordprocessor. So it is an app. On the other hand, an Element like Sisiphus is running inside Edit. So Edit is a framework which is providing an API. So it looks like a part of an OS. Now we can start to argue, which category Edit is belonging to.<br>
<br>
>From a conventional Linux standpoint, it is fair to say that parts of the kernel belong to the OS, while programs running in the user address space are apps. This distinction does not apply to the classic Oberon, where there is only one address space. We can say that everything is an application, or everything is an OS. We can also say that command modules are apps, while the imported modules are services. However, the top most command modules can get imported into some even more topmost modules, in principle ad infinitum. I am not sure, where to draw the boundary between the OS and the apps, or between servers and clients. I am not sure if trying to draw such a line is productive.<br>
<br>
My point was that both the ETH and V4 low level modules were intentionally quite similar to the original Oberon System modules. If so then it should be possible to plant both the ETH and Linz module trees on a common set of low level modules. It should also be possible to use ETH Edit to host Elements and Dialogs. These are the most important parts of V4.<br>
<br>
In my opinion, the benefit would be to mend the rift which somehow developed over the years between the two systems. I am not sure why the rift has developed, but I suspect it was not beneficial to the community.<br>
<br>
W.<br>
______________________________<wbr>__________<br>
From: Jörg [<a href="mailto:joerg.straube@iaeth.ch">joerg.straube@iaeth.ch</a>]<br>
Sent: Tuesday, January 30, 2018 2:07 PM<br>
To: Skulski, Wojciech; 'ETH Oberon and related systems'<br>
<div class="HOEnZb"><div class="h5">Subject: RE: [Oberon] Software Tracking Project<br>
<br>
Wojtek<br>
<br>
V4 and S3 are OSes not applications, although this differentiation is a<br>
little blurry in Oberon.<br>
In today's world, one could call your idea of running an OS on top of<br>
another OS virtualization.<br>
Or one could take the idea of Linux, with a common kernel and different OS<br>
flavors on top.<br>
<br>
In the operating system A2 (aka Bluebottle, aka AOS, written in<br>
ActiveOberon) it's possible to start the legacy Oberon OS as separate task<br>
in A2.<br>
<br>
So, your idea is well possible (in SW almost everything is possible :-) but<br>
needs quite some work.<br>
<br>
br<br>
Jörg<br>
<br>
-----Original Message-----<br>
From: Skulski, Wojciech [mailto:<a href="mailto:skulski@pas.rochester.edu">skulski@pas.rochester.<wbr>edu</a>]<br>
Sent: Tuesday, January 30, 2018 5:23 PM<br>
To: <a href="mailto:joerg.straube@iaeth.ch">joerg.straube@iaeth.ch</a>; ETH Oberon and related systems<br>
<<a href="mailto:oberon@lists.inf.ethz.ch">oberon@lists.inf.ethz.ch</a>><br>
Subject: RE: [Oberon] Software Tracking Project<br>
<br>
Joerg:<br>
<br>
do not you think that V4 and S3 can coexist on top of the same lower level<br>
layer? You could possibly launch either one or the other, or perhaps even<br>
both, though it would make little sense.<br>
<br>
Merging the two could possibly end the rift which was dividing the community<br>
for reasons which were hard to grasp from a distance.<br>
<br>
W.<br>
______________________________<wbr>__________<br>
From: Oberon [<a href="mailto:oberon-bounces@lists.inf.ethz.ch">oberon-bounces@lists.inf.<wbr>ethz.ch</a>] on behalf of Jörg<br>
[<a href="mailto:joerg.straube@iaeth.ch">joerg.straube@iaeth.ch</a>]<br>
Sent: Tuesday, January 30, 2018 9:35 AM<br>
To: 'ETH Oberon and related systems'<br>
Subject: Re: [Oberon] Software Tracking Project<br>
<br>
Hi<br>
<br>
Isn't this request like: I would like to see Linux and Android merged?<br>
They are similar: same language, same compiler (perhaps even same CPU, same<br>
Kernel). But some of the APIs differ.<br>
<br>
br<br>
Jörg<br>
<br>
-----Original Message-----<br>
From: Oberon [mailto:<a href="mailto:oberon-bounces@lists.inf.ethz.ch">oberon-bounces@lists.<wbr>inf.ethz.ch</a>] On Behalf Of<br>
Treutwein Bernhard<br>
Sent: Tuesday, January 30, 2018 2:35 PM<br>
To: '<a href="mailto:oberon@lists.inf.ethz.ch">oberon@lists.inf.ethz.ch</a>' <<a href="mailto:oberon@lists.inf.ethz.ch">oberon@lists.inf.ethz.ch</a>><br>
Subject: Re: [Oberon] Software Tracking Project<br>
<br>
>I would like to see V4 and ETH System merged.<br>
<br>
I think this is an excellent idea.<br>
<br>
Maybe UV4 would be a good starting point:<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_project
s_oberon_&d=DwIFAw&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpw
aGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=nqDS5CyXZIYdcOmlMrjf7C4H8TsPIxpkqLljZCQ
9wns&s=mdw5q5iL8zSP_3yaqyCEu0f1Qh2Sr6YOoIrvCsDEIrc&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__<wbr>sourceforge.net_project<br>
s_oberon_&d=DwIFAw&c=<wbr>kbmfwr1Yojg42sGEpaQh5ofMHBeTl9<wbr>EI2eaqQZhHbOU&r=uUiA_zLpw<br>
aGJIlq-_BM9w1wVOuyqPwHi3XzJRa-<wbr>ybV0&m=<wbr>nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx<wbr>pkqLljZCQ<br>
9wns&s=mdw5q5iL8zSP_<wbr>3yaqyCEu0f1Qh2Sr6YOoIrvCsDEIrc<wbr>&e=</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_obero
n_wiki_Home_&d=DwIFAw&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_z
LpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=nqDS5CyXZIYdcOmlMrjf7C4H8TsPIxpkqLlj
ZCQ9wns&s=BCyGCZty5GWxx7gh6dZCSwsvaF--hofW42_t0BG1DSM&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__<wbr>sourceforge.net_p_obero<br>
n_wiki_Home_&d=DwIFAw&c=<wbr>kbmfwr1Yojg42sGEpaQh5ofMHBeTl9<wbr>EI2eaqQZhHbOU&r=uUiA_z<br>
LpwaGJIlq-_<wbr>BM9w1wVOuyqPwHi3XzJRa-ybV0&m=<wbr>nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx<wbr>pkqLlj<br>
ZCQ9wns&s=<wbr>BCyGCZty5GWxx7gh6dZCSwsvaF--<wbr>hofW42_t0BG1DSM&e=</a><br>
<br>
--<br>
Bernhard<br>
<br>
--<br>
<a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailm
an_listinfo_oberon&d=DwIFAw&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=
uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx
pkqLljZCQ9wns&s=coZmt0X5ozfRQnjkEK2IiCurdoMPAHxU6iMuKVZ0Om8&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__lists.<wbr>inf.ethz.ch_mailm<br>
an_listinfo_oberon&d=DwIFAw&c=<wbr>kbmfwr1Yojg42sGEpaQh5ofMHBeTl9<wbr>EI2eaqQZhHbOU&r=<br>
uUiA_zLpwaGJIlq-_<wbr>BM9w1wVOuyqPwHi3XzJRa-ybV0&m=<wbr>nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx<br>
pkqLljZCQ9wns&s=<wbr>coZmt0X5ozfRQnjkEK2IiCurdoMPAH<wbr>xU6iMuKVZ0Om8&e=</a><br>
<br>
--<br>
<a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailm
an_listinfo_oberon&d=DwIFAw&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=
uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx
pkqLljZCQ9wns&s=coZmt0X5ozfRQnjkEK2IiCurdoMPAHxU6iMuKVZ0Om8&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__lists.<wbr>inf.ethz.ch_mailm<br>
an_listinfo_oberon&d=DwIFAw&c=<wbr>kbmfwr1Yojg42sGEpaQh5ofMHBeTl9<wbr>EI2eaqQZhHbOU&r=<br>
uUiA_zLpwaGJIlq-_<wbr>BM9w1wVOuyqPwHi3XzJRa-ybV0&m=<wbr>nqDS5CyXZIYdcOmlMrjf7C4H8TsPIx<br>
pkqLljZCQ9wns&s=<wbr>coZmt0X5ozfRQnjkEK2IiCurdoMPAH<wbr>xU6iMuKVZ0Om8&e=</a><br>
<br>
--<br>
<a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems<br>
<a href="https://lists.inf.ethz.ch/mailman/listinfo/oberon" rel="noreferrer" target="_blank">https://lists.inf.ethz.ch/<wbr>mailman/listinfo/oberon</a><br>
</div></div></blockquote></div><br></div>