firekylin :wirting a new hobby os
Re: firekylin :wirting a new hobby os
A normal copyright notice contains no contact details.
Re: firekylin :wirting a new hobby os
Correct me if I'm wrong, but I don't think there are restrictions on what you can put in a copyright notice. I don't know why doing something like:iansjack wrote:A normal copyright notice contains no contact details.
Code: Select all
/*
* Copyright (c) 2016 Foo Bar<[email protected]>
*/
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
-
- Member
- Posts: 95
- Joined: Thu Jan 29, 2009 9:13 am
Re: firekylin :wirting a new hobby os
s/normal/typical/
a Copyright Notice needs a name. A signature on a painting qualifies as a Notice. The Notice is not required to have Copyright protection, but it is a heads up to idiots who might think its public domain. There is no reason a Copyright Notice cannot include contact details, be written in Swahili, avoid certain letters of the alphabet, or even be written in verse and itself qualify as a created work.
a Copyright Notice needs a name. A signature on a painting qualifies as a Notice. The Notice is not required to have Copyright protection, but it is a heads up to idiots who might think its public domain. There is no reason a Copyright Notice cannot include contact details, be written in Swahili, avoid certain letters of the alphabet, or even be written in verse and itself qualify as a created work.
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: firekylin :wirting a new hobby os
Looks like a nice start.
You should add support for pipes; I tried doing:
And I didn't see anything on the serial port.
You should add support for pipes; I tried doing:
Code: Select all
echo Hello! > /dev/com1
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: firekylin :wirting a new hobby os
ok , I don't know all things, so I think all your are right.
but , In China ,Copyright to a pseudonyms and also to the real man .
anyhow , I have rewite the copyright with my real name, and put the code unde The BSD License . But I don't know is this right.
I also rewrite the README file . And I remove the stdio code port from MINIX , I real can not understand The license of MINIX, so
I just so this.
I remaned minix_fs.h to minix.h , but the struct and variable I have not change them , does this matter .
but I node to suppor '>' by my shell ,and /dev/com1 also , if you see some thing that is too bad .
but , In China ,Copyright to a pseudonyms and also to the real man .
anyhow , I have rewite the copyright with my real name, and put the code unde The BSD License . But I don't know is this right.
I also rewrite the README file . And I remove the stdio code port from MINIX , I real can not understand The license of MINIX, so
I just so this.
I remaned minix_fs.h to minix.h , but the struct and variable I have not change them , does this matter .
so,beautiful, I really want to know did you complie the code .omarrx024 wrote:Looks like a nice start.
You should add support for pipes; I tried doing:And I didn't see anything on the serial port.Code: Select all
echo Hello! > /dev/com1
but I node to suppor '>' by my shell ,and /dev/com1 also , if you see some thing that is too bad .
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: firekylin :wirting a new hobby os
Yes, I compiled the code. You don't have an ISO image, so how else would I have tried it?firekylin wrote:so,beautiful, I really want to know did you complie the code .
but I node to suppor '>' by my shell ,and /dev/com1 also , if you see some thing that is too bad .
You know your OS is advanced when you stop using the Intel programming guide as a reference.
-
- Member
- Posts: 396
- Joined: Wed Nov 18, 2015 3:04 pm
- Location: San Jose San Francisco Bay Area
- Contact:
Re: firekylin :wirting a new hobby os
i work with many chinese in our team. normally they are good hard working people but the biggest issue i have them is the imperfect English and shoddy quality. I always have problem in this respect. They dont like to improve their skills and quality. I see exactly same problems with your post, broken English, full of grammatical and punctuation errors.firekylin wrote: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 pibuters 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.
If you really think you want to think, work, perform and speak at a world-class then good English is a must besides software skills otherwise there will be always people disdain at you. Now in China it seems there are many tech opportunities these day so English skill may not matter (my understanding) but if you work in a English speaking country or with people, language improvement is incredibly important.
key takeaway after spending yrs on sw industry: big issue small because everyone jumps on it and fixes it. small issue is big since everyone ignores and it causes catastrophy later. #devilisinthedetails
Re: firekylin :wirting a new hobby os
I absolutely agree.ggodw000 wrote:i work with many chinese in our team. normally they are good hard working people but the biggest issue i have them is the imperfect English and shoddy quality. I always have problem in this respect. They dont like to improve their skills and quality. I see exactly same problems with your post, broken English, full of grammatical and punctuation errors.firekylin wrote:I am a chinese ,and I am very poor in English. I do not want to learn more English.TheRussianFail wrote: - I'm sorry if I offend you, but with that english you aren't going to get pibuters any time soon. You should learn proper english.
but , I really don't know does your mean . if it copyrighted to me , it can not open-source.
If you really think you want to think, work, perform and speak at a world-class then good English is a must besides software skills otherwise there will be always people disdain at you. Now in China it seems there are many tech opportunities these day so English skill may not matter (my understanding) but if you work in a English speaking country or with people, language improvement is incredibly important.
There is no reason why to not learn World International language.
Re: firekylin :wirting a new hobby os
Seem you do not understand what copyright means.firekylin wrote: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.
Copyright, consists of license, which is used to mark what can user/customer/etc. do and what it isn't allowed to do.
Plain copyright, will only allow user to use compiled code in personal use.
But copyright with specific license can be very different.
Re: firekylin :wirting a new hobby os
I have puts a license for firekylin.lukaandjelkovic wrote:
Copyright, consists of license, which is used to mark what can user/customer/etc. do and what it isn't allowed to do.
Plain copyright, will only allow user to use compiled code in personal use.
But copyright with specific license can be very different.
- moondeck
- Member
- Posts: 56
- Joined: Sat Dec 19, 2015 12:18 pm
- Libera.chat IRC: moondeck
- Location: The Zone, Chernobyl
Re: firekylin :wirting a new hobby os
What license is that? I can only see the standard "all rights reserved" AFAIK its not a license.
My operating system https://github.com/moondeck/hydrogen/
Re: firekylin :wirting a new hobby os
The BSD License . do I use error. I have a LICENSE file under the project. cant you help me.moondeck wrote:What license is that? I can only see the standard "all rights reserved" AFAIK its not a license.