Queeg OS copyrights?

[Tom]

Hi, I downloaded Queeg OS, and found no copyright things, like no GNU GPL. Is it ok if I c/p the OS's code into mine and put the GNU copyright? If so, I would need to put Copyright (C) 2002 Tom Fritz, and who else?

[frank]

Hi, I downloaded Queeg OS, and found no copyright things, like no GNU GPL. Is it ok if I c/p the OS's code into mine and put the GNU copyright? If so, I would need to put Copyright (C) 2002 Tom Fritz, and who else?

well if it is uncopyrighed you can...

but why should you copy someone else's code?
and why else did you make the bootsector stuff, just too boot someone else's code???

I suggest you start coding yourself instead of copying someone else's stuff ,

start with stdio.h (a putc and printf function) and some input/ouput functions, like I did
then start writing a driver (for your harddisk/floppy) which will load your user program (shell/gui)

Best,
Frank

[Tom]

Ok, well, I'll just use the code from Linux 0.1 and just include it, because it's GNU GPL

[frank]

huh?
I thought you we're writing your own os

[Tom]

I am, but why go to all the trouble to make all the simple printf stuff when using the code from other programs is what GNU GPL is about?

[frank]

I like making printf,putc and the other things
Got my own C libary now instead of glibc (gnu c libary)
Almost every kernel (Well a lot of kernels I saw) contain the glibc,
looks like not much people enjoy making a c libary (except for me ofcourse ))
You can just grab the glibc from thix (that kernel puts the gnu c lib in another dir called glibc)

Good luck,
Frank

[df]

i dont remember the copyright I put in Queeg... thats going back a few years... is that the Nasm version or the C version? Some of the files have my copyright in them, some have the GNU copyright in them (some of the libc stuff)...

as a whole entitiy, it didnt have a singular copyright over it.

I'll have to dig the code out tonight and have a proper look.

[Whatever5k]

I agree with Frank in doing my own libc. It's no fun just copying existing sources - it's not you, who wrote the OS then.

edit: I think it's ok to take over small functions like outb() and so on. It's also ok if you're inspired by someone's function, and write a similar one, with a similar concept (but not past&copy).

[crazybuddha]

A copyright notice is NOT the same thing as a copyright. In the US, at least, a notice isn't technically required -- you simply have an easier time in court if you've registered the copyright and display a notice. Someone's work is copyrighted simply by virtue of them creating it, and you must get permission from the copyright holder to "use" it publically. Software copyrights are a bit tricky, but generally speaking if the code is recognizably someone else's implementation, you're asking for trouble if you become a commercial success with it. If you must use someone's code verbatim in a publically distributed work, you would do well to ask permission. Courtesy, appreciation, and respect would suggest this as well. Otherwise, write your own implementation of the general solution. You'll learn more that way anyway.

[df]

the same exists in australia. anything I wrote is automatically copyright to me. I dont consider much if anything in Queeg is worthwhile of my copyright tho.

[Pype.Clicker]

same applies in Europe : by the act of writing something, you become the author of that thing and thus you have copyright on it. And that's why there is GPL and other 'copyleft' notices where you explicitly give some of your rights to other people...

[Tom]

I think I might have to make my own libary I can't get anything that's not mine to link. I'll just make my own libary & release it in pk0.5. ( It will be fun though, because I'm having fun making it now ).

Thank you,