diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2012-05-24 23:08:09 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2012-05-24 23:08:09 +0200 |
| commit | 2910b7c5b1d55bc304344b584a25ea571a9075fb (patch) | |
| tree | bfbfbc98d4c0e205d2726fa44170a16e8421855e /hurd/running | |
| parent | 35b719f54c96778f571984065579625bc9f15bf5 (diff) | |
Prepare toolchain/logs/master branch.
Diffstat (limited to 'hurd/running')
71 files changed, 0 insertions, 3589 deletions
diff --git a/hurd/running/arch_hurd.mdwn b/hurd/running/arch_hurd.mdwn deleted file mode 100644 index 0e6075bb..00000000 --- a/hurd/running/arch_hurd.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="Arch Hurd"]] - -Arch Hurd is a port of Arch Linux to the GNU Hurd, founded on 2010-01-04 by Michael Walker (Barrucadu) and, with input from a variety of people including Allan McRae (allan), Matthias Lanzinger (melpo), and Alexander Preisinger (giselher), the project has made excellent process. There is a livecd available on the Arch Hurd website, with which you can try or install Arch Hurd. - -### Links - -* Official Website: <http://www.archhurd.org> -* Installation Guide: <http://wiki.archhurd.org/wiki/Installation_Guide> -* Mailing Lists: <http://lists.archhurd.org> -* Forum: <http://bbs.archhurd.org> -* IRC: #archhurd on irc.freenode.net diff --git a/hurd/running/bee.mdwn b/hurd/running/bee.mdwn deleted file mode 100644 index f5eb132c..00000000 --- a/hurd/running/bee.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -[Bee GNU/Hurd](http://bee.es.gnu.org/) - -Castellano distribution, pkgsrc package based. [[BochsEmulator]] image -available too. They have their own -[wiki](http://es.gnu.org/cgi-bin/beewiki.pl?Wiki_Bee_GNU) and a [mailing -list](http://bee.es.gnu.org/?p=mail&l=en) (no archive). diff --git a/hurd/running/debian.mdwn b/hurd/running/debian.mdwn deleted file mode 100644 index fcd4d49b..00000000 --- a/hurd/running/debian.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -[[!meta title="Debian GNU/Hurd"]] - -# Debian Resources -- Official page about the Debian GNU/Hurd port: [Debian GNU/Hurd](http://www.debian.org/ports/hurd/) -- Debian [[FAQ]] — Frequently Asked Questions - -## QEMU Image -[[!inline pages=hurd/running/debian/qemu_image raw=yes feeds=no]] - -# Installing -- [Installation Instructions](http://www.debian.org/ports/hurd/hurd-install) - - [Upgrading K11 or K14 based systems to unstable](http://lists.debian.org/debian-hurd/2007/09/msg00007.html) -- [[After_install]] — Do this to get networking, new console and X - -# Contributing -- [[Porting]] — Helping with porting packages - * [[Patch_submission]] — How to submit patches for build failures -- [[Creating_image_tarball]] - -# Additional Information -- [Presentation](http://people.debian.org/~mbanck/talks/hurd_lt2004/html/) - *Debian GNU/Hurd*, [[MichaelBanck]], LinuxTag 2004 Karlsruhe -- [[Status]] -- [Archive Qualification](http://wiki.debian.org/ArchiveQualification/hurd-i386) diff --git a/hurd/running/debian/CDNotesHome.mdwn b/hurd/running/debian/CDNotesHome.mdwn deleted file mode 100644 index a154415b..00000000 --- a/hurd/running/debian/CDNotesHome.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -Charles, here's a place for you! As usual, you can find [more information here](http://www.debian.org/ports/hurd/hurd-cd). Past notes may be of help as well. - ----- - -It seems the building of the CDs is being passed to the University of Calicut. [Re: latest ISO images](http://lists.debian.org/debian-hurd/2007/07/msg00095.html) K 14 is the latest stable, L1 is the development version. - --- [[Main/GrantBow]] - 24 Jul 2007 diff --git a/hurd/running/debian/CrossInstall.mdwn b/hurd/running/debian/CrossInstall.mdwn deleted file mode 100644 index 1cde150c..00000000 --- a/hurd/running/debian/CrossInstall.mdwn +++ /dev/null @@ -1,76 +0,0 @@ -## <a name="Easy_install_with_CrossHurd"> Easy install with CrossHurd </a> - -Qurious about the Hurd? Have a 1-5 GiB partition free? Let's install GNU/Hurd on it! - -### <a name="Preparing_the_partition"> Preparing the partition </a> - -We'll assume you have a partition ready, for the sake of argument we use an example here: /dev/hda3 is the Hurd partition (type: Linux) and /dev/hda4 is the Linux swap that we'll reuse. - -First we create the Ext2 filesystem, notice the `hurd` option. - - # mke2fs -o hurd /dev/DEVICE - -Next we create a useful mountpoint and mount the partition. - - # mkdir /gnu - # mount /dev/hda3 /gnu - -### <a name="Retrieving_CrossHurd"> Retrieving CrossHurd </a> - -Unless you don't run Debian GNU/Linux download it from <http://packages.debian.org/crosshurd>, or simply apt-get the package from Testing or Unstable. - - # apt-get install crosshurd - -### <a name="Cross_installing"> Cross installing </a> - -The crosshurd package only operates in the given target directory, which is the first question asked when running the program. - - # cd /gnu - # crosshurd - -Answer the questions you get: $ What is the target directory?: `/gnu` $ Target Debian system?: gnu $ Target CPU?: i386 - -Now the program starts retrieving all the necessary base packages. - -### <a name="Preparing_to_reboot"> Preparing to reboot </a> - -When all packages have been extracted we must prepare [[GRUB]] for the Hurd when we reboot. Add the below entry to your `/boot/grub/menu.lst` file to boot the Hurd in single user mode (-s). Single user mode is needed only for the two reboots when running the Native Install. - - title GNU (kernel GNUmach 1.3) - root (hd0,2) - kernel /boot/gnumach.gz root=device:hd0s3 -s - 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) - module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - -**_Nota Bene:_** In your menu file there should be no extra white space after the back slashes. - -### <a name="Native_install"> Native install </a> - -Ah, reboot and select "GNU (kernel GNUmach 1.3)" from the Grub menu. At the prompt, setup TERM and run the native-install script. - - # export TERM=mach - # ./native-install - -When done the native install requests that you reboot once again and rerun native-install. This time you will be asked a lot of questions, see the [[Hurd/InstallNotes]] for details. - - # reboot - ... - # export TERM=mach - # ./native-install - -Done, continue setting up your system, see the [[Hurd/InstallNotes]] for more help. - --- [[Main/JoachimNilsson]] - 22 Mar 2005 - ----- - -Jeff Bailey has set up a system where you can install a Hurd system without having to use CDs. It's another type of cross-installation method which uses Debian package management tools to get the packages required as opposed to the one single big tarball. - -As of 2005-03-22, the latest version of crosshurd is 1.7.11. It can be found at <http://packages.debian.org/crosshurd>. - --- [[Main/PeterMelville]] - 12 Jun 2004 diff --git a/hurd/running/debian/DebianAptOffline.mdwn b/hurd/running/debian/DebianAptOffline.mdwn deleted file mode 100644 index 9596040d..00000000 --- a/hurd/running/debian/DebianAptOffline.mdwn +++ /dev/null @@ -1,62 +0,0 @@ -[[!meta copyright="Copyright © 2005, 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -# How to Installing Packages without a Network Connection from your Hurd Installation - -This procedure is based on that found in -`/usr/share/doc/apt-doc/offline.text.gz` (Debian package `apt-doc`). - -This requires having apt installed on the Host operating system. - -Put a copy of [apt.conf.offline](DebianAptOffline/apt.conf.offline) -into your Debian GNU/Hurd installations /etc/apt/ directory. - -## If you _can_ mount your Debian GNU/Hurd partition from another OS, which can connect to the Internet - -As root on the internet connected OS: - - # mount /dev/DEBIAN_GNU_HURD_PARTITON /mnt - # cd /mnt - # apt-get -c etc/apt/apt.conf.offline {update, upgrade, install foo, etc.} - -Then, reboot into your Debian GNU/Hurd installation and as root, run: - - # apt-get {update, upgrade, install foo, etc.} - -## If you _cannot_ mount your Debian GNU/Hurd partition under another OS. - -From your Debian GNU/Hurd installation run, as the root user: - - # tar cf myhurdsconf.tar /etc/apt/{apt.conf.offline,sources.list} /var/lib/dpkg/status - -Copy _myhurdsconf.tar_ to the remote system. - -This copies your apt configuration and the status of your system -(what packages are installed, which versions, etc.) - -From the remote sytem, as any user, run: - - $ mkdir myhurd - $ cd myhurd - $ tar -xf myhurdsconf.tar - $ mkdir -p var/lib/apt/lists/partial var/cache/apt/archives/partial tmp - $ apt-get -c etc/apt/apt.conf.offline {update, upgrade, install foo, etc.} - $ tar cf myhurdsconf.tar etc/apt/{apt.conf.offline,sources.list} var/ - -Copy _myhurdsconf.tar_ back to your Debian GNU/Hurd system. - -Finally, from your Debian GNU/Hurd installation as the root user: - - # mkdir tmp - # cd tmp - # tar -xf myhurdsconf.tar - # mv var/cache/apt/archives/*.deb /var/cache/apt/archives/ - # mv var/lib/apt/lists/*_* /var/lib/apt/lists/ - # apt-get {update, upgrade, install foo, etc.} diff --git a/hurd/running/debian/DebianAptOffline/apt.conf.offline b/hurd/running/debian/DebianAptOffline/apt.conf.offline deleted file mode 100644 index 59aed564..00000000 --- a/hurd/running/debian/DebianAptOffline/apt.conf.offline +++ /dev/null @@ -1,23 +0,0 @@ - APT - { - /* This is not necessary if the two machines are the same arch, it tells - the remote APT what architecture the Debian machine is */ - Architecture "hurd-i386"; - - Get::Download-Only "true"; - }; - - Dir - { - /* Use the disc for state information and redirect the status file from - the /var/lib/dpkg default */ - State "./var/lib/apt"; - State::status "./var/lib/dpkg/status"; - - // Binary caches will be stored locally - Cache::archives "./var/cache/apt/archives/"; - Cache "./tmp/"; - - // Location of the source list. - Etc "./etc/apt/"; - }; diff --git a/hurd/running/debian/DebianDpkgArchitecture.mdwn b/hurd/running/debian/DebianDpkgArchitecture.mdwn deleted file mode 100644 index c768ff4e..00000000 --- a/hurd/running/debian/DebianDpkgArchitecture.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -The output of dpkg-archicture on Debian's hurd-i386 port: - -DEB\_BUILD\_ARCH=hurd-i386 - -DEB\_BUILD\_ARCH\_OS=hurd - -DEB\_BUILD\_ARCH\_CPU=i386 - -DEB\_BUILD\_GNU\_CPU=i486 - -DEB\_BUILD\_GNU\_SYSTEM=gnu - -DEB\_BUILD\_GNU\_TYPE=i486-gnu - -DEB\_HOST\_ARCH=hurd-i386 - -DEB\_HOST\_ARCH\_OS=hurd - -DEB\_HOST\_ARCH\_CPU=i386 - -DEB\_HOST\_GNU\_CPU=i486 - -DEB\_HOST\_GNU\_SYSTEM=gnu - -DEB\_HOST\_GNU\_TYPE=i486-gnu - --- [[Main/MichaelBanck]] - 14 Jan 2006 diff --git a/hurd/running/debian/DebianIntegrationDeveloper.mdwn b/hurd/running/debian/DebianIntegrationDeveloper.mdwn deleted file mode 100644 index 8b34cb7b..00000000 --- a/hurd/running/debian/DebianIntegrationDeveloper.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -Currently, the [Debian](http://www.debian.org) Project consists of two distinct classes of people - Users and Developers. There is a [Quality Assurance](http://qa.debian.org) group that exists to try to help bridge this gap, however it is not as strong as some people would like it to be. In many ways, a DID is another name for what Debian currently classifies as QA. - -A Debian Integration Developer (DID) is a middle-person, someone to assist users and developers. From a [user](http://www.debian.org/support) perspective they answer, categorize and enhance bug reports with patches or Policy suggestions and generally help with user-level integration of multiple Debian software packages as installed. From a [developer](http://www.debian.org/devel/) perspective they update Debian specific package defaults and configuration systems. Upon reflection, this is also a group of folks that can be described as containing both Developer status (maintaining one package) and those who do not feel comfortable classifying themselves as developers. These groups share common goals. - -Besides these two perspectives, there is also a range of tasks that fall into the domain of "[Quality Assurance](http://qa.debian.org)." Tasks necessary to perform on a range of individual packages such as Policy compliance checking, debconf use, /etc/alternatives and similar debian configuration mechanisms that integrate. The Work Needed and Prospective Packages system is an important function. Questions are sometimes raised regarding the diligence or MIA status of developers, in a way, ensuring the overall quality of the debian operational infrastructure. Gathering feedback from users and developers regarding enhancements and changes to these systems. Helping to Integrate the various infrastructure groups when responding to the environment in which Debian resides in is raising the quality of the organization. Many of the tasks that exist in this grey area can be accomplished by non-packaging maintaining users if they understand how Debian and package maintenance works. - -The more I write and think about this area, the more clearly the concept of idealistic leadership is brought to mind. Yet keys to the success of Debian can be directly attributed to the lack of a centralized organizational structure and a strong set of negotiated policies. - -Software dependencies can be very complex. There is often a need for a semi-knowledgable developer (DID or QA) to understand how things work best in a coordinated manner, how best to Integrate. This is also a natural path from which to recruit new package maintainers if assistance is provided along the way. Another separate group that subscribe to a [mail list](http://lists.debian.org) and perform this extremely valuable service is [Debian-Mentors](http://lists.debian.org/debian-mentors/). - -Recognition for the significance of contribution is one reason to give this group of helpful people more courage and identity in helping the Debian project in a clearly defined and less daunting a way. The [devel](http://www.debian.org/devel) page has relevant links. There is a page describing [how you can help](http://www.debian.org/devel/join/), but (indicating the mentality) it's simply a link to the same page as the first step in the [new maintainer process](http://www.debian.org/devel/join/). Behind this first page is the real [new maintainer page](http://www.debian.org/devel/join/newmaint). There's also a [TODO list](http://www.debian.org/devel/todo/) but it's very very broad. - -Perhaps a little bit of this resides in all members of the Debian community and is an important ingredient to the project's overall success. This may be because the developers are in fact, also the users. This can be extremely demanding for new users of Debian. It does take time to come up to speed with what Debian is about, [who participates](http://www.debian.org/intro/organization) to keep it running as it does and what processes exist. The Bug Tracking System's [pseudo-package list](http://www.debian.org/Bugs/pseudo-packages) may give great insight into some processes. - --- [[Main/GrantBow]] - 25 Feb 2004 diff --git a/hurd/running/debian/DebianPackages.mdwn b/hurd/running/debian/DebianPackages.mdwn deleted file mode 100644 index 7e09dce0..00000000 --- a/hurd/running/debian/DebianPackages.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -There are many different systems related to Debian that are related to the efforts. Some of these target information to/from upstream developers, some to end users. Here are some useful links. - -<dl> - <dt><a href="http://qa.debian.org/developer.php" target="_top">Developer Packages Overview</a></dt> - <dd> new system! </dd> -</dl> - -<dl> - <dt><a href="http://bugs.debian.org" target="_top">Bug Tracking System</a></dt> - <dd> also see [[Distrib/BtsFiling]], use a URL like <nop>http://bugs.debian.org/<em>bug-number</em> or <nop>DebianBug:<em>number</em> in a topic using the [[TWiki/InterWikis]] format. </nop></nop></dd> -</dl> - -<dl> - <dt><a href="http://packages.debian.org" target="_top">Package lookup</a></dt> - <dd> also use a URL like <nop>http://packages.debian.org/<em>package-name</em> or <nop>DebianPackage:<em>name</em> in a topic. </nop></nop></dd> -</dl> - -<dl> - <dt><a href="http://packages.qa.debian.org" target="_top">Package Tracking System</a></dt> - <dd><nop>PTS:<em>name</em> in a topic. Email based tracking system to get notices of all package activity - used for packages that highly interest you. This is a new system for Debian and was recently <a href="http://lists.debian.org/debian-devel-announce/2002/debian-devel-announce-200201/msg00011.html" target="_top">announced</a>. </nop></dd> -</dl> - -<dl> - <dt><a href="http://www.debian.gr.jp/~kitame/maint.cgi" target="_top">Package &amp; Maintainer lookup</a></dt> - <dd> from Takuo Kitame </dd> -</dl> - -<dl> - <dt><a href="http://buildd.debian.org/" target="_top">Buildd System</a></dt> - <dd> system to compile and upload binary packages from source automatically. </dd> -</dl> - -<dl> - <dt><a href="http://db.debian.org/" target="_top">Maintainer LDAP</a></dt> - <dd> LDAP directory with the information of Debian developers. </dd> -</dl> - -<dl> - <dt><a href="http://ftp-master.debian.org/testing/update_excuses.html" target="_top">testing "update excuses"</a></dt> - <dd> not needed for Hurd yet. </dd> -</dl> - --- [[Main/GrantBow]] - 15 Jan 2003 diff --git a/hurd/running/debian/DebianTranslatorPolicy.mdwn b/hurd/running/debian/DebianTranslatorPolicy.mdwn deleted file mode 100644 index 7092a761..00000000 --- a/hurd/running/debian/DebianTranslatorPolicy.mdwn +++ /dev/null @@ -1,40 +0,0 @@ -**_This page describes the Debian packaging policy for translators._** - -## <a name="Package_Naming_Scheme"> Package Naming Scheme </a> - -Candidates for package naming schemes (_foofs_ is a filesystem based translator, e.g. _tarfs_, _bar_ is a node based translator, e.g. _random_): - -* _foofs-translator_, _bar-translator_ [current favourite] - -* _foofs_, _bar_ [this will make searching somewhat more of a hassle and may easily conflict with already used package names] - -* _foofs-trans_, _bar-trans_ - -* _hurd-translator-foofs_, _hurd-translator-bar_ - -Do we need to destinguish between file system and node based translators? - -Source packages should be called whatever the tarball/cvs module says. - -## <a name="Where_to_Put_Files"> Where to Put Files </a> - -The translators should go into _/hurd_. - -## <a name="What_about_setting_passive_trans"> What about setting passive translators in _/servers_ or _/dev_? </a> - -The idea is that the package should set passive translators in its _postinst_ instructions. - -There may, however, be difficulties with that: it's perfectly valid to have two different _random_ translator packages installed (they won't conflict with each other as long as their file names don't clash), but which one should sit on _/dev/random_ and _/dev/urandom_? Debian's _alternatives system_ doesn't help here, because the translators may need different command line arguments. - -One idea is to have the _postinst_ instructions set the passive translator if there isn't already one set on the relevant node(s). - -## <a name="Short_Long_Description_Guideline"> Short/Long Description Guidelines </a> - - [packagename]: Foo translator for [doing bar]. - Foo is a GNU/Hurd translator which does [bar]. - -## <a name="Miscellaneous"> Miscellaneous </a> - -There could / should be a meta package (or even more than one) that just depends e.g. on all installable translators, so that they'll conveniently find their way into the system by just installing that meta package. - --- [[Main/MichaelBanck]] - 10 Mar 2006 diff --git a/hurd/running/debian/GNUDebianBuildProcess.mdwn b/hurd/running/debian/GNUDebianBuildProcess.mdwn deleted file mode 100644 index 55a9c6aa..00000000 --- a/hurd/running/debian/GNUDebianBuildProcess.mdwn +++ /dev/null @@ -1,133 +0,0 @@ -components, required and somewhat related - BEFORE you have .debs - -### <a name="Software_States"> Software States </a> - -see [Debian Policy Manual](http://www.debian.org/doc/debian-policy/). - -* Upstream source -* Debian Source Package - * Build-depends -* Debian Binary Package - * Essential - boolean, default is no/unset, see Policy [ref](http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Essential) - * Architecture - policy [ref](http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture) - * Section (main, contrib, non-free, non-US/main, non-US/contrib, non-US/non-free) - * updates, security - * Subsection (admin, base, comm, contrib, devel, doc, editors, electronics, embedded, games, gnome graphics, hamradio, interpreters, kde, libs, libdevel, mail, math, misc, net, news, non-US, non-free, oldlibs, otherosfs, perl, python science, shells, sound, tex, text, utils, web, x11) - * Priority (required, important, standard, optional, extra) policy [ref](http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities) - * a particular set of packages is called the [Base System](http://www.debian.org/doc/debian-policy/ch-binary.html#s3.7) -* Source and binary package upload example from [new maintainers guide](http://www.debian.org/doc/maint-guide/ch-build.en.html) - * gentoo\_0.9.12.orig.tar.gz - * gentoo\_0.9.12-1.dsc - * gentoo\_0.9.12-1.diff.gz - * gentoo\_0.9.12-1\_i386.deb - * gentoo\_0.9.12-1\_i386.changes - -### <a name="Groups"> Groups </a> - -* software author(s) -* Debian Package Maintainers, Co-Maintainers & uploaders -* ftp-masters -* buildd admins - It seems the two primary buildd admins are Ryan Murray and James Troup. -* QA -* bug-filers -* porters for supported platforms (i386, m69k, sparc, alpha, powerpc, arm, mips, mipsel, hppa, ia64, s390) -* porters for unreleased platforms (amd64, sh) -* porters of non-linux platforms (hurd-i386, netbsd-i386, netbsd-alpha, freebsd-i386) -* International translation providers -* system administrators -* users - -### <a name="Build_Debian_Archive_amp_Debian_"> Build, Debian Archive & Debian Systems Software </a> - -* wanna-build available in the buildd [CVS](http://m68k.debian.org/buildd/getting.html) -* buildd [CVS](http://m68k.debian.org/buildd/getting.html), [statistics](http://buildd.debian.org/stats/) -* [quinn-diff](http://buildd.debian.org/quinn-diff/) with anon-CVS - * July 2002 (samosa.sh ?) hurd output [http://buildd.debian.org/quinn-diff/output/unstable/by\_priority-hurd-i386.txt](http://buildd.debian.org/quinn-diff/output/unstable/by_priority-hurd-i386.txt) - * email [reference](http://lists.debian.org/debian-hurd/2000/debian-hurd-200012/msg00168.html) -* [katie](http://ftp-master.debian.org) (was dinstall), ftp-master - * update-excuses [output](http://ftp-master.debian.org/testing/update_excuses.html) -* andrea, see wanna-build for source (no longer at <http://buildd.debian.org/andrea/> ) -* [madison](http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-madison) from developer's reference -* [fakeroot](http://packages.qa.debian.org/fakeroot) -* [sbuild](http://packages.qa.debian.org/sbuild) -* [pbuilder](http://packages.qa.debian.org/pbuilder) -* turtle [reference](http://lists.debian.org/debian-hurd/2001/debian-hurd-200103/msg00328.html) -* [Package Tracking System](http://lists.debian.org/debian-devel-announce/2002/debian-devel-announce-200201/msg00011.html) (PTS) -* [Bug Tracking System](http://bugs.debian.org) (BTS) - * Release Critical mailing to <debian-devel-announce@lists.debianNOSPAM.org> -* [Work Needed and Prospective Packages](http://www.debian.org/devel/wnpp/) (WNPP) -* [Lintian](http://lintian.debian.org/) -* [apt-proxy](http://packages.qa.debian.org/apt-proxy) or [apt-cacher](http://packages.qa.debian.org/apt-cacher) -* [reportbug](http://packages.qa.debian.org/reportbug) -* [dpkg](http://packages.qa.debian.org/dpkg) -* [apt](http://packages.qa.debian.org/apt) -* grep-dctrl -* dpkg-awk - -also see appendix A [Overview of Debian Maintainer Tools](http://www.debian.org/doc/developers-reference/ap-tools.en.html) in the Developer's Reference. - -### <a name="Input_amp_Output_Files_Formats"> Input & Output Files/Formats </a> - -* sources file from an archive -* packages file from an archive -* log from build process -* lintian report -* debcheck report -* upstream related files (tar.gz, dsc [[SampleDscFile]]) -* source deb -* binary deb -* /etc/apt/sources.list file -* bug reports -* web pages -* location to upload files for incoming: ftp-master.debian.org:/org/ftp.debian.org/incoming/ or via ftp to /pub/UploadQueue/ - -<table border="1" cellpadding="1" cellspacing="0"> - <tr> - <th bgcolor="#99CCCC"><strong>Inputs</strong></th> - <th bgcolor="#99CCCC"><strong>1</strong></th> - <th bgcolor="#99CCCC"><strong>2</strong></th> - <th bgcolor="#99CCCC"><strong>3</strong></th> - <th bgcolor="#99CCCC"><strong>4</strong></th> - </tr> - <tr> - <td> </td> - <td> X </td> - <td> </td> - <td> </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>1</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> X </td> - <td> </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>2</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> </td> - <td> X </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>3</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> </td> - <td> </td> - <td> X </td> - <th bgcolor="#99CCCC"><strong>4</strong></th> - </tr> - <tr> - <td> </td> - <td colspan="4"> </td> - <th align="right" bgcolor="#99CCCC"><strong>Outputs</strong></th> - </tr> -</table> - -also see [[GNUDebianPackages]] for information on what you can do AFTER you have .debs. - --- [[Main/GrantBow]] - 03 March 2004 diff --git a/hurd/running/debian/GNUDebianPackages.mdwn b/hurd/running/debian/GNUDebianPackages.mdwn deleted file mode 100644 index de1798ad..00000000 --- a/hurd/running/debian/GNUDebianPackages.mdwn +++ /dev/null @@ -1,103 +0,0 @@ -tools for AFTER you have .debs - -### <a name="Software_States"> Software States </a> - -* Debian Source Package -* Debian Binary Package - * Component (main, contrib, non-free, non-US, updates, security) - * Priority - * Section - * installed state - installed, half-installed, not-installed, unpacked, half-configured, config-files - -### <a name="Groups"> Groups </a> - -* bug-filers -* users - -* Debian Package Maintainers, Co-Maintainers & uploaders -* ftp-masters -* QA -* porters for supported platforms (i386, m69k, sparc, alpha, powerpc, arm, mips, mipsel, hppa, ia64, s390) -* porters for unreleased platforms (amd64, sh) -* porters of non-linux platforms (hurd-i386, netbsd-i386, netbsd-alpha, freebsd-i386) -* International translation providers -* system administrators - -### <a name="Software_amp_Systems"> Software & Systems </a> - -* dselect -* wajig -* grep-dctrl -* dpkg-awk -* [reportbug](http://packages.qa.debian.org/reportbug) -* [dpkg](http://packages.qa.debian.org/dpkg) -* [apt](http://packages.qa.debian.org/apt) - -* [apt-proxy](http://packages.qa.debian.org/apt-proxy) or [apt-cacher](http://packages.qa.debian.org/apt-cacher) -* [Package Tracking System](http://lists.debian.org/debian-devel-announce/2002/debian-devel-announce-200201/msg00011.html) (PTS) -* [Bug Tracking System](http://bugs.debian.org) (BTS) - * Release Critical mailing to <debian-devel-announce@lists.debianNOSPAM.org> -* [Work Needed and Prospective Packages](http://www.debian.org/devel/wnpp/) (WNPP) -* [katie](http://ftp-master.debian.org) (was dinstall), ftp-master - * update-excuses [output](http://ftp-master.debian.org/testing/update_excuses.html) - -### <a name="Input_amp_Output_Files_Formats"> Input & Output Files/Formats </a> - -* sources file from an archive -* packages file from an archive -* source deb -* binary deb -* /etc/apt/sources.list file -* bug reports -* web pages - -<table border="1" cellpadding="1" cellspacing="0"> - <tr> - <th bgcolor="#99CCCC"><strong>Inputs</strong></th> - <th bgcolor="#99CCCC"><strong>1</strong></th> - <th bgcolor="#99CCCC"><strong>2</strong></th> - <th bgcolor="#99CCCC"><strong>3</strong></th> - <th bgcolor="#99CCCC"><strong>4</strong></th> - </tr> - <tr> - <td> </td> - <td> X </td> - <td> </td> - <td> </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>1</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> X </td> - <td> </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>2</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> </td> - <td> X </td> - <td> </td> - <th bgcolor="#99CCCC"><strong>3</strong></th> - </tr> - <tr> - <td> </td> - <td> </td> - <td> </td> - <td> </td> - <td> X </td> - <th bgcolor="#99CCCC"><strong>4</strong></th> - </tr> - <tr> - <td> </td> - <td colspan="4"> </td> - <th align="right" bgcolor="#99CCCC"><strong>Outputs</strong></th> - </tr> -</table> - -also see [[GNUDebianBuildProcess]] for tools BEFORE you have .debs - --- [[Main/GrantBow]] - 03 March 2004 diff --git a/hurd/running/debian/GnuDebianRelationship.mdwn b/hurd/running/debian/GnuDebianRelationship.mdwn deleted file mode 100644 index 94fd6265..00000000 --- a/hurd/running/debian/GnuDebianRelationship.mdwn +++ /dev/null @@ -1,32 +0,0 @@ -I have hesitated in starting this page due to the sensitive nature of this relationship and the (May 2002) flame war on debian-devel and other mail lists. I believe that rather than guessing about relevant points of the discussion, the facts should be presented in a clear manner. I hope the facts presented here are accurate and precise enough to be helpful in the ongoing discussion. I have not read all messages in all relevant threads. - -This is a work in progress. Please email me directly if you have comments or suggestions. - -* Debian Advantages of Hurd [[porting/guidelines]] Efforts - * One of the first ports to non-Linux system along with \*BSD and win32. - * Official GNU system distribution. - -* Debian Disadvantages of Hurd [porting/guidelines]] Efforts - * Perceived zealous GNU and FSF promotion. - -* Hurd Port Advantages of Debian - * Glibc use. - * Gcc use. - * Debian reputation - * Debian mirror infrastructure - ftp, both official and private. Includes bandwidth, hardware, maintenance efforts. - * Debian www infrastructure - many languages supported, mirrors. - * [Debian developer machine](http://db.debian.org/machines.cgi) infrastructure, many architectures, compile farm, buildd software. - * Many Debian Developers maintaining software packages, bug reports, porting efforts. - * Bug tracking system - BTS infrastructure - * Package infrastructure architecture capabilities are improving. dpkg update in progress. - -* Hurd Port Disadvantages of Debian - * Possible DFSG vs. Free Software compatibility issues. - * BTS Severity practices/use for unreleased ports issues. - * Debian non-parallel development issues. - * [Architecture handling](http://master.debian.org/~brinkmd/arch-handling.txt) issues. - * Linux base history with assumed Linux assumptions. - * Possible incompatibility of third party standards compliance issues. i.e. LSB, FHS, GNU Coding Standards - * Perceived zealous Debian promotion. - --- [[Main/GrantBow]] - 22 May 2002 diff --git a/hurd/running/debian/MediaPressKitDiscuss.mdwn b/hurd/running/debian/MediaPressKitDiscuss.mdwn deleted file mode 100644 index 2bd97290..00000000 --- a/hurd/running/debian/MediaPressKitDiscuss.mdwn +++ /dev/null @@ -1,76 +0,0 @@ -# <a name="Media_Press_Kit"> Media / Press Kit </a> - -## <a name="Problem"> Problem </a> - -Debian awareness not as high as other Linux distributions. Some people don't take Debian seriously because of it's organizational structure. Target audience lacks education. Most current Debian users are rather skilled and sometimes PERCIEVED as arrogant. "Non-technical" participation is not fully recognized. - -## <a name="Target_Audience"> Target Audience </a> - -* non-users without any experience of Debian. - * Technically-minded people will often be convinced already of why they should use Debian -* casual users who might be interested in Debian -* ammunition for those who are campaigning to have Debian used - * With our backgrounds, we could emphasize that we can provide material in the langauge that decision-makers can understand. - -## <a name="Debian_Resources"> Debian Resources </a> - -It's important to identify and work with the existing infrastructures for this type of thing. More research about who is out there that is interested in press relations needs to be done before showing the work completed to others. - -* [Contacts](http://www.debian.org/contact) page includes <press@debianNOSPAM.org> but I don't know who's behind that alias. I'll send an email right now to find out. -* [Events team](http://www.debian.org/events/) - * Mail list [debian-events-na](http://lists.debian.org/debian-events-na) - * Mail list [debian-events-eu](http://lists.debian.org/debian-events-eu) -* Debian Weekly News [DWN](http://www.debian.org/News/weekly/) and their mail list [debian-news](http://lists.debian.org/debian-news) -* [debian-announce](http://lists.debian.org/debian-announce) and their [News page](http://www.debian.org/News/) -* [DebianPlanet.org](http://www.debianplanet.org) -* Others? - -## <a name="Solution_Goal"> Solution / Goal </a> - -* persuade people to use Debian -* give target audience realistic expectations of running GNU/Linux - * skills expected - * differences from what they already know -* educate target audience about benefits and advantages of Debian. -* give target audience realistic expectations of running Debian - * skills expected - * differences from what they already know -* background materials, "marketing collateral" - -You have proposed two documents that sound on target to me. - -<dl> - <dt>[[WhyDebian]]</dt> - <dd> A bullet list meant to give a quick answer. </dd> - <dt>[[DebianProductSheet]]</dt> - <dd> includes interesting facts </dd> -</dl> - -The third is a collection of success stories which is more of a process than a clearly defined deliverable in itself. That sounds wonderful. - -I think another active process for tracking recent news (if it doesn't already exist) should also be useful for similar purposes. - -## <a name="Result"> Result </a> - -* two documents: Why Debian? & Debian Product Sheet - * these will be documents of a Debian media/press kit - * processes to keep these documents updated over time. For example, every release. - * beginning of a central repository for info about Debian -* a web repsitory for success stories - * some kind of link or integration with current website. -* increased appreciation by official Debian organization for non-technical participation. -* increased non-technical Debian user involvement -* increased adoption of Debian GNU/Linux by users. -* consideration for using SPI funds for hiring part-time PR resources - --- [[Main/GrantBow]] - 13 Jan 2003 - -[This article](http://www.theage.com.au/articles/2003/01/08/1041989994382.html) was in the [most recent](http://www.debian.org/News/weekly/2003/02/) version of the [Debian Weekly News](http://www.debian.org/News/weekly/). - --- [[Main/GrantBow]] - 15 Jan 2003 - -Here are some interesting urls from [this issue](http://www.debian.org/News/weekly/2003/03/) of the Debian Weekly news: - -**Debian Presentations.** Wolfgang Borgert was [looking](http://lists.debian.org/debian-devel-0301/msg00991.html) for a set of slides on dpkg, apt-get and debconf. Javier Fern�ndez-Sanguino Pe�a [intends](http://lists.debian.org/debian-devel-0301/msg01022.html) to provide a 'presentations' section in the [Debian Documentation Project](http://cvs.debian.org/ddp/?cvsroot=debian-doc) (DDP) and has already created an [archive](http://dat.etsit.upm.es/~jfs/debian/www/ddp/slides/) of slides. Whilst the Debian web site does link to [talks](http://www.debian.org/events/talks) given by developers and some [sample slides](http://www.debian.org/events/materials/slides/), it is difficult to gather this information and publish it in a homogeneous way. Talks should be reported to <events@debianNOSPAM.org> and forwarded to him. - --- [[Main/GrantBow]] - 22 Jan 2003 diff --git a/hurd/running/debian/SampleDscFile.mdwn b/hurd/running/debian/SampleDscFile.mdwn deleted file mode 100644 index d3b7b9f8..00000000 --- a/hurd/running/debian/SampleDscFile.mdwn +++ /dev/null @@ -1,24 +0,0 @@ - -----BEGIN PGP SIGNED MESSAGE----- - Hash: SHA1 - - Format: 1.0 - Source: glibc - Version: 2.3.2.ds1-11 - Binary: libc6, libc6-s390x, locales, libc0.3-prof, libc6.1-dev, libc6-i686, libc1-pic, libc6.1-dbg, glibc-doc, libc6-dev-sparc64, libc0.3-dbg, libc6.1-pic, libc6-dbg, libc0.3, libc0.3-pic, libc6.1-prof, libc6.1, libc6-dev-s390x, libc1, libc0.3-dev, libc6-sparcv9, nscd, libc1-dev, libc6-pic, libc6-prof, libc1-prof, libc-udeb, libc6-sparc64, libc6-dev, libc1-dbg - Maintainer: GNU Libc Maintainers - Architecture: any - Standards-Version: 3.6.1.0 - Build-Depends: gettext (>= 0.10.37-1), make (>= 3.80-1), dpkg-dev (>= 1.4.1.5), debianutils (>= 1.13.1), tar (>= 1.13.11), bzip2, texinfo (>= 4.0), linux-kernel-headers (>= 2.5.999-test7-bk-9) [!hurd-i386], mig (>= 1.3-2) [hurd-i386], hurd-dev (>= 20020608-1) [hurd-i386], gnumach-dev [hurd-i386], texi2html, file, gcc-3.3, autoconf, binutils (>= 2.14.90.0.5) [!s390], binutils (>= 2.13.90.0.4-1) [s390], sed (>= 4.0.5-4), gawk, debhelper (>= 4.0.0) - Build-Depends-Indep: perl, po-debconf - Uploaders: Ben Collins , GOTO Masanori , Philip Blundell , Jeff Bailey , Daniel Jacobowitz - Files: - b982bf6ad7ebc8622d3b81d51c44b78a 13246448 glibc_2.3.2.ds1.orig.tar.gz - 2951fde13e9ba21d70d8c7e580849730 1997696 glibc_2.3.2.ds1-11.diff.gz - - -----BEGIN PGP SIGNATURE----- - Version: GnuPG v1.2.3 (GNU/Linux) - - iD8DBQFADZsWbgOPXuCjg3cRAg9LAJ9r3ioJNdzloaM4qQu3FJj2R3y7pQCeNPD+ - i03WJeMdyAhKjHGM2sRqWVk= - =37je - -----END PGP SIGNATURE----- diff --git a/hurd/running/debian/SoftwareLicensing.mdwn b/hurd/running/debian/SoftwareLicensing.mdwn deleted file mode 100644 index e236fea1..00000000 --- a/hurd/running/debian/SoftwareLicensing.mdwn +++ /dev/null @@ -1,116 +0,0 @@ -There are differences betwen the [Debian Free Software Guidelines](http://www.debian.org/social_contract#guidelines) (DFSG) and [Free Software](http://www.fsf.org/philosophy/free-sw.html) as defined by the Free Software Foundation. The FSF's GNU project is the sponsor of the GNU/Hurd project. Debian GNU/Hurd is a "port" or distribution of this software. I have not yet performed a comparison between the list of acceptable DFSG licenses (if a list exists) and the acceptable Free Software [license list](http://www.gnu.org/licenses/license-list.html). (Perhaps not directly related but for reference, here's the Open Source [license list](http://www.opensource.org/licenses/index.html)) - -What will this consist of? In the end the result will need to be simply a list of packages with their license marked next to them. This will be relatively simple for those packages that use a standard license. Software that has it's own custom license will need to be categorized. - -I am thinking of ways to automatically check the licenses and to get lists of the various "Priority:" packages. I thought this list of package names would be easy to obtain. The first step is getting the list of packages. This is possible by parsing /var/lib/dpkg/available, using dpkg or using apt-cache. - -The next step is checking the licenses of the packages. There is no dpkg package field available for license. A script that checks licenses will involve using "apt-get source" to check the COPYING and/or similar files in each package. - --- [[Main/GrantBow]] - 5 Oct 2002 - -I used the following command on an old Hurd machine to get the 22 packages with Essential in their description. I've listed them and put them in a table at the end of this topic. - - sed -e '/./{H;$!d;}' -e 'x;/Essential\:\ yes/!d' /var/lib/dpkg/status | egrep ^Package | sort - -base-files base-passwd bash bsdutils debianutils diff dpkg e2fsprogs fileutils findutils grep gzip hostname hurd ncurses-base ncurses-bin perl-base sed shellutils tar textutils util-linux - -Using `base` instead of `Essential\:\ yes` above I find 64 additional packages. - -adduser alsa-base apt autoconf2.13 bug cpp-3.0 cvs debconf debconf-utils debhelper debiandoc-sgml debian-policy developers-reference exim fetchmail-common g++-3.0 gcc-3.0 gcc-3.0-base gettext gettext-base gnumach groff groff-base inetutils libc0.3 libc0.3-dev libdb2 libdb2++ libdb2-dev libdb2++-dev libdb2-util libdb3 libgdbmg1 libncurses5 libnet-perl libpam0g libpam-runtime libperl5.6 libpopt0 libpopt-dev libreadline4 libstdc++3 libstdc++3-dev libwrap0 libxaw7 man-db mawk mutt netbase passwd perl python python2.1 screen sgmltools-lite slang1 ssh tcpd texinfo xfree86-common xlibs xserver-common xterm xutils - --- [[Main/GrantBow]] - 11 Jan 2003 - -<table border="1" cellpadding="1" cellspacing="0"> - <tr> - <td> Name </td> - <td> Compatible License? </td> - </tr> - <tr> - <td> base-files </td> - <td> </td> - </tr> - <tr> - <td> base-passwd </td> - <td> </td> - </tr> - <tr> - <td> bash </td> - <td> </td> - </tr> - <tr> - <td> bsdutils </td> - <td> </td> - </tr> - <tr> - <td> debianutils </td> - <td> </td> - </tr> - <tr> - <td> diff </td> - <td> </td> - </tr> - <tr> - <td> dpkg </td> - <td> </td> - </tr> - <tr> - <td> e2fsprogs </td> - <td> </td> - </tr> - <tr> - <td> fileutils </td> - <td> </td> - </tr> - <tr> - <td> findutils </td> - <td> </td> - </tr> - <tr> - <td> grep </td> - <td> </td> - </tr> - <tr> - <td> gzip </td> - <td> </td> - </tr> - <tr> - <td> hostname </td> - <td> </td> - </tr> - <tr> - <td> hurd </td> - <td> </td> - </tr> - <tr> - <td> ncurses-base </td> - <td> </td> - </tr> - <tr> - <td> ncurses-bin </td> - <td> </td> - </tr> - <tr> - <td> perl-base </td> - <td> </td> - </tr> - <tr> - <td> sed </td> - <td> </td> - </tr> - <tr> - <td> shellutils </td> - <td> </td> - </tr> - <tr> - <td> tar </td> - <td> </td> - </tr> - <tr> - <td> textutils </td> - <td> </td> - </tr> - <tr> - <td> util-linux </td> - <td> </td> - </tr> -</table> diff --git a/hurd/running/debian/after_install.mdwn b/hurd/running/debian/after_install.mdwn deleted file mode 100644 index 36c37281..00000000 --- a/hurd/running/debian/after_install.mdwn +++ /dev/null @@ -1,85 +0,0 @@ -First steps after installation. - -So you have managed to get past the first `native-install` runs in single-user -mode? - -Time to get to work. - -[[!toc]] - - -### Get Networking Running - -[[Network]]. - -Check if your NIC was detected by GNU Mach: - - # devprobe eth0 - -`devprobe` (run as user *root*) will print `eth0` on successful detection. If -it doesn't, your NIC was not detected correctly. You can then try to do the -following (also as user *root*) for getting details: - - # cat /dev/klog > ~/klog - [Wait a second, then press `Ctrl-C'.] - -Now examine the `~/klog` file. - -If the NIC was detected: - - # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0 - -Or read about how to configure [[DHCP]]. - - -# Setup GRUB - -You surely want grub to have a nice menu entry able to boot GNU, instead of -typing a boring arcane. There are Debian-specific scripts that may help -you. See [[GRUB]]'s page for this. - - -# Setup `apt-get` - -Sometimes getting `apt-get` to work is not straightforward. Good mirrors to -put in `/etc/apt/sources.list` are: - - deb http://ftp.debian.org/debian unstable main contrib - deb-src http://ftp.debian.org/debian unstable main contrib - deb http://ftp.debian-ports.org/debian unreleased main - deb-src http://ftp.debian-ports.org/debian unreleased main - -`apt-get` update a couple of times if some file fails to download. - -If when doing your first `apt-get`, `dpkg` complains of missing programs, get root in a login shell (`su -`). - -Installing packages without having a network connection is described -[[Distrib/DebianAptOffline]]. - -# [[translator/Random]] - -You often need `scp` and `ssh`. There is now a `random-egd` package available which uses -a random translator by Ryan Hunter and the entropy gathering daemon as entropy source. - -See [[Translator/random]] for more information. - -# [[Console]] - -The latest Hurd package in Debian, plus the `native-install` script, creates -all necessary device nodes and other magic. You just need to edit -`/etc/default/hurd-console` to tune the parameters and tell it to start at -bootup. - -You can also call the Hurd console manually with the proper arguments: - - console -d vga -d pc_kbd --repeat=kbd -d pc_mouse --repeat=mouse \ - -d generic_speaker -c /dev/vcs - - -# [[Hurd/DebianXorg]] - -You first must have setup the virtual console. See above. - -# What about package XYZ? - -See if you can find a useful tip in [[package_troubleshooting]]. diff --git a/hurd/running/debian/creating_image_tarball.mdwn b/hurd/running/debian/creating_image_tarball.mdwn deleted file mode 100644 index ac91dab4..00000000 --- a/hurd/running/debian/creating_image_tarball.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -[[!meta copyright="Copyright © 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -The following [[anonftpsync-ports]] is used to create a local Debian GNU/Hurd -repo. You will need atleast 12G of disk space. Change the -"TO=/home/foo/rsync-debian-ports" to your desired target directory. - -Run it using: - - sudo sh anonftpsync-ports - -In /home/foo/rsync-debian-ports, you will find the following directories: - - base dists indices pool pool-hurd-i386 project diff --git a/hurd/running/debian/creating_image_tarball/anonftpsync-ports b/hurd/running/debian/creating_image_tarball/anonftpsync-ports deleted file mode 100644 index 0988dbde..00000000 --- a/hurd/running/debian/creating_image_tarball/anonftpsync-ports +++ /dev/null @@ -1,180 +0,0 @@ -#! /bin/sh -set -e - -# This script originates from http://www.debian.org/mirror/anonftpsync -# modified by Martin Zobel-Helas <zobel@debian.org>, 2005-01-16 -# these modifications are published under the terms of the GNU GPL -# Modifications: -# + some more documentation about variables -# + added ARCH_EXCLUDE -# + mirror in a safe way, first /pool, then /dists and the rest -# modified by Aurelien Jarno <aurel32@debian.org>, 2007-12-02 -# these modifications are published under the terms of the GNU GPL -# + modifications to mirror debia,-ports.org -# Version: $Id: anonftpsync,v 1.18 2005/10/28 15:25:54 aba Exp $ - - -# Note: You MUST have rsync 2.0.16-1 or newer, which is available in slink -# and all newer Debian releases, or at http://rsync.samba.org/ - -# Set the variables below to fit your site. You can then use cron to have -# this script run daily to automatically update your copy of the archive. - -# Don't forget: -# chmod 744 anonftpsync - -# TO is the destination for the base of the Debian mirror directory -# (the dir that holds dists/ and ls-lR). -# (mandatory) - -TO=/home/foo/rsync-debian-ports - -# RSYNC_HOST is the site you have chosen from the mirrors file. -# (http://www.debian-ports.org/mirrors) -# (mandatory) - -RSYNC_HOST=rsync.debian-ports.org - -# RSYNC_DIR is the directory given in the "Packages over rsync:" line of -# the mirrors file for the site you have chosen to mirror. -# (mandatory) - -RSYNC_DIR=debian/ - -# LOGDIR is the directory where the logs will be written to -# (mandatory) - -LOGDIR=/var/log/rsync-debian-ports - -# ARCH_EXCLUDE can be used to exclude a complete architecture from -# mirrorring. Please use as space seperated list. -# Possible values are: -# armel hurd-i386 kfreebsd-amd64 kfreebsd-i386 -# -# There is one special value: source -# This is not an architecture but will exclude all source code in /pool -# -# eg. -# ARCH_EXCLUDE="hurd-i386" -# -# With a blank ARCH_EXCLUDE you will mirror all availible architectures -# (optional) - -ARCH_EXCLUDE="armel kfreebsd-amd64 kfreebsd-i386 m68k" - -# EXCLUDE is a list of parameters listing patterns that rsync will exclude. -# The following example would exclude mostly everything: -#EXCLUDE="\ -# --exclude binary-hurd-i386/ --exclude binary-kfreebsd-i386/ -# --exclude *_hurd-i386.deb --exclude *_knetbsd-i386.deb \ -# --exclude stable/ --exclude testing/ --exclude unstable/ \ -# --exclude source/ \ -# --exclude *.orig.tar.gz --exclude *.diff.gz --exclude *.dsc \ -# --exclude /base/ --exclude /bochs/ --exclude /obsolete/ \ -# " - -# With a blank EXCLUDE you will mirror the entire archive. -# (optional) - -EXCLUDE="--exclude binary-kfreebsd-i386/ --exclude *_knetbsd-i386.deb \ - --exclude source/ --exclude *.orig.tar.gz --exclude *.diff.gz \ - --exclude /bochs/ --exclude /obsolete/ \ - --exclude *kfreebsd* --exclude *m68* --exclude *sh* \ - " - -# MAILTO is the address to send logfiles to; -# if it is not defined, no mail will be sent -# (optional) - -MAILTO= - -# There should be no need to edit anything below this point, unless there -# are problems. - -#-----------------------------------------------------------------------------# - -# Check for some environment variables -if [ -z $TO ] || [ -z $RSYNC_HOST ] || [ -z $RSYNC_DIR ] || [ -z $LOGDIR ]; then - echo "One of the following variables seems to be empty:" - echo "TO, RSYNC_HOST, RSYNC_DIR or LOGDIR" - exit 2 -fi - -if ! [ -d ${TO}/project/trace/ ]; then - # we are running mirror script for the first time - mkdir -p ${TO}/project/trace -fi - -# Note: on some non-Debian systems, hostname doesn't accept -f option. -# If that's the case on your system, make sure hostname prints the full -# hostname, and remove the -f option. If there's no hostname command, -# explicitly replace `hostname -f` with the hostname. -HOSTNAME=`hostname -f` - -LOCK="${TO}/Archive-Update-in-Progress-${HOSTNAME}" - -# Exclude architectures defined in $ARCH_EXCLUDE -for ARCH in $ARCH_EXCLUDE; do - EXCLUDE=$EXCLUDE"\ - --exclude binary-$ARCH/ \ - --exclude disks-$ARCH/ \ - --exclude installer-$ARCH/ \ - --exclude Contents-$ARCH \ - --exclude Contents-$ARCH.gz \ - --exclude *_$ARCH.deb \ - --exclude *_$ARCH.udeb \ - --exclude pool-$ARCH/" - if [ "$ARCH" == "source" ]; then - SOURCE_EXCLUDE="\ - --exclude *.tar.gz \ - --exclude *.diff.gz \ - --exclude *.dsc " - fi -done - -# Logfile -LOGFILE=$LOGDIR/debian-mirror-ports.log - -# Get in the right directory and set the umask to be group writable -# -cd $HOME -umask 002 - -# Check to see if another sync is in progress -if lockfile -! -l 10800 -r 0 "$LOCK"; then - echo ${HOSTNAME} is unable to start rsync, lock file exists - exit 1 -fi -# Note: on some non-Debian systems, trap doesn't accept "exit" as signal -# specification. If that's the case on your system, try using "0". -trap "rm -f $LOCK > /dev/null 2>&1" exit - -set +e - -# First sync /pool-* -rsync --recursive --links --hard-links --times --verbose \ - $EXCLUDE $SOURCE_EXCLUDE \ - $RSYNC_HOST::$RSYNC_DIR/pool-* $TO >> $LOGFILE 2>&1 -result=$? - -if [ 0 = $result ]; then - # Now sync the remaining stuff - rsync --recursive --links --hard-links --times --verbose --delete-after \ - --exclude "Archive-Update-in-Progress-${HOSTNAME}" \ - --exclude "project/trace/" \ - --exclude "/pool-*/" \ - $EXCLUDE \ - $RSYNC_HOST::$RSYNC_DIR $TO >> $LOGFILE 2>&1 - - date -u > "${TO}/project/trace/${HOSTNAME}" -else - echo "ERROR: Help, something weird happened" | tee -a $LOGFILE - echo "mirroring /pool-* exited with exitcode" $result | tee -a $LOGFILE -fi - - -if ! [ -z $MAILTO ]; then - mail -s "debian ports archive synced" $MAILTO < $LOGFILE -fi - -savelog $LOGFILE diff --git a/hurd/running/debian/dhcp.mdwn b/hurd/running/debian/dhcp.mdwn deleted file mode 100644 index 8d351aae..00000000 --- a/hurd/running/debian/dhcp.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_porting]] - -In order to use DHCP, you need to install the `ifup` and `isc-dhcp-client` -packages, and manually create the following two symbolic links: - - # ln -s ../rcS.d/S06ifupdown-clean ../rcS.d/S11networking /etc/rc.boot/ - -During execution at boot time, the `S11networking` script will emit some error -messages while trying to configure the loopback interface. These are not -fatal. - -Debian GNU/Hurd doesn't currently execute's Debian standard `/etc/rcS.d/*` boot -scripts, but has its own `/libexec/rc` script -- which integrates scripts from -`/etc/rc.boot/` instead. - - -# Open Issues - - * [[!debbug 616290]] - - * [[Proper Hurdy DHCP support|hurd/translator/pfinet/dhcp]] diff --git a/hurd/running/debian/faq.mdwn b/hurd/running/debian/faq.mdwn deleted file mode 100644 index 8aaadf9c..00000000 --- a/hurd/running/debian/faq.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2009, 2010 Free Software Foundation, -Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="Debian GNU/Hurd FAQ"]] - -See also [[after_install]] instructions, and other [[/FAQ]]. - -[[!inline -pages="hurd/running/debian/faq/* and !*/discussion" -show=0 -feeds=no -actions=yes -rootpage="hurd/running/debian/faq" postformtext="Add a new item titled:"]] diff --git a/hurd/running/debian/faq/2_gib_partition_limit.mdwn b/hurd/running/debian/faq/2_gib_partition_limit.mdwn deleted file mode 100644 index 195191cb..00000000 --- a/hurd/running/debian/faq/2_gib_partition_limit.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="2 GiB Partition Limit"]] - -The 2 GiB limit has been removed in Debian GNU/Hurd. diff --git a/hurd/running/debian/faq/512_mib_ram_limit.mdwn b/hurd/running/debian/faq/512_mib_ram_limit.mdwn deleted file mode 100644 index f89a5c01..00000000 --- a/hurd/running/debian/faq/512_mib_ram_limit.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="512 MiB RAM Limit"]] - -Just like any 32bit OS without bad tricks, GNU Mach does not cope well with lots -of memory. Newer versions of the Debian `gnumach` package will limit themselves -to around 1 GiB of memory. If you want more, you can twiddle the VM_MAX_ADDRESS -limit between kernelland and userland in i386/include/mach/i386/vm_param.h. - -If you have an older version, or still experience problems with `vmstat` (see -above) reported much less memory than you have, the best is to limit the memory -it can see via GRUB's `upppermem` feature. Add `uppermem 786432` to GRUB's Hurd -entry in `menu.lst`. diff --git a/hurd/running/debian/faq/apt_umount.mdwn b/hurd/running/debian/faq/apt_umount.mdwn deleted file mode 100644 index db0dbfd1..00000000 --- a/hurd/running/debian/faq/apt_umount.mdwn +++ /dev/null @@ -1,25 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="apt: unmount cdroms"]] - -You can add a shell script umount so that apt can automatically unmount cdroms. - - #!/bin/sh - # Filename: /usr/bin/umount - - settrans -fg "$@" - -Give executable permission to the script. - - # chmod +x /usr/bin/umount - -In `/etc/fstab` add a trailing `/` after cdrom like `/cdrom/` since apt uses a -trailing `/`. diff --git a/hurd/running/debian/faq/bad_hypermeta_data.mdwn b/hurd/running/debian/faq/bad_hypermeta_data.mdwn deleted file mode 100644 index bc960e30..00000000 --- a/hurd/running/debian/faq/bad_hypermeta_data.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -If you get the error `bad hypermeta data` when trying to mount an ext3 -partition from GNU/Linux, that is usually because the file system has not been -unmounted cleanly (maybe GNU/Linux got suspended to disk) and the Hurd cannot -mount it as ext2 without checking. Either boot back into GNU/Linux and unmount -it or you can try to run `fsck.ext3` from GNU/Hurd directly. diff --git a/hurd/running/debian/faq/debugging_inside_glibc.mdwn b/hurd/running/debian/faq/debugging_inside_glibc.mdwn deleted file mode 100644 index 91b71d64..00000000 --- a/hurd/running/debian/faq/debugging_inside_glibc.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation, -Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -To get [[debugging]] information for glibc, you need to install the -`libc0.3-dbg` package. At the place [[debugging/GDB]] looks for debugging -symbols by default (`/usr/lib/debug/lib/`), Debian's `libc0.3-dbg` stores only -the frame unwind information used for backtracing. If you want to step into -glibc while debugging, you need to add `LD_LIBRARY_PATH=/usr/lib/debug` to -debugged program's environment (`set env VAR value` from the GDB command line). -If that still does not work, try `LD_PRELOAD=/usr/lib/debug/libc.so.0.3` -instead. diff --git a/hurd/running/debian/faq/debugging_translators.mdwn b/hurd/running/debian/faq/debugging_translators.mdwn deleted file mode 100644 index b55484e1..00000000 --- a/hurd/running/debian/faq/debugging_translators.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -In order to [[debug|debugging]] translators and being able to step into glibc -during it, you need the `hurd-dbg` and `libc0.3-dbg` packages installed. If you need to debug the initialization of the translator, -start the translator like `settrans -P /foo /usr/bin/env -LD\_LIBRARY\_PATH=/usr/lib/debug /hurd/foofs`. The `-P` option will make it -pause and you will be able to attach [[debugging/GDB]] to the process. diff --git a/hurd/running/debian/faq/dev_random.mdwn b/hurd/running/debian/faq/dev_random.mdwn deleted file mode 100644 index 3b5fdffe..00000000 --- a/hurd/running/debian/faq/dev_random.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="/dev/random"]] - -There is no random device by default as no secure implementation has been -finished yet. An easy (but very insecure) work-around is to copy a binary file -like `/bin/bash` to `/dev/random` and `/dev/urandom`. A slightly more secure -alternative is installing the `random-egd` from the `debian-ports` repository. - diff --git a/hurd/running/debian/faq/df.mdwn b/hurd/running/debian/faq/df.mdwn deleted file mode 100644 index bbd3a7b9..00000000 --- a/hurd/running/debian/faq/df.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -There is no `/etc/mtab` (due to dynamic translator startup, its content is hard -to define actually, see -[[the mtab GSoC project idea|community/gsoc/project_ideas/mtab]]), -so just running `df` will yield the following error. - - df: cannot read table of mounted file systems - -Pass `df` a path like `df /` or `df ./` to see the disk usage of that particular -file system. diff --git a/hurd/running/debian/faq/eata.mdwn b/hurd/running/debian/faq/eata.mdwn deleted file mode 100644 index fa7dbdec..00000000 --- a/hurd/running/debian/faq/eata.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -In some virtual machines (e.g. VirtualBox), "probing eata on XXX" may be -quite long. This is apparently due to poor efficiency of the virtualizer, not -Mach. There is no such issue on real hardware or using qemu/kvm. diff --git a/hurd/running/debian/faq/free_memory.mdwn b/hurd/running/debian/faq/free_memory.mdwn deleted file mode 100644 index c1c0a83c..00000000 --- a/hurd/running/debian/faq/free_memory.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Run `vmstat` to see memory and swap usage. diff --git a/hurd/running/debian/faq/hurd_console.mdwn b/hurd/running/debian/faq/hurd_console.mdwn deleted file mode 100644 index c4a619a1..00000000 --- a/hurd/running/debian/faq/hurd_console.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Edit `/etc/default/hurd-console` to configure the Hurd console and enable it on -bootup. See [[console]] for further information about the Hurd console. diff --git a/hurd/running/debian/faq/kernel_logs.mdwn b/hurd/running/debian/faq/kernel_logs.mdwn deleted file mode 100644 index ff14ce5f..00000000 --- a/hurd/running/debian/faq/kernel_logs.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -The kernel logs are written to `/dev/klog`. Run `cat /dev/klog > foo` as root -and hit `ctrl+c` after a few seconds to catch the logs. You can do this only -once and do not do this in single-user mode (where `ctrl+c` does not work). diff --git a/hurd/running/debian/faq/other_repositories.mdwn b/hurd/running/debian/faq/other_repositories.mdwn deleted file mode 100644 index 88781d46..00000000 --- a/hurd/running/debian/faq/other_repositories.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -If you want to use the `apt-get source` facility, make sure that -`/etc/apt/sources.list` contains a line like - - deb-src http://ftp.de.debian.org/debian unstable main - -... replacing _de_ with your homeland's code. diff --git a/hurd/running/debian/faq/ps_hangs.mdwn b/hurd/running/debian/faq/ps_hangs.mdwn deleted file mode 100644 index febfeb59..00000000 --- a/hurd/running/debian/faq/ps_hangs.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -If `ps` hangs, try `ps -M` which might still work by not getting detailed -information from processes. diff --git a/hurd/running/debian/faq/reporting_bugs.mdwn b/hurd/running/debian/faq/reporting_bugs.mdwn deleted file mode 100644 index 40781ab0..00000000 --- a/hurd/running/debian/faq/reporting_bugs.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Please try to reproduce bugs which are not obviously Hurd-specific on Debian -GNU/Linux and then file them there. - -If you find a genuine issue in Debian GNU/Hurd, please file it in our Alioth -bug tracker at -<http://alioth.debian.org/tracker/?atid=411594&group_id=30628&func=browse> -If you find a bug in the Hurd or GNU Mach themselves, either file a bug against -the respective Debian packages, or directly at -<http://savannah.gnu.org/bugs/?group=hurd> diff --git a/hurd/running/debian/faq/sata_disk_drives.mdwn b/hurd/running/debian/faq/sata_disk_drives.mdwn deleted file mode 100644 index dad10cb9..00000000 --- a/hurd/running/debian/faq/sata_disk_drives.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -[[!meta copyright="Copyright © 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -GNU Mach does not support SATA disk drives (/dev/sda etc. in GNU/Linux) natively, so using device:sd0s1 will not work, sd* devices are for SCSI drives only. The only way to get those drives to work is to put them into compatibility mode in the BIOS, if such an option exists. GNU Mach will then recognize them as hda etc. diff --git a/hurd/running/debian/faq/sshd_only_works_for_root_logins.mdwn b/hurd/running/debian/faq/sshd_only_works_for_root_logins.mdwn deleted file mode 100644 index 1a3c46e1..00000000 --- a/hurd/running/debian/faq/sshd_only_works_for_root_logins.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 2010 Free Software Foundation, -Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -This isssue has been fixed in the Debian hurd / libc0.3 packages as of 2010-11. -Retire this item sometime after 2011. - ---- - -Privilege seperation does not work with Hurd currently. You need to explicitely -set `PrivilegeSeparation` to `no` in `/etc/ssh/sshd_options`, just commenting out -the entry will not work as it is on by default. Also make sure you have -`/dev/random`, see below. diff --git a/hurd/running/debian/faq/xserver-common.mdwn b/hurd/running/debian/faq/xserver-common.mdwn deleted file mode 100644 index d1b17f31..00000000 --- a/hurd/running/debian/faq/xserver-common.mdwn +++ /dev/null @@ -1,12 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -You need to run `dpkg-reconfigure x11-common` and select `Anybody` for -starting X as there is no way to detect console users currently. diff --git a/hurd/running/debian/package_troubleshooting.mdwn b/hurd/running/debian/package_troubleshooting.mdwn deleted file mode 100644 index c6236c2f..00000000 --- a/hurd/running/debian/package_troubleshooting.mdwn +++ /dev/null @@ -1,49 +0,0 @@ -This page reports known Hurd-specific bugs, quirks and corresponding solutions and workarounds with Debian GNU/Hurd package installation and working. - -## <a name="Dpkg_wants_external_programs_"> Dpkg wants external programs? </a> - -It may be that dpkg wants external GNU/Linux-specific programs that it can't found or that just don't exist on the Hurd. You can trick dpkg by copying and running this script as root: - - #!/bin/bash - ln -s /sbin/ldconfig /bin/ldconfig - ln -s /bin/true /bin/update-rc.d - ln -s /bin/true /bin/start-stop-daemon - ln -s /bin/true /bin/install-info - ln -s /bin/true /bin/update-alternatives - -## <a name="SSH_not_working"> </a> SSH not working - -You must set up the [[translator/random]] device first. - -## <a name="An_X_package_hangs_at_startup_wi"> An X package hangs at startup without error messages </a> - -Observed with GTK programs like xchat, synaptic, inkscape. It is an issue with -[[libpthread]] that (as of 04 Feb 2007) is still unresolved. Sorry. - -## <a name="Borked_fonts_on_GTK_app"> </a> Borked fonts on GTK app - -This is related to issues in Pango. - -* Install pango-dev package -* Run as root: - - pango-querymodules > /etc/pango/pango.modules - -## <a name="Installing_a_package_seems_to_ha"> Installing a package seems to hang forever </a> - -There are various reasons for this. - -* If interrupting the process with ctrl-c gives a line like that: - - File "/usr/lib/python2.4/os.py", line 723, in urandom - bytes += read(_urandomfd, n - len(bytes)) - KeyboardInterrupt - -it is the random device fault. Follow the [[translator/random]] guide. If you already did, try _anyway_ to detach and reattach the translators. - -## <a name="Cannot_compile_even_trivial_C_pr"> Cannot compile even trivial C programs </a> - -Check to have installed the following: - - apt-get install build-essential - apt-get install libc-dev diff --git a/hurd/running/debian/patch_submission.mdwn b/hurd/running/debian/patch_submission.mdwn deleted file mode 100644 index 1dd8a4db..00000000 --- a/hurd/running/debian/patch_submission.mdwn +++ /dev/null @@ -1,66 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 2011 Free Software Foundation, -Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -If you fixed a Debian package which *FTBFS* (fails to build from source), you -should submit the patch so that all users can profit from your work. - -If it is not a Debian-specific patch, you should strongly consider submitting -the patch upstream for inclusion. This applies even more so if it is a GNU -package, or otherwise frequently used package, or you know upstream anyway. - -If you had to change the code considerably and are not 100% sure you did not -introduce a regression, or are not very experienced with these kinds of code -changes, you should first submit your patch for review to the [Debian alioth -patch -tracker](http://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse). - -If the patch is trivial, or one of the Debian porters approved your patch for -submission, submit the patch to the Debian BTS (bug tracking system). You can -either use the reportbug tool, or just simple mail. In any case, you should -follow these guidelines: - - * The submission address is <submit@bugs.debian.org>. - - * The mail's subject (which will become the bug's title) should be - `SOURCE-PACKAGE: FTBFS on hurd-i386: REASON`. - - * The first lines of the mail's body (the so-called *pseudo-header*): - - Package: PACKAGE - Severity: important -- not *serious* - Version: VERSION -- the version of the source package in unstable. - Tags: patch -- if you include a ready-to-be-applied patch. - User: debian-hurd@lists.debian.org - Usertags: hurd - X-Debbugs-CC: debian-hurd@lists.debian.org - -The last three lines are used to to change the current *User* to the specified -value (the default is the email sender/from address), specify *Usertags* to add -the specified tags for the current user, and *X-Debbugs-CC* so that the -[[mailing list|mailing_lists/debian-hurd]] knows about your report. - -In the bug description, mention that the package fails to build on hurd-i386 -and (if possible) quote the failure. If possible, point to the failing build -log from <http://buildd.debian-ports.org/build.php> or elsewhere. - -Then, explain the failure (Debian maintainers usually do not know much about -Hurd-specific failures), and attach the patch. - -The patch should be in unidiff form. - -If the package uses a patch system, it is preferable to submit the patch in a -ready-to-use form (e.g. as a *dpatch*), but this is not required. Also, try to -keep the patch small, e.g., do not submit a 100 KiB autotools diff for a -one-line change in `configure.in` or a `Makefile.am`, but in this case mention -that autotools need to be rerun and let the maintainer choose (you can suggest -you would file a complete diff if the maintainer prefers). - -Last but not least, try to be courteous. diff --git a/hurd/running/debian/porting.mdwn b/hurd/running/debian/porting.mdwn deleted file mode 100644 index b57b295e..00000000 --- a/hurd/running/debian/porting.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 2009, 2010, 2011 Free Software -Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="Debian packages that need porting"]] - -[[!tag stable_URL]] - -More than half of the Debian archive has been compiled successfully on the -Hurd, however, many programs fail to build for various reasons. - -A [list of build failures including error -messages](http://unstable.buildd.net/buildd/hurd-i386_Failed.html) can be -found, as well as a [preliminary -analysis](http://lists.debian.org/debian-hurd/2007/07/msg00000.html) of them and [solutions](http://lists.debian.org/debian-hurd/2007/07/msg00001.html), and some more details in [[hurd/porting/guidelines]]. [Graphs and statistics](http://people.debian.org/~sthibault/) about the consequence in terms of build dependencies are available. - -There is a mailing list, -[debian-hurd-build-logs](http://lists.alioth.debian.org/mailman/listinfo/debian-hurd-build-logs), -where *builds logs from the Debian GNU/Hurd autobuilders* are posted. It is a -high-traffic and high-volume list, and for that reason *not* archived, so you -have to subscribe to see the messages. - -It might be a good idea to record your intention to port something either in -the list below or in the [Alioth task -tracker](http://alioth.debian.org/pm/task.php?group_project_id=34&group_id=30628&func=browse) -so other people do not do duplicated work. - -Also, the [[community/HurdFr]] guys maintain their own [liste des travaux de -packaging](http://wiki.hurdfr.org/index.php/Liste_des_travaux_de_packaging). - -Aside from the Alioth task tracker, here is a list of some packages (the -important ones, as they're, e.g., blocking other packages from being built) -that need someone to work on them. - -When you have a patch to submit, please adhere to the [[patch_submission]] -guidelines. - -There is also further information available about [[hurd/porting]]. - -[[!map -pages="tagged(open_issue_porting) and !tagged(fixed_in_debian) and !*/discussion" -show=title]] - -[[!inline -pages="tagged(open_issue_porting) and !tagged(fixed_in_debian) and !*/discussion" -show=0 -feeds=no -actions=yes -rootpage="open_issues" postformtext="Add a new item titled:"]] diff --git a/hurd/running/debian/qemu_image.mdwn b/hurd/running/debian/qemu_image.mdwn deleted file mode 100644 index 809bf7b1..00000000 --- a/hurd/running/debian/qemu_image.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -There is a QEMU image with [[Debian GNU/Hurd|debian]] pre-installed available -as <http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.tar.gz>. - -Usage: - - $ wget http://people.debian.org/~sthibault/hurd-i386/debian-hurd.img.tar.gz - $ tar -xz < debian-hurd.img.tar.gz - $ qemu -net nic,model=rtl8139 -net user -hda debian-hurd-*.img - -Just in case you were wondering: the *root* password is *root*. - -[[!if test="destpage(hurd/running/qemu)" then="" else="For more detailed -instructions, please see the [[hurd/running/QEMU]] page."]] diff --git a/hurd/running/debian/status.mdwn b/hurd/running/debian/status.mdwn deleted file mode 100644 index 95e48edc..00000000 --- a/hurd/running/debian/status.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -Debian GNU/Hurd is currently an official, non-releasing Debian port. I.e., there is no testing or stable distribution. - - - [Build daemon/archive status](http://unstable.buildd.net/buildd/hurd-i386_stats) - - [Number of registered users](http://buildd.net/cgi/archvote.phtml) diff --git a/hurd/running/distrib.mdwn b/hurd/running/distrib.mdwn deleted file mode 100644 index befb015d..00000000 --- a/hurd/running/distrib.mdwn +++ /dev/null @@ -1,149 +0,0 @@ -Working distributions of GNU/Hurd: - -* [[Debian]] - -GNU/Hurd distributions in early stages of development: - -* [[Arch|arch_hurd]] (features a LiveCD) -* [[Nix]] -* [[Gentoo]] -* [[GNU]] - -<!-- Bee GNU/Hurd doesn't seem to exist anymore. -* [[Bee]] ---> - -# Issues - -<dt>[[SoftwareLicensing]]</dt> -<dd> The copyright and license information for software that is distributed with the Hurd software is important. Debian has its DFSG guidelines. Other distributions will need to address these same issues. </dd> - -[[GnuDebianRelationship]] - - -## <a name="Installation"> Installation </a> - -<dl> - <dt> Install Instructions</dt> - <dd> Currently, <a href="http://www.debian.org/ports/hurd/hurd-install" target="_top">Debian's installation instructions</a> are the most up-to-date. [[Hurd/InstallNotes]] is an errata companion document with more helpful hints that have not yet been incorporated. </dd> -</dl> - -<dl> - <dt>[[CrossInstall]]</dt> - <dd> Another way to install a system. </dd> -</dl> - -<dl> - <dt> Release Information</dt> - <dd> About the latest CD release. Includes errata, known bugs and fixes. See [[CDNotesHome]] and [[TarballNotesHome]] for summaries </dd> -</dl> - -<dl> - <dt>[[GRUB]]</dt> - <dd> A quick reference and explanation. </dd> -</dl> - -<dl> - <dt>[[InstallTips]]</dt> - <dd> Info on how to install without a cd drive or linux installed as well as a few tips. </dd> -</dl> - -Another installation method is using an emulated environment. The [[BochsEmulator]] was originally the recommended virtual machine solution, however most have switched over to QEMU, as it runs faster. - -* [[hurd/running/QEMU]] - A guide on how to use QEMU to run the hurd. -* [[BochsFAQ]] - Common questions you should read. -* [[VmWare]] - Why using it is discouraged. - -<dl> - <dt> Debian Installer</dt> - <dd> Work has been started by James Morrison and Glenn <nop>McGrath to [[PortDebootstrap]]. There is also a [[NewDebianInstaller]]. Why should Hurd folks care? It's important because this is the next generation installer that is intended to be used by all ports when Sarge is released. </nop></dd> -</dl> - - -# Using - -Debian [[debian/after_install]] instructions are a must-read to prepare an -usable system. - -[[debian/Package_troubleshooting]] reports known bugs, quirks and workarounds -about getting applications to work (if possible). - - -# For Developers - -<dl> - <dt>[[SavannahProjects]]</dt> - <dd> Savannah is a CVS & Bug system evolved from a free version of the code that powers <a href="http://sf.net" target="_top">sourceforge.net</a>. It has forked and been slightly modified for use by FSF, GNU and non-GNU projects. Actual Development takes place here. There is also a <a href="http://savannah.gnu.org/people/?group=hurd" target="_top">help wanted</a> list. </dd> -</dl> - -<dl> - <dt>[[porting/guidelines]] FAQ</dt> - <dd> What does it take to move a piece of Debian packaged software to the GNU/Hurd port? </dd> -</dl> - -<dl> - <dt>[[BuildingTheHurd]]</dt> - <dd> A summary by the Gentoo folks, thanks <a href="http://cvs.gentoo.org/~avenj/" target="_top">Jon Portnoy</a> - <a href="mailto:avenj@gentooNOSPAM.org">avenj@gentooNOSPAM.org</a></dd> -</dl> - -<dl> - <dt> Debian Infrastructure</dt> - <dd> Testing is critical in helping the development effort. Bugs (defect reports) can be filed against the Debian software package in which they are found. [[debian/patch_submission]] tells how to file a Debian bug report. [[DebianPackages]] has some information about how Debian splits the software into packages and some references. There is a buildd autobuilder compiling the Debian Sid archive software for the GNU/Hurd port. [[BuilddStatus]] includes information on the buildd & turtle efforts. </dd> -</dl> - -<dl> - <dt><a href="http://hurd.she.kicks-ass.org:8084/uninstallable/" target="_top">Uninstallable packages</a></dt> - <dd> Many packages depend on these uninstallable packages. So building one of them will allow other to be build too. </dd> -</dl> - -<dl> - <dt> Technical References</dt> - <dd> There are many standards and documents that might be applicable for those interested in developing software. </dd> -</dl> - -* GNU [Coding Standards](http://www.gnu.org/prep/standards.html) -* [[TestSuites]] - Posix, Perl, results feedback, etc. -* [[Documentation]] -* [[System_API_Limitations]] -* [[CodeAnnouncements]] - Recent coding projects related to the Hurd - -<dl> - <dt> Debian <a href="http://www.debian.org/devel/" target="_top">Developer's Corner</a></dt> - <dd> The following references are provided as a starting point for those interested in helping to package software for Debian GNU/Hurd and Debian GNU/Linux. </dd> -</dl> - -* [Policy Manual](http://www.debian.org/doc/debian-policy/) -* Developer's [Reference](http://www.debian.org/doc/developers-reference/) -* New Maintainers [Guide](http://www.debian.org/doc/maint-guide/) -* There are many Debian email lists - -<dl> - <dt> Debian Todo</dt> - <dd> Packages needing attention. A possible use of this site could be to help track similar needs via [[HurdWnpp]]. This is not yet implemented. </dd> -</dl> - -<dl> - <dt>[[GnuDistributionRumors]]</dt> - <dd> There are some discussions and several rumors circulating about creating a completely new distribution, not using a Debian architecture. </dd> -</dl> - -# Misc. - -<dl> - <dt> Why a separate section of the website for this?</dt> - <dd> There are fundamentally different issues about distributions compared with coding. Distributions are concerned with final default configurations of packaged software and system integration as they use many software packages and help give users a sense of using an OS "product." </dd> -</dl> - -<dl> - <dt>[[WhyDebian]]</dt> - <dd> A one page document focused on Debian aimed at users to answer their question "Why Debian?" </dd> -</dl> - -<dl> - <dt>[[DebianProductSheet]]</dt> - <dd> Technical description of Debian aimed at those interested in Debian. </dd> -</dl> - -* [Misc. Docs @Etherhogz](http://www.etherhogz.org/doc/) (broken) -* [Ognyan Kulev Collection](http://debian.fmi.uni-sofia.bg/~ogi/hurd/links/index.html) of links (unsupported) -* [2000 Jim Franklin Collection](http://angg.twu.net/the_hurd_links.html) of links diff --git a/hurd/running/faq.mdwn b/hurd/running/faq.mdwn deleted file mode 100644 index 2746a20a..00000000 --- a/hurd/running/faq.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -[[!meta copyright="Copyright © 2009, 2010 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="General FAQ About Running GNU/Hurd"]] - -See also other [[/FAQ]]. - -[[!inline -pages="hurd/running/faq/* and !*/discussion" -show=0 -feeds=no -actions=yes -rootpage="hurd/running/faq" postformtext="Add a new item titled:"]] diff --git a/hurd/running/faq/native-install_doesnt_finish.mdwn b/hurd/running/faq/native-install_doesnt_finish.mdwn deleted file mode 100644 index a852e1dd..00000000 --- a/hurd/running/faq/native-install_doesnt_finish.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -Copying baseGNU to the virtual disk works. Even booting got through but when I -try to run native-install it never gets to the very end. First time it froze on -*sed* package, the other time on *sysv-rc*. - -> How much memory did you configure for the [[QEMU]] system? It may simply be -> -- I've seen this myself -- that the system runs out of memory, as at the -> native-install stage (I think at least) swap is not yet configured and -> enabled. What I've been doing is: boot (with -s), MAKEDEV hdWHATEVER in -> /dev/ for the swap device, run /hurd/mach-defpager, followed by swapon -> /dev/hdWHATEVER. Does this help? - ->> Thank You very much, more memory solved the freezing. - -[[!tag open_issue_hurd]] diff --git a/hurd/running/gentoo.mdwn b/hurd/running/gentoo.mdwn deleted file mode 100644 index ef72bfad..00000000 --- a/hurd/running/gentoo.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -* [Archived try at a Gentoo GNU/Hurd](http://www.mundurat.net/ggh/) - -Unofficial port to Gentoo and the portage system. It was -[announced](http://forums.gentoo.org/viewtopic.php?t=41939&postdays=0&postorder=asc&start=0) -March 17, 2003 in the Gentoo forums. There's a #gentoo and a #gentoo-hurd IRC channel similar to -[[IRC]]. - -### State of the GGH, 2009-05 - -> *Did you work a bit more on the Gentoo GNU/Hurd?* - -I tried to resume my work 3-4 months ago but I found some problems with -portage and python functions not implemented on Hurd so I stopped. I think -that back in 2006 with portage 2.0.54 those functiones weren't necessary. - -> *And do you have some information which might help others advance what you began?* - -I just have all the ebuilds and binary packages I merged online on -[http://www.mundurat.net/ggh/portage](http://www.mundurat.net/ggh/portage). - -To continue my work just take a Debian/Hurd and install portage by hand. - -Once there take the profile and start bootstraping portage and all the -ebuild it needs (patch, python, bzip2...). - -The major problems are: - -- combine the perfect gcc/binutils/glibc/gnumach/hurd and to be able to boot -- lack of development on gnumach/hurd and current 'degraded' status. - -I don't think I can help much right now, but if you have any other -question just write me. - -MiKeL diff --git a/hurd/running/gnu.mdwn b/hurd/running/gnu.mdwn deleted file mode 100644 index 94012ef5..00000000 --- a/hurd/running/gnu.mdwn +++ /dev/null @@ -1,82 +0,0 @@ -# <a name="The_GNU_Operating_System"> </a> The GNU Operating System - -The GNU Operating System, or GNU System as it is more commonly known, will be a -complete [[Unix]]-like operating system composed entirely of [free -software](http://www.gnu.org/philosophy/free-sw.html). The creation of the GNU -System is one of the goals of the [GNU Project](http://www.gnu.org/), which was -[launched in 1983](http://www.gnu.org/gnu/initial-announcement.html) by -[Richard Stallman](http://www.stallman.org/). - - - -[[gnu/GNU]]. - -It is our wish and goal to establish a new direction for the GNU system distribution. To that end, this page will begin setting some direction. This was spawned by several discussions over a few days on the Hurd mailing lists and IRC. - -This is not intended to detract from Debian GNU/Hurd and we should help them where we can. - -I really want this to be more of a community driven effort in the spirit of say, Ubuntu. We all have different motivations and skill levels but we need a common goal to get this system going. - -These are just some quick notes I am making late at night. Let's clean this up. - -## <a name="Motivations"> Motivations </a> - -1. There is a possibility that Debian drops support for GNU/Hurd. -2. Other GNU/Linux distributions do not support the Hurd infrastructure well. -3. Benefiting from the Hurd design and using a microkernel. -4. Freedom. - -## <a name="Community"> Community </a> - -1. Let's establish some ground rules. -2. We need infrastructure - * Wiki for community documentation - * Mailing lists like gnu-system-discuss exists for mostly technical items - * IRC channels like #hug and ##hurd - * Perhaps less formal and less intimidating channels and mailing lists would involve broader parts of the community -3. We need a community vision and direction. - * Let's work together for a common goal - * Let's establish goals and priorities and get resources on them. (More later) - * Major goal to create a system making full use of Hurd features? - * We should never hesitate to throw away existing stuff whenever it hinders us to make good use of Hurd features - * However, we should try to reuse existing stuff (from Debian for example) as long as it doesn't limit our possibilities or impose considerable overhead - * Let's have fun. It's GNU and it's important but let's enjoy ourselves. - -## Download - - * Official GNU snapshot <http://www.update.uu.se/~ams/GNU> - * Extended GNU distribution <http://i-hug.sarovar.org/downloads/GNU/extended/> - -## <a name="Tools"> Tools </a> - -1. Developer Needs - * RPC Trace -2. Installer - * Native installer would be preferred but we can bootstrap GNU/Linux for now if necessary -3. Package Management - * There is a proposal to use stowfs. Let's get this going and test it out. Can it be made to work? How long will it take? - * Repository for packages - * Probably we can host it on the GNU servers - * Bug / Issue tracking - * Probably we should set up a Savannah project - * How to handle experimental patches to the core packages (Hurd, Mach, libc etc.) that are not in official CVS yet? - -## Resources - - * [[Universal_package_manager]] - * How to [[set_up_GNU|setup]] and archiver for GNU - * [[Create_an_image]] - -## <a name="Todo"> Todo </a> - -1. AMS had made a GNU release. We can try it and test it to good use. We can fix broken things in it, and enhance it. - * The snapshot is very old. Probably better to build something from current stuff, even if it means more work - * ams said that he would like to get a new snapshot out that would be on a Live CD and using stowfs. I think what we need to do is start using/fixing GNU System Creator (GSC) to build packages for this effort. -2. GNU is all about freedom AND ease of use. So, given installers are by nature quite complex, how should we install GNU on users's computers? I think ams's GSC comes into play here, maybe ams or sdschulze could (re-)write specifications of GSC. -3. Until we have an installer ready, we could go the Gentoo-like route, and have every part manually installed. A good installation documentation may help. Our next milestone may be just this (in case ams hasn't already done it): - * have a good installation document out, with all the required packages hosted at gnu.org or savannah.org - * get stowfs working -4. Maybe try to use hacked Debian packages until we get native ones? -5. Move on, start coding, documenting, packaging. - -I tried refactoring this page, but didn't get far. -- [[Main/AaronHawley]] - 18 Feb 2006 diff --git a/hurd/running/gnu/create_an_image.mdwn b/hurd/running/gnu/create_an_image.mdwn deleted file mode 100644 index c7a97a4e..00000000 --- a/hurd/running/gnu/create_an_image.mdwn +++ /dev/null @@ -1,97 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Creating a bootable qemu image from a root filesystem and bootloader - -1. Create a hard disk image - - qemu-img create -f qcow <imagename.img> <size>G - -2. Use a live CD (better to have a lighter OS like system rescue CD to make the - process faster) and the image created to boot. - - qemu -cdrom /dev/cdrom -hda <imagename.img> -boot d - -3. Once system is booted use a partition editing tool (like fdisk, cfdisk, - parted, gparted, qtparted ...) to partition the image. - - cfdisk - - create the necessary partitions (root and swap partitions boot, home ... if - required) - -4. Create a file system for the root partition - - mke2fs /dev/hda1 - -5. Mount the partition - - mkdir disk - mount /dev/hda1 disk - -6. Copy the file system from the host machine to the mounted directory (use a - compressed file system to make the copying faster) - - Grab the GNU snapshot from ams' site - <http://www.update.uu.se/~ams/home/slask/GNU/> - - scp <user>@<host>:<path to the compressed file system> disk - -7. Uncompress the files - - cd disk - tar -jxvf <compressed filesystem> - -8. Unmount the mounted partition - - cd .. - umount disk - -9. power off the guest OS. - - poweroff - -10. To make the file system bootable download a grub floppy image - - <http://hurd.in/pub/Hurd/HurdOnVMware/grub.img> - -11. Run qemu to boot into your brand new system - - qemu -hda <hard disk image.img> -fda grub.img -boot a - -Happy Hacking !! - - -Make your new system boot from the hard disk - -1. Mount your grub image - - mkdir floppy - mount -t ext2 -o loop grub.img floppy - -2. Use previous steps 2 and 5 to boot from a liveCD and mount the partition - - cd disk/boot - scp -r <user>@<host>:<path to mounted floppy image directory>/boot/grub - -3. Poweroff the guest - - poweroff - -4. Boot new system using floppy image previous step 11 - - use install to hard disk option if you used the above grub image - - or go to grub command line and type - - root (hd0,0) - setup (hd0) - - Now you have a bootable system image. Enjoy Maadi !! diff --git a/hurd/running/gnu/gnu.mdwn b/hurd/running/gnu/gnu.mdwn deleted file mode 100644 index 3ee5f657..00000000 --- a/hurd/running/gnu/gnu.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -## <a name="GNU_FSF_amp_RMS"> </a> GNU, FSF & RMS - -GNU stands for GNU's Not [[Unix]]. It is a project announced in 1983 by -[[RichardStallman]] (RMS). The Free Software Foundation -([FSF](http://www.fsf.org/fsf/fsf.html)) was founded in 1985 to act as a parent -organization for GNU and many other projects. GNU and some non-GNU projects -are now hosted on the [Savannah](http://savannah.gnu.org) platform similar to -SourceForge.net. - -<dl> -<dt>[[History]]</dt> -<dd> Background information about the GNU Project. </dd> -<dt>[[Names]]</dt> -<dd> A page describing the name GNU itself and it's usage. </dd> -<dt>[[Manifesto]]</dt> -<dd> A founding document that still influences the system's technical design and moral philosophy. </dd> -<dt> FAQ Link</dt> -<dd> What is the relation between <a href="http://www.gnu.org/software/hurd/faq.en.html#q1-2" target="_top">GNU and Hurd</a>? </dd> -<dt> Assisting</dt> -<dd> If you would like to help the GNU movement visit the official site at <a href="http://www.gnu.org" target="_top">http://www.gnu.org</a>. </dd> -<dt>[[SoftwareProjects]]</dt> -<dd> Information about other GNU projects. </dd> -<dt><a href="http://lists.gnu.org/mailman/listinfo/gnu-system-discuss" target="_top">gnu-system-discuss</a></dt> -<dd> Mailing list for discussion about the GNU system. </dd> -</dl> - -[[TODO]]. diff --git a/hurd/running/gnu/history.mdwn b/hurd/running/gnu/history.mdwn deleted file mode 100644 index f321c961..00000000 --- a/hurd/running/gnu/history.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -The GNU project has a long history. For software projects, it is exceptionally long. For social movements it is quite short. Although, its history is incomplete, and is being made now (to which you could contribute). - -* [Announcement](http://www.gnu.org/gnu/initial-announcement.html): The original announcement made in 1983 by [[RichardStallman]]. -* [The GNU Project](http://www.gnu.org/gnu/gnu-history.html): A summary by [[RichardStallman]]. -* [History of the GNU Project](http://www.gnu.org/gnu/thegnuproject.html): About the GNU Project, by [[RichardStallman]]. - -Page started from links at [[GNU]]. -- [[Main/AaronHawley]] - 17 Feb 2006 diff --git a/hurd/running/gnu/manifesto.mdwn b/hurd/running/gnu/manifesto.mdwn deleted file mode 100644 index c2a3294f..00000000 --- a/hurd/running/gnu/manifesto.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -Written early in the life of the GNU project, the GNU manifesto still influences the design of the GNU system. - -* [The GNU Manifesto](http://www.gnu.org/gnu/manifesto.html) - -Started page. -- [[Main/AaronHawley]] - 17 Feb 2006 diff --git a/hurd/running/gnu/names.mdwn b/hurd/running/gnu/names.mdwn deleted file mode 100644 index fcab6a11..00000000 --- a/hurd/running/gnu/names.mdwn +++ /dev/null @@ -1,8 +0,0 @@ -The GNU stands for GNU's Not [[Unix]]. It is a project as described in [[GNU]]. - -What can be confusing is the usage. GNU can stand for: - -* an entire system as envisioned in 1983. GNU/Hurd is a synonym. -* GNU components when used with the Linux kernel: GNU/Linux This term has been adopted by the [Debian project](http://www.debian.org) but is not recognized as widely as the FSF would like. - --- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/hurd/running/gnu/richardstallman.mdwn b/hurd/running/gnu/richardstallman.mdwn deleted file mode 100644 index d6688850..00000000 --- a/hurd/running/gnu/richardstallman.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -Richard Stallman (or ''RMS'') is the found of the GNU project, the Free Software Foundation and author of numerous GNU software packages. More useful information about Richard is available from his Wikipedia entry or his personal Web site. - -* [Wikipedia: Richard Stallman](http://en.wikipedia.org/wiki/Richard_Stallman/): Entry at Wikipedia -* [Stallman dot org](http://www.stallman.org/): Personal Web site. - -Page started. This seems like the appropriate Wiki to have the page. -- [[Main/AaronHawley]] - 17 Feb 2006 diff --git a/hurd/running/gnu/setup.mdwn b/hurd/running/gnu/setup.mdwn deleted file mode 100644 index 2fb30c7b..00000000 --- a/hurd/running/gnu/setup.mdwn +++ /dev/null @@ -1,84 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Setup is very easy (You need a GNU/Linux system to install GNU, we are developing an installer for GNU and if you want to help us join us on [gnu-system-discuss](http://lists.gnu.org/mailman/listinfo/gnu-system-discuss)), just follow these steps ... - -## Step 1: Find a home for GNU - -create a partition with minimum of 800 MB (if you want to install programs later you might need to allocate more space) - -It comes with GNU Emacs 21.4, gcc 4.0, gdb 6.3, parted, wget and many more - -Note: 2GB limit for partitions is no more there, it is fixed - -## Step 2: Create GNU Hurd filesystem on the partition - - # mke2fs -o hurd /dev/hdd6 - -## Step 3: Grab a snapshot of the GNU - -from <http://www.update.uu.se/~ams/home/slask/GNU/> or Extended GNU from <http://i-hug.sarovar.org/downloads/GNU/extended/> - -## Step 4: Extract the snapshot to the newly created partition - - # mount /dev/hdd6 /mnt - # cd /mnt - # tar -jxvf <path to downloaded location>/GNU--2006-01-08.tar.bz2 - -Wait for the extraction to complete, depending on the system configuration the time varies. The compressed image is 178MB and it uncompresses to about 750MB - -## Step 5: Configure grub to boot GNU - -This can be tricky since the partition naming is different for linux, grub and hurd - -My configuration look like this ... - - title GNU (also known as GNU/Hurd)(Single user) - root (hd0,5) - kernel /boot/gnumach.gz root=device:hd3s6 -s - 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) - module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - - title GNU (also known as GNU/Hurd)(Multi-user) - root (hd0,5) - kernel /boot/gnumach.gz root=device:hd3s6 - 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) - module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - - grub linux hurd - hd0,5 hdd6 hd3s6 - -If you have only one harddisk it will be hd0 for grub wherever you connect it. -But linux and hurd names depend on whether you connect it as primary master -(hda or hd0), primary slave (hdb or hd1) [this is my cdrom drive], secondary - master (hdc or hd2) or secondary slave (hdd or hd3) [this is my precious -Maxtor 2GB hard disk]. - -The partition naming of hurd is similar to BSD slices. hda1 is hd0s1, hda2 is - hd0s2 ... - -In my case the root device is hd0s6 (hdd6) - -## Step 6: Now boot into your brand new GNU System. - -It will do some initial setup and you will get a prompt. -Now reboot into your configured GNU System. - - # reboot - -## Step 7: Start using your GNU system - -Here is the GNU/Hurd users guide. It starts from the basics. <http://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html> - -*Warning! : It is not yet ready for normal use, it is a developer's release.* - -So when you encounter bugs report it to bug-hurd@gnu.org - -Join us on gnu-system-discuss <http://lists.gnu.org/mailman/listinfo/gnu-system-discuss> to help finish the GNU System. diff --git a/hurd/running/gnu/softwareprojects.mdwn b/hurd/running/gnu/softwareprojects.mdwn deleted file mode 100644 index 4790c5c9..00000000 --- a/hurd/running/gnu/softwareprojects.mdwn +++ /dev/null @@ -1,8 +0,0 @@ -Some of the GNU software effects the Hurd development directly or indirectly. Here's a place for notes about these changes. The official sources are the GNU software [Directory](http://www.gnu.org/directory/) (sponsored by the UN!), [Projects](http://www.gnu.org/projects/), [Packaging](http://www.gnu.org/software/packaging/) and [savannah](http://savannah.gnu.org/) pages, but this page is for Hurd related notes about them. - -<dl> - <dt> GCC</dt> - <dd> deb packages of gcc-{3.2,3.3} are available for testing from <a href="http://people.debian.org/~mbanck/hurd-gcc-4.0/" target="_top">http://people.debian.org/~mbanck/hurd-gcc-4.0/</a> ./ </dd> -</dl> - -* [[Universal_package_manager]] and archiver for GNU diff --git a/hurd/running/gnu/todo.mdwn b/hurd/running/gnu/todo.mdwn deleted file mode 100644 index e2dc2e89..00000000 --- a/hurd/running/gnu/todo.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -There are varying things to be done for the operating system requiring a variety of effort, and skills. The following are todo lists with a focus on meeting needs for releasing the GNU system. - -* [Alfred Szmidt's todo list](http://lists.gnu.org/archive/html/gnu-system-discuss/2006-06/msg00056.html) - Post to gnu-system-discuss on 21 Jun 2006. -* [Hurd Task list](http://savannah.gnu.org/task/?group=hurd) - Maintained on the GNU Savannah list. - -Page started. -- [[Main/AaronHawley]] - 29 Jun 2006 diff --git a/hurd/running/gnu/universal_package_manager.mdwn b/hurd/running/gnu/universal_package_manager.mdwn deleted file mode 100644 index bf1b92e0..00000000 --- a/hurd/running/gnu/universal_package_manager.mdwn +++ /dev/null @@ -1,158 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation, -Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -## Mission - -"To enable the GNU System to install packages of any format like rpm, deb, -ebuild... so that GNU System will be able to use softwares packaged by projects like Debian and Gentoo" - -## Features - -Basically all package management schemes follow similar approach, it will have a single binary archive containing the actual software and some metadata like packages it requires, what all it provides ... So when we install an rpm package this tool will help rpm tool to recognise the packages installed by stow and it will be stowed instead of the normal rpm way of installing in /usr. - -There can be both aproaches - - * Re-implement rpm, dpkg... to recognise stow as backend instead of its own data store. In that case we will have to re-implement, apt-rpm, yum ... - * Implement a translator which reads stow and show it as an rpm data store for yum, deb data store for apt-get ... - -One goal is obviously choice of packaging and hence availability of more packages. Also this gives maintainers a choice to continue building packages for GNU in the format they are already familiar with. The second goal is to demonstrate the flexibility GNU offers in implementing functionality in filesystems (open/read/write interface). - -## Why? - - * The GNU Hurd provides a lot of advanced features and functionalities. We aim to exploit those features. - * Combining translators with UnionFS gives a very exciting package manager. - * We could use the good features of existing packaging systems like deb, rpm, ebuilds, ports ... plus unionfs and hurd translator is a compelling combination. - -With the increased flexibility in implementing filesystems as per the requirements, we can implement the functionality similar to apt-get, emerge or yum... (dependency tracking, versions tracking...) in the filesystem itself. - -## What? - - * Have a basic filesystem based package manager - * Write translators to convert between GNU's packaging format and the existing one's like rpm, deb ... - -## How? - - * Installation of a package is just drag the package (be it a tgz, rpm, deb or an exe) and drop it to the package manager. - - * apt-cache search vim --> ls -al /packages/meta/ |grep vim - * apt-get install vim --> install vim - -Just a sample script. - - $ cd /packages/meta/vim/current/depends - $ for i in `ls *` - $ do - $ if [ -f /packages/binary/$i ] - $ then - $ echo "$i is installed" - $ else - $ install $i - $ fi - $ done - -The same can be achieved using any of the languages or front ends or even manual copying. - -If all the dependencies are there - - $ cp -r /ftp/ftp.gnu.org/packages/binary/vim/7.0 /packages/binary/vim/7.0 - -## Implementation Details - -Lets take the example of rpm, it is simply a cpio archive with software and -meta data as its contents. Just extract it to stow directory with a name -package-version. When apt-get or yum asks for information about already -installed packages read the stow tree and return back the requested data. - -Same case for ebuild. We can provide these details to any packaging system -in the way it wants using a translator. So support for a new format is -just writing the new translator. - -## Initial idea - -A bit more complex than the earlier scheme but it is more exciting and we can look at this scheme seriously once we have the simple scheme working. - -All packages are installed at -`/packages/binary/<packagename>/<packageversion>`. - -For example vim 6.4 version can be installed from source like - - # cd vim64 - # ./configure --prefix=/packages/binary/vim/6.4 - # make - # make install - -Now if you have another vim version, say 7.0 then just follow the steps - - # cd /packages/source/vim - # CP /<pathtovimtarball>/vim-7.0.tar.bz2 - # tar -jxvf vim-7.0.tar.bz2 - # mv vim70 7.0 - # ./configure --prefix=/packages/binary/vim/7.0 - # make - # make install - -You have 2 versions of vim and how can you specify which one is the current version? You can symlink the current version to select the version you would like to see as default - - # ln -s /packages/binary/vim/7.0 /packages/vim/current - -## Metadata: /packages/meta - -Dependency information is stored as a symbolic link to the required packages in a subdirectory called depends. - -## Requirement - -We will require unionfs support if we chose to go through path 2 (which is what I like because we can really show off with translators.) - - * Developing status - planning - * Near term goal - implement stow backend for dpkg - * High priority task - make unionfs work on boot. Mail from AMS to gnu-system-discuss on problem statement <http://www.mail-archive.com/gnu-system-discuss@gnu.org/msg00198.html> - -## Developer Guidelines. - - * GNU coding standards <http://www.gnu.org/prep/standards/> - - -## FAQ - Frequently asked questions - - 1. How can I join this project? - -OK. I will give you steps. - -i. Install a GNU System by folowing [[these_instructions|setup]] - -ii. Read about GNU Design: [[Towards_a_New_Strategy_of_OS_Design|hurd-paper]] - -iii. Read about translators <http://www.debian.org/ports/hurd/hurd-doc-translator> - -iv. Try out these cool [[translator_examples|translator/examples]] - -v. Add your name below and give a shout in the list. - - -## Comments?? - -Add your comments here - -## Interested? - -To join the project just list your name below. - - 1. PraveenA - 2. IsaacPraveen - 3. VikramVincent - 4. MaheshM - 5. Nidhin Raghavan - 6. Ajish.B - 7. Ambili.B - 8. Abhradip Mukherjee - 9. Ermenegildo Fiorito - 10. Oltion Doda - 11. Russell James diff --git a/hurd/running/live_cd.mdwn b/hurd/running/live_cd.mdwn deleted file mode 100644 index c9360594..00000000 --- a/hurd/running/live_cd.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -[[Arch Hurd|hurd/running/arch_hurd/]] offers Hurd LiveCDs at <http://www.archhurd.org/gethurd.php>. - -Also you can download a gzipped iso of a Hurd Live CD at -<http://www.superunprivileged.org/hurd/live-cd/>. - -The Superunpriveleged crew also offers a tiny Hurd Live CD that is under 10 -MiB: <http://www.superunprivileged.org/hurd/tiny-cd/> - -Use it like this: - - $ qemu -cdrom hurd-tiny-cd-20060722.iso - -A more recent Live CD can be found at <http://teythoon.cryptobitch.de/hurd/livecd/hurd-live-install-1273300101.iso.xz>. - -It can be run with qemu via - - $ wget http://teythoon.cryptobitch.de/hurd/livecd/hurd-live-install-1273300101.iso.xz - $ xz -d hurd-live-install-1273300101.iso.xz - $ qemu -cdrom hurd-live-install-1273300101.iso - -These [[!wikipedia LiveCD]]s should be useful for those who want to try out the -Hurd before they commit to installing it on their hard disks. In addition to -that, the bootable Hurd CDs should enable us to have a native installer instead -of relying on Linux. - -* [[RequirementsForLiveCD]] -* [[BuildingHurdLiveCD]] diff --git a/hurd/running/nix.mdwn b/hurd/running/nix.mdwn deleted file mode 100644 index 663589f6..00000000 --- a/hurd/running/nix.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="Nix-based GNU/Hurd System"]] - -<http://www.nixos.org/> - - * <http://hydra.nixos.org/jobset/gnu/hurd-master> - - * <http://hydra.nixos.org/job/gnu/hurd-master/qemu_image/latest/download> - - * <http://hydra.nixos.org/job/gnu/hurd-master/qemu_test> - ---- - -This QEMU image is not (yet) comparable to NixOS, because the latter provides -extra features, such as whole-system configuration (including services, etc.), -and whole-system transactional update and rollback. It is is cross-built using -Nix, and because of that, it uses per-package installation directories under -`/nix/store`. diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn deleted file mode 100644 index fcf58d8a..00000000 --- a/hurd/running/qemu.mdwn +++ /dev/null @@ -1,351 +0,0 @@ -[[!meta copyright="Copyright © 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 -Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -This page discusses things for [[Unix]] systems, there is a separate page for -[[Microsoft_Windows]] systems. - -# Readily Available Images - -You can use the following images to give the GNU/Hurd a try. - -## Debian GNU/Hurd - -[[!inline pages=hurd/running/debian/qemu_image raw=yes feeds=no]] - -## [[Nix]] - -## Unofficial Images - -Note that the following images are unofficial ones: they have been prepared by -volunteers and may not have been tested extensively. - -* [Disk image](http://draketo.de/dateien/hurd/bab-hurd-qemu-2008-10-29.img.tar.bz2) - with a short intro on translators. Just start it with 'qemu *disk_image.img*'. - It should work without any of the configuration below. If you want to know what you can do - with it, please have a look at [[its_wikipage|hurd/running/qemu/babhurd_image]]. And when - you use it, please [tell me your experience with it](http://draketo.de/contact)! - [[community/weblogs/ArneBab]] - -# Arch Hurd Live CD - -Also you can use QEMU to easily try one of the -[[Hurd_LiveCDs|hurd/running/live_cd/]]. - - -# What is Needed to create a QEMU image - -## Debian Installer - -Instructions for creating a qemu image from the install CDs from debian installer can be found in the README alongside the d-i Hurd images: <http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/> - -## Old method - -1. First thing is to install [[/QEMU]]. -2. A [[grub]] boot disk for the floppy disk image needed for booting. The [0\.97 version](ftp://alpha.gnu.org/gnu/grub/grub-0.97-i386-pc.ext2fs) works fine. I downloaded it and renamed to `floppy.img`. Alternatively, the Debian grub-disk package (up till version 0.97-28) is fine as well. -3. You will need a [Debian/Hurd installation CD](http://www.debian.org/ports/hurd/hurd-cd). K16 works fine. - -# KVM acceleration - -Check if your CPU supports kvm: - - $ egrep '^flags.*(vmx|svm)' /proc/cpuinfo - -#### If you don't have hardware support (slow): - $ apt-get install qemu - -Do not enable kernel-kqemu, as that assumes some particular behavior from the guest kernel, which we are reluctant to artificially add to gnumach. - -If QEMU with KVM is not available, [[Virtualbox]] reportedly has better -performance. - -#### If you have hardware support (recommended): - $ apt-get install qemu-kvm - $ modprobe kvm - -Intel VTx/VTd: Enable Intel kvm in the BIOS - -On a HP xw4600 Workstation: F10, Security->System Security; Enable VTx and VTd - -Check that the kvm module is loaded: - - $ lsmod|grep kvm - kvm_intel 38050 0 - kvm 213800 1 kvm_intel - - $ ls -l /dev/kvm - crw-rw----+ 1 root kvm 10, 232 Mar 14 15:02 /dev/kvm - -Add yourself to the kvm group: - - $ adduser your_user kvm; logout; login - -AMD SVM (AMD-V): Enable AMD-V in the BIOS if not enabled. - -Check that the kvm module is loaded: - - $ lsmod|grep kvm - kvm_amd 31862 0 - kvm 214088 1 kvm_amd - -More info on kvm at: http://www.linux-kvm.org/page/FAQ - -If your machine supports hardware acceleration, you should really use the kvm variant of qemu, as it speeds things quite a lot. Note however that kvm tends to make assumptions when accelerating things in the linux kernel, you may need some -no-kvm-something option. At the moment in Debian you need to pass - - -no-kvm-irqchip - -to the command line, see below, if you are running Linux kernels 2.6.37 or 2.6.38 else IRQs may hang sooner or later. The kvm irq problems will be solved in kernel 2.6.39. - -/!\ Note that there are known performance issues with KVM on Linux 2.6.39 -kernels, compared to 2.6.32: [[!debbug 634149]]. We're preparing on a change -on our side to work around this. - - -# HAP/EPT/NPT acceleration - -Performance will be yet better if HAP (EPT or NPT) is available: - - $ grep ept /proc/cpuinfo - $ grep npt /proc/cpuinfo - -# Installing Debian/Hurd with QEMU using the Debian installer - -Note: If you have hardware support, replace the qemu commands below with kvm, e.g. qemu-ing -> kvm-img. - -First off you will need to create a disk image using `qemu-img`. I have set mine to 4 GiB, although you should be able to get away with less. - - $ qemu-img create hd0.img 4G - -Next you will want to start up QEMU and begin the installation process. - - $ qemu -m 512 -hda hd0.img -cdrom mini.iso -net nic,model=rtl8139 -net user - -Now at his point do the regular install using `hd0` as your harddrive. Partition it and install the base system. - -In the installer make your choice of install option: Default install (or your choice) - - Language: English - Country, territory or area: your_choice - Locale: your_choice - -Note that even if you can set the country and locale, your local keyboard is not yet supported. - -In case of problems with timezone or locale settings do the following after the installation is completed - - To get the correct timezone: - $ dpkg-reconfigure tzdata - To get your locale setting: - $ nano /etc/locale.gen - $ locale-gen - -Network: Now configured automatically with dhcp - - IP address: 10.0.2.15 - Netmask: 255.255.0.0 - Gateway: 10.0.2.2 - Nameserver: 10.0.2.3 - - Qemu network setup: - QEMU VLAN <------> Firewall/DHCP server <-----> Internet - | (10.0.2.2) - | - ----> DNS server (10.0.2.3) - | - ----> SMB server (10.0.2.4) - -Partitioning method: Guided (or your choice) - -Partitioning `/dev/hd0`: All files in one partition. - -**Important**: Since partman does not yet mount other partitions than / automatically at reboot, it is crucial that you choose this option for now. - -Once you have finished installing the base system (might take some time) the system is rebooted and next boot will be from the hard disk. Now you are able to log in to your newly installed GNU/Hurd system. - -Also see another text about how to [[gnu/create_an_image]] for the -[[GNU_system|gnu]]. - -## Running the installed system - -Starting qemu/qemu-kvm: - - $ kvm -m 512 -net nic,model=rtl8139 -net user,hostfwd=tcp::5555-:22 -hda hd0.img -vga vmware - vmsvga_value_write: guest runs Linux. - -Note: See below on port forwarding in the networking section. - -Note: Using the vmware vga driver is useful for setting up X windows, see [Debian GNU/Hurd](http://www.debian.org/ports/hurd/hurd-install) - -If you have problems with grub hanging during boot with the vmware vga driver: Disable the graphic boot - - $ nano /etc/default/grub - uncomment GRUB_TERMINAL=console - $ /usr/sbin/update-grub - -### A few words about the qemu console - -During the graphical emulation, you can use the following keys: - - <Ctrl><Alt>-f Toggle full screen - <Ctrl><Alt>-u Restore the screen's un-scaled dimensions - <Ctrl><Alt>-n Switch to virtual console 'n'. Standard console mappings are: - 1 Target system display - 2 Monitor - 3 Serial port - <Ctrl><Alt> Toggle mouse and keyboard grab. - - -# Transferring Files - -## Mounting Disk Image on Host - -You may wish to mount your disk image on your host system to transfer files. To do this you will first need to find the offset of the partition you wish to mount. - - # fdisk -ul hd0.img - ... - 128 heads, 63 sectors/track, 0 cylinders, total 0 sectors - Units = sectors of 1 * 512 = 512 bytes - - Device Boot Start End Blocks Id System - hd0.img1 * 63 3515903 1757920+ 83 Linux - hd0.img2 3515904 4193279 338688 82 Linux swap / Solaris - -Now take the number of sectors for the beginning of the partition and multiply it by the sector size. My partition starts at sector 63 and I have a sector size of 512 therefore my offset is 32256. For a start at 2048 the ofsset is 1048576. - - # mount -o loop,offset=32256 hd0.img /mnt/diskimage - -## Having QEMU create *virtual FAT disk images* - -[Link to the manual](http://www.nongnu.org/qemu/qemu-doc.html#SEC25). - -QEMU has a facility to create FAT file systems on-the-fly: - - qemu [...] -hdc fat:[somewhere] - -The Hurd [[`fatfs`_translator|translator/fatfs]] currently is read-only, but -for testing executables (etc.) that is enough. And it is much easier than -loop-mounting the file systems images. (Also you don't need `root' rights.) - -However, note that there is a bug in [[translator/fatfs]]: [[!GNU_Savannah_bug -25961]]. - - -# Networking in QEMU - -Some further notes about [[networking]] and home hints about -[[networking/sharing_files]]. - -## Internet Access - -If you just want to access the internet from within QEMU, you can setup pfinet for QEMU's user-networking: - - # settrans -afgp /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0 - # echo "nameserver 10.0.2.3" > /etc/resolv.conf - -If you are on [[Debian GNU/Hurd|debian]], you can even use [[debian/DHCP]]. - -To get ssh working: - - # apt-get install random-egd openssh-server (Similarly for telnet if preferred) - -(See also <http://www.nongnu.org/qemu/qemu-doc.html#SEC32>.) - -Outgoing internet connections should just work then. -Testing it can be difficult with a minimal installation, -but `apt-get update` should work after you have filled out -`/etc/apt/sources.list`. -After that you should be able to install other network packages, -but note that `ping` doesn't work with QEMU's user-networking stack. - -If you want to connect from the host system to the Hurd system running in QEMU, you can use port forwarding in QEMU or to setup something more advanced, like bridged networking. - -## Port Forwarding in QEMU -(In the following we assume we use kvm!) - -#### Logging in to Hurd from a terminal in your host system -This is the recommended way to work with a Command Line Interface (CLI) since all your keyboard and locale settings are preserved. - -a) with ssh (assuming you have installed openssh-server) - - $ kvm -m 1024 -net nic,model=rtl8139 -net user,hostfwd=tcp::5555-:22 -hda hd0.img & - -Logging in to the running Hurd: - - $ ssh -p5555 localhost - -Copying files: - - 1) On your host - To Hurd: scp -p -P5555 file localhost: - From Hurd: scp -p -P5555 localhost:file . - 2) On Hurd - To host: scp -p file {10.0.2.2,your_host_ip}: . - From host: scp -p {10.0.2.2,your_host_ip}:file . - -b) with telnet (assuming you have installed a telnet server, like telnetd) - - $ kvm -m 1024 -net nic,model=rtl8139 -net user,hostfwd=tcp::5556-:23 -hda hurd-install.qemu & - -Logging in to the running Hurd: - - $ telnet localhost 5556 - -c) With the tap interface, see below. - -## Bridged Networking - -### What is Needed - -1. Your Linux kernel will need 802.1d Ethernet Bridging support and TUN/TAP device driver support. -2. You will need to install [bridge-utils](http://bridge.sourceforge.net). - - -### Setting Up the Host Bridge - -You need to setup a bridge on the host first. This assumes `eth0` is down. I have modified my hosts network startup scripts to automatically setup a bridge, you may want to do this also. - - # brctl addbr br0 - # ifconfig eth0 0.0.0.0 promisc up - # brctl addif br0 eth0 - -At this point you will need to setup `br0` as you would normally `eth0` (`dhcpcd br0` for example). - -### The qemu-ifup Script - -This script gets called when QEMU starts and will attach the tun device to the bridge. QEMU will look for this file at `/etc/qemu-ifup` and that is where I keep mine. - - #!/bin/sh - sudo ifconfig $1 0.0.0.0 promisc up - sudo brctl addif br0 $1 - - -### Setting up the Network in the Hurd - -Now it is time to start-up your QEMU Hurd system and get networking going in there. - -**Important:** Remember you may need to use the `-M isapc` or `-isa` flag if using an older version of the gnumach package. - - $ qemu -hda hd0.img -cdrom debian-K9-hurd-i386-CD1.iso -fda floppy.img -boot a -net nic -net tap - -Once you have logged in as `root` run the `pfinet` translator with values that apply to your network. Think of your QEMU client as another computer in your network. - - # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a xxx.xxx.xxx.xxx -g xxx.xxx.xxx.xxx -m xxx.xxx.xxx.xxx - -That should do it! Do not forget to edit/update `/etc/resolv.conf` to get DNS working. - - -# Related Links - -These are links that users may find helpful. - -Debian [[debian/after_install]] -- good source of information pertaining to your -system after installation. - -[[Image_for_L4]] -- a QEMU image for the Hurd/L4 project. - -<http://eyeside.net/hurd/Hurd-on-QEMU.html> diff --git a/hurd/running/qemu/babhurd_image.mdwn b/hurd/running/qemu/babhurd_image.mdwn deleted file mode 100644 index c0952fcf..00000000 --- a/hurd/running/qemu/babhurd_image.mdwn +++ /dev/null @@ -1,67 +0,0 @@ -What this little Hurd image can do ----------------------------------- - -### About this text - -This is the README file accompanying a -[disk\_image](http://draketo.de/dateien/hurd/bab-hurd-qemu-2008-10-29.img.tar.bz2) for -[[running_the_GNU/Hurd_via_qemu|hurd/running/qemu]]. To run the disk image, just use *'qemu -disk_image.img'*. - -You can find the custom *.bashrc* used to tell the user about it as well as this text itself -in the Mercurial repository [hurd_intro](http://bitbucket.org/ArneBab/hurd_intro). - -### Intro - -The Hurd has some unique capabilities, and we created this simple image -to enable you to easily try two of them: - -* The simplest of translators: Hello World! -* Transparent FTP - -### Hello World - -To try out the simplest of translators, you can go the following simple steps: - - $ cat hello - $ setrans hello /hurd/hello - $ cat hello - "Hello World!" - $ settrans -g hello - $ cat hello - -What you do with these steps is first verifying that the file "hello" is empty. - -Then you setup the translator /hurd/hello in the file/node hello. - -After that you check the contents of the file, and the translator returns "Hello World!". - -To finish it, you tell the translator to go away from the file "hello" via "settrans -g hello" and verify that now the file is empty again. - -### Transparent FTP - -We already setup a a transparent FTP translator for you at /ftp: - -With it you can easily access public FTP via the file system, for example the one from the GNU project: - - $ ls /ftp://ftp.gnu.org/ - -But you can also do this very easily yourself: - - $ # Setup the translator on the node ftp: - $ settrans -c ftp: /hurd/hostmux /hurd/ftpfs / - -and you can access FTP sites via the pseudo-directory ftp:, for example with - - $ ls ftp://ftp.gnu.org/ - -What you do here is setting up the translator /hurd/hostmux on ftp: and passing it the translator /hurd/ftpfs to use for resolving accesses as well as / as additional path component. - - -These were only two basic usages of translators on the Hurd. We're sure you'll quickly see many other ways to use this. - -As a last comment: You can setup a translator on any node you have access to, so you can for example mount any filesystems as normal user. - -You might currently be logged in as root, but you could just as well do the same as normal user. - -Why don't you try it out? diff --git a/hurd/running/qemu/discussion.mdwn b/hurd/running/qemu/discussion.mdwn deleted file mode 100644 index 1ce14b01..00000000 --- a/hurd/running/qemu/discussion.mdwn +++ /dev/null @@ -1,144 +0,0 @@ -[[!meta copyright="Copyright © 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free -Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_documentation]] - -# Using Partitions - -[[IRC]], #hurd, 2007-07-04. - - <azeem-uni> so, is there a way to use a Debian GNU/Hurd partition - (/dev/hda6) with qemu directly? - <tschwinge> Don't dare to do that, please. - <tschwinge> It will lead to inconsistencies. - <tschwinge> Because the Linux kernel thinks that it has complete control - over the disk, or something. - <tschwinge> In theory you could run something like ``-hda /dev/hda'', - having GRUB installed on there to offer you to boot your Hurd system from - hda6 and that will even work, but then don't get the idea to stop qemu, - mount that partition on your Linux system and restart qemu. That's where - I got lots of inconsistencies then, afterwards. - <azeem-uni> it's probably the same problem as having that partition - mounted, suspending to disk, booting into it in the Hurd, and resume - Linux - <neal> right - <tschwinge> That's a different problem. - <tschwinge> Then the partitoon is still mounted. - <neal> no, I think it is basically the same problem - <tschwinge> The file system stuff is cached in the kernel. - <neal> you have data that has not been written to disk yet - <tschwinge> Right. - <neal> and neither is prepared for the resource to be shared - <tschwinge> In the azeem-uni scenarion the data is on the file system layer - and in my scenarion it's some disk block caching inside the Linux kernel, - I guess. - <azeem-uni> anyway, do you guys think if I use -hda /dev/hda and tell Grub - to boot off /dev/hda6, that the rest of hda should be fine, right? - <azeem-uni> maybe adding -snapshot makes it totally safe - <neal> azeem: Should be fine. - <tschwinge> Yes. - -The problem is actually that the linux block cache doesn't make any consistency -between /dev/hda and /dev/hda6, so if you give /dev/hda to qemu, qemu writings -won't be consistent with mounting /dev/hda6 in linux. You can give /dev/hda6 -directly to qemu and it will be fine. - - -# Host-side Writeback Caching - -IRC, freenode, #hurd, 2011-06-07 - - <braunr> hm, i guess i should have used cache=writeback with kvm before - starting the debian installer :/ - <braunr> ah yes, much better - <braunr> this shows how poor the state of our I/O drivers and subsystem is - :/ - <antrik> indeed... still no clustered pageout :-( - <braunr> and no I/O scheduler either - <braunr> although an I/O scheduler has limited value without clustered - pageouts - <braunr> since one of its goals is to pack related I/O requests together eh - <braunr> i wonder if the wiki mentions using cache=writeback to speed up - qemu performances - <braunr> it would help those unable to use kvm a lot - <braunr> and even those running kvm too - <braunr> kvm -m $RAM \ -monitor stdio \ -drive - cache=writeback,index=0,media=disk,file=hd0.img \ - <braunr> etc.. - <braunr> the idea is that qemu doesn't open its disk file synchronously - <braunr> changes are queued in the host page cache before being flushed to - the disk image - <braunr> but if you brutally close your qemu instance, you're likely to - loose file system consistency - <braunr> ext2fs will think it has committed its metadata to the disk, but - the disk image won't be updated synchronously - <braunr> on my machine (which is quite fast), my kvm has installed debian - like 10 times faster than without the option - <antrik> braunr: I don't think killing qemu should hurt in this - case... probably only matters when the host machine dies - <braunr> antrik: ah yes, right - <braunr> it really makes everything faster, even downloading, since I/O - requests aren't interleaved between networking RPCs - <antrik> regarding I/O sheduler... this discussion came up before, but I - don't remember the outcome -- doesn't the glued Linux driver actually - come with one? - <braunr> i don't remember either - <antrik> braunr: err... I don't think interleaving has anything to do with - it... I guess it's simply the fact that downloading writes the result to - disk, which suffers from lacking clustered pageout like everything else - <antrik> (my internet connection is too slow though to notice :-) ) - <braunr> well, if there is no I/O during downloading, downloading is faster - :) - -IRC, freenode, #hurd, 2011-06-08 - - <braunr> youpi: does xen provide disk caching options ? - <youpi> through a blktap, probably - <braunr> ok - -([[microkernel/mach/gnumach/ports/Xen]], *Host-side Writeback Caching*.) - - <braunr> we should find the pages mentioning qemu on the wiki and add the - options to enable disk image caching - <braunr> it really makes the hurd run a lot faster - <braunr> as a workaround for emulators until I/O is reworked, ofc - -IRC, freenode, #hurd, 2011-06-09 - - <gnu_srs> braunr recommends to use writeback caching with kvm. Is this - really recommended with the frequent crashes I experience? - <youpi> provided that you terminate your kvm normaly (i.e. quitting it, not - killing it), there should be no difference - <jkoenig> I think the host's stability is what matters - <jkoenig> the data presumably sits in linux's cache even if qemu dies - violently - <gnu_srs> But the freezes I see force me to kill kvm :-( - <youpi> maybe kvm doesn't even do caching indeed, I don't know - <youpi> gnu_srs: you can quit even when frozen - <youpi> use the console - <youpi> (the kvm console) - <jkoenig> gnu_srs, "Writeback caching will report data writes as completed - as soon as the data is present in the host page cache. This is safe as - long as you trust your host. If your host crashes or loses power, then - the guest may experience data corruption." (from the qemu manpage) - -IRC, freenode, #hurd, 2011-06-11 - - <gnu_srs> braunr: If you are online. For me setting the parameters -drive - cache=writeback,index=0,media=disk,file=hd0.img does not show any speed - improvement at all compared to the default. - <braunr> gnu_srs: what's your complete qemu command line ? - <gnu_srs> kvm -m 1024 -net nic,model=rtl8139 -net - user,hostfwd=tcp::5556-:22 -drive - cache=writeback,index=0,media=disk,file=hd0.img -cdrom netinst.iso - <braunr> what qemu version ? - <gnu_srs> qemu-kvm 0.14.1+dfsg-1: Sorry, I cannot be online until - tomorrow again. diff --git a/hurd/running/qemu/image_for_l4.mdwn b/hurd/running/qemu/image_for_l4.mdwn deleted file mode 100644 index 515f51bc..00000000 --- a/hurd/running/qemu/image_for_l4.mdwn +++ /dev/null @@ -1,376 +0,0 @@ -This page is initially taken from <http://perso.ens-lyon.fr/alexandre.buisse/hurd.html> with the following signature: - -> 04-02-2005 Alexandre Buisse -> -> Send any comments or ameliorations to <Nattfodd@gmailNOSPAM.com> - ----- - -This is a howto on how to get a working image of Hurd/L4 with qemu, on ia32 arch. - -# <a name="1_Floppy_image"> 1. Floppy image </a> - -You will need the following : - -* automake 1.7 (or greater) -* autoconf 2.53 (or greater) -* grub -* the CVS version of hurd-l4, which you can retrieve from the savannah server: `cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co hurd-l4` -* two flavours of Pistachio, the L4 kernel, which can be found at <http://www.l4ka.org/projects/pistachio/download.php>. Take the demodisk for ia32 (`pistachio-ia32-0.4-demodisk.bin.bz2`), we'll checkout the CVS later (the 0.4 tarball isn't recent enough). - -We will begin with the hurd itself (these steps are taken from the `README`). - - $ cd hurd-l4 - $ autoreconf -f -i -s - -You shouldn't have any warnings with this autoreconf. If that is not the case, it probably hasn't used the good version of automake or autoconf. For instance, on Gentoo Linux, you must set WANT\_AUTOCONF to 2.5 and WANT\_AUTOMAKE to 1.7. - - $ ./configure --enable-maintainer-mode --prefix=/l4 - $ make - $ make install - $ mkdir /l4/boot - $ install -s laden/laden /l4/boot - $ install -s wortel/wortel /l4/boot - $ install -s physmem/physmem /l4/boot - $ install -s task/task /l4/boot - $ install -s deva/deva /l4/boot - $ install -s ruth/ruth /l4/boot - -Now we'll prepare the Pistachio kernel : - - $ cd .. - $ cvs -d:pserver:guest:guest@cvs.l4ka.org:/public-cvs login - $ cvs -z3 -d:pserver:guest@cvs.l4ka.org:/public-cvs co pistachio - $ cd pistachio - -We must apply some patchs for it to work properly with The Hurd. They are located in `hurd-l4/README`: - - $ patch -p1 < ../hurd-l4/README - -We will first compile sigma0 (and some other tools) : - - $ cd user - $ autoreconf -f -i -s - $ mkdir BUILDDIR - $ cd BUILDDIR - -We need to change the linkbase of sigma0 : - - $ ../configure --with-s0-linkbase=0x40000 --prefix=/l4 - $ make - $ make install - -And now the kernel itself : - - $ cd ../../kernel - -You can use any builddir as long as the directory doesn't yet exist. - - $ make BUILDDIR=/tmp/pistachio-build - $ cd /tmp/pistachio-build - $ vi Makeconf.local - -You should modify the first three lines to : - - ARCH=ia32 - CPU=i586 - PLATFORM=pc99 - -now run: - - $ make menuconfig - -Set the options as they fit you but for qemu to work, you must have the following hardware : - - IA32 Basic Architecture - Pentium1 Processor Type - -You can now: - - $ make - -You should obtain a file named ia32-kernel into your build directory. - - $ cp ia32-kernel /l4/boot - $ cp /l4/libexec/l4/sigma0 /l4/boot - -We now have to modify a little bit the demodisk to use the kernel and servers we just obtained : - - $ mkdir qemu - $ mkdir qemu/image - $ cd qemu - $ cp ~/pistachio-ia32-0.4-demodisk.bin.bz2 . - $ bunzip2 pistachio-ia32-0.4-demodisk.bin.bz2 - $ mount -o loop pistachio-ia32-0.4-demodisk.bin image - $ cd image/boot - $ cp /l4/boot/* . - $ cd grub - $ vi menu.lst - -Your should edit `menu.lst` to make it look like : - - title GNU Hurd on L4 - kernel /boot/laden -D -o serial,uart1,speed=9600 - module /boot/ia32-kernel - module /boot/sigma0 - module /boot/wortel -D -o serial,uart1,speed=9600 - module /boot/physmem - module /boot/task - module /boot/deva - module /boot/task - module /boot/ruth - -The two -D are intended for debug, you can delete them if you want. It is possible that filenames are limited to 8 characters, check your image/boot directory for ia32-kernel. If it has been renamed into ia32-ker, modify the according line in menu.lst - -When you start qemu, you will have two windows : the shell from which you launched it and a VGA window. You can interact with L4 in both windows (switching with the `config/console` command in the debugger). You can choose to have wortel and laden output to the serial device (the shell), which is default behaviour, or to VGA (change `-o serial,urt1,speed=9600` by `-o vga` in your menu.lst). - -The image is now ready : - - $ cd ../../../ - $ umount image - -We can launch qemu: - - $ qemu -dummy-net -serial stdio -fda pistachio-ia32-0.4-demodisk.bin -boot a - -Congratulations, you just booted Hurd/L4 ! To start the Kernel Debugger, press `ESC`. To switch the KDB mode from character (I find it unusable) to command line, type - - > c - /conf> m - -# <a name="2_Disk_Image"> 2. Disk Image </a> - -Everything went fine, and Hurd/L4 should have shown you a nice boot on our floppy image. Our next step will be to make banner run and show us its nice ASCII Art on this brand new OS. - -However, there is one problem : banner linked with the libc weights about 6MB, and we only have a 1.44MB floppy. We will then begin with making an image of a whole hard disk instead of a simple floppy. - -We still will work with qemu, of course, but we'll also use Bochs to install Grub on the image (I have not yet tried with qemu). - -To begin with, some mathematics. We'll make a 30MB image but you can adapt this value to your need. A disk is made of heads, cylinders and sectors (we won't go in detail about what these really mean). A sector has a constant size of 512 bytes and there are at most 255 heads and 63 sectors. The total size of a disk is C \* H \* S \* 512. We'll use the maximum capacity for S and 16 sectors and that will give us how much cylinders we need : C = E(30,000,000 / (16 \* 63 \* 512)) = 58. The exact size of our image will then be : 58 \* 16 \* 63 \* 512 = 29,933,568 bytes and we will have 58 \* 16 \* 63 = 58464 pieces of 512 bytes. - -Let's create it : we use the magic command `dd` on the special device which contain an infinity of 0. - - $ dd if=/dev/zero of=hurd_l4.img bs=512 count=58464 - 58464+0 records in - 58464+0 records out - -We will mount it in loopback : - - $ losetup /dev/loop0 hurd_l4.img - -We need now to have it recognized as a hard disk : - - $ fdisk -u -C58 -S63 -H16 /dev/loop0 - Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel - Building a new DOS disklabel. Changes will remain in memory only, - until you decide to write them. After that, of course, the previous - content won't be recoverable. - - Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) - - Command (m for help): - -We should create a new primary partition (press: `'n'`, `'p'`, `'1'`, default, default) and toggle it bootable (`'a'`, `'1'`). Now, if you press `'p'`, you should see something like : - - Command (m for help): p - - Disk /dev/loop0: 29 MB, 29933568 bytes - 16 heads, 63 sectors/track, 58 cylinders, total 58464 sectors - Units = sectors of 1 * 512 = 512 bytes - - Device Boot Start End Blocks Id System - /dev/loop0p1 * 63 58463 29200+ 83 Linux - -If everything is fine (especially check the `Start` and `End` fields), you can press `'w'` to write the table on the disk: - - Command (m for help): w - The partition table has been altered! - - Calling ioctl() to re-read partition table. - - WARNING: Re-reading the partition table failed with error 22: Invalid argument. - The kernel still uses the old table. - The new table will be used at the next reboot. - Syncing disks. - -You will have noticed that the partition only starts at the 63rd sector. The beginning of the disk contains the MBR which is used for booting. We must then remount the disk making sure that this part is skipped before formating it. We know that a sector uses 512 bytes so we should begin at 63 \* 512 = 32256 : - - $ losetup -d /dev/loop0 - $ losetup -o32256 /dev/loop0 hurd_l4.img - -Now comes time to format it into a decent filesystem : - - $ mke2fs /dev/loop0 - mke2fs 1.35 (28-Feb-2004) - Filesystem label= - OS type: Linux - Block size=1024 (log=0) - Fragment size=1024 (log=0) - 7328 inodes, 29200 blocks - 1460 blocks (5.00%) reserved for the super user - First data block=1 - 4 block groups - 8192 blocks per group, 8192 fragments per group - 1832 inodes per group - Superblock backups stored on blocks: - 8193, 24577 - - Writing inode tables: done - Writing superblocks and filesystem accounting information: done - - This filesystem will be automatically checked every 22 mounts or - 180 days, whichever comes first. Use tune2fs -c or -i to override. - -We should now be able to mount it the right way : - - $ mkdir mnt - $ losetup -d /dev/loop0 - $ mount -o loop,offset=32256 hurd_l4.img mnt/ - -Here comes grub time (I assume you have the grub files in `/boot/grub` and the `menu.lst` we've obtained in the previous section is in `~/`) : - - $ mkdir -p mnt/boot/grub - $ cp /boot/grub/stage1 /boot/grub/stage2 /boot/grub/e2fs_stage1_5 mnt/boot/grub/ - $ cp ~/menu.lst mnt/boot/grub - -We will make a grub bootimage and boot it with bochs : - - $ cat stage1 stage2 > grubboot.img - -Copy the following into `.bochsrc` (replace the parts in caps by the right info) : - - config_interface: textconfig - display_library: x - romimage: file=/usr/share/bochs/BIOS-bochs-latest, address=0xf0000 - megs: 32 - vgaromimage: /usr/share/bochs/VGABIOS-elpin-2.40 - floppya: 1_44=PATH_TO_YOUR_GRUBBOOT_IMAGE, status=inserted - ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14 - ata1: enabled=0, ioaddr1=0x170, ioaddr2=0x370, irq=15 - ata0-master: type=disk, path="PATH_TO_YOUR_DISK_IMAGE", cylinders=NUMBER_OF_CYLINDERS, heads=16, spt=63 - newharddrivesupport: enabled=1 - boot: a - - log: /dev/stdout - panic: action=ask - error: action=report - info: action=report - debug: action=ignore - debugger_log: - - com1: enabled=1, dev=/dev/ttyS0 - vga_update_interval: 300000 - keyboard_serial_delay: 250 - keyboard_paste_delay: 100000 - floppy_command_delay: 500 - ips: 1000000 - mouse: enabled=0 - private_colormap: enabled=0 - fullscreen: enabled=0 - screenmode: name="sample" - keyboard_mapping: enabled=0, map=/usr/share/bochs/keymaps/x11-pc-fr.map - i440fxsupport: enabled=0 - -And start Bochs with this configuration : - - $ bochs -qf .bochsrc - -When asked, choose `5. begin simulation`. It is possible that you enter first into a debugger, answer `'c'` to make it continue. You should see a grub commandline. Tell it to install grub on the disk : - - grub> root (hd0,0) - Filesystem type is ext2fs, partition type 0x83 - - grub> setup (hd0) - Checking if "/boot/grub/stage1" exists... yes - Checking if "/boot/grub/stage2" exists... yes - Checking if "/boot/grub/e2fs_stage1_5" exists... yes - Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 15 sectors are embedded. succeeded - Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/boot/grub/stage2/boot/grub/menu.lst"... succeeded. - Done. - -Quit by pressing `^C q` in the shell from which you launched bochs. Our image is now ready. Copy all the releving files in `mnt/boot` like for the floppy and then umount it and launch qemu : - - $ cp /l4/boot/* mnt/boot/ - $ umount mnt - $ qemu -serial stdio -dummy-net -hda hurd_l4.img -boot c - -# <a name="3_Running_Banner"> 3. Running Banner </a> - -Still under construction but you should have no problems following `hurd-l4/libc/README` now that the hdd image works. - ----- - --- [[Main/OgnyanKulev]] - 05 Feb 2005 - -I didn't bother to licence it as it is so small, but consider it is under some sort of creative commons that allows redistribution and modification. <br /> -- Alexandre Buisse < <nattfodd@gmailNOSPAM.com> > - --- [[Main/JoachimNilsson]] - 05 Feb 2005 - -Comments from Marcus Brinkmann: - -> Thanks a lot for that. Some comments: -> -> $ ../configure --with-s0-linkbase=0x40000 --prefix=/l4 -> -> I'd recommend to explain how to use `--without-com0` here (or whatever it is called, don't remember) to choose VGA output, or how to configure the serial port. If you use vga, no `-o` option to laden and wortel should be used so you get all output on vga (but of course you can also mix it, whatever you want). -> -> Serial 1 is currently going to be used for remote debugging of userland apps. -> -> QEMU supports up to four serial ports, I use: `-serial stdio` and `-serial pty` and then I get the debugging output and kernel debugger in the terminal I started qemu in, and can use the pty for remote debugging with gdb (the latter doesn't work yet). -> -> Next: -> -> You should modify the first three lines to : -> ARCH=ia32 -> CPU=i586 -> PLATFORM=pc99 -> -> I never did that. I did change the menu item Processor Type to Pentium1 though. Maybe it has the same effect (and then your document would be a bit redundant here). -> -> Somebody should at some point document all those menu options, some are quite useful for debugging! -> -> Thanks, Marcus - --- [[Main/OgnyanKulev]] - 05 Feb 2005 - -I've been doing this sort of thing (See also `info grub` for making bootable eltorito grub cd ISOs): - - $ cd /usr/src/controlled/qemu-images - $ ls -R l4 - ls -R l4 - l4: - boot deva ia32-kernel laden physmem sigma0 task wortel - - l4/boot: - grub - - l4/boot/grub: - menu.lst stage2_eltorito - - $ cd /usr/src/controlled/qemu-images # dir above "l4" dir. - $ mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \ - -boot-load-size 4 -boot-info-table \ - -o /usr/src/controlled/qemu-images/l4.iso l4 - - $ qemu -boot d -cdrom /usr/src/controlled/qemu-images/l4.iso - --- [[Main/DerekDavies]] - 07 Feb 2005 - -You don't need a compiler targeting the Hurd. The above works with a compiler targeting Linux which are quite a bit easier to find. By adding "--target=i686-unknown-linux-gnu" to my configure line, I was able to cross compile hurd-l4 from Cygwin. - --- [[Main/MichaelAdams]] - 22 Feb 2005 - -A bootable CD iso image is now available at <http://gnuppix.org> - --- [[Main/ChristopheDevine]] - 03 Mar 2005 - -Included the anonymous password in the CVSROOT for L4. - --- [[Main/NowhereMan]] - 19 Mar 2005 - -I was able to use qemu instead of bochs to install grub on the new disk image. Just use: - - qemu -dummy-net -serial stdio -fda grubboot.img -hda hurd_l4.img -boot a - -and then the commands to type in the grub shell are the same. - --- [[Main/MatteoSettenvini]] - 05 May 2005 diff --git a/hurd/running/qemu/microsoft_windows.mdwn b/hurd/running/qemu/microsoft_windows.mdwn deleted file mode 100644 index 832b4bef..00000000 --- a/hurd/running/qemu/microsoft_windows.mdwn +++ /dev/null @@ -1,52 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -Welcome, This document is for getting you started in a few minutes. - -1. Install Qemu for Windows - - The executable can be downloaded from - <http://free.oszoo.org/ftp/qemu/win32/release/> Doble click on the - installer and follow the instructions. - -2. Obtain Qemu image - - * Debian GNU/Hurd qemu image can be downloaded from - <http://www.numenor.art.pl/balrog/hurd/>, but also see the main - [[QEMU]] page. - * Uncompress the image and rename it to debian-hurd-for-qemu.img (.img is - the only thing that matters, you can chose any name) Note: .img is for - QEMUMenu.bat, which saves you from remembering the command line options - of qemu and helps you change the settings (like chosing different - images, allocating RAM for the guest OS ...) interactivly. - * Copy this file to the directory where you installed Qemu. - -3. Start Qemu - - Double click the QEMUMenu.bat and enter the number to chose between images. - -4. Qemu short cuts - - * ctrl alt - to exit grab from qemu, get mouse cursor out from the qemu - window - * ctrl alt f - full screen - * ctrl alt 2 - qemu contrl console, use this to change devices - (eg. changing cdrom), send keys to the guest (for example if you want - to send ctrl alt del to the guest type "sendkey ctrl-alt-del" ... type - "help" for a listing of all the options. - * ctrl alt 1 - Hurd login console - -## QEmu Image Hangs on Boot -The Debian GNU/Hurd K16 QEmu image hangs during the boot process. You may have better luck by converting the image to qcow format - - ..\qemu-0.9.0-x86\qemu-img.exe convert debian-hurd-k16-qemu.img -O - qcow debian-hurd-k16-qemu.qcow - ..\qemu-0.9.0-x86\qemu.exe -L ..\qemu-0.9.0-x86 -m 512 -hda - debian-hurd-k16-qemu.qcow -localtime -M pc diff --git a/hurd/running/qemu/networking.mdwn b/hurd/running/qemu/networking.mdwn deleted file mode 100644 index 2bc9b16d..00000000 --- a/hurd/running/qemu/networking.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -## User mode network - -This is the default networking option for qemu. This does not require root -previleges. If you have DHCP running it will take the ip as 10.0.2.15 - -You can setup an ip 10.0.2.* -Gateway is 10.0.2.2 -Name server is 10.0.2.3 -Netmask is 255.255.255.0 - -You can setup the pfinet translator with the command - - $ settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 10.0.2.15 -g 10.0.2.2 -m 255.255.255.0 - -Configure nameserver in /etc/resolve.conf - - nameserver 10.0.2.3 - -Setup a proxy with the command - - $ export http_proxy="http://<proxy.com>:<port>" - -Note: you can add this to your /etc/profile file so that every time you don't -have to setup this. - -If you are using a direct connection to internet install a proxy server on the -host os and use this. (I was not able to use it without proxy) - -You might be able to do it using iptables, some clues -<http://sujith-h.livejournal.com/9520.html> - -Use scp,ftp... to transfer files (also see -[[hurd/running/debian/faq#index2h1]]), read about [[sharing_files]]. diff --git a/hurd/running/qemu/networking/sharing_files.mdwn b/hurd/running/qemu/networking/sharing_files.mdwn deleted file mode 100644 index 5bdec5f1..00000000 --- a/hurd/running/qemu/networking/sharing_files.mdwn +++ /dev/null @@ -1,38 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -# SCP - -Setup OpenSSH server on host system. - -* Copying files from Guest to Host - - $ scp <file> <user>@<host>: - -* Copying files from Host to Guest. - - $ scp <user>@<host>:<file> - -Use scp -r for copying directories. - - -# FTP - -Setup ftp server (like proftpd) on the host. - -* Use ftp client from GNU inetutils - - $ ftp <host> - - Use mget to copy files from host and mput to copy files to the host. - -* The GNU way - setup an ftp translator - - $ settrans -ac ftp/<host> /hurd/ftpfs <username>:<password>@<host>:<path> diff --git a/hurd/running/virtualbox.mdwn b/hurd/running/virtualbox.mdwn deleted file mode 100644 index f57fcbc3..00000000 --- a/hurd/running/virtualbox.mdwn +++ /dev/null @@ -1,46 +0,0 @@ -[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="VirtualBox"]] - -<http://www.virtualbox.org/> - - -# Installation - -The disk controller has to be configured as IDE. Neither SATA nor SCSI are -supported. - -The network controller should be configured as PCnet-PCI II or PCNet-FAST III -for instance. INTEL PRO or Paravirtualized Network do not work. - - -## Converting from qemu image - -It is possible to convert qemu raw image to one of the formats recognized by VirtualBox, namely vdi format. - -If you are not sure if the image is a raw format, use qemu to get the information: - - qemu-img info debian-hurd-original.img - -To convert the image you need the VirtualBox package properly installed with a VBoxManage tool (which is part of the package). Convert image from raw to vdi: - - VBoxManage convertfromraw debian-hurd-original.img debian-hurd-converted.vdi --format VDI - - -# Performance - -If [[QEMU with KVM|qemu]] is not available, VirtualBox reportedly has better -performance. - -IRC, freenode, #hurd, 2011-10-31: - - <youpi> I don't know what virtualbox does with hardware emulation, but - gnumach is awfully slow to probe things there diff --git a/hurd/running/vmware.mdwn b/hurd/running/vmware.mdwn deleted file mode 100644 index 1f99e247..00000000 --- a/hurd/running/vmware.mdwn +++ /dev/null @@ -1,56 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -## Installation - -Use <http://www.easyvmx.com/> web based tool to create vmx configuration files -which can be used with VMware player (which is a freeware). If you have a -VMware workstation or server you don't have to do this step. - -Note: I have tried it with K10 version of Debian GNU/Hurd on VMware running on -a Debian GNU/Linux machine. - -You can get more information about obtaining Debain GNU/Hurd CDROMS from -<http://www.us.debian.org/ports/hurd/hurd-cd>. - -Insert the first cdrom and proceed with the installation as per the -installation guide <http://www.us.debian.org/ports/hurd/hurd-install>. - -## VMware specific notes: - -You will need a grub floppy image to boot GNU/Hurd. I have attached a copy of -it with this document. You can also download it from here -<http://www.update.uu.se/~ams/home/slask/GNU/grub.img>. - -When you reboot the machine after the base tar ball is extracted (first reboot) -press 'Esc' key while VMware start up and set removable devices as the fisrt -boot device. - -Select "GNU (Also known as GNU/Hurd)" ie, the first option and press 'e' to -edit the grub menu and go to second line and press 'e' again to change -/boot/gnumach to /boot/gnumach.gz. - -Add a link to /boot/gnumach from /boot/gnumach.gz so that you don't have to -edit grub every time you boot. - - # ln -s /boot/gnumach.gz /boot/gnumach - -Or mount the floppy image and change it. - - # mkdir /media/floppy - # mount -o loop <path-to-grub.img> /media/floppy - -Edit /media/floppy/boot/grub/menu.lst with your favorite text editor and change -/boot/gnumach to /boot/gnumach.gz. - -## After install tweaks - -Start using GNU, here is -<http://www.gnu.org/software/hurd/users-guide/using_gnuhurd.html>. |