Vace-
I did not say you were not a good programmer, I haven't seen your code - I have no idea how good a programmer you are. I said I don't believe most (not all, most) virus writers are very talented. That does not mean there aren't some out there who are. There are two systems that pop immediately to mind that are frameworks to deliver exploits that are coded very well. However, I do believe these to be the exception, rather than the rule.
You brought it up that you were a "virus writer" (on a site that has a declared policy against anything of the sort), and keep referencing yourself as one. I'm just saying, in the security field that gets you little to no credit. I'm hoping that soon you will break away from identifying yourself as one, and move on to "developer, " or even "kernel developer" - I think that is not only a much more noble aspiration, but more legal and marketable as well ;).
And I never questioned your understanding of a kernel, I was attempting to re-interpret some of the concerns posted here - I think it would be great if you guys were able to create an OS, but to make one that will be able to compete with Windows and Linux, it will take several years, possibly several decades. If I questioned your understanding of a kernel, I would have linked you to howthingswork.c om or something else giving a more basic view, rather than kernel.org which holds the development and the source for the Linux kernel.
You can take the early versions of Linux and use them as a bit of a guide - not only see where they were going, but see what features had to be added in, what the most common problems were, what the most common exploits were, how they structured their code, how they versioned it, things like that that will help you a great deal with creating your project plan and timeline rather than just jumping into "creating a kernel" without any sort of plan, or exact idea of where you are going. You are a programmer - you should know that you need a clear goal - good documentation, good pseudocode, and defined goals/modules.
I'm sorry if my post came off as condescending or attacking, I was just attempting to clarify what I thought the main issue would be that you would run into (the commitment of spending that much time in front of your IDE/debugger). I think this is a great project and wish you and your team the best.
I did not say you were not a good programmer, I haven't seen your code - I have no idea how good a programmer you are. I said I don't believe most (not all, most) virus writers are very talented. That does not mean there aren't some out there who are. There are two systems that pop immediately to mind that are frameworks to deliver exploits that are coded very well. However, I do believe these to be the exception, rather than the rule.
You brought it up that you were a "virus writer" (on a site that has a declared policy against anything of the sort), and keep referencing yourself as one. I'm just saying, in the security field that gets you little to no credit. I'm hoping that soon you will break away from identifying yourself as one, and move on to "developer, " or even "kernel developer" - I think that is not only a much more noble aspiration, but more legal and marketable as well ;).
And I never questioned your understanding of a kernel, I was attempting to re-interpret some of the concerns posted here - I think it would be great if you guys were able to create an OS, but to make one that will be able to compete with Windows and Linux, it will take several years, possibly several decades. If I questioned your understanding of a kernel, I would have linked you to howthingswork.c om or something else giving a more basic view, rather than kernel.org which holds the development and the source for the Linux kernel.
You can take the early versions of Linux and use them as a bit of a guide - not only see where they were going, but see what features had to be added in, what the most common problems were, what the most common exploits were, how they structured their code, how they versioned it, things like that that will help you a great deal with creating your project plan and timeline rather than just jumping into "creating a kernel" without any sort of plan, or exact idea of where you are going. You are a programmer - you should know that you need a clear goal - good documentation, good pseudocode, and defined goals/modules.
I'm sorry if my post came off as condescending or attacking, I was just attempting to clarify what I thought the main issue would be that you would run into (the commitment of spending that much time in front of your IDE/debugger). I think this is a great project and wish you and your team the best.
Comment