SauOS: ready for code!

[imate900]

What I said I'll be filling in some code for SauOS, and I'd like some of the community to help me. Here's what I'm going to fill in:

• Multiboot header
• RWFS

I'll make a 0.01 pre-alpha in June.

Project page

[nekros]

Hey, I'd be glad to help you with RWFS. Oh, and your rwfs header is out of date. That's easily fixed since the complete version (won't be revised for awhile) is in my project wiki.(Look in my signature). I haven't written a detailed document for the filesystem yet so I wouldn't mind at all answering any questions you have.

[imate900]

Hey, I'd be glad to help you with RWFS. Oh, and your rwfs header is out of date. That's easily fixed since the complete version (won't be revised for awhile) is in my project wiki.(Look in my signature). I haven't written a detailed document for the filesystem yet so I wouldn't mind at all answering any questions you have.

Thanks. In my next commit to SauOS SVN, it'll have the updated header

[imate900]

Hey, I'd be glad to help you with RWFS. Oh, and your rwfs header is out of date. That's easily fixed since the complete version (won't be revised for awhile) is in my project wiki.(Look in my signature). I haven't written a detailed document for the filesystem yet so I wouldn't mind at all answering any questions you have.

Thanks. In my next commit to SauOS SVN, it'll have the updated header

The header is updated.

[imate900]

Hey, I'd be glad to help you with RWFS. Oh, and your rwfs header is out of date. That's easily fixed since the complete version (won't be revised for awhile) is in my project wiki.(Look in my signature). I haven't written a detailed document for the filesystem yet so I wouldn't mind at all answering any questions you have.

You are now a member of the project.

[imate900]

So far, so good. We only need loads of drivers, more Makefiles, POSIX and more 'fore we're done.

[imate900]

SauOS changes: it's now supposed to be POSIX-compilant WITH a few expections, there I might implement my way. I don't care if it's not POSIX-compilant by 0.1. This is planned for 1.0.

[JamesM]

Am I missing something or have you just got the contents of my tutorial in your source tree?

And also, I'm not sure what you've done to your svn repo but none of your files are showing up in the google web-based browser...

[imate900]

Am I missing something or have you just got the contents of my tutorial in your source tree?

I only recently removed it.

And also, I'm not sure what you've done to your svn repo but none of your files are showing up in the google web-based browser...

See note above. Yes, I base the OS off your tutorials. Let me know if this is wrong. Seriously, OS programming is harder without a basis (for me)

[neon]

See note above. Yes, I base the OS off your tutorials. Let me know if this is wrong. Seriously, OS programming is harder without a basis (for me)

Basing anything off of tutorials is bad.

[earlz]

See note above. Yes, I base the OS off your tutorials. Let me know if this is wrong. Seriously, OS programming is harder without a basis (for me)

Basing anything off of tutorials is bad.

I dont know about that.. I mean, usually I suppose cause it's usually noobs that do that.

But I mean how my OS is, I use tutorials to get started, and have reference docs to ensure I understand it, and where I could better the tutorial [for myself]. Everyone has to start somewhere, and kernel development, even after you have created a few can be very daunting to just jump into without some kind of guide(be it a tutorial, or a past OS project's code)

[imate900]

See note above. Yes, I base the OS off your tutorials. Let me know if this is wrong. Seriously, OS programming is harder without a basis (for me)

Basing anything off of tutorials is bad.

I dont know about that.. I mean, usually I suppose cause it's usually noobs that do that.

But I mean how my OS is, I use tutorials to get started, and have reference docs to ensure I understand it, and where I could better the tutorial [for myself]. Everyone has to start somewhere, and kernel development, even after you have created a few can be very daunting to just jump into without some kind of guide(be it a tutorial, or a past OS project's code)

I go with earlz... Without a guide, it is hard after all

[Combuster]

I agree with neon. Tutorials illustrate the the most straightforward method of doing things. They do not take into account software design, or any of the many other things that make a good program. In fact, all the good practices get removed to leave only that what is taught.

Which is why you shouldn't build on top of tutorial code.

[neon]

But I mean how my OS is, I use tutorials to get started, and have reference docs to ensure I understand it, and where I could better the tutorial [for myself]. Everyone has to start somewhere, and kernel development, even after you have created a few can be very daunting to just jump into without some kind of guide(be it a tutorial, or a past OS project's code)

References and documents are not related to tutorials. It is fine to use a tutorial as a reference, though.

In my opinion, basing your system off of a tutorial is never a good idea for the reasons Combuster pointed out. For myself as an example, I share no code between my OS dev series and real system. The reason being is because they have completely different design goals and intents.

I go with earlz... Without a guide, it is hard after all

Without a guide, anything is hard This is why software engineering and design is important

[earlz]

Well, maybe I have been using tutorials as a reference then.. I'm not sure.. (JamesM, your VFS system will never work in a 1TB disk that is full of files!! lol) I end up copying code for structures and contants and such from tutorials, but always find that I must code the functions to deal with them myself because the tutorial either doesn't have a good "in the end" design or it is inefficient, or I just plain don't like how it works and I could do better.

so maybe that is more for what I was meaning: tutorials should only be used as a reference for anything but your first little test OS.