diff options
| author | Thomas Lange <lange@debian.org> | 2023-10-06 12:45:37 +0200 |
|---|---|---|
| committer | Thomas Lange <lange@debian.org> | 2023-10-06 12:45:37 +0200 |
| commit | 9f5b551837a8d4c6a8c9346cf4c44755b863a813 (patch) | |
| tree | 0856db540a5d047169c7b6513e04d38306bff237 /greek/ports | |
| parent | 794834c196b3285bb39846e22bfab051860258ab (diff) | |
remove a lot of files which are not translations but only copies of the english version
Diffstat (limited to 'greek/ports')
53 files changed, 0 insertions, 6895 deletions
diff --git a/greek/ports/alpha/Makefile b/greek/ports/alpha/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/alpha/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/alpha/index.wml b/greek/ports/alpha/index.wml deleted file mode 100644 index 7bd69a182bc..00000000000 --- a/greek/ports/alpha/index.wml +++ /dev/null @@ -1,28 +0,0 @@ -#use wml::debian::template title="Alpha Port" NOHEADER="true" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="8da95139c3595d47371ba8d288784086ae2ebacd" maintainer="galaxico" - -<h1>Debian GNU/Linux on Alpha Systems</h1> - -<p>The Alpha port is <a -href="https://lists.debian.org/debian-devel-announce/2009/10/msg00000.html">\ -no longer officially supported</a> in the Debian stable release. -The last release with official Alpha support was <a -href="https://www.debian.org/releases/lenny/releasenotes">Debian 5.0 -<q>lenny</q></a>. -For further information, please visit the <a href="port-status">port -status page</a>.</p> - - -<p>If you'd like to join us in this project, please peruse this page -and <a href="links#lists">join the mailing list</a>. -Things can be fast-moving and we all -realise that not everyone has the technical expertise to do it all, -but any help that people can or want to offer would be gladly -accepted.</p> - -<p><em>Cheers and happy Alpha-ing!<br /> -Helge Kreutzmann (former maintainer of these webpages),<br /> -Chris Chimelis (original maintainer of these webpages)</em></p> - -<p class="center"><img src="alpha-penguin.jpg" /></p> diff --git a/greek/ports/alpha/links.wml b/greek/ports/alpha/links.wml deleted file mode 100644 index 6330a7f17b7..00000000000 --- a/greek/ports/alpha/links.wml +++ /dev/null @@ -1,97 +0,0 @@ -#use wml::debian::template title="Alpha Port -- Links" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="b9cb4ebb36a3cc48be8b8b2ac3b06f113491d26f" maintainer="galaxico" - -<h1>Alpha Links</h1> - -<ul> - -<li><a href="http://www.alphalinux.org/">AlphaLinux.org</a><br /> -This page pretty much contains everything you may want or need to know -about running Linux on Alphas. Includes numerous links and an excellent -news section. This site is also the home of the official -<a href="http://www.alphalinux.org/docs/">FAQs and HOWTOs</a> related to Linux on Alphas.</li> - -<li><a href="http://www.alphalinux.org/docs/alpha-howto.html">\ -Intro to Alpha Systems</a><br /> -A rather old, but still informative document for the new or experienced user. -It describes -the differences between Alphas and other architectures as well as describing -the different systems. <b>If you have an old system and you really need to -know what your system is -despite what it says on the case, see -<a href="http://www.alphalinux.org/docs/alpha-howto.html#The%20Systems">this subsection</a>.</b></li> - -<li><a href="http://www.alphalinux.org/faq/FAQ.html">Linux/Alpha FAQ</a><br /> -A good source of information, the Linux/Alpha FAQ was originally put -together by Red Hat users, but has expanded to include more general info -and is still a great reference.</li> - -<li><a href="http://www.alphalinux.org/faq/SRM-HOWTO/index.html">SRM Firmware HOWTO</a><br /> -The official HOWTO for systems using SRM firmware. If you need to use -<a href="https://sourceforge.net/projects/aboot/">aboot</a> -to boot your Alpha, this is the page for you. -#This HOWTO is included in -#the latest version of the -#<a href="https://tracker.debian.org/pkg/aboot">Debian packet</a> -#as well. -</li> - -<li><a href="http://alphalinux.org/faq/MILO-HOWTO/t1.html">MILO HOWTO</a><br /> -The official HOWTO for MILO. Please note that -<a href="$(HOME)/devel/debian-installer/">debian-installer</a> lacks MILO support. -SRM is highly recommended, but if you cannot switch -and you are interested -in MILO support for post-Woody releases of Debian, then read -<a href="https://lists.debian.org/debian-alpha/2004/debian-alpha-200402/msg00003.html">this post to debian-alpha</a> and subscribe to -<a href="https://lists.debian.org/debian-boot/">debian-boot</a> to add MILO support. The latest known locations -are -<a href="http://www.suse.de/~stepan/">Stepan Rainauers page</a>, <a href="ftp://genie.ucd.ie/pub/alpha/milo/">Nikita Schmidt</a> -and the -work done by <a href="http://dev.gentoo.org/~taviso/milo/">Gentoo</a>.</li> - -<li><a href="http://www.alphalinux.org/faq/alphabios-howto.html">AlphaBIOS Firmware HOWTO</a><br /> -The official HOWTO for systems using AlphaBIOS firmware.</li> - -<li><a href="https://digital.com/about/dec/">Digital's Old Documentation Library</a> <!-- with a <a href="ftp://ftp.unix-ag.org/user/nils/Alpha-Docs/">Mirror by Nils Faerber</a> --> </li> - -<!-- <li><a href="http://www.alphanews.net/">alphanews.net</a><br /> -Some alpha related news are posted here, for several OS which run or used -to run on alphas.</li> --> - -<li><a href="http://www.helgefjell.de/browser.php">Browsers running on Linux Alpha</a><br /> -If you have troubles with your browser in an 64bit environment (should not be the case anymore, nowadays) or -if you just want to try out a new one, here you find a list of known-to work (and not to work) browsers.</li> - -<li><a href="http://alphacore.info/wiki/">AlphaCore WikiPage</a><br /> -This Wiki, currently mainly focused on AlphaCore (Fedora Core on Alpha) also -intends to collect general useful alpha related information.</li> -</ul> - -<p> -Thanks to Nils Faerber for allowing me to -include parts of his link collection here. -</p> - -<h1><a name="lists">Mailing Lists</a></h1> - -<ul> - -<li>The debian-alpha mailing list<br /> -Send an email with the subject 'subscribe' to -<email "debian-alpha-request@lists.debian.org" /> to subscribe. -<a href="https://lists.debian.org/debian-alpha/">Archives are -available</a>.</li> - -<li>Red Hat's Linux/Alpha List - -<p> -This list is oriented towards Red Hat Linux/Alpha users, but also has -valuable tips for general Linux-Alpha issues. To subscribe, -go to the <a href="https://www.redhat.com/mailman/listinfo/axp-list">List Info page</a>. -<a href="https://www.redhat.com/archives/axp-list/">Archives</a> of this list are also available. -An alternative (searchable) archive can be found at -<url "http://www.lib.uaa.alaska.edu/axp-list/" />. -</p></li> - -</ul> diff --git a/greek/ports/alpha/port-status.wml b/greek/ports/alpha/port-status.wml deleted file mode 100644 index f28a808274a..00000000000 --- a/greek/ports/alpha/port-status.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::template title="Alpha Port -- Status" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<h1>Debian GNU/Linux on Alpha – Status</h1> - -<p>The Alpha port, first officially released with Debian 2.1 -<q>slink</q>, is now archived: the last release with official support -for it was Debian 5.0 <q>lenny</q>. -</p> - -<h2>Debian GNU/Linux 5.0 <q>lenny</q></h2> - -<p>This is the last Debian release which includes the Alpha port.</p> - -<h2>Debian GNU/Linux 4.0 <q>etch</q></h2> - -<p>This release had support for Alpha, but only -those machines which can use SRM/aboot to boot can be installed with the - new installer.</p> - - -<h2>Debian GNU/Linux 3.1 <q>sarge</q></h2> - -<p>This release had full support for Alpha.</p> - -<h2>Debian GNU/Linux 3.0 <q>woody</q></h2> - -<p>This release had solid support for Alpha and is the last one to support - machines soly using milo (i.e. not SRM).</p> - -<h2>Debian GNU/Linux 2.2 <q>potato</q></h2> - -<p>Potato has much more software available and supports -more types of Alphas than slink did.</p> - -<h2>Debian GNU/Linux 2.1 <q>slink</q></h2> - -<p>The Alpha port was initially released with this release.</p> - -<h1>Hardware support</h1> - -<p>Quite a lot of hardware is now supported on Linux/Alpha. Unfortunately, - the exact combination of machine, hardware and kernel version is - non-trivial, so if you don't find your combo in - <a href="http://alphalinux.org/ALOHcl/">this list on alphalinux.org</a>, - and researching the - <a href="links#lists">list archives for Debian and Red Hat</a>-AXP-Lists - neither yields a result, then - <a href="https://lists.debian.org/debian-alpha/">subscribe</a> to the - Debian-Alpha list and ask. - Usually someone has tried already and can provide useful - information.</p> diff --git a/greek/ports/alpha/sys_types.wml b/greek/ports/alpha/sys_types.wml deleted file mode 100644 index 8e17082d2fb..00000000000 --- a/greek/ports/alpha/sys_types.wml +++ /dev/null @@ -1,1033 +0,0 @@ -#use wml::debian::template title="Alpha Port -- System Types" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="6f3adf6374f35194686f89dec2ba66b1ecf3bb5f" maintainer="galaxico" - -<p> -This list might not be complete, so if you see something that is not -on here or something that is incorrect please post it to -<a href="mailto:debian-alpha@lists.debian.org">debian-alpha</a> for verification -and inclusion. Please note that -<a href="https://www.gnu.org/software/hurd/gnumach.html">GNUMach</a> -currently only supports -<a href="https://www.gnu.org/software/hurd/faq.en.html#q2-3">IA 32</a> -based machines. As soon as porting to alpha is started, -this list will be updated to show which machines are actually supported.</p> - -#FIXME: Add links where appropriate, to e.g. BSDs info pages? -#FIXME: Also Niels has some machine specific links - -<br> -<br> -<table class="ridgetable"> -<tr> -<th>Model:</th> - -<th>Alias:</th> -<th>Supported by Linux</th> -<th>Supported by GNUMach</th> -</tr> - -<tr> -<td>21164 PICMG SBC (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part — single board computer)</td> - -<td>Takara/DMCC</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DMCC 21264 PICMG (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Eiger <i>(Tsunami family, but with 1 p-chip)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Alphabook1</td> - -<td>Alphabook1/Burns <i>(Alpha Notebook family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Alpha Demonstration Unit (prototype unit)</td> - -<td>ADU</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164</td> - -<td>PC164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-BX</td> - -<td>Ruffian <i>(Samsung produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-LX</td> - -<td>LX164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-SX</td> - -<td>SX164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-UX</td> - -<td>Ruffian <i>(Samsung produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC64</td> - -<td>Cabriolet <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPCI64</td> - -<td>Cabriolet <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 200 4/100...166</td> - -<td>Mustang <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 200 4/233</td> - -<td>Mustang+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 205 4/133...333</td> - -<td>LX3 <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 250 4/300</td> - -<td>M3+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 255 4/233...300</td> - -<td>LX3+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 300 4/266</td> - -<td>Melmac <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 400 4/166</td> - -<td>Chinet <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 400 4/233...300</td> - -<td>Avanti <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 500 5/266...300</td> - -<td>Maverick <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 500 5/333...500</td> - -<td>Bret <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600/266...300</td> - -<td>Alcor <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600/300...433</td> - -<td>XLT <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600A</td> - -<td>Alcor-Primo <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as800">AlphaServer 800</a> 5/333...500</td> - -<td>Corelle <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 4/200</td> - -<td>Mikasa <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 4/233...266</td> - -<td>Mikasa+ <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 5/300</td> - -<td>Pinnacle <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 5/333...500</td> - -<td>Primo <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 4/233...266</td> - -<td>Noritake <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 5/300</td> - -<td>Pinnacle <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 5/333...500</td> - -<td>Primo <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as1200">AlphaServer 1200</a> 5/xxx</td> - -<td>Tincup/DaVinci <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000 4/xxx</td> - -<td>Demi-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000 5/xxx</td> - -<td>Demi-Gamma-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100 4/xxx</td> - -<td>Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100 5/xxx</td> - -<td>Gamma-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000a 4/xxx</td> - -<td>Demi-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000a 5/xxx</td> - -<td>Demi-Gamma-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100a 4/xxx</td> - -<td>Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100a 5/xxx</td> - -<td>Gamma-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 4000 5/xxx</td> - -<td>Wrangler/Durango <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as4100">AlphaServer 4100</a> 5/xxx</td> - -<td>Dodge <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 8200</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 8400</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS10</td> - -<td>Slate <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS15</td> - -<td>Hyperbrick II <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20</td> - -<td>Catamaran/Goldrush <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20E</td> - -<td>Goldrack <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20L</td> - -<td>Shark <i>(Tsunami family)</i> (orig. CS20 by API)</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS25</td> - -<td>Granite <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES40</td> - -<td>Clipper <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES45</td> - -<td>Privateer <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES47</td> - -<td>Marvel 2P <i>(Marvel family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES80</td> - -<td>Marvel 4x2P <i>(Marvel family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS60</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS60E</td> - -<td>TurboLaser-Lite <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS80</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS1280</td> - -<td>Marvel 8P <i>(Marvel family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS140</td> - -# TL67 ? -<td>Turbo-Laser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS160</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS320</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>Alpha XL-233...266</td> - -<td>XL <i>(Alpha XL family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AXPpci33</td> - -<td>Noname <i>(Noname family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 2000/300</td> - -<td>Jensen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 2000/500</td> - -<td>Culzen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300</td> - -<td>Pelican</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300L</td> - -<td>Pelica</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300LX</td> - -<td>Pelica+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300X</td> - -<td>Pelican+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/400</td> - -<td>Sandpiper</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/500</td> - -<td>Flamingo</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/500X</td> - -<td>Hot Pink</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/600</td> - -<td>Sandpiper+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/700</td> - -<td>Sandpiper45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/800</td> - -<td>Flamingo II</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/900</td> - -<td>Flamingo45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 4000 model 610</td> - -<td>Fang</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 4000 model 710</td> - -<td>Cobra</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 610/180</td> - -<td>Laser/Ruby</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 610/200</td> - -<td>Laser/Ruby+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 710</td> - -<td>Laser/Ruby45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 10000</td> - -<td>Blazer/Ruby</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DECpc 150</td> - -<td>Jensen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3300</td> - -#Note to translators: Whitebox means that these machines where limited -#to run NT instead of Digital Unix (though they still could be made to -#run Linux :-)) ) -<td>Whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3300R</td> - -<td>Rackmount whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3305</td> - -<td>Whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3305R</td> - -<td>Rackmount whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 5300</td> - -<td>Whiteboxed <a href="#as1200">Alpha Server 1200</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 5305</td> - -<td>Whiteboxed <a href="#as1200">Alpha Server 1200</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7300</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7305</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7310</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>DP264</td> - -<td>DP264 <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB64+ (PCI Eval Board)</td> - -<td>EB64+ <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB66</td> - -<td>EB66 <i>(EB66 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB66+</td> - -<td>EB66+ <i>(EB66 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB164</td> - -<td>EB164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 433a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 433au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 500a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 500au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 600a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 600au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPL164-2</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPL164-4</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPX164-2</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPX164-4</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>SMARTengine 21264 PCI/ISA SBC</td> - -<td>Eiger <i>(Tsunami family, but with 1 p-chip)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UDB/Multia</td> - -<td>UDB/Multia <i>(Noname family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP1000</td> - -<td>Nautilus <i>(Nautilus family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP1100</td> - -<td>Galaxy-Train/Nautilus Jr. <i>(Nautilus family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP2000</td> - -<td>Swordfish <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>XP900</td> - -<td>Webbrick <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>XP1000</td> - -<td>Monet/Brisbane <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaVME 4/xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Cortex</td> -<td>No</td> -<td>No</td> -</tr> - -#Most likely never produced: -<tr> -<td>Unknown</td> - -<td>Cusco</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AXPvme xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Medulla</td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Was cancelled: -<tr> -<td>Unknown</td> - -<td>Tradewind</td> -<td>No</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>Warhol <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>Windjammer <i>(Tsunami family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>PC264 <i>(Tsunami family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Ever produced? -<tr> -<td>Unknown</td> - -<td>XXM</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaVME 5/xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Yukon <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -</table> - diff --git a/greek/ports/amd64/Makefile b/greek/ports/amd64/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/amd64/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/amd64/index.wml b/greek/ports/amd64/index.wml deleted file mode 100644 index 9800c83094d..00000000000 --- a/greek/ports/amd64/index.wml +++ /dev/null @@ -1,78 +0,0 @@ -#use wml::debian::template title="AMD64 Port" -#use wml::debian::translation-check translation="3d9c842c8a62070d2b0db0fed7812af4619c7b91" maintainer="galaxico" - - -#use wml::debian::toc - -<toc-display/> - -<toc-add-entry name="about">Debian on AMD64</toc-add-entry> -<p>This page is meant to assist users and Debian developers running -Debian GNU/Linux on the AMD64 architecture. Here, you will find -information about the current status of the port, which machines are -publicly accessible by developers, where to discuss development of -the port, where to get further information about Debian porters, and -pointers to more information.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>AMD64 has been an officially supported Debian architecture since the -release of Debian 4.0 (etch).</p> - -<p>The port consists of a kernel for all AMD 64bit CPUs with <em>AMD64</em> -extension and all Intel CPUs with <em>Intel 64</em> extension, and a common -64bit userspace.</p> - -<toc-add-entry name="features">A complete 64bit userland</toc-add-entry> -<p>The AMD64 port is thoroughly 64bit, allowing the user to benefit from all -advantages this architecture has compared to i386: -</p> -<ul> -<li>no memory segmentation into low and high memory</li> -<li>up to 128TiB virtual address space per process (instead of 2GiB)</li> -<li>64TiB physical memory support instead of 4GiB (or 64GiB with the PAE -extension)</li> -<li>16 general purpose registers in the CPU instead of 8</li> -<li>gcc defaults to SSE2 math instead of 387 FPU</li> -<li>gcc omits frame-pointers by default at -O2</li> -<li>compilation time optimization uses a common base for AMD64/Intel 64 instead of legacy i386 cruft</li> -<li>memory pages are not executable by default</li> -</ul> - -<p>Native execution of legacy 32bit binaries is supported by the kernel, and -core libraries needed are provided via Debian's <a -href="https://wiki.debian.org/Multiarch">Multiarch mechanism</a>.</p> - - -<toc-add-entry name="i386support">Minimalistic AMD64 runtime support for i386</toc-add-entry> -<p>The official i386 distribution actually includes minimalistic AMD64 -support, consisting of a 64bit kernel, a toolchain able to create 64bit binaries -and the amd64-libs package to run third-party amd64 binaries with native shared -libraries.</p> - - -<toc-add-entry name="ml">Mailing List</toc-add-entry> - -<p>Discussions and development for this port take place on the <a -href="https://lists.debian.org/debian-amd64/">debian-amd64</a> -list.</p> - - -<toc-add-entry name="publicmachines">Public machines</toc-add-entry> - -<p> -All Debian members can port packages using the Debian -<a href="https://db.debian.org/machines.cgi">porterbox machines</a>. -</p> - -<toc-add-entry name="links">Links</toc-add-entry> - -<ul> -#<li><a href="https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html">The debian-amd64 howto and FAQ</a></li> - -#<li><a href='https://anonscm.debian.org/viewvc/debian-amd64/'>CVS Repository</a></li> - -#<li><a href="https://alioth.debian.org/projects/debian-amd64/">the debian-amd64 Alioth project</a></li> - -<li><a href="https://wiki.debian.org/DebianAMD64">the debian-amd64 Wiki</a></li> -</ul> - diff --git a/greek/ports/arm/Makefile b/greek/ports/arm/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/arm/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/arm/index.wml b/greek/ports/arm/index.wml deleted file mode 100644 index bd370605c1b..00000000000 --- a/greek/ports/arm/index.wml +++ /dev/null @@ -1,127 +0,0 @@ -#use wml::debian::template title="ARM Ports" -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::toc -#use wml::debian::translation-check translation="51585e94038fbe80235329bd777a3ef8e5016e69" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian on arm</toc-add-entry> <p>On these -pages you'll find information about the ongoing effort of porting -Debian GNU/Linux to various versions of the <a -href="https://en.wikipedia.org/wiki/ARM_architecture">ARM -architecture</a> which are found in all types of system, from embedded -through to large server.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>Debian fully supports three ports to different flavours of -little-endian ARM hardware:</p> - -<ul> - -<li>The <a href="https://wiki.debian.org/ArmEabiPort">ARM EABI</a> -(armel) port targets a range of older 32-bit ARM devices, particularly -those used in NAS hardware and a variety of *plug computers.</li> - -<li>The newer <a href="https://wiki.debian.org/ArmHardFloatPort">ARM -hard-float</a> (armhf) port supports newer, more powerful 32-bit -devices using version 7 of the ARM architecture specification.</li> - -<li>The <a href="https://wiki.debian.org/Arm64Port">64-bit ARM</a> -(arm64) port supports the latest 64-bit ARM-powered devices.</li> - -</ul> - -<p>Other ports to ARM hardware exist / have existed in and around -Debian - see <a href="https://wiki.debian.org/ArmPorts">the wiki</a> -for more links and an overview.</p> - -<p>For a full and up-to-date list of the different hardware supported -by each of the ports, check the respective wiki pages. New ARM devices -are released every week, and it's easier for people to keep -information updated there.</p> - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> -<p>Multiple machines are made available to Debian developers for ARM -porting work: abel.debian.org (armel/armhf), asachi.debian.org -(armhf/arm64) and harris.debian.org (armhf). The machines have -development chroot environments which you can access with -<em>schroot</em>. Please see the <a -href="https://db.debian.org/machines.cgi">machine database</a> for -more information about these machines.</p> - -<toc-add-entry name="contacts">Contacts</toc-add-entry> -<h3>Mailing lists</h3> - -<p>The Debian ARM port mailing list is located at -<email "debian-arm@lists.debian.org">. -If you wish to sign up, send a message with the word <q>subscribe</q> as the -subject to <email "debian-arm-request@lists.debian.org">. The list is -archived at the <a href="https://lists.debian.org/debian-arm/">debian-arm -list archives</a>.</p> - -<p> -It's also a good idea to sign up with the -<a href="http://www.arm.linux.org.uk/mailinglists/">\ -linux-arm</a> mailing list.</p> - -<h3>IRC</h3> - -<p>You can find us on IRC on <em>irc.debian.org</em> on the channel -<em>#debian-arm</em>.</p> - -<toc-add-entry name="people">People</toc-add-entry> -<p> -This is a list of significant people who are currently involved in the Debian -ARM ports. -</p> - -<ul> - -<li>Ian Campbell <email "ijc@debian.org"> -<br /> -debian-installer, kernel -</li> - -<li>Aurelien Jarno <email "aurel32@debian.org"> -<br /> -ARM buildd maintainer and general porter -</li> - -<li>Steve McIntyre <email "steve@einval.com"> -<br /> -Local admin for ARM machines, documentation and general porter -</li> - -<li>Martin Michlmayr <email "tbm@cyrius.com"> -<br /> -Documentation, debian-installer -</li> - -<li>Riku Voipio <email "riku.voipio@iki.fi"> -<br /> -armel porter and buildd maintainer -</li> - -<li>Wookey <email "wookey@wookware.org"> -<br /> -Documentation -</li> - -</ul> - -<toc-add-entry name="dedication">Dedication</toc-add-entry> - -<p>Chris Rutter -who was the Project Coordinator and Autobuilder Coordinator for Debian ARM -port got killed in a car accident. We dedicate the ARM port's -release in the Debian GNU/Linux <q>woody</q> distribution to his -memory.</p> - -<toc-add-entry name="thanks">Thanks</toc-add-entry> - -<p> -These people were helpful in making the ARM port viable for Debian: - -Jim Studt, Jim Pick, Scott Bambrough, Peter Naulls, Tor Slettnes, -Phil Blundell, Vincent Sanders -</p> diff --git a/greek/ports/hppa/Makefile b/greek/ports/hppa/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/hppa/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/hppa/index.wml b/greek/ports/hppa/index.wml deleted file mode 100644 index 66d3e331b86..00000000000 --- a/greek/ports/hppa/index.wml +++ /dev/null @@ -1,48 +0,0 @@ -#use wml::debian::template title="PA-RISC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="1f99c642fe56e0113f0730c6247f562992a7e25f" maintainer="galaxico" - -<h1>Debian for PA-RISC</h1> - -<h2>Status</h2> -HPPA became an officially supported Debian architecture in release -3.0 (woody), and was dropped as of stable release 6.0 (squeeze). -Additional information about the port may be found at -<a href="https://parisc.wiki.kernel.org/">https://parisc.wiki.kernel.org/</a>. - -<p> -If you have questions, or would like to help, start by subscribing to the -debian-hppa mailing list, documented below! - -<h2>Contacts</h2> - -The principal instigator of this port was Bdale Garbee, but he no longer -actively contributes to it. -The best way to ask questions now is via the mailing list. - -<h2>Mailing List</h2> - -<p> -To subscribe to the mailing list for this port, send a message with the -word "subscribe" as the subject to -<a -href="mailto:debian-hppa-request@lists.debian.org">\ -debian-hppa-request@lists.debian.org</a> to sign up, or use the -<a href="$(HOME)/MailingLists/subscribe">mailing list subscription</a> page. -<p> -The list is archived at the -<a href="https://lists.debian.org/debian-hppa/">list archives</a>. - -<h2>Links</h2> - -<ul> - -<li><a href="https://parisc.wiki.kernel.org/">The PA-RISC Linux Project Web</a> -<li><a href="https://www.pateam.org/doc.html">ESIEE's HOWTO Documents</a> -<li><a href="http://docs.hp.com/hpux/hw/">HP Systems Documentation</a> -<li><a href="http://h21007.www2.hp.com/dev/">\ - HP PA-RISC Architecture Reference Documents, Etc</a> -<li><a href="https://www.openpa.net/">The OpenPA Project</a> - -</ul> - diff --git a/greek/ports/hppa/news.wml b/greek/ports/hppa/news.wml deleted file mode 100644 index 8abb4906f33..00000000000 --- a/greek/ports/hppa/news.wml +++ /dev/null @@ -1,77 +0,0 @@ -#use wml::debian::template title="PA-RISC Port -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="1f99c642fe56e0113f0730c6247f562992a7e25f" maintainer="galaxico" - -<h1>News about Debian for PA-RISC</h1> - -<h3><:=spokendate ("2001-08-06"):></h3> - -<p><strong>Debian accepts hppa for release with Debian 3.0 (woody)!</strong> - -<p> -It is with great pleasure that we announce the acceptance of hppa as an -architecture for the upcoming Debian 3.0 stable release, codename woody. -Installation tools for hppa are now in the woody tree, and packages now in -unstable are beginning to be promoted to the testing/woody tree. - -<h3><:=spokendate ("2001-07-17"):></h3> - -<p><strong>Official Request to Release with Debian 3.0 (woody)</strong> - -<p> -Nearly 70% of all Debian packages are built and up to date in the archive, -an automated build system is running smoothly, installation tools are -available in the archive, and the number of running systems is growing -steadily. - -<h3><:=spokendate ("2001-05-31"):></h3> - -<p><strong>HP Releases 0.9 CD Images!</strong> - -<p> -HP has made a snapshot of the "sid" unstable Debian tree for hppa available -as a set of CDROM images. See <a href="http://www.parisc-linux.org/release-0.9/"> -the release page </a> for more information. This release makes it plausible -that the hppa architecture might be ready to release with woody, though there -is much work left to do between now and then! - -<h3><:=spokendate ("2000-10-16"):></h3> - -<p><strong>Binary Trees Created</strong> - -<p> -Binary trees for the hppa architecture were added to the 'sid' distribution -on Debian's master site today. Bdale is running an auto-builder, and packages -should start showing up on Debian mirror sites shortly. Installation info and -some critical packages are still available only through the -<a href="https://parisc.wiki.kernel.org/">PA-RISC Linux</a> -web site, however. - -<h3><:=spokendate ("2000-08-01"):></h3> - -<p><strong>Name Change</strong> - -<p> -At OLS, the issue of using 'parisc' vs 'hppa' for the Debian architecture -string was finally decided, in favor of 'hppa'. This ports page is being -moved to reflect the change, and a request is in the works to rename the -debian-parisc mailing list to debian-hppa. - -<h3><:=spokendate ("2000-03-31"):></h3> - -<p><strong>HP Contributes Build Machine</strong> - -<p> -HP has made a -J5000 -available to Debian on long-term loan to aid in compiling packages when we get -to that point. -<p> -Also, the mailing list debian-parisc has been activated. - -<h3><:=spokendate ("2000-03-04"):></h3> - -<p><strong>Debian PA-RISC Port Officially Starts</strong> - -<p> -A new mailing list, debian-parisc, has been requested but is not active yet. diff --git a/greek/ports/hppa/systems.wml b/greek/ports/hppa/systems.wml deleted file mode 100644 index 1cb12caf10f..00000000000 --- a/greek/ports/hppa/systems.wml +++ /dev/null @@ -1,12 +0,0 @@ -#use wml::debian::template title="PA-RISC Port -- Systems" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="2fc9dfddd8c0dbff8db3c43eebd31df1cdfab7d1" maintainer="galaxico" - -<h2>Systems Overview</h2> - -<h3>HP9000 715/50 (Scorpio)</h3> - -<p>Linux will work quite well on that machine, but you may have to run -with a serial console, as Linux doesn't support graphics on all -hardware yet. Also, Linux doesn't support EISA cards on any PA-RISC -boxes yet, so if you have any of those they won't work. diff --git a/greek/ports/hurd/hurd-cd.wml b/greek/ports/hurd/hurd-cd.wml deleted file mode 100644 index 1ebb53fe81b..00000000000 --- a/greek/ports/hurd/hurd-cd.wml +++ /dev/null @@ -1,100 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Hurd-CDs" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="f1e7499d83a6ebf7321674af80d60a51cf5db6fd" maintainer="galaxico" - -<define-tag cdserie>L1</define-tag> -<define-tag cdbasetarball>gnu-2009-10-18.tar.gz</define-tag> -<define-tag cdbasename>debian-<cdserie>-hurd-i386</define-tag> - -<h1>Debian GNU/Hurd</h1> - -<p>While many people call the GNU system GNU/Hurd this is not strictly true. -The kernel is GNU Mach not the Hurd. The Hurd is a series of servers which -run on top of the microkernel, GNU Mach. Both the Hurd and GNU Mach are -part of the GNU project while the Linux kernel is an independent project.</p> - -<p>The easiest (and well-tested) method of trying Debian GNU/Hurd is to use a -virtual machine via KVM. Some pre-installed images are available on -<url "https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/README.txt">, but one can also -use the Debian Installer to install in KVM or a native machine (but hardware -support vary, so it is more recommended to give a try with KVM). -</p> - -<h2>Using the Debian Installer installation CD-ROM</h2> - -<p>A hurd-i386 port of the standard Debian Installer can be -downloaded from <url "https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/"> . -Make sure to read the README file available along the iso images. -It works like the usual Linux port of the Debian Installer, i.e. automatically, except a -few details:</p> - -<ul> - -<li>Make sure to enable swap space, else Mach will have troubles if you use all -your memory.</li> - -<li>Do not mount a separate partition on <code>/usr</code>, else the boot will -fail.</li> - -<li> -Read <a href="hurd-install">the notes about manual installation</a> which -document some of the final configuration steps. -</li> - -</ul> - -<p>Instructions for burning CDs from the images can be found in the -<a href="$(HOME)/CD/faq/">Debian CD FAQ</a>.</p> - -<h2>Newer snapshots</h2> - -<p>Some newer snapshots are available on <url "https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/"></p> - -<p>Daily (untested!) snapshots are available on <url "https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/">. Since they are based on the unstable distribution, quite often they cannot actually install a system, due to ongoing transitions in unstable etc. So really rather use the snapshot linked above.</p> - -<h2>Making a GRUB boot-disk</h2> - -<p> -If you are installing the Hurd alone on your system, you can let the installer -install GRUB itself. If you are installing the Hurd along an existing system, -you will most probably want to be able to choose between both. If your existing -system is Linux, you can probably simply run update-grub and it will detect your -newly-installed Hurd system. Otherwise, or if you do not manage to boot the Hurd -that way, you can use a GRUB boot-disk.</p> - -<p> -Install the package grub-disk or grub-rescue-pc, they contain a GRUB floppy -image. You can use "dd" if you are working in GNU/Linux or rawrite if you are -working in MS. -</p> - -<p> -Make certain that you understand Linux, GRUB and Hurd methods -of naming drives and partitions. You will be using all three and the -relationship between them can be confusing. -</p> - -<p>Hurd uses different partition names to Linux, so be careful. IDE -hard disks are numbered in order, beginning from hd0 for the primary -master and its slave hd1, followed by the secondary master hd2 and -its slave hd3. SCSI drives are also numbered in absolute order. They will -always be sd0, sd1, and so on regardless of whether the two drives are -SCSI id 4 and 5 or whatever. Experience has shown that CD-ROM drives -can be tricky. More about this later.</p> - -<p>Linux-style partitions are always called sn when using the Hurd, -where n is the partition number, so the first partition on the first -IDE drive will be hd0s1, the third partition on the second SCSI drive -will be sd1s3, and so on.</p> - -<p>GRUB1 has yet another partition naming system. It calls partitions (hdN,n), -but this time the disk number and partition number are both zero indexed, and -the disks run in order, all the IDE disks first, and the SCSI ones second. This -time, the first partition on the first IDE drive will be (hd0,0). GRUB2 does -the same, but the partition number is one indexed, so in that case it will be -(hd0,1). To really cause a confusion, (hd1,2) could refer to the first SCSI -drive if you only have one IDE drive, or it could refer to the second IDE drive. -So it is important that you have worked out the various names of your partitions -before you start.</p> - -<p>Enjoy the Hurd.</p> diff --git a/greek/ports/hurd/hurd-devel-debian.wml b/greek/ports/hurd/hurd-devel-debian.wml deleted file mode 100644 index 932f99212db..00000000000 --- a/greek/ports/hurd/hurd-devel-debian.wml +++ /dev/null @@ -1,165 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Development" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="dd86de49807cb957ea73388b4bf2565163644a0c" maintainer="galaxico" - -<h1> -Debian GNU/Hurd</h1> -<h2> -Development of the Distribution</h2> - -<h3> -Porting Debian Packages</h3> -<p> -If you want to help the Debian GNU/Hurd port, you should make yourself -familiar with the Debian packaging system. Once you have done this by -reading the available documentation and visiting the <a -href="$(HOME)/devel/">Developer's Corner</a> you should know how to -extract Debian source packages and build a Debian package. Here is a -crash course for the very lazy people:</p> - -<h3> -Obtaining Source and Building Packages</h3> - -<p> -Obtaining Source code can be done by simply running <code>apt-get source -package</code>, which will also extract the source. -</p> - -<p> -Extracting a Debian source package requires the file -<code>package_version.dsc</code> and the files listed in it. You build the -Debian build directory with the command -<code>dpkg-source -x package_version.dsc</code> -</p> - -<p> -Building a package is done in the now existing Debian build directory -<code>package-version</code> with the command -<code>dpkg-buildpackage -B "-mMyName <MyEmail>"</code>. -Instead <code>-B</code> you can use -<code>-b</code> if you also want to build the architecture independent -parts of the package. You can add -<code>-uc</code> to avoid signing the package with your pgp key.</p> - -<p> -Building may needed additional installed packages. The simplest way it to run -<code>apt-get build-dep package</code> which will install all required packages. -</p> - -<p> -Using pbuilder can be convenient. It can be built with -<code>sudo pbuilder create --mirror http://deb.debian.org/debian-ports/ --debootstrapopts --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg --debootstrapopts --extra-suites=unreleased --extrapackages debian-ports-archive-keyring</code> -and then one can use <code>pdebuild -- --binary-arch</code> which will handle downloading build dependencies, etc, and put the result in <code>/var/cache/pbuilder/result</code> -</p> - -<h3> -Pick One</h3> -<p> -Which package needs to be worked on? Well, every package that is not -yet ported, but needs to be ported. This changes constantly, so -it's preferred to concentrate first on packages with a lot of reverse -dependencies, which can be seen in the package dependency graph -<url "https://people.debian.org/~sthibault/graph-radial.pdf"> updated every day, -or on the most-wanted list -<url "https://people.debian.org/~sthibault/graph-total-top.txt"> (this is -long-term wanted, the short-term wanted is -<url "https://people.debian.org/~sthibault/graph-top.txt">). -It is also usually a good idea to pick from the out of date lists -<url "https://people.debian.org/~sthibault/out_of_date2.txt"> and -<url "https://people.debian.org/~sthibault/out_of_date.txt">, as these used to be -working, and are now broken probably only for just a couple of reasons. -You can also just pick one of the missing packages at random, or watch out for -autobuilding logs on the debian-hurd-build-logs mailing list, or use the -wanna-build list from -<url "https://people.debian.org/~sthibault/failed_packages.txt"> . Some build issues are easier to fix than the others. Typically, "undefined reference to foo", where foo is something like pthread_create, dlopen, cos, ... (which are obviously available on hurd-i386), which just shows that the configure step of the package forgot to include -lpthread, -ldl, -lm, etc. on the Hurd too. Note however that ALSA MIDI functions are not available. -</p> -<p> -Also, check whether work has already been done on -<url "https://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse">, -<url "https://alioth.debian.org/tracker/?atid=411594&group_id=30628&func=browse">, -and the BTS (<url "https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-hurd@lists.debian.org;tag=hurd">), and <url "https://wiki.debian.org/Debian_GNU/Hurd">, -and the live state of packages on buildd.debian.org, e.g. -<url "https://buildd.debian.org/util-linux">. -</p> - -<h4> -Packages That Won't Be Ported</h4> -<p> -Some of these packages, or parts of them, might be portable later, but -currently they are considered to be unportable at least. They are normally -marked as NotForUs in the buildd database. -</p> - -<ul> -<li> -<code>base/makedev</code>, because the Hurd comes with its own version -of this script. The Debian source package only contains a Linux -specific version.</li> -<li> -<code>base/modconf</code> and <code>base/modutils</code>, because -modules are a concept specific to Linux.</li> -<li> -<code>base/netbase</code>, because the remaining stuff that is there -is highly specific to the Linux kernel. The Hurd uses -<code>inetutils</code> instead.</li> -<li> -<code>base/pcmcia-cs</code>, because this package is Linux specific.</li> -<li> -<code>base/setserial</code>, because it is specific to the Linux -kernel. However, with the port of Linux char drivers to GNU Mach, we -might be able to use it.</li> -</ul> - -<h3> <a name="porting_issues"> -General Porting Issues</a></h3> -<p> -<a href=https://www.gnu.org/software/hurd/hurd/porting/guidelines.html>A list of -common issues</a> is available on the upstream website. The following common -issues are specific to Debian.</p> -<p>Before attempting to fix something, check whether the kfreebsd* port maybe -has some fix already, which just needs to be extended to hurd-i386.</p> - -<ul> -<li> -<code>Broken libc6 dependency</code> -<p> -Some packages use an erroneous dependency on <code>libc6-dev</code>. This -is incorrect because <code>libc6</code> is specific to some architectures -of GNU/Linux. The corresponding package for GNU is <code>libc0.3-dev</code> -but other OSes will have different ones. You can locate the problem in the -<code>debian/control</code> file of the source tree. Typical solutions include -detecting the OS using <code>dpkg-architecture</code> and hardcoding the -soname, or better, use a logical OR. eg: -<code>libc6-dev | libc6.1-dev | libc0.3-dev | libc0.1-dev | libc-dev</code>. -The <code>libc-dev</code> is a -virtual package that works for any soname but you have to put it only as the -last option.</p></li> -<li> -<code>undefined reference to snd_*, SND_* undeclared</code> -<p> -Some packages use ALSA even on non-Linux architectures. The oss-libsalsa package -provides some emulation over OSS, but it is limited to 1.0.5, and some features -are not provided, such as all sequencer operations. -</p> -<p> -If the package permits it, alsa support should be disabled on the -<code>!linux-any</code> archs (e.g. through a <code>configure</code> -option), and a <code>[linux-any]</code> qualifier added to the -alsa <code>Build-Depends</code>, and the converse added to -<code>Build-Conflicts</code>, such as -<code>Build-Conflicts: libasound2-dev [!linux-any]</code>. -</p> -</li> -<li> -<code>dh_install: Cannot find (any matches for) "foo" (tried in ., debian/tmp)</code> -<p> -That typically happens when upstream didn't install something because it didn't -recognize the OS. Sometimes it's just dumb (e.g. it doesn't know that building -a shared library on GNU/Hurd is exactly like on GNU/Linux) and that needs -fixing. Sometimes it actually makes sense (e.g. not installing systemd service -files). In that case, one can use dh-exec: build depend on <tt>dh-exec</tt>, -<tt>chmod +x</tt> the <tt>.install</tt> file, and prepend the problematic lines -with e.g. <tt>[linux-any]</tt> or <tt>[!hurd-any]</tt>. -</p> -</li> -</ul> diff --git a/greek/ports/hurd/hurd-doc-server.wml b/greek/ports/hurd/hurd-doc-server.wml deleted file mode 100644 index 4dd790aef9d..00000000000 --- a/greek/ports/hurd/hurd-doc-server.wml +++ /dev/null @@ -1,967 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Τεκμηρίωση" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="f4f6753d2f1e1d5bb9708ce8b3f7dde77940b870" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> - -<p> Ο Dirk Ritter μου έστειλε το παρακάτω κείμενο, που περιέχει την έξοδο της -επιλογής <tt>--help</tt> για κάθε πρόγραμμα εξυπηρετητή Hurd. Αυτό μπορεί να -είναι ένα καλό σημείο αφετηρίας για περαιτέρω τεκμηρίωση των προγραμμάτων των -εξυπηρετητών, ιδιαίτερα εκείνων που είναι χρήσιμοι σε έναν χρήστη όπως οι -ext2fs, ufs, isofs, ftpfs, crash, κλπ. -</p> - -<p> -Since then, I updated the text using mail excerpts from the Hurd mailing -lists. Thanks to Martin von Loewis. - -<h2>Προκαταρκτική Περιγραφή της Διεπαφής χρήστη του GNU/Hurd</h2> - -<p> -Currently there is next to nothing but this might be better than nothing at -all, so please send complaints, corrections and additions to -<a href="mailto:dirk@gnumatic.s.bawue.de">Dirk Ritter</a>, -<dirk@gnumatic.s.bawue.de>. Please note that my programming skills are -<em>very</em> limited, so you should not expect me to actually understand -anything related to Operating Systems design and implementations.</p> - -<table border="2" - summary="Index of HURD servers and translators:"> - -<caption><em>Index of HURD servers and translators:</em></caption> - -<tr> - <th><a href="#auth" name="TOC_auth" type="text/html"> - The authentication server</a></th> - <th>"<code>auth</code>"</th> -</tr> -<tr> - <th><a href="#crash" name="TOC_crash" type="text/html"> - The crash server</a></th> - <th>"<code>crash</code>"</th> -</tr> -<tr> - <th><a href="#exec" name="TOC_exec" type="text/html"> - The exec server</a></th> - <th>"<code>exec</code>"</th> -</tr> -<tr> - <th><a href="#ext2fs" name="TOC_ext2fs" type="text/html"> - The ext2fs server</a></th> - <th>"<code>ext2fs</code>"</th> -</tr> -<tr> - <th><a href="#fifo" name="TOC_fifo" type="text/html"> - The fifo translator</a></th> - <th>"<code>fifo</code>"</th> -</tr> -<tr> - <th><a href="#firmlink" name="TOC_firmlink" type="text/html"> - The firmlink translator</a></th> - <th>"<code>firmlink</code>"</th> -</tr> -<tr> - <th><a href="#ftpfs" name="TOC_ftpfs" type="text/html"> - The ftp filesystem translator</a></th> - <th>"<code>ftpfs</code>"</th> -</tr> -<tr> - <th><a href="#fwd" name="TOC_fwd" type="text/html"> - The fwd server</a></th> - <th>"<code>fwd</code>"</th> -</tr> -<tr> - <th><a href="#hostmux" name="TOC_hostmux" type="text/html"> - The hostmux server</a></th> - <th>"<code>hostmux</code>"</th> -</tr> -<tr> - <th><a href="#ifsock" name="TOC_ifsock" type="text/html"> - The ifsock server</a></th> - <th>"<code>ifsock</code>"</th> -</tr> -<tr> - <th><a href="#init" name="TOC_init" type="text/html"> - The init server</a></th> - <th>"<code>init</code>"</th> -</tr> -<tr> - <th><a href="#isofs" name="TOC_isofs" type="text/html"> - The iso filesystem server</a></th> - <th>"<code>isofs</code>"</th> -</tr> -<tr> - <th><a href="#magic" name="TOC_magic" type="text/html"> - The magic server</a></th> - <th>"<code>magic</code>"</th> -</tr> -<tr> - <th><a href="#new-fifo" name="TOC_new-fifo" type="text/html"> - The new-fifo server</a></th> - <th>"<code>new-fifo</code>"</th> -</tr> -<tr> - <th><a href="#nfs" name="TOC_nfs" type="text/html"> - The nfs server</a></th> - <th>"<code>nfs</code>"</th> -</tr> -<tr> - <th><a href="#null" name="TOC_null" type="text/html"> - The null server</a></th> - <th>"<code>null</code>"</th> -</tr> -<tr> - <th><a href="#pfinet" name="TOC_pfinet" type="text/html"> - The pfinet server</a></th> - <th>"<code>pfinet</code>"</th> -</tr> -<tr> - <th><a href="#pflocal" name="TOC_pflocal" type="text/html"> - The pflocal server</a></th> - <th>"<code>pflocal</code>"</th> -</tr> -<tr> - <th><a href="#proc" name="TOC_proc" type="text/html"> - The process server</a></th> - <th>"<code>proc</code>"</th> -</tr> -<tr> - <th><a href="#storeio" name="TOC_storeio" type="text/html"> - The storage translator</a></th> - <th>"<code>storeio</code>"</th> -</tr> -<tr> - <th><a href="#symlink" name="TOC_symlink" type="text/html"> - The symbolic link translator</a></th> - <th>"<code>symlink</code>"</th> -</tr> -<tr> - <th><a href="#term" name="TOC_term" type="text/html"> - The terminal server</a></th> - <th>"<code>term</code>"</th> -</tr> -<tr> - <th><a href="#ufs" name="TOC_ufs" type="text/html"> - The ufs server</a></th> - <th>"<code>ufs</code>"</th> -</tr> -<tr> - <th><a href="#usermux" name="TOC_usermux" type="text/html"> - The usermux server</a></th> - <th>"<code>usermux</code>"</th> -</tr> - -# Uncomment and fill the blanks... -#<tr> -# <th><a href="#" name="TOC_" type="text/html"> -# The server</a></th> -# <th>"<code></code>"</th> -#<tr> -</table> - - -<h2 class="center"><a href="#TOC_auth" name="auth" type="text/html"> -The authentication server - "<code>auth</code>"</a></h2> - -<p> -Passes credentials when two mutually untrusting servers communicate. -In a sense, each auth server establishes a domain of trust. (Martin von -Loewis, 10 Oct 1996)</p> - -<P> -One of its interesting features is that it makes it possible for -processes to impersonate several identities at the same time, and -also to dynamically acquire or relinquish identities.</p> - -<p> -Running "<code>/hurd/auth --help</code>" gives: -<br> -<pre> -Usage: auth [OPTION...] - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - -<h2 class="center"><a href="#TOC_crash" name="crash" type="text/html"> -The crash server - "<code>crash</code>"</a></h2> - -<p> -The crash server gets active whenever a task gets a fatal error signal, -for example because it violates memory boundaries (segmentation fault). -The crash server has three modes of operation: suspending the process group -(pgrp) of the offending task, killing it or dumping a core file. -The latter is not yet implemented. Think of the crash -server of an airbag.</p> -<p> -You can set the mode of operation with <code>settrans</code> of course, but -also with <code>fsysopts</code> at runtime. This is true for the system wide -default and usually requires root privileges. A user can select a different -default with the <code>CRASHSERVER</code> environment variable. You set this -variable to an inode that has the <code>crash</code> server attached to it. -On a default Debian GNU/Linux system, there three default operations have -corresponding translators in <code>/servers/crash-*</code>.</p> - -<pre> - - These options specify the disposition of a crashing process: - -s, --suspend Suspend the process - -k, --kill Kill the process - -c, --core-file Dump a core file - --dump-core -</pre> - - -<h2 class="center"><a href="#TOC_exec" name="exec" type="text/html"> -The execute server - "<code>exec</code>"</a></h2> - -<p> -Exec manages the creation of a new process image from the image file.</p> - -<P> -Actually this server has support to create a runnable process image -out of any image file recognized by the BFD library (this includes -a.out, ELF, and many others). Gzipped executable are also -recognized (useful for boot floppies).</p> - -<p> -Running "<code>/hurd/exec --help</code>" gives: -<br> -<pre> -Usage: exec [OPTION...] -Hurd standard exec server - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ext2fs" name="ext2fs" type="text/html"> -The ext2 filesystem server - "<code>ext2fs</code>"</a></h2> - -<p> -This server manages ext2-type filesystems. It does the same as -<code>ext2fs.static</code>, only that <code>ext2fs.static</code> -is a statically linked executable. - -<p> -Running "<code>/hurd/ext2fs --help</code>" gives: -<br> -<pre> -Usage: ext2fs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - -C, --directory=DIRECTORY - --device-master-port=PORT - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_fifo" name="fifo" type="text/html"> -The fifo server - "<code>fifo</code>"</a></h2> - -<p> -The fifo translator implements named pipes. - -<p> -Running "<code>/hurd/fifo --help</code>" gives: -<br> -<pre> -Usage: fifo [OPTION...] -Translator for fifos - - -d, --dgram Reads reflect write record boundaries - -m, --multiple-readers Allow multiple simultaneous readers - -n, --noblock Don't block on open - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_firmlink" name="firmlink" type="text/html"> -The firmlink server - "<code>firmlink</code>"</a></h2> - -<p> -A translator for firmlinks. - -<p> -Running "<code>/hurd/firmlink --help</code>" gives: -<br> -<pre> -Usage: firmlink [OPTION...] TARGET -A translator for firmlinks - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -A firmlink is sort of half-way between a symbolic link and a hard link; - -Like a symbolic link, it is `by name', and contains no actual reference to the -target. However, the lookup returns a node which will redirect parent lookups -so that attempts to find the cwd that go through the link will reflect the link -name, not the target name. The target referenced by the firmlink is looked up -in the namespace of the translator, not the client. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ftpfs" name="ftpfs" type="text/html"> -The ftp filesystem server - "<code>ftpfs</code>"</a></h2> - -<p> -A server for ftp filesystems. - -<p> -Running "<code>/hurd/ftpfs --help</code>" gives: -<br> -<pre> -Usage: ftpfs [OPTION...] REMOTE_FS [SERVER] -Hurd ftp filesystem translator - - -D, --debug[=FILE] Print debug output to FILE - - Parameters: - --bulk-stat-period=SECS Period for detecting bulk stats (default 10) - --bulk-stat-threshold=SECS Number of stats within the bulk-stat-period - that trigger a bulk stat (default 5) - --name-timeout=SECS Time directory names are cached (default 300) - --node-cache-size=ENTRIES Number of recently used filesystem nodes that - are cached (default 50) - --stat-timeout=SECS Time stat information is cached (default 120) - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If SERVER is not specified, an attempt is made to extract it from REMOTE_FS, -using `SERVER:FS' notation. SERVER can be a hostname, in which case anonymous -ftp is used, or may include a user and password like `USER:PASSWORD@HOST' (the -`:PASSWORD' part is optional). - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_fwd" name="fwd" type="text/html"> -The fwd server - "<code>fwd</code>"</a></h2> - -<p> -When accessed, the fwd translator forwards requests to another server. -It is used in the fifo and symlink server. The idea is so that you don't get -a jillion servers for such trivial things; fwd is used to coordinate -having one server handle several different nodes conveniently. - -<p> -Running "<code>/hurd/fwd --help</code>" gives: -<br> -<pre> -Usage: /hurd/fwd SERVER [TRANS_NAME [TRANS_ARG...]] -</pre> - - - -<h2 class="center"><a href="#TOC_hostmux" name="hostmux" type="text/html"> -The hostmux server - "<code>hostmux</code>"</a></h2> - -<p> -I have no idea what this server is good for. - -<small> -(A server for host lookups?) -</small> - -<p> -Running "<code>/hurd/hostmux --help</code>" gives: -<br> -<pre> -Usage: hostmux [OPTION...] TRANSLATOR [ARG...] -A translator for invoking host-specific translators - - -H, --host-pattern=PAT The string to replace in the translator - specification with the hostname; if empty, or - doesn't occur, the hostname is appended as - additional argument instead (default `${host}') - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -This translator appears like a directory in which hostnames can be looked up, -and will start TRANSLATOR to service each resulting node. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ifsock" name="ifsock" type="text/html"> -The ifsock server - "<code>ifsock</code>"</a></h2> - -<p> -<code>ifsock</code> only handles <code>S_IFSOCK</code> filesystem -nodes for filesystems which don't do it themselves, acting as a hook -upon which to hang Unix domain socket addresses. pfinet and pflocal -implement the socket API. (Thomas Bushnell, 10 Oct 1996) - -<p> -Running "<code>/hurd/ifsock --help</code>" gives: -<br> -<pre> -/hurd/ifsock: Must be started as a translator -</pre> - - - -<h2 class="center"><a href="#TOC_init" name="init" type="text/html"> -The initialisation server - "<code>init</code>"</a></h2> - -<p> -A server for system boot procedures and basic runtime configurations. - -<p> -Running "<code>/hurd/init --help</code>" gives: -<br> -<pre> -Usage: init [OPTION...] -Start and maintain hurd core servers and system run state - - -d, --debug - -f, --fake-boot This hurd hasn't been booted on the raw machine - -n, --init-name - -q, --query Ask for the names of servers to start - -s, --single-user Startup system in single-user mode - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_isofs" name="isofs" type="text/html"> -The iso filesystem server - "<code>isofs</code>"</a></h2> - -<p> -A server for iso-type filesystems, commonly used on compact disks. - -<p> -Running "<code>/hurd/isofs --help</code>" gives: -<br> -<pre> -Usage: isofs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - -C, --directory=DIRECTORY - --device-master-port=PORT - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_magic" name="magic" type="text/html"> -The magic server - "<code>magic</code>"</a></h2> - -<p> -A translator that returns the magic retry result <code>MAGIC</code>. - -Normal end users probably need not to know much about it since it is used, -for example, to facilitate terminal I/O. Programmers might benefit from the -following pieces of information Thomas Bushnell gave: - -<blockquote> -<p> -The key here is to know what a "magic retry result" is. -The thing to do is to look at the <code>dir_lookup</code> <abbr>RPC</abbr> -documented in <code><hurd/fs.defs></code> and -<code><hurd/hurd_types.defs></code>. - -<br> -Magic lookup results are basically for cases where the lookup needs -information that is part of the calling process's state, and not part -of the normal name lookup procedure. These "punt to caller's state" -things have to each be implemented specially in the C library (see -<code>libc/hurd/hurdlookup.c</code>), and cover the known cases to provide the -functionality that many other systems provide. -</p> -</blockquote> - -<p> -He also kindly explained a particular behavior that usually puzzles normal -end users when they first encounter it: - -<blockquote> -<p> -The inability to "<kbd>ls /dev/fd</kbd>" is because the translator -doesn't know what file descriptors you have open, so it can't tell you which -ones exist. But the behavior of it is exactly as on other systems. -</p> -</blockquote> - -<p> -Running "<code>/hurd/magic --help</code>" gives: -<br> -<pre> -Usage: magic [OPTION...] MAGIC -A translator that returns the magic retry result MAGIC - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_new-fifo" name="new-fifo" type="text/html"> -The new-fifo server - "<code>new-fifo</code>"</a></h2> - -<p> -Alternative server for named pipes. - -<p> -Running "<code>/hurd/new-fifo --help</code>" gives: -<br> -<pre> -Usage: new-fifo [OPTION...] - - -d, --dgram Reflect write record boundaries - -n, --noblock Don't block on open - -r, --multiple-readers Allow multiple simultaneous readers - -s, --server Operate in server mode - -S, --standalone Don't attempt to use a fifo server - -U, --use-server=NAME Attempt use server NAME - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_nfs" name="nfs" type="text/html"> -The network filesystem server - "<code>nfs</code>"</a></h2> - -<p> -Network file system support for Sun's Network File System. - -<p> -Running "<code>/hurd/nfs --help</code>" gives: -<br> -<pre> -Usage: nfs [OPTION...] REMOTE_FS [HOST] -Hurd nfs translator - - -h, --hard Retry file systems requests until they succeed - -s, --soft[=RETRIES] File system requests will eventually fail, after - RETRIES tries if specified, otherwise 3 - -R, --read-size=BYTES, --rsize=BYTES - Max packet size for reads (default 8192) - -W, --write-size=BYTES, --wsize=BYTES - Max packet size for writes (default 8192) - - Timeouts: - --cache-timeout=SEC Timeout for cached file data (default 3) - --init-transmit-timeout=SEC - --max-transmit-timeout=SEC - --name-cache-neg-timeout=SEC - Timeout for negative directory cache entries - (default 3) - --name-cache-timeout=SEC Timeout for positive directory cache entries - (default 3) - --stat-timeout=SEC Timeout for cached stat information (default 3) - - Server specification: - --default-mount-port=PORT Port for mount server, if none can be found - automatically - --default-nfs-port=PORT Port for nfs operations, if none can be found - automatically - --mount-port=PORT Port for mount server - --mount-program=ID[.VERS] - --nfs-port=PORT Port for nfs operations - --nfs-program=ID[.VERS] - --pmap-port=SVC|PORT - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If HOST is not specified, an attempt is made to extract it from REMOTE_FS, -using either the `HOST:FS' or `FS@HOST' notations. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_null" name="null" type="text/html"> -The kitchen sink - "<code>null</code>"</a></h2> - -<p> -A server for lots of free space and countless numbers of zeroes, implements -<code>/dev/null</code> and <code>/dev/zero</code>. - -<p> -Running "<code>/hurd/null --help</code>" gives: -<br> -<pre> -Usage: null [OPTION...] -Endless sink and null source - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_pfinet" name="pfinet" type="text/html"> -The TCP/IP server - "<code>pfinet</code>"</a></h2> - -<p> -A server for TCP/IP, which implements the (IPv4) PF_INET protocol -family. The server which will implement the IPv6 protocol family would -be called pfinet6 in the current scheme.</p> -<p> -Setting this up isn't hard at all. It always is placed in -<code>/servers/socket/2</code>, because that's where glibc will look for it. -So be sure to install it this way: -<code>settrans /servers/socket/2 /hurd/pfinet -6 /servers/socket/26 --interface=/dev/eth0 OPTIONS</code> and -<code>settrans /servers/socket/26 /hurd/pfinet -4 /servers/socket/2 --interface=/dev/eth0 OPTIONS</code>, -where <code>OPTIONS</code> -specify your IP address, netmask and the gateway (if any). Only one -network interface is supported currently. Later, you can also set further -interfaces like <code>eth1</code> and so on with the same command.</p> -<p> -If you don't have a network card you should at least install the loopback -interface, so localhost works (important for print spooling and other useful -stuff). Do this with the above command, but don't specify any interface or -<code>OPTIONS</code>. A simple <code>settrans /servers/socket/1 -/hurd/pfinet</code> will do it.</p> -<p> -Running "<code>/hurd/pfinet --help</code>" gives: -<br> -<pre> -Swansea University Computer Society TCP/IP for NET3.019 -IP Protocols: ICMP, UDP, TCP -Usage: pfinet [OPTION...] -Interface-specific options before the first interface specification apply to -the first following interface; otherwise they apply to the previously specified -interface. - - -i, --interface=DEVICE Network interface to use - - These apply to a given interface: - -a, --address=ADDRESS Set the network address - -g, --gateway=ADDRESS Set the default gateway - -m, --netmask=MASK Set the netmask - -s, --shutdown Shut it down - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_pflocal" name="pflocal" type="text/html"> -The pflocal server - "<code>pflocal</code>"</a></h2> - -<p> -Implements UNIX domain sockets. Needed for pipes, for example. - -<p> -Running "<code>/hurd/pflocal --help</code>" gives: -<br> -<pre> -Usage: /hurd/pflocal -</pre> - -<h2 class="center"><a href="#TOC_proc" name="proc" type="text/html"> -The process server - "<code>proc</code>"</a></h2> - -<p> -The proc server assigns PID's and process structures to tasks, and manages -all the process level stuff like wait, bits of fork, C library support. - -<p> -Running "<code>/hurd/proc --help</code>" gives: -<br> -<pre> -Usage: proc [OPTION...] -Hurd process server - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_storeio" name="storeio" type="text/html"> -The storage translator - "<code>storeio</code>"</a></h2> - -<p> -A translator for devices and other stores. - -<p> -Running "<code>/hurd/storeio --help</code>" gives: -<br> -<pre> -Usage: storeio [OPTION...] DEVICE... -Translator for devices and other stores - - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --rdev=ID The stat rdev number for this node; may be either - a single integer, or of the form MAJOR,MINOR - -r, --readonly Disallow writing - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Allow writing - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_symlink" name="symlink" type="text/html"> -The symbolic link server - "<code>symlink</code>"</a></h2> - -<p> -A server for symbolic links for filesystems which don't support it -themselves. - -<p> -Running "<code>/hurd/symlink --help</code>" gives: -<br> -<pre> -? -</pre> -(There has not been any output? Strange...) - - -<h2 class="center"><a href="#TOC_term" name="term" type="text/html"> -The terminal server - "<code>term</code>"</a></h2> - -<p> -Implements a POSIX terminal. - -<p> -Running "<code>/hurd/term --help</code>" gives: -<br> -<pre> -Usage: term ttyname type arg -</pre> - - - -<h2 class="center"><a href="#TOC_ufs" name="ufs" type="text/html"> -The ufs server - "<code>ufs</code>"</a></h2> - -<p> -A server for ufs-type filesystems. It does the same as -<code>ufs.static</code>, only that <code>ufs.static</code> -is a statically linked executable. - -<p> -Running "<code>/hurd/ufs --help</code>" gives: -<br> -<pre> -Usage: ufs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -C, --compat=FMT FMT may be GNU, 4.4, or 4.2, and determines which - filesystem extensions are written onto the disk - (default is GNU) - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - --device-master-port=PORT - --directory=DIRECTORY - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_usermux" name="usermux" type="text/html"> -The usermux translator - "<code>usermux</code>"</a></h2> - -<p> -A translator for invoking user-specific translators. - -<p> -Running "<code>/hurd/usermux --help</code>" gives: -<br> -<pre> -Usage: usermux [OPTION...] [TRANSLATOR [ARG...]] -A translator for invoking user-specific translators - - -C, --clear-patterns Reset all patterns to empty; this option may then - be followed by options to set specific patterns - --home-pattern=PAT The string to replace in the translator - specification with the user's home directory - (default `${home}') - --uid-pattern=PAT The string to replace in the translator - specification with the uid (default `${uid}') - --user-pattern=PAT The string to replace in the translator - specification with the user name (default - `${user}') - -?, --help Give this help list - --usage Give a short usage message - -This translator appears like a directory in which user names can be looked up, -and will start TRANSLATOR to service each resulting node. If no pattern occurs -in the translator specification, the users's home directory is appended to it -instead; TRANSLATOR defaults to /hurd/symlink. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -# Uncomment and fill the blanks... -#<h2 class="center"><a href="#TOC_" name="" type="text/html"> -#The server - "<code></code>"</a></h2> -# -#<p> -#A server for . -# -#<p> -#Running "<code>/hurd/ --help</code>" gives: -#<br> -#<pre> -# -#</pre> diff --git a/greek/ports/hurd/hurd-doc-translator.wml b/greek/ports/hurd/hurd-doc-translator.wml deleted file mode 100644 index 037dade40e6..00000000000 --- a/greek/ports/hurd/hurd-doc-translator.wml +++ /dev/null @@ -1,241 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="55a70d0c0f3df8d4df237334ac6de72daaa99f73" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> -<h2>Translators</h2> -<ul> -<li><a href="#concept" name="TOC_concept">Concept</a></li> -<li><a href="#examples" name="TOC_examples">Examples</a></li> -<li><a href="#actpas" name="TOC_actpas">Passive Translators, Active Translators</a></li> -<li><a href="#manage" name="TOC_manage">Managing Translators</a></li> -</ul> - -<h3><a href="#TOC_concept" name="concept">Concept</a></h3> -<p> -Before we take a closer look at translators, let us consider regular -filesystems. A filesystem is a store for a hierarchical tree of directories -and files. You access directories and files by a special character string, -the path. Furthermore, there are symbolic links to refer to one file at -several places in the tree, there are hard links to give one and the same -file several names. There are also special device files for communication -with the hardware device drivers of the kernel, and there are mount points -to include other stores in the directory tree. Then there are obscure -objects like FIFOs.</p> -<p> -Although these objects are very different, they share some common -properties, for example, they have all an owner and a group associated with -them as well as access rights (permissions). This information is written in -inodes. This is actually a further commonality: Every object has exactly -one inode associated with it (hard links are somewhat special as they share -one and the same inode). Sometimes, the inode has further information -stored in it. For example, the inode can contain the target of a symbolic -link.</p> -<p> -However, these commonalities are usually not exploited in the -implementations, despite the common programming interface to them. All -inodes can be accessed through the standard POSIX calls, for example -<code>read()</code> and <code>write()</code>. For example, to add a new -object type (for example a new link type) to a common monolithic unix -kernel, you would need to modify the code for each filesystem -separately.</p> -<p> -In the Hurd, things work differently. Although in the Hurd a special -filesystem server can exploit special properties of standard object types -like links (in the ext2 filesystem with fast links, for example), it has a -general interface to add such features without modifying existing code.</p> -<p> -The trick is to allow a program to be inserted between the actual content of -a file and the user accessing this file. Such a program is called a -translator, because it is able to process the incoming requests in many -different ways. In other words, a translator is a Hurd server which provides -the basic filesystem interface.</p> -<p> -Translators have very interesting properties. From the kernel's point of -view, they are just another user process. This means, translators can be run -by any user. You don't need root privileges to install or modify a -translator, you only need the access rights for the underlying inode the -translator is attached to. Many translators don't require an actual file to -operate, they can provide information by their own means. This is why -the information about translators is stored in the inode.</p> -<p> -Translators are responsible to serve all file system operations that involve -the inode they are attached to. Because they are not restricted to the usual -set of objects (device file, link etc), they are free to return anything -that makes sense to the programmer. One could imagine a translator that -behaves like a directory when accessed by <code>cd</code> or -<code>ls</code> and at the same time behaves like a file when accessed by -<code>cat</code>.</p> - -<h3><a href="#TOC_examples" name="examples">Examples</a></h3> -<h4>Mount Points</h4> -<p> -A mount point can be seen as an inode that has a special translator attached -to it. Its purpose would be to translate filesystem operations on the mount -point in filesystem operations on another store, let's say, another -partition.</p> -<p> -Indeed, this is how filesystems are implemented under the Hurd. A -filesystem is a translator. This translator takes a store as its argument, -and is able to serve all filesystem operations transparently.</p> - -<h4>Device Files</h4> -<p> -There are many different device files, and in systems with a monolithical -kernel, they are all provided by the kernel itself. In the Hurd, all device -files are provided by translators. One translator can provide support for -many similar device files, for example all hard disk partitions. This way, -the number of actual translators needed is quite small. However, note that -for each device file accessed, a separate translator task is started. -Because the Hurd is heavily multi threaded, this is very cheap.</p> -<p> -When hardware is involved, a translator usually starts to communicate with -the kernel to get the data from the hardware. However, if no hardware access -is necessary, the kernel does not need to be involved. For example, -<code>/dev/zero</code> does not require hardware access, and can therefore -be implemented completely in user space.</p> - -<h4>Symbolic Links</h4> -<p> -A symbolic link can be seen as a translator. Accessing the symbolic link -would start up the translator, which would forward the request to the -filesystem that contains the file the link points to.</p> -<p> -However, for better performance, filesystems that have native support -for symbolic links can take advantage of this feature and implement -symbolic links differently. Internally, accessing a symbolic link would not -start a new translator process. However, to the user, it would still look -as if a passive translator is involved (see below for an explanation what a -passive translator is).</p> -<p> -Because the Hurd ships with a symlink translator, any filesystem server that -provides support for translators automatically has support for symlinks (and -firmlinks, and device files etc)! This means, you can get a working -filesystem very fast, and add native support for symlinks and other features -later.</p> - -<h3><a href="#TOC_actpas" name="actpas">Passive Translators, Active Translators</a></h3> -<p> -There are two types of translators, passive and active. They are really -completely different things, so don't mix them up, but they have a close -relation to each other.</p> - -<h4>Active Translators</h4> -<p> -An active translator is a running translator process, as introduced above. -You can set and remove active translators using the -<code>settrans -a</code> -command. The <code>-a</code> option is necessary to tell -<code>settrans</code> that you want to modify the active translator.</p> -<p> -The <code>settrans</code> command takes three kind of arguments. First, you -can set options for the <code>settrans</code> command itself, like -<code>-a</code> to modify the active translator. Then you set the inode you -want to modify. Remember that a translator is always associated with an -inode in the directory hierarchy. You can only modify one inode at a time. -If you do not specify any more arguments, <code>settrans</code> will try to -remove an existing translator. How hard it tries depends on the force -options you specify (if the translator is in use by any process, you will -get "device or resource busy" error message unless you force it to go away).</p> -<p> -But if you specify further arguments, it will be interpreted as a command -line to run the translator. This means, the next argument is the filename of -the translator executable. Further arguments are options to the translator, -and not to the <code>settrans</code> command.</p> -<p> -For example, to mount an ext2fs partition, you can run -<code>settrans -a -c /mnt /hurd/ext2fs /dev/hd2s5</code>. The -<code>-c</code> option will create the mount point for you if it doesn't -exist already. This does not need to be a directory, by the way. To unmount, -you would try <code>settrans -a /mnt</code>.</p> - -<h4>Passive Translators</h4> -<p> -A passive translator is set and modified with the same syntax as the active -translator (just leave away the <code>-a</code>), so everything said above is -true for passive translators, too. However, there is a difference: passive -translators are not yet started.</p> -<p> -This makes sense, because this is what you usually want. You don't want the -partition mounted unless you really access files on this partition. You -don't want to bring up the network unless there is some traffic and so -on.</p> -<p> -Instead, the first time the passive translator is accessed, it is -automatically read out of the inode and an active translator is started on -top of it using the command line that was stored in the inode. This is -similar to the Linux automounter functionality. However, it does not come as -an additional bonus that you have to set up manually, but an integral part of -the system. So, setting passive translators defers starting the translator -task until you really need it. By the way, if the active translator dies for -some reason, the next time the inode is accessed the translator is -restarted.</p> -<p> -There is a further difference: active translators can die or get lost. As -soon as the active translator process is killed (for example, because you -reboot the machine) it is lost forever. Passive translators are not transient -and stay in the inode during reboots until you modify them with the -<code>settrans</code> program or delete the inodes they are attached to. -This means, you don't need to maintain a configuration file with your mount -points.</p> -<p> -One last point: Even if you have set a passive translator, you can still -set a different active translator. Only if the translator is automatically -started because there was no active translator the time the inode was -accessed the passive translator is considered.</p> - -<h3><a href="#TOC_manage" name="manage">Managing Translators</a></h3> -<p> -As mentioned above, you can use -<code>settrans</code> -to set and alter passive and active translators. There are a lot of options -to change the behaviour of <code>settrans</code> in case something goes -wrong, and to conditionalize its action. Here are some common usages:</p> -<ul><li><code>settrans -c /mnt /hurd/ext2fs /dev/hd2s5</code> mounts a -partition, the translator will stay across reboots.</li> -<li><code>settrans -a /mnt /hurd/ext2fs ~/dummy.fs</code> mounts a -filesystem inside a data file, the translator will go away if it dies.</li> -<li><code>settrans -fg /nfs-data</code> forces a translator to go away.</li> -</ul> -<p> -You can use the <a href="hurd-doc-utils#showtrans"><code>showtrans</code></a> -command to see if a translator is attached to an inode. This will only show -you the passive translator though.</p> -<p> -You can change the options of an active (filesystem) translator with -<code>fsysopts</code> without actually restarting it. This is very -convenient. For example, you can do what is called "remounting a -partition read-only" under Linux simply by running <code>fsysopts -/mntpoint --readonly</code>. The running active translator -will change its behaviour according to your request if possible. -<code>fsysopts /mntpoint</code> without a parameter shows you the current -settings.</p> - -<h4>Examples</h4> -<p> -I recommend that you start by reading the <code>/bin/mount</code> command, -it is only a small script. Because setting filesystem translators is -similar to mounting partitions, you can easily grasp the concept this way. -Make a file system image with <code>dd if=/dev/zero of=dummy.fs bs=1024k -count=8; mke2fs dummy.fs</code> and "mount" it with <code>settrans -c dummy -/hurd/ext2fs `pwd`/dummy.fs</code>. Note that the translator is not started -yet, no new <code>ext2fs</code> process is running (verify with <code>ps -Aux</code>). Check that everything is correct using <code>showtrans</code>.</p> -<p> -Now type <code>ls dummy</code> and you will notice the short delay that -occurs while the translator is started. After that, there will be no more -delays accessing dummy. Under Linux, one would say that you automounted a -loop file system. Check with <code>ps Aux</code> that there is an <code>ext2fs -dummy</code> process up and running now. Now put some files into the new -directory. Try to make the filesystem read-only with <code>fsysopts</code>. -Note how further write attempts fail now. Try to kill the active translator -with <code>settrans -g</code>.</p> -<p> -You should have some understanding of what is going on now. Now remember -that this was only <em>one</em> special server, the Hurd ext2fs server. -There are many more server in the <code>hurd</code> directory. Some of them -are for filesystems. Some are needed for file system features like links. -Some are needed for device files. Some are useful for networking. Imagine -"mounting" an FTP Server with <code>settrans</code> and downloading files -simply with the standard <code>cp</code> command. Or editing your web sites -with <code>emacs /ftp/homepage.my.server.org/index.html</code>!</p> diff --git a/greek/ports/hurd/hurd-doc-utils.wml b/greek/ports/hurd/hurd-doc-utils.wml deleted file mode 100644 index 8b1081045b4..00000000000 --- a/greek/ports/hurd/hurd-doc-utils.wml +++ /dev/null @@ -1,123 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="cdc565969852e30580c3ad8ce3e7952261f03573" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> - -<table border="2" - summary="Index of GNU/Hurd utilities"> - -<caption><em>Index of GNU/Hurd utilities:</em></caption> - -<tr> - <th><a href="#syncfs" name="TOC_syncfs" type="text/html"> - Sync'ing filesystems</a></th> - <th>"<code>syncfs</code>"</th> -</tr> -<tr> - <th><a href="#showtrans" name="TOC_showtrans" type="text/html"> - Show the passive translator of a FILE</a></th> - <th>"<code>showtrans</code>"</th> -</tr> -<tr> - <th><a href="#devprobe" name="TOC_devprobe" type="text/html"> - Probing for hardware devices</a></th> - <th>"<code>devprobe</code>"</th> -</tr> - -#Uncomment and fill the blanks... -#<tr> -# <th><a href="#" name="TOC_" type="text/html"> -# The server</a></th> -# <th>"<code></code>"</th> -#</tr> -</table> - - -<h2 class="center"><a href="#TOC_syncfs" name="syncfs" type="text/html"> -Sync'ing filesystems - "<code>syncfs</code>"</a></h2> - -<p> -<code>syncfs</code> can be used to flush the write cache for disk -filesystems. - -<p> -Running "<code>/bin/syncfs --help</code>" gives: -<br> -<pre> -Usage: syncfs [FILE...] - Force all pending disk writes to be done immediately - - -s, --synchronous Wait for completion of all disk writes - -c, --no-children Do not synchronize child filesystems - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - - The filesystem containing each FILE is synchronized, and its child - filesystems unless --no-children is specified. With no FILE argument - synchronizes the root filesystem. - -Report bugs to bug-hurd@gnu.org. -</pre> - -<h2 class="center"><a href="#TOC_showtrans" name="showtrans" type="text/html"> -Show the passive translator of a FILE - "<code>showtrans</code>"</a></h2> - -<p> -If you want to know which passive translator is connected to an inode if -any, use <code>settrans</code> to figure it out. - -<p> -Running "<code>/bin/showtrans --help</code>" gives: -<br> -<pre> -Usage: showtrans FILE... - Show the passive translator of FILE... - - -p, --prefix Always display `FILENAME: ' before translators - -P, --no-prefix Never display `FILENAME: ' before translators - -s, --silent No output; useful when checking error status - -t, --translated Only display files that have translators - - A FILE argument of `-' prints the translator on the node - attached to standard input. - -</pre> - -<h2 class="center"><a href="#TOC_devprobe" name="devprobe" type="text/html"> -Probing for devices - "<code>devprobe</code>"</a></h2> - -<p> -The <code>devprobe</code> utility probes for one or multiple Mach devices. -Just specify the names as arguments on the command line: If some of the -devices exists it will echo their names one per line and exits successfully, -otherwise it will return 1. The provided options make it easier to use this -utility in batch mode. - -<p> -Running "<code>/bin/devprobe --help</code>" gives: -<br> -<pre> -Usage: devprobe DEVNAME... - Test for the existence of mach device DEVNAME... - - -s, --silent Don't print devices found - -f, --first Stop after the first device found - - The exit status is 0 if any devices were found. -</pre> - -#Uncomment and fill the blanks... -#<h2 class="center"><a href="#TOC_" name="" type="text/html"> -#The server - "<code></code>"</a></h2> -# -#<p> -#A server for . -# -#<p> -#Running "<code>/hurd/ --help</code>" gives: -#<br> -#<pre> -# -#</pre> diff --git a/greek/ports/hurd/hurd-install.wml b/greek/ports/hurd/hurd-install.wml deleted file mode 100644 index 77bdd2a048f..00000000000 --- a/greek/ports/hurd/hurd-install.wml +++ /dev/null @@ -1,917 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd — Configuration" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="ad90efc904807b8db1f35dd7d05b950182b3c1fa" maintainer="galaxico" - -<h1>Debian GNU/Hurd Configuration</h1> - -<p> -This document aims to provide an easy and relatively painless set of -instructions on how to configure Debian GNU/Hurd with a minimum -amount of effort. -</p> - -<p> -It is based in Neal H. Walfield's <q>The Hurd Installation Guide</q>. -Many thanks to Neal for his contribution. -</p> - -<h2>Overview </h2> - -<p> -GNU is similar in nature to any Unix-like system: after logging in, the user is -presented with a shell and the familiar Unix VFS (virtual filesystem). Although -GNU tries to be POSIX compliant, it is <q>Not Unix</q>. GNU/Hurd builds upon many of -the Unix concepts and extends them to either add new functionality or to fix -what has been perceived as flaws in the original design. The most noticeable -difference is translators, user space programs which interact with the VFS. -These filesystems do not live in the kernel nor do they need to be run -as root; they only need access to the backing store and the -<code>mount point</code>. Another difference is that processes, rather than having a single -user identity fixed at creation time, have identity tokens which are disjoint -from the process, i.e. they may be added with the appropriate permission from -an authority or destroyed. -</p> - -<p> -Being familiar with the Unix environment (and especially GNU userland, found in -popular variants such as GNU/Linux) is an imperative for feeling at ease in -GNU. Having experience with the Debian tools will also prove invaluable to the -configuration and maintenance of a GNU/Hurd box. -</p> - -<p> -This guide endeavors to make installing GNU/Hurd as painless a process as -possible. If there are errors, they are most certainly the author's. Please -report them, along with any other suggestions or criticisms, to him; all are -gladly accepted. -</p> - -#<h2> 2. Real Estate or Finding A Home </h2> -# -#<p> -#If you do not have an available partition or an extra hard drive, this can be -#the longest step. In this case, you will need to repartition the hard drive. -#One solution is to use GNU's partition editor, -#<a href="https://packages.debian.org/parted">Parted</a>. It features not only -#basic partition editing but also partition resizing and moving functionality. -#The manual is quite complete and includes several tutorials. Note that also -#there is a <code>63 GNU HURD or SysV</code> partition type, it should not be -#used or else the installation CD will not find it. Just use <code>83 -#Linux</code> -#</p> -# -#<p> -#The Hurd supports several extensions to the ext2fs filesystem format. Foremost -#among these are passive translators and a fourth set of permission bits for -#unknown users (users without an identity, not the other user). To use these -#extensions, the owner of the partition must be set to <code>hurd</code>. -#<code>mke2fs</code>, unless specifically overridden on the command line, will -#set the owner to whatever kernel it is running on. As the Hurd will diligently -#respect this setting, care must be taken to set this appropriately or the Hurd -#will fail in subtle ways. Be aware that even if a file system is owned by a -#particular kernel, others may still use it; they just may not be able to use -#certain extensions. -#</p> -# -#<p> -#To create a filesystem, use <code>mke2fs</code> and pass it <q><var>-b 4096 -#-I 128 -o hurd</var></q> to designate the Hurd as the owner of the new file -#system. For instance, assuming the partition is <tt><q>/dev/hda1</q></tt>: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# mke2fs -b 4096 -I 128 -o hurd /dev/hda1 -#</pre></td></tr></table> -# -# -#<h2> 3. The Boot Loader </h2> -# -#<p> -#The bootloader of the GNU system is Grub, the GRand Unified Boot loader, -#and it is its main purpose to boot the GNU system core (Mach and the Hurd). -#Any boot loader that supports the multiboot standard, though, may be used to -#load Mach and the Hurd. At the moment (that we're aware of), GNU Grub is the -#only bootloader that supports such standard. -#</p> -# -#<p> -#A word about Grub. Unlike traditional boot loaders on the x86, such as LILO, -#Grub is very powerful. It has a command line interface, bootp, dummy terminal -#support and a plethora of other features. In addition, it can boot almost any -#kernel. If you have ever booted an alpha or sparc, you will understand what -#Grub can do. Therefore, do not be scared: Grub is better. You will like it. -#You will not go back. -#</p> -# -#<p> -#It is probably better if you install -#<a href="https://packages.debian.org/grub2">Grub</a> before installing the -#Hurd, but you can always install it onto your hard drive at a later date. -#</p> -# -# -#<h2> 4. Cross Install </h2> -# -#<p> -#The next step is to get a base system. There are several alternatives, if you -#are running a Debian system you can use the package crosshurd. Otherwise you -#can get an updated base system tarball from any of the mirrors listed at -#<url "https://wiki.debian.org/DebianPorts/Mirrors" />. -#</p> -# -#<p> -#The tarball is set up to extract everything into the current directory. -#After the filesystem is mounted, the archive can be extracted. -#Assuming that the filesystem is on <tt><q>/dev/hda2</q></tt>, the mount point -#is <tt><q>/gnu</q></tt> and archive is in current user's home directory, the -#following is required: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# mount -t ext2 /dev/hda2 /gnu -# \# cd /gnu -# \# tar --same-owner -xvjpf ~/gnu.tar.bz2 -#</pre></td></tr></table> -# -# -#<h2> 5. Booting GNU/Hurd </h2> -# -#<p> -#All is now in readiness to boot GNU/Hurd for the first time. Note that depending -#on your version of GRUB, small details with vary. Please make sure whether you -#have GRUB1 (aka legacy aka 0.95 and later up to 0.97), or GRUB2 (aka 1.95 and -#later). Examples below will provide both versions, make sure to pick the right -#one. -#</p> -# -#<p> -#Please also note that some problems have been reported when booting with only -#128MB memory, because of swap not being setup yet at this stage. Make sure to -#provide at least 256MB memory. -#</p> -# -#<p> -#If your system already has GRUB installed, just reboot it. Else, you need to use -#a Grub boot disk. On Debian, the grub-disk (grub1) or grub-rescue-pc (grub2) -#packages provides CD and Floppy disk images. Make sure that the Grub boot disk -#is in the drive, reboot. If all goes well, either a Grub menu or command line -#will be displayed. If the menu has a <tt><q>GNU/Hurd</q></tt> entry, you will -#probably be able to just reuse it to save a lot of typing burden. For now, if -#presented with a menu, press <kbd>c</kbd> to go to the command line. -#</p> -# -#<p> -#First, GNU Mach needs to be loaded. This requires knowing the filesystem -#and the path to GNU Mach. Grub uses a partition nomenclature that is a bit -#different from both Linux and the Hurd: both IDE and SCSI drives are named -#<tt><q>(hdN,M)</q></tt>. <code>N</code> is the drive number (zero based) as -#enumerated by the BIOS. That is, Grub makes no distinction between IDE and SCSI -#disks. <code>M</code> identifies the partition on the drive. It is zero based -#in grub1 but one based in grub2. If this sounds confusing, relax: Grub is also -#helpful. -#</p> -# -#<p> -#To determine on which filesystem a particular file resides, Grub provides the -#<code>find</code> command. When this command is issued along with a filename, -#Grub searches on each filesystem for the specified file and prints where it was -#found. For example, to search for the kernel, <tt><q>/boot/gnumach.gz</q></tt>: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> find /boot/gnumach.gz -# (hd0,0) -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> search -f /boot/gnumach.gz -# (hd0,1) -#</pre></td></tr> -#</table> -# -#<p> -#Here, Grub1 indicates that <tt><q>/boot/gnumach.gz</q></tt> is on -#<tt><q>(hd0,0)</q></tt> and Grub2, on <tt><q>(hd0,1)</q></tt> (remember the difference -#in partition numbering between Grub1 and Grub2). To save you a couple of -#typing, set Grub's root to that value: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> root (hd0,0) -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> set root=(hd0,1) -#</pre></td></tr> -#</table> -# -#<p> -#Before loading the kernel, at least one option, the root partition, must be -#specified on the command line. This will be used by the Hurd itself (i.e. not -#Grub). As such, it must be in terms that the Hurd can understand. -#</p> -# -#<p> -#GNU Mach enumerates disks starting at zero. IDE drives are prefixed with -#<code>hd</code>, while SCSI disks are prefixed with <code>sd</code>. Like -#Linux, drives are number by their position on the controller. For instance, the -#primary master is <code>hd0</code> and the secondary slave is <code>hd3</code>. -#Partitions use the BSD slice naming convention and append <code>sM</code> to the -#drive name to indicate a given partition. Note that <code>M</code> is a one, not -#zero, based index. The slice number is simple to calculate: if you have Grub2, -#just reuse the same index, if you have Grub1, just increment what was used for -#Grub1 by one. -#</p> -# -#<p> -#Since the Hurd has not yet been configured, it must be started in single user -#mode. Adding a <q><var>-s</var></q> to the kernel command line is all that is -#required. -#</p> -# -#<p> -#To sum it up, assuming that the first drive (i.e. <tt><q>(hd0)</q></tt>) is the -#master on the master controller, we would have: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> kernel /boot/gnumach.gz root=device:hd0s1 -s -# [Multiboot-elf, ...] -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> multiboot /boot/gnumach.gz root=device:hd0s1 -s -#</pre></td></tr> -#</table> -# -#<p> -#Next, the root filesystem server and the <code>exec</code> server must be -#loaded. This is done using Grub's boot module capability. The ${var} are -#filled in by GNU Mach. The arguments are used by the Hurd to indicate what -#type of information is being provided. Since the ext2fs command line is very -#long, it can be broken up by escaping the newline character in the normal Unix -#fashion. Be sure that there is not space after the antislash at the end of each -#line. Also be sure to differentiate <kbd>{</kbd> and <kbd>}</kbd> from <kbd> -#(</kbd> and <kbd>)</kbd>. Mind the subttle differences between Grub1 and -#Grub2: Grub2 needs that the filename be repeated and quotes need -#to be used. Note that at this stage the <var>--readonly</var> option of -#<code>ext2fs.static</code> must not be passed. -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> module /hurd/ext2fs.static \ -# --multiboot-command-line=${kernel-command-line} \ -# --host-priv-port=${host-port} \ -# --device-master-port=${device-port} \ -# --exec-server-task=${exec-task} -T typed ${root} \ -# $(task-create) $(task-resume) -# [Multiboot-module 0x1c4000, 0x2cfe6a bytes] -# grub1> module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) -# [Multiboot-module 0x494000, 0x27afe bytes] -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> module /hurd/ext2fs.static ext2fs \ -# --multiboot-command-line='${kernel-command-line}' \ -# --host-priv-port='${host-port}' \ -# --device-master-port='${device-port}' \ -# --exec-server-task='${exec-task}' -T typed '${root}' \ -# '$(task-create)' '$(task-resume)' -# grub2> module /lib/ld.so.1 exec /hurd/exec '$(exec-task=task-create)' -#</pre></td></tr> -#</table> -# -#<p> -#Alternatively, you can throw these lines into a <tt><q>menu.lst</q></tt> -#(Grub1) or <tt><q>grub.cfg</q></tt> (Grub2) configuration file in the partition, -#and load it by using <tt><q>configfile /path/to/menu.lst</q></tt> (Grub1) or -#<tt><q>configfile /path/to/grub.cfg</q></tt> (Grub2) from the grub prompt. You -#can of course also simply install grub in some MBR and point it to there. -#</p> -# -#<p> -#GNU/Hurd can be now booted: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -#grub> boot -#</pre></td></tr></table> -# -#<p> -#If GNU/Hurd fails to boot, it could be due to shared IRQs: GNU Mach does not -#play well with these. You can verify your situation by looking at, for -#instance, the <tt><q>/proc/interrupts</q></tt> file under GNU/Linux. Also, as GNU -#Mach does not support loadable kernel modules, many of the drivers are compiled -#into the default kernel. If there are old peripherals, this can be a problem: a -#device may incorrectly respond to a probe intended for a completely unrelated -#device and thereby cause a crash. Building a new kernel with only the required -#device drivers will usually solve this problem. GNU Mach is easily cross -#compiled. If you are running Debian, install the <tt><q>mig</q></tt> package, -#and your stock <tt><q>gcc</q></tt> should do. -#</p> -# -#<p> -#If this does not help, ask on the appropriate mailing list. -#</p> -# -# -#<h2> 6. Native Install </h2> -# -#<p> -#Once you are presented with a shell prompt, and any time that the Hurd is in -#single user mode, it is necessary to set the terminal type: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# export TERM=mach -#</pre></td></tr></table> -# -#<p> -#Be warned that <kbd>CONTROL-C</kbd> and family will not work in single user -#mode. -#</p> -# -#<p> -#We can now run the <code>native-install</code> script. This will configure the -#packages and set up several important translators: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# ./native-install -#</pre></td></tr></table> -# -#<p> -#Before the script terminates, it will indicate that you can now reboot and enter -#multi-user mode. Do so, this is the Hurd, welcome! -#</p> - - -<h2> Installation </h2> - -<p> -You can simply use the Debian installer, see the -<a href="hurd-cd">prepared CD images</a>. -Then the following steps will be needed for proper configuration. -</p> - -<p> -You can also get a pre-installed image and run it in qemu: -</p> - -<table><tr><td> </td><td class=example><pre> -$ wget https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/debian-hurd.img.tar.gz -$ tar xzf debian-hurd.img.tar.gz -$ kvm -m 1G -drive file=$(echo debian-hurd*.img),cache=writeback -</pre></td></tr></table> - -<p> -To enable accessing the box through ssh, you can append -</p> - -<table><tr><td> </td><td class=example><pre> --net nic -net user,hostfwd=tcp:127.0.0.1:2222-:22 -</pre></td></tr></table> - -<p> -and ssh to your local TCP port 2222. -</p> - -<p> -You can also convert the image to the VDI format for virtualbox: -</p> - -<table><tr><td> </td><td class=example><pre> -$ VBoxManage convertfromraw debian-hurd-*.img debian-hurd.vdi --format vdi -</pre></td></tr></table> - -<h2> Configuration </h2> - -<h3> The Network </h3> - -<p> -The Debian way is supported starting from sysvinit 2.88dsf-48 and hurd 1:0.5.git20140320-1: <tt>/etc/network/interfaces</tt> is used like on -Linux. The only difference is that network boards appear in <tt>/dev</tt>, and -interfaces should thus be specified as <tt>/dev/eth0</tt> etc. -</p> - -#<p> -#First, make sure that your network card is recognized by GNU Mach: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# devprobe eth0 -# eth0 -#</pre></td></tr></table> -# -#<p> -#If <code>devprobe eth0</code> does not return <code>eth0</code>, the kernel -#didn't detect your network board and you need to try another board. For -#instance, qemu's e1000 board is not supported, the rtl8139 one should work: -#<code>-net nic,model=rtl8139 -net user</code> -#</p> - -#<p> -#Starting from version 20120520-1, the hurd package includes DDE drivers which -#are used to support more recent devices (drivers are taken from Linux -#2.6.32). Translators for that are already set up for you, and all you -#need to do is to replace <code>eth0</code> (the mach driver name) with -#<code>/dev/eth0</code> (the DDE driver path) in the remainder of this document. -#</p> -# -#<p> -#It is possible to try to use the DDE driver even if GNU Mach has a driver: -#passing <code>nonetdev</code> on the gnumach command line will disable the GNU -#Mach driver, and the DDE driver will start working. -#</p> - -<p> -If network does not seem to work, use the following to get debugging information -from the DDE driver: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fga /dev/netdde /hurd/netdde -</pre></td></tr></table> - -<p> -and then kill any devnode and pfinet process to let them restart with the newer -netdde. If it still does not work, please post in a bug report the full output of the netdde settrans -above, as well as the output of <code>lspci</code> and <code>lspci -n</code> . -</p> - -<p> -To configure the network without going through <tt>/etc/network/interfaces</tt>, -the pfinet translator must be configured. -This can be done by using <code>dhclient</code> from the -<code>isc-dhcp-client</code> package. -This can also be done by hand by using <code>inetutils-ifconfig</code> -from the <code>inetutils-tools</code> package, and <code>ping</code> is -available in the <code>inetutils-ping</code> package. -Last but not least, this can be done (and recorded for good) by hand using the -<code>settrans</code> command to attach a translator to a given -filesystem node. When programs access the node by, for example sending an RPC, -the operating system will transparently start the server to handle the request. -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l -</pre></td></tr></table> - -<p> -Here, <code>settrans</code> is passed several options. The first two, -<q><var>fg</var></q>, force any existing translator to go away. The next two, -<q><var>ap</var></q>, make both active and passive translators. By making the -translator active, we will immediately see any error messages on -<tt><q>stderr</q></tt>. The latter saves the translator and arguments in the node -so it can be transparently restarted later (i.e. making the setting persistent -across reboots). The options are followed by the node to which the translator -is to be attached, then the program (i.e. translator) to run and any arguments -to give it. The <q><var>-i</var></q> option is the interface <code>pfinet</code> -will listen on, <q><var>-a</var></q> is the IP address, <q><var>-g</var></q> is the -gateway and <q><var>-m</var></q> is the network mask. -</p> - -<p> -Be sure to add name servers to your <tt><q>/etc/resolv.conf</q></tt> file: -</p> - -<table><tr><td> </td><td class=example><pre> - nameserver 192.168.1.1 -</pre></td></tr></table> - -<p> -To test the configuration, <code>ping -c2 gateway</code>. The -<q><var>-c</var></q> is important to limit the number of pings; recall, -<kbd>CONTROL-C</kbd> does not work in single user mode. -</p> - -<p> -Help on <code>settrans</code> can be obtained by passing it the -<q><var>--help</var></q> option. Help on a specific translator can be gotten by -invoking it from the command line with the same argument, e.g.: -</p> - -<table><tr><td> </td><td class=example><pre> - \# /hurd/pfinet --help -</pre></td></tr></table> - -<p> -As there can be a lot of output, consider piping this through a pager such as -<code>less</code>. -</p> - -<p> -To also configure IPv6 support, the same configuration has to be recorded on -both <tt>/servers/socket/2</tt> and <tt>/servers/socket/26</tt>, referencing -each other so that only one is actually started, bound to both nodes: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fgap /servers/socket/2 /hurd/pfinet -6 /servers/socket/26 -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l - \# settrans -p /servers/socket/26 /hurd/pfinet -4 /servers/socket/2 -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l -</pre></td></tr></table> - -<p> -The pfinet server enables IPv6 autoconfiguration by default. The current status -can be obtained from <tt>fsysopts /servers/socket/26</tt>. Addresses can also -be set by hand, by using e.g. <tt>-A 2001:123:123::42/64 -G 2001:123:123::1</tt>. -</p> - -<p> -The configuration of pfinet can also be changed live -(without record on disk) by using <tt>fsysopts</tt>: -</p> - -<table><tr><td> </td><td class=example><pre> - \# fsysopts /servers/socket/2 - /hurd/pfinet --interface=/dev/eth0 --address=10.3.0.1 --netmask=255.255.0.0 --gateway=10.3.0.128 - \# fsysopts /server/socket/2 -a 10.3.0.2 -m 255.255.0.0 -g 10.3.0.128 -</pre></td></tr></table> - -<p> -A firewall can be set up by interposing the <tt>eth-filter</tt> translator, for instance, this prevents access to port 22: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -c /dev/eth0f /hurd/eth-filter -i /dev/eth0 -r "not port 22" -</pre></td></tr></table> - -<p> -The filtered device, <tt>/dev/eth0f</tt>, can then be given to <tt>pfinet</tt> -or <tt>dhclient</tt> instead of /dev/eth0. -</p> - - -<h3> Keyboard layout </h3> - -<p> -The layout of the keyboard can be configured through the standard -<code>keyboard-configuration</code> package. Make sure that it is installed, and -run <code>dpkg-reconfigure keyboard-configuration</code>. Only the layout is -supported, variants are not (yet). The effect will not -be immediate, as the console needs to be restarted to take the parameter into -account. Rebooting should be fine for instance. -</p> - -<h3> Other File Systems </h3> - -<p> -Next, edit <tt><q>/etc/fstab</q></tt> to add any additional filesystems as well as -swap space. It is <em>very important</em> that swap space be used; the Hurd -will be an order of magnitude more stable. Note that the Hurd can transparently -share a swap partition with Linux but will happily page to any device including -a raw partition such as your home partition. By default, <code>nano</code> and <code>vi</code> are -the only editors installed by the base distribution. -</p> - -<p> -Here is an example <tt><q>/etc/fstab</q></tt> file: -</p> - -<table><tr><td> </td><td class=example><pre> -\# <file system> <mount point> <type> <options> <dump> <pass> -/dev/hd0s1 / ext2 rw 0 1 -/dev/hd0s2 /home ext2 rw 0 2 -/dev/hd0s3 none swap sw 0 0 -</pre></td></tr></table> - -<p> -If any <code>/dev</code> device entry is missing, remember to create it using the <code>MAKEDEV</code> command: -</p> - -<table><tr><td> </td><td class=example><pre> - \# cd /dev - \# ./MAKEDEV hd0s1 hd0s2 hd0s3 -</pre></td></tr></table> - -<p> -You can also mount a filesystem by hand by calling <code>settrans</code>: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans /mnt /hurd/ext2fs /dev/hd0s5 -</pre></td></tr></table> - -<p> -The idea behind this command is that you set on the <code>/mnt</code> node the -<code>/hurd/ext2fs /dev/hd0s5</code> translator. <code>/hurd/ext2fs</code> will -get executed and start read/writing <code>/dev/hd0s5</code> and show its content -on <code>/mnt</code>. More information can be found in the -<a href="hurd-doc-translator">Translator documentation</a>. -</p> - -<p> -To mount an nfs filesystem, <code>/hurd/nfs</code> translator is used. When -run as non-root, the translator will connect to the server using a port above -1023. By default, GNU/Linux will reject this. To tell GNU/Linux to accept -connections originating from a non-reserved port, add the -<q><var>insecure</var></q> option to the export line. Here is an example -<tt><q>/etc/exports</q></tt> file assuming the client's ip address is -<tt><q>192.168.1.2</q></tt>: -</p> - -<table><tr><td> </td><td class=example><pre> - /home 192.168.1.2(rw,insecure) -</pre></td></tr></table> - -<p> -To mount this from a GNU box and assuming that nfs server's ip address is -<tt><q>192.168.1.1</q></tt>: -</p> - -<table><tr><td> </td><td class=example><pre> -\# settrans -cga /mount/point /hurd/nfs 192.168.1.1:/home -</pre></td></tr></table> - - -<h2> Have fun with Debian GNU/Hurd </h2> - -<p> -Now, what nice things can we do with the Hurd? -</p> - -<h3> Mount disk images </h3> - -<p> -Accessing the content of a CD image is a bit tedious with standard Unix systems -if you are not root. On GNU/Hurd, it amounts to this: -</p> - -<table><tr><td> </td><td class=example><pre> -settrans ~/mnt /hurd/iso9660fs CD_image.iso -</pre></td></tr></table> - -<p> -And it is completely safe: the <code>iso9660fs</code> translator is running -under your identity, not root. You can even code your own translator for any -kind of filesystem. Yes, this is like FUSE. Without all the kludge. -</p> - -<h3> Transparent FTP </h3> - -<p> -The following sets up a transparent <code>ftp</code> directory: -</p> - -<table><tr><td> </td><td class=example><pre> -settrans -c /ftp: /hurd/hostmux /hurd/ftpfs / -</pre></td></tr></table> - -<p> -Now, <code>cd</code> to e.g. <code>/ftp://ftp.gnu.org/</code>, and run <code>ls</code> there. -Yes, you can from your home simply run <code>tar xf ftp://ftp.gnu.org/pub/gnu/gcc/gcc-4.6.0/gcc-4.6.0.tar.bz2</code> ! -</p> - -<h3> Sub-Hurd </h3> - -<p> -A <a href="https://www.gnu.org/software/hurd/hurd/subhurd.html">sub-Hurd</a> is a -complete subsystem. Very much like virtualization containers on first -sight. Except that you do not need to be root at all to run one. -</p> - -<h3> gdb ext2fs, pfinet, ... </h3> - -<p> -Yes, you can run gdb on e.g. the ext2fs implementation, the <code>pfinet</code> TCP/IP stack, etc. -</p> - -<h3> And many more things! </h3> - -<p> -Some in-progress work include <code>mboxfs</code>, <code>tarfs</code>, <code>xmlfs</code>, <code>gopherfs</code>, ... -</p> - -#<h3> 7.3 Rebooting </h3> -# -#<p> -#Finally, reboot into multiuser mode, i.e. in the same way single user mode was -#brought up minus the <q><var>-s</var></q> option when loading the kernel. For -#details, see section 5. Booting GNU/Hurd. -#</p> -# -#<p> -#Happy Hacking! -#</p> - -<h2>Final Words </h2> - -<p> -The following are just install-time quickies, make sure to also read -documentation for the installed system: the <a href=hurd-doc>Debian GNU/Hurd documentation</a>, -but also the <a href=http://hurd.gnu.org/>Upstream website</a>. -</p> - - -#<h3> 8.1 The Grub Menu </h3> -# -#<p> -#Having to always load the kernel by hand can be very tedious. Edit the -#<tt><q>/boot/grub/menu.lst</q></tt> for Grub1 or -#<tt><q>/boot/grub/grub.cfg</q></tt> for Grub2 and tailor it appropriately; -#booting will become much quicker and easier. -#</p> -# -# -#<h3> 8.2 Adding Devices </h3> -# -#<p> -#By default, only a few devices are created in the <tt><q>/dev</q></tt> directory. -##Use the <code>MAKEDEV</code> script to create any needed device nodes. -#</p> - -<h3><a name=morepackages> Installing More Packages </a></h3> - -<p> -There are several ways to add packages. Downloading and using -<code>dpkg -i</code> works but is very inconvenient. The easiest method -is to use <code>apt-get</code>. -</p> - -<p> -If you have used the Debian GNU/Hurd 2021 release, the safest -way is use the snapshot of this release, by creating a file -<code>/etc/apt/apt.conf.d/99ignore-valid-until</code> containing -</p> - -<table><tr><td> </td><td class=example><pre> -Acquire::Check-Valid-Until "false"; -</pre></td></tr></table> - -<p> -And then the snapshot can be used as apt source: edit -<tt><q>/etc/apt/sources.list</q></tt>, add the following unreleased entry. -</p> - -<table><tr><td> </td><td class=example><pre> -deb http://snapshot.debian.org/archive/debian-ports/20210812T100000Z/ sid main -deb-src http://snapshot.debian.org/archive/debian/20210812T100000Z/ sid main -deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20210812T100000Z/ unreleased main -</pre></td></tr></table> - -<p> -Update, install the <code>debian-ports-archive-keyring</code> package, and update again, you now have the -full Debian GNU/Hurd 2021 release available. -</p> - - -<p> -If you have used a snapshot later than the 2021 release, you can add these -sources to get the most recent packages: -</p> - -<table><tr><td> </td><td class=example><pre> -deb http://deb.debian.org/debian-ports unstable main -deb-src http://deb.debian.org/debian unstable main -deb http://deb.debian.org/debian-ports unreleased main -</pre></td></tr></table> - -<p> -Update, install the <code>debian-ports-archive-keyring</code> package, and -update again. -</p> - -<p> -If when doing your first <code>apt-get</code>, <code>dpkg</code> complains of -missing programs, get root in a login shell (i.e. <code>su -</code>, not just -<code>su</code>). -</p> - -<p> -If GNU Mach does not recognize your network card or you use a modem, the only -way to upgrade will be to download the packages and then transfer them to the -GNU system. The easiest way to do this is to use apt off-line. Refer to -<tt><q>/usr/share/doc/apt-doc/offline.text.gz</q></tt> for detailed instructions. -</p> - - -<h3>The Hurd console</h3> - -<p> -Besides the Mach console you encountered during installation, the GNU/Hurd -features a powerful user-space console providing virtual terminals. -If you have installed in pseudo-graphical mode, it should be started -automatically at boot, otherwise you can start it manually with the following -command: -</p> - -<table><tr><td> </td><td class=example><pre> - \# console -d vga -d pc_mouse --repeat=mouse -d pc_kbd --repeat=kbd -d generic_speaker -c /dev/vcs -</pre></td></tr></table> - -<p> -If it is confirmed to be working, it can be enabled at boot from -<tt>/etc/default/hurd-console</tt>: turn <tt>ENABLE="false"</tt> into -<tt>ENABLE="true"</tt>. -</p> - -<p> -Inside the Hurd console, you can switch between virtual terminals via -<kbd>ALT+F1</kbd>, <kbd>ALT+F2</kbd> and so on. <kbd>ALT+CTRL+BACKSPACE</kbd> detachs -the Hurd console and brings you back to the Mach console, from where you -can reattach again with the above command. -</p> - - -<h3>X.Org </h3> - -<p> -X.Org has been ported and all video cards, which it supports that do not -require a kernel module or drm should work. -</p> - -<p> -You need to already be running the Hurd console and have repeaters setup as -indicated in the previous section. For instance, check that <code>echo -$TERM</code> prints <code>hurd</code>, and check that <code>/dev/cons/kbd</code> -and <code>/dev/cons/mouse</code> exist. -</p> - -<p> -You need to run <tt>dpkg-reconfigure x11-common xserver-xorg-legacy</tt> to allow any user to start -Xorg, because the X wrapper does not know about the Hurd and Mach consoles. -</p> - -<p> -You also need to create a <tt>/etc/X11/xorg.conf</tt> to enable the control-alt-backspace shortcut: -</p> - -<table><tr><td> </td><td class=example><pre> -Section "InputDevice" - Identifier "Generic Keyboard" - Driver "kbd" - Option "XkbOptions" "terminate:ctrl_alt_bksp" -EndSection -</pre></td></tr></table> - -<p> -It may happen that for some reason Xorg chooses a 16/9 resolution but a 4/3 desktop size. Blame Xorg, not the Hurd :) To avoid the issue, append this to <tt>/etc/X11/xorg.conf</tt> : -</p> - -<table><tr><td> </td><td class=example><pre> -Section "Screen" - Identifier "myScreen" - SubSection "Display" - Virtual 1024 768 - EndSubSection -EndSection -</pre></td></tr></table> - -<p> -You will need several X packages. <code>xorg</code>, -<code>rxvt</code> and a window manager: <code>twm</code>, <code>icewm</code>, <code>openbox</code>, ... -are a good start. If you want X to get started at boot, you have to install a -display manager. <code>lightdm</code> and <code>gdm</code> do not work yet, but -<code>xdm</code> should just work fine. -</p> - -<p> -Finally, run <code>startx /usr/bin/yourwm</code> -</p> - -<p> -If that doesn't work, as mentioned by the error message, look in <tt>/var/log/Xorg.0.log</tt> (or post it to the list for people to have a look). -</p> - -<h3>Upgrading your System</h3> - -<p> -If you are using a Debian release snapshot, you will not have any upgrade -available, since the released distribution is frozen at the release date. -<b>This means you will not get security updates!</b> You may rather want to -enable the unstable distribution as described in section -<a href=#morepackages>Installing More Packages</a>. -</p> - -<p> -Once you have enabled the unstable distribution, note that since this is -unstable, it is affected by library transition hickups, so do not be surprised -that it will sometimes not be able to upgrade some packages. Generally, you can -use the recommended Debian upgrade procedure: first use -</p> - -<table><tr><td> </td><td class=example><pre> -\# apt upgrade --without-new-pkgs -</pre></td></tr></table> - -<p>to upgrade what can be without changing the list of packages, and then use</p> - -<table><tr><td> </td><td class=example><pre> -\# apt full-upgrade -</pre></td></tr></table> - -<p>to upgrade the rest.</p> - -<p>Note: if you very seldomly upgrade your system, you may hit upgrade -issues. Make sure to first upgrade to the latest release snapshot (Hurd 2021, -see section <a href=#morepackages>Installing More Packages</a>) before upgrading -from the unstable distribution.</p> - -<h3>Last words</h3> - -<p> -To shutdown your system, simply use <code>halt</code>, <code>poweroff</code> or <code>reboot</code>. If that happens to sometimes hang because some daemon is not terminating properly, you can use instead <code>halt-hurd</code>, <code>poweroff-hurd</code>, <code>reboot-hurd</code>, which don't actually shut down daemons, but properly sync data to disk. -</p> diff --git a/greek/ports/hurd/hurd-news.wml b/greek/ports/hurd/hurd-news.wml deleted file mode 100644 index 7dc9ac47872..00000000000 --- a/greek/ports/hurd/hurd-news.wml +++ /dev/null @@ -1,433 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="b913c6c68c2f0764dc42c375ce0fc712fe6f2d1f" maintainer="galaxico" - -<h1>News about Debian GNU/Hurd</h1> - -<h3><:=spokendate ("2021-08-14"):></h3> - -<p>Debian GNU/Hurd 2021 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2021</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"Bullseye" release (August 2021), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/11.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -70% of the Debian archive, and more to come!</p> - -<ul> -<li>The port of go is complete</li> -<li>Support for file record locking was added</li> -<li>Some parts of experimental APIC, SMP and 64bit support was added</li> -<li>Userland IRQ delivery was reworked</li> -<li>An experimental rump-based userland disk driver was introduced. This - means dropping the Linux glue from the GNU Mach kernel is getting - very close!</li> -<li>Many fixes, including some important security fixes.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2019-07-07"):></h3> - -<p>Debian GNU/Hurd 2019 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2019</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"buster" release (July 2019), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/10.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -80% of the Debian archive, and more to come!</p> - -<ul> -<li>An ACPI translator is available, it is currently only used to shut down the -system.</li> -<li>The LwIP TCP/IP stack is now available as an option.</li> -<li>A PCI arbiter has been introduced, and will be useful to properly manage PCI -access, as well as provide fine-grain hardware access.</li> -<li>Support for LLVM was introduced.</li> -<li>New optimisations include protected payloads, better paging management and -message dispatch, and gsync synchronization.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2017-06-18"):></h3> - -<p>Debian GNU/Hurd 2017 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2017</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"stretch" release (May 2017), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/9.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -80% of the Debian archive, and more to come!</p> - -<ul> -<li>The core GNU Hurd and GNU Mach packages were updated to versions 0.9 and - 1.8, respectively. Besides numerous other improvements, they bring vastly - improved stability under memory load and prolonged uptime.</li> -<li>The native fakeroot tool has been greatly improved, allowing to be used for - building packages, making that quite faster and safer.</li> -<li>It is now possible to run subhurds as unprivileged user, thus providing easy -lightweight virtualization.</li> -<li>The supported memory size was extended beyond 3GiB.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2015-04-25"):></h3> - -<p>Debian GNU/Hurd 2015 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2015</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"jessie" release (April 2015), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/8.0/hurd-i386/">Debian Ports</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with more -than 80% of the Debian archive, and more to come!</p> - -<p>Since the last snapshot release coinciding with "wheezy", the init system has been -switched to sysvinit for a more Debian-like experience. Further changes since -the last snapshot include:</p> - -<ul> -<li>The core GNU Hurd and GNU Mach packages were updated to versions 0.6 and - 1.5, respectively. Besides numerous other improvements, they bring vastly - improved stability under load and prolonged uptime.</li> -<li>The networking drivers were migrated to user-space drivers using the NetDDE - framework and a Linux-2.6.32 codebase.</li> -</ul> - -<p> -Notable new or upgraded packages which required considerable porting effort and/or -are known to work well on Debian GNU/Hurd include Iceweasel 31 ESR, Xfce 4.10, -X.org 7.7 and Emacs 24.4. -</p> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2013-05-21"):></h3> - -<p>Debian GNU/Hurd 2013 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2013</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the Debian -"wheezy" release (May 2013), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/7.0/hurd-i386/">Debian Ports</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd.</p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with more than 75% of the Debian archive, and more to come!</p> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a>, -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>Due to the very small number of developers, -our progress of the project has not been as fast as other successful -operating systems, but we believe to have reached <a -href="https://www.gnu.org/software/hurd/hurd/status.html">a very decent -state</a>, even with our limited resources. </p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>over the past -decades</a>. There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2011-06-11"):></h3> - -<p>Various bugs of the debian-installer based image were fixed, there is no -known issue except that GNOME and KDE are not installable yet.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2011-02-15"):></h3> - -<p>The debian-installer based image was updated to squeeze d-i packages.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2010-09-01"):></h3> - -<p>A debian-installer based image is available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2009-10-19"):></h3> - -<p>The L1 DVD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2007-12-21"):></h3> - -<p>The K16 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2007-11-19"):></h3> - -<p>The K15 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2006-11-27"):></h3> - -<p>The K14 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2006-04-26"):></h3> - -<p>The K11 CD mini image is now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2005-10-26"):></h3> - -<p>The K10 CD and DVD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2005-05-14"):></h3> - -<p>The K9 CD Images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2004-12-30"):></h3> - -<P>The K8 CD Images are now available. These Images support Filesystems bigger -than 2 GB and feature an update of the network device drivers.<br/> -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2004-03-06"):></h3> - -<P>After a long time of not being updated, new CVS snapshots of <a -href="https://tracker.debian.org/pkg/hurd">the Hurd</a> and <a -href="https://tracker.debian.org/pkg/gnumach">GNU Mach</a> are uploaded.</p> - -<h3><:=spokendate ("2003-07-31"):></h3> - -<P>The K4 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2003-04-30"):></h3> - -<P>The K3 CD images are now available. -They have been renamed to GNU-K3-CDx.iso <br> -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - - -<h3><:=spokendate ("2003-03-06"):></h3> - -<P>The K2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2002-10-10"):></h3> - -<P>The J2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - - -<P>Upgrading Debian GNU/Hurd from a libio-based system before -2002-08-12 (including J1 CD series). - -<P>Updating a Debian GNU/Hurd system in August 2002 requires to follow -the procedure outlined in the <A HREF="extra-files/hurd-upgrade.txt">upgrade -manual</A>. This update procedure is necessary because the Hurd -interfaces went through an incompatible change to prepare support of -long files. - -<h3><:=spokendate ("2002-08-05"):></h3> - -<P>The J1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2002-02-26"):></h3> - -<P>The H3 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-12-15"):></h3> - -<P>The H2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-11-11"):></h3> - -<P>The H1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-10-05"):></h3> - -<P>The G1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-08-07"):></h3> - -<p> -Today is the first time we crossed the 40% mark in the <a -href="https://buildd.debian.org/stats/graph.png">statistic about -up-to-date packages</a> per architecture.</p> - -<h3><:=spokendate ("2001-07-31"):></h3> - -<P>The F3 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-07-12"):></h3> - -<p>Marcus Brinkmann has made available his presentation about the hurd. -It is currently available from:</p> -<a href="http://www.marcus-brinkmann.de/talks.en.html">http://www.marcus-brinkmann.de/talks.en.html</a> - -<h3><:=spokendate ("1999-11-01"):></h3> - -<p> -Cleaned up some outstanding bug reports which were closed by now. Going to -upload some more packages, in addition to those uploaded in the last days -(inetutils, grub, man-db, now coming hostname, mtools, ...). All those now -compile without any changes, which is a good thing. Seems we are slowly -stabilizing the basic set of packages.</p> - -<h3><:=spokendate ("1999-09-29"):></h3> - -<p> -There are <a -href="ftp://alpha.gnu.org/gnu/hurd/contrib/marcus/">patches to glue -Linux character devices into GNU Mach</a> now. These patches are very -experimental, and the tty driver does not work correctly with the term -translator, but we are working on it and hope to be able to provide a -binary soon. Note that this will bring the Linux console to the Hurd -(including color and virtual consoles), as well as drivers for various -non standard mice and other serial devices.</p> - -<p> -I heard that some people are concerned about the size of GNU Mach, as -well as it becoming a subset of Linux. Please note that we are only -searching for a temporary solution here, until we have the time to -redesign the driver interface in GNU Mach (or use another -Microkernel). The microkernel is not at all that important as the Hurd -servers are which run on top of it.</p> - -<p> -On the package side, we have now a proper <code>shadow</code> package -(which produces <code>passwd</code> (thanks, BenC!)). Also, -<code>man-db</code> should work out of the box now even with long -filenames, but I haven't checked the other changes. All in all, the -base section is getting into a good shape. Torin has applied my patch -for <code>perl</code>, and that's another package I have to check out -if it can be `finalized' now.</p> - -<h3><:=spokendate ("1999-08-31"):></h3> - -<p> -<code>debianutils 1.12</code> does now compile without patch.</p> - -<h3><:=spokendate ("1999-08-05"):></h3> - -<p> -Source NMU for <code>passwd</code> (<code>shadow</code>) should fix -all remaining problems in this package. This should make for a -smoother install. On the other side, <code>mutt</code> requires a -small patch.</p> - -<h3><:=spokendate ("1999-07-27"):></h3> - -<p> -New packages of the core system are finished now. The Hurd has a new -way to boot (the part that happens after init is started), take a look -at <code>/libexec/runsystem</code>. This is useful for the -<code>sysvinit</code> package, which is almost done. Fixed a buglet in -GNU Lib C and one in GNU Mach. Autodetection of all network cards -should work now, but maybe we need to tweak the order a bit (3c5x9 -before 3c59x).</p> - -<h3><:=spokendate ("1999-07-22"):></h3> - -<p> -<code>cpio 2.4.2-25</code> fixes the remaining Hurd compatibility issue -and can now be compiled without changes. Thanks Brian!</p> - -<h3><:=spokendate ("1999-07-05"):></h3> - -<p> -Perl 5.005.03 patches submitted to the maintainer. The upstream code -was already clean (thanks, Mark!), but the Debian packaging scripts -were linux specific.</p> diff --git a/greek/ports/i386/Makefile b/greek/ports/i386/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/i386/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/i386/index.wml b/greek/ports/i386/index.wml deleted file mode 100644 index 0af2351dba4..00000000000 --- a/greek/ports/i386/index.wml +++ /dev/null @@ -1,22 +0,0 @@ -#use wml::debian::template title="Debian GNU/Linux on x86 Machines" BARETITLE=true -#use wml::debian::translation-check translation="e9c587fe48386f2bedf1d5a6284b6959c2b4635c" maintainer="galaxico" - -<p>Being the first architecture supported by Debian, -most of the general Debian web pages apply to this port.</p> - -<p>There is some information specific to this architecture, however, that we -will list here.</p> - -<h2>Installing</h2> - -<p>If you wish to install Debian, you should look at the -<a href="$(HOME)/releases/stable/i386/">installation instructions</a> -whether you are installing from a CD or downloading off the -Internet.</p> - -<h2>Development</h2> - -<p> -The build servers for this architecture are operated by -<a href="https://dsa.debian.org/">DSA</a>. -</p> diff --git a/greek/ports/ia64/Makefile b/greek/ports/ia64/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/ia64/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/ia64/index.wml b/greek/ports/ia64/index.wml deleted file mode 100644 index ef761bc7faa..00000000000 --- a/greek/ports/ia64/index.wml +++ /dev/null @@ -1,64 +0,0 @@ -#use wml::debian::template title="IA-64 Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/ia64/menu.inc" -#use wml::debian::translation-check translation="09225985e5d001870fb942c6fb74704fe3fc552a" maintainer="galaxico" - -<h1>Debian for IA-64</h1> - -<h2>Status</h2> - -<p> -IA-64 was a supported Debian architecture from Debian 3.0 (woody) to Debian 7 (wheezy) - -<p> -If you would like to help, start by subscribing to the -<a href="#mailinglist">debian-ia64 mailing list</a>. - -<p> -The normal Debian channels for acquiring installation media and documentation -include ia64 CD images. - -<h2>BIOS Versions</h2> - -<p> -All modern ia64 systems should work fine. -<p> -It's possible that you may find a very early ia64 machine that needs a BIOS -upgrade to work well with Linux. -One particular combination we've heard about is trying to run new -kernels on "Lion" systems with really old BIOS versions. -To try to make this easier, -here's what we know about BIOS versions that work well for Debian on older -ia64 systems: - -<ul> -<li> Lion, aka HP rx4610, version 99b works well. -<li> BigSur, aka HP i2000, version 130 works well. -</ul> - -<p> -Firmware downloads for -<a href="http://www.hp.com">HP</a> -systems are available starting -<a href="http://welcome.hp.com/country/us/eng/software_drivers.htm"> HERE </a>. -</p> - -<p> -If anyone has information about suitable BIOS versions for other IA-64 systems -that are successfully running Debian, let us know on the debian-ia64 list! </p> - -<h2>Contacts</h2> - -<p> -The instigators of the IA-64 port were Bdale Garbee and Randolph Chung. -The best way to ask questions now is via the mailing list. - -<h2><a name="mailinglist">Mailing List</a></h2> - -<p> -To subscribe to the mailing list for this port, send a message containing -the word "subscribe" as the subject to -<email "debian-ia64-request@lists.debian.org"> to sign up, or use the -<a href="https://lists.debian.org/debian-ia64/">list web page</a>. -You can also browse and search the -<a href="https://lists.debian.org/debian-ia64/">list archive</a>. -</p> diff --git a/greek/ports/ia64/news.wml b/greek/ports/ia64/news.wml deleted file mode 100644 index 85a7e17a8c2..00000000000 --- a/greek/ports/ia64/news.wml +++ /dev/null @@ -1,74 +0,0 @@ -#use wml::debian::template title="IA-64 Port -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/ia64/menu.inc" -#use wml::debian::translation-check translation="f832fa04df640fc3eba2bdbd0d92b593c3b68afd" maintainer="galaxico" - -<h1>News about Debian for IA-64</h1> - -<h3><:=spokendate ("2003-03-04"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -A new installation CDROM image is now available. This version uses a -2.4.19 020821.1 kernel. This kernel includes all the storage and network -drivers required to install on every ia64 system Bdale has access to. -Enjoy! -<a href="http://gluck.debian.org/ia64/ia64-net-20030304.iso">HTTP</a>. - -<h3><:=spokendate ("2002-05-06"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -The ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 has been freshened to the kernel and "boot floppies" versions that -we expect to be included in the Debian 3.0 (woody) release. Enjoy! -<a href="http://gluck.debian.org/ia64/ia64-net-20020506.iso">HTTP</a>. - -<h3><:=spokendate ("2002-01-28"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -The ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 has been freshened to a version from early December that works well -on the systems we have access to. -<a href="http://gluck.debian.org/ia64/ia64-base-20011202-rc1.iso.gz">HTTP</a>. - -<h3><:=spokendate ("2001-08-10"):></h3> - -<p><strong>Installer CD image published</strong> - -<p> -An ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 is now available via -<a href="http://gluck.debian.org/ia64/cd-20010810.iso.gz">HTTP</a>. - -<h3><:=spokendate ("2001-08-06"):></h3> - -<p><strong>Debian accepts ia64 for release with Debian 3.0 (woody)!</strong> - -<p> -It is with great pleasure that we announce the acceptance of ia64 as an -architecture for the upcoming Debian 3.0 stable release, codename woody. -Installation tools for ia64 are now in the woody tree, and packages now in -unstable are beginning to be promoted to the testing/woody tree. - -<h3><:=spokendate ("2001-07-24"):></h3> - -<p><strong>Official Request to Release with Debian 3.0 (woody)</strong> - -<p> -Approximately 70% of all Debian packages are built and up to date in the -archives, an automated build system is running smoothly, installation tools -are available in the archive, and the number of systems running is growing -rapidly. - -<h3><:=spokendate ("2001-01-16"):></h3> - -<p><strong>First Native Boot</strong> - -<p> -Debian booted on IA-64 natively for the first time, after development in a -chroot environment on top of a TurboLinux base install. - diff --git a/greek/ports/kfreebsd-gnu/Makefile b/greek/ports/kfreebsd-gnu/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/kfreebsd-gnu/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/kfreebsd-gnu/index.wml b/greek/ports/kfreebsd-gnu/index.wml deleted file mode 100644 index 71d328728c2..00000000000 --- a/greek/ports/kfreebsd-gnu/index.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::template title="Debian GNU/kFreeBSD" -#use wml::debian::translation-check translation="6f3adf6374f35194686f89dec2ba66b1ecf3bb5f" maintainer="galaxico" - -#use wml::debian::toc - -<toc-display/> - -<p>Debian GNU/kFreeBSD is a port that consists of -<a href="https://www.gnu.org/">GNU userland</a> using the -<a href="https://www.gnu.org/software/libc/">GNU C library</a> on top of -<a href="https://www.freebsd.org/">FreeBSD</a>'s kernel, coupled with the -regular <a href="https://packages.debian.org/">Debian package set</a>.</p> - -<div class="important"> -<p>Debian GNU/kFreeBSD is not an officially supported -architecture. It has been released with Debian 6.0 (Squeeze) and 7.0 -(Wheezy) as a <em>technology preview</em> and the first non-Linux -port. Since Debian 8 (Jessie) it is though no more included in official -releases.</p> -</div> - -<toc-add-entry name="resources">Resources</toc-add-entry> - -<p>There's more information about the port (including an FAQ) in the -<a href="https://wiki.debian.org/Debian_GNU/kFreeBSD">Debian GNU/kFreeBSD</a> -wiki page. -</p> - -<h3>Mailing lists</h3> -<p><a href="https://lists.debian.org/debian-bsd">Debian GNU/k*BSD mailing list</a>.</p> -<h3>IRC</h3> -<p><a href="irc://irc.debian.org/#debian-kbsd">#debian-kbsd IRC channel</a> (at irc.debian.org).</p> - -<toc-add-entry name="Development">Development</toc-add-entry> - -<p>Because we use Glibc the portability problems are very simple and most times it's -just a matter of copying a test case for "k*bsd*-gnu" from another Glibc-based -system (like GNU or GNU/Linux). Look at the -<a href="https://salsa.debian.org/bsd-team/web/raw/master/porting/PORTING">porting</a> -document for details.</p> - -<p>Also look at the <a href="https://salsa.debian.org/bsd-team/web/raw/master/TODO">TODO</a> -file for more details on what needs to be done.</p> - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> - -<p>lemon.debian.net (kfreebsd-amd64) is -available to Debian developers for porting work. Please see the -<a href="https://db.debian.org/machines.cgi">machine database</a> for more -information about these machines. In general, you will be able to use the -two chroot environments: testing and unstable. Note that these systems -are not administrated by DSA, so <b>do not send requests to debian-admin -about it</b>. Instead use <email "admin@lemon.debian.net">.</p> diff --git a/greek/ports/m68k/Makefile b/greek/ports/m68k/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/m68k/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/m68k/index.wml b/greek/ports/m68k/index.wml deleted file mode 100644 index efee34d5b4e..00000000000 --- a/greek/ports/m68k/index.wml +++ /dev/null @@ -1,141 +0,0 @@ -#use wml::debian::template title="Motorola 680x0 Port" NOHEADER="yes" -#use wml::debian::toc -#use wml::debian::translation-check translation="821d2af3a565be7b911813a3fb1a5543be4391e6" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian on Motorola 680x0</toc-add-entry> - -<p>The Motorola 680x0 series of processors have powered personal -computers and workstations since the mid-1980s. Debian currently runs -on the 68020, 68030, 68040 and 68060 processors: this is an unofficial port -meaning that there's not an official and released m68k port any more but -this port is under development.</p> - -<p>Please note that a -<a href="https://foldoc.org/memory+management+unit"> -memory management unit (MMU)</a> is -<em>required</em>; this rules out the "EC" variants of these -processors. Floating-point emulation is available; however, it is not -functional on some mac models due to a bug in some revisions of the 68LC040 -processor. (68LC040 processors in other subarchitectures are fine; only -Macintoshes appear to have been shipped with the broken 68LC040 -processors).</p> - -<toc-add-entry name="status">Status</toc-add-entry> - -<p>The Debian m68k port was first officially released with Debian 2.0 -(hamm) and was an official port until Debian 4.0 (etch). There's now an effort -to revive this port.</p> - -<p>Currently, the Debian/m68k port supports Atari, Amiga, VMEbus, and some -Macintosh systems.</p> - -<p>For further information on the current status of the m68k port, please -visit our <a href="https://wiki.debian.org/M68k/Status">wiki page</a>.</p> - -<p>Help is always needed and welcome! In particular, kernels and boot -images supporting other ports of <a href="http://www.linux-m68k.org/">\ -the Linux/m68k kernel</a>, like the Q40/Q60 and Sun 3, would be nice.</p> - -<p>If you're willing to help, we maintain TODO lists on <a -href='https://wiki.debian.org/'>the Debian wiki</a> for <a -href='https://wiki.debian.org/M68k/Porting'>the Debian/m68k system</a> and -<a href='https://wiki.debian.org/DebianInstaller/M68k'>The Debian-installer -port to the m68k architecture</a>.</p> - - -<p>The <a href="http://unstable.buildd.net/index-m68k.html">Debian/68k autobuild -system</a> contains up to date information about the porting effort. -In case of questions and/or problems related to the autobuild system -please contact <email "debian-68k@lists.debian.org" /> with a subject tag of -"[buildd]".</p> - -<toc-add-entry name="credits">Credits</toc-add-entry> - -<p> -This is a list of people who are working on the Debian/m68k project. -It also includes some significant contributors who have "moved on" to -other things. Let us know if you're missing from this list! - -<dl> - -<dt>Frank Neumann -<dd> -Launched m68k port of Debian. - -<dt>Martin "Joey" Schulze -<dd> -Provided infrastructure at Infodrom for "kullervo", the primary build -daemon, to be connected to the Internet. Also helped organize Linux -hacker meetings at Oldenburg. - -<dt>Roman Hodek -<dd> -With James Troup, created <tt>buildd</tt>, the automated build daemon -for the m68k port. buildd is now used by other architectures, too. - -<dt>James Troup -<dd> -Wrote <tt>quinn-diff</tt> and other utilities to automate package building. - -<dt>David Huggins-Daines -<dd> -Maintained m68k support on the boot-floppies team. Also supports the <a -href="http://www.mac.linux-m68k.org/">upstream Mac kernel</a>. - -<dt>Michael Schmitz -<dd> -Built and tested the installation system for 2.1. - -<dt>Christian T. Steigies -<dd> -Maintains Debian/68k kernel packages. - -<dt>Stephen R. Marenka -<dd> -Together with Wouter Verhelst, ported debian-installer (the installation -system for Debian 3.1 and above) to the m68k architecture. - -<dt>Wouter Verhelst -<dd> -Together with Stephen Marenka, ported debian-installer (the installation system -for Debian 3.1 and above) to the m68k architecture. - -<dt>Thorsten Glaser -<dd> -Collected patches from Debian/m68k maintainers, Linux m68k developers, and -other people; brought Debian/m68k through the transition from linuxthreads to -NPTL with TLS by integrating those into the Debian packages and being the -human equivalent of a buildd for long enough to bootstrap Sid again. -Finn Thain, Andreas Schwab and Geert Uytterhoeven provided valuable input to -this, besides those already mentioned above. - -</dl> - - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p> -The mailing list for this project is <email "debian-68k@lists.debian.org" />. -To subscribe, send a message containing the word "subscribe" as the subject -to <email "debian-68k-request@lists.debian.org" />, or use the -<a href="https://lists.debian.org/debian-68k/">mailing list web page</a>. -You can also browse and search -<a href="https://lists.debian.org/debian-68k/">the list archives</a>. - -<p>The m68k porters' mailing list used to be at <email -"m68k-build@nocrew.org"/>. This also used to be the contact address for -the m68k autobuild system. However, to contact m68k porters today, the -preferred procedure is to use debian-68k@lists.debian.org with a subject -tag of [buildd].</p> - -<p>Please send comments about these web pages to -<a href="mailto:debian-68k@lists.debian.org">the Debian/m68k mailing -list</a>.</p> - -<toc-add-entry name="links">Links</toc-add-entry> - -<p> -A dedicated page gather some <a href="links">links related to the m68k port</a>. -</p> diff --git a/greek/ports/m68k/links.wml b/greek/ports/m68k/links.wml deleted file mode 100644 index 00848aab106..00000000000 --- a/greek/ports/m68k/links.wml +++ /dev/null @@ -1,39 +0,0 @@ -#use wml::debian::template title="Motorola 680x0 Port -- Links" NOHEADER="yes" -#use wml::debian::translation-check translation="534d1b782cfb92f46dc41fd064f779fffc329b12" maintainer="galaxico" - - -<h1>Links about Linux on Motorola 680x0</h1> - -<ul> -<li><a href="http://www.linux-m68k.org/">The Linux/m68k Home -Pages</a>: support site for the Linux kernel on 680x0 hardware, -regardless of distribution. - -<li>The <a href="http://www.linux-m68k.org/faq/faq.html">Linux/m68k -FAQ</a> and <a -href="http://www.us.linux-m68k.org/cgi-bin/faqw.py?req=home">Linux/m68k -FAQ Wizard</a>. The FAQ Wizard will eventually replace the "old" FAQ; -in the meantime, you'll need to refer to the old FAQ where the FAQ -Wizard is incomplete. - -<li>The <a href="http://www.linux-m68k.org/Registry/">Linux/m68k User -Registry</a>, a rough "counter" of how many people use Linux/m68k. - -<li><a href="http://www.mac.linux-m68k.org/">Linux/m68k for the -Macintosh Project</a> - -<li>Installation guides for <a -href="http://www.linux-m68k.org/debian-amiga.html">Amigas</a>, <a -href="http://www.linux-m68k.org/debian-atari.html">Ataris</a>, <a -href="http://www.linux-m68k.org/debian-mac.html">Macs</a> and <a -href="http://www.linux-m68k.org/debian-vme.html">VMEbus</a> machines. - -<li>Christian Steigies has written <a -href="https://people.debian.org/~cts/debian-m68k-faq/">a page</a> with the -"Number One FAQ" for Debian/m68k: how to get X running. Please read -it before asking why your X11 isn't working! - -<li>The <a href="$(HOME)/CD/vendors/">Debian CD vendors</a> listing, -showing who sells CD-ROMs with Debian for m68k platforms. - -</ul> diff --git a/greek/ports/mips/Makefile b/greek/ports/mips/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/mips/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/mips/index.wml b/greek/ports/mips/index.wml deleted file mode 100644 index 830beedbb4e..00000000000 --- a/greek/ports/mips/index.wml +++ /dev/null @@ -1,133 +0,0 @@ -#use wml::debian::template title="MIPS Port" -#use wml::debian::translation-check translation="821d2af3a565be7b911813a3fb1a5543be4391e6" maintainer="galaxico" - -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::toc - -<toc-display/> - -<toc-add-entry name="about">Overview</toc-add-entry> -<p>The MIPS port is actually two ports, <em>debian-mips</em> and -<em>debian-mipsel</em>. They differ in the <a -href="https://foldoc.org/endian">endianness</a> -of the binaries. MIPS CPUs are able to run at both endiannesses, but -since that's normally not changeable in software, we need to have both -architectures. SGI machines run in <a -href="https://foldoc.org/big-endian">big-endian</a> -mode (debian-mips) while the Loongson 3 machines run in -<a -href="https://foldoc.org/little-endian">little-endian</a> -mode (debian-mipsel). Some boards, such as Broadcom's BCM91250A evaluation -board (aka SWARM) can run in both modes, selectable by a switch on the board. -Some Cavium Octeon based machines can switch between both modes in the -bootloader.</p> - -<p>Given most MIPS machines have 64-bit CPUs, a <em>debian-mips64el</em> port -is currently in development and might be released with Debian GNU/Linux 9.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>Debian GNU/Linux <current_release_jessie> supports the following machines:</p> - -<ul> - -<li>SGI Indy with R4x00 and R5000 CPUs, and Indigo2 with R4400 CPU (IP22).</li> - -<li>SGI O2 with R5000, R5200 and RM7000 CPU (IP32).</li> - -<li>Broadcom BCM91250A (SWARM) evaluation board (big and little-endian).</li> - -<li>MIPS Malta boards (big and little-endian, 32 and 64-bit).</li> - -<li>Loongson 2e and 2f machines, including the Yeelong laptop (little-endian).</li> - -<li>Loongson 3 machines (little-endian).</li> - -<li>Cavium Octeon (big-endian).</li> - -</ul> - -<p>In addition to the above machines, it is possible to use Debian on a lot more -machines provided that a non-Debian kernel is used. This is for example the -case of the MIPS Creator Ci20 development board.</p> - -<toc-add-entry name="info">General Information about</toc-add-entry> - -<p>Please see the <a href="$(HOME)/releases/stable/mips/release-notes/">\ -release notes</a> and <a href="$(HOME)/releases/stable/mips/">\ -installation manual</a> for more information.</p> - - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> - -<p>Two machines are made available to Debian developers for MIPS porting -work: etler.debian.org (mipsel/mips64el) and minkus.debian.org (mips). -The machines have development chroot environments which you can access -with <em>schroot</em>. Please see the -<a href = "https://db.debian.org/machines.cgi"> machine database</a> for more -information about these machines.</p> - - -<toc-add-entry name="credits">Credits</toc-add-entry> - -<p>This is a list of people who are working on the MIPS port:</p> - -#include "$(ENGLISHDIR)/ports/mips/people.inc" - -<toc-add-entry name="contacts">Contacts</toc-add-entry> - -<h3>Mailing lists</h3> - -<p>There are a couple of mailing lists dealing with Linux/MIPS and especially -Debian on MIPS.</p> - -<ul> - -<li>debian-mips@lists.debian.org — This list deals with Debian on MIPS.<br /> -Subscribe via mail to <email debian-mips-request@lists.debian.org>.<br /> -The archive is at <a href="https://lists.debian.org/debian-mips/">lists.debian.org</a>.</li> - -<li>linux-mips@linux-mips.org — This list is for discussions about -MIPS kernel supports.<br /> -See the <a href = "https://www.linux-mips.org/wiki/Net_Resources#Mailing_lists">Linux/MIPS</a> -page for subscription information.</li> - -</ul> - -<h3>IRC</h3> - -<p>You can find us on IRC on <em>irc.debian.org</em> on the channel -<em>#debian-mips</em>.</p> - - -<toc-add-entry name="links">Links</toc-add-entry> - -<dl> - <dt>Linux/MIPS kernel development — Lots of related information about MIPS</dt> - <dd><a href="https://www.linux-mips.org/">linux-mips.org</a></dd> - <dt>CPU Vendor</dt> - <dd><a href="https://imgtec.com/mips">https://imgtec.com/mips</a></dd> - <dt>Information about SGI hardware</dt> - <dd><a href="http://www.sgistuff.net/hardware/">http://www.sgistuff.net/hardware/</a></dd> - <dt>Debian on SGI Indy</dt> - <dd><a href="http://www.pvv.org/~pladsen/Indy/HOWTO.html">http://www.pvv.org/~pladsen/Indy/HOWTO.html</a></dd> - <dt>Debian on SGI Indy</dt> - <dd><a href="https://nathan.chantrell.net/linux/sgi-indy-and-debian-linux/">https://nathan.chantrell.net/linux/sgi-indy-and-debian-linux/</a></dd> - <dt>Debian on SGI O2</dt> - <dd><a href="https://cyrius.com/debian/o2/">http://www.cyrius.com/debian/o2</a></dd> -</dl> - - -<toc-add-entry name="thanks">Thanks</toc-add-entry> - -<p>The porterboxes and most of the build servers for the <em>mips</em> and -<em>mipsel</em> architectures are provided by <a href="https://imgtec.com"> -Imagination Technologies</a>.</p> - - -<toc-add-entry name="dedication">Dedication</toc-add-entry> - -<p>Thiemo Seufer, who was the lead MIPS porter in Debian, got killed in a -car accident. We <a href = -"$(HOME)/News/2008/20081229">dedicate the release</a> of the -Debian GNU/Linux <q>lenny</q> distribution to his memory.</p> - diff --git a/greek/ports/netbsd/Makefile b/greek/ports/netbsd/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/netbsd/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/netbsd/index.wml b/greek/ports/netbsd/index.wml deleted file mode 100644 index de8e3ebffac..00000000000 --- a/greek/ports/netbsd/index.wml +++ /dev/null @@ -1,134 +0,0 @@ -#use wml::debian::template title="Debian GNU/NetBSD" BARETITLE="yes" NOHEADER="yes" -#use wml::fmt::verbatim -#use wml::debian::translation-check translation="c9a7e0f78250fe2fea728e669907c9ee47374e1c" maintainer="galaxico" - -############################################################################# -<div class="important"> -<p><strong> -This porting effort has long been abandoned. It has had no updates since October -2002. The information in this page is only for historical purposes. -</strong></p> -</div> - -<h1> -Debian GNU/NetBSD -</h1> - -<p> -Debian GNU/NetBSD (i386) was a port of the Debian Operating System to the -NetBSD kernel and libc (not to be confused with the other Debian BSD ports -based on glibc). At the time it was abandoned (around October 2002), it was -in an early stage of development - however, it was installable from scratch. -</p> - -<p> -There was also an attempt to start a Debian GNU/NetBSD (alpha) port, which -could be run from a chroot in a native NetBSD (alpha) system, but was not -able to boot of its own, and was using most of the native NetBSD libraries. -A <a -href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200201/msg00203.html">status -message</a> was sent to the list. -</p> - -<h2>Historical News</h2> - -<dl class="gloss"> - <dt class="new">2002-10-06:</dt> - <dd> - Experimental install floppies are now available for installing - a Debian GNU/NetBSD system. - </dd> - <dt>2002-03-06:</dt> - <dd> - Matthew hacked <a href="https://packages.debian.org/ifupdown">ifupdown</a> - in a workable state. - </dd> - <dt>2002-02-25:</dt> - <dd> - Matthew has reported that shadow support and PAM works on NetBSD - now. <a href="https://packages.debian.org/fakeroot">fakeroot</a> - seems to work on FreeBSD, but still has issues on NetBSD. - </dd> - <dt>2002-02-07:</dt> - <dd> - Nathan has just <a - href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00091.html">reported</a> - that he got Debian GNU/FreeBSD to boot multiuser. Also, he's - working on a packages-only install (using a hacked debootstrap) - featuring a considerably smaller tarball. - </dd> - <dt>2002-02-06:</dt> - <dd> - According to Joel gcc-2.95.4 passed most of its test-suite and - is packaged. - </dd> - <dt>2002-02-06:</dt> - <dd>X11 works on NetBSD! Again, kudos to Joel Baker - </dd> - <dt>2002-02-04:</dt> - <dd>First step towards a Debian/*BSD archive: <br /> - <a href="mailto:lucifer@lightbearer.com">Joel Baker</a> - <a href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00067.html"> - announced</a> a <kbd>dupload</kbd>able archive for FreeBSD and - NetBSD Debian packages. - </dd> - <dt>2002-02-03:</dt> - <dd>Debian GNU/NetBSD now - <a href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00043.html"> - self-hosting</a>! Note that it still needs a working NetBSD for - installation. - </dd> - <dt>2002-01-30:</dt> - <dd>The Debian GNU/*BSD port now has a webpage!</dd> -</dl> - -<h2>Why Debian GNU/NetBSD?</h2> - -<ul> -<li>NetBSD runs on hardware unsupported by Linux. Porting Debian to -the NetBSD kernel increases the number of platforms that can run a -Debian-based operating system.</li> - -<li>The Debian GNU/Hurd project demonstrates that Debian is not tied -to one specific kernel. However, the Hurd kernel was still relatively -immature - a Debian GNU/NetBSD system would be usable at a production -level.</li> - -<li>Lessons learned from the porting of Debian to NetBSD can be used -in porting Debian to other kernels (such as those of <a -href="https://www.freebsd.org/">FreeBSD</a> and <a -href="https://www.openbsd.org/">OpenBSD</a>).</li> - -<li>In contrast to projects like <a href="https://www.finkproject.org/">Fink</a>, -Debian GNU/NetBSD did not exist in order to provide extra software or a -Unix-style environment to an existing OS (the *BSD ports trees are already -comprehensive, and they unarguably provide a Unix-style environment). -Instead, a user or administrator used to a more traditional Debian system -would feel comfortable with a Debian GNU/NetBSD system immediately and -competent in a relatively short period of time.</li> - -<li>Not everybody likes the *BSD ports tree or the *BSD userland (this -is a personal preference thing, rather than any sort of comment on -quality). Linux distributions have been produced which provide *BSD -style ports or a *BSD style userland for those who like the BSD user -environment but also wish to use the Linux kernel - Debian GNU/NetBSD -is the logical reverse of this, allowing people who like the GNU -userland or a Linux-style packaging system to use the NetBSD -kernel.</li> - -<li>Because we can.</li> -</ul> - -<h2> -Resources -</h2> - -<p> -There is a Debian GNU/*BSD mailing list. Most of the historic discussions -about this port happened there, which are accessible from the web archives at -<url "https://lists.debian.org/debian-bsd/" />. -</p> - -## Local variables: -## sgml-default-doctype-name: "HTML" -## End: diff --git a/greek/ports/powerpc/Makefile b/greek/ports/powerpc/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/powerpc/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/powerpc/devel.wml b/greek/ports/powerpc/devel.wml deleted file mode 100644 index 31f632e223d..00000000000 --- a/greek/ports/powerpc/devel.wml +++ /dev/null @@ -1,15 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Development" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<br> -<br> - -<p>For more up-to-date information on Debian PowerPC port development, please -contact us on the <a href="https://lists.debian.org/debian-powerpc/"> -debian-powerpc</a> mailing list. - -<ul> -<li> <a href="https://buildd.debian.org/stats/">The PowerPC Autobuilder Status Pages</a> -<li> <a href="https://buildd.debian.org/quinn-diff/output/unstable/by_section-powerpc/index.html">The Quinn-Diff List</a> -</ul> diff --git a/greek/ports/powerpc/docu.wml b/greek/ports/powerpc/docu.wml deleted file mode 100644 index 0e4313db058..00000000000 --- a/greek/ports/powerpc/docu.wml +++ /dev/null @@ -1,76 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="e7b0e9e8622d110f19021682096b635ff8d35735" maintainer="galaxico" - -<h2> Documents & Information </h2> - -<h3> OpenFirmware, FirmWorks and PPCBug Documents </h3> -<ul> - <li> <a href="http://til.info.apple.com/techinfo.nsf/artnum/n60285"> OpenFirmware (Apple) </a> </li> - <li> <a href="http://www.firmworks.com/"> FirmWorks </a> </li> - <li> <a href="http://playground.sun.com/pub/1275/"> OpenFirmware (Sun) </a> </li> - <li> <a href="http://www.linuxppc.org/userguide/of.html"> OpenFirmware (Page 1) </a> </li> - <li> <a href="http://www.linuxppc.org/userguide/old_install.html#bv"> OpenFirmware (Page 2)</a> </li> - <li> <a href="http://www.linuxppc.org/userguide/output_dev.html"> Videomodes </a> </li> - <li> PPCBug -- no URL available </li> -</ul> - -<h3> General Information on Installation and Processor/Microcontroller </h3> -<ul> - <li> <a href="https://www.ibm.com/it-infrastructure/power"> IBM (RS/6000) </a> </li> - <li> <a href="http://www.dartmouth.edu/cgi-bin/cgiwrap/jonh/lppc/faq.pl?file=572"> Conversion from Red Hat/LinuxPPC to Debian/PowerPC </a> </li> - <li> <a href="http://www.mot.com/PowerPC/"> PowerPC </a> </li> - <li> <a href="http://www-3.ibm.com/chips/techlib/techlib.nsf/products/PowerPC_604e_Microprocessor"> PowerPC 604e </a> </li> -# <li> <a href="http://www.mklinux.apple.com"> MkLinux </a> </li> - <li> <a href="http://www.dartmouth.edu/cgi-bin/cgiwrap/jonh/lppc/faq.pl"> FAQ-O-Matic </a> </li> -</ul> - -<h3> Motorola Documentation </h3> -<ul> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/index.html"> Motorola Scripts (Table of Contents) </a> </li> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/manuals/pem32b.pdf"> The PEM </a> </li> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/manuals/PRG.pdf"> The PRG </a> </li> -</ul> - -<h3> ISDN Installation </h3> -<p> - The Elsa PCI ISDN card doesn't work currently. ISA cards should be fully functional. -</p> -<ul> - <li> <a href="http://www.hrz.uni-wuppertal.de/zugang/netzanschluss/isdn4l/linux_isdn-2.html"> ISDN Installation </a> </li> -</ul> - -<h3> Beowulf/Clustering </h3> -<ul> - <li> <a href="http://metalab.unc.edu/mdw/HOWTO/Parallel-Processing-HOWTO-2.html"> Parallel-Processing </a> </li> - <li> <a href="http://www.scl.ameslab.gov/Projects/ClusterCookbook/"> Cluster-Processing </a> </li> - <li> <a href="http://source.rfc822.org/pub/local/cluster/"> Pics, movies, ... </a> </li> -</ul> - -<h2>News and Other Information</h2> - -<h3> News </h3> -<ul> - <li> <a href="http://penguinppc.org/">PenguinPPC</a> </li> - <li> <a href="http://www.macosrumors.com/">Mac OS Rumors</a> </li> - <li> <a href="https://slashdot.org/">Slashdot</a> </li> -# <li> <a href="http://www.corplinux.com/powerpenguin">PowerPenguin</a> </li> -</ul> - -<h3> Info </h3> -<ul> - <li> <a href="https://www.linuxjournal.com/"> Linux Journal </a> </li> - <li> <a href="http://www.eet.com/story/OEG19990512S0025">Nintendo (1)</a> </li> - <li> <a href="http://www.chips.ibm.com/news/1999/gekko/index.html">Nintendo (2)</a> </li> - <li> <a href="http://www.opensource.apple.com/projects/darwin/">Darwin Project</a> </li> - <li> <a href="http://www.MacKiDo.com/Hardware/">The MacKiDo Info Pages (Hardware)</a> </li> - <li> <a href="http://www.maconlinux.org/">Mac-on-Linux (MOL)</a> </li> -</ul> - - - - - - - - diff --git a/greek/ports/powerpc/history.wml b/greek/ports/powerpc/history.wml deleted file mode 100644 index dcce86df2c1..00000000000 --- a/greek/ports/powerpc/history.wml +++ /dev/null @@ -1,78 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- History" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="70cf45edbaeb4b8fc8f99d683f2f5c5c4435be92" maintainer="galaxico" - -<br> -<br> - -<h1>Debian/PowerPC History</h1> - -<p> - The PowerPC port started in 1997 after the German <a - href="http://www.linux-kongress.org/">Linux Kongress</a> in - Würzburg where the Debian project was sponsored a <a - href="http://www.infodrom.north.de/Infodrom/tervola.html">PowerPC</a> - for development issues. -</p> - -<p> - Fortunately working boot- and rootdisks were found at <a - href="http://www.linuxppc.org/">LinuxPPC</a> and we could try to - install something on the machine. Unfortunately this required - some programs that only run under Mac OS. The only way to install - them was to get another machine running Mac OS who has them already - installed. Since data exchange with other non-Mac OS machines were - only able through msdos-formatted floppies this was a chicken-and-egg - problem. -</p> - -<p> - Somehow we managed to hook another disk to the machine and - installed Linux on it. That was Apple's famous DR 1. Suddenly we - begun to port dpkg and friends to the new system. Wow, that was - possible. It was impressive how the first packages were ported - and built. Unfortunately DR one didn't come with a dynamic linker - and shared libraries. Another problem was that the libraries and - header files seemed to be somewhat outdated and we weren't able to - compile a new libc out of the box. However, the biggest and most - serious problem were these suspicious crashes that also screwed - the file systems entirely. Fixable only by re-installations. -</p> - -<p> - Klee Dienes, another Debian Developer, worked on this problem and - suddenly came up with a <a - href="ftp://ftp.infodrom.north.de/pub/Linux/linux-pmac/debian/mklinuxfs.tar.gz">mklinux tarball</a> - of a more recent system - a haxored Debian GNU/Linux. This - tarball came with an old 1.99 version of libc. From this time the - machine run stable on the network and we could continue our - effort. We were compiling a lot of packages and noticed that some - header files were not proper and that many programs were not - compilable by the regular compiler. -</p> - -<p> - So Joel Klecker, a new Debian Developer at that time, started to - work on egcs and it's compilation on the PowerPC machine. After - this was done the next step was to work on current libc versions. - It turned out that our libc-1.99 version is incompatible to the next - pre2.1 version that was needed in order to move the port into a - stable state. -</p> - -<p> - At this stage Hartmut Koptein switched over from m68k to the powerpc - port and started development for it. Development versions of - Debian/PowerPC were available in 1998 and 1999. -</p> - -<p> - The port was officially released for the first time with Debian GNU/Linux - 2.2 ("potato"), in August 2000. -</p> - -<p> - The development of the port continues. A build daemon has been set up - on voltaire.debian.org, - a PowerPC machine donated by Daniel Jacobowitz, also a Debian developer. -</p> diff --git a/greek/ports/powerpc/index.wml b/greek/ports/powerpc/index.wml deleted file mode 100644 index 4a6e5ef85ad..00000000000 --- a/greek/ports/powerpc/index.wml +++ /dev/null @@ -1,202 +0,0 @@ -#use wml::debian::template title="PowerPC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::toc -#use wml::debian::translation-check translation="bd1362b966297f3e701c0512bd20e9497fda943e" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian for PowerPC</toc-add-entry> - -<p> -<img src="pics/ppc750.jpg" alt="PPC-750 picture" class="rightico"> - The PowerPC is a <a href="https://en.wikipedia.org/wiki/Reduced_instruction_set_computer">\ - RISC</a> microprocessor architecture - developed by <a href="https://www.ibm.com/it-infrastructure/power">IBM</a>, - Motorola (now <a href="http://www.freescale.com/">Freescale</a>) and <a - href="https://www.apple.com/">Apple</a>. The PowerPC architecture allows both - 64-bit and 32-bit implementations (the 64-bit implementation includes - the 32-bit implementation). The first PowerPC microprocessor was the - 601, a 32-bit implementation released in 1992. Several other 32-bit - implementations have since been released, including the 603, 604, 750 - (G3), 7400 (G4) and the PowerQUICC embedded communications - processors. 64-bit implementations include the 620, POWER4, POWER5 - and the 970 (G5). -</p> - -<p> - Linux for the PowerPC was first released at the 2.2.x version of - the kernel. A key resource for PowerPC Linux development is <a - href="http://penguinppc.org/">penguinppc</a>, which also includes - a hardware compatibility list. PowerPC support in the - Linux kernel is now developed as part of the `main' Linux kernel at - <a href="https://www.kernel.org/">kernel.org</a>. -</p> - -<p> - The Debian PowerPC port began in 1997 at the <a href="http://www.linux-kongress.org/"> - German Linux Congress</a> in Würzburg. - <a href="http://www.infodrom.north.de/Infodrom/tervola.html">A - PowerPC machine</a> (Motorola StarMax 4000, 200 MHz 604e) was donated to - the Debian project. Additional information about this computer is available - from <a href="history">the history page</a>. -</p> - -<toc-add-entry name="powerpc">Debian on 32-bit PowerPC (powerpc)</toc-add-entry> - -<p> -It first became an official <q>release architecture</q> with Debian -GNU/Linux 2.2 (<q>potato</q>) and had retained that status until the publication -of Debian 9 (<q>stretch</q>). The last supported release for 32-bit PowerPC is Debian 8 (<q>jessie</q>). - -See the <a href="$(HOME)/releases/jessie/powerpc/release-notes/">\ -release note</a> and <a href="$(HOME)/releases/jessie/powerpc/">\ -installation manual</a> for further information. -</p> - -<toc-add-entry name="ppc64el">Debian on 64-bit Little Endian PowerPC (ppc64el)</toc-add-entry> -<p> -Starting on the release of Debian 8 (<q>jessie</q>), ppc64el is an officially -supported architecture on Debian. - -See the <a href="$(HOME)/releases/stable/ppc64el/release-notes/">\ -release note</a> and <a href="$(HOME)/releases/stable/ppc64el/">\ -installation manual</a>. -</p> - -<p> -Here you can find information about the -<a href="https://en.wikipedia.org/wiki/Ppc64">64-bit PowerPC</a> -<a href="https://en.wikipedia.org/wiki/Endianness">Little Endian</a> -architecture. -</p> -<p> -However, note that there is also information at the -<a href="https://wiki.debian.org/ppc64el">ppc64el wiki</a> page, such as -installation and ABI information. -</p> - -<toc-add-entry name="installation">Installation</toc-add-entry> - -<p> - There are a variety of systems using the PowerPC - microprocessor. Check our <a href="inst/install">Installation</a> pages - for specific information about installing Debian/PowerPC on your system. -</p> - - -<p> - There are some quirks you need to know about when installing on an - iBook, TiBook, or iBook2, especially when dual booting with Mac - OS X. Some iBook2 hardware, especially on recently introduced models, - is not well supported as yet. For specific information on potential - problems and solutions, study these web pages: -</p> - -<ul> -<li>William R. Sowerbutts' <a - href="http://www.sowerbutts.com/linux-mac-mini/">Installing - Debian GNU/Linux on the Mac Mini</a></li> -<li>Mij's <a href="http://mij.oltrelinux.com/ibook/ppc_linux.html">\ - Hints on installing debian on an iBook2</a></li> -<li><a href="http://seb.france.free.fr/linux/ibookG4/iBookG4-howto.html">\ - Installing Debian GNU/Linux on an iBook 3.3 (G4)</a> by Sébastien FRANÇOIS</li> -<li><a href="https://lists.debian.org/debian-powerpc/2002/07/msg00858.html">\ - Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO</a> by Rolf Brudeseth</li> -<li> Installing Debian GNU/Linux on a p630 LPAR (7028-6C4) - <a - href="https://web.archive.org/web/20080625231946/http://people.debian.org/~fmw/p630-LPAR-Debian-en.txt">English</a> - and <a - href="https://web.archive.org/web/20080916213451/http://people.debian.org/~fmw/p630-LPAR-Debian-de.txt">German</a> - (Florian M. Weps)</li> -<li>Daniel DeVoto's <a href="http://ppcluddite.blogspot.de/2012/03/installing-debian-linux-on-ppc-part-i.html">\ -Installing Debian Wheezy/testing on an iBook G3</a></li> -</ul> - -<p> - Debian GNU/Linux does not officially support NuBus PowerPC - machines, such as the 6100, 7100, 8100 and most of the Performa - series. However, an MkLinux-based kernel is available, which can be - launched from a Mac OS boot loader. A Debian system can be installed - using this kernel, which is available at - <url "http://nubus-pmac.sourceforge.net/">. -</p> - -<p> - When upgrading from Potato to Woody or upgrading really old kernels, - there is some <a href="keycodes">important information</a> you should - be aware of regarding a change in keyboard coding. This could save - you some time and headaches! -</p> - -<toc-add-entry name="docs">Links - Documentation</toc-add-entry> - -<p>Up-to-date information on Linux for PowerPC is at -<a href="http://penguinppc.org/">PenguinPPC</a>. -We have an <a href="docu">older collection of PowerPC links</a> and -a couple of <a href="devel">pointers</a> for Debian PowerPC developers.</p> - -<p>Hardware specifications for Apple computers are available at -<a href="https://support.apple.com/specs">AppleSpec</a>.</p> -<p> -More information and documentation about the POWER architecture: -</p> -<ul> -<li><a href="https://www-03.ibm.com/technologyconnect/tgcm/TGCMServlet.wss?alias=OpenPOWER"> -Official ELFv2 ABI Specification</a> (under section 'Link') -or this -<a href="https://www-03.ibm.com/technologyconnect/tgcm/TGCMFileServlet.wss/ABI64BitOpenPOWER_21July2014_pub.pdf?id=B81AEC1A37F5DAF185257C3E004E8845"> -PDF</a>. Registration required. </li> -<li><a href="https://gcc.gnu.org/wiki/cauldron2014#Slides_and_Notes">GNU Tools -Caldron 2014</a> slides & video</li> -</ul> - -<toc-add-entry name="availablehw">Available Hardware for Contributors</toc-add-entry> - -<p> Please read the <a href="https://db.debian.org/machines.cgi">list of -Debian machines</a> to access powerpc/ppc64el Debian porterboxen. -</p> - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p>If you need help, try asking for help in the following places:</p> - -<h3>Mailing Lists</h3> - -<p>The Debian PowerPC mailing list is the proper place for questions, -suggestions for improvements, or just for chat concerning PowerPC -systems running Debian. The debian-user list is also available for -general Debian questions which are not specific to PowerPC.</p> - -<p>To join the list, send e-mail to -<a href="mailto:debian-powerpc-request@lists.debian.org"> -<debian-powerpc-request@lists.debian.org></a> with the word -"subscribe" in the Subject line. -<a href="https://lists.debian.org/debian-powerpc/">List archives are -available</a>.</p> - -<h3>Usenet Newsgroups</h3> - -<p>Linux for PowerPC Systems</p> -<ul> - <li><a href="news:comp.os.linux.powerpc">comp.os.linux.powerpc</a></li> -</ul> - -<p>Linux in general</p> -<ul> - <li><a href="news:comp.os.linux.misc">comp.os.linux.misc</a></li> - <li><a href="news:comp.os.linux.networking">comp.os.linux.networking</a></li> - <li><a href="news:comp.os.linux.hardware">comp.os.linux.hardware</a></li> - <li><a href="news:comp.os.linux.x">comp.os.linux.x</a></li> -</ul> - -<h3>IRC</h3> - -<p>The <code>#debian</code> channel on <code>irc.debian.org</code> is -for general topics relating to Debian, and there is the -<code>#debianppc</code> channel for topics specific to Debian on -PowerPC processors. You will almost always find someone on-line who is -happy to share information and help you with your problem.</p> - -<hr /> - -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" diff --git a/greek/ports/powerpc/inst/Makefile b/greek/ports/powerpc/inst/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/powerpc/inst/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/powerpc/inst/apus.wml b/greek/ports/powerpc/inst/apus.wml deleted file mode 100644 index 09184ca3ead..00000000000 --- a/greek/ports/powerpc/inst/apus.wml +++ /dev/null @@ -1,226 +0,0 @@ -#use wml::debian::template title="PowerPC Port (APUS)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="a9738774706d265243f4d1b6f43b411f8536f5c8" maintainer="galaxico" - -<h1>Installing Debian GNU/Linux on a PowerPC APUS Machine</h1> - -<p> - -Apus is the "Amiga PowerUp System", and consists of an Amiga computer, -A1200, A3000 or A4000, together with one of the PowerPC/m68k -accelerator boards from the now dead company Phase5, the BlizzardPPC -or CyberStormPPC board. - -<h2>Known Problems</h2> -<p> - -There are some issues involved with bootstrap on systems which don't -use either PowerUp or WarpUp only, but some hybrid mutant of them -both. I am not very familiar with this stuff as I use plain powerup -only, so I hope someone will contribute a more complete description of -it. -<p> - -Also the SCSI controller of the CyberStormPPC is not yet supported by -Linux, so you cannot use disks attached to it. - -<h2>Partitioning from the AmigaOS side</h2> -<p> - -<code>amiga-fdisk</code> is the fdisk variant for RDB partition tables -used by the Amiga hardware. It is working, but I recommend you use the -Amiga partitioning tools to do it from AmigaOS instead. -<p> - -HDToolbox, being the official Commodore partitioning tool, should be -installed on every AmigaOS system. Just launching HDToolbox should -partition the IDE disk of the onboard IDE interface. If you want to -access the SCSI disk on your BlizzardPPC board SCSI controller, you -should use the "hdtoolbox blizzppcscsi.device" command. -<p> - -Another option is to use SCSIConfig, the partitioner from Phase5 which -is on the floppies that came with your accelerator board. -<p> - -You will need to set the partition type to custom, and provide the -following partition type IDs: -<pre> - * Linux partition: 0x4c4e5800 - * Linux swap partition: 0x53575000 -</pre> - -<h2>Bootstrap</h2> -<p> - -You will find the <code>bootstrap</code> program in the -<code>apus/bootstrap</code> directory of the powerpc boot floppies -distribution (found at /debian/dists/woody/main/disks-powerpc/current). -<p> - -The <code>bootstrap</code> program consists of three programs. All -three need to be executable and in your AmigaOS path. They are the -<code>bootstrap</code> executable and the ppcboot_wup or ppcboot_pup -part, that is the actual launcher (ppcboot_pup for the powerup system -and ppcboot_wup for the warpup system). -<p> - -You will launch <code>bootstrap</code> with a line like this: -<pre> -\# bootstrap --apus "kernel options" -</pre> -where "kernel options" are defined in the following sections. -<p> - -<code>bootstrap</code> will then give some output, then blank the -screen for 10 to 30 seconds, and then you will have the Linux console. - -<h3>The Debian <code>bootstrap</code> Command</h3> -<p> - -The actual <code>bootstrap</code> command to launch the Debian -installer system would be: -<pre> -\# bootstrap --apus -k apus/linux -r apus/images-1.44/root.bin root=/dev/ram -</pre> -After installation, to launch Debian, use: -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 -</pre> -where sda3 is my Debian root partition, change it to the partition -that is hosting your root partition. - - -<h2>Kernel Options</h2> -<p> -You will need to add some kernel options depending on your actual -configuration, which will be explained in the following sections. - -<h3>Graphic Card Options</h3> -<p> - -The graphic device to be used is an option prefaced with video=. Some -examples are shown below. To enable the native graphics in vga mode -(640x480): -<pre> - video=amifb:vga -</pre> -To enable the Bvision/CyberVision graphic card in 1152x864 at 60Hz mode, -with the SUN12x22 fonts: -<pre> - video=pm2fb:mode:1152x864-60,font:SUN12x22 -</pre> - -To disable one of the graphic devices: -<pre> - video=amifb:disable -</pre> -You can map virtual consoles to the different devices being used. Use -<tt> - video=map:01 -</tt> -to map virtual console (vc) 1 to device 0, vc 2 to device 1, and after -that repeat the same pattern (vc3 to device 0, vc4 to device 1, etc.). -To map vc 1,2,3,5,6,7 to device 0 and vc 4,8 to device 1 you would use -<pre> - video=map:0001 -</pre> - - -<h3>The nobats Option</h3> -<p> - -Blizzard users with scsi disks will need to use the "nobats" option. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 nobats -</pre> - -<h3>The 60nsram Option</h3> -<p> -People with 60ns ram can also use the 60nsram option. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 60nsram -</pre> - -<h3>Debugging Options</h3> -<p> -If you are experiencing problems, you can use the debug option to -specify console message output to go to a serial console or memory -instead of the normal console. This is useful for debugging when the -kernel output doesn't come to the console output. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 60nsram debug=mem -</pre> -Then you can read the result with the bootmesg utility from the apus/bootstrap -directory. -<p> - -Another useful tool is the dmesg utility which will give you the bootstrap -process debugging info. - -<h2>Apus Particularities in <code>dbootstrap</code></h2> -<p> - -There are some specific differences for apus in the use of -<code>dbootstrap</code>. - -<h3>Partitioning the Hard Disk - <code>amiga-fdisk</code></h3> -<p> - -The apus subarch uses the <code>amiga-fdisk</code> partitioning tool. As noted -above, you can also use AmigaOS-side partitioning tools. - -<h3>Installing the OS Kernel and Modules</h3> -<p> - -This option is actually not working. I am in the process of proposing -an "Install the OS Modules" option to replace it, but in the meantime -you can just skip this step. The kernel is not needed anyway, since it -resides on the -# <!-- FIXME Sven?? server? network? --> - -<h3>Options Not Applicable for apus</h3> -<p> - -Well some options simply don't make sense on apus, so until I exclude them -from the menu, just ignore them. They should not work anyway. - -<p> -These options are: -<pre> -* Make System Bootable directly from the Hard Disk. - -* Make a Boot Floppy. - -* Eject the Floppy. -</pre> - -<h2>Links for Further Information</h2> -<p> - -The official Linux-apus doc and FAQ is at: -<p> -<a href="http://sourceforge.net/projects/linux-apus/"> -http://sourceforge.net/projects/linux-apus/</a> -<p> - -Another source of valuable information is the Linux-m68k web site and faq -found at: - -<p> -<a href="http://sourceforge.net/projects/linux-m68k/"> -http://sourceforge.net/projects/linux-m68k/</a> -<p> - -There you will find lots of information regarding Linux on the amiga platform -that is common to Linux-m68k and Linux-apus. - -<h2>Conclusion</h2> -<p> - -Well, this little guide tries to explain all the particularities of the -Linux-apus installation of Debian. The rest of it is quite similar to any -other Debian/powerpc installation, as well as the generic Debian installation. -You will thus find further info in the <a href="$(DOC)/">Debian documentation -directory</a> as well as in the other generic Linux information sites and -docs. diff --git a/greek/ports/powerpc/inst/chrp.wml b/greek/ports/powerpc/inst/chrp.wml deleted file mode 100644 index 41ea689d7ba..00000000000 --- a/greek/ports/powerpc/inst/chrp.wml +++ /dev/null @@ -1,23 +0,0 @@ -#use wml::debian::template title="PowerPC Port (CHRP)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="cf494cce15b1c5c14c9d7c7f2f6226e11abb143a" maintainer="galaxico" - -<h1 class="center">Debian GNU/Linux PowerPC CHRP Page</h1> - -<h2>Download</h2> - -To install Debian GNU/Linux 3.0 on a CHRP system download the following files:<br> -<br> -<ul> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/linux.bin">linux.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/rescue.bin">rescue.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-1.bin">driver-1.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-2.bin">driver-2.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/base-images-current/basedebs.tar">basedebs.tar</a></li> -</ul> - -<h2>Useful links</h2> - -<ul> -<li><a href="http://users.telenet.be/geertu/Linux/PPC/">CHRP System from Geert Uytterhoeven</a></li> -</ul> diff --git a/greek/ports/powerpc/inst/install.wml b/greek/ports/powerpc/inst/install.wml deleted file mode 100644 index 7a32dc2fdfc..00000000000 --- a/greek/ports/powerpc/inst/install.wml +++ /dev/null @@ -1,220 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Install " NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="70cf45edbaeb4b8fc8f99d683f2f5c5c4435be92" maintainer="galaxico" - -<h2> Debian GNU/Linux installation on PowerPC machines </h2> -<p> - Check the following pages for specific information about - installing Debian/PowerPC on your system: -</p> -<ul> - <li> <a href="apus">Amiga PowerUP System</a> </li> - <li> <a href="chrp">CHRP</a> </li> - <li> <a href="prep">PReP</a> </li> - <li> <a href="pmac">PowerMac</a> </li> -</ul> - <p> -There are four major supported <em>powerpc</em> flavors: -PMac (Power-Macintosh), Apus, CHRP and PReP machines. Ports to other -<em>powerpc</em> architectures, such as the Be-Box and MBX -architecture, are underway but not yet supported by Debian. We may -have a 64bit port in the future. - -<p> -There are also four flavours of the powerpc kernel in Debian. These -are based on the specific CPU type in use (and should not be confused -with the architecture flavours discussed above):</p> - -<div><dl> - -<dt>powerpc</dt> - -<dd><p> -Most systems use this kernel flavour, which supports the PowerPC 601, -603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh -systems up to and including the G4 use processors supported by this -kernel.</p></dd> - -<dt>power3</dt> - -<dd><p> -The POWER3 processor is used in older IBM 64-bit server systems: known -models include the IntelliStation POWER Model 265, the pSeries 610 and -640, and the RS/6000 7044-170, 7043-260, and 7044-270.</p></dd> - -<dt>power4</dt> - -<dd><p> -The POWER4 processor is used in more recent IBM 64-bit server systems: -known models include the pSeries 615, 630, 650, 655, 670, and 690. -The Apple G5 is also based on the POWER4 architecture, and uses this -kernel flavour.</p></dd> - -<dt>apus</dt> - -<dd><p> -This kernel flavour supports the Amiga Power-UP System. -</p></dd> - -</dl></div> - - <p> -Apple (and briefly a few other manufacturers - Power Computing, for -example) makes a series of Macintosh computers based on the PowerPC -processor. For purposes of architecture support, they are categorized -as Nubus, OldWorld PCI, and NewWorld. - <p> -Nubus systems are not currently supported by debian/powerpc. The -monolithic Linux/PPC kernel architecture does not have support for -these machines; instead, one must use the MkLinux Mach microkernel, -which Debian does not yet support. These include the 6100/7100/8100 -line of Power Macintoshes. - <p> -OldWorld systems are most Power Macintoshes with a floppy drive and a -PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are -OldWorld machines. The beige colored G3 systems are also OldWorld. - <p> -The so called NewWorld PowerMacs are any PowerMacs in translucent -colored plastic cases, all iMacs, iBooks, G4 and G5 systems. The -NewWorld PowerMacs are also known for using the `ROM in RAM' system -for Mac OS, and were manufactured from mid-1998 onwards. - -<p>Here is a list of powerpc machines which should work with Debian.</p> - -<table class="reltable"> -<colgroup span="2"> -<tr> - <th><strong>Model Name/Number</strong></th> - <th><strong>Architecture</strong></th> -</tr> -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Apple</strong></td> - <td></td> -</tr> - -<tr class="even"><td>iMac Bondi Blue, 5 Flavors, Slot Loading</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iMac Summer 2000, Early 2001</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iMac G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook, iBook SE, iBook Dual USB</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook2</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook G4</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh Blue and White (B&W) G3</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 PCI, AGP, Cube</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 Gigabit Ethernet</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 Digital Audio, Quicksilver</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 FireWire Pismo (2000)</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 Lombard (1999)</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G4 Titanium</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G4 Aluminum</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Mac mini</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Xserve G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td colspan="2"></td></tr> - -<tr class="even"><td>Performa 4400, 54xx, 5500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Performa 6300, 6360, 6400, 6500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 4400, 5400</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 7200, 7300, 7500, 7600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 8200, 8500, 8600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 9500, 9600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh (Beige) G3 Minitower</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh (Beige) Desktop, All-in-One</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerBook 2400, 3400, 3500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 Wallstreet (1998)</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Twentieth Anniversary Macintosh</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Workgroup Server 7250, 8550, 9650, G3</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Power Computing</strong></td> - <td></td> -</tr> - -<tr class="even"><td>PowerBase, PowerTower / Pro, PowerWave</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerCenter / Pro, PowerCurve</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>UMAX</strong></td> - <td></td> -</tr> - -<tr class="even"><td>C500, C600, J700, S900</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>APS</strong></td> - <td></td> -</tr> - -<tr class="even"><td>APS Tech M*Power 604e/2000</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Motorola</strong></td> - <td></td> -</tr> - -<tr class="even"><td>Starmax 3000, 4000, 5000, 5500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Firepower, PowerStack Series E, PowerStack II</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MPC 7xx, 8xx</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MTX, MTX+</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MVME2300(SC)/24xx/26xx/27xx/36xx/46xx</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MCP(N)750</td> <td><a href="prep">PReP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>IBM RS/6000</strong></td> - <td></td> -</tr> - -<tr class="even"><td>40P, 43P</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Power 830/850/860 (6070, 6050)</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>6015, 6030, 7025, 7043</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>p640</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>B50, 43-P150, 44P</td> <td><a href="chrp">CHRP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Genesi</strong></td> - <td></td> -</tr> - -<tr class="even"><td>Pegasos I, Pegasos II</td> <td><a href="chrp">CHRP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Amiga Power-UP Systems (APUS)</strong></td> - <td></td> -</tr> - -<tr class="even"><td>A1200, A3000, A4000</td> <td><a href="apus">APUS</a></td></tr> -</table> -<p> -Here is a list of machines which are not known to work with -Debian. They may well work, and we'd like to hear if you test one and -have some success. -</p> -<table class="reltable"> -<colgroup span="2"> -<tr> - <th><strong>Model Name/Number</strong></th> - <th><strong>Architecture</strong></th> -</tr> -<tr class="even"><td>IBM Longtrail II, First 'free' or 'open' PowerPC Board</td> <td><a href="chrp">CHRP</a></td></tr> -<tr class="even"><td>7248-100,7248-120,7248-132 </td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Notebook Thinkpad 820: 7247-821/822/823 </td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Notebook Thinkpad 850: 7247-851/860 </td> <td><a href="prep">PReP</a></td></tr> -</table> - - - - - - - - - - - diff --git a/greek/ports/powerpc/inst/pmac.wml b/greek/ports/powerpc/inst/pmac.wml deleted file mode 100644 index 7725f0b64e9..00000000000 --- a/greek/ports/powerpc/inst/pmac.wml +++ /dev/null @@ -1,91 +0,0 @@ -#use wml::debian::template title="PowerPC Port (PowerMac)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="b5617866ae4047b55b0439a5c5796df65590cec3" maintainer="galaxico" - -<h1 class="center">Debian GNU/Linux PowerPC PowerMac Page</h1> - -<p> -Here are some highlights of the PowerMac installation of Debian. For -detailed instructions, please study -<a href="$(HOME)/releases/stable/powerpc/">the fine Installation -Manual</a>. The -Debian Installer team have spent many long hours attempting to answer -your questions in advance and give you excellent written guidance as -you install Debian. -</p> - -<p> -It is certainly possible, and there are actually quite elegant -solutions for the NewWorld Macs, to dual boot your Debian PowerMac -system with Mac OS and/or Mac OS X. If you are planning on doing a new -installation of Mac OS X, though, do it before installing Debian. The -Mac OS X installer is very unkind to existing systems when it -installs. Shortly, you may also have the option of running Debian -within a Darwin system. -</p> - -<p> -The Debian installation uses a 2.6 series kernel. This kernel should -support most PowerMac hardware. A 2.4 series powerpc flavour kernel is -available for users with externally supplied modules that have not -been ported to 2.6 kernels. However, the use of this kernel is -strongly discouraged. -</p> - -<p> -You will need to partition your disk; Linux must be installed on its -own partition(s). If you have a single-disk system, that will entail -backing up everything on your system and restoring it after -partitioning is complete. Some third-party partitioning tools may be -able to 'shrink' a partition so you have room for more partitions on -your disk without destroying what's already there, but they will -undoubtedly advise a backup also. Drive Setup does not offer that -option, it erases the entire drive. -</p> - -<p> -1 GB is probably enough space for an experimental Linux system. You can -get by with less, perhaps as little as 400 MB for a really basic system, -but you'll more than likely want more than just the basics. -</p> - -<p> -After partitioning your disk, you will need to obtain an installation -CD or download the installer system. Once you finally sit down to do -the installation (preferably with installation manual in hand), you -will probably burn up 2 or 3 hours making it happen. An experienced -installer can get a basic install done in under half an hour. -</p> - -<p> -If you're really uncomfortable with command lines, then install the X -desktop after you've finished the basic system install. But give it a -second thought, too: there's a world of power in the Linux command -line. Some things that are very difficult to do in a graphical -interface are very fast and efficient on the command line. Also, since -the Linux system is command-line based, there are some functions which -are only accessible from the command line. The default system sets up -6 command line consoles, and one graphical one. You can get a lot of -work done in those other consoles while you're browsing the web... and -that way you can have the best of both worlds. -</p> - -<p> -The PowerPC platform runs really well with Linux. It's highly -respected in much of the Linux world. Enjoy, and remember to give -something back! -</p> - -<p> -For help with Quik on OldWorld Macs, see -<a href="http://penguinppc.org/bootloaders/quik/">\ -http://penguinppc.org/bootloaders/quik/</a> -</p> - -<p> -For detailed information on the various Mac models and in particular -info on working with OpenFirmware with any given model, check out the -<a href="http://www.netbsd.org/Ports/macppc/models.html">NetBSD -PowerPC Model list</a>. Since their installation requires one to get -OpenFirmware up first, they're the experts on that angle. -</p> diff --git a/greek/ports/powerpc/inst/prep.wml b/greek/ports/powerpc/inst/prep.wml deleted file mode 100644 index a040fb5f66b..00000000000 --- a/greek/ports/powerpc/inst/prep.wml +++ /dev/null @@ -1,209 +0,0 @@ -#use wml::debian::template title="PowerPC Port (PReP)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="baca2cc9eb45158bf723feec7aa48e19ee745253" maintainer="galaxico" - -<h1>Debian GNU/Linux PowerPC PReP Page</h1> - -<h3>Intro</h3> -<p> - - IBM and Motorola both make or have made PReP architecture - machines. At this point, the PReP support has only been tested on - Motorola legacy PowerStack(tm) (Blackhawk, Comet, Utah motherboard) - systems and the current embedded solution in the PowerPlus(tm) - family. These include the MTX, MTX+, - MVME2300(sc)/2400/2600/2700/3600/4600, and MCP(n)750. IBM produces a - variety of desktop workstation that are PowerPC PReP compliant. These - include the RS/6000 40P, 43P, 830, 850, 860, 6015, and 6030. - -</p> - -<h3>Known Problems</h3> -<p> -MTX+ (7 PCI slot MTX system) cannot boot the 2.2 kernel, it hangs on the IDE -driver initialization. This is a known problem and will be fixed in an -upcoming kernel patch. -</p> -<p> -All Motorola PowerPlus systems have broken IDE support in the kernel. -This problem has been identified and fixed. Changes will soon be available -as a Debian kernel patch package and will be rolled into the kernel -source. -</p> - -<h3>Firmware</h3> -<p> - -Depending on the age and/or maker of your PReP system you will have -either PPCBUG (Motorola), Open Firmware (IBM or Motorola), or IBM's -PReP firmware. The boot commands are slightly different but all of -these systems implement the PReP standard so the same kernel can be -booted on all platforms. A complete explanation of firmware commands -is out of the scope of this document but some information will be -provided where necessary. - -</p> - -<h3>Setup for Installation</h3> - -<h4>Floppy Based Install</h4> - -<p> -Write the <code>boot1440.bin</code>, <code>root1440.bin</code>, -<code>resc1440.bin</code>, <code>drv14-*.bin</code>, and -images to floppy disks. <code>dd</code> can -be used on a Linux/Unix system or <code>rawrite</code> can be used on -a DOS/Windows system. -</p> - -<h4>Network Based Install</H4> -<p> - -Place <code>resc1440.bin</code> and <code>drivers.tgz</code> files -into an exported NFS filesystem on your NFS server. It is best to -place the files as follows: -<code>/[mountpoint]/debian/[installfiles]</code> . -</p> - -<p> -Place the <code>boot.bin</code> file in the tftp directory on your TFTP server. -</p> - -<h4>Console Options</h4> -<p> -On Motorola PPCBUG systems you may boot and install using - either VGA console or serial console. PPCBUG and Linux will fall back to serial console - mode if no VGA or keyboard is detected. -</p> - -<p> -In order to properly view the installation on a serial console, some -terminal emulation capabilities are necessary. In order to see the -installation in color, it is necessary to have a terminal emulator with -support for ANSI color. The standard color xterm included with most -Linux distribution is sufficient, as are most terminal programs on -Windows (for example, <a -href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>). -In order to view the line drawing characters -that make the GUI boxes, it is essential that a font containing the IBM -extended line art character be used. Under Linux, the "linux8x8" font -can be used and under Windows one can select the MSLineDraw font. -</p> - - -<h3>Booting</h3> -<dl> -<dt> PPCBUG -<dd> Use the "ENV" command and turn on the "Network PReP boot enable" option. -<dd> Use the "NIOT" command to configure the client, server, and optional gateway IP addr - that will be used to tftp the kernel. If it is a brand new board, be sure to - <tt>SET <var><date/time></var></tt> to start the hwclock or networking and other things will not function. -<dt> Boot the image with -<dd> PPCBUG>NBO 0 0 ,,, bootprep.bin -<dt> OpenFirmware -<dt> Use the following command to tftp boot a PReP image: -<dd> >boot ‹server_ipaddr›,‹file›,‹client_ipaddr› -</dl> - - - -<h2>Debian Installation</h2> -<ol> -<li> Configure the keyboard -<p> - If on serial console, the configure keyboard step is skipped. -</p> - -<li> Partition the Harddrive -<p> -Create a primary partition of 2MB and change its type to PPC PReP boot -(type 41). OF PReP machines may have trouble booting if the PPC PReP boot -partition is anywhere other than primary partition 1. Although all the -Motorola PPCBUG systems can have PPC PReP boot located on any primary -partition, it is general practice to make the PPC PReP boot partition on -sda1 or hda1. -</p> -<p> -After the PPC PReP boot partition is created, follow the normal Linux -conventions for partitioning. At least a root and swap partition should -be created and they may be on either primary or logical partitions. -</p> - -<li> Install Rescue and Driver disks -<p> -Installing from floppy is straightforward, insert the rescue and driver -disks as you are prompted for them. -</p> -<p> -For a network based install, choose the NFS option and you will be -prompted to configure networking. When it prompts for the NFS server -to utilize, enter the NFS server and directory that you set up -earlier. Choose the defaults for the rest of the questions. -</p> - -<li> Configure Driver modules -<p> - For now, important modules are built in the kernel so just choose "Exit". -</p> - -<li> Install Base System -<p> -If a floppy install is selected, simply insert the base disks as requested. -If NFS install is selected, enter the NFS server and directory in -which the base system is located and choose the defaults to install -the Debian base system. -</p> - -<li> Make Bootable from Harddrive -<p> -Makes the system bootable from the PPC PReP boot partition that was -created earlier. If that partition is missing, an error will be displayed. -</p> - -<li> Make Boot Floppy -<p> -Writes a bootable image to a disk in the floppy drive. -</p> - -</ol> - -<h2>Debian Base System Boot</h2> -<p> - If you configured a type 41 PReP boot partition and had the installation - program make the system bootable from the hard drive then you can simply - issue a firmware boot command to have it boot from hard disk (PPCBUG and - OF both have autoboot options you may also turn on). -</p> -<p> -Note: to force the kernel to root from the correct partition, it may be -necessary to write to the PReP Global Environment variable, "bootargs". -In the case of a Motorola PReP installation which will default to root from -sda1 and where the root filesystem is actually on sda2, one must set -<tt>bootargs=/dev/sda2</tt> . -</p> - -<p>PPCBUG</p> - -<dl> -<dt>Set the bootargs parameter -<dd>PPCBUG>GEVEDIT bootargs -<dd>PPCBUG>bootargs=root=/dev/sda2 -<dt>Perform a boot (assumes SCSI disk on controller 0, SCSI ID 0): -<dd>PPCBUG>PBOOT 0 -<dt>Perform a boot (assumes SCSI disk on controller 0, SCSI ID x) -<dd>PPCBUG>PBOOT 0 x0 -</dl> -<dl> -<dt>Openfirmware -<dt>Perform a boot (for installed IDE/SCSI disk aliased to disk0) -<dd>>boot disk0 -<dt>Perform a boot (for installed IDE/SCSI disk aliased to hdisk0) -<dd>>boot hdisk0 -</dl> -<p> - Now the kernel boots from the hard disk. -</p> - -<hr> -Please email with any suggestions/complaints/problems with the installation -on PReP and this documentation to <a href="mailto:porter@debian.org">Matt Porter</a> diff --git a/greek/ports/powerpc/keycodes.wml b/greek/ports/powerpc/keycodes.wml deleted file mode 100644 index ad58a37fcad..00000000000 --- a/greek/ports/powerpc/keycodes.wml +++ /dev/null @@ -1,224 +0,0 @@ -#use wml::debian::template title="PowerPC Keycodes Change" NOHEADER="yes" -#use wml::fmt::verbatim -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="0cfff43768945b514bb734757927bbbd8b043626" maintainer="galaxico" - - -<h2>PowerPC Linux Keycodes Alert!</h2> -<p> -If you're running a kernel built previous to around April 2001, and -are considering an upgrade to woody, a kernel upgrade, or a keymap -change, it's ESSENTIAL you be aware of the Debian keycodes change for -PowerPC in woody.</p> -<p> -Here's what happened: to pull powerpc into the linux mainstream and -eliminate present and future conflicts, woody's console-data package -was changed to present linux keycode maps for installation instead of -ADB keycode maps (which used to be the norm for powerpc kernels). The -ADB keycode maps are no longer officially Debian supported.</p> -<p> -The installation system's kernel was changed to follow that path, so -the new installation kernel uses linux keycodes, not ADB -keycodes. That is a permanent change; a kernel compiled without -support for ADB keycodes is unable to use ADB keymaps. Linux keycodes -are a feature of the `New Input Layer' which is set to become the -standard for all input devices on all architectures during the -post-2.4 kernel version cycle.</p> -<p> -If you would rather stay with ADB keycodes for the time being, and the -kernel you want to use has been compiled with -CONFIG_MAC_ADBKEYCODES=n, you can re-compile it with -CONFIG_MAC_ADBKEYCODES=y and continue to use an ADB keymap.</p> -<p> -The mac/apple keyboard maps for ADB keycodes vs. linux keycodes are very -different. That's why you must be prepared. If you don't coordinate -your boot instructions, your kernel, and your keymap, you may someday -type 'root' and the login prompt and instead see 'sswj'. A very -disconcerting circumstance.</p> - - -<h2>Planning Ahead</h2> -<p> -A very common circumstance for this to come up is upgrading from -potato to woody. In that case, a special dialog has been incorporated -when console-data is upgraded. A check is made of the kernel you're -running when the upgrade takes place, and if you are running an ADB -kernel, you are warned about the situation and asked to make a choice.</p> -<p> -Since you already know everything about the issue, it will be an easy -choice. Put in a new boottime keymap, then after the upgrade is -complete (BEFORE rebooting), modify your boot configuration (quik.conf -or yaboot.conf) to add a line as follows to the kernel image section -you are booting:</p> -<pre> -append="keyboard_sends_linux_keycodes=1" -</pre> -<p> -If you already have an append= line, add the new term inside the -quotes like</p> -<pre> -append="video=ofonly keyboard_sends_linux_keycodes=1" -</pre> -<p> -Don't forget to run quik or ybin after your editing is complete, to -save the config changes to the real bootloader files.</p> -<p> -Another instance where this issue can come up is when upgrading X from -4.0.x to 4.1.x with an ADB keycodes kernel. Your XF86Config-4 probably -has XkbModel set to "macintosh", but the meaning of that changed so -that a macintosh keyboard is assumed to use the new Linux keycodes. If -you are staying with ADB keycodes, you'll need to change the XkbModel -to "macintosh_old". </p> - -<h2>New Woody Installations</h2> -<p> -For a new woody installation, you will have a linux-keycode keymap and -linux-keycode kernel installed for you. So they'll match, and you -won't have any problem. Unless...</p> -<p> -Unless you change the kernel after installation and it turns out to be -an ADB kernel. Then you will have the same problem in reverse. Or -unless...</p> -<p> -Unless you change the keymap manually, selecting from -/usr/share/keymaps/mac. Those are all ADB keymaps, and they won't -match your linux-keycode kernel! </p> - - -<h2>It Won't Happen To Me -- But When It Does</h2> -<p> -So, how to extract yourself when you type root and see sswj? Or in -the reverse case, type (tab)ssw and see root?</p> -<p> -Linux people hate to turn the switch off on their computers. And -there's always some filesystem corruption when you do that, which may -or may not be repaired correctly. So here are some suggestions to get -the system shut down gracefully if this happens.</p> -<p> -If you have ssh installed on your system and can connect from another -computer, you can temporarily correct the problem remotely. Login to -the root account, and execute the following:</p> - -<verbatim> -cd /proc/sys/dev/mac_hid/ -echo 0 > keyboard_lock_keycodes -echo 1 > keyboard_sends_linux_keycodes -</verbatim> - -<p> -Your keyboard will then respond normally until you reboot. Use the -opportunity to synchronize your keymap, kernel and bootloader!</p> -<p> -If your system has a key combination used as a reboot or shutdown -command, you can try to use the tables below to figure out what the -combination is and apply it. On PowerPC, a common key combo is -Control-Shift-Delete. With an ADB keymap loaded, interpreted as linux -keycodes, that would be Control-F6-F12. With a linux keycodes map -loaded, interpreted by an ADB mapped kernel, you'd need -Shift-AltGr-Equals. Good luck.</p> -<p> -My keyboard doesn't have a Delete key, so when I had a linux-keycodes -map loaded in an ADB-configured kernel, I figured out from the table -how to login as root ( 2==3 followed by F5 ). For my root -password, I used the table below. For reboot, I typed ( 21 tab-key -==3 followed by F5 ). You could also use halt ( p]j3 followed by F5 ).</p> -<p> -Some characters can't be typed in the wrong keymap. Those are blank or -missing in the tables.</p> - -<h2>Linux-keycodes keymap loaded, kernel configured for ADB</h2> - -<p> </p> - -<pre> -If you want: a b c d e f g h i j k l m n o p q r s t u v w -instead type: ] TAB m u 1 [ i p 5 Return l j ` Space = 9 y 2 o 3 6 . t - - x y z 0 1 2 3 4 5 6 7 8 9 * / [ ] , = - ` \ ; - n 4 / b d f h g z x c v Alt F7 7 - Backspace w q ; , ' - - Control Shift Enter Tab Backspace Fwd-Del Space - F6 Ctrl or \ F5, 8 r e F12 CapsLock - - Home NumLock Clear AltGr =(numkpd) Escape F11 F12 - Clear +(numkpd) F6-6 Shift Fwd-Del s kp-5 kp-6 - - F1 F2 F3 F4 F7 F9 - Left-Arrow Right-Arrow Down-Arrow Up-Arrow kp-. kp-* - - Left-Arrow Right-Arrow Up-Arrow Down-Arrow - F13 F11 -</pre> - -<h2>Kernel configured for Linux-keycodes, ADB keymap loaded</h2> - -<pre> -If you want: a b c d e f g h i j k l m n o p q r s t u v w -instead type: 0 7 1 Backspace 2 4 3 g l ' k c x s h - Tab Esc w d 8 = - - x y z 0 1 2 3 4 5 6 7 8 9 * / [ ] , = - ` ; - 6 q 5 Control e r t y i u [ Return p z f a \ o ] m ` - - Control Shift Return Tab Backspace Fwd-Del \ Space - Shift AltGr j b , =(numkpd) Shift n - - Clear AltGr =(numkpd) CapsLock Escape Alt - Home CapsLock Fwd-Del Space / kp-* - - F1 F2 F3 F4 F5 F6 F7 F8 F9 F0 F11 F12 - Enter Ctrl / Fwd-Del - - Left-Arrow Right-Arrow Up-Arrow Down-Arrow - F1 F2 F4 F3 -</pre> - - -<h2>How To Figure Out Your Current Status</h2> -<p> -The keymaps don't currently have comments inside, so if you're -wondering which kind of map is active, you can tell by peeking at the -keycode 1 line with</p> -<pre> -zgrep 'keycode *1 =' /etc/console/boottime.kmap.gz -</pre> -If keycode 1 = Escape, that's the linux (actually i386) keycodes map. -If keycode 1 = s, that's ADB (except for ADB dvorak, keycode 1 = o). -<p> -The config-XXXXX files in /boot will reveal whether the kernel you're -booting with is compiled with ADB keycode support or not. To find -out, use</p> -<pre> -grep MAC_ADB /boot/* -</pre> -<p> -You should get a list of config files for kernels you can boot. If -there's an entry like</p> -<pre> -/boot/config-2.4.12-powerpc:CONFIG_MAC_ADBKEYCODES=y -</pre> -<p>then your kernel is compiled with ADB codes support. If the last -letter is n, it's a linux-keycode kernel.</p> - -<h2>How To Fix It</h2> -<p> -Once you've got your errant system shut down, you still need to -fix it. How can you tell what is needed? You may have to use your -rescue disk or boot another partition in order to fix things up. </p> -<p> -If your problem is an ADB-compiled kernel trying to use a linux-codes -keymap, just add </p> -<pre> -keyboard_sends_linux_keycodes=1 -</pre> -<p>at the boot: prompt after typing your kernel image label. That is only -a one-boot fix, though; you need to make the change permanent by -editing your boot config file and saving it for the bootloader.</p> -<p> -If your problem is the reverse (linux-keycodes kernel trying to use an -ADB keymap), you'll need to get rid of the ADB keymap. You can copy in -any keymap from the /usr/share/keymaps/i386 folder, there are lots to -choose from. For example</p> -<pre> -cd /usr/share/keymaps/i386/qwerty/ -cp mac-usb-us.kmap.gz /etc/console/boottime.kmap.gz -</pre> diff --git a/greek/ports/s390/Makefile b/greek/ports/s390/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/s390/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/s390/index.wml b/greek/ports/s390/index.wml deleted file mode 100644 index 06a7e63c7f2..00000000000 --- a/greek/ports/s390/index.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="S/390 Port" -#use wml::debian::toc -#use wml::debian::translation-check translation="0d2ff40f3ac99634f3bb83bb7589af752e6783c5" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="status">Status</toc-add-entry> - -<p>S/390 has been an officially supported Debian architecture since the release -of Debian 3.0 (woody).</p> - -<p>For instructions on installing Debian, see the -<a href="$(HOME)/releases/stable/s390x/">Installation Guide</a>.</p> - -<toc-add-entry name="team">S/390 porting team</toc-add-entry> - -<p> -The following people contributed to the Debian port to s390: -</p> - -<ul> - <li>Aurélien Jarno</li> - <li>Bastian Blank</li> - <li>Chu-yeon Park and Jae-hwa Park</li> - <li>Frank Kirschner</li> - <li>Frans Pop</li> - <li>Gerhard Tonn</li> - <li>Jochen Röhrig</li> - <li>Matt Zimmerman</li> - <li>Philipp Kern</li> - <li>Richard Higson</li> - <li>Stefan Gybas</li> -</ul> - -<toc-add-entry name="development">Development</toc-add-entry> - -<p>One build server and the porterbox for the <em>s390x</em> architectures are -currently hosted by <a href="https://www.itzbund.de/">Informationstechnikzentrum -Bund (ITZBund)</a>. Other build servers -are provided by <a href="http://www.iic.kit.edu">Informatics Innovation Center, -Karlsruhe Institute of Technology (KIT)</a> and <a -href="https://www.marist.edu/">Marist College</a>. We thank those hosters for -their support!</p> - -<p>In the past <a href="http://www.millenux.de/">Millenux</a> and the <a -href="https://www.ibm.com/it-infrastructure/z/os/linux-support">Linux -Community Development System</a> hosted such build machines.</p> - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p>If you would like to help, you should subscribe to the debian-s390 -mailing list. To do this, send a message containing the word "subscribe" -as the subject to <email "debian-s390-request@lists.debian.org">, or use the -<a href="https://lists.debian.org/debian-s390/">mailing list web page</a>. -You can also browse and search the -<a href="https://lists.debian.org/debian-s390/">mailing list archive</a>.</p> diff --git a/greek/ports/sparc/Makefile b/greek/ports/sparc/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/sparc/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/sparc/credits.wml b/greek/ports/sparc/credits.wml deleted file mode 100644 index 8546252961b..00000000000 --- a/greek/ports/sparc/credits.wml +++ /dev/null @@ -1,46 +0,0 @@ -#use wml::debian::template title="Debian SPARC -- Credits" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="05db930935ccece0e86ce3e75f8029e944ca0888" maintainer="galaxico" - -<h1>Debian SPARC Credits</h1> - <p> -A selected list of people that we'd like to thank for helping with the -SPARC porting effort are: -<ul> - <li> -Johnie `netgod' Ingram who ran SPARC auto-compiles, getting the huge -majority of packages ported with no hassles (no hassles to the rest of -us, anyway ;-) - <li> -Adam Haberlach who produced a Debian SPARC page before I did, from -which I have filched some information. Adam's email address and web -site have bitten the dust -- if you're out there, Adam, contact me! - <li> -Eric Delaunay, the fearless master of the boot floppies - <li> -Steve Dunham, general hacker on the bleeding edge - <li> -Anders Hammarquist, master of X on SPARC <em>and</em> alpha - <li> -Christian Meder, who kicks us all into line on the mailing list, and -uploads packages by the dozen! - <li> -Steve McIntyre, for masterminding the CD efforts - <li> -Ben Collins, who is porting a lot of packages and working on the -autobuilder - <li> -Ward Deng, from Kachina Technologies, who has provided assistance and -hardware for porting - <li> -Jules Bean who originally set up these web pages. - </ul> - - -# <!-- Keep this comment at the end of the file -# Local variables: -# mode: sgml -# sgml-indent-data:nil -# sgml-doctype:"../../releases/.doctype" -# End: -# --> diff --git a/greek/ports/sparc/index.wml b/greek/ports/sparc/index.wml deleted file mode 100644 index c2d6c58b42c..00000000000 --- a/greek/ports/sparc/index.wml +++ /dev/null @@ -1,133 +0,0 @@ -#use wml::debian::template title="SPARC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="f9d5abd797e762089776545824869e3e44bd2c42" maintainer="galaxico" - -<h1>Debian SPARC Port</h1> - -<ul> - <li><a href="#intro">Overview</a></li> - <li><a href="#status">Current Status</a></li> - <li><a href="#sparc64bit">About 64-bit SPARC support</a> - <ul> - <li><a href="#kernelsun4u">Compiling kernels for sun4u</a></li> - </ul></li> - <li><a href="#errata">Errata</a></li> - <li><a href="#who">Who are we? How can I help?</a></li> - <li><a href="#links">Where can I find out more information?</a></li> -</ul> - -<h2 id="intro">Overview</h2> - <p> -These pages are meant to assist users and Debian developers running -Debian GNU/Linux on the SPARC architecture. In these pages, you will -find information about the current status, currently known problems, -information for and about Debian porters, and pointers to more -information. - </p> - -<h2 id="status">Current Status</h2> - <p>Support for pre-UltraSPARC machines was dropped with the end of -service life of Debian Etch (see <a href="https://wiki.debian.org/Sparc32"> -https://wiki.debian.org/Sparc32</a>). -After that, the 32-bit port required an UltraSPARC CPU and ran a 64-bit kernel. - </p> - <p> -This 32-bit port was eventually dropped with the end of the service -life of Debian Wheezy. - </p> - <p> -Currently, there is no official Debian port for SPARC, but a full 64-bit -SPARC port called sparc64 is supported by the Debian Ports team. - </p> - -<h2 id="sparc64bit">About 64-bit SPARC support</h2> - <p> -The Debian SPARC port, -as mentioned above, does support the sun4u (<q>Ultra</q>) -and sun4v (Niagara CPU) architectures. -It uses a 64-bit kernel (compiled with gcc 3.3 or newer), but most of the -applications run in 32-bit. This is also called a <q>32-bit -userland</q>. - </p> - <p> -The Debian SPARC 64 (a.k.a., <q>UltraLinux</q>) porting effort is not -currently conceived as a full porting effort like other ports. -Rather, it is intended to be an <em>add-on</em> to the SPARC Port. - </p> - <p> -In fact, there is really no point in having all applications running -in 64-bit mode. Full 64-bit mode involves a significant overhead -(memory and disk size) with often no benefit. Some applications -really can benefit from being in 64-bit mode, and that is the purpose -of this porting effort. - </p> - -<h3 id="kernelsun4u">Compiling kernels for sun4u</h3> - <p> -To compile a Linux kernel for Sun4u, you'll need to use the Linux 2.2 -or newer source tree. - </p> - <p> -We highly suggest you also use the <tt>kernel-package</tt> package to -help with the installation and management of kernels. You can compile -a configured kernel in one command (as root): - </p> -<pre> - make-kpkg --subarch=sun4u --arch_in_name --revision=custom.1 kernel_image -</pre> - - -<h2 id="errata">Errata</h2> - <p> -Some of the common problems with fixes or workarounds can be found on our -<a href="problems">Errata page</a>. - </p> - - -<h2 id="who">Who are we? How can I help?</h2> - <p> -The Debian SPARC port is a distributed effort, just as Debian is. -Countless people have helped with the porting and documentation -efforts, although a short list of <a href="credits">credits</a> are -available. - </p> - <p> -If you'd like to help, please -join in the <debian-sparc@lists.debian.org> mailing list as -<a href="#links">described below</a>, and chime in. - </p> - <p> -Registered developers who would like to actively port and upload -ported packages should read the porter guidelines in the <a href="$(DOC)/developers-reference/">Developers -Reference</a>, and see the <a href="porting">SPARC porting page</a>. - </p> - - -<h2 id="links">Where can I find out more information?</h2> - <p> -A Debian Wiki page is dedicated about <a href="https://wiki.debian.org/Sparc64">Debian Sparc64 port</a>. - </p> - <p> -The best place to ask Debian-specific questions about the SPARC port -is on the mailing list, <a href="https://lists.debian.org/debian-sparc/">\ -<debian-sparc@lists.debian.org></a>. -Mailing list <a -href="https://lists.debian.org/debian-sparc/">archives</a> are -browsable on the web. - </p> - <p> -To subscribe to the list, send a mail to -<a href="mailto:debian-sparc-request@lists.debian.org">\ -debian-sparc-request@lists.debian.org</a>, with the word `subscribe' -in the subject line, and no body. Alternatively, subscribe on the web -with the <a href="https://lists.debian.org/debian-sparc/">Mailing List -subscription</a> page. - </p> - <p> -Kernel questions should be addressed to the list -<sparclinux@vger.rutgers.edu>. Subscribe by sending a message -with body <q>subscribe sparclinux</q> to the address <a -href="mailto:majordomo@vger.rutgers.edu">majordomo@vger.rutgers.edu</a>. -There is also a Red Hat list, of course. - </p> - diff --git a/greek/ports/sparc/porting.wml b/greek/ports/sparc/porting.wml deleted file mode 100644 index fbfb45e5781..00000000000 --- a/greek/ports/sparc/porting.wml +++ /dev/null @@ -1,67 +0,0 @@ -#use wml::debian::template title="Debian SPARC -- Porting Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="f9d5abd797e762089776545824869e3e44bd2c42" maintainer="galaxico" - -<h1>Debian SPARC Porting Documentation</h1> - -<h2>Porting Debian Packages to SPARC</h2> - <p> -If you want to be an official porter, you must be a registered Debian -developer. That is, your public key must appear in the official -keyring. - <p> -The Debian SPARC porting effort is now organized around the excellent -<code>wanna-build</code> system, first used for the <a -href="../m68k/">m68k</a> port. With <code>wanna-build</code> in -place, porting boils down to locating the packages where automatic -compilation failed, and then going though and determining what went -wrong. - <p> -Failed build logs can be found at -<a href="https://buildd.debian.org/status/architecture.php?a=sparc64">the SPARC 64 buildd web pages</a>. -Also, you can email <code>wanna-build</code> and ask it for the failed -build logs (see the file <code>README.mail</code> from the -<code>wanna-build</code> distribution). - <p> -Serious porters should learn how to interact with -<code>wanna-build</code> via email. You'll need to ask <a -href="mailto:bcollins@debian.org">Ben Collins -<bcollins@debian.org></a> to add your public key to the known -list of keys. - <p> -All Debian developers can use Debian's -<a href="https://db.debian.org/machines.cgi">porterbox machines</a> to -test their packages on the SPARC architecture. - - -<h2>I'm not an official developer; can I still help?</h2> - <p> -Certainly. In fact, most of the real work in a Debian port requires -not official status, just knowledge. There are a number of things you -can do: -<ul> - <li> -Track down bugs, and report them to the <a href="$(HOME)/Bugs/">Debian -Bug Tracking System</a>. - <li> -Figure out patches for known bugs. Be sure to submit the patch to the -Bug Tracking System! - <li> -Help with documentation. Most documentation areas are managed under -CVS, and most documentation authors can give out CVS access to -non-porters who are interested in helping. - </ul> - <p> -So, go ahead and email <a -href="mailto:debian-sparc@lists.debian.org"><debian-sparc@lists.debian.org></a> -with a description of how you'd like to help; we're sure someone there -can get you started. - - -# <!-- Keep this comment at the end of the file -# Local variables: -# mode: sgml -# sgml-indent-data:nil -# sgml-doctype:"../../releases/.doctype" -# End: -# --> diff --git a/greek/ports/sparc/problems.wml b/greek/ports/sparc/problems.wml deleted file mode 100644 index eb1f835637f..00000000000 --- a/greek/ports/sparc/problems.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="SPARC Port -- Errata" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="bc5a5b465aa5f94e13b4ed873d83cbd36b1a2f2b" maintainer="galaxico" - -<h1>Debian SPARC Errata</h1> - <p> -This page contains a list of well-known problems with Debian SPARC. -Stress is placed on the stable release (or freeze, if appropriate), -since these problems turn over much less frequently, and effect a -greater number of people. - <p> -The following list of problems do not attempt to replace the Debian -bug-tracking system (BTS). The main purpose of this information is to -reduce user confusion, reduce traffic on the mailing list, and to -explain workarounds until the bug is fixed. If there is a bug number -associated with a problem, that bug number will be noted. - - -<h2>X Window System</h2> - <p> -Problems relating to the X Window System. - -<h3>How do I know which X server to run?</h3> - <p> -This depends on your machine and which framebuffer (video card) you -have installed. The following list of X server packages should help -- pick the -one which matches your hardware and install the package (and set it -the default X server when asked during installation). -<dl> - <dt>xserver-xsun</dt> - <dd> -Used for most Sun and clone 8-bit framebuffers, such as CG3, CG6, etc. Also -includes monochrome support. - <dt>xserver-xsun-mono</dt> - <dd> -Used for BWTWO and other monochrome framebuffers, or operating color -framebuffers in monochrome mode. - <dt>xserver-xsun24</dt> - <dd> -X server supporting 24-bit color -- suitable for 24-bit framebuffers -supported by the Linux kernel. Not too many folks can use this. - <dt>xserver-mach64</dt> - <dd> -Use this X server for ATI Rage framebuffers, such as found in many -PCI-based UltraSPARC machines. - </dl> - -# <p> -# There are experimental Creator accelerated X servers somewhere to be -# found. Is that in the distribution already? - - -<h3>Issues with Mach64 Server</h3> - <p> -This server will only look for the framebuffer on <tt>/dev/fb0</tt>. -You may have to fool around with symlinks in there to fake it. |