Firebee/FireBee_Setup-Dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initial commit

Browse Source
This commit is contained in:
root
2023-06-12 09:14:09 +02:00
commit b4912f303e
2545 changed files with 209350 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
mint/1-19-c02/doc/COPYING Normal file
View File

@@ -0,0 +1,62 @@
COPYING CONDITIONS
------------------------------------------------------------------------------
This is a little complicated. First of all, I hope all things are handled
correctly. I don't want to bother anyone and I don't want to break any
copyright terms. If you think I made a mistake, please contact me.
The source code of the FreeMiNT CVS repository is based on several different
packages with different copying terms. I spent a lot of time lately doing the
same things on every package I updated over and over again. Furthermore, large
parts of the code were identical in some of the packages. So my main goal was
to get rid of such time consuming jobs, making FreeMiNT development much more
efficient.
CVS, a freely available source control system, helped a lot in achieving this
goal. It handles a unique source base (the CVS master tree) and records every
change with the exact date, the author and a changelog message. For that to
work I had to restructure the kernel source, the modules, and the tools into
one source hierarchy.
------------------------------------------------------------------------------
Here now a short summary which parts of the source tree apply to which
copyright terms.
======================================================================
==> Please look at the header of the files for exact informations! <==
======================================================================
This is just a hint how things are sorted. Files that fall under the GPL
are marked with `COPYING.GPL'.
sys/ - COPYING.MiNT if copyright is held by Eric Smith,
otherwise it's stated at the top of the file
adi - COPYING.GPL
gen-syscall/ - COPYING.GPL
sockets/ - Copyright Kay Roemer, see sys/sockets/COPYING
xif/ - various authors, see file header
xdd/ - COPYING.GPL if not stated otherwise
flop_raw/ - Public Domain
xfs/
ext2fs/ - COPYING.GPL
minixfs/ - Copyright S.N. Henson, see sys/xfs/minixfs/COPYING
nfs/ - Copyright Ulrich Kuehn, see sys/xfs/nfs/COPYING
ksocket/ - COPYING.GPL
tools/ - COPYING.GPL if not stated otherwise
minix/ - Copyright S.N. Henson, see sys/xfs/minixfs/COPYING
nfs/ - Copyright Ulrich Kuehn, see sys/xfs/nfs/COPYING
toswin2/ - Public Domain
xaaes/ - COPYING.GPL
Frank Naumann
<fnaumann@freemint.de>

340
mint/1-19-c02/doc/COPYING.GPL Normal file
View File

@@ -0,0 +1,340 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) 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
this service 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 make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. 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.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
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
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the 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 a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE 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.
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
convey 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 2 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, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision 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, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This 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 Library General
Public License instead of this License.

515
mint/1-19-c02/doc/COPYING.LGPL Normal file
View File

@@ -0,0 +1,515 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations
below.
When we speak of free software, we are referring to freedom of use,
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 this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
^L
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it
becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
^L
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control
compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
^L
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
^L
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
^L
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
^L
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
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
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply, and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License
may add an explicit geographical distribution limitation excluding those
countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser 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 Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
^L
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "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
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY 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
LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
^L
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms
of the ordinary General Public License).
To apply these terms, attach the following notices to the library.
It is safest to attach them to the start of each source file to most
effectively convey 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 library's name and a brief idea of what it
does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library 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
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper
mail.
You should also get your employer (if you work as a programmer) or
your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James
Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

54
mint/1-19-c02/doc/COPYING.MiNT Normal file
View File

@@ -0,0 +1,54 @@
MiNT is Not TOS: A Multitasking Operating System Extension for the Atari ST
Copyright 1990,1991,1992 Eric R. Smith.
Copyright 1992,1993,1994 Atari Corporation
All rights reserved.
MINT is still under development, and is probably still very
buggy. Treat it as you would any experimental software;
with extreme caution. Please read the following notice
carefully:
THE MiNT SOURCE CODE AND EXECUTABLES ARE PROVIDED FREE OF CHARGE,
AS IS. ATARI CORPORATION AND ERIC R. SMITH MAKE NO REPRESENTATIONS
OR WARRANTIES WITH RESPECT TO THIS CODE, AND IN PARTICULAR
SPECIFICALLY DISCLAIM ANY IMPLIED WARRANTIES OF
MERCHANTIBILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE THIS
CODE AT YOUR OWN RISK.
----------------------------------------------------------------------------
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION, AND MODIFICATION
1. Redistribution and use of unmodified verbatim copies of MiNT (in either
source or binary forms) are permitted, provided that the above copyright
notices and this documentation are distributed along with all such copies
of MiNT.
2. Redistribution of modified copies of the source code of MiNT, or
of binaries compiled from such modified copies, is permitted under
the terms of paragraph 1 above, provided also that the following
conditions are adhered to:
a) all modified files must carry prominent notices stating that
the files have been changed, and the date of any change; and
b) any binary compiled from a modified version of the MiNT source
code must, when executed, print a notice stating that it is
a modified version of MiNT; and
c) any work that is based in whole or in part on MiNT must be
licensed, at no charge, to all third parties under the terms
of this license. Mere aggregation of a work with another work
based upon MiNT does not cause it to fall under this clause.
In plain English: (1) means you can copy unmodified versions of MiNT,
with the only restriction being that you must preserve copyright
notices, and include a copy of this file. (2) Means that if you
modify your version of MiNT, you can redistribute it as long as
you keep the original copyright notices (including this file),
you clearly indicate that it is a modified version, and you agree
that anyone you give it to can also give it away. If you bundle
MiNT (or a modified version of MiNT) with another program, that
other program does not fall under the terms of this license, but
the copy of MiNT (or the modified version of MiNT) does, and hence
must remain freely copyable.

88
mint/1-19-c02/doc/ext2fs.txt Normal file
View File

@@ -0,0 +1,88 @@
ext2.xfs
========
This is a full working Ext2 filesystem driver for FreeMiNT. The complete
project is copyrighted by the GNU Public License.
It can read and write the actual ext2 version as implemented in Linux
for example. The partition size is not limited and the logical sector
size can be 1024, 2048 or 4096 bytes. The only restriction is that
the physical sector size is smaller or equal to the logical sector
size. The blocksize can be configured if you initialize the partition
with mke2fs.
The next good thing is that it's a lot faster as the MinixFS. The Ext2
has a very good structure that is designed for maximal speed and avoids
also fragmentation automatically.
If you have any problems send me an e-mail or write to the MiNT list.
I'm very interested in feedback and suggestions.
Requirements:
-------------
Ext2.xfs requires a XHDI compatible harddisk driver.
It also requires a recent FreeMiNT version (at least 1.15.1 beta 0.6).
The right version is checked on startup.
There are now two versions: ext2.xfs and ext2_st.xfs. The ext2.xfs
version requires at least a 68020 processor. If you have a 68000
processor you must use the ext2_st.xfs version.
It's your task to verify that you use the right version!
NOTE: The 68000 version isn't tested. That's why it's not included here!
If you are interested to test the 68000 version and the 68000 e2fsprogs
please contact me. I don't have a 68000 based ATARI and can't test
it self.
Tips & Tricks:
--------------
Make sure that your ext2-partition is recognised by the harddisk
driver. You can achieve this by either changing its partition ID to
e.g. RAW or by telling your driver to serve the current partition
name (e.g. LNX).
The default cache of the new buffer cache in FreeMiNT is small. To
get a better performance of the Ext2.xfs increase the buffer cache
(I suggest at least a size of 500kb as minimum).
Also use the latest e2fsprogs (version 1.14). These version work
much better as the previous version 1.10 from Axel.
Installation:
-------------
Copy ext2.xfs into the directory of yout boot partition
which contains minix.xfs (e.g. c:\multitos) and restart your computer.
Look in the FreeMiNT 1.15.1 release archive for an example script
to automatically check your filesystems at boottime!
WARNING:
--------
BE CAREFUL WHEN USING THIS PROGRAM. I, THE AUTHOR, CAN'T TAKE ANY
GARANTY THAT YOU WILL NOT LOOSE ALL OR ANY OF OUR PRECIOUS DATA WHEN
USING THIS PROGRAM. BACKUP OFTEN, BACKUP QUICK.
History:
--------
See in ChangeLog for more details
Thanks to Axel Kaiser who started this project and put it into the GPL.
Now it's almost ready, stable and very fast.
Thanks also to all other people that helped me and told me that
they are very happy to see this development. This was a good
motivation.
Have fun.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 16.09.2000

64
mint/1-19-c02/doc/inet4/BUGS Normal file
View File

@@ -0,0 +1,64 @@
These are strictly speaking no bugs, but unimplemented features or
BSD incompatibilities:
Transmission Control Protocol:
------------------------------
- MSS fixed at 536 bytes currently. May use larger values on directly
connected networks. DONE.
- Selecting for exceptional conditions (ie waiting for urgent data)
does not work. This needs work on the kernel. WORKS with TeSches
patches applied.
- A process is only notified of urgent data arrival via SIGURG when
he does a read(), write() or select(). FIXED. Signalling is now done
asynchronously using a separate process.
- There is currently no round trip time estimation done for calculating
the retransmission timeout. DONE.
- No "Nagle-Algorithm" implemented.
- No congestion avoidance. DONE.
- No slow start implemented. DONE.
- No delayed acks.
- The following is really a bug in BSD. Here are the BSD out-of-band semantics:
Lets say you write 5 bytes of out of band data using the MSG_OOB
flag with send().
Then the receiver will only be able to receive the urgent data if he
has no other unread urgent data pending. If he has no urgent data
pending he can receive the last byte of the urgent data using recv()
with MSG_OOB.
The other 4 bytes are received as normal data. The "mark" (you can
query the system if you have received all data up until the mark
using the SIOCATMARK ioctl) is placed behind these 4 bytes.
Here are the MintNet semantics of out of band handling.
You can write as much urgent data as you want.
The receiver can read *all* the urgent data using recv() with the
MSG_OOB flag.
The "mark" is placed *before* the urgent data byte with the lowest
sequence number.
If there are several chunks of urgent data waiting to be read, the
"mark" moves from the first to the next one when you read data after
the current position of the mark.
You can partially emulate the BSD semantics by placing the socket
into "out-of-band-data-inline" mode using the SO_OOBINLINE socket
option. You can then read urgent data using MSG_OOB or the normal
read().
User Datagram Protocol:
-----------------------
- recv/recvfrom return the amount of data copied -- not the size of
the datagram as BSD does with MSG_PEEK.
Internet Control Message Protocol:
----------------------------------
- Most message types not implemented.

36
mint/1-19-c02/doc/inet4/COPYING Normal file
View File

@@ -0,0 +1,36 @@
All files in this archive are Copyright (c) 1993-95 Kay Roemer.
Exceptions are explicitely stated.
I cannot take over any responsibility for any files in this distribution.
Therefore the following disclaimer:
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
You are welcome to use, copy, distribute and modify the source code
included in this package for noncommercial purposes as long as the
following conditions are met:
o All the files are kept in the distribution.
o Any modifications on files in the distribution are clearly
marked as such, including a statement that the original author
is not responsible for your modifications and possible damage
resulting in your modifications.
o You may not sell this package or parts of it for more than
double the cost of copying the files onto media, including
the cost of the media, excluding local taxes.
Usage of MintNet or parts of it as part of commercial products requires a
written licence from Kay Roemer.
You have agreed with the above conditions when holding copies of the
distribution in your posession.

324
mint/1-19-c02/doc/inet4/README Normal file
View File

@@ -0,0 +1,324 @@
MintNet alpha release README
----------------------------
Contents:
0. Disclaimer
1. What is MintNet?
2. Things needed to run MintNet
3. Things needed to recompile MintNet
4. Recompiling MintNet
5. How to install
6. Network programming
7. BSD Unix (in)compatibilities
8. If you have found a bug
0. Disclaimer
-------------
This package should be regarded as experimental. It is quite possible
that it contains bugs that may do the weirdest things to your hard drive
although I believe it is quite stable now. Anyway, make regular backups!
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1. What is MintNet?
-------------------
MintNet is a networking extension for Atari computers running Mint.
It currently implements the suite of networking protocols referred to as
'TCP/IP' and a local interprocess communication mechanism known as 'unix
sockets' that is in principle similar to named pipes. MintNet is prepared
for adding further networking protocol stacks (like Novells IPX/SPX or
Appletalk for instance).
Thus you can use MintNet to intergrate your Atari into a networked environ-
ment that consists of systems supporting TCP/IP (as the Internet).
MintNet consists of four major parts, a loadable device driver for Mint
(sockdev.xdd), several loadable packet drivers (eg. slip.xif), a library
(socket.olb) and some tool programs (in the tool/ subdirectory) to setup
and manage MintNet.
The device driver links to the Mint Kernel when loaded and installs the
device u:/dev/socket through which the services provided by MintNet can
be accessed.
The libary provides you with the usual BSD socket API functionality using
the services of u:/dev/socket. That means porting Unix software to MintNet
using this libary is really easy. In fact many important packages like ftp,
telnet, ... are ported to MintNet using this library.
The packet drivers are responsible for sending and receiving datagrams over
some type of hardware, for instance slip.xif is responsible for sending
datagrams over serial lines using the SLIP or PPP protocol. For every type
of communication hardware such a packet driver is needed. sockdev.xdd calls
the proper packet driver for sending and receiving datagrams and does not
contain communication hardware specific code.
Packet drivers are currently available for SLIP, PPP, PLIP, Ethernet and
loopback.
Please contact me if you want to write Ethernet hardware drivers or have
hardware that is worth to write a driver for.
2. Things needed to run MintNet
-------------------------------
There are some (in fact a lot) things needed to get MintNet running:
1) An up to date Mint version. Preferably Mint 1.12, MH-Mint 1.12hX or
newer. A megapatched Mint 1.11h9 will probably work too. This is because
the MintNet device driver needs some features of the Mint Kernel that have
been added recently.
Mint binaries, sources and documentation is available via anonymous FTP
from ftp.uni-muenster.de:/pub/atari/Mint/Kernel.
2) Until there are no easy to use installer program and window system based
applications for MintNet you need some experience with cli's and a Unix-like
setup. That is *not* because MintNet itself needs this, but (un)fortunately
all the currently available applications using MintNet are ports of Unix
programs and they need a basic Unix setup to work.
3) Some networking applications for MintNet. A good starting set is inetd,
ping, telnet, ftp, pppd (if you want to use PPP), dip (if you want to use
SLIP).
These programs are not part of this package. They can be found for instance
at ftp.uni-muenster.de:/pub/atari/Mint/Network.
4) Most of those Networking applications require you to run syslogd, a program
that logs system messages to files or the console. If you want to run telnet
or rlogin *servers* on your host you need the login program, too.
Both programs are part of the MintOS 1.4.1 package which is available via
anonymous ftp from earth.ox.ac.uk:/pub/mintos.
For the unexperienced KGMD (Knarfs German Mint Distribution) is a good
starting point. It provides you with a ready to go MintNet environment.
KGMD 1.0 can be found at ftp.phil.uni-sb.de:/pub/atari/mint/KGMD-1.0/.
Another package that contains a basic Mint setup is the Mint distribution kit
MDK (which is a bit outdated), available from phlem.ph.kcl.ac.uk.
3. Things needed for compiling
------------------------------
This package contains already compiled versions of the libraries and the
socket device driver for people who are not willing or able to compile
the stuff. If you are one of them you can ignore the following instructions
about compiling and use the precompiled binaries instead.
1) tar and gzip to unpack the archive (bit silly this one since you are
reading this file).
2) gcc, preferably 2.3.3 or >= 2.5.8, since versions inbetween those have
been reported to be buggy.
3) gmake, preferably 3.6x or later.
4) binutils PL >= 30.
5) MiNTLibs PL >= 41, because as of PL 41 they support the socket library
in errno.h and strerror(). If you don't mind getting messages like 'unknown
error' from perror(), you can use earlier versions too.
6) Minixfs or something similar that supports long filenames. This is not
absolutely neccessary, but there are some filenames that do not fit into
the 8+3 filename scheme.
4. Rebuilding the library and device driver
-------------------------------------------
Edit MakeVars to reflect your setup.
It is easiest to rebuild the whole package by typing
1) make clean
2) make depend
3) make all
into the top level directory. This will rebuild the socket device driver
and all the libraries as necessary. 1) deletes all .o files from previous
compilations. 2) generates the dependency-files that tell make which files
need to be rebuilt when changing one particular file.
Of cource you can 'cd' to one particular subdirectory and remake only parts
of the package. Please have a look at the Makefiles.
You should get the following binaries out of the above steps:
lib/socket.olb -- 32 bit socket library.
lib/socket16.olb -- 16 bit socket library.
lib/bsocket.olb -- 32 bit -mbaserel socket library.
lib/bsocket16.olb -- 16 bit -mbaserel socket library.
net/sockdev.xdd -- socket device driver.
net/drivers/plip.xif -- PLIP packet driver
net/drivers/slip.xif -- combined SLIP/PPP packet driver
net/drivers/dummy.xif -- dummy (lookpback) ethernet driver
net/drivers/de600.xif -- driver for de600 adapter connected to ROM port
net/drivers/riebl*.xif -- drivers for RIEBL card
net/drivers/pamsdma.xif -- driver PAM's external DMA adaptor
net/drivers/lance.xif -- driver for PAM's internal card
net/drivers/biodma.xif -- driver for BIODATA's external DMA adaptor
tool/netstat -- netstat utility, show active connections.
tool/route -- route utility, change/show routing table.
tool/ifconfig -- ifconfig utility, change/show interface config.
tool/slattach -- slattach utility, attach SLIP interface.
tool/iflink -- iflink utility, link Mint device to interface.
tool/arp -- arp utility, change/show ARP table.
tool/ifstats -- ifstats utility, show interface statistics.
5. Installing the libraries and the device driver
-------------------------------------------------
Run the shell script install.sh in the MintNet top level directory:
# ./install.sh
You will be asked for your networking parameters like hostname, domainname,
IP address and what connections to directly connected hosts you wish to
establish. From your answers the script will generate basic config files, that
enable you to use MintNet after reboot.
Now you may want to "hand tune" the configuration files a bit. They are
hold in /etc. The most important are
* /etc/resolv.conf (host name resolver config. Read man/cat5/resolver.5)
* /etc/host.conf (more host name resolver config. Read man/cat8/resolv+.8)
* /etc/hosts (host name database)
* /etc/hostname (your hostname)
* /etc/domainname (your domainname)
* /etc/rc.net (MintNet startup shell script, *must* be executed after reboot,
from /etc/rc or mint.cnf)
The basic MintNet utilities are described by manual pages in man/cat8/.
Read route.8, ifconfig.8, netstat.8!
The script install.sh is intended for first installation only. If you have
already a working MintNet installation and only want to update the binaries
to a newer version, then type 'make install' into the toplevel MintNet
directory. Change to the 'man' directory and type 'make install' to install
the manuals.
6. Getting information about socket and network programming
-----------------------------------------------------------
Because MintNet providedes you with a BSD socket compatible API (with some
extensions and omissions) through the socket.olb library, any literature on
Unix networking would help alot.
You can obtain information about using the facilities provided by this package
by having a look at the manual pages in the man subdirectory. You could also
get the texinfo manual from the GNU-C library or a good book, like
- Comer, Stevens: `Internetworking with TCP/IP I-III' (for learning)
- Richard W. Stevens: `Unix Network Programming'
- Andrew S. Tannenbaum: `Computer Networks'
- Leffler, McKusick, Karels, Quaterman: `4.3 BSD Unix -- Design and
Implementation' (for insiders)
- Santifaller: `TCP/IP und NFS in Theorie und Praxis' (an introduction)
- Loosemore, McGrath, Oram, Stallman: `The GNU C Library Reference Manual'
(for reference)
- RFCs 786(UDP), 790(assigned numbers), 791(IP), 792(ICMP), 793(TCP),
1055(SLIP), 1122(Host Requirements), 1331(PPP), 1144(VJ compression),
894,1042(IP over 802.x), 826(ARP), 903(RARP) (for protcol specifications)
7. BSD Unix (in)compatibility
-----------------------------
Here are some notes on incompatibilities to the BSD Unix programming interface
for the ones familiar with it.
- The socket ioctl's are currently not in the Mint Library. Use the file
sockios.h from the include dir instead or get my portlib.
- Most IP options are not processed like they should.
- Very few (only the most important from my point of view) ICMP message
types are implemented.
- Currently sendmsg() and recvmsg() on AF_UNIX sockets do not support sending
and receiving of access rights. (ie file handles).
- There are lots of new error codes, like ENOTCONN, ... To get meaningful
messages from perror() and strerror() and for support of the new errorcodes
you will need the MiNTLibs patchlevel >= 41.
- On AF_UNIX stream sockets you can set the send buffer size with the
setsockopt() call only if the socket is connected. For AF_UNIX dgram
sockets you can't at all set the send buffer size, only receive buffer size.
- stat(), fstat() on sockets and AF_UNIX socket files return for the file
type S_IFCHR and S_IFREG, respectively (not S_IFSOCK).
- select()ing for writing on dgram sockets will always report that writing
will not block, even if the desriptor is NOT ready for writing.
- The FIONREAD ioctl() call on AF_UNIX/AF_INET dgram sockets returns the
size of the next datagram or zero if none is available.
The FIONWRITE ioctl() call on AF_UNIX dgram sockets returns an infinite
number bytes if you did not specify a destination address for the socket
using connect().
FIONWRITE on UDP sockets returns always `infinity'.
- Sending and receiving of more than one TCP urgent data byte is supported.
Unfortunately this causes some incompatibilities. Read the file net/inet/BUGS
to learn the differences.
8. If you have found a bug
--------------------------
In case you find a bug or incompatibility in MintNet or want me to implement
some feature you need then don't hesitate to contact me at the below given
Email address.
If you report a bug I need a detailed description of your setup, of the
symptoms and the circumstances that caused the bug to appear and if possible
a small peace of code that reproduces the bug.
Keep in mind that I can't do anything to solve problems described by messages
like 'MintNet does not work! What shall I do?'
Please report bugs only to me (Torsten Lang) since Kay Roemer does not maintain
the package any more. Thanks.
Have fun with MintNet,
--
Kay Roemer roemer@informatik.uni-frankfurt.de
http://www.uni-frankfurt.de/~roemer/
--
Torsten Lang Torsten@Lang.net

