Jon: We need a better logo for this page - ever since the Gentoo and Bee movements got involved I've been thingking about fixing this logo, but I haven't had any time. Suggestions, gfx donations? -- [[Main/JoachimNilsson]] - 30 Jun 2004
# Getting Your GNU/Hurd Running
This web is about the distribution of software: where and how to get it.
Neal Walfield wrote a step-by-step guide that is the first document anyone installing Debian GNU/Hurd should read. Install Notes? is an errata companion document with more helpful hints that have not yet been incorporated.
Info on how to install without a cd drive or linux installed as well as a few tips.
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.
* [[HurdOnQEMU]] - A guide on how to use QEMU to run the hurd.
* [[BochsFAQ]] - Common questions you should read.
* [[VmWare]] - Why using it is discouraged.
Debian Installer
Work has been started by James Morrison and Glenn McGrath to Port Debootstrap?. There is also a New Debian Installer?. 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.
Savannah is a CVS & Bug system evolved from a free version of the code that powers sourceforge.net. 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 help wanted list.
Testing is critical in helping the development effort. Bugs (defect reports) can be filed against the Debian software package in which they are found. Bts Filing? tells how to file a Debian bug report. Debian Packages? 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. Buildd Status? includes information on the buildd & turtle efforts.
Many packages depend on these uninstallable packages. So building one of them will allow other to be build too.
Technical References
There are many standards and documents that might be applicable for those interested in developing software.
* GNU [Coding Standards](http://www.gnu.org/prep/standards.html)
* [[TestSuites]] - Posix, Perl, results feedback, etc.
* [docs and papers](http://www.gnu.org/software/hurd/docs.html)
* [[SystemAPILimits]]
* [[Hurd/HurdSpecificGlibcApi]]
* [[CodeAnnouncements]] - Recent coding projects related to the Hurd
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.
* [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
Debian Todo
Packages needing attention. A possible use of this site could be to help track similar needs via Hurd Wnpp?. This is not yet implemented.
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."
Technical description of Debian aimed at those interested in Debian.
* [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
----
Meta discussions about the Distrib web goes in the [[WebDiscuss]] topic.
[[WebPreferences]] - administrative