From 5a701fc07a17e2b74699a6a6a3ba9f8c020ec650 Mon Sep 17 00:00:00 2001 From: Steve McIntyre <93sam@debian.org> Date: Thu, 1 Apr 1999 06:58:02 +0000 Subject: [PATCH] Initial revision --- COPYING | 340 +++++++++++ EOP | 3 + README | 317 ++++++++++ README.1ST.alpha | 30 + README.1ST.i386 | 33 ++ README.1ST.m68k | 18 + README.1ST.sparc | 50 ++ README.m68k | 157 +++++ README.multicd | 21 + arch | 23 + boot-alpha | 106 ++++ boot-i386 | 110 ++++ boot-m68k | 180 ++++++ boot-sparc | 78 +++ cts_amiga_info.tar.gz | Bin 0 -> 1817 bytes debian/changelog | 249 ++++++++ debian/config | 74 +++ debian/control | 15 + debian/copyright | 8 + debian/dirs | 3 + debian/rules | 145 +++++ debian/substvars | 0 exclude-alpha | 3 + exclude-i386 | 0 exclude-m68k | 18 + exclude-sparc | 9 + flatten | 81 +++ foo | 0 hfs.map | 6 + isomarkboot-alpha | Bin 0 -> 13736 bytes isomarkboot-i386 | Bin 0 -> 25884 bytes macinstall-cd.tar.gz | Bin 0 -> 77773 bytes master | 1233 +++++++++++++++++++++++++++++++++++++++ mkhybrid.diff | 929 ++++++++++++++++++++++++++++++ mkisofsrc | 7 + mklinks | 69 +++ mklist | 185 ++++++ pkg-order | 415 +++++++++++++ slink1.info | 1 + slink1.list | 5 + slink1.needed | 795 +++++++++++++++++++++++++ slink1.volid | 1 + slink2.extras | 3 + slink2.info | 1 + slink2.list | 8 + slink2.optional | 416 ++++++++++++++ slink2.volid | 1 + slink3.extras | 2 + slink3.info | 1 + slink3.list | 12 + slink3.volid | 1 + slink4.extras | 2 + slink4.info | 1 + slink4.list | 19 + slink4.volid | 1 + slink5.extras | 2 + slink5.info | 1 + slink5.list | 5 + slink5.volid | 1 + slink_cd | 1280 +++++++++++++++++++++++++++++++++++++++++ useful | 396 +++++++++++++ vecho | 22 + 62 files changed, 7892 insertions(+) create mode 100644 COPYING create mode 100644 EOP create mode 100644 README create mode 100644 README.1ST.alpha create mode 100644 README.1ST.i386 create mode 100644 README.1ST.m68k create mode 100644 README.1ST.sparc create mode 100644 README.m68k create mode 100644 README.multicd create mode 100755 arch create mode 100755 boot-alpha create mode 100755 boot-i386 create mode 100755 boot-m68k create mode 100755 boot-sparc create mode 100644 cts_amiga_info.tar.gz create mode 100644 debian/changelog create mode 100644 debian/config create mode 100644 debian/control create mode 100644 debian/copyright create mode 100644 debian/dirs create mode 100755 debian/rules create mode 100644 debian/substvars create mode 100644 exclude-alpha create mode 100644 exclude-i386 create mode 100644 exclude-m68k create mode 100644 exclude-sparc create mode 100755 flatten create mode 100644 foo create mode 100644 hfs.map create mode 100644 isomarkboot-alpha create mode 100644 isomarkboot-i386 create mode 100644 macinstall-cd.tar.gz create mode 100644 master create mode 100644 mkhybrid.diff create mode 100644 mkisofsrc create mode 100755 mklinks create mode 100755 mklist create mode 100755 pkg-order create mode 100644 slink1.info create mode 100644 slink1.list create mode 100644 slink1.needed create mode 100644 slink1.volid create mode 100644 slink2.extras create mode 100644 slink2.info create mode 100644 slink2.list create mode 100644 slink2.optional create mode 100644 slink2.volid create mode 100644 slink3.extras create mode 100644 slink3.info create mode 100644 slink3.list create mode 100644 slink3.volid create mode 100644 slink4.extras create mode 100644 slink4.info create mode 100644 slink4.list create mode 100644 slink4.volid create mode 100644 slink5.extras create mode 100644 slink5.info create mode 100644 slink5.list create mode 100644 slink5.volid create mode 100755 slink_cd create mode 100644 useful create mode 100644 vecho diff --git a/COPYING b/COPYING new file mode 100644 index 00000000..60549be5 --- /dev/null +++ b/COPYING @@ -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. + + + Copyright (C) 19yy + + 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) 19yy 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. + + , 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. diff --git a/EOP b/EOP new file mode 100644 index 00000000..00428ebf --- /dev/null +++ b/EOP @@ -0,0 +1,3 @@ +# END_OF_PROCESSING must be here to catch the end of this file - the next file +# is actual package data and we need a separator. +END_OF_PROCESSING diff --git a/README b/README new file mode 100644 index 00000000..e6d6fa02 --- /dev/null +++ b/README @@ -0,0 +1,317 @@ +README for slink_cd v 1.13, released Mar 31 1999 +(c) Steve McIntyre + +What this program does +====================== +It will create CDs of Debian from a local set of files. You will +probably need to mirror most of the Debian site; check out the Debian +mirror package for an example of how to this. A full mirror will take +about 7GB at the time of writing. + +What this program doesn't do +============================ +It does not fix world hunger or bring peace on earth. And it's not +guaranteed to work at all, in fact. But if you have any problems, +please contact me and tell me about them. I'll be glad to help and to +fix any bugs that you might find. + +What it needs +============= +You will almost definitely need a Linux box to run the scripts here, +preferably a Debian one. I haven't had the chance to test on other +machines, but I'm fairly certain there are bits that won't run. + +To make the full set of images you will need a lot of disk space - +each CD image will take up ~600MB. And of course you'll need the +mirror itself for the files. But this no longer has to be local - see +"Making a symlink-farm" below. + +In terms of other software, you'll need + + perl + bash + sed + awk (any awk should do) + +These _should_ be standard on any Linux system. You'll also need: + + mkisofs/mkhybrid (a recent version - the standard one in Debian slink + should do) + + a PATCHED mkhybrid (if you want to use the symlink-farm method - see below) + + slice (to create the slink1.needed file from master) + + dpkg-multicd (VERY Debian-specific. Maybe it will work on other systems, + but I don't know and you'll probably have to play with it) + + cdwrite/cdrecord (to write the images once you've created them. They will + be standard ISO images, so even most *spit* Windoze CD + creation programs should be able to write them at a + push.) + sysutils + pkg-order + dpkg-perl + unzip (for i386 bootable CDs) + lha (for m68k CDs) + silo (if you want to create sparc disks - this may be problematic + on non-sparc machines) + isomarkboot (for alpha CDs - source is in the aboot package, binaries + for i386 and alpha are contained in this tar file) + m68k-cd-misc.tar.gz (from the same place you got this package, + for m68k CDs. Copy it to $BASEDIR before you start.) + hfsutils (for Mac stuff on m68k CDs) + +There may be other things too, but for now these are all I can think of. + +How do I use it? +================ +To be reading this, you must have extracted the tar file. Good +start. Next what you need to do is: + + customise the file lists (slink.{needed,useful,list}) if necessary + edit slink.info (dselect multicd disk info) + list any extras in slink.extras + edit slink.volid (ISO VOLID) + edit mkisofsrc (other ISO headers) + list any packages to be excluded in exclude-$ARCH if necessary + set up parameters in slink_cd or in the environment + run slink_cd with appropriate parameters + +Huh? +==== +Customise the file lists if you want to. The lists distributed with +this program should work for most people, and will be the basis of the +official Debian slink CD images when they are made. + +The (Debian) contents of discs 1 and 2 are calculated at run-time to +match as closely as possible the list of files needed by the Debian +install programs, and then the rest of the packages are split +(hopefully) sensibly. If you wish to produce a single standalone disc +of the key parts of Debian, this is easy - see "Single Debian discs" +below. If you want to create more complete sets, this is also easy. + +The file "master" lists the packages that are REQUIRED for all the +standard suggested systems to work at first install. These packages +come to about 300MB in total. The file "slink1.useful" contains a list +of further packages that I and others thought should also go on the +first disc and these take about 220MB more. This second list can +easily be modified if you so desire, but if you do please be careful +that the dependencies are met, as I did. The package "pkg-order" is +very useful here. When the lists for disc 1 is created, these packages +plus any others of "important", "standard" or "required" priority will +be marked to go on disc 1. The rest of the binary packages from the +main section will go onto disc 2, taking about 325 MB. + +And, finally, list the packages you want to _completely_ exclude from +the CDs in exclude-$ARCH. Reasons for doing this may include unmet +dependencies, broken packages, broken Packages files etc. + +Beyond this list of packages, the rest of the specification is quite +easy. For each disc, a file slink.list should contain a list of +files to go onto that disc. These can list directories or files, +either will work. The standard layout will look something like: + + 1: main binary-ARCH section 1 + docs + install stuff + boot disks + 2: main binary-ARCH section 2 + contrib (binary-ARCH and source) + (OPTIONAL) non-US (binary-ARCH and source) + project + 3: main source section 1 + 4: main source section 2 + 5: (OPTIONAL) non-free (binary-ARCH and source) + +* ARCH is a special keyword - see below for more info. + +============================================================================= +NOTE: The non-free section is not part of Debian and the programs contained + within are not endorsed by Debian, but they have been packaged as a + service to our users who may still need them until free alternatives + have been made available. +============================================================================= + +The non-US section is slightly complicated by the fact that in most +cases it will have to be mirrored separately, as the main Debian +servers in the USA cannot legally export this software. More on +the non-US configuration later. + +To generate the 5th (non-free) CD you will need to specify "non-free" +as a command-line option when running slink_cd. To add the non-US +section on disk 2 you will need to specify "non-US" as an option. + +Other things to be configured: + +The dselect (installation) multi-cd install method uses the contents +of a file .disk/info on each CD when determining the contents of a +disc and in deciding which discs are needed. The .info file for each +disc will be created using slink.info. Edit these accordingly, and +the date will automatically be added by the script when used. + +Extra files may be added to each disc if you desire. Many OEM +producers of Debian CDs may want to use this - it allows you to +customise the contents of your CDs, for example if you wish to add +extra software of your own or other local content. Simply list them in +slink.extras. + +The CD Volume ID for each disk will be created from the contents of +slink.volid. + +If you wish to configure other options in the CD ISO headers, edit +mkisofsrc. See the mkhybrid/mkisofs documentation for more details. + +============================================================================= + Working examples for all of these files are given. +============================================================================= + +* In ALL of these files, the keyword "ARCH" is magic and will be + replaced by the appropriate architecture (i386,m68k,powerpc,sparc,alpha) + when you run the scripts here. This makes it easier to produce images for + several platforms in one run. + +e.g. in slink1.list: + + dists/slink/main/binary-ARCH/Release + + will become + + dists/slink/main/binary-i386/Release + +when run to produce i386 disks. + +The other things to configure are found in the main slink_cd script itself: + +ARCH - the target architecture +MIRROR - the location of your Debian mirror +NONUS - the location of the non-US part of your Debian mirror, + if applicable +MKISOFS - the location of your mkisofs/mkhybrid program +MKISOFS_OPTS - the options to use with your mkisofs/mkhybrid program +TDIR - the location of the temporary directory to use. This must be + on the same partition as your mirror, unless you use the + "genlinks" option to create a sym-link farm (below) +OUT - the directory in which we should write the completed images +BOOTDIR - (sparc specific) - where do we find silo? + +All of these can be changed by using environment variables, which is +especially useful when making CDs for multiple architecture in one +run. See the "arch" script for an example of this. + +Making a sym-link farm +====================== +When slink_cd is run, temporary trees/files will be made under +$TDIR. This no longer MUST be on the same partition as the mirror, +for the hard-links hack to work. There is now a new option, +"genlinks", which will create a tree of sym-links for you from a +mirror elsewhere, be it scattered across several mount points (small +disks) or mounted readonly via NFS from another machine. The CD images +can then be created from the sym-link farm. There are a couple of +limitations to this method, so the original hard-links method will +still be preferred and is the default. These limitations are: + +speed: the sym-links method is much slower, for a variety of reasons +reliability: the final "du" output of the script is no use with sym-links, + so you will probably have to create the CD images to make sure + all is well in testing. +compatibility: the hard-links method will work with any recent version of + mkhybrid/mkisofs, but to use the sym-links method you need a + specially patched version of mkhybrid. + +There is a patch for mkhybrid 1.12a4.7 included with this +program. Grab the original source from +http://www.ps.ucl.ac.uk/~jcpearso/mkhybrid.html or +http://www.chiark.greenend.org.uk/~stevem/DebianCD/ . There is also a +statically-linked i386 binary at the latter site. You will also need +to add the "-F" option to the mkhybrid command line for this sym-links +hack to work. + +Non-US +====== +To make Debian CDs with the non-US section you will need to specify +the location of your non-US mirror, and also add "non-US" to the +slink_cd command line. The default place for the non-US stuff is on +disc 2, but this can be changed. + +Non-free +======== +To make a set of Debian CDs with the non-free section you will need to +add "non-free" to the slink_cd command line. This will create a tree +etc. for the fifth disc, containing non-free. Attempting to create the +fifth disc without specifying "non-free" will fail. See the earlier +disclaimer about the non-free section. CD producers should definitely +read the copyrights of non-free packages to check they can sell them on +CD before doing so. Debian packages contain copyright information in +/usr/doc//copyright. + +Single Debian discs +=================== +Some producers may want to make single Debian CDs that will work on +their own without mentioning packages that would be on the other +CDs. The "single_disk" option should work for these people. And check +the extras lists above if you want to add more of your own +software/data to this single disc - the layout has been specifically +optimised so you have ~100MB of space there for you. Of course, this +layout will mean that many of the Debian binary packages will not be +packaged up and also there will be no source. Check the GPL and other +licenses to see what this means to you... + +Complete options list +===================== +You can specify any combination of steps to do on the command-line: + + clean removes old link trees + genlist creates a list of files optimised to make disc#1 as standalone + as possible, with ~100MB spare for local customisations + (see "extras"). Check the contents of "slink1.useful" - + this lists the Priority: optional main binary-$ARCH packages + that will be moved to CD#1. Also checks that the Packages file + is up-to-date (maybe not on a borken mirror) and creates a new + one if not. + genlinks creates a sym-link farm in $TDIR/tmp-mirror to work from + tree creates new link trees + single_disk makes a single disc (#1) which will stand alone (SEE BELOW) + flatten goes through the trees removing sym-links outside of the + selected dist + md5check checks the md5sums of all the packages and boot disks + in the trees + packages creates Packages.cd files to go on each CD, and then checks them + for consistency of dependencies + boot adds the bootable CD and install tools as appropriate + extras adds specified extras to the CDs (see below) + md5list creates a complete md5sum of each CD tree to go on the disk + images actually create all the ISO images. Make sure all the necessary + steps above have been run first, or these images may be + complete garbage + image Create image number x, where x is 1-4 or can also be 5 if + non-free is built. + imagesums Once the images are made, make md5sums of them into "MD5SUMS" + i386 targets binary-i386 + m68k targets binary-m68k + alpha targets binary-alpha + sparc targets binary-sparc + powerpc targets binary-powerpc + non-free adds the stuff for CD #5 (non-free) + non-US adds the non-US stuff for CD #2. + -v increments the debug level. Default level is 0, maximum is 3 + force_deps continue on even if the pkg-order check fails in "packages" + above. Use with care! + +N.B. "single_disk" should now be obsoleted due to changes in the +layouts, but should still work. + +If you specify no command-line options then the standard set of +commands (see below) will be done in order. THIS WILL NOT MAKE ANY +IMAGES. + +Some options will not work together. Some options depend on others +Some of these combinations are obvious, but in particular: + + "tree" needs "genlist" + "flatten" will not work with "genlinks" + "image5" needs "non-free" + "single_disk" will not work with "non-free" or "non-US" + "imagesums" needs at least one "image[12345x]" + +END. diff --git a/README.1ST.alpha b/README.1ST.alpha new file mode 100644 index 00000000..18b49e79 --- /dev/null +++ b/README.1ST.alpha @@ -0,0 +1,30 @@ +README for Debian 2.1 CD installation (Alpha architecture). +========================================================== + +To boot the installation system from CD, you will need the instructions +in /dists/stable/main/disks-alpha/README, then insert CD#1 in your CD-ROM drive + and boot. + +CD#1 contains milos and kernels for all architectures supported by Linux. + +If your system will not boot from CD: +- Make boot floppies from the images on the first CD, in the directory + \dists\stable\main\disks-alpha\current. + + From a Unix (including Linux) system use: + dd bs=18k if=/dists/stable/main/disks-alpha/current/xxx/resc1440.bin of= + dd bs=18k if=/dists/stable/main/disks-alpha/current/root1440.bin of= + + From a DOS system, the program rawrite2.exe will also write the floppy images. e.g. + + d: (change to the CD drive) + cd \dists\stable\main\disks-alpha\current + rawrite2 -f resc1440.bin -d a: (a: is the 1.44 MB floppy drive) + + +See /install/install.txt for more information, and /README.multicd for +last-minute information about the multi-cd installation method. + +Loic Prylli 3 Mar 1999 diff --git a/README.1ST.i386 b/README.1ST.i386 new file mode 100644 index 00000000..7d62d547 --- /dev/null +++ b/README.1ST.i386 @@ -0,0 +1,33 @@ + +README for Debian 2.1 CD installation. +====================================== + +To boot the installation system from CD, you will need to insert +either CD#1 or CD#2 in your CD-ROM drive and reboot. + +CD#1 contains a normal kernel that should work for most people and +contains many drivers. + +CD#2 is a smaller system based on the "tecra" kernel - this is smaller +because it has fewer drivers compiled in to avoid a known problem with +large kernels on laptops, especially the Toshiba Tecra series. + +If your system will not boot from CD, there are other options: + +1.Boot a DOS system with CD drivers, then run boot.bat from the + \install direcory on the first CD. + +2.Make boot floppies from the images on the first CD, in the directory + \dists\stable\main\disks-i386\current. The program rawrite2.exe in + that directory will write the floppy images under DOS. e.g. + + d: (change to the CD drive) + cd \dists\stable\main\disks-i386\current + rawrite2 -f resc1440.bin -d a: (a: is the 1.44 MB floppy drive) + + +See \install\install.txt for more information, and \README.multicd for +last-minute information about the multi-cd installation method. + +Steve McIntyre 15 Feb 1999 + diff --git a/README.1ST.m68k b/README.1ST.m68k new file mode 100644 index 00000000..ef2e29e9 --- /dev/null +++ b/README.1ST.m68k @@ -0,0 +1,18 @@ + +README for Debian 2.1 CD installation. +====================================== + +If you have a BVME 4000 or 6000, you can boot the installation system +from CD. You will need to insert CD#1 in your CD-ROM drive and reboot. + +If your system will not boot from CD, you should run the appropriate +installation program for your system. They are in subdirectories of +install for each platform (amiga, atari, mac, vme). + +See \install\install.txt for more information. Some more detailed +notes about this CD set are in \README.m68k. Also check \README.multicd for +last-minute information about the multi-cd installation method. + +Chris Lawrence 12 Feb 1999 + + diff --git a/README.1ST.sparc b/README.1ST.sparc new file mode 100644 index 00000000..0b90b24b --- /dev/null +++ b/README.1ST.sparc @@ -0,0 +1,50 @@ +README for Debian 2.1 CD installation. +====================================== + +To boot the installation system from CD, you will need to insert +either CD#1 in your CD-ROM drive, drop to the PROM prompt (Stop-A), +and enter: "boot cdrom" (if you have an older PROM, you may have to +use "b sd(0,6,0)" instead). + +This CD should boot on sun4c, sun4m, and sun4u systems. At the silo +prompt you will be given a choice of linux or linux-2.2.1 (if you just +press return, you get linux). The former provides the officially +supported 2.0.35 kernel, and the latter provides a 2.2.1 kernel. +Some sun4m systems have been known to not boot the 2.0.35 kernel, so if it +locks up while the background is still white, try the 2.2.1 kernel. + +There is no 2.0.35 kernel for Ultras, so on those machines you will get +the 2.2.1 kernel regardless of what you select. + +If your system will not boot from CD, there are other options: + +1. Make boot floppies from the images on the first CD, in the directory + /dists/stable/main/dists-sparc/current. The program rawrite2.exe in + the /tools directory will write the floppy images under DOS. e.g. + + cd /dists/stable/main/disks-sparc/current + rawrite2 -f resc1440.bin -d a: + + Under Unix, this can be done with "dd" or "cat" (see the documentation + in the /install directory). + +2. Use tftp booting (documented in the /install directory). The tftp + boot images are also in /dists/stable/main/dists-sparc/current. The + file tftpboot.img supports 32-bit sparc machines and uses a 2.0 kernel + and the file tftpboot-2.2.1.img supports all sparc machines and + uses a 2.2.1 kernel. + +See /install/install.txt for more information, and /README.multicd for +last-minute information about the multi-cd installation method. + +The install documentation in /install was up to date when this CD image +was created. The Debian web site has the most up-to-date information at + + http://www.debian.org/releases/slink/sparc + +which may document issues that were discovered after these CD images +were created. + + +Steve Dunham +March 6, 1999 diff --git a/README.m68k b/README.m68k new file mode 100644 index 00000000..307b1954 --- /dev/null +++ b/README.m68k @@ -0,0 +1,157 @@ +README for Debian/m68k 2.1 CD-ROM set +------------------------------------- +The Debian/m68k CD-ROM set consists of two binary CDs containing the +contents of the Debian GNU/Linux 2.1 ("slink") distribution for m68k +systems; as the source CDs are identical for all Debian platforms, +those are omitted in this particular set. There is no Debian/m68k +non-free CD-ROM image containing additional software that does not fit +the Debian Free Software Guidelines (like Aladdin Ghostscript, pine +and xv). Some non-free packages compiled for m68k are available at +your local Debian mirror (see README.mirrors.txt for a list). + +Non-US software has been excluded from these images as well. These +packages are available at most Debian mirrors outside North America, +and many of them can be freely imported into the United States and +Canada. However, they cannot be exported from the United States. + +The packages on these CDs should be compatible with Linux/m68k 2.0 and +2.2 kernels, although they have only been extensively tested with the +former. All of them should work on any Linux/m68k platform (including +those we don't officially support yet), with the exception of the +platform-specific kernels and certain programs that take advantage of +platform-specific features (like the setsscserial package). + +If you are installing for the first time and running a 2.2 kernel, you +may have problems; try switching to the second virtual console +(left-alt-F2) and typing 'dinstall' if the installation program +doesn't come up during the boot process. + +Supported Platforms +------------------- +Please note that on any system the minimum requirements are a 68020, +68030, 68040 or 68060 processor with a memory management unit and a +floating point unit (either on-chip or on a separate chip). At least +6 MB of usable system RAM will be necessary to install Debian. + +As of the Debian 2.1 release, the following m68k platforms are +officially supported by Debian/m68k. + +* Amiga (and possibly some clones; DraCo definitely NOT supported) +* Atari ST/TT/Falcon/Medusa +* Apple Macintosh (most non-Powerbook models; for the latest, check + http://www.mac.linux-m68k.org/) +* BVM Ltd. BVME 4000 and 6000 single-board computers + (see http://www.sleepie.demon.co.uk/linuxvme/) +* Motorola VMEbus (MVME 162, 166, 167) single-board computers + (see http://www.sleepie.demon.co.uk/linuxvme/) + +Please consult the Linux/m68k FAQ (included on the first CD) to see if +your specific system configuration is supported. + +You may be able to use Debian on other m68k platforms with kernels +that are distributed elsewhere; however, Debian does not officially +support any platforms not on the list above. Reports of success and +failure will be appreciated by the developers. + +Extras +------ +The first CD includes several extra directories that are not included +in Debian CDs for other platforms: + +* m68k-faq: Includes the most recent version of the Linux/m68k FAQ. + If you don't have a web browser, you can read the text version + (however, you need gzip to decompress it) or the PDF version (using + Adobe Acrobat, xpdf or Ghostscript). + Please pay particular attention to the hardware requirements for + your system type. + +* m68k-tools: In subdirectories for Amigas and Ataris, versions of + GNU zip and GNU tar. The Amiga directory also includes an ancient + version of ixemul.library, which may be necessary to run amiboot, + gzip and/or tar. The Atari directory includes "rawwrite.ttp", which + may be useful for creating installation floppies (if you choose to + install that way). + +* install: In subdirectories for each m68k platform, the unpacked + contents of the installation kits. A copy of the official + Debian 2.1 installation guide and unofficial Linux/m68k-specific + installation guides for Amiga, Atari and Mac users are included + here. + + The install directory itself contains the base tarfile + (base2_1.tgz), which is used by the installation program to install + your base system. It also includes the Debian Installation Guide + and a tutorial on how to use "dselect"; both of these documents are + available in HTML (for use with a web browser) and as plain text files. + + Subdirectories contain the other files which are needed for each + platform, which are generally named as follows: + + 1. A driver disk image (drv1440.bin) + 2. A rescue disk image (resc1440.bin) + 3. A compressed root disk image (root.bin) + 4. A compressed Linux/m68k 2.0.36 kernel image (linux) + 5. A compressed kernel mapfile (sysmap.gz; useful for debugging) + 6. A bootstrap program (name varies). + 7. A text file with detailed installation instructions + (on the Amiga, Atari and Mac only at present). + + Note that in the vme directory, the bvme6000 files are also used on + the BVME 4000, and the mvme167 files are also used on the MVME 166. + +The Intel-specific "tools" directory is provided for people who have +access to Intel hardware to make bootable floppies. These tools are +not necessary for most users, however, since Debian GNU/Linux can be +installed directly from these CD-ROMs. + +In addition, the first CD is bootable on some of BVM Ltd.'s BVME +single-board computers; this feature should drop BVME users directly +into the Debian installation process by booting the rescue disk image. + +Additional file: +* update-mirror: A Python script that may help in keeping a Debian/m68k + binaries-only mirror up-to-date. Requires python-base and rsync. + +Upgrading from 2.0 +------------------ +If you have a Debian/m68k 2.0 (hamm) installation, refer to the +Release Notes (/Release-Notes) for details on how to cleanly upgrade +your installation. I recommend using the 'apt' method, either through +'dselect' or directly with apt-get. Systems running other +Debian-based distributions may also be upgradable using this method; +however, we make no guarantees, as we only tested with official Debian +systems. + +Install the new libc6 package BEFORE installing the new dpkg version. +The pre-dependencies on dpkg are set to require this ordering. + +Thanks +------ +Thanks to the following people who helped make this CD-ROM set possible: + +* Frank Neumann for getting the whole Debian/m68k project started, + writing the Amiga installation guide, and putting together the Amiga + installation kit. +* Michael Schmitz for putting together the Atari and Mac installation + kits and installation guides. +* Nick Holgate for putting together the VMEbus installation kit and + writing tftplilo. +* Roman Hodek and James Troup for the build daemons, which have saved + eons for the Debian/m68k developers. +* Steve McIntyre for writing the slink_cd script. +* Adam Di Carlo (the former Adam P. Harris) for maintaining the official + installation manual and incorporating our ruminations into it. +* Linus and everyone else who contributed to Linux and Linux/m68k. +* Last, but not least, the users of Debian/m68k, for using Debian, + filing bug reports and suggesting improvements to our distribution. + +Updated information, as always, will be on the web at +http://www.debian.org/ and http://www.linux-m68k.org/ + +Until we release "potato"... + + +Chris Lawrence +Oxford, Mississippi, USA +13 February 1999 + diff --git a/README.multicd b/README.multicd new file mode 100644 index 00000000..1884e14e --- /dev/null +++ b/README.multicd @@ -0,0 +1,21 @@ +Multicd installation instructions +================================= + +Once you have installed the base system and rebooted your machine, you +will need to go through and configure parts of the system (root +password etc.). After this you will be presented with dselect, the +standard package installation program on a Debian system. + +If you wish to use the multicd installation method, as is the default +for CD-based installs, you should be careful to insert the LAST BINARY +CD of your set when you start, e.g.: + + if you have a single CD, insert that single CD + if you have a 2-CD binary set, insert CD#2 + if you have an official 4-CD set, insert CD#2 + (#3 and #4 should contain source only) + etc. + +README.multicd +23 Feb 1999 +Steve McIntyre \ No newline at end of file diff --git a/arch b/arch new file mode 100755 index 00000000..6f1af5a5 --- /dev/null +++ b/arch @@ -0,0 +1,23 @@ +#!/bin/bash + +# Example script to use with slink_cd - this will create trees for +# i386, m68k, sparc and alpha. +# (c) Steve McIntyre 11 Feb 1999, released under GPL + +for ARCH in m68k i386 alpha sparc +do + echo TDIR=/debian/local/slinkcd-$ARCH OUT=/debian/local/OUT-$ARCH \ + MIRROR=/debian NONUS=/debian/Debian-non-US \ + ./slink_cd \ + clean genlist tree flatten md5check packages boot \ + extras $ARCH md5list images imagesums + + TDIR=/debian/local/slinkcd-$ARCH OUT=/debian/local/OUT-$ARCH \ + MIRROR=/debian NONUS=/debian/Debian-non-US \ + BOOTDIR=/usr/lib/silo \ + ./slink_cd \ + clean genlist tree flatten md5check packages boot \ + extras $ARCH md5list images imagesums +done + + diff --git a/boot-alpha b/boot-alpha new file mode 100755 index 00000000..f789d9d5 --- /dev/null +++ b/boot-alpha @@ -0,0 +1,106 @@ +#!/bin/bash +# +# boot-alpha v 1.13 (c) Steve McIntyre +# and Loic Prylli +# Released under GPL 31 Mar 1999 +# See the file COPYING for license details +# Released as part of the slink_cd package, not much use standalone +# +# Do install stuff for alpha, including making bootable CDs +# +# $1 is Debian-mirror location +# $2 is start directory location (where the scripts live) +# $3 is tmpdir location +# $4 is the binary arch +# $5 is debug level +# $6 is $BOOTDIR (not needed for i386, but let's stay consistent) + +MIRROR=$1 +BASEDIR=$2 +TDIR=$3 +ARCH=$4 +VERBOSE=$5 +BOOTDIR=$6 + +. $BASEDIR/vecho # Include local definitions for vecho, vvecho, vvvecho + +# Now check the boot-disks; make sure they exist and we +# have a "current" directory. If not, exit +if [ ! -e slink1/dists/stable/main/disks-$ARCH ] ; then + echo "No boot disks found for arch $ARCH." + echo "Exit." + exit 1 +fi + +cd slink1/dists/stable/main/disks-$ARCH +if [ ! -e current ] ; then + echo "No \"current\" boot disks found for arch $ARCH." + echo "Exit." + exit 1 +fi + +# OK, we have what we need. Now check and see what mess +# things are in. We _don't_ need more than one set of boot +# disks and it would be useful if the ftp maintainers +# would remove old versions instead of leaving them +# around... + +if [ -L current ] ; then + # Find the link, rename it for safety then put it back + CURRENT_LINK=`ls -l current | awk '{print $11}'` + mv $CURRENT_LINK .tmp_link + rm -rf 2* + mv .tmp_link $CURRENT_LINK +else + # We can simply remove all the others if current is a directory + rm -rf 2* +fi + +cd $TDIR +# Hack for bootable disks +vecho "Copying boot images to /boot for disc 1" + +echo "extract aboot(bootlx) from sable set" +echo dump srmbootcode boot1/boot/bootlx |\ + debugfs slink1/dists/stable/main/disks-$ARCH/current/sable/resc1440.bin +for subarch in avanti avanti-s xl xlt cabriolet eb66 eb66p eb64p eb164 pc164 \ + lx164 sx164 jensen noname takara mikasa mikasa-p noritake noritake-p alcor miata \ + sable sable-g book1 ruffian; do + mkdir boot1/boot/$subarch + echo "drive m: file=\"$TDIR/slink1/dists/stable/main/disks-$ARCH/current/$subarch/resc1440.bin\"" > mtoolsrc.tmp + echo "extracting stuff for $subarch" + case $subarch in + jensen|noritake*|mikasa-p|sable*|book1|miata-s|avanti-s|generic) + echo dump linux boot1/boot/$subarch/linux |\ + debugfs slink1/dists/stable/main/disks-$ARCH/current/$subarch/resc1440.bin + ;; + ruffian) + MTOOLSRC=$TDIR/mtoolsrc.tmp mcopy m:linux m:milo m:ldmilo.exe boot1/boot/$subarch/. + ;; + *) + MTOOLSRC=$TDIR/mtoolsrc.tmp mcopy m:linux m:milo m:linload.exe boot1/boot/$subarch/. + ;; + esac +done + +mkdir slink1/tools/rawrite1 +(cd slink1/tools/rawrite1; \ + unzip -Lq $MIRROR/tools/rawrite1.zip ) + +mkdir slink1/tools/rawrite2 +(cd slink1/tools/rawrite2; \ + unzip -Lq $MIRROR/tools/rawrite2.zip; \ + rm rawrite2.c ) + +(echo "Tools for DOS :" ; \ + echo "rawrite1/ rawrite 1.3 : create disks from disk images (*.bin)"; +\ + echo "rawrite2/ rawrite 2.0 : create disks from disk images (*.bin)"; +\ + echo " rawrite 2.0 is much faster, but it locks up on some machines";\ + ) |todos > slink1/tools/README.tools + +cp slink1/tools/rawrite1/rawrite3.com slink1/install/rw1_3.com +cp slink1/tools/rawrite2/rawrite2.exe slink1/install/rw2_0.exe + +exit 0 \ No newline at end of file diff --git a/boot-i386 b/boot-i386 new file mode 100755 index 00000000..ef29568c --- /dev/null +++ b/boot-i386 @@ -0,0 +1,110 @@ +#!/bin/bash +# +# boot-i386 v 1.13 (c) Steve McIntyre +# Released under GPL 31 Mar 1999 +# See the file COPYING for license details +# Released as part of the slink_cd package, not much use standalone +# +# Do install stuff for i386, including making bootable CDs +# +# $1 is Debian-mirror location +# $2 is start directory location (where the scripts live) +# $3 is tmpdir location +# $4 is the binary arch +# $5 is debug level +# $6 is $BOOTDIR (not needed for i386, but let's stay consistent) + +MIRROR=$1 +BASEDIR=$2 +TDIR=$3 +ARCH=$4 +VERBOSE=$5 +BOOTDIR=$6 + +. $BASEDIR/vecho # Include local definitions for vecho, vvecho, vvvecho + +# Now check the boot-disks; make sure they exist and we +# have a "current" directory. If not, exit +if [ ! -e slink1/dists/stable/main/disks-$ARCH ] ; then + echo "No boot disks found for arch $ARCH." + echo "Exit." + exit 1 +fi + +(cd slink1/dists/stable/main/disks-$ARCH/current/ ; \ + cp resc*.bin linux root.bin $TDIR/slink1/install ) + +cd slink1/dists/stable/main/disks-$ARCH +if [ ! -e current ] ; then + echo "No \"current\" boot disks found for arch $ARCH." + echo "Exit." + exit 1 +fi + +# OK, we have what we need. Now check and see what mess +# things are in. We _don't_ need more than one set of boot +# disks and it would be useful if the ftp maintainers +# would remove old versions instead of leaving them +# around... + +if [ -L current ] ; then + # Find the link, rename it for safety then put it back + CURRENT_LINK=`ls -l current | awk '{print $11}'` + mv $CURRENT_LINK .tmp_link + rm -rf 2* + mv .tmp_link $CURRENT_LINK +else + # We can simply remove all the others if current is a directory + rm -rf 2* +fi + +cd $TDIR +# Hack for bootable disks +vecho "Copying boot image to /boot for disc 1" +cp slink1/dists/stable/main/disks-$ARCH/current/resc1440.bin \ + boot1/boot +if [ -e slink1/dists/stable/main/disks-$ARCH/current/resc1440tecra.bin ] ; then + mkdir -p boot2/boot + vecho "Copying tecra boot image to /boot for disc 2" + cp slink1/dists/stable/main/disks-$ARCH/current/resc1440tecra.bin \ + boot2/boot +fi + +vecho "Extracting tools for disc 1" +mkdir -p slink1/tools/fips20 +(cd slink1/tools/fips20; \ + unzip -Lq $MIRROR/tools/fips20.zip; \ + rm restorrb source -rf) + +(cd slink1/tools; \ + unzip -Lq $MIRROR/tools/lodlin16.zip; \ + rm lodlin16/src lodlin16/initrd loadlin16/debian -rf ) + +mkdir slink1/tools/rawrite1 +(cd slink1/tools/rawrite1; \ + unzip -Lq $MIRROR/tools/rawrite1.zip ) + +mkdir slink1/tools/rawrite2 +(cd slink1/tools/rawrite2; \ + unzip -Lq $MIRROR/tools/rawrite2.zip; \ + rm rawrite2.c ) + +(echo "Tools for DOS :" ; \ + echo "fips20/ non-destructively shorten a FAT partition" ; \ + echo "lodlin16/ load Linux kernel from DOS" ;\ + echo "rawrite1/ rawrite 1.3 : create disks from disk images (*.bin)"; \ + echo "rawrite2/ rawrite 2.0 : create disks from disk images (*.bin)"; \ + echo " rawrite 2.0 is much faster, but it locks up on some machines";\ + ) |todos > slink1/tools/README.tools + +cp slink1/tools/lodlin16/*.exe slink1/install +cp slink1/tools/rawrite1/rawrite3.com slink1/install/rw1_3.com +cp slink1/tools/rawrite2/rawrite2.exe slink1/install/rw2_0.exe +cp slink1/tools/fips*/*.exe slink1/install + +(echo "@ echo off" ; \ + echo "rem Flush any write-cached disk blocks before we leave DOS. " ; \ + echo "smartdrv /c" ; \ + echo "loadlin.exe linux root=/dev/ram ro initrd=root.bin" ; \ + ) |todos > slink1/install/boot.bat + diff --git a/boot-m68k b/boot-m68k new file mode 100755 index 00000000..bfb12b3e --- /dev/null +++ b/boot-m68k @@ -0,0 +1,180 @@ +#!/bin/bash +# +# boot-m68k v 1.13 (c) Steve McIntyre , +# Chris Lawrence , Christian Steigies , +# Michael Schmitz +# Released under GPL 31 Mar 1999 +# See the file COPYING for license details +# Released as part of the slink_cd package, not much use standalone +# +# Do install stuff for sparc, including making bootable CDs +# +# $1 is Debian-mirror location +# $2 is start directory location (where the scripts live) +# $3 is tmpdir location +# $4 is the binary arch +# $5 is debug level +# $6 is $BOOTDIR +# +# Enjoy! This is all completely free. +# - Chris Lawrence +# +# Rewritten by Steve McIntyre in sh to +# interface better with the slink_cd package and cope with the mirror +# layout, 28 Feb 1999. +# Hopefully this will do the same job as the python map stuff did, it +# appears to... +# +# If you're burning a CD, use the mkhybrid in potato (HFS is broken in the +# slink version of mkhybrid; at least it is for me). Please don't use Joliet +# extensions; some Mac kernels have apparently been known to choke on them +# (and you really shouldn't be supporting a Microsoft Standard anyway :-) +# +# You may also want the following: +# * A copy of the Linux/m68k FAQ +# * A copy of my m68k-specific README and m68k-tools directories +# * The m68k kernel sources from sunsite.auc.dk:/projects/680x0 +# (Sunsite-Denmark is rsync-capable at sunsite.auc.dk::ftp) +# I recommend getting the 2.0.36 and 2.2.1-pre2 sources at least. +# (Actually 2.0.36 is non-essential since it's on the CDs already; +# you probably DO want the 2.2.1-pre2 tree however [under v2.1!]). +# +# MVME/BVME users will love you if you also include the "tools" directory +# from the FTP site, since they may want/need rawwrite for MS-DOS. +# +# The first two items are in a tar file at master.debian.org:~lawrencc, along +# with a silly rsync script that will accomplish the last item. + +MIRROR=$1 +BASEDIR=$2 +TDIR=$3 +ARCH=$4 +VERBOSE=$5 +BOOTDIR=$6 + +. $BASEDIR/vecho # Include local definitions for vecho, vvecho, vvvecho + +DISKSROOT="$MIRROR/dists/slink/main/disks-m68k/current" +CDROOT="$TDIR/slink1" +INSTALLDIR="$CDROOT/install" + +cd $INSTALLDIR + +vecho Installing Amiga files +lha xqf $DISKSROOT/amiga/amigainstall.lha +mv debian amiga +mv debian.info amiga.info +cp $DISKSROOT/amiga/* amiga + +# Needs to be executable +chmod a+x amiga/amiboot-5.6 + +# Add .info files for amiga +tar -C .. -xzf $BASEDIR/cts_amiga_info.tar.gz +for file in `tar tzf $BASEDIR/cts_amiga_info.tar.gz` +do + chmod a+r ../$file +done +# And fix a few things up... +mkdir common +mv basecont.txt.info common +mv ../README.info ../README.m68k.info +cp ../README.1ST.info ../README.multicd.info + +vecho Installing Atari files +lha xqf $DISKSROOT/atari/install.lzh +mv debian atari +cp $DISKSROOT/atari/* atari + +vecho Installing Mac files +tar -C .. -zxf $DISKSROOT/source/macinstall.tar.gz +cp $DISKSROOT/mac/* mac + +for TYPE in common bvme6000 mvme162 mvme167 source +do + vecho Installing $TYPE files + if [ ! -d $TYPE ] ; then + mkdir $TYPE + fi + cp $DISKSROOT/$TYPE/* $TYPE +done + +vecho hexbin Mac files +cd $INSTALLDIR/mac +hexbin *.hqx + +vecho Installing m68k FAQ and tools +mkdir $CDROOT/tmp +cd $CDROOT/tmp +tar xzf $BASEDIR/m68k-cd-misc.tar.gz +mv m68k-faq m68k-tools .. +mv update-kernels ../update-kernels.m68k +cd .. +rm -rf tmp + +cd $CDROOT +# make mountpoint and temp HFS filesystem image +rm -rf /var/tmp/mnt-macinstall +mkdir /var/tmp/mnt-macinstall +dd if=/dev/zero of=/var/tmp/macinstall-temp.img bs=1024 count=1440 +hformat /var/tmp/macinstall-temp.img +# mount it (':' is top dir) using hfsutils +hmount /var/tmp/macinstall-temp.img +# copy booter and preferences files in place (color table missing but +# Penguin-17 has colors fixed anyway +hcopy -b install/mac/Penguin-17.hqx : +hcopy -b install/mac/Penguin_Prefs.hqx :"Penguin Prefs" +hcopy -b "install/mac/Penguin_Prefs_(autoboot).hqx" :"Penguin Prefs (autoboot)" +# unmount HFS image +humount /var/tmp/macinstall-temp.img +# mount this HFS floppy image again as netatalk using the loopback mount command +if [ ! 'mount -t hfs -o loop,fork=netatalk,afpd /var/tmp/macinstall-temp.img /var/tmp/mnt-macinstall' ] ; then + # We managed to mount it loop-back + # copy over both Penguin-15 and .AppleDouble/Penguin-15 + # copy over both Penguin Prefs and .AppleDouble/Penguin Prefs + # (.AppleDouble files go into .AppleDouble subdir of target dir) + cp /var/tmp/mnt-macinstall/Penguin* install/mac/ + mkdir install/mac/.AppleDouble + cp /var/tmp/mnt-macinstall/.AppleDouble/Penguin* install/mac/.AppleDouble/ + # unmount, cleanup + umount /var/tmp/mnt-macinstall + rm /var/tmp/macinstall-temp.img + rmdir /var/tmp/mnt-macinstall +else + # We failed to mount it. Use the fallback tar.gz that we have + vecho HFS loopback mount failed on /var/tmp/macinstall-temp.img + vecho This is not fatal, but check that you have permissions to do this + vecho and that you have HFS support in your kernel... + vecho Extracting $BASEDIR/macinstall-cd.tar.gz instead. + tar xzf $BASEDIR/macinstall-cd.tar.gz +fi + +# +# can remove the .hqx stuff now I guess. +# +# make CD image using the command +# mkhybrid -map --netatalk -a -j -hfs -r -V