Hi.
I'm just wondering...
Shall we have a deep research in some existing OSes before we start our own,or just have a general view on their important and creative ideas/concepts/architectures in advance,and have a detailed research in their implementations before we make those parts of our own?
Which do you prefer?I sometimes feel confused and even lost about that because I belong to the latter group...
When to look into other OSes' implementations?
Re: When to look into other OSes' implementations?
Hi,
IMHO the point of research is to discover these options. It doesn't really matter how you do the research, as long as you discover the options you would've chosen if you'd known all possible options
This makes it a gamble. If there were 10 options for one part of the kernel and you looked at one OS your chances are 10%. If you look at 20 OSs then some would be the same for that part of the kernel, and you might find about 80% of the options.
From here it depends how inventive you are. If there's 10 possible options and you only know of 5 of them, are you able to "invent" the option you really want from what you know about the other 5?
Cheers,
Brendan
Before you know exactly what you want, you need to know of everything you could possibly choose.m wrote:Shall we have a deep research in some existing OSes before we start our own,or just have a general view on their important and creative ideas/concepts/architectures in advance,and have a detailed research in their implementations before we make those parts of our own?
IMHO the point of research is to discover these options. It doesn't really matter how you do the research, as long as you discover the options you would've chosen if you'd known all possible options
This makes it a gamble. If there were 10 options for one part of the kernel and you looked at one OS your chances are 10%. If you look at 20 OSs then some would be the same for that part of the kernel, and you might find about 80% of the options.
From here it depends how inventive you are. If there's 10 possible options and you only know of 5 of them, are you able to "invent" the option you really want from what you know about the other 5?
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
- AndrewAPrice
- Member
- Posts: 2299
- Joined: Mon Jun 05, 2006 11:00 pm
- Location: USA (and Australia)
Maybe start with a general idea of operating systems and what you want, then do a lot of wikipediaing and read these forums..
My OS is Perception.
The most important thing you need, before you start coding your OS, is a strong idea of what the OS is for. People who want to just learn, by coding useally end up giving up very quickly or restarting the OS from scratch, which is fine, if that what you want.
But if you want your OS to end up being usefull eg: it is never finished, but useable, that strong idea is very important.
Take MenuetOS as a example, its goal was to prove you could code and fit a full asm, GUI, multi-tasking OS on a floppy. which it did, once it got there with no clear goal, it's lost its way. Remember that there are other types of OS other than desktops, it could be just as easy to say i want to prove you can write a OS in pascal.
If your idea is, i want to code a multi-tasking C OS, like linux, i have a suggestion just use linux.
But if you want your OS to end up being usefull eg: it is never finished, but useable, that strong idea is very important.
Take MenuetOS as a example, its goal was to prove you could code and fit a full asm, GUI, multi-tasking OS on a floppy. which it did, once it got there with no clear goal, it's lost its way. Remember that there are other types of OS other than desktops, it could be just as easy to say i want to prove you can write a OS in pascal.
If your idea is, i want to code a multi-tasking C OS, like linux, i have a suggestion just use linux.