You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(2) |
Feb
(5) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Johan G. <jg...@di...> - 2002-03-11 12:25:28
|
I'm also reading the list. Regards Johan |
From: Sune F. <cr...@ti...> - 2002-03-10 22:35:47
|
On Wed, 6 Mar 2002 23:00:59 +0100 (CET), Simon Strandgaard <ne...@di...> wrote: > who is actualy suscribing to this mailing list? I am! Finally! *cheers*.. For those who don't know me, I think I was one of the 'founders' of this OS idea, along with Mr. Henrik Spuur Hansen. I have been developing a microkernel (loosely based on concepts from the late Jochen Liedtke's L4 kernel) for x486+ based PC's. The kernel is not finished, but does have most of it's primary features - some of them just need some work, and there are some potential problems with some also. To sum up the key elements: 1. Completely memory seperated based on a concept of 'address spaces'. An address space is a virtual memory, as seen from the threads in it. 2. Preemptive multithreading. A thread is an execution residing inside an address space. Each aspace can have any number (or zero) threads. At least one is needed to do any work though. 3. Security consitsting of the microkernel ensuring communication integrity and security. Inter thread communication is based on either memory mapping, granting or copying. 4. Fully paged and dynamic virtually mapped memory, with support for a higher level pager (ie. memory-to-disk) task. Well that's about it for the main parts. :). Regards, -- Sune |
From: Niels T. <Te...@im...> - 2002-03-07 21:15:10
|
On Wed, 6 Mar 2002 23:00:59 +0100 (CET) you, Simon Strandgaard <ne...@di...> wrote: > who is actualy suscribing to this mailing list? I am too. -- Niels, The Offspring Mailinglist www.image.dk/~teglsbo |
From: Dennis H. <de...@di...> - 2002-03-07 11:55:44
|
I am... On Wed, 6 Mar 2002, Simon Strandgaard wrote: > who is actualy suscribing to this mailing list? > please respond all of you! > > Regards > SimonS > > > _______________________________________________ > Metasystem-devel mailing list > Met...@li... > https://lists.sourceforge.net/lists/listinfo/metasystem-devel > _______________________________________________________________ Dennis Hansen [Email: de...@di...] Department of Computer Science, University of Copenhagen (DIKU) |
From: Simon S. <ne...@di...> - 2002-03-06 22:01:05
|
who is actualy suscribing to this mailing list? please respond all of you! Regards SimonS |
From: Niels T. <Te...@im...> - 2002-03-01 23:42:57
|
On Sun, 24 Feb 2002 23:41:05 +0100 (CET) you, Johan Gade <jg...@di...> wrote: > This is perhaps a good time to test this list.... > Who is recieving it??? Copy. -- Niels, The Offspring Mailinglist www.image.dk/~teglsbo |
From: Simon S. <ne...@di...> - 2002-02-27 18:02:31
|
He spoke primary about how unix was born and the history of IT. A story we have heard many times before, so im a bit dissapointed: nothing new. There were the usual DIKU people hanging around. I didnt see you Henrik? i tried to call you yesterday? I hoped there would have been talked more about the future instead of the past! SimonS |
From: Henrik N. S. H. <hn...@me...> - 2002-02-26 11:24:57
|
Hi everyone... As you can see I'm on the recieving end of this list... Regarding the Peter Salus event: I'm in on it... -if I can get the appropriate hours off from work (which = I probably can). Maybe Simon S. would be so kind as to contact me by phone and provide me = with the details (such as where the "room 0.10" is located)? Regards - Henrik N. Spuur Hansen =20 | Message: 1 | Date: Sun, 24 Feb 2002 23:41:05 +0100 (CET) | From: Johan Gade <jg...@di...> | To: met...@li... | Subject: [Metasystem-devel] Peter Salus: "What ever happened to OS = R&D" talk on ITC, wednesday |=20 | This is perhaps a good time to test this list.... |=20 | Who is recieving it??? Perhaps the above talk could be interesting = it's | on wednesday 27th at 15:00. |=20 | See: http://linuxlab.dk/calendar/events#20020227 |=20 | /Johan |
From: Simon S. <ne...@di...> - 2002-02-25 22:15:07
|
I dont know yet, i have project at DIKU in hci design, maybe im busy that day. But i can hope. SimonS On Sun, 24 Feb 2002, Johan Gade wrote: > This is perhaps a good time to test this list.... > > Who is recieving it??? Perhaps the above talk could be interesting it's > on wednesday 27th at 15:00. > > See: http://linuxlab.dk/calendar/events#20020227 |
From: Johan G. <jg...@di...> - 2002-02-24 22:41:27
|
This is perhaps a good time to test this list.... Who is recieving it??? Perhaps the above talk could be interesting it's on wednesday 27th at 15:00. See: http://linuxlab.dk/calendar/events#20020227 /Johan |
From: Simon S. <ne...@di...> - 2002-02-24 14:42:04
|
devel =3D things we have to develop ourselves port =3D things which can be ported with only a few modifications. system: * devel: microkernel * devel: library model * devel: exec library * thread management * resource manager for driver resources console: * drivers: * seriel input/output * keyboard, mouse * devel: shell filesystem: * devel: dos * devel: transaction server * drivers required: * legacy dma support * busmaster dma support * atapi * port: filsystem: macintosh, beos fs * port: zip/tgz kompresion networking: * drivers required: * 3com, realtek * port: protocolstack ??? maybe freebsd * port: afs filesystem graphic: * drivers required: * vesa * port: sdl, openptc, hermes, ?? * port: gui ?? |
From: Simon S. <ne...@di...> - 2002-01-29 14:22:33
|
I just started translating some of the danish cryos documents into = english. You can take a look at my first attempt. Im only halfway through..please correct me if im wrong somewhere. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/metasystem/text/uk/cryos/d= os/cry1.txt?rev=3D1.1&only_with_tag=3DMAIN&content-type=3Dtext/vnd.viewcv= s-markup It is most important documents which needs translation is: cry1.txt cry4.txt cry5.txt cry3.txt Simon Strandgaard |
From: Simon S. <ne...@di...> - 2002-01-11 13:55:29
|
There havnt been spoken much how the directory layout at sourceforge has to look like. So lets discuss how! As i proposed earlier in the "teams" mail, there should be some teams, each responsible for their own subprojects. In the directory hierarchy they each sould have its own directory to mess around with. We should avoid messing up the root directory, because its the first place newcomers start looking. If its non intuitive we will quickly be rejected. Furthermore its important to keep the dirnames as intuitive as possible. I have come up with some names that i think tells what their responsibility very good. directory hierarchy layouted as follow. ----------------------- ---------------------------- /core homedir for core team /graphics homedir for graphics team /language homedir for language team /ports homedir for ports team /security homedir for security team /system homedir for kernel team /microkernel /text homedir for system documentation /dk collection of idears in danish faq questions/answers hierarchy this file ----------------------- ---------------------------- I think the name "system" is better than "kernel", newbies dont know what a kernel is. Regards Simon Strandgaard |
From: Simon S. <ne...@di...> - 2001-12-13 11:36:27
|
Because of this projects size, there must be established some coordination. There are many subtasks which is partly able to be parallelized, example: in this early stage GUI development has nothing to do with the microKernel. Those tasks can easily be splited between several teams. I see following teams and their responsabilities: * Kernel - handles microKernel, exec.library. * Language - bytecode, IPC/RPC, distribyted systems, package management, system script, system language. * Driver - drivers, Filesystems, hardware probe. * Graphic - GUI, gadgets. * Library/API - think out/maintain APIs for libraries, datatypes, handlers. * Security - think out rolebased securitymodel. * Port - port software to the system. * Core - representences from all teams that ensures the system keep holding its course. During time there will be a high amount of communication between the groups. Some of us will be a little everywhere. Each team has its own representence/spiritual leader, who is member of the Core Team. Responsebilities/Team leaders as i see it: Allan - Graphics team Jesper - Language team Simon - Driver team or should it be API team? Sune - Kernel team Left needs to be assigned responsebility for the security and library teams. Regards SimonS |