Apologies
Posted: Tue Feb 19, 2002 12:00 am
Well, as some of you have probably noticed (and
Schol-R-LEA has blatently pointed out), I've been
quite a ***** lately.
I know it's not much of an excuse, but I had been
trying to quit smoking, and the girl I'm kinda
seeing, I see all of about twice a month...
But, anyway, that aside, I do apologize. It was
entirely unwarranted. Everyone here's supposed
to be working towards a common goal, so... I'll
try to be civil
In all honestly, though, I see a lot of people
that seem to think developing an operating system
is some trivial task, that any programmer can
accomplish. I still believe that you need a good
solid assembly background, and a working knowledge
of 386+ protected mode before starting a task
like developing an OS. A lot of people, in the
past, without these have simply crashed and
burned.
All I can say, to all the newbies in the field,
is to do your research. Chase has created an
excellent resource here at osdev.org, but it's
not the only one. Check around on the 'net (the
links off this page are invaluable) and grab some
books!!! There are some _great_ books out there
on protected mode, osdev and assembly (I can
grab some ISBNs if anybody's interested).
Also, Schol-R-LEAs right, everybody should read the
OS-Dev FAQ before posting. When 90% of the questions
are 'why does my boot sector triple fault upon
entering pmode?' there's very little room to get
into the (sorry..) more interesting discussions
like different memory models, protection schemes,
file systems, etc.
Lastly, as much as the GPL license allows for
reusing code, I would personally argue otherwise
in this field. To those asking for drivers to
various hardware, or boot sector code, etc., I
would suggest writting your own. Not only will
you gain a greater understanding, but you'll be
able to integrate everything so much more tightly.
By all means, check out code as a basis for your
own, but don't steal it. Afterall, just 'cuz you
can steal code, doesn't mean you understand it.
Cheers,
Jeff
PS: God I hope that doesn't sound bitchy... just
tryin' to help.
Schol-R-LEA has blatently pointed out), I've been
quite a ***** lately.
I know it's not much of an excuse, but I had been
trying to quit smoking, and the girl I'm kinda
seeing, I see all of about twice a month...
But, anyway, that aside, I do apologize. It was
entirely unwarranted. Everyone here's supposed
to be working towards a common goal, so... I'll
try to be civil
In all honestly, though, I see a lot of people
that seem to think developing an operating system
is some trivial task, that any programmer can
accomplish. I still believe that you need a good
solid assembly background, and a working knowledge
of 386+ protected mode before starting a task
like developing an OS. A lot of people, in the
past, without these have simply crashed and
burned.
All I can say, to all the newbies in the field,
is to do your research. Chase has created an
excellent resource here at osdev.org, but it's
not the only one. Check around on the 'net (the
links off this page are invaluable) and grab some
books!!! There are some _great_ books out there
on protected mode, osdev and assembly (I can
grab some ISBNs if anybody's interested).
Also, Schol-R-LEAs right, everybody should read the
OS-Dev FAQ before posting. When 90% of the questions
are 'why does my boot sector triple fault upon
entering pmode?' there's very little room to get
into the (sorry..) more interesting discussions
like different memory models, protection schemes,
file systems, etc.
Lastly, as much as the GPL license allows for
reusing code, I would personally argue otherwise
in this field. To those asking for drivers to
various hardware, or boot sector code, etc., I
would suggest writting your own. Not only will
you gain a greater understanding, but you'll be
able to integrate everything so much more tightly.
By all means, check out code as a basis for your
own, but don't steal it. Afterall, just 'cuz you
can steal code, doesn't mean you understand it.
Cheers,
Jeff
PS: God I hope that doesn't sound bitchy... just
tryin' to help.