10
mint/1-19-c02/doc/inet4/README.1ST Normal file
View File

@@ -0,0 +1,10 @@
!!! IMPORTANT !!!
MintNet now needs Mint 1.11h9 or newer to run. I don't consider this a
problem, because Mint 1.12 and later versions are available in binary form.
If you intend to use MintNet in a SingleTOS+Mint environment, you must copy
nohog.acc to the root of your boot drive. This accessory keeps AES from
staying all the time in supervisor mode (thus preventing Mint from switching
contexts and MintNet from working). nohog.acc is taken from the MinixFS
distribution and is written by Stephen N. Henson.

151
mint/1-19-c02/doc/inet4/README.mas Normal file
View File

@@ -0,0 +1,151 @@
README FILE FOR IP MASQUERADING
The IP masquerading support was implemented by Mario Becroft in May 1999 and
is placed in the public domain.
The following files changed from the standard net-1.03 distribution:
tool/Makefile
net/inet/Makefile
net/inet/ip.c
net/inet/ip.h
net/inet/tcp.c
net/inet/inet.c
The following files were added to the standard net-1.03 distribution:
include/masquerade.h
include/masqextern.h
tool/masqconf.c
net/inet/masqdev.c
net/inet/masquerade.c
README.masquerade
INTRODUCTION
I implemented IP masquerading for MiNTnet, as well as a quick fix for the "land"
bug which would freeze mintnet.
I am sure that my implementation is not optimal and contains many bugs, because
this is the first low-level network programming I have ever done and I am not
very familiar with it. When even experienced programmers get bugs in their code,
you can only begin to imagine the kind of errors I am likely to make.
Nevertheless it does seem to work, so I must have done something right.
To use the IP masquerading features, simply copy the new sockdev.xdd into
your mint folder and reboot the machine. IP masquerading is still disabled by
default, but can be enabled using the masqconf program, as explained below.
USING MASQCONF / QUICK START GUIDE
To configure the IP masquerading you use the masqconf program from the tool
directory.
To show the current configuration and any masquerade database entries, invoke
masqconf with no arguments.
To get help, invoke masqconf with help or any unknown command as an argument.
Normally you don't need to worry about all the available settings, the only
important ones are address, netmask and flags. The rest can be left at the
default values.
address should be set to the address of the network to be masqueraded for,
and netmask should be the netmask of that network.
For example if you have a local network 10.0.0.0 you might configure IP
masquerading for all machines on the network with the following command:
masqconf address 10.0.0.0 netmask 255.0.0.0
Once you have correctly set the parameters you must set the ENABLED flag to
make IP masquerading operate, like so:
masqconf set ENABLED
That is all there is to it. Now you can access the internet from any of
the machines on your network, even though you only have one actual IP address!
PORT REDIRECTION
Apart from allowing a masqueraded machine to initiate connections to another
computer the IP masquerading supports permanent redirection of certain ports
on the masquerading gateway to go to a masqueraded machine. You configure this
with the masqconf redirect command. The parameters are gateway port,
destination address an destination port.
For example to redirect incoming HTTP requests on the gateway machine to
port 456 of masqueraded machine 10.0.0.5, you could use the following command:
masqconf redirect 80 10.0.0.5 456
To stop redirecting a port, use the masqconf unredirect command. For example
to reverse the above redirection, issue the following command:
masqconf unredirect 80
FAQ
Q. Why does (xyz feature) not work properly?
A. Like I said this is my first project with any kind of low-level network
programming, and I probably made quite a lot of mistakes. Certainly notify me
if you find a bug, but it's even better if you try to fix it yourself then
mail me and explain how you fixed it. But also see the next question.
Q. Why do some protocols like FTP and DCC not work via IP masquerading?
A. Some programs send low-level protocol information in a high-level protocol,
including IP addresses and port numbers. IP masquerading doesn't know about
that, and doesn't masquerade those addresses properly. Eventually I plan to
add support for this, but it is very complicated. In the mean time, you can
sometimes avoid the problem by adjusting the settings in the problematic
program, for example if you set your FTP client to passive mode it will work
ok.
Q. Why doesn't this documentation explain a whole lot of things like the
timeouts, masquerade database, port redirection, flags, etc., etc.?
A. I want to make IP masquerading available, but I did not have time to
write lots of documentation. Read the source code! Or if you send me an email
I will be happy to help. I hope to write some better documentation later.
BUGS
Lots!
Seriously, it can't be so bad as I've used the IP masquerading quite a lot and
it doesn't fail. But I have noticed some inconsistencies.
Sometimes a condition occurs where a TCP connection that is not yet opened
(or not yet properly closed) tosses lots of packets backwards and forwards in
an endless loop. I don't know why this happens, but I am looking into it. If
you see this bug, try to track it down and fix it. As a temporary fix, just
disable IP masquerading (masqconf unset ENABLED) then enable it again
(masqconf set ENABLED) to break the loop.
I think there is some sort of bug handling incoming ICMP error messages
for a masqueraded host. Particularly, error messages about UDP datagrams
seem to get through to the host that sent the datagram which caused the error,
but the host doesn't seem to interpret them. Is the checksum wrong, or
something?
CONTACTING ME
I would like to hear anything you have to say about the IP masquerading.
Please send an email to:
mb@tos.pl.net
Please note that this address will become invalid in about a month's time.
I will announce my new address at that time via the MiNT mailing list and
other appropriate forums.

