Compare commits

..

75 Commits

Author SHA1 Message Date
c18bf28d4b Change how big is xanvicos.png 2024-10-03 21:51:59 +02:00
d49920e22f Change how big is xanvicos.png 2024-10-03 21:51:59 +02:00
8e1d0374ee Change how big is xanvicos.png 2024-10-03 21:51:59 +02:00
2de2aae8d3 Add XanvicOS png in README 2024-10-03 21:51:59 +02:00
2584f99851 Add XanvicOS png in README 2024-10-03 21:51:59 +02:00
c14b852d35 Edited README 2024-10-03 21:51:59 +02:00
7fd1d354c3 Better README 2024-10-03 21:51:59 +02:00
d42b0f11ab Better README 2024-10-03 21:51:59 +02:00
66112b62d2 Now messages are in english 2024-10-03 21:51:59 +02:00
ab90e9cf83 Removed docs folder 2024-10-03 21:51:59 +02:00
d34eeecb4d Better README
I just wrote something new and corrected some errors
2024-10-03 21:51:59 +02:00
59a2a76d79 Better Contributing
Add the "What we want" section and changed "Hurt and/or harass someone
"
2024-10-03 21:51:59 +02:00
23c1765e2c License is now in markdown 2024-10-03 21:51:59 +02:00
1807f3951d Better security policy 2024-10-03 21:51:59 +02:00
b4ec69f757 2.0 -> 2.1 2024-10-03 21:51:59 +02:00
52ab3562e5 Better Contributing 2024-10-03 21:51:59 +02:00
022fcf7155 Changed Wiki link 2024-10-03 21:51:59 +02:00
3d9be52c2c Modified Contributing 2024-10-03 21:51:59 +02:00
4f3f3318ad Modified Contributing 2024-10-03 21:51:59 +02:00
f75260171a Idk 2024-10-03 21:51:59 +02:00
dfe05378bd Idk 2024-10-03 21:51:59 +02:00
VinceAle7082
6226aefaf5 Update README.md 2024-10-03 21:51:59 +02:00
42457395a0 boh 2024-10-03 21:51:59 +02:00
6882c401ac Hello World from printf and stage2 2024-10-03 21:51:59 +02:00
b7c291927b Hello world from printf! 2024-10-03 21:51:59 +02:00
7417029fdf boh 2024-10-03 21:51:59 +02:00
bc07c33645 Move XanvicOS png 2024-10-03 21:51:59 +02:00
a0a1030359 Add XanvicOS png 2024-10-03 21:51:59 +02:00
c56aae6af3 Update README.md 2024-10-03 21:51:59 +02:00
6960359367 Changed the message in main 2024-10-03 21:51:59 +02:00
f2a2931174 Update README.md 2024-10-03 21:51:59 +02:00
89e4c63514 Update README.md 2024-10-03 21:51:59 +02:00
cbcb18286c Update README.md 2024-10-03 21:51:59 +02:00
81b5ecfd77 Update README.md 2024-10-03 21:51:59 +02:00
1b93dd0b53 Update README.md 2024-10-03 21:51:59 +02:00
0e4fcfff28 Update README.md 2024-10-03 21:51:59 +02:00
4d49103f4d Update README.md 2024-10-03 21:51:59 +02:00
13297c2d9a Implemented printf! 2024-10-03 21:51:59 +02:00
2357008a54 Update issue templates 2024-10-03 21:51:59 +02:00
1d025c6d2f Update README.md 2024-10-03 21:51:59 +02:00
501f88ab81 Delete CNAME 2024-10-03 21:51:59 +02:00
efe31fbc4a Create CNAME 2024-10-03 21:51:59 +02:00
6f1307e079 Delete CNAME 2024-10-03 21:51:59 +02:00
ede60df3c2 Some things (still doesn't compile) 2024-10-03 21:51:59 +02:00
ca53f59ddf Update SECURITY.md 2024-10-03 21:51:59 +02:00
b622f62401 Update issue templates 2024-10-03 21:51:59 +02:00
c1e05eeae5 Update issue templates 2024-10-03 21:51:59 +02:00
ffc52de28a Create SECURITY.md 2024-10-03 21:51:59 +02:00
acd6ca6d66 Create CONTRIBUTING.md 2024-10-03 21:51:59 +02:00
d691d82077 Create CODE_OF_CONDUCT.md 2024-10-03 21:51:59 +02:00
9a1c8358b7 Create LICENSE
Add the GPLv3 License to XanvicOS
2024-10-03 21:51:59 +02:00
aecdc4a166 Update README.md 2024-10-03 21:51:59 +02:00
142c410867 Update README.md 2024-10-03 21:51:59 +02:00
2a86a0fe36 Create CNAME 2024-10-03 21:51:59 +02:00
8c3911fb59 Update README.md 2024-10-03 21:51:59 +02:00
a82379b1f3 Half implemented printf (doesn't compile) 2024-10-03 21:51:59 +02:00
3fbdaba8dc Doesn't work 2024-10-03 21:51:59 +02:00
726b08d95c Update README.md 2024-10-03 21:51:59 +02:00
22e0dce448 Idk why those files are here, so I removed them. 2024-10-03 21:51:59 +02:00
465e078a30 Half implemented printf() [DOESN'T COMPILE]
Idk what to write, a friend wants to play minecraft so... here is the code I wrote before him calling me.
2024-10-03 21:51:59 +02:00
0952cda630 I'm back (I reinstalled Gentoo) 2024-10-03 21:51:59 +02:00
91d85c003c Update README.md 2024-10-03 21:51:59 +02:00
bf7fc7b1e7 Update README.md 2024-10-03 21:51:59 +02:00
c07e9d7f3b Update README.md 2024-10-03 21:51:59 +02:00
de34f6ca69 Update README.md 2024-10-03 21:51:59 +02:00
16df2cee6f Update README.md 2024-10-03 21:51:59 +02:00
4fe22355fa Update README.md 2024-10-03 21:51:59 +02:00
bff356941a Update README.md 2024-10-03 21:51:59 +02:00
6ee5249bec Update README.md 2024-10-03 21:51:59 +02:00
54c081c68d Update README.md 2024-10-03 21:51:59 +02:00
ce295fac13 Update README.md
Mistyped
2024-10-03 21:51:59 +02:00
111814b5a0 Update README.md 2024-10-03 21:51:59 +02:00
1441704156 Update README.md 2024-10-03 21:51:59 +02:00
2a06f7d20c Update README.md 2024-10-03 21:51:59 +02:00
bf3b0283c4 Now the Stage 1 of the bootloader loads Stage 2 in memory.
I already wrote this but my computer crashed, so I won't write as much as before.
Now the bootloader is divided in stage1 and stage2, I added and edited some makefiles, stage 2 is written in Asm and C, the kernel isn't loaded into memory.

PS: after this commit I'll add another branch called "coding", the code in that branch won't work 100% because it's missing something, but I don't want to do a "mega commit" every time (those commits will still be in the main branch).
To everyone who wants to try XanvicOS or """using""" it, use the main branch, because the main branch's code is working.
I'll write this in the README.md right after this commit.
2024-10-03 21:51:59 +02:00
27 changed files with 1360 additions and 192 deletions

30
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@ -0,0 +1,30 @@
---
name: Bug report
about: Create a report to help us improve
title: 'Bug :'
labels: bug
assignees: VinceAle7082
---
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- XanvicOS version: [e.g. 0.1-pr1]
**Additional context**
Add any other context about the problem here.

View File

@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest a feature you want added into XanvicOS
title: 'Feature : '
labels: enhancement
assignees: VinceAle7082
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.

30
.github/ISSUE_TEMPLATE/vulnerability.md vendored Normal file
View File

@ -0,0 +1,30 @@
---
name: Vulnerability
about: Create a report of a vulnerability to help us improve
title: Vulnerability
labels: vulnerability
assignees: VinceAle7082
---
**Describe the bug**
A clear and concise description of what the vulnerability is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Desktop (please complete the following information):**
- XanvicOS version: [e.g. 0.1-pr1]
**Screenshots**
If applicable, add screenshots to help explain your problem.
**How is the vulnerability dangerous?**
This vulnerability is number/10
**Additional context**
Add any other context about the problem here.

2
.gitignore vendored
View File

@ -1 +1,3 @@
build/ build/
*.err
.vscode

132
CODE_OF_CONDUCT.md Normal file
View File

@ -0,0 +1,132 @@
# Contributor Covenant Code of Conduct
## Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.
We pledge to act and interact in ways that contribute to an restpectful, open, welcoming,
diverse, inclusive, and healthy community.
## Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, experiences, and culture
* Giving and gracefully accepting constructive feedback, or any feedback in general
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience, because we are just humans.
* Focusing on what is best not just for us as individuals, but for the overall
community
Examples of unacceptable behavior include:
* The use of too much sexualized language or imagery, and sexual attention or advances of
any kind
* Insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address,
without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.
## Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
vinceale7082@vinceale7082.is-a.dev or vinceale7082@gmail.com
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
## Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
### 1. Correction
**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology will be requested, unless it's not that big of a deal.
### 2. Warning
**Community Impact**: A violation through a single incident or series of
actions.
**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.
### 3. Temporary Ban
**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.
**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within the
community.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].
[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations

39
CONTRIBUTING.md Normal file
View File

@ -0,0 +1,39 @@
# What we want
XanvicOS is this little project that I write because I want to explore OS developing, and maybe make some friends.
So, I want that everyone in this project we'll respect each other, because without respect nothing can be done.
This project isn't nothing serius, just a hobby project.
# Here is what you can't do
## Violate the license
XanvicOS has a license, the GPLv3 license. If has been chosen by the author of something, it has been chosen for a reason. If you violate it you don't respect the idea of the creator about his code.
So, in respec of the author, don't violate it.
## Violate the Code of Conduct
Pretty much for the same reason as the license: it exist, it has been chosen, please respect the author and what he wants.
## Hurt and/or harass someone
If you don't understand why, we DON'T need more people like you. As I already wrote in "What we want", we need to respect each other, so let's do it, no?
## Do something stupid
"Doing something stupid" means a lot, by don't knowing what you are doing, to commit crimes. But it doesn't mean you can't make some errors here and there, we are humans after all.
# Here is what you need to do
## Respect each other
As I already said, this project is built off the idea of respecting each other while contributing. Without respect nothing can be done.
## Don't troll (too much)
You can make some trolls, but you can't make like 100 pull request about deleting all the code and call it "modernize the code"
## Think before doing
Self-explenatory, before doing something, think about what can be done better. If you can't think of anything better, then do it

675
LICENSE.md Normal file
View File

@ -0,0 +1,675 @@
# GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
<https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
## Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom
to share and change all versions of a program--to make sure it remains
free software for all its users. We, the Free Software Foundation, use
the GNU General Public License for most of our software; it applies
also to any other work released this way by its authors. You can apply
it to your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you
have certain responsibilities if you distribute copies of the
software, or if you modify it: responsibilities to respect the freedom
of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the
manufacturer can do so. This is fundamentally incompatible with the
aim of protecting users' freedom to change the software. The
systematic pattern of such abuse occurs in the area of products for
individuals to use, which is precisely where it is most unacceptable.
Therefore, we have designed this version of the GPL to prohibit the
practice for those products. If such problems arise substantially in
other domains, we stand ready to extend this provision to those
domains in future versions of the GPL, as needed to protect the
freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish
to avoid the special danger that patents applied to a free program
could make it effectively proprietary. To prevent this, the GPL
assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
## TERMS AND CONDITIONS
### 0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds
of works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of
an exact copy. The resulting work is called a "modified version" of
the earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user
through a computer network, with no transfer of a copy, is not
conveying.
An interactive user interface displays "Appropriate Legal Notices" to
the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
### 1. Source Code.
The "source code" for a work means the preferred form of the work for
making modifications to it. "Object code" means any non-source form of
a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users can
regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same
work.
### 2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey,
without conditions so long as your license otherwise remains in force.
You may convey covered works to others for the sole purpose of having
them make modifications exclusively for you, or provide you with
facilities for running those works, provided that you comply with the
terms of this License in conveying all material for which you do not
control copyright. Those thus making or running the covered works for
you must do so exclusively on your behalf, under your direction and
control, on terms that prohibit them from making any copies of your
copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the
conditions stated below. Sublicensing is not allowed; section 10 makes
it unnecessary.
### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such
circumvention is effected by exercising rights under this License with
respect to the covered work, and you disclaim any intention to limit
operation or modification of the work as a means of enforcing, against
the work's users, your or third parties' legal rights to forbid
circumvention of technological measures.
### 4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
### 5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these
conditions:
- a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
- b) The work must carry prominent notices stating that it is
released under this License and any conditions added under
section 7. This requirement modifies the requirement in section 4
to "keep intact all notices".
- c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
- d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
### 6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of
sections 4 and 5, provided that you also convey the machine-readable
Corresponding Source under the terms of this License, in one of these
ways:
- a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
- b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the Corresponding
Source from a network server at no charge.
- c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
- d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
- e) Convey the object code using peer-to-peer transmission,
provided you inform other peers where the object code and
Corresponding Source of the work are being offered to the general
public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal,
family, or household purposes, or (2) anything designed or sold for
incorporation into a dwelling. In determining whether a product is a
consumer product, doubtful cases shall be resolved in favor of
coverage. For a particular product received by a particular user,
"normally used" refers to a typical or common use of that class of
product, regardless of the status of the particular user or of the way
in which the particular user actually uses, or expects or is expected
to use, the product. A product is a consumer product regardless of
whether the product has substantial commercial, industrial or
non-consumer uses, unless such uses represent the only significant
mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to
install and execute modified versions of a covered work in that User
Product from a modified version of its Corresponding Source. The
information must suffice to ensure that the continued functioning of
the modified object code is in no case prevented or interfered with
solely because modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or
updates for a work that has been modified or installed by the
recipient, or for the User Product in which it has been modified or
installed. Access to a network may be denied when the modification
itself materially and adversely affects the operation of the network
or violates the rules and protocols for communication across the
network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
### 7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders
of that material) supplement the terms of this License with terms:
- a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
- b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
- c) Prohibiting misrepresentation of the origin of that material,
or requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
- d) Limiting the use for publicity purposes of names of licensors
or authors of the material; or
- e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
- f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions
of it) with contractual assumptions of liability to the recipient,
for any liability that these contractual assumptions directly
impose on those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions; the
above requirements apply either way.
### 8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
### 9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run
a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
### 10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
### 11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims owned
or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within the
scope of its coverage, prohibits the exercise of, or is conditioned on
the non-exercise of one or more of the rights that are specifically
granted under this License. You may not convey a covered work if you
are a party to an arrangement with a third party that is in the
business of distributing software, under which you make payment to the
third party based on the extent of your activity of conveying the
work, and under which the third party grants, to any of the parties
who would receive the covered work from you, a discriminatory patent
license (a) in connection with copies of the covered work conveyed by
you (or copies made from those copies), or (b) primarily for and in
connection with specific products or compilations that contain the
covered work, unless you entered into that arrangement, or that patent
license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
### 12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under
this License and any other pertinent obligations, then as a
consequence you may not convey it at all. For example, if you agree to
terms that obligate you to collect a royalty for further conveying
from those to whom you convey the Program, the only way you could
satisfy both those terms and this License would be to refrain entirely
from conveying the Program.
### 13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
### 14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions
of the GNU General Public License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies that a certain numbered version of the GNU General Public
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that numbered version or
of any later version published by the Free Software Foundation. If the
Program does not specify a version number of the GNU General Public
License, you may choose any version ever published by the Free
Software Foundation.
If the Program specifies that a proxy can decide which future versions
of the GNU General Public License can be used, that proxy's public
statement of acceptance of a version permanently authorizes you to
choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
### 15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
### 16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
### 17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
## How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively state
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper
mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands \`show w' and \`show c' should show the
appropriate parts of the General Public License. Of course, your
program's commands might be different; for a GUI interface, you would
use an "about box".
You should also get your employer (if you work as a programmer) or
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. For more information on this, and how to apply and follow
the GNU GPL, see <https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License. But first,
please read <https://www.gnu.org/licenses/why-not-lgpl.html>.

View File

@ -15,11 +15,10 @@ immagine_floppy: $(BUILD_DIR)/main_floppy.img
$(BUILD_DIR)/main_floppy.img: bootloader kernel $(BUILD_DIR)/main_floppy.img: bootloader kernel
dd if=/dev/zero of=$(BUILD_DIR)/main_floppy.img bs=512 count=2880 dd if=/dev/zero of=$(BUILD_DIR)/main_floppy.img bs=512 count=2880
mkfs.fat -F 12 -n "XanvOS" $(BUILD_DIR)/main_floppy.img mkfs.fat -F 12 -n "XANVOS" $(BUILD_DIR)/main_floppy.img
dd if=$(BUILD_DIR)/stage1.bin of=$(BUILD_DIR)/main_floppy.img conv=notrunc dd if=$(BUILD_DIR)/stage1.bin of=$(BUILD_DIR)/main_floppy.img conv=notrunc
mcopy -i $(BUILD_DIR)/main_floppy.img $(BUILD_DIR)/stage2.bin "::stage2.bin" mcopy -i $(BUILD_DIR)/main_floppy.img $(BUILD_DIR)/stage2.bin "::stage2.bin"
mcopy -i $(BUILD_DIR)/main_floppy.img $(BUILD_DIR)/kernel.bin "::kernel.bin" mcopy -i $(BUILD_DIR)/main_floppy.img $(BUILD_DIR)/kernel.bin "::kernel.bin"
mcopy -i $(BUILD_DIR)/main_floppy.img test.txt "::test.txt"
#Kernel #Kernel

View File

@ -1,17 +1,21 @@
<img src="https://vinceale7082.is-a.dev/xanvicos/xanvicos.png" width=50% height=50%>
Hey all, Vincenzo Aleskey Brocato (VinceAle7082) here! <br> Hey all, Vincenzo Aleskey Brocato (VinceAle7082) here! <br>
This is a little project where I try to make an OS just for fun <br> This is a little project where I try to explore OS developing just for fun!<br>
<br>
***What exacly is XanvicOS?*** ## What exactly is XanvicOS?
<hr> XanvicOS is a little project that I write when I have free time. I want to create an os that can run 16, 32 and 64 bit binaries, in future I hope I might be able to add a package manager, and in even more time maybe even linux binaries support. <br>
XanvicOS is the development name for this OS (the final name will be something like TearOS or SunShine OS), I'll try to make an OS with a 16 and 64 bit mode (like the Windows 9x series, excluding Windows ME). <hr> I also want to create a windows manager with some features that I like that I'll call SunShineWM. If you want to help, you can. <br>
In this OS will be possible to run natively linux executables, and there will be a source-based package manager (like Gentoo GNU/Linux's portage) <hr>
<br> ## Why are there 2 branches?
The main branch is the branch where I push my commits, but it can be full of bugs, doesn't compile, or even both. <br>
I created the stable branch so someone can try XanvicOS, without worring if the code compiles or not. <br>
Basically stable=normal, main=developement<br>
If you want to try XanvicOS, clone the stable branch, if you want to contribute, use the main one. <br>
Features will be added to the stable branch after the main one<br>
## How to compile XanvicOS?
[Read this](https://vinceale7082.is-a.dev/xanvicos/wiki/important_things.html)
***How can I contribute to this project?***
<hr>
You can fix issues, help me find a better name, add features to the kernel and other things, just add something to this project ;)
<br>
<hr>
<br> <br>
PS: if I wrote something wrong, sorry, English isn't my first language. PS: if I wrote something wrong, sorry, English isn't my first language.

23
SECURITY.md Normal file
View File

@ -0,0 +1,23 @@
# Security Policy
## What are the supported versions?
The supported version is the latest commit in the stable, and main branch.
If you want talk about a bug, vulnerability, or feature please make sure that you are on the latest release, beause maybe the issue has already been resolved or the feature has been added.
## Reporting a Vulnerability
Vulnerabilities are important, if you discover them, please report them immediately.
If you want to report it: create an issue, select vulnerability, read the template and edit it. Congratulations, you just reported a vulnerability!
## What order do we follow when fixing a vulnerability
We take vulnerabilities seriusly because they are security risks, but some vulnerabilities are more important and dangerous than others.
For this reason we have a n/10 scale in the vulnerability template.
We read every vulnerability, and fix them in order of importance.
## What security risks do I take when I use XanvicOS?
XanvicOS is just a hobby project. I try to fix all the bugs, but sometimes I don't discover some.
XanvicOS isn't being developed by a multi billion dollar company, but just by a student during his free time.
By using XanvicOS in a not controlled enviroment (like a VM) you basically accept the fact that by using it you are exposing yourself to some security risks.
If you find any, please report them. You'll help us.

BIN
XanvicOS.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 257 KiB

View File

@ -1,28 +0,0 @@
<head>
<title>Xanvico</title>
</head>
<body>
<style>h1 {text-align: center;}</style>
<h1>Xanvico</h1>
<hr>
<a href="https://vinceale7082.github.io/XanvicOS/en/index.html"><U>Home</U></a> | <a href="https://vinceale7082.github.io/XanvicOS/en/xanvico/xanvico.html"><U>XanvicOS</U></a>
<hr>
<h2>Welcome to the Xanvico's archive!</h2>
<h3>Why does this website exist?</h3>
I created this website because I wanted to.
<h3>What you'll be using this website for?</h3>
I'll use this website the things that I do.
<h3>What exacly is Xanvico and XanvicOS?</h3>
Xanvico is the name of our frind group.
<br>
XanvicOS is the operative system that we're working and I'll not use an existing kernel like the Linux or BSD ones because I hate my life.
<br>
The operative system will be a DOS like system that supports the x86_64 architecture that will execute 16,32 and 64 bit executable and the GNU/Linux (and if I can do it) and Windows ones.
<br>
In the future we'll think about developing source based package manager (like Gentoo's portage).
<br>
A GUI will be added in future (I hope it'll be a tiling window manager with some additions like an app menu, a bar like the waybar and others).
<br>
<hr>
<p>~Vincenzo Aleksey Brocato </p>
</body>

View File

@ -1,19 +0,0 @@
<head>
<title>Xanvico</title>
</head>
<body>
<style>h1 {text-align: center;}</style>
<h1>XanvicOS</h1>
<hr>
<a href="https://vinceale7082.github.io/XanvicOS/en/index.html"><U>Home</U></a> | <a href="https://vinceale7082.github.io/XanvicOS/en/xanvico/xanvico.html"><U>Xanvico</U></a>
<hr>
<h3>What are Xanvico and XanvicOS?</h3>
I already explained it in the home page, I don't wanna write it again.
<h3>How is going on the XanvicOS development?</h3>
Good
<h3>How will you call the XanvicOS's kernel?</h3>
Idk, help me.
<br>
<hr>
<p>~Vincenzo Aleksey Brocato</p>
</body>

View File

@ -1,13 +0,0 @@
<head>
<title>XanvicOS Website</title>
</head>
<body>
<h1>
<U>
Welcome to XanvicOS Website
</U>
</h1>
<hr>
<a href="https://vinceale7082.github.io/XanvicOS/it/index.html">Italian Website</a> | <a href="https://vinceale7082.github.io/XanvicOS/en/index.html">Engish Website</a>
<hr>
</body>

View File

@ -1,28 +0,0 @@
<head>
<title>Xanvico</title>
</head>
<body>
<style>h1 {text-align: center;}</style>
<h1>Xanvico</h1>
<hr>
<a href="https://vinceale7082.github.io/XanvicOS/it/index.html"><U>Home</U></a> | <a href="https://vinceale7082.github.io/XanvicOS/it/xanvico/xanvico.html"><U>XanvicOS</U></a>
<hr>
<h2>Benvenuto nell'archivio di Xanvico!</h2>
<h3>Perché questo sito esiste?</h3>
Ho creato questo sito perché avevo voglia di farlo.
<h3>A cosa serve questo sito?</h3>
Questo sito serve a pubblicare le peggio cavolate che faccio.
<h3>Cosa sono Xanvico e XanvicOS</h3>
Xanvico è il nome del gruppo di amici composto da me e altri 2 ragazzi.
<br>
XanvicOS è il sistema operativo su cui ̷s̷̷t̷̷i̷a̷̷m̷̷o̷ sto lavorando e non userò un kernel già esistente come quello linux o quello BSD perché odio la vita.
<br>
Il sistema operativo dovrebbe essere un sistema simile al DOS che supporta l'archittetura x86_64, ma che può avviarsi in una "DOS mode" (come Windows 9x, escludendo Windows ME) che in futuro sarà capace di eseguire nativamente gli eseguibili 16,32 e 64 bit e quelli di GNU/Linux e (se ci riesco) anche di Windows.
<br>
In futuro si penserà anche allo sviluppo di un package manager dove si può compilare tutti i pacchetti da sorgente (come Portage, package manager di Gentoo GNU/Linux, distro che sto attualmente usando) ma in futuro sarà anche possibile installare pacchetti già compilati dal sottoscritto.
<br>
Una GUI verrà aggiunta in futuro (spero che sia un tiling window manager con qualche aggiunta) e quando essa sarà stabile pubblicherò il codice sorgente su github in modo da farmi aiutare anche da altri.
<br>
<hr>
<p>~Vincenzo Aleksey Brocato</p>
</body>

View File

@ -1,19 +0,0 @@
<head>
<title>Xanvico</title>
</head>
<body>
<style>h1 {text-align: center;}</style>
<h1>XanvicOS</h1>
<hr>
<a href="https://vinceale7082.github.io/XanvicOS/it/index.html"><U>Home</U></a> | <a href="https://vinceale7082.github.io/XanvicOS/it/xanvico/xanvico.html"><U>XanvicOS</U></a>
<hr>
<h3>Cos'è Xanvico/XanvicOS?</h3>
L'ho già spiegato nella pagina Home, non ho voglia di scrivere.
<h3>A che punto XanvicOS?</h3>
Si avvia in nella modalità 16 bit grazie ad un floppy formattato con FAT12 da cui il bootloader carica il kernel che fa apparire sullo schermo il messaggio di Hello World.
<h3>Come chiamerai il kernel di XanvicOS (ad esempio Linus Torvalds ha chiamato il suo Linux)?</h3>
Non ne ho la più pallida idea. Aiutami!
<br>
<hr>
<p>~Vincenzo Aleksey Brocato</p>
</body>

View File

@ -256,11 +256,11 @@ puts:
.loop: .loop:
lodsb lodsb
or al, al ; verify if next character is n or al, al
jz .fine jz .fine
mov ah, 0x0E ; call bios interrupt mov ah, 0x0E
mov bh, 0 ; set page number to 0 mov bh, 0
int 0x10 int 0x10
jmp .loop jmp .loop
@ -274,16 +274,16 @@ puts:
;Mostra delle stringhe sullo schermo ;Mostra delle stringhe sullo schermo
msg_caricamento: msg_caricamento:
db 'Caricamento...', ENDL, 0 db 'Loading...', ENDL, 0
msg_errore_lettura: msg_errore_lettura:
db 'Errore del disco', ENDL, 0 db 'Reading disk error!', ENDL, 0
msg_stage2_non_trovato: msg_stage2_non_trovato:
db 'Stage 2 non trovato', ENDL, 0 db 'Stage 2 not found!', ENDL, 0
msg_stage2_trovato: msg_stage2_trovato:
db 'Stage 2 trovato', ENDL, 0 db 'Stage 2 found!', ENDL, 0
;Errori ;Errori

View File

@ -1,9 +1,8 @@
BUILD_DIR?=build/ BUILD_DIR?=build/
ASM?=nasm ASM?=nasm
ASMFLAGS?=-f obj ASMFLAGS?=-f obj
CC?=gcc
CC16?=/usr/bin/watcom/binl/wcc CC16?=/usr/bin/watcom/binl/wcc
CFLAGS16?= CFLAGS16?=-4 -d3 -s -wx -ms -zl -zq # -oneatxzh
LD16?=/usr/bin/watcom/binl/wlink LD16?=/usr/bin/watcom/binl/wlink
SOURCES_C=$(wildcard *.c) SOURCES_C=$(wildcard *.c)
@ -17,8 +16,8 @@ all: stage2
stage2: $(BUILD_DIR)/stage2.bin stage2: $(BUILD_DIR)/stage2.bin
$(BUILD_DIR)/stage2.bin: $OBJECTS_ASM $OBJECTS_C $(BUILD_DIR)/stage2.bin: $(OBJECTS_ASM) $(OBJECTS_C)
$(LD16) NAME $(BUILD_DIR)/stage2.bin FILE \{ $(OBJECTS_ASM) $(OBJECTS_C) \} OPTION_MAP=$(BUILD_DIR)/stage2.map @linker.lnk $(LD16) NAME $(BUILD_DIR)/stage2.bin FILE \{ $(OBJECTS_ASM) $(OBJECTS_C) \} OPTION MAP=$(BUILD_DIR)/stage2.map @linker.lnk
$(BUILD_DIR)/stage2/c/%.obj: %.c always $(BUILD_DIR)/stage2/c/%.obj: %.c always
$(CC16) $(CFLAGS16) -fo=$@ $< $(CC16) $(CFLAGS16) -fo=$@ $<

View File

@ -0,0 +1,12 @@
FORMAT RAW BIN
OPTION QUIET,
NODEFAULTLIBS,
START=entry,
VERBOSE,
OFFSET=0,
STACK=0x200
ORDER
CLNAME CODE
SEGMENT _ENTRY
SEGMENT _TEXT
CLNAME DATA

View File

@ -0,0 +1,22 @@
bits 16
section _ENTRY class=CODE
extern _cstart_
global entry
entry:
cli
mov ax, ds
mov ss, ax
mov sp, 0
mov bp, sp
sti
xor dh, dh
push dx
call _cstart_
cli
hlt

View File

@ -0,0 +1,12 @@
#include "stdint.h"
#include "stdio.h"
void _cdecl cstart_(uint16_t bootDrive)
{
const char far* far_str = "far string";
puts("Hello World from Stage 2!\r\n");
printf("Hello World from the printf library!");
for (;;);
}

View File

@ -1,56 +1,21 @@
org 0x0
bits 16 bits 16
section _ENTRY class=CODE
%define ENDL 0x0D, 0x0A extern _cstart_
global entry
;Codice del kernel entry:
start: cli
mov si, msg_helloworld mov ax, ds
call puts mov ss, ax
call premi_per_riavviare mov sp, 0
mov bp, sp
sti
xor dh, dh
push dx
call _cstart_
.halt:
cli cli
hlt hlt
puts:
; save registers we will modify
push si
push ax
push bx
.loop:
lodsb
or al, al
jz .fine
mov ah, 0x0E
mov bh, 0
int 0x10
jmp .loop
.fine:
pop bx
pop ax
pop si
ret
;Stringhe
msg_helloworld:
db 'Hello World dallo stage2 del Bootloader!', ENDL, 0
msg_premi_per_riavviare:
db 'Premi un tasto per riavviare...', ENDL, 0
;Errori
;Variabili
;Cose che non so dove mettere
premi_per_riavviare:
mov si, msg_premi_per_riavviare
call puts
mov ah, 0
int 16h
jmp 0FFFFh:0

View File

@ -0,0 +1,17 @@
#pragma once
typedef signed char int8_t;
typedef unsigned char uint8_t;
typedef signed short int16_t;
typedef unsigned short uint16_t;
typedef signed long int int32_t;
typedef unsigned long int uint32_t;
typedef signed long long int int64_t;
typedef unsigned long long int uint64_t;
typedef uint8_t bool;
#define false 0
#define true 1

View File

@ -0,0 +1,234 @@
#include "stdio.h"
#include "x86.h"
void putc(char c)
{
x86_Video_WriteCharTeletype(c, 0);
}
void puts(const char* str)
{
while(*str)
{
putc(*str);
str++;
}
}
void puts_f(const char far* str)
{
while(*str)
{
putc(*str);
str++;
}
}
#define PRINTF_STATE_NORMAL 0
#define PRINTF_STATE_LENGTH 1
#define PRINTF_STATE_LENGTH_SHORT 2
#define PRINTF_STATE_LENGTH_LONG 3
#define PRINTF_STATE_SPEC 4
#define PRINTF_LENGTH_DEFAULT 0
#define PRINTF_LENGTH_SHORT_SHORT 1
#define PRINTF_LENGTH_SHORT 2
#define PRINTF_LENGTH_LONG 3
#define PRINTF_LENGTH_LONG_LONG 4
int* printf_number(int* argp, int length, bool sign, int radix);
void _cdecl printf(const char* fmt, ...)
{
int* argp = (int*)&fmt;
int state = PRINTF_STATE_NORMAL;
int length = PRINTF_LENGTH_DEFAULT;
int radix = 10;
bool sign = false;
argp++;
while (*fmt)
{
switch (state)
{
case PRINTF_STATE_NORMAL:
switch (*fmt)
{
case '%': state = PRINTF_STATE_LENGTH;
break;
default: putc(*fmt);
break;
}
break;
case PRINTF_STATE_LENGTH:
switch (*fmt)
{
case 'h': length = PRINTF_LENGTH_SHORT;
state = PRINTF_STATE_LENGTH_SHORT;
break;
case 'l': length = PRINTF_LENGTH_LONG;
state = PRINTF_STATE_LENGTH_LONG;
break;
default: goto PRINTF_STATE_SPEC_;
}
break;
case PRINTF_STATE_LENGTH_SHORT:
if (*fmt == 'h')
{
length = PRINTF_LENGTH_SHORT_SHORT;
state = PRINTF_STATE_SPEC;
}
else goto PRINTF_STATE_SPEC_;
break;
case PRINTF_STATE_LENGTH_LONG:
if (*fmt == 'l')
{
length = PRINTF_LENGTH_LONG_LONG;
state = PRINTF_STATE_SPEC;
}
else goto PRINTF_STATE_SPEC_;
break;
case PRINTF_STATE_SPEC:
PRINTF_STATE_SPEC_:
switch (*fmt)
{
case 'c': putc((char)*argp);
argp++;
break;
case 's': if (length == PRINTF_LENGTH_LONG || length == PRINTF_LENGTH_LONG_LONG)
{
puts_f(*(const char far**)argp);
argp += 2;
}
else
{
puts(*(const char**)argp);
argp++;
}
break;
case '%': putc('%');
break;
case 'd':
case 'i': radix = 10; sign = true;
argp = printf_number(argp, length, sign, radix);
break;
case 'u': radix = 10; sign = false;
argp = printf_number(argp, length, sign, radix);
break;
case 'X':
case 'x':
case 'p': radix = 16; sign = false;
argp = printf_number(argp, length, sign, radix);
break;
case 'o': radix = 8; sign = false;
argp = printf_number(argp, length, sign, radix);
break;
default: break;
}
state = PRINTF_STATE_NORMAL;
length = PRINTF_LENGTH_DEFAULT;
radix = 10;
sign = false;
break;
}
fmt++;
}
}
const char g_HexChars[] = "0123456789abcdef";
int* printf_number(int* argp, int length, bool sign, int radix)
{
char buffer[32];
unsigned long long number;
int number_sign = 1;
int pos = 0;
switch (length)
{
case PRINTF_LENGTH_SHORT_SHORT:
case PRINTF_LENGTH_SHORT:
case PRINTF_LENGTH_DEFAULT:
if (sign)
{
int n = *argp;
if (n < 0)
{
n = -n;
number_sign = -1;
}
number = (unsigned long long)n;
}
else
{
number = *(unsigned int*)argp;
}
argp++;
break;
case PRINTF_LENGTH_LONG:
if (sign)
{
long int n = *(long int*)argp;
if (n < 0)
{
n = -n;
number_sign = -1;
}
number = (unsigned long long)n;
}
else
{
number = *(unsigned long int*)argp;
}
argp += 2;
break;
case PRINTF_LENGTH_LONG_LONG:
if (sign)
{
long long int n = *(long long int*)argp;
if (n < 0)
{
n = -n;
number_sign = -1;
}
number = (unsigned long long)n;
}
else
{
number = *(unsigned long long int*)argp;
}
argp += 4;
break;
}
do
{
uint32_t rem;
x86_div64_32(number, radix, &number, &rem);
buffer[pos++] = g_HexChars[rem];
} while (number > 0);
if (sign && number_sign < 0)
buffer[pos++] = '-';
while (--pos >= 0)
putc(buffer[pos]);
return argp;
}

View File

@ -0,0 +1,6 @@
#pragma once
void putc(char c);
void puts(const char* str);
void puts_f(const char far* str);
void _cdecl printf(const char* fmt, ...);

View File

@ -0,0 +1,48 @@
bits 16
section _TEXT class=CODE
global _x86_Video_WriteCharTeletype
_x86_Video_WriteCharTeletype:
push bp
mov bp, sp
push bx
mov ah, 0Eh
mov al, [bp + 4]
mov bh, [bp + 6]
int 10h
pop bx
mov sp, bp
pop bp
ret
global _x86_div64_32
_x86_div64_32:
push bp
mov bp, sp
push bx
mov eax, [bp + 4]
mov ecx, [bp + 12]
xor edx, edx
div ecx
mov bx, [bp + 16]
mov [bx + 4], eax
mov eax, [bp + 4]
div ecx
mov [bx], eax
mov bx, [bp + 18]
mov [bx], edx
pop bx
mov sp, bp
pop bp
ret

View File

@ -0,0 +1,6 @@
#pragma once
#include "stdint.h"
void _cdecl x86_div64_32(uint64_t dividend, uint32_t divisor, uint64_t* quotientOut, uint32_t* remainderOut);
void _cdecl x86_Video_WriteCharTeletype(char c, uint8_t page);