a idea!
RE:a idea!
yep, sign me up
Just brainstorming:
Community Operating System (COS)
Ozone Operating System (cool O3 logo, O3 System --Object Oriented Operating System--)
...
Just brainstorming:
Community Operating System (COS)
Ozone Operating System (cool O3 logo, O3 System --Object Oriented Operating System--)
...
RE:a idea!
hmm i will take that into consideration... we need like the perfect time to do meetings and such... we will probley be using the Internet Relay Chat ((IRC)) for the meetings i aint saying you have to go out to get it... but i will think the best time since most of us are in the North American and Europe it will be morning for the USA and correct me if i am wrong afternoon/nighttime for Europe... sooo that will probley be the best time... which meetings will be held on saturdays mainly... sooo theres 1 point... meetings can be held on sundays but i will probley not be around that time, i am of a religion that does not believe in working on sundays, sooo theres what i say :/
RE:a idea!
It's already taken:
http://www.o3one.org/
Anyway, I gotta work in the morning, so I'm gonna hit the sack, but I'll see if I can think up some names for tomorrow, see what you guys things.
Cheers,
Jeff
http://www.o3one.org/
Anyway, I gotta work in the morning, so I'm gonna hit the sack, but I'll see if I can think up some names for tomorrow, see what you guys things.
Cheers,
Jeff
RE:a idea!
This seems to be turing into another one of those "Do you think it is possible" things. Length-wise, of course. I would be interested in a community OS.
~ TripleFault !)
~ TripleFault !)
RE:a idea!
QUOTE: "Do you think it is possible" things. END QUOTE
what does that mean? it doesnt seem to fit into the discussion maybe the begining but a community OS will bring the community together i think...
if your interested just wait and see what the end results are and/or join the team for a closer look
-Flich
what does that mean? it doesnt seem to fit into the discussion maybe the begining but a community OS will bring the community together i think...
if your interested just wait and see what the end results are and/or join the team for a closer look
-Flich
RE:a idea!
All right, where can I subscribe?
I think we should collect our e-mail addresses somewhere to keep them together... Here's mine:
[email protected]
http://www.manuelhohmann.de/mhohmann (mainly german, but the project pages ('Projekte') are in english)
Obviously this is really international teamwork.
My resume:
Languages:
ASM (2+ yrs)
C, C++, Pascal (3+ yrs)
Java (3+ yrs)
VBScript, JScript (3 yrs)
VB (4 yrs)
HTML (3 yrs)
XML/XSL (1 yr)
PHP (< 1 yr)
OSs:
Amiga Workbench (1 yr, hey, everyone has to start somewhere...)
Win/DOS (6 yrs)
Linux (1 yr)
currently developing XenOS (7 months)
OSDev:
bootloader
gdt,ldt,idt
paging
interrupts
text mode
simple keyboard driver
real time clock
COM/LPT (currently working on)
Besides that I'm a theorist: OS architecture, process management, strategies etc.
Some suggestions for project names (I don't know if they're already taken):
CryptOS (Come, Register Your Program Today - OS) (Greek for 'hidden')
HephaistOS (Here Every Program Has An Internal Segment Table - OS ... something like that) (master of the forge from the Greek myths)
Greek is a wonderful language for operating system names, since many words end with 'os'. (Of course these names should be written unsing greek letters.)
And for those who haven't laughed enough today: Object Oriented Programming System (OOPS)
I think we should collect our e-mail addresses somewhere to keep them together... Here's mine:
[email protected]
http://www.manuelhohmann.de/mhohmann (mainly german, but the project pages ('Projekte') are in english)
Obviously this is really international teamwork.
My resume:
Languages:
ASM (2+ yrs)
C, C++, Pascal (3+ yrs)
Java (3+ yrs)
VBScript, JScript (3 yrs)
VB (4 yrs)
HTML (3 yrs)
XML/XSL (1 yr)
PHP (< 1 yr)
OSs:
Amiga Workbench (1 yr, hey, everyone has to start somewhere...)
Win/DOS (6 yrs)
Linux (1 yr)
currently developing XenOS (7 months)
OSDev:
bootloader
gdt,ldt,idt
paging
interrupts
text mode
simple keyboard driver
real time clock
COM/LPT (currently working on)
Besides that I'm a theorist: OS architecture, process management, strategies etc.
Some suggestions for project names (I don't know if they're already taken):
CryptOS (Come, Register Your Program Today - OS) (Greek for 'hidden')
HephaistOS (Here Every Program Has An Internal Segment Table - OS ... something like that) (master of the forge from the Greek myths)
Greek is a wonderful language for operating system names, since many words end with 'os'. (Of course these names should be written unsing greek letters.)
And for those who haven't laughed enough today: Object Oriented Programming System (OOPS)
RE:a idea!
Well, here's a few:
if O3 is taken then O2 Oxygen Operating System
Iris Operating System (I'm searching into body parts now )
OpenWindows (legal debacle?)
Maybe something from Norse mythology:
Odin Operating System
Thor Operating System
Freya Operating System
Loki Operating System
To conclude I can add that this name could only be a temporary project name (some kind of a codename).
if O3 is taken then O2 Oxygen Operating System
Iris Operating System (I'm searching into body parts now )
OpenWindows (legal debacle?)
Maybe something from Norse mythology:
Odin Operating System
Thor Operating System
Freya Operating System
Loki Operating System
To conclude I can add that this name could only be a temporary project name (some kind of a codename).
RE:a idea!
If not OpenWindows, maybe OpenDoors (doesn't sound secure...)?
OO7 (has the license to kill processes - and is a codename), O-16 (ok, sounds like 16bit...), O-O-O (chess), C-14, OXOS (Open Extendable OS)...
Thor Operating System sounds powerful. What about LiviOS?
Iris OS already exists ('Development Links' on this site).
We should also discuss about supported platforms. Of course, i386 and successors, the IBM PC should be one target system. But there are lots of others. If the kernel is written in C(++), it should be easy to port it. Only system specific things (drivers, processor management) should be coded in assembler (x86, 68000, whatever). Some device dependent routines could use inline assembler, but then they have to be coded once for each system and compiler.
We should also find a common assembler syntax (Intel or AT&T). I prefer Intel, but some of you (Linux developers) may have a different view.
Since we are from different countries, it could be interesting to write a multilingual OS from the beginning (that's easier than adding this feature later). (A colleague told me when he sold a machine to france, he had to replace the 'Start' and 'Stop' signs by french ones.) Of course this applies only to user messages, not to function names (calling 'schreibef' instead of 'printf' would be horrible and useless).
OO7 (has the license to kill processes - and is a codename), O-16 (ok, sounds like 16bit...), O-O-O (chess), C-14, OXOS (Open Extendable OS)...
Thor Operating System sounds powerful. What about LiviOS?
Iris OS already exists ('Development Links' on this site).
We should also discuss about supported platforms. Of course, i386 and successors, the IBM PC should be one target system. But there are lots of others. If the kernel is written in C(++), it should be easy to port it. Only system specific things (drivers, processor management) should be coded in assembler (x86, 68000, whatever). Some device dependent routines could use inline assembler, but then they have to be coded once for each system and compiler.
We should also find a common assembler syntax (Intel or AT&T). I prefer Intel, but some of you (Linux developers) may have a different view.
Since we are from different countries, it could be interesting to write a multilingual OS from the beginning (that's easier than adding this feature later). (A colleague told me when he sold a machine to france, he had to replace the 'Start' and 'Stop' signs by french ones.) Of course this applies only to user messages, not to function names (calling 'schreibef' instead of 'printf' would be horrible and useless).
RE:a idea!
I can i18n (internationalize) it in Dutch (Belgian and Netherlands). I also prefer AT&T syntax cause I'm having a bit of a problem learning GCC's __asm__ __volatile__ (with the inputs and outputs stuff) but I could learn it as well.
Anyway, if we write the kernel to be portable, it will be portable (no inline asm, but external asm files in arch/ directory). I think it's best to target IA-32 (i386+) and later probably IA-64.
Thor Operating System sounds good to me too in fact... we could draw a large celtic battle hammer smashing windows and stuff lol
DR
Anyway, if we write the kernel to be portable, it will be portable (no inline asm, but external asm files in arch/ directory). I think it's best to target IA-32 (i386+) and later probably IA-64.
Thor Operating System sounds good to me too in fact... we could draw a large celtic battle hammer smashing windows and stuff lol
DR
RE:a idea!
Count me in. I will have spare time as am currently at university.
Email is [email protected]
Resume:
ASM 2+ years
C/C++ 1+ year
Delphi/Pascal 6+ Years
Html 6+ Years
Perl 4+ Years
OSDev:
32bit Pmode
Virtual memory management (paging)
Multi tasking
File system (my own + FAT12)
Own boot loader
Floppy/HDD drivers
svga graphics (basic)
All written using GCC and NASM.
and more...
knicos.
Email is [email protected]
Resume:
ASM 2+ years
C/C++ 1+ year
Delphi/Pascal 6+ Years
Html 6+ Years
Perl 4+ Years
OSDev:
32bit Pmode
Virtual memory management (paging)
Multi tasking
File system (my own + FAT12)
Own boot loader
Floppy/HDD drivers
svga graphics (basic)
All written using GCC and NASM.
and more...
knicos.
RE:a idea!
Thor OS is a good name, like to idea of the hammer, lol
Yes, no inline assembly, easier to convert to a different platform. I cant understand GCC __asm__ anyway.
My opinion: Keep the OS simple in structure, a MicroKernel. Also keep the file system layout simple (better than Linux anyway). In my OS, everything is a file (even more so than in linux), and this approach works very well.
Yes, no inline assembly, easier to convert to a different platform. I cant understand GCC __asm__ anyway.
My opinion: Keep the OS simple in structure, a MicroKernel. Also keep the file system layout simple (better than Linux anyway). In my OS, everything is a file (even more so than in linux), and this approach works very well.
RE:a idea!
someone should start by making a projekt hompage where the project status is reported and with its own forum, so u guys don´t need to talk about it here..
a homepage is also needed for uploading the diffrent versions of the os..
or??
a homepage is also needed for uploading the diffrent versions of the os..
or??