19
mint/1-19-c02/doc/inet4/README.mtl Normal file
View File

@@ -0,0 +1,19 @@
README FILE FOR IP MASQUERADING (TORSTEN LANG)
The ip masquerading support now also contains support for ftp. Unfortunately
this still is not stable but I realease it anyway and hope that someone else
will be able to find and fix the problem (and certainly pass the fix to me ;-).
The ftp support is implemented in a way that makes it quite easy to add support
for other protocols too (like irc). Since I have no possibility to test these
other protocols I have not implemented support for these.
CONTACTING ME
If you find the remaining bug in the ftp support that causes the connection to
break after a few "dir" commands please let me know immediately. Please send
mail to:
Torsten@Lang.net
Hopefully this address will stay valid for the near future.

39
mint/1-19-c02/doc/minixfs/COPYING Normal file
View File

@@ -0,0 +1,39 @@
Minixfs is copyright S.N. Henson 1991,1992,1993,1994,1995.
This code may be freely distributed unmodified, provided this copyright notice
is intact. A small copying fee may be charged for redistribution provided this
does not exceed the equivalent of five pounds Sterling (UK currency).
You are free to compile, modify and recompile modified versions of this
program. Modified versions of this source may be redistributed provided:
1. Modified versions are clearly marked as such in each file modified.
2. This copying file is included unmodified in any distribution.
3. An additional startup message is added stating that it is a modified
version after the original startup message.
4. The orginal copyright startup message is not modified in any way.
5. No additional restrictions are placed on the modified version, in particular
full source must still be freely available and freely distributable.
Binaries compiled from this code may also be redistributed. Binaries
compiled from modified versions of this code may also be redistributed provided
this copying file is included intact and conditions 1 to 5 above are met.
This version may not be used for profit or in a commercial environment,
this includes the development of software that requires a registration fee.
If you wish to use Minixfs to develop anything other than free software or use
it in a commercial environment then Minixfs must be registered for a small fee,
please contact me for further details.
Distribution of this program with commercial packages is not allowed
without my written permission, please contact me if you wish to do this,
or indeed if you want a similar filesystem writing for a different purpose
(e.g. TT Unix or Spectre), however I am not in a position to write filesystems
for other commercial packages free of charge.
I reserve the right to modify these conditions at some future date.
Please note that although I believe each release to be stable and
test it thoroughly I offer no guarantee. Therefore, THIS PROGRAM COMES
WITH NO WARANTEE WHATSOEVER AND USE IS ENTIRELY AT YOUR OWN RISK, I WILL
NOT BE LIABLE FOR ANY DAMAGE CAUSED DIRECTLY OR INDIRECTLY FROM ITS USE.

