New OS
That sounds like a single idea extended to an OS, a request for help because you actually have no clue how to do it on a forum where one of the basic rules is that you don't do that because we've had dozens to hundreds of these none of which end up with anything.
If you can't do it yourself and don't have anything to show to convince others to join (and a vision is *not* sufficient, as we've seen examples of that) don't bother posting.
If you can't do it yourself and don't have anything to show to convince others to join (and a vision is *not* sufficient, as we've seen examples of that) don't bother posting.
sigh...
At least you told me why you think I'm stupid... 
By the way: I do know what I'm doing!!! I know a fair amount of Assembly Language and C, I understand any tutorials completely and have done small things relating to OS developments here and there. This is a project to basically assemble everything together. I need help, because I have never designed anything this big before, and can't possibly do it all alone. At least give me hints, tips, links, samples OR SOMETHING before you you decide that I'm a worthless freak!!!!!
By the way: I do know what I'm doing!!! I know a fair amount of Assembly Language and C, I understand any tutorials completely and have done small things relating to OS developments here and there. This is a project to basically assemble everything together. I need help, because I have never designed anything this big before, and can't possibly do it all alone. At least give me hints, tips, links, samples OR SOMETHING before you you decide that I'm a worthless freak!!!!!
-
piranha
- Member
- Posts: 1391
- Joined: Thu Dec 21, 2006 7:42 pm
- Location: Unknown. Momentum is pretty certain, however.
- Contact:
You don't know what you're doing so research it.
If you quit with your 'great potential' because of a pointless project saying that others made you quit....then good for you. Is this a great project? AND, if it were a great project don't you think that the experienced people would've said something good?
-JL
Thats almost like saying "I will drop a refrigerator on my foot, even though everyone says it will hurt, just to prove them wrong!"I resent that!!! This is a serious project, by a serious person. If you don't agree that's fine, but don't be rude like that!! It's because of idiots like you that great projects are abandoned, and programmers with great potential quit! Thankfully, I am greatly devoted to this project, so if your to stupid to accomplish something like this don't put others down because of it. I WILL finish this project, and I'll do it just... to... piss... you... OFF!
If you quit with your 'great potential' because of a pointless project saying that others made you quit....then good for you. Is this a great project? AND, if it were a great project don't you think that the experienced people would've said something good?
-JL
SeaOS: Adding VT-x, networking, and ARM support
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
dbittman on IRC, @danielbittman on twitter
https://dbittman.github.io
We have discussed this before I think.
JamesM made a somewhat rude reply,I agree, and the author of this thread was hurt by it.
Now people recent the author because of the somewhat childish and whining reply by the author, thus the author is discouraged and we will never make a diference.
Well, I'm kinda drunk at the moment and I may just be talking nonsense, but I do know the feeling when you get a great idea, want to make a diference and so on an so forth, only to be meet with the reply: "you are a complete idiot, you are bad at what you do and you should feel bad!"
The new guy may or may not have been talking nonsense, but be nice anyway, he will learn sooner or later and if not, feel free to discourage him.
Once again, I may just be a drunk who haven't got a clue about anything.
JamesM made a somewhat rude reply,I agree, and the author of this thread was hurt by it.
Now people recent the author because of the somewhat childish and whining reply by the author, thus the author is discouraged and we will never make a diference.
Well, I'm kinda drunk at the moment and I may just be talking nonsense, but I do know the feeling when you get a great idea, want to make a diference and so on an so forth, only to be meet with the reply: "you are a complete idiot, you are bad at what you do and you should feel bad!"
The new guy may or may not have been talking nonsense, but be nice anyway, he will learn sooner or later and if not, feel free to discourage him.
Once again, I may just be a drunk who haven't got a clue about anything.
This was supposed to be a cool signature...
Re: New OS
This is a really dumb idea and you should stop posting.SphinCorp wrote:Memory auto correction: 1/2 of all RAM will be reserved in part for a system recovery dump, which will be 1 second or so behind the actual running system. Apps should also have partial dumps, and the ability to go "dormant" by extending it's dump. If an error occurs, the memory address is found, and the equivalent dump address is taken, then the error is corrected using dump info, which would be from 1 second ago.
now lets be nice guys, but i would suggest reading the book 'operating system design and implementation' by tanenbaum its a good thing to start with. right now i am reading ebooks on assembly and improving my skills with c to a point i am happy with before any kernel hacking or developement. there are alot of tutorials easily accessed using google and there are some great books on amazon not mention a wiki with great features.
os dev is so metal
If you are hoping to recruit people, you should act more professional.At least give me hints, tips, links, samples OR SOMETHING before you you decide that I'm a worthless freak!!!!!
Show us some of your work, then. I am sure members here would be more supportive if you can prove that you know what you are doing.By the way: I do know what I'm doing!!! I know a fair amount of Assembly Language and C, I understand any tutorials completely and have done small things relating to OS developments here and there.
Also, just knowing C and assembly language has nothing to do with OS development. They are just tools used to develop software, thats all.
Learn to manage large projects. This is not related to any specific field of programming, but rather software engineering. Probably the best book I read on software engineering is Code Complete--you should read it.I need help, because I have never designed anything this big before, and can't possibly do it all alone.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Sigh...
Well then off to the library for me I suppose...
I really have to stop using this forum... You guys are mean, nonsupporting, and rude. I came to you for advice and help and I regret it. And I though OSDDev.org was good...
Maybe I'll use the DevShed forums instead. At least they help me when I ask.
I really have to stop using this forum... You guys are mean, nonsupporting, and rude. I came to you for advice and help and I regret it. And I though OSDDev.org was good...
Maybe I'll use the DevShed forums instead. At least they help me when I ask.
I know you are still brain storming. So your design is very premature, but for it to be become appealing to others you will have to at some point elaborate on a lot of things like (but not limited too):
- How will these errors be detected?
- Does simply patching memory from a dump of one second ago solve a problem? What if the problem started more than one second ago, because the application took many seconds to finally start working with this location in memory (where you detect the error at)?
- What if the majority of problems are not memory errors, but bugs in the actual program so that memory patching from X seconds ago would have no affect?
- How can you patch a single region of memory for the application where you detected an error with out trashing other things or breaking the application all together? Where will the execution of the thread(s) for this application resume at?
...
You seem to have misunderstood me completely. This system is to protect the kernel at all costs, not the apps. The only reason the apps make a dump, is so that that kernel can find out exactly what went wrong, and cut the app out of memory, and then put it in dormancy ( minimum information stored by the kernel in the memory protection half for eventual reanimation of the thread / process) it is the application that must handle the error, retrieve the info, then parse it. The kernel should help with that. That way, the kernel will never panic, because it can retrieve past runtime info, and basic runtime info from a basic system thread constantly running in dormancy in the background. Does that make more sense? My teacher thought it was genius...
Re: ...
I understand that the applications make a dump so that the kernel can find out exactly what went wrong and put it in dormancy. I could see the application handling the error, retrieving the information, and parsing things -- from the dump I am assuming. That makes sense.SphinCorp wrote:You seem to have misunderstood me completely. This system is to protect the kernel at all costs, not the apps. The only reason the apps make a dump, is so that that kernel can find out exactly what went wrong, and cut the app out of memory, and then put it in dormancy ( minimum information stored by the kernel in the memory protection half for eventual reanimation of the thread / process) it is the application that must handle the error, retrieve the info, then parse it. The kernel should help with that. That way, the kernel will never panic, because it can retrieve past runtime info, and basic runtime info from a basic system thread constantly running in dormancy in the background. Does that make more sense? My teacher thought it was genius...
The first problem I have is if this problem happens and contaminates the application dump because it was not detected soon enough or before the dump occurs? I mean how can the application recover?
Also exactly how are you suspecting that an application will harm the kernel? Or, is the kernel somehow making a dump so in the case of an error it can use this system to recover also?
It sounds like a _GREAT_ idea, but exactly how can the kernel/application find out exactly what went wrong?