firekylin :wirting a new hobby os
firekylin :wirting a new hobby os
Hello,everyone .
now ,I am write a hobby os ,it has be support minix1 file system. an IDE driver , tty.
https://coding.net/u/liuxiaofeng/p/firekylin/git
now ,I am write a hobby os ,it has be support minix1 file system. an IDE driver , tty.
https://coding.net/u/liuxiaofeng/p/firekylin/git
Last edited by firekylin on Sun Jul 24, 2016 4:55 am, edited 1 time in total.
Re: firekylin :wirting a new hobby os
Hi,firekylin wrote:Hello,everyone .
now ,I am write a hobby os ,it has be support minix1 file system. an IDE driver , tty.
https://github.com/ximo-os/firekylin.git
- I'm sorry if I offend you, but with that english you aren't going to get contributers any time soon. You should learn proper english.
- Your code is technically copyrighted to you, without any open-sourceness.
- Your code has to be copyrighed to someone that actually exists, like
and notLinux Torvalds
.linust
If some of you people keep insisting on having backwards compatibitity with the stone age, we'll have stone tools forever.
My Hobby OS: https://github.com/heatd/Onyx
My Hobby OS: https://github.com/heatd/Onyx
Re: firekylin :wirting a new hobby os
Ok, Microsoft Gates.TheRussianFail wrote:- Your code has to be copyrighed to someone that actually exists, likeLinux Torvalds
Re: firekylin :wirting a new hobby os
TheRussianFail wrote:Hi,firekylin wrote:Hello,everyone .
now ,I am write a hobby os ,it has be support minix1 file system. an IDE driver , tty.
https://github.com/ximo-os/firekylin.git
- I'm sorry if I offend you, but with that english you aren't going to get contributers any time soon. You should learn proper english.
- Your code is technically copyrighted to you, without any open-sourceness.
- Your code has to be copyrighed to someone that actually exists, likeand notLinux Torvalds.linust
I am a chinese ,and I am very poor in English. I do not want to learn more English.
but , I really don't know does your mean . if it copyrighted to me , it can not open-source.
Re: firekylin :wirting a new hobby os
ROFLMAOmikegonta wrote:Ok, Microsoft Gates.TheRussianFail wrote:- Your code has to be copyrighed to someone that actually exists, likeLinux Torvalds
Re: firekylin :wirting a new hobby os
No, no, no. Willows Henry "Bill" Gates III.I for Workgroups.mikegonta wrote:Ok, Microsoft Gates.TheRussianFail wrote:- Your code has to be copyrighed to someone that actually exists, likeLinux Torvalds
Re: firekylin :wirting a new hobby os
Portions of your code, which you are claiming copyright to, are very similar to existing code. For example, the header file "minix_fs.h". Not only do you use the same name as existing header files but you also use the same names for many variables and structures in this file.
Now I realize that the status of header files is a little different to pure code files, and that "fair usage" is far laxer with them, but usage is different from claiming copyright.
I think you would be advised to review all of your files - header and code - to determine whether you have copied any part of them from elsewhere. If so, you need to acknowledge this and not claim copyright on the whole file. It would probably be easier to just use one of the common licences - BSD licence is my favourite - and not try to claim copyright on code that, let's face it, people are unlikely to want to rip off.
Now I realize that the status of header files is a little different to pure code files, and that "fair usage" is far laxer with them, but usage is different from claiming copyright.
I think you would be advised to review all of your files - header and code - to determine whether you have copied any part of them from elsewhere. If so, you need to acknowledge this and not claim copyright on the whole file. It would probably be easier to just use one of the common licences - BSD licence is my favourite - and not try to claim copyright on code that, let's face it, people are unlikely to want to rip off.
Re: firekylin :wirting a new hobby os
If not claim copyright on the whole file, but how to claim copyright on part of file. use bsd licence can avoid this .iansjack wrote:Portions of your code, which you are claiming copyright to, are very similar to existing code. For example, the header file "minix_fs.h". Not only do you use the same name as existing header files but you also use the same names for many variables and structures in this file.
Now I realize that the status of header files is a little different to pure code files, and that "fair usage" is far laxer with them, but usage is different from claiming copyright.
I think you would be advised to review all of your files - header and code - to determine whether you have copied any part of them from elsewhere. If so, you need to acknowledge this and not claim copyright on the whole file. It would probably be easier to just use one of the common licences - BSD licence is my favourite - and not try to claim copyright on code that, let's face it, people are unlikely to want to rip off.
use a license , should be put them in all files at first line, and they are too mare lines , I don't link this.
Re: firekylin :wirting a new hobby os
You should put copyright notices at the head of the file acknowledging all copyright holders. Or just don't bother claiming copyright.
This is one (only one) of the reasons that most people use one of the open source licences, particularly as their code is nothing special that others would want to make money from.
You should also carefully check the code that you are copying for any licensing notices; it may well specify that derivative works have to abide by the same licence that it does.
This is one (only one) of the reasons that most people use one of the open source licences, particularly as their code is nothing special that others would want to make money from.
You should also carefully check the code that you are copying for any licensing notices; it may well specify that derivative works have to abide by the same licence that it does.
Re: firekylin :wirting a new hobby os
At least in the US, this isn't true - you can copyright something under a pseudonym. I don't really know much about EU copyright laws, or whether pseudonyms are accepted internationally, though...TheRussianFail wrote:- Your code has to be copyrighed to someone that actually exists, like ...
Re: firekylin :wirting a new hobby os
Just about every nation on Earth is a signatory to the Berne Convention on Copyright which specifically allows copyright to be assigned to a pseudonym. (Article 15)
Re: firekylin :wirting a new hobby os
Really? Thats cool. My bad then. But then who has the copyright, the pseudonym or the actual person who made the content?iansjack wrote:Just about every nation on Earth is a signatory to the Berne Convention on Copyright which specifically allows copyright to be assigned to a pseudonym. (Article 15)
If some of you people keep insisting on having backwards compatibitity with the stone age, we'll have stone tools forever.
My Hobby OS: https://github.com/heatd/Onyx
My Hobby OS: https://github.com/heatd/Onyx
Re: firekylin :wirting a new hobby os
The person associated with the pseudonym, I presume. (i.e. The person who created the pseudonym.)
Copyright doesn't have to belong to the author. It can be assigned to another person or, more commonly, company or institution.
Copyright doesn't have to belong to the author. It can be assigned to another person or, more commonly, company or institution.
Re: firekylin :wirting a new hobby os
Copyright to pseudonyms are cool. Companies who would buy your work under a licence will try to find you,fail,and you wont get that 1M$ contract.
-
- Member
- Posts: 1146
- Joined: Sat Mar 01, 2014 2:59 pm
Re: firekylin :wirting a new hobby os
Presumably the pseudonym will include contact details, just like a real name would. One can hardly find someone by name alone.Boris wrote:Copyright to pseudonyms are cool. Companies who would buy your work under a licence will try to find you,fail,and you wont get that 1M$ contract.
When you start writing an OS you do the minimum possible to get the x86 processor in a usable state, then you try to get as far away from it as possible.
Syntax checkup:
Wrong: OS's, IRQ's, zero'ing
Right: OSes, IRQs, zeroing
Syntax checkup:
Wrong: OS's, IRQ's, zero'ing
Right: OSes, IRQs, zeroing