diff options
Diffstat (limited to 'en/preparing')
| -rw-r--r-- | en/preparing/backup.xml | 11 | ||||
| -rw-r--r-- | en/preparing/bios-setup/m68k.xml | 23 | ||||
| -rw-r--r-- | en/preparing/minimum-hardware-reqts.xml | 5 | ||||
| -rw-r--r-- | en/preparing/needed-info.xml | 14 | ||||
| -rw-r--r-- | en/preparing/non-debian-partitioning.xml | 6 | ||||
| -rw-r--r-- | en/preparing/nondeb-part/m68k.xml | 127 | ||||
| -rw-r--r-- | en/preparing/pre-install-bios-setup.xml | 17 |
7 files changed, 3 insertions, 200 deletions
diff --git a/en/preparing/backup.xml b/en/preparing/backup.xml index 4d7bde4ee..548646bb7 100644 --- a/en/preparing/backup.xml +++ b/en/preparing/backup.xml @@ -27,15 +27,4 @@ partitions. </para> -<para arch="m68k"> - -With the exception of the BVM and Motorola VMEbus computers, the only -supported installation method for m68k systems is booting from a local -disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these -machines you will need the original operating system in order to boot -Linux. In order to boot Linux on the BVM and Motorola VMEbus machines -you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs. - -</para> - </sect1> diff --git a/en/preparing/bios-setup/m68k.xml b/en/preparing/bios-setup/m68k.xml deleted file mode 100644 index 4c7d4b178..000000000 --- a/en/preparing/bios-setup/m68k.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="m68k" id="firmware-revs"> - <title>Firmware Revisions and Existing OS Setup</title> - -<para> - -&arch-title; machines are generally self-configuring and do not require -firmware configuration. However, you should make sure that you have -the appropriate ROM and system patches. On the Macintosh, MacOS -version >= 7.1 is recommended because version 7.0.1 contains a bug in -the video drivers preventing the boot loader from deactivating the -video interrupts, resulting in a boot hang. On the BVM VMEbus systems -you should make sure you are using BVMBug revision G or higher boot ROMs. -The BVMBug boot ROMs do not come as standard on the BVM systems but are -available from BVM on request free of charge. - -</para> - - </sect2> - diff --git a/en/preparing/minimum-hardware-reqts.xml b/en/preparing/minimum-hardware-reqts.xml index db88ed3f9..71ea4ed63 100644 --- a/en/preparing/minimum-hardware-reqts.xml +++ b/en/preparing/minimum-hardware-reqts.xml @@ -20,11 +20,6 @@ risk being frustrated if they ignore these suggestions. A Pentium 4, 1GHz system is the minimum recommended for a desktop system. -</para><para arch="m68k"> - -A 68030 or better processor is recommended for m68k -installs. You may get by with a little less drive space than shown. - </para><para arch="powerpc"> Any OldWorld or NewWorld PowerPC can serve well as a desktop system. diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml index 7589751f8..8dfffbd71 100644 --- a/en/preparing/needed-info.xml +++ b/en/preparing/needed-info.xml @@ -52,19 +52,13 @@ Often contains useful information on configuring or using your hardware. <!-- We need the arch dependence for the whole list to ensure proper xml as long as not architectures have a paragraph --> - <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel"> + <itemizedlist arch="x86;alpha;sparc;mips;mipsel"> <listitem arch="x86"><para> <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> </para></listitem> -<listitem arch="m68k"><para> - -<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> - -</para></listitem> - <listitem arch="alpha"><para> <ulink url="&url-alpha-faq;">Linux/Alpha FAQ</ulink> @@ -214,13 +208,9 @@ networking and e-mail. <entry>How many you have.</entry> </row> <row arch="not-s390"><entry>Their order on the system.</entry></row> -<!-- "not-m68k;not-s390" would really turn out to be everything... --> -<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc"> +<row arch="not-s390"> <entry>Whether IDE (also known as PATA), SATA or SCSI.</entry> </row> -<row arch="m68k"> - <entry>Whether IDE or SCSI (most m68k computers are SCSI).</entry> -</row> <row arch="not-s390"><entry>Available free space.</entry></row> <row arch="not-s390"><entry>Partitions.</entry></row> <row arch="not-s390"> diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml index ad82c4d17..3ebf133cc 100644 --- a/en/preparing/non-debian-partitioning.xml +++ b/en/preparing/non-debian-partitioning.xml @@ -32,10 +32,6 @@ If you already have an operating system on your system (VM, z/OS, OS/390, …) </phrase> -<phrase arch="m68k"> -(Amiga OS, Atari TOS, Mac OS, …) -</phrase> - and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some @@ -49,7 +45,6 @@ You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch="x86">, such as fdisk or PartitionMagic</phrase><phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase -arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes. @@ -191,7 +186,6 @@ Boot the Debian installer to continue installing Debian. &nondeb-part-alpha.xml; &nondeb-part-x86.xml; -&nondeb-part-m68k.xml; &nondeb-part-sparc.xml; &nondeb-part-powerpc.xml; diff --git a/en/preparing/nondeb-part/m68k.xml b/en/preparing/nondeb-part/m68k.xml deleted file mode 100644 index 37734ca55..000000000 --- a/en/preparing/nondeb-part/m68k.xml +++ /dev/null @@ -1,127 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="m68k"><title>Partitioning in AmigaOS</title> -<para> - -If you are running AmigaOS, you can use the <command>HDToolBox</command> -program to adjust your native partitions prior to installation. - -</para> - </sect2> - - <sect2 arch="m68k"><title>Partitioning in Atari TOS</title> -<para> - -Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for -data and <quote>SWP</quote> for swap partitions. If using the low memory -installation method, a small Minix partition is also needed (about 2 MB), -for which the partition ID is <quote>MNX</quote>. Failure to set the -appropriate partition IDs not only prevents the Debian installation process -from recognizing the partitions, but also results in TOS attempting to use -the Linux partitions, which confuses the hard disk driver and renders the -whole disk inaccessible. - -</para><para> - -There are a multitude of third party partitioning tools available (the -Atari <command>harddisk</command> utility doesn't permit changing the -partition ID); this manual cannot give detailed descriptions for all -of them. The following description covers <command>SCSITool</command> (from -Hard+Soft GmBH). - -<orderedlist> -<listitem><para> - -Start <command>SCSITool</command> and select the disk you want to partition -(<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>). - -</para></listitem> -<listitem><para> - -From the <guimenu>Partition</guimenu> menu, select either -<guimenuitem>New</guimenuitem> to add new partitions or change the -existing partition sizes, or <guimenuitem>Change</guimenuitem> to -change one specific partition. Unless you have already created -partitions with the right sizes and only want to change the partition -ID, <guimenuitem>New</guimenuitem> is probably the best choice. - -</para></listitem> -<listitem><para> - -For the <guimenuitem>New</guimenuitem> choice, select -<guilabel>existing</guilabel> in the dialog box -prompting the initial settings. The next window shows a list of -existing partitions which you can adjust using the scroll buttons, or -by clicking in the bar graphs. The first column in the partition list -is the partition type; just click on the text field to edit it. When -you are finished changing partition settings, save the changes by -leaving the window with the <guibutton>OK</guibutton> button. - -</para></listitem> -<listitem><para> - -For the <guimenuitem>Change</guimenuitem> option, select the partition -to change in the selection list, and select <guilabel>other -systems</guilabel> in the dialog box. The -next window lists detailed information about the location of this -partition, and lets you change the partition ID. Save changes by -leaving the window with the <guibutton>OK</guibutton> button. - -</para></listitem> -<listitem><para> - -Write down the Linux names for each of the partitions you created or -changed for use with Linux — see <xref linkend="device-names"/>. - -</para></listitem> -<listitem><para> - -Quit <command>SCSITool</command> using the -<guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> -menu. The computer will reboot to make sure the changed partition -table is used by TOS. If you changed any TOS/GEM partitions, they will -be invalidated and have to be reinitialized (we told you to back up -everything on the disk, didn't we?). - -</para></listitem> -</orderedlist> - -</para><para> - -There is a partitioning tool for Linux/m68k called -<command>atari-fdisk</command> in the installation system, but for now we -recommend you partition your disk using a TOS partition editor or some -disk tool. If your partition editor doesn't have an option to edit the -partition type, you can do this crucial step at a later stage (from -the booted temporary install RAMdisk). <command>SCSITool</command> is only -one of the partition editors we know of which supports selection of -arbitrary partition types. There may be others; select the tool that -suits your needs. - -</para> -</sect2> - - <sect2 arch="m68k"><title>Partitioning in MacOS</title> -<para> - -Partitioning tools for Macintosh tested include <command>pdisk</command>, -<command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), -<command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim -Endres, GPL). Full versions are required for <command>HDT</command> and -<command>SilverLining</command>. The Apple tool requires a patch in order -to recognize third-party disks (a description on how to patch <command>HD -SC Setup</command> using <command>ResEdit</command> can be found at -<ulink url="http://www.euronet.nl/users/ernstoud/patch.html"></ulink>). - -</para><para> - -For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create -empty space for the Linux partitions, and complete the partitioning under -Linux, or use the MacOS version of pdisk available for download from -<ulink url="http://homepage.mac.com/alk/downloads/pdisk.sit.hqx">Alsoft</ulink>. - -</para> -</sect2> - diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml index 2e80da6b1..3bf222467 100644 --- a/en/preparing/pre-install-bios-setup.xml +++ b/en/preparing/pre-install-bios-setup.xml @@ -16,28 +16,13 @@ hardware; it is most critically invoked during the bootstrap process </para> &bios-setup-i386.xml; -&bios-setup-m68k.xml; &bios-setup-powerpc.xml; &bios-setup-sparc.xml; &bios-setup-s390.xml; - <sect2 arch="m68k;x86;powerpc" id="hardware-issues"> + <sect2 arch="x86;powerpc" id="hardware-issues"> <title>Hardware Issues to Watch Out For</title> -<para arch="m68k"> - -Atari TT RAM boards are notorious for RAM problems under Linux; if you -encounter any strange problems, try running at least the kernel in -ST-RAM. Amiga users may need to exclude RAM using a booter memfile. - -<phrase condition="FIXME"><emphasis> - -FIXME: more description of this needed. - -</emphasis></phrase> - -</para> - <formalpara arch="x86"> <title>USB BIOS support and keyboards</title> <para> |