160
mint/1-19-c02/doc/minixfs/README Normal file
View File

@@ -0,0 +1,160 @@
MinixFS 0.74
============
Note: Only run with FreeMiNT 1.15.1 and above!
It's recommended to use this version with at least FreeMiNT 1.15.5
for best performance!
What's new?
-----------
Two bugfixes.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 01.04.2000
==============================================================================
******************************************************************************
==============================================================================
MinixFS 0.72
============
Note: Only run with FreeMiNT 1.15.1 and above!
What's new?
-----------
Added filesystem clean flag. Updated also fsck & minit for this.
If you use the new fsck please also use the new xfs driver!
Added native UTC mode to the xfs driver.
Updates and some bugfixes.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 10.10.1999
==============================================================================
******************************************************************************
==============================================================================
MinixFS 0.71
============
Note: Only run with FreeMiNT 1.15.0 and above!
What's new?
-----------
Support for (configurable) write-protection on filesystem level.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 13.04.1999
==============================================================================
******************************************************************************
==============================================================================
MinixFS 0.70 pl8
================
Note: Only run with FreeMiNT 1.15.0 and above!
What's new?
-----------
An updated fsck is included here. Requires XHDI and access all
partitions in a clean and safe way. It's also a little bit faster.
Also updates and bugfixes for MinixFS and minit.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 05.03.1999
==============================================================================
******************************************************************************
==============================================================================
MinixFS 0.70 pl7
================
Note: Only run with FreeMiNT 1.15.0 and above!
fsck sources are not included here
What's new?
-----------
A totally rewritten minit (MinixFS initializer) is included here.
Also updates and bugfixes for MinixFS.
Note: New minit requires XHDI and can't create MinixFS filesystems
on floppys at the moment (update follow).
Also minit create always MinixFS V2 now.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 22.12.1998
==============================================================================
******************************************************************************
==============================================================================
MinixFS 0.70 pl6
================
Note: Only run with FreeMiNT 1.15.0 and above!
This is an update archive and include only the source from MinixFS and a
minix.xfs ready to install. All other tools (minit, fsck, ...) are not
included here.
What's new?
-----------
First, a more detailed list of changes you found in Changes.
I removed completly the cache management and low level I/O interface. This is
integrated in the new kernel. This reduce also the code size (now 26 kb,
MinixFS 0.60 ~40 kb). For technical reasons I must remove (buggy) Mount/Unmount
Support.
I also added some new Dcntl's that are used by FSetter for example.
Please note that the old MinixFS use 120 kB as default cache. The default cache
of the new buffer cache management in FreeMiNT 1.15 is 100 kB. And the new global
buffer cache is also used by the new fat-fs and other xfs in the future.
Frank Naumann
<fnaumann@freemint.de>
Magdeburg, 10.10.1998

53
mint/1-19-c02/doc/nfs/COPYING Normal file
View File

@@ -0,0 +1,53 @@
All files in this archive are Copyright (c) 1993, 1994 by Ulrich Kuehn.
Exceptions are explicitely stated.
I cannot take over any responsibility for any files in this distribution.
Therefore the following disclaimer:
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
You are welcome to use, copy, distribute and modify the source code
included in this package as long as the following conditions are met:
o All the files are kept in the distribution.
o Any modifications on files in the distribution are clearly
marked as such, including a statement that the original author
is not responsible for your modifications and possible damage
resulting in your modifications.
o You may not sell this package for more than the cost of copying
the files onto media, including the cost of the media, excluding
local taxes. This does not apply to modified versions, which are
only allowed to be distributed for free (of course you are
allowed to sell the diffs, but not the modified package!).
For exceptions the written consent of the author is necessary.
You have agreed with the above conditions when holding copies of the
distribution in your posession, you can terminate this by destroying
any copy and all modified versions of this software in your possession.
Of course any donations of money in any amount are very wellcome, just send
it to my address or ask for a bank connection...
My address is:
Email:
kuehn@math.uni-muenster.de (preferred)
Snail mail:
Ulrich Kuehn
Geibelstr.9
48161 Muenster
Germany

145
mint/1-19-c02/doc/nfs/README Normal file
View File

@@ -0,0 +1,145 @@
This is an early beta version of an networking file system for MiNT.
Copyright 1993, 1994 by Ulrich K<>hn. All rights reserved.
DISCLAIMER:
===========
THIS PROGRAM COMES WITH ABSOLUTELY NO WARRANTY, NOT
EVEN THE IMPLIED WARRANTIES OF MERCHANTIBILITY OR
FITNESS FOR A PARTICULAR PURPOSE. USE AT YOUR OWN
RISK.
See also the file COPYING for further details.
EXPLANATION:
============
A network file system allows computers to access file that are physically
located on another computer transparently. Therefor the must be a means of
data transport between these two computers (see above for the current
situation). The computer accessing the remote file is called the client,
the computer being physically the owner of that file is the server.
On the server, there must be a service program running, that satisfies the
access requests of the client. This program is called nfs daemon, short
named nfsd. Because normally the client does not know which files can be
accessed by it, it must be told so; this is called mounting of a remote
directory or file and done with a program called mount on the client.
On the server side there must run another service program, the mount daemon
called mountd, which serves these mount requests by clients.
So: without nfsd no file access, without mountd no mounts to access files.
Another point is that both server and client can be the same computer!
Then the daemon programs run on that machine, and also the mount program is
executed there. This is the easiest way to test this package.
INSTALLATION:
=============
There are a few things to do (better try first server and client on the
same computer) :
- (both server and client) make sure to have Kay Roemer's mint-net (a socket
device) installed correctly. Version >= 0.30
(eMail: roemer@hera.rbi.informatik.uni-frankfurt.de)
This includes:
- make sure to have a directory u:\etc (make a symbolic link to
your preferred place in mint.cnf)
- place the following files in u:\etc
hostname, hosts, networks, services, resolv.conf
- name your host by writing a name into u:\etc\hostname
- (client) copy the nfs.xfs (the client filesystem driver) to a place where
MiNT can find it at boot time (that is \mint or \multitos on your boot drive)
- (server) install the portmapper daemon from the sun rpc package. Place
the rpc file into u:\etc
The portmapper is essential as both the mount daemon and the mount
command rely on that, but as a temporary hack, they can also work without
the portmapper.
- (server) create a file u:\etc\xtab containing all the exported directories
or files. This file is necessary for both nfsd and mountd (if necessary,
rename them to nfsd.ttp and mountd.ttp). Please look into the bundled
example, as no further docs are availbale at the moment. (or look into
some unix adm doc)
- reboot
Then start the mountd and the nfsd. Now the system is ready to do some
nfs mounts. Here an example: (suppose \etc\xtab contains a line
\f\source ....)
mount hostname:\f\source \nfs\source
where hostname is the name of your host. (all operations done while drive
u: is the current. It should be, as mount treats the ':' as separator
betweeen hostname and directory name)
Another point is that if you are trying to run server and client stuff on
the same machine, the hostname for the mount command must be 'localhost'
or 'loopback' (there should be such a line in \etc\hosts), as the resolver
otherwise does not find the correct host (this behavior might depend on the
version of the mint-net your are using, or on your configuration)
After this operation you should have a directory source in u:\nfs which has
all the contents of the original \f\source
All this can be done within mint.cnf (or better use a shell script which
is started from mint.cnf -- look at the example rc.mup and mint.cnf)
A new feature of the mountd and nfsd is that they can be started by
the inetd and terminate themselfes in this case after a short time, so
there is no need to hold the all the time running in memory. Just install
the inetd and make sure that the mount and nfs lines in u:\etc\inetd.conf
are correct, that means they are active and the paths are correct.
COMPILATION:
============
If you want to rebuild the binaries by yourself, you have first to edit
the paths in the Makevars file, especially the BUILDDIR variable.
Then simply type make all or make install and wait...
BUGS:
=====
- the nfsd is not able to find a file on a TOSFS (in the state of MiNT
<= 1.10) if it has only its nfs handle and no internal information. So
it does not work properly on such a file system, sorry. But it works on
a patched TOSFS with Julian Reschke's crc patch applied and enabled.
This patch is included in MiNT 1.12 (get this anyway, as binaries are
available!), but it seems to be disabled by default (take a look into
tosfs.c in the MiNT source).
- no caching of results for nonidempotent requests. So if the anser of a
file remove request gets lost and the client resends this request, it
will fail because the file is already gone.
- no exportfs command, so you have to edit your \etc\xtab yourself and
cannot use the \etc\exports file.
- several mount options are still not supported by the XFS, such as
hard mounts
MY CONFIGURATION:
=================
I am running this system on a TT030 with 4/4 Mb ram, TOS 3.06, a patched
MiNT 1.12, using both minixfs and the patched tosfs, and it seems to be
quite stable now, but who knows?
THANKS:
=======
Many thanks go to Kay Roemer for his great socket device, which made this
nfs possible. He also constantly supplied me with critics, suggestions,
ideas and bug fixes.
CONTACT ADDRESS:
================
If you have questions, bug reports, suggestions, etc. please contact
me under:
kuehn@math.uni-muenster.de (Ulrich Kuehn) preferred
Ulrich Kuehn, Geibelstr.9, 48161 Muenster, Germany
Have fun
Ulrich

40
mint/1-19-c02/doc/xconout2.txt Normal file
View File

@@ -0,0 +1,40 @@
XCONOUT2.XDD
============
This piece of code implements a device /dev/xconout2 to MiNT. Once
installed it doesn't do anything at all, which is why it should be
quite save to install it even if you don't actually always use it.
If you open /dev/xconout2 (which can only be done by one program)
a new routine will be installed as a xconout2 handler. After this
all data being written to the console, may it be any program writing
directly to /dev/console or any daemon which was started with stdout
pointing to /dev/console or even MiNT's internal debugging routines
is not printed but buffered instead.
So if you write a program which opens and selects this device for
reading you'll be able to catch everything which might possibly destroy
the screen contents under any kind of graphic application. If you should
want to print the data to the console anyway, you can do this by writing
it back to /dev/xconout2. Note that both read and write calls will
never block.
The only reason why this appears as a device driver is that a user
level program doesn't need any MiNT specific functions (contrary to the
stuff implemented in W0R8) and it's quite save: In case of a program
crash the file will be closed by MiNT, which will install the original
routine again. So even in cases of severe program crashes there's no
chance of the vector pointing to abandoned memory and thus perhaps
crashing the whole system any more (as it sometimes did in W0R8).
BUGS: None (?).
KNOWN FEATURES: Doesn't use XBRA and things like these. I very much doubt
that under a multitasking environment it's very clever to change vectors
from elsewhere that inside the OS itself. So I hope there isn't any
program which will cause greater problems.
Anyway: USE IT AT YOUR OWN RISK! THERE'S NO WARRANTY!
ciao,
TeSche <itschere@techfak.uni-bielefeld.de>

BIN
mint/1-19-c02/ext2.xfs Normal file
View File

Binary file not shown.

70
mint/1-19-c02/firebee/doc/fec.txt Normal file
View File

@@ -0,0 +1,70 @@
fec.xif
==========
The MiNT-Net xif driver for Firebee onboard ethernet interface,
based on Freescale DMA API.
Installation and usage
======================
Install MiNT-Net and copy the fecdma.xif into your mint folder.
Then configure the eth0 interface as usual.
Bring up the network interface and assign an specific IP to it:
ifconfig eth0 addr 192.168.220.101
To add an route to an specific host within you network:
route add 192.168.220.99 eth0
You can influence driver mode by renaming the .xif file.
recognized filenames:
"FEC.XIF" => Auto-Negotiate, no promiscuous mode
"FECP.XIF" => Auto-Negotiate, promiscuous mode
"FECP10.XIF" => 10Mbit half duplex, promiscuous mode
"FEC10.XIF" => 10Mbit half duplex, no promiscuous mode
How it works
============
The core of this driver is the so called DMA cookie.
This cookie provides us with pointers to the so called Multichannel
DMA API. That API is provided by Freescale and built into FireTOS.
Most FEC drivers (and also many others) are built on top of the
MCDMA API. For more info read the "Multichannel DMA API User's Guide"
and MCF5475 Reference Manual provided by Freescale.
Currently nearly the same Network Buffer Scheme as FireTOS uses,
is used for packet buffering. It makes use of the
dma_malloc / dma_free functions provided with FireTOS DMA cookie.
These functions work on memory areas which aren't affected
by CPU cache. We could also use cache-visible memory,
but then we would have to flush the cache (regions) before
we send / receive data. Another Option is to use a static RAM
area, but there isn't much space, which forces to use less
buffer descriptors ( around 3 for rx, 3 for tx ) and that slows
down transfer speeds alot. So the usage of SRAM is a bit
problematic. (Altough SRAM access time is faster.)
The DMA Cookie also provides us with the Freescale Multichannel
DMA API + dma utility functions. With these functions we can
start an so called "DMA task". There are specific DMA
tasks for Receiving / Transmitting FEC data. It's built within the
DMA API. So everything we have to do: start the dma task, and
most of the work is done. The FEC is controlled by the DMA Task,
and the driver just needs to handle incoming packets and submit
outgoing packets to the task.
While writing this, there is no official release of FireTOS which
contains the DMA Cookie. So you either have to look for an
non-official version, or wait until Didier Mequignon releases the
next FireTOS version.
Enjoy!
m0n0
7. Nov. 2011

BIN
mint/1-19-c02/firebee/fec.xif Normal file
View File

Binary file not shown.

2333
mint/1-19-c02/fonts/cs/cp125008.txt Normal file
View File

File diff suppressed because it is too large Load Diff

2839
mint/1-19-c02/fonts/cs/cp125009.txt Normal file
View File

File diff suppressed because it is too large Load Diff

4887
mint/1-19-c02/fonts/cs/cp125010.txt Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
mint/1-19-c02/fonts/cs/iso2a-16.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/cs/iso2a-6.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/cs/iso2a-8.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/pl/ISO-8859-2.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/pl/system08.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/pl/system10.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/ru/d_kyr_08.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/ru/d_kyr_09.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/fonts/ru/d_kyr_10.fnt Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/inet4.xdd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Britain/british.tbl Normal file
View File

Binary file not shown.

9
mint/1-19-c02/keyboard/Czech/Ctime.1st Normal file
View File

@@ -0,0 +1,9 @@
Soubory *.tbl jsou mapovaci tabulky klavesnice.
czech_kam klavesnice v kodu bratri Kamenickych
czech_iso klavesnice v kodu ISO 8859-2
Pro spravne zobrazeni ceskych znaku je potreba mit nainstalovan prislusny font.
Pro instalaci staci nakopirovat prislusnou tabulku do systemoveho adresare
a pojmenovat ji KEYBOARD.TBL. Po pristim startu systemu bude tabulka zavedena.

BIN
mint/1-19-c02/keyboard/Czech/czech_iso.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Czech/czech_kam.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Finland/finnish.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/France/french-pc.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/France/french.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Germany/german.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Greece/greek.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Hungary/hungarian.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Italy/italian.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Netherlands/dutch.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Norway/norwegian.tbl Normal file
View File

Binary file not shown.

26
mint/1-19-c02/keyboard/Poland/Czytaj.1st Normal file
View File

@@ -0,0 +1,26 @@
Pliki *.tbl zawieraj<61> tabele dla poszczeg<65>lnych, fizycznych typ<79>w
klawiatur rozszerzonych o polskie znaki w standardzie ISO-8859-2, w
uk<EFBFBD>adzie programisty (Alternate + a = <20> etc.).
Do uzyskania poprawnego wygl<67>du liter na ekranie potrzebny jest
ponadto font z polskimi znakami w ISO-8859-2. Namiastka takiego fontu
znajduje si<73> w katalogu fonts/.
Instalacja:
1) Wybierz jeden z plik<69>w *.tbl stosownie do tego, jaki masz typ
klawiatury (np. je<6A>li masz hiszpa<70>sk<73>, wybierasz spanish-pl.tbl).
2) Przekopiuj go do tego samego katalogu, gdzie jest plik mint.cnf.
3) Zmie<69> nazw<7A> tej kopii na keyboard.tbl
4) Zr<5A>b restart systemu.
Poniewa<EFBFBD> nie mam wszystkich typ<79>w klawiatur, wi<77>c nie mia<69>em szansy
sprawdzi<EFBFBD>, czy tablice konwersji dzia<69>aj<61> poprawnie.
Pliki <20>r<EFBFBD>d<EFBFBD>owe tablic *.tbl s<> razem z programem mktbl w katalogu
freemint/tools.
EOF

BIN
mint/1-19-c02/keyboard/Poland/british.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/french.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/german.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/italian.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/papyrus/papyrus.mac Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/papyrus/papyrus.pap Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/spanish.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/swiss_de.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/swiss_fr.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Poland/usa.tbl Normal file
View File

Binary file not shown.

6
mint/1-19-c02/keyboard/ReadMe Normal file
View File

@@ -0,0 +1,6 @@
To enable the keyboard translation you should copy the appropriate
*.tbl file to the FreeMiNT <sysdir>, rename it there to keyboard.tbl
and reboot.
The *.tbl files in source forms are distributed along with the mktbl
program in the directory freemint/tools/mktbl/.

BIN
mint/1-19-c02/keyboard/Russian/russian.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Spain/spanish.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Sweden/swedish.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Switzerland/swiss_de.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/keyboard/Switzerland/swiss_fr.tbl Normal file
View File

Binary file not shown.

4
mint/1-19-c02/keyboard/USA/Readme.1st Normal file
View File

@@ -0,0 +1,4 @@
Keyboard table for Hades, US keyboard, UK ROM.
Prepared by Lonny Pursell, 27.XI.2002

BIN
mint/1-19-c02/keyboard/USA/uk2us.tbl Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/lp.xdd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/minix.xfx Normal file
View File

Binary file not shown.

240
mint/1-19-c02/mint.cnf Normal file
View File

@@ -0,0 +1,240 @@
# ---------------- FreeMiNT configuration file ---------------------
# for FireBee Setup 2023
#
# The "set" directive controls the behaviour of the mint.cnf parser.
# It accepts one of three parameters:
#
#set -q - silent output (+q for verbose output)
#set -v - print command lines (+v don't)
#set -c - control interpretation of escape sequences
set -q
# The include command allows you to include other files while the
# mint.cnf file is being interpreted. The included file will be
# interpreted as a part of the mint.cnf file.
#include u:/c/mint/vars.cnf
# The smaller the KERN_SLICES value, your processes have faster
# response time but the general performance is worse. Very fast
# machines however, may benefit from setting 1 here.
#KERN_SLICES=2
# KERN_DEBUG_LEVEL controls output of global debugging information.
# The higher the level, the more stuff MiNT will spew about about
# what it's doing.
#
# The average user doesn't want to hear about this stuff, so the
# default is 1, i.e. display ALERT messages only. Note that you need
# a debug kernel to get more: normal kernels do not contain so much
# debug information.
#
# KERN_DEBUG_DEVNO is the BIOS device number to which the info
# should be sent.
#
# Devno can be: 0=printer, 1=aux/modem, 2=screen (console), 3=midi,
# 4=keybrd, 5=raw.
#
# The default is the console.
#KERN_DEBUG_LEVEL=1
#KERN_DEBUG_DEVNO=2
# KERN_BIOSBUF controls how BIOS I/O is performed. Normally, MiNT
# tries to buffer this to provide a (considerable) improvement in
# speed. However, some applications may get upset by this.
#
# KERN_BIOSBUF=NO turns off all buffering for maximum compatibility.
# The default is YES.
#KERN_BIOSBUF=YES
# KERN_SECURITY_LEVEL= enables the appropriate security level:
#
# 0 - recommended for single user setups, like MultiTOS (default).
# 1 - recommended for multiuser setups, like KGMD.
# 2 - full protection, unsupported by software, thus discouraged.
#KERN_SECURITY_LEVEL=1
# KERN_MPFLAGS controls the memory protection behaviour. Its argument
# is a bitfield. Only the bit 0 is defined: 1 means, that more strict
# model of the protection should be enabled. Some programs may
# refuse to run, so the default is 0.
#KERN_MPFLAGS=1
# TPA_FASTLOAD=YES forces fast loading (without zeroing all the
# memory) for all programs. This defines a default state, that can be
# modified later via appropriate kernel calls (use MiNT Setter
# utility to toggle it later when neessary, without reboots).
#
# TPA_FASTLOAD=NO (default) means that the information from the
# program header will be used to decide (this is like TOS does).
TPA_FASTLOAD=YES
# Set maximum additional TPA size for new processes
# (in kilobytes). The default is 1024. Better keep it low (1024 is
# what we call low) if your machine has 4 MB RAM or less.
TPA_INITIALMEM=8192
# FS_VFAT= enables VFAT extension for selected drives.
# The VFAT extension is disabled by default.
#
# If you use both TOS and MiNT, better don't enable VFAT extension
# on your boot drive.
#FS_VFAT=D,E,F,G
FS_VFAT=A,C,D,E,F,G
# FS_VFAT_LCASE=YES tells the kernel to return lowercase filenames
# from VFAT directory searches. The default is NO.
#FS_VFAT_LCASE=YES
# FS_WB_ENABLE= enables write back cache for selected drives. The
# write back cache is disabled by default. Also, it does not have
# any effect for TOSFS drives.
#FS_WB_ENABLE=A,C,D,E,F,G,H,I,J
# FS_CACHE_SIZE= specifies the size of disk cache in kilobytes for the
# internal caching module. Default is 128.
FS_CACHE_SIZE=2048
# FS_CACHE_PERCENTAGE specifies the size of the disk cache (in
# percents) to be filled with linear reads. The default is 5.
FS_CACHE_PERCENTAGE=10
# FS_UPDATE= set update time for system update daemon in seconds
# default is 5, it isn't recommended to use a value less than 4.
#FS_UPDATE=10
# Software write protection on filesystem level.
#FS_WRITE_PROTECT=R,S
# FDC_HIDE_B= tells the MiNT to remove floppy drive B: from the
# system.
# It is useful on single floppy systems to get rid of "Insert
# disk B: into drive A:" messages from the AES. Default is NO.
FDC_HIDE_B=YES
# PROC_MAXMEM= gives the maximum amount of memory that any process
# may use (in kilobytes). The default is to make this unlimited, but
# if you have a lot of memory and/or programs that grab more memory
# than they should, try setting this.
#
# E.g. to limit processes to 4096K of memory, remove the '#' at the
# beginning of the next line.
#
# WARNING: the process will not be allowed to allocate memory beyond
# the limit, and it won't "see" more memory as available from the
# system.
# Please understand that programs like "free" (or any other that
# interrogates the system how much memory is available) is a process
# as well, thus it will undergo this limit too!
#
# Decent shells (desktops) allow you to limit the maximum amount of
# memory independently for each program.
#PROC_MAXMEM=4096
# Three commands, that define output files for RS-232, console and
# printer devices. The argument for each one must be a pathname.
#
# For best results, the convention u:/drive/pathname should be used
# for all specified pathnames from now on.
#GEMDOS_AUX=u:/c/mint/aux.out
#GEMDOS_CON=u:/c/mint/con.out
#GEMDOS_PRN=u:/c/mint/prn.out
# End of kernel settings
#
# -------------------------- Commands ------------------------------
#
# Here are some commands that you can give to MiNT:
#
# alias d: path -- make a fake "drive" that actually points to the
# given path
# cd path -- changes MiNT's default directory
# echo message -- print something on the screen
# exec program -- runs a program; you must give the complete path
# and file extensions (e.g. c:/bin/echo.prg)
# include file -- include another portion of the MINT.CNF file.
# sln path link -- make a symbolic link named "link" pointing to
# "path". "link" must be on drive U: for this to work
#
#-------------------------------------------
#
# Set up system symbolic links
include u:/c/mint/sys.cnf
# Basic environment variables
setenv PATH /bin;/sbin;/usr/bin;/usr/sbin
setenv SLBPATH 'c:\mint\slb\;c:\gemsys\xtension\;c:\gemsys\slb\'
setenv HOME u:/home
setenv TMPDIR u:/tmp
setenv HOSTNAME firebee
setenv USER root
setenv LOGNAME root
setenv SHELL u:/bin/bash
#
# *** Variables for AES selector selgem.prg ***
setenv AES1 XaAES
setenv AES2 MyAES
setenv AES1PATH u:/c/mint/1-19-c02/xaaes/xaloader.prg
setenv AES2PATH u:/c/gemsys/myaes/myaesv4e.prg
#
# Check filesystems.
#exec c:\mint\tools\fscheck\vfatfsck.ttp c:
# Initalize network.
include u:/c/mint/network.cnf
# Run MGW (Draconis gateway for MiNTnet)
#exec u:/c/mint/tools/mgw/mgw.prg
# Run GLUESTIK to MinTNet gateway
exec u:/c/mint/tools/gluestik/gluestik.prg --force
# The best option is to have INIT= command here, after all pathnames
# are already set up by commands above.
# If the MiNT is supposed to execute GEM, you should specify the full
# path and filename like that:
#
#GEM=u:/c/mint/1-19-c02/xaaes/xaloader.prg
# You can also request MiNT to execute the TOS AES residing in ROM.
# WARNING: this is not recommended, you should use a GEM version
# instead, that is multitasking friendly.
#
#GEM=ROM
# Otherwise, if your init program is not GEM, you should use INIT= as
# follows:
#
INIT=u:/c/gemsys/slgemv4e.prg
#INIT=u:/c/mint/sys/bin/bash
# If you leave both commands above commented out, the MiNT will
# attempt to execute a file called `sh.tos' found in the system
# directory (the same where the mint.cnf resides), and if this
# fails, the internal minimum shell will be executed.
#
# The "echo" command is really straightforward.
#
echo Setup complete, now booting the system...
echo

420
mint/1-19-c02/mint_def.cnf Normal file
View File

@@ -0,0 +1,420 @@
# ---------------- FreeMiNT configuration file ---------------------
#
# The mint.cnf file is loaded, when the entire system is practically
# up, all device drivers and filesystem drivers have been loaded etc.
# If you want to control earlier settings, see mint.ini file.
#
# Edit this with a normal ASCII text editor. Lines starting with '#'
# are comments. Other lines are commands for MiNT to execute at boot
# up, or variables that control how MiNT behaves.
# NOTICE: as of FreeMiNT 1.16.0, the format of most keywords has
# changed. Old keywords are still supported, however, you
# cannot use this configuration file for older versions
# of MiNT!
# The term `sysdir' we use here is short for `system directory' and
# means the directory, where you keep your mint.cnf file, your
# modules (XFS and XDD files) and other such system binaries. The
# sysdir value is usually u:/c/mint.
#
# For clarity, it is assumed all over this example file, that your
# boot drive is C:, and, if you have installed SpareMiNT distribution,
# that your SpareMiNT drive is E:. Note, that if you have installed
# SpareMiNT, you can refer to your sysdir as u:/boot/mint/
#
# -------------------- ACTUAL CONFIGURATION -----------------------
#
# Set current working directory to u: respective /
#
# FreeMiNT 1.16 does this automatically, this line is only required
# on previous versions (also on 1.16 alphas compiled before second
# half of July 2004).
#cd u:/
#
# ------------------ mint.cnf parser commands ---------------------
#
# The '#' sign at the begin of the line means that a comment follows.
# The entire line after the '#' sign will be ignored by the parser.
# The "set" directive controls the behaviour of the mint.cnf parser.
# It accepts one of three parameters:
#
#set -q - silent output (+q for verbose output)
#set -v - print command lines (+v don't)
#set -c - control interpretation of escape sequences
#set -q
# The include command allows you to include other files while the
# mint.cnf file is being interpreted. The included file will be
# interpreted as a part of the mint.cnf file.
#include u:/c/mint/vars.cnf
# More commands follow.
#
# ---------------------- Kernel settings --------------------------
#
#
# Here are things you can change if you want to. There are reasonable
# defaults for all of these.
#
# KERN_SLICES controls how long a process may run before being
# interrupted. The number means an amount of 20 ms time intervals.
#
# The default value (2) is usually best, but if you tend to run
# very processor intensive applications in the foreground, you might
# want to put KERN_SLICES=3 (this makes CPU hogs get more time than
# they otherwise would).
#
# The smaller the KERN_SLICES value, your processes have faster
# response time but the general performance is worse. Very fast
# machines however, may benefit from setting 1 here.
#KERN_SLICES=2
# KERN_DEBUG_LEVEL controls output of global debugging information.
# The higher the level, the more stuff MiNT will spew about about
# what it's doing.
#
# The average user doesn't want to hear about this stuff, so the
# default is 1, i.e. display ALERT messages only. Note that you need
# a debug kernel to get more: normal kernels do not contain so much
# debug information.
#
# KERN_DEBUG_DEVNO is the BIOS device number to which the info
# should be sent.
#
# Devno can be: 0=printer, 1=aux/modem, 2=screen (console), 3=midi,
# 4=keybrd, 5=raw.
#
# The default is the console.
#KERN_DEBUG_LEVEL=1
#KERN_DEBUG_DEVNO=2
# KERN_BIOSBUF controls how BIOS I/O is performed. Normally, MiNT
# tries to buffer this to provide a (considerable) improvement in
# speed. However, some applications may get upset by this.
#
# KERN_BIOSBUF=NO turns off all buffering for maximum compatibility.
# The default is YES.
#KERN_BIOSBUF=YES
# KERN_SECURITY_LEVEL= enables the appropriate security level:
#
# 0 - recommended for single user setups, like MultiTOS (default).
# 1 - recommended for multiuser setups, like KGMD.
# 2 - full protection, unsupported by software, thus discouraged.
#KERN_SECURITY_LEVEL=1
# KERN_MPFLAGS controls the memory protection behaviour. Its argument
# is a bitfield. Only the bit 0 is defined: 1 means, that more strict
# model of the protection should be enabled. Some programs may
# refuse to run, so the default is 0.
#KERN_MPFLAGS=1
# TPA_FASTLOAD=YES forces fast loading (without zeroing all the
# memory) for all programs. This defines a default state, that can be
# modified later via appropriate kernel calls (use MiNT Setter
# utility to toggle it later when neessary, without reboots).
#
# TPA_FASTLOAD=NO (default) means that the information from the
# program header will be used to decide (this is like TOS does).
#TPA_FASTLOAD=YES
# Set maximum additional TPA size for new processes
# (in kilobytes). The default is 1024. Better keep it low (1024 is
# what we call low) if your machine has 4 MB RAM or less.
#TPA_INITIALMEM=4096
# FS_NEWFATFS= enables the new FAT filesystem driver for selected FAT
# filesystems. The old TOS FS will be used otherwise.
#
# The default depends on whether the TOSFS driver is compiled into the
# kernel or not. If it is, all drives are TOSFS by default. If not,
# all drives are NEWFATFS by default and this keyword has no effect.
#FS_NEWFATFS=A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,V,W,X,Y,Z
# FS_VFAT= enables VFAT extension for selected drives specified in the
# FS_NEWFATFS= command. The VFAT extension is disabled by default.
#
# If you use both TOS and MiNT, better don't enable VFAT extension
# on your boot drive.
#FS_VFAT=D,E,F,G
# FS_VFAT_LCASE=YES tells the kernel to return lowercase filenames
# from VFAT directory searches. The default is NO.
#FS_VFAT_LCASE=YES
# FS_WB_ENABLE= enables write back cache for selected drives. The
# write back cache is disabled by default. Also, it does not have
# any effect for TOSFS drives.
#FS_WB_ENABLE=C,D,E,F
# FS_CACHE_SIZE= specifies the size of disk cache in kilobytes for the
# internal caching module. Default is 128.
#FS_CACHE_SIZE=4096
# FS_CACHE_PERCENTAGE specifies the size of the disk cache (in
# percents) to be filled with linear reads. The default is 5.
#FS_CACHE_PERCENTAGE=10
# FS_UPDATE= set update time for system update daemon in seconds
# default is 5, it isn't recommended to use a value less than 4.
#FS_UPDATE=10
# Software write protection on filesystem level.
#FS_WRITE_PROTECT=R,S
# FDC_HIDE_B= tells the MiNT to remove floppy drive B: from the
# system.
# It is useful on single floppy systems to get rid of "Insert
# disk B: into drive A:" messages from the AES. Default is NO.
#FDC_HIDE_B=YES
# PROC_MAXMEM= gives the maximum amount of memory that any process
# may use (in kilobytes). The default is to make this unlimited, but
# if you have a lot of memory and/or programs that grab more memory
# than they should, try setting this.
#
# E.g. to limit processes to 4096K of memory, remove the '#' at the
# beginning of the next line.
#
# WARNING: the process will not be allowed to allocate memory beyond
# the limit, and it won't "see" more memory as available from the
# system.
# Please understand that programs like "free" (or any other that
# interrogates the system how much memory is available) is a process
# as well, thus it will undergo this limit too!
#
# Decent shells (desktops) allow you to limit the maximum amount of
# memory independently for each program.
#PROC_MAXMEM=4096
# Three commands, that define output files for RS-232, console and
# printer devices. The argument for each one must be a pathname.
#
# For best results, the convention u:/drive/pathname should be used
# for all specified pathnames from now on.
#GEMDOS_AUX=u:/c/mint/aux.out
#GEMDOS_CON=u:/c/mint/con.out
#GEMDOS_PRN=u:/c/mint/prn.out
# End of kernel settings
#
# -------------------------- Commands ------------------------------
#
# Here are some commands that you can give to MiNT:
#
# alias d: path -- make a fake "drive" that actually points to the
# given path
# cd path -- changes MiNT's default directory
# echo message -- print something on the screen
# exec program -- runs a program; you must give the complete path
# and file extensions (e.g. c:/bin/echo.prg)
# include file -- include another portion of the MINT.CNF file.
# sln path link -- make a symbolic link named "link" pointing to
# "path". "link" must be on drive U: for this to work
# Examples follow
#
# Notice you have to adjust commands below for your filesystem
# structure.
#
# You could use "alias" to provide a quick way of getting at
# nested directories, e.g. if you do
#
# alias r: u:/c/some/long/path
#
# then clicking on drive r: puts you into the folder c:/some/long/path
# The "sln" command may be used to create "links" on drive U:. If
# u:/foo is a link to c:/bar, then u:/foo/foo.txt is another way
# of saying c:/bar/foo.txt. Judicious use of links can make
# re-arranging hard disks and directories painless (if you always
# use the names on drive u:, it doesn't matter where you put
# the actual directories).
# Setting up the root filesystem for UNIX environment
#
# WARNING: directories listed in the left column must really exist!
sln c:/mint/1-19-c02/sys-root/bin u:/bin
#sln e:/boot u:/boot
sln c:/mint/1-19-c02/sys-root/etc u:/etc
#sln e:/home u:/home
#sln e:/lib u:/lib
#sln e:/mnt u:/mnt
sln c:/mint/1-19-c02/sys-root/opt u:/opt
sln c:/mint/1-19-c02/sys-root/root u:/root
#sln e:/sbin u:/sbin
sln c:/mint/1-19-c02/sys-root/share u:/share
sln c:/mint/1-19-c02/sys-root/tmp u:/tmp
#sln e:/usr u:/usr
sln c:/mint/1-19-c02/sys-root/var u:/var
# Some people want also to do this:
#sln u:/pipe/pty.A u:/dev/pty.A
#sln u:/pipe/pty.B u:/dev/pty.B
#sln u:/pipe/pty.C u:/dev/pty.C
#sln u:/pipe/pty.D u:/dev/pty.D
#sln u:/pipe/pty.E u:/dev/pty.E
#sln u:/pipe/pty.F u:/dev/pty.F
#sln u:/pipe/pty.G u:/dev/pty.G
#sln u:/pipe/pty.H u:/dev/pty.H
#sln u:/pipe/pty.I u:/dev/pty.I
#sln u:/pipe/pty.J u:/dev/pty.J
#sln u:/pipe/pty.K u:/dev/pty.K
# PCONVERT and UNIXMODE variables control some internals of
# MiNT Library.
#
# FreeMiNT 1.16.0 sets these two below automatically.
# Default values are as below.
#setenv PCONVERT PATH,HOME,SHELL
#setenv UNIXMODE /brUs
# Default path
#
# Default on 1.16.0 is c:/, on 1.16.1 this is the sysdir.
setenv PATH /sbin;/bin;/usr/sbin;/usr/bin
# Default path to search the SLBs (MagiC style 'shared libraries
# Default - on 1.16.0 - is the system directory (so called sysdir).
#
# Note, that FreeMiNT 1.16.0 and up will search SLBs in the sysdir
# automatically, if found nowhere else, so it is useless to
# explicitly add this here.
setenv SLBPATH /c/mint/slb
# It is advisable to set this here to a preferred name
setenv HOSTNAME saturn
# This also can be useful
setenv TMPDIR u:/tmp
# Checking filesystem if necessary
# Note: you need a correct /etc/fstab
#exec u:/c/mint/bin/sh u:/c/mint/bin/fscheck.sh
#echo
# Alternative method, if you have e2fsck.ttp in /c/mint,
# and e: is your ext2fs drive.
#exec u:/c/mint/e2fsck.ttp -C 0 -p e:
# Set up time stuff. Note that you need MiNT Lib timezone package
# (installed along with the library) for this below to work.
#
# Such settings are valid if your clock ticks in UTC. For local
# time you have to add -l to the tzinit.
#setenv TZ 'Europe/London'
#exec u:/sbin/tzinit
#exec u:/sbin/tzinit -l
# The "exec" command is used to launch programs. Note that programs
# so launched are started before GEM is, so they must be TOS/TTP
# programs.
# Start Draconis to MiNT-Net gateway
#exec u:/c/mint/mgw.prg
#echo
# Start Gluestik
#exec u:/c/mint/gluestik.prg
#echo
# Default login variables. Leave them commented out, if you use
# UNIX style login. If you're using plain MultiTOS and want to
# run UNIX shells under TOSWIN, please uncomment it.
setenv LOGNAME root
setenv USER root
setenv HOME /root
setenv SHELL /bin/bash
# These lines (with proper pathnames) are obligatory, if you're
# going to use N.AES and Thing Desktop, respectively.
#
# Note that of you don't set the THINGDIR, the Thing desktop
# will store all its files in your $HOME.
#setenv AESDIR u:/c/mint/n_aes/
#setenv THINGDIR u:/c/mint/thing/
# The best option is to have INIT= command here, after all pathnames
# are already set up by commands above.
# If the MiNT is supposed to execute GEM, you should specify the full
# path and filename like that:
GEM=u:/c/mint/1-19-c02/xaaes/xaloader.prg
# You can also request MiNT to execute the TOS AES residing in ROM.
# WARNING: this is not recommended, you should use a GEM version
# instead, that is multitasking friendly.
#GEM=ROM
# Otherwise, if your init program is not GEM, you should use INIT= as
# follows:
#INIT=u:/c/mint/init.prg
# If you leave both commands above commented out, the MiNT will
# attempt to execute a file called `sh.tos' found in the system
# directory (the same where the mint.cnf resides), and if this
# fails, the internal minimum shell will be executed.
# Before the MiNT executes the rest of the operating system, it is
# usually the best to change the current directory to the top
# directory of all filesystems.
#
# FreeMiNT 1.16.0 does this automatically.
#cd u:/
#
# The "echo" command is really straightforward.
#
echo Setup complete, now booting the system...
echo

BIN
mint/1-19-c02/mintv4e.prg Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/nfs.xfs Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/autumn.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/default.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/flwrpwr.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_blue.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_cyan.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_green.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_purple.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_red.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/g_yellow.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/menubar.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/mint.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_blue.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_cyan.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_deflt.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_green.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_purple.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_red.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/gradient/n_yellow.grd Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/dbox.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/dbutton.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/dtext.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/exterior.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/info.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/popbkg.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/slide.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/slider.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/slwtitle.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/8b/wtitle.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/hc/dbox.img Normal file
View File

Binary file not shown.

BIN
mint/1-19-c02/xaaes/img/hc/dbutton.img Normal file
View File

Binary file not shown.

Some files were not shown because too many files have changed in this diff Show More