From 720ef091e7c6c0552038cb0cc71f449a152e631f Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 30 Oct 2007 16:06:17 +0100 Subject: Remove `unsorted/BuildingTheHurd'. Obsolete. --- unsorted/BuildingTheHurd.mdwn | 251 ------------------------------------------ 1 file changed, 251 deletions(-) delete mode 100644 unsorted/BuildingTheHurd.mdwn (limited to 'unsorted') diff --git a/unsorted/BuildingTheHurd.mdwn b/unsorted/BuildingTheHurd.mdwn deleted file mode 100644 index fb412eae..00000000 --- a/unsorted/BuildingTheHurd.mdwn +++ /dev/null @@ -1,251 +0,0 @@ -## Table of Contents - -%TOC% - -Created from the original by [Jon Portnoy](http://cvs.gentoo.org/~avenj/), - -## Introduction - -For a Linux to Hurd cross-compiler you need these versions (I tried newer versions of gcc but they won't compile) - -* [binutils-2.13.90.0.16](http://ftp.gnu.org/gnu/binutils/) - -* egcs-core-1.2.2 <- a very old version of gcc, but it is very stable, you will need it for compiling the gnumach headers and the mig kernel - -* [gcc-core-2.95.2](http://ftp.gnu.org/gnu/gcc/) <- for compiling hurd - -* [glibc-2.2.5](http://ftp.gnu.org/gnu/glibc/) - -* [gnumach-1.3](http://ftp.gnu.org/gnu/gnumach/gnumach-1.3.tar.gz) - -* [mig-1.3](http://ftp.gnu.org/gnu/mig/mig-1.3.tar.gz) - -* [hurd](http://www.gnu.org/software/hurd/download.html) - -## Building - -### The directory structure - -It is easier to compile the whole sources in an extra directory: - -* `build/binutils` <- the unpacked binutils sources - -* `build/binutils.build` - -* `build/egcs` <- the unpacked egcs sources - -* `build/egcs.build` - -* `build/gcc` <- the unpacked gcc sources - -* `build/gcc.build` - -* `build/glibc` <- the unpacked glibc sources - -* `build/glibc.build` - -* `build/gnumach` <- the unpacked gnumach kernel sources - -* `build/gnumach.build` - -* `build/mig` <- the unpacked mig kernel sources - -* `build/mig.build` - -* `build/hurd` <- the unpacked hurd kernel sources - -* `build/hurd.build` - -### Exporting the `CFLAGS` and `PATH` - -`/usr/local` is where the sources we compile will be installed. If you want to choose another directory you have to change the path to the bin directory and too you have to change the `--prefix` path to the directory you want. - - $ export CFLAGS="-march=i686 -O2 -fomit-frame-pointer" - $ export PATH=/usr/local/bin:$PATH - -**_All commands that are prefixed by `#` must be run as root with `CFLAGS` and `PATH` exported._** - -### Cross binutils - - $ cd binutils.build - $ ../binutils/configure --prefix=/usr/local --target=i686-pc-gnu - $ make - $ make check - # make install - $ cd .. - -### Cross egcs - -When the `/usr/local/bin` directory do not exist before you will now have to export the `PATH` again because after installing binutils you will have it. - - $ cd egcs.build - $ ../egcs/configure --prefix=/usr/local --target=i686-pc-gnu \ - --with-gnu-as --with-gnu-ld - $ make -k - # make -k install - $ ln -s /usr/local/i686-pc-gnu \ - /usr/local/lib/gcc-lib/i686-pc-gnu/egcs-2.91.66/i686-pc-gnu - $ cd .. - -### GNUmach Headers - - $ cd gnumach.build - $ ../gnumach/configure --build=i686-pc-linux-gnu --host=i686-pc-gnu - # make -k install-headers prefix=/usr/local/i686-pc-gnu - $ cd .. - -### Mig - -Mig is the Mach Interface Generator - needed by Mach and the Hurd to create C code from their IDL files. Mig is what helps us do RPC without ever knowing much about it. - - $ cd mig.build - $ ../mig/configure --target=i686-pc-gnu --host=i686-pc-linux-gnu \ - --prefix=/usr/local - $ make - # make install - $ cd .. - -### Gnumach Headers inclusive Mig - -When you first compile the GNUmach headers Mig won't be mentioned (it wasn't installed actually) and this causes some errors when compiling the GNUmach headers but you need them to compile mig. (I don't know if you have to do this but i think it is the better way) - - $ cd gnumach.build - $ rm -r * (deletes every file and directory in this directory) - $ ../gnumach/configure --build=i686-pc-linux-gnu --host=i686-pc-gnu - # make -k install-headers prefix=/usr/local/i686-pc-gnu - $ cd .. - -### Cross GCC - -For the coexistence of EGCS and GCC you have to move the `/usr/local/bin/i686-pc-gnu-gcc` to the `/usr/local/bin` directory in `i686-pc-gnu-egcs`. So you can choose wich compiler you want use: with the `CC` environment variable set to `i686-pc-gnu-egcs` you can use EGCS without this command you use GCC. - - # mv /usr/local/bin/i686-pc-gnu-gcc \ - /usr/local/bin/i686-pc-gnu-egcs - - $ cd gcc.build - $ ../gcc/configure --prefix=/usr/local --target=i686-pc-gnu \ - --with-gnu-as --with-gnu-ld - $ make -k compile the glibc-headers) - # make -k install - $ cd .. - - # ln -s /usr/local/i686-pc-gnu/ \ - /usr/local/lib/gcc-lib/i686-pc-gnu/2.95.2/i686-pc-gnu - -You need `make -k` because otherwise it will fail but with `-k` you will have everything you need. - -### Hurd Headers - - $ cd hurd.build - $ ../hurd/configure --build=i686-pc-linux-gnu -�host=i686-pc-gnu \ - -�prefix=/usr/local/i686-pc-gnu --disable-profile - # make install-headers no_deps=t - $ cd .. - -### Cross GLibC - -For having glibc compiled with the cross-gcc and not with your original gcc you have to export another `PATH`. The normal user who configures and compiles and also root has to export this `PATH`. - - $ export PATH=/usr/local/bin:/usr/local/i686-pc-gnu/bin:$PATH - $ cd glibc.build - $ ../glibc/configure --without-cvs --enable-add-ons=crypt \ - --disable-profile --build=i686-pc-linux-gnu \ - --host=i686-pc-gnu --prefix=/usr/local/i686-pc-gnu - -AS ROOT WITH EXPORTED CFLAGS: - - # export PATH=/usr/local/bin:/usr/local/i686-pc-gnu/bin:$PATH - # make -k install-headers install_root=/usr/local/i686-pc-gnu - # cp ../glibc/include/features.h \ - /usr/local/i686-pc-gnu/include/features.h - # touch /usr/local/i686-pc-gnu/include/gnu/stubs.h - $ cd .. - -### Building Cross egcs - - # mv /usr/local/bin/i686-pc-gnu-gcc \ - /usr/local/bin/i686-pc-gnu-foo (for protecting gcc) - # mv /usr/local/bin/i686-pc-gnu-egcs \ - /usr/local/bin/i686-pc-gnu-gcc - $ cd egcs.build - $ make - # make install (as root, export CFLAGS and the NEW PATH) - $ cd .. - # mv /usr/local/bin/i686-pc-gnu-gcc \ - /usr/local/bin/i686-pc-gnu-egcs - # mv /usr/local/bin/i686-pc-gnu-foo \ - /usr/local/bin/i686-pc-gnu-gcc - -### Building Cross GCC - - $ cd gcc.build - $ make - # make install - $ cd .. - -Remember to export `CFLAGS` and the new `PATH` - -### Building Cross GLibC - - $ cd glibc.build - $ make - # make install root_install=/usr/local/i686-pc-gnu - -Remember to export `CFLAGS` and the new `PATH` - -For solving a glibc bug you have to link the `/usr/local/i686-pc-gnu/include/libc.so.0.2` with the `/usr/local/i686-pc-gnu/lib/libc.so` ever when you (re)install glibc. - - # ln -sf /usr/local/i686-pc-gnu/lib/libc.so.0.2 \ - /usr/local/i686-pc-gnu/lib/libc.so - -### Install the GNUmach kernel somewhere - - $ rm -r gnumach.build - $ mkdir gnumach.build - $ cd gnumach.build - -You will need more than the `-�target` and `-�host` variables to build the GNUmach kernel. You have to enable some kernel features with the `--enable` command to have your kernel working properly. To have a quick view of what you need you can view the `gnumach/i386/README-Drivers` (I do not know how old it is, so maybe there are more options available but i haven't searched for more). - -My configure command: - - $ ../gnumach/configure --build=i686-pc-linux-gnu \ - --host=i686-pc-gnu �-enable-lpr \ - --enable-floppy --enable-ide \ - --enable-aic7xxx �-enable-rtl8139 - # ln -s /usr/local/i686-pc-gnu/include \ - /where/you/want/to/install/the/kernel/include - # ln -s /usr/locali686-pc-gnu/lib \ - /where/you/want/to/install/the/kernel/lib - $ make - # make install-kernel \ - prefix=/where/you/want/to/install/the/kernel (as root ...) - -### Hurd Servers - - $ rm -r hurd.build - $ mkdir hurd.build - $ cd hurd.build - $ nano -w/vi (or what editor you ever use) ../hurd/Makeconf - -You have to comment out the `CFLAGS` in this file or delete the `-std=gnu99` and the `-O3`. - - $ ../hurd/configure �build=i686-pc-linux-gnu \ - --host=i686-pc-gnu \ - -�prefix=/where/you/want/to/install/the/kernel \ - --disable-profile - $ make -k - # make -k install prefix=/where/you/want/to/install/the/kernel - -You have to use `-k` because when you don't use it the compilation will brake with an error. I tried different installations of gcc and glibc and too i used different versions of hurd but i cannot solve this prob so maybe it is hurd related. - -So there is no warranty that the hurd kernel you compiled will work. I will try it and then update this guide. - ----- - -## Document History - -Created from the original, , by [Jon Portnoy](http://cvs.gentoo.org/~avenj/) - -I would recommend not using EGCS, but instead using the GCC cross compiler. See [[Hurd/BuildingHurd]] and [[Mach/BuildingOskitMach]] for more information on building the GNU OS components.
-- [[Main/JoachimNilsson]] - 13 Apr 2003 - -Text formatting.
-- [[Main/OgnyanKulev]] - 13 Apr 2003 -- cgit v1.2.3 From d7896c327ed673f648a4c78736c7081664a4399c Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 16 Dec 2007 01:30:22 +0100 Subject: unsorted/DsvidWalter: Remove. --- unsorted/DsvidWalter.mdwn | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 unsorted/DsvidWalter.mdwn (limited to 'unsorted') diff --git a/unsorted/DsvidWalter.mdwn b/unsorted/DsvidWalter.mdwn deleted file mode 100644 index b7030c67..00000000 --- a/unsorted/DsvidWalter.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -* Name: Dsvid Walter -* Email: -* Company Name: -* Company URL: -* Location: [[Main/HurdUser]] -* Country: USA -* Comment: - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 70 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 17 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. -- cgit v1.2.3 From ce4f558ce3b00461584b3f8f58a0b17c529ec88c Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 16 Dec 2007 01:31:22 +0100 Subject: unsorted/ExtThree: Remove. --- unsorted/ExtThree.mdwn | 3 --- 1 file changed, 3 deletions(-) delete mode 100644 unsorted/ExtThree.mdwn (limited to 'unsorted') diff --git a/unsorted/ExtThree.mdwn b/unsorted/ExtThree.mdwn deleted file mode 100644 index 87225f56..00000000 --- a/unsorted/ExtThree.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -Here's a note about Ext3 support saying that [it's not started](http://lists.debian.org/debian-hurd/2002/debian-hurd-200209/msg00069.html) yet. - --- [[Main/GrantBow]] - 21 Oct 2002 -- cgit v1.2.3 From 754d9e9cd2472656da918b30b62880756becb483 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 16 Dec 2007 01:31:55 +0100 Subject: unsorted/LusHenriques: Remove. --- unsorted/LusHenriques.mdwn | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 unsorted/LusHenriques.mdwn (limited to 'unsorted') diff --git a/unsorted/LusHenriques.mdwn b/unsorted/LusHenriques.mdwn deleted file mode 100644 index f89d2ce5..00000000 --- a/unsorted/LusHenriques.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -* Name: Lu�s Henriques -* Email: -* Company Name: -* Company URL: -* Location: (Please specify office location) -* Country: Portugal -* Comment: - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 70 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 17 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. -- cgit v1.2.3 From f64d33727968e5e628d1d84e721aca6019de1c2f Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 16 Dec 2007 01:32:30 +0100 Subject: unsorted/MichaelDAdams: Remove. --- unsorted/MichaelDAdams.mdwn | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 unsorted/MichaelDAdams.mdwn (limited to 'unsorted') diff --git a/unsorted/MichaelDAdams.mdwn b/unsorted/MichaelDAdams.mdwn deleted file mode 100644 index a4ac3f15..00000000 --- a/unsorted/MichaelDAdams.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -* Name: Michael D. Adams -* Email: -* Company Name: -* Company URL: -* Location: [[Main/HurdUser]] -* Country: USA -* Comment: - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 70 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 17 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. -- cgit v1.2.3 From 5707bde8b664b4bc99a7b7ace37cb646c50c7e1b Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 16 Dec 2007 01:34:18 +0100 Subject: unsorted/AsHawley: Remove. --- unsorted/AsHawley.mdwn | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 unsorted/AsHawley.mdwn (limited to 'unsorted') diff --git a/unsorted/AsHawley.mdwn b/unsorted/AsHawley.mdwn deleted file mode 100644 index 0ff04800..00000000 --- a/unsorted/AsHawley.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -* Name: ashawley -* Email: -* Company Name: Ballistic Helmet -* Company URL: -* Location: [[Main/VirtualOffice]] -* Country: USA -* Comment: none. - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 70 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 17 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. -- cgit v1.2.3 From fc54b328dc205f693881aa8fd1337940e6c89787 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 14 Feb 2008 16:21:09 +0100 Subject: Restore user pages of Bas Wijnen and Tom Bachmann. --- community/meetings/fosdem_2008.mdwn | 4 ++-- community/meetings/self-organised_2008.mdwn | 4 ++-- hurd/ng/copyvsrevocablecopyvsmap.mdwn | 2 +- hurd/ng/designgoals.mdwn | 2 +- hurd/ng/firstclassreceivebuffer.mdwn | 2 +- hurd/ng/howmuchconfinementdowewant.mdwn | 2 +- hurd/ng/hurdishapplicationsforpersistence.mdwn | 2 +- hurd/ng/pathmax.mdwn | 2 +- hurd/ng/permissionbits.mdwn | 2 +- hurd/ng/setuidvsconstructor.mdwn | 2 +- hurd/ng/sharedlibraries.mdwn | 2 +- hurd/ng/thepolycastinterface.mdwn | 2 +- hurd/ng/trivialconfinementvsconstructorvsfork.mdwn | 2 +- hurd/ng/whatisacapability.mdwn | 2 +- hurd/ng/whatisaconstructor.mdwn | 2 +- hurd/ng/whatisaspacebank.mdwn | 2 +- hurd/ng/whatsinagroup.mdwn | 2 +- unsorted/AwarenessOfWhatHappens.mdwn | 2 +- unsorted/FlexibilityForUser.mdwn | 2 +- unsorted/SecurityForUser.mdwn | 2 +- user.old/BasWijnen.mdwn | 22 ---------------------- user.old/TomBachmann.mdwn | 20 -------------------- user/baswijnen.mdwn | 3 +++ user/tombachmann.mdwn | 3 +++ 24 files changed, 28 insertions(+), 64 deletions(-) delete mode 100644 user.old/BasWijnen.mdwn delete mode 100644 user.old/TomBachmann.mdwn create mode 100644 user/baswijnen.mdwn create mode 100644 user/tombachmann.mdwn (limited to 'unsorted') diff --git a/community/meetings/fosdem_2008.mdwn b/community/meetings/fosdem_2008.mdwn index 12c9ed3a..c7d5bd3d 100644 --- a/community/meetings/fosdem_2008.mdwn +++ b/community/meetings/fosdem_2008.mdwn @@ -23,7 +23,7 @@ Bruxelles. "Andrew Resch","?","?","?","?" "Ben Asselstine","?","?","?","?" "[[Barry_de_Freese|bddebian]]","?","?","?","?" -"Bas Wijnen and girlfriend","yes","Friday","Monday","yes (two)" +"[[Bas_Wijnen|baswijnen]] and girlfriend","yes","Friday","Monday","yes (two)" "Christian Dietrich","no","n/a","n/a","n/a" "Christopher Bodenstein","?","?","?","?" "Colin Leitner","no","n/a","n/a","n/a" @@ -59,7 +59,7 @@ Bruxelles. "Thomas Bushnell","?","?","?","?" "[[Thomas_Schwinge|tschwinge]]","plans to go","probably Friday (Thursday might also be possible)","Sunday or Monday","yes" "Tim Retout","plans to go","?","?","no" -"Tom Bachmann","?","?","?","?" +"[[Tom_Bachmann|tombachmann]]","?","?","?","?" "[[Vikram_Vincent|vincentvikram]]","no","n/a","n/a","n/a" "Wouter van Heyst","?","?","?","?" "Yoshinori K. Okuji","?","?","?","?" diff --git a/community/meetings/self-organised_2008.mdwn b/community/meetings/self-organised_2008.mdwn index 9558eb4d..e2805909 100644 --- a/community/meetings/self-organised_2008.mdwn +++ b/community/meetings/self-organised_2008.mdwn @@ -13,8 +13,8 @@ is included in the section entitled This meeting will be held in a to-be-determined place, at a to-be-determined time. This page hopes to help finding a good time and place, and finding out who wants to come. ## Who wants to come? -* Bas Wijnen (no preference for specific times) -* Tom Bachmann (weekend in the middle of germany would be preferred) +* [[Bas_Wijnen|baswijnen]] (no preference for specific times) +* [[Tom_Bachmann|tombachmann]] (weekend in the middle of germany would be preferred) * Please add yourself here ## Who will come? diff --git a/hurd/ng/copyvsrevocablecopyvsmap.mdwn b/hurd/ng/copyvsrevocablecopyvsmap.mdwn index 9c99c0a1..0cda7e24 100644 --- a/hurd/ng/copyvsrevocablecopyvsmap.mdwn +++ b/hurd/ng/copyvsrevocablecopyvsmap.mdwn @@ -3,4 +3,4 @@ TBD, see: * * --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/designgoals.mdwn b/hurd/ng/designgoals.mdwn index 9e685e55..d04007c2 100644 --- a/hurd/ng/designgoals.mdwn +++ b/hurd/ng/designgoals.mdwn @@ -32,7 +32,7 @@ Extensibility has often been a strong argument to support the multiserver approa However, I do believe there are benefits in multiserver environments you cannot get in a monolithic one, namely enhanced security and stability through protection boundaries. Also, whilst wanting to become adopted as general purpose OS, ngHurd still strives to allow for research also, so even according to the above-referenced paper extensibility is to be one of its goals. -Therefore, I'd want to propose to weaken the impact of extensibility on the design, by lowering it to the category "Regular Goals". -- [[Main/TomBachmann]] - 13 Dec 2006 +Therefore, I'd want to propose to weaken the impact of extensibility on the design, by lowering it to the category "Regular Goals". -- [[TomBachmann]] - 13 Dec 2006 ## Regular Goals diff --git a/hurd/ng/firstclassreceivebuffer.mdwn b/hurd/ng/firstclassreceivebuffer.mdwn index c3cc3142..30087bf2 100644 --- a/hurd/ng/firstclassreceivebuffer.mdwn +++ b/hurd/ng/firstclassreceivebuffer.mdwn @@ -1,3 +1,3 @@ TBD, see e.g. and --- [[Main/TomBachmann]] - 31 Aug 2006 +-- [[TomBachmann]] - 31 Aug 2006 diff --git a/hurd/ng/howmuchconfinementdowewant.mdwn b/hurd/ng/howmuchconfinementdowewant.mdwn index 663e5bbb..1963ae73 100644 --- a/hurd/ng/howmuchconfinementdowewant.mdwn +++ b/hurd/ng/howmuchconfinementdowewant.mdwn @@ -90,4 +90,4 @@ Marcus started a challenge [5] to find a use case for non-trivial confinement th * [4] * [5] --- [[Main/TomBachmann]] - 01 May 2006 +-- [[TomBachmann]] - 01 May 2006 diff --git a/hurd/ng/hurdishapplicationsforpersistence.mdwn b/hurd/ng/hurdishapplicationsforpersistence.mdwn index 12861ecb..d785694b 100644 --- a/hurd/ng/hurdishapplicationsforpersistence.mdwn +++ b/hurd/ng/hurdishapplicationsforpersistence.mdwn @@ -2,4 +2,4 @@ TBD, see: * ; summary: passive translators started by the filesystem cannot be done right and persistence makes passive translators unnecessary --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/pathmax.mdwn b/hurd/ng/pathmax.mdwn index 1c792937..1ea337e9 100644 --- a/hurd/ng/pathmax.mdwn +++ b/hurd/ng/pathmax.mdwn @@ -1,3 +1,3 @@ TBD, see and [Vulnerabilities in Synchronous IPC Designs](http://citeseer.ist.psu.edu/shapiro03vulnerabilities.html) --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/permissionbits.mdwn b/hurd/ng/permissionbits.mdwn index 1e1493df..eac00057 100644 --- a/hurd/ng/permissionbits.mdwn +++ b/hurd/ng/permissionbits.mdwn @@ -1,3 +1,3 @@ TBD, see: --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/setuidvsconstructor.mdwn b/hurd/ng/setuidvsconstructor.mdwn index 44c5f7fa..87cce8df 100644 --- a/hurd/ng/setuidvsconstructor.mdwn +++ b/hurd/ng/setuidvsconstructor.mdwn @@ -3,4 +3,4 @@ TBD, see e.g.: * * --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/sharedlibraries.mdwn b/hurd/ng/sharedlibraries.mdwn index 01b85df8..d4969420 100644 --- a/hurd/ng/sharedlibraries.mdwn +++ b/hurd/ng/sharedlibraries.mdwn @@ -1,3 +1,3 @@ TBD, see --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/thepolycastinterface.mdwn b/hurd/ng/thepolycastinterface.mdwn index 5d1fb8dc..702364cf 100644 --- a/hurd/ng/thepolycastinterface.mdwn +++ b/hurd/ng/thepolycastinterface.mdwn @@ -49,4 +49,4 @@ see also: * * --- [[Main/TomBachmann]] - 30 Apr 2006 +-- [[TomBachmann]] - 30 Apr 2006 diff --git a/hurd/ng/trivialconfinementvsconstructorvsfork.mdwn b/hurd/ng/trivialconfinementvsconstructorvsfork.mdwn index 4d221a8e..4eeef6ee 100644 --- a/hurd/ng/trivialconfinementvsconstructorvsfork.mdwn +++ b/hurd/ng/trivialconfinementvsconstructorvsfork.mdwn @@ -75,4 +75,4 @@ Now this isn't much more complicated than the constructor which does: Therefore I am not so convinced that we want a constructor. It gets in the way of debugging, for example, and it doesn't really give any gain. --- [[Main/BasWijnen]] - 13 Jun 2006 +-- [[BasWijnen]] - 13 Jun 2006 diff --git a/hurd/ng/whatisacapability.mdwn b/hurd/ng/whatisacapability.mdwn index a4ed5ed8..f3a42dd8 100644 --- a/hurd/ng/whatisacapability.mdwn +++ b/hurd/ng/whatisacapability.mdwn @@ -1,3 +1,3 @@ TBD, see e.g.: --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/hurd/ng/whatisaconstructor.mdwn b/hurd/ng/whatisaconstructor.mdwn index 3f05a37a..583babe9 100644 --- a/hurd/ng/whatisaconstructor.mdwn +++ b/hurd/ng/whatisaconstructor.mdwn @@ -3,4 +3,4 @@ TBD, see: * * --- [[Main/TomBachmann]] - 16 May 2006 +-- [[TomBachmann]] - 16 May 2006 diff --git a/hurd/ng/whatisaspacebank.mdwn b/hurd/ng/whatisaspacebank.mdwn index d7961210..607501db 100644 --- a/hurd/ng/whatisaspacebank.mdwn +++ b/hurd/ng/whatisaspacebank.mdwn @@ -1,3 +1,3 @@ TBD, see e.g. or --- [[Main/TomBachmann]] - 31 Aug 2006 +-- [[TomBachmann]] - 31 Aug 2006 diff --git a/hurd/ng/whatsinagroup.mdwn b/hurd/ng/whatsinagroup.mdwn index 122f2012..219f4ed0 100644 --- a/hurd/ng/whatsinagroup.mdwn +++ b/hurd/ng/whatsinagroup.mdwn @@ -1,3 +1,3 @@ TBD, see --- [[Main/TomBachmann]] - 20 Jun 2006 +-- [[TomBachmann]] - 20 Jun 2006 diff --git a/unsorted/AwarenessOfWhatHappens.mdwn b/unsorted/AwarenessOfWhatHappens.mdwn index bd64c3de..4ba78999 100644 --- a/unsorted/AwarenessOfWhatHappens.mdwn +++ b/unsorted/AwarenessOfWhatHappens.mdwn @@ -4,4 +4,4 @@ The user must know what the operations are he can perform in the operating syste _Awareness means that the user knows what happens._ --- [[Main/TomBachmann]] - 29 Apr 2006 +-- [[TomBachmann]] - 29 Apr 2006 diff --git a/unsorted/FlexibilityForUser.mdwn b/unsorted/FlexibilityForUser.mdwn index 06263fab..71b05cfd 100644 --- a/unsorted/FlexibilityForUser.mdwn +++ b/unsorted/FlexibilityForUser.mdwn @@ -4,4 +4,4 @@ The user must have a range of options available that support him to achieve an a _Flexibility means that the user controls what can happen **with** his resources._ --- [[Main/TomBachmann]] - 29 Apr 2006 +-- [[TomBachmann]] - 29 Apr 2006 diff --git a/unsorted/SecurityForUser.mdwn b/unsorted/SecurityForUser.mdwn index 51e1f9da..739cc1ca 100644 --- a/unsorted/SecurityForUser.mdwn +++ b/unsorted/SecurityForUser.mdwn @@ -4,4 +4,4 @@ The user must be sure that his actions have predictable consequences, even in th _Security means that the user controls what can happen **to** his resources._ --- [[Main/TomBachmann]] - 29 Apr 2006 +-- [[TomBachmann]] - 29 Apr 2006 diff --git a/user.old/BasWijnen.mdwn b/user.old/BasWijnen.mdwn deleted file mode 100644 index 4ee47324..00000000 --- a/user.old/BasWijnen.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -* Name: Bas Wijnen -* Email: -* Company Name: -* Company URL: -* Location: [[HurdUser]] -* Country: Netherlands -* Comment: - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 70 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 17 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. diff --git a/user.old/TomBachmann.mdwn b/user.old/TomBachmann.mdwn deleted file mode 100644 index 45be2c9f..00000000 --- a/user.old/TomBachmann.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -* Name: [[TomBachmann]] -* Email: [e\_mc\_h2@webNOSPAM.de](mailto:e_mc_h2@webNOSPAM.de) -* Location: [[HurdUser]] -* Country: Germany -* Comment: - -**_Personal Preferences (details in %TWIKIWEB%.TWikiVariables)_** - -* Horizontal size of text edit box: - * Set EDITBOXWIDTH = 150 -* Vertical size of text edit box: - * Set EDITBOXHEIGHT = 40 -* Optionally write protect your home page: (set it to your %TWIKIWEB%.WikiName) - * Set ALLOWTOPICCHANGE = - -**_Related topics_** - -* %TWIKIWEB%.%WIKIPREFSTOPIC% has site-level preferences of %WIKITOOLNAME%. -* %WEBPREFSTOPIC% has preferences of the %WIKITOOLNAME%.%WEB% web. -* %WIKIUSERSTOPIC% has a list of other TWiki users. diff --git a/user/baswijnen.mdwn b/user/baswijnen.mdwn new file mode 100644 index 00000000..170eeae7 --- /dev/null +++ b/user/baswijnen.mdwn @@ -0,0 +1,3 @@ +* Name: Bas Wijnen +* Email: +* Country: Netherlands diff --git a/user/tombachmann.mdwn b/user/tombachmann.mdwn new file mode 100644 index 00000000..639df67d --- /dev/null +++ b/user/tombachmann.mdwn @@ -0,0 +1,3 @@ +* Name: Tom Bachmann +* Email: +* Country: Germany -- cgit v1.2.3 From 1c3269629a6dd61ba6b78a24641d6821567bbf82 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Wed, 28 May 2008 00:54:52 +0100 Subject: porting explanations from the thread 'Analysis of build failures in Debian GNU/Hurd' --- unsorted/PortingIssues.mdwn | 89 ++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 79 insertions(+), 10 deletions(-) (limited to 'unsorted') diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn index 747fb230..993d4843 100644 --- a/unsorted/PortingIssues.mdwn +++ b/unsorted/PortingIssues.mdwn @@ -53,6 +53,10 @@ If you get Bad File Descriptor error when trying to read from a file (or accessi Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX incompatibility. If there is no upper limit on the length of a path (as its the case for GNU), this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use `sysconf()` to query the length at runtime. If `sysconf()` returns -1, you have to use `realloc()` to allocate the needed memory dynamically. +## `ARG_MAX` + +Same as `PATH_MAX`. There is no limit on the number of arguments. + ## `MAXHOSTNAMELEN` Same as `PATH_MAX`. When you find a `gethostname()` function, which acts on a static buffer, you can replace it with Neal's [xgethostname function](http://ftp.walfield.org/pub/people/neal/xgethostname/) which returns the hostname as a dynamic buffer. For example: @@ -81,7 +85,7 @@ Fixed code: ## `NOFILE` -Replace with `RLIMIT_NOFILE` +Replace with `getrlimit(RLIMIT_NOFILE,...)` ## GNU specific `#define` @@ -137,27 +141,92 @@ Those are evil if they don't exist and you want to name a directory this way. Fo Change it to use `termios.h` (check for it properly with autoconf `HAVE_TERMIOS_H` or the `__GLIBC__` macro) +Also, change calls to `ioctl(fd, TCGETS, ...)` and `ioctl(fd, TCSETS, ...)` with `tcgetattr(fd, ...)` and `tcsetattr(fd, ...)`. + ## `AC_HEADER_TERMIO` The autoconf check for `AC_HEADER_TERMIO` tryes to check for termios, but it's only really checking for termio in `termios.h`. It is better to use `AC_CHECK_HEADERS(termio.h termios.h)` -## broken libc6 dependency +## missing `_IOT` -Some packages use an erroneous dependency on `libc6-dev`. This is incorrect because `libc6` is specific to GNU/Linux. The corresponding package for GNU is `libc0.3-dev` but other OSes will have different ones. You can locate the problem in the `debian/control` file of the source tree. Typical solutions include detecting the OS using `dpkg-architecture` and hardcoding the soname, or better, use a logical OR. eg: `libc6-dev | libc0.3-dev | libc-dev`. The `libc-dev` is a virtual package that works for any soname but you have to put it only as the last option. +This comes from ioctls. Fixing this is easy if the structure members can be expressed by using the _IOT() macro, else it's simply impossible... See `bits/termios.h` for an instance: + +`#define _IOT_termios /* Hurd ioctl type field. */ \ + _IOT (_IOTS (tcflag_t), 4, _IOTS (cc_t), NCCS, _IOTS (speed_t), 2)` + +because `struct termios` holds 4 members of type `tcflag_ts`, then `NCCS` +members of type `cc_tsi` and finaly 2 members of type `speed_ts`. + +As you can see, this limits the number of kinds of members to 3, and in +addition to that (see the bitfield described in `ioctls.h`), the third +kind of member is limited to 3 members. However, since at the API +compatibility layer you are generally allowed to reorder fields in +structures, you can usually manage to fit into these limits. + +Note: if a field member is a pointer, then the ioctl can't be expressed +this way, and that makes sense, since the server you're talking to +doesn't have direct access to your memory. Ways other than ioctls must +then be found. + +## `SA_SIGINFO` + +Not implemented, packages may be fixed for working around this: use void sighandler(int num) prototype and sa_handler field. + +## `MSG_NOSIGNAL` + +Not implemented yet: [Savannah bug](https://savannah.gnu.org/bugs/?18218) + +## `IPV6_PKTINFO` + +Not fixed yet: [Glibc bug](http://sourceware.org/bugzilla/show_bug.cgi?id=3906) + +## `SOL_IP` + +Not implemented yet. -## Third argument in `ioctl` (`TIOCFLUSH`, etc) +## `HZ` -Broken arguments for `ioctl`'s which might work on other systems will cause segfault on GNU, because they are passed to and from a Hurd server RPC. +Linuxish and doesn't even make sense since the value may vary according to the running kernel. Should use `sysconf(_SC_CLK_TCK)` or `CLK_TCK` instead. -For example, `TIOCFLUSH` wants an `(int *)`, but will run on GNU/Linux if you pass it a 0. The solution in this case is to declare and assign an `int`, eg: +## `SIOCDEVPRIVATE` - int out = 0; +Oh, we should probably provide it. -and pass its address to `ioctl`: +## `MAP_NORESERVE` - ioctl (fd, TIOCFLUSH, &out); +Not POSIX, but we could implement it. -See [a simple fix for TIOCFLUSH in telnet](http://mail.gnu.org/archive/html/bug-inetutils/2001-08/msg00015.html). +## `O_DIRECT` + +Long story to implement. + +## `PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP` + +We could easily provide it; + +## `PTHREAD_STACK_MIN` + +We should actually provide it. + +## `linux/types.h` or `asm/types.h` + +These are not POSIX, `sys/types.h` and `stdint.h` should be used instead. + +## `iopl` + +Not supported. Try to replace with `ioperm(0, 65536, 1)` (conditionned with `__GNU__` as that will not work in Linux). + +## `semget`, `sem_open` + +Not implemented, will always fail. Use `sem_init()` instead if possible. + +## `net/if_arp.h`, `net/ethernet.h`, etc. + +Not implemented, not POSIX. Try to disable the feature in the package. + +## broken libc6 dependency + +Some packages use an erroneous dependency on `libc6-dev`. This is incorrect because `libc6` is specific to GNU/Linux. The corresponding package for GNU is `libc0.3-dev` but other OSes will have different ones. You can locate the problem in the `debian/control` file of the source tree. Typical solutions include detecting the OS using `dpkg-architecture` and hardcoding the soname, or better, use a logical OR. eg: `libc6-dev | libc0.3-dev | libc-dev`. The `libc-dev` is a virtual package that works for any soname but you have to put it only as the last option. ---- -- cgit v1.2.3 From 775228a56db6f28b2d4a91b7a9513b7508fe8a2a Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Thu, 5 Jun 2008 02:44:14 +0100 Subject: add error_t, E* and C++ issue --- unsorted/PortingIssues.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'unsorted') diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn index 993d4843..454f24eb 100644 --- a/unsorted/PortingIssues.mdwn +++ b/unsorted/PortingIssues.mdwn @@ -133,6 +133,17 @@ You can for example look in the latest coreutils (the above is a simplified vers Of course, if you don't care about broken systems (like MS-DOG) not supporting `strerror()` you can just replace `sys_errlist[]` directly (upstream might not accept your patch, but debian should have no problem) +## C++, `error_t` and `E*` + +On the Hurd, `error_t` is an enumeration of the `E*` constants. However, C++ +does not like `E*` integer macros being directly assigned to that enumeration. In short, replace + + error_t err = EINTR; + +by + + error_t err = error_t(EINTR); + ## Filenames ending in a slash \`/' Those are evil if they don't exist and you want to name a directory this way. For example, `mkdir foobar/` will not work on GNU. This is POSIX compatible. POSIX says that the path of a directory may have slashes appended to it. But the directory does not exist yet, so the path does not refer to a directory, and hence trailing slashes are not guaranteed to work. Just drop the slashes, and you're fine. -- cgit v1.2.3 From df835e043986380221d7720b263863a38aedb207 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Thu, 12 Jun 2008 15:56:05 +0100 Subject: add IOV_MAX --- unsorted/PortingIssues.mdwn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'unsorted') diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn index 454f24eb..87d2154b 100644 --- a/unsorted/PortingIssues.mdwn +++ b/unsorted/PortingIssues.mdwn @@ -57,6 +57,10 @@ Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX Same as `PATH_MAX`. There is no limit on the number of arguments. +## `IOV_MAX` + +Same as `PATH_MAX`. There is no limit on the number of iovec items. + ## `MAXHOSTNAMELEN` Same as `PATH_MAX`. When you find a `gethostname()` function, which acts on a static buffer, you can replace it with Neal's [xgethostname function](http://ftp.walfield.org/pub/people/neal/xgethostname/) which returns the hostname as a dynamic buffer. For example: -- cgit v1.2.3 From e4e89e1683012c879012522105a3471a00714613 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Fri, 12 Sep 2008 23:40:55 +0200 Subject: MSG_NOSIGNAL and IPV6_PKTINFO got fixed --- unsorted/PortingIssues.mdwn | 8 -------- 1 file changed, 8 deletions(-) (limited to 'unsorted') diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn index 87d2154b..ff63bda3 100644 --- a/unsorted/PortingIssues.mdwn +++ b/unsorted/PortingIssues.mdwn @@ -187,14 +187,6 @@ then be found. Not implemented, packages may be fixed for working around this: use void sighandler(int num) prototype and sa_handler field. -## `MSG_NOSIGNAL` - -Not implemented yet: [Savannah bug](https://savannah.gnu.org/bugs/?18218) - -## `IPV6_PKTINFO` - -Not fixed yet: [Glibc bug](http://sourceware.org/bugzilla/show_bug.cgi?id=3906) - ## `SOL_IP` Not implemented yet. -- cgit v1.2.3 From 1f41e899e3da7b8f681e3787b5150e1cd9ecf50a Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 7 Oct 2008 22:59:01 +0200 Subject: Reintegrate the QEMU page, change formatting, add copyright and license statements. --- hurd/running/qemu.mdwn | 2 +- qemu.mdwn | 36 ++++++++++++++++++++++++++++++++++++ unsorted/QEMU.mdwn | 15 --------------- 3 files changed, 37 insertions(+), 16 deletions(-) create mode 100644 qemu.mdwn delete mode 100644 unsorted/QEMU.mdwn (limited to 'unsorted') diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn index eab49b08..3a9784f7 100644 --- a/hurd/running/qemu.mdwn +++ b/hurd/running/qemu.mdwn @@ -17,7 +17,7 @@ volunteers and may not have been tested extensively. # What is Needed -1. First thing is to install [[QEMU]]. +1. First thing is to install [[/QEMU]]. 2. A [grub](http://www.gnu.org/software/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 an 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. diff --git a/qemu.mdwn b/qemu.mdwn new file mode 100644 index 00000000..97ce5693 --- /dev/null +++ b/qemu.mdwn @@ -0,0 +1,36 @@ +[[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]]."]]"""]] + +QEMU is free software written by Fabrice Bellard that implements a fast +processor [[emulator|emulation]], allowing a user to run one operating system +within another one. It is similar to projects such as [[Bochs]] and VMware +Workstation, but has several features these lack, including increased speed and +support for multiple architectures. By using dynamic translation it achieves a +reasonable speed while being easy to port on new host CPUs. + +QEMU has two operating modes: + + * User mode emulation: QEMU can launch Linux processes compiled for one CPU + on another CPU. Linux system calls are converted because of endianness and + 32/64 bit mismatches. Wine and Dosemu are the main targets for QEMU. + + * System mode emulation: QEMU emulates a full system, including a processor + and various peripherials. It enables easier testing and debugging of + system code. It can also be used to provide virtual hosting of several + virtual PCs on a single server. + +The majority of the program is under the [[LGPL]], with the system mode +emulation under the [[GPL]]. + +# External Links + + * + * QEMU Wiki + * [Qemu on Windows](http://www.h7.dion.ne.jp/~qemu-win/) diff --git a/unsorted/QEMU.mdwn b/unsorted/QEMU.mdwn deleted file mode 100644 index 27086257..00000000 --- a/unsorted/QEMU.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -QEMU is free software written by Fabrice Bellard that implements a fast processor emulator, allowing a user to run one operating system within another one. It is similar to projects such as Bochs and VMware Workstation, but has several features these lack, including increased speed and support for multiple architectures. By using dynamic translation it achieves a reasonable speed while being easy to port on new host CPUs. - -QEMU has two operating modes: - -* User mode emulation: QEMU can launch Linux processes compiled for one CPU on another CPU. Linux system calls are converted because of endianness and 32/64 bit mismatches. Wine and Dosemu are the main targets for QEMU. - -* System mode emulation: QEMU emulates a full system, including a processor and various peripherials. It enables easier testing and debugging of system code. It can also be used to provide virtual hosting of several virtual PCs on a single server. - -The majority of the program is under the [[LGPL]], with the system mode emulation under the [[GPL]]. - -## External links - -* -* QEMU Wiki -* [Qemu on Windows](http://www.h7.dion.ne.jp/~qemu-win/) -- cgit v1.2.3 From 9574f098caf72da7f709c8467e96606cce04fff9 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 5 Nov 2008 14:41:44 +0100 Subject: Move information to another page. --- related-projects.html | 131 ----------------------------------------- unsorted/SavannahProjects.mdwn | 1 + 2 files changed, 1 insertion(+), 131 deletions(-) delete mode 100644 related-projects.html (limited to 'unsorted') diff --git a/related-projects.html b/related-projects.html deleted file mode 100644 index 2556f5e2..00000000 --- a/related-projects.html +++ /dev/null @@ -1,131 +0,0 @@ - - - -The GNU Hurd - GNU Project - Free Software Foundation (FSF) - - - - - - - - - - - - -

-[ - - - English -| Esperanto -| Spanish -] -

-What's New
-
-ChangeLogs
-
-Documentation
-

-GNU Hurd
-
-Installation
-Getting Help
-Source Code
-Development
-History
-
-GNU Mach
-
-Installation
-Source Code
-
-GNU MIG
-
-Source Code
-
-Related Projects -

Related Projects

-The Hurd is not alone, it is inspired by other projects, and other -projects have been influenced or spawned by the Hurd. -

-Below you can find some of the projects which are closely related to -the Hurd, be it because they develop software that might be part of -the Hurd system some day, be it because they support or use the Hurd -in their own development. -

-This list is nowhere near to be complete. We recommend to follow the -mailing lists to be informed about recent developments. -

-Some of these links are at other web sites not maintained by the -FSF. The FSF is not responsible for the content of these other web -sites. - -

Software

- -

GNU/Hurd on Alpha

-The purpose of this project is to provide a working implementation of -the GNU Hurd for the Alpha architecture. -
-http://savannah.gnu.org/projects/hurd-alpha/ - -

The GNU Hurd on top of the L4 microkernel

-The purpose of this project is to port the Hurd system to the L4 microkernel. -
-http://www.gnu.org/software/hurd/hurd-l4.html - - -

- -

- -[ - - - English -| Esperanto -| Spanish -] - -

- -

-Return to GNU's home page. -

- -Please send FSF & GNU inquiries & questions to - -gnu@gnu.org. -There are also other ways to -contact the FSF. -

- -Please send comments on these web pages to - -web-hurd@gnu.org, -send other questions to -gnu@gnu.org. -

-Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. -

-Updated: - -$Date$ $Author$ - -

- - diff --git a/unsorted/SavannahProjects.mdwn b/unsorted/SavannahProjects.mdwn index 3024ed64..b1111ed5 100644 --- a/unsorted/SavannahProjects.mdwn +++ b/unsorted/SavannahProjects.mdwn @@ -7,6 +7,7 @@ * [pthreads](http://savannah.gnu.org/projects/pthreads) - porting of thread library for glibc * [hurd-iso](http://savannah.gnu.org/projects/hurd-iso) - CD-ROM images * [gnumach-alpha](http://savannah.gnu.org/projects/gnumach-alpha) - port for Alpha processor machines +* [hurd-alpha](http://savannah.gnu.org/projects/hurd-alpha) - provide a working implementation for the Alpha architecture * [[Hurd/THUG]] - Toronto Area GNU/Hurd User Group and their [documentation page](http://www.freesoftware.fsf.org/thug/docs.html) * [francine](http://savannah.gnu.org/projects/francine) - "secure, colourful and themeable login program" -- cgit v1.2.3 From 3393b31de8361941817e4878dca1174731f7f161 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 6 Nov 2008 12:03:58 +0100 Subject: Don't know what to do with the changelogs.html page. --- changelogs.html | 194 ----------------------------------------------- unsorted/changelogs.html | 107 ++++++++++++++++++++++++++ 2 files changed, 107 insertions(+), 194 deletions(-) delete mode 100644 changelogs.html create mode 100644 unsorted/changelogs.html (limited to 'unsorted') diff --git a/changelogs.html b/changelogs.html deleted file mode 100644 index 5eb70e22..00000000 --- a/changelogs.html +++ /dev/null @@ -1,194 +0,0 @@ - - - -The GNU Hurd - GNU Project - Free Software Foundation (FSF) - - - - - - - - - - - - -

-[ - - - English -| Esperanto -| Spanish -] -

-What's New
-
-ChangeLogs
-
-Documentation
-

-GNU Hurd
-
-Installation
-Getting Help
-Source Code
-Development
-History
-
-GNU Mach
-
-Installation
-Source Code
-
-GNU MIG
-
-Source Code
-
-Related Projects -

ChangeLogs

-As the Hurd sources are kept and maintained in a CVS repository that -is accessible via the web, you can follow the progress of development -closely. We maintain ChangeLogs, in which we record every change to -the source code at the time it is committed. The links below lead you -directly to the ChangeLog files in the Hurd and its associated packages. -

-If you want to follow the development of the Hurd closely, we suggest -that you subscribe to the commit-hurd mailing -list to which notifications about changes to the Hurd source code -are sent. The complete source -code is also available, of course. -

The Hurd

-The Hurd source tree contains many independent parts, and therefore -has one ChangeLog for each directory. There is one ChangeLog -in the main directory, and one in each of the following -subdirectories: -

Translators and other servers: -auth, -exec, -ext2fs, -ftpfs, -hostmux, -init, -isofs, -mach-defpager, -nfs, -nfsd, -pfinet, -pflocal, -proc, -storeio, -term, -tmpfs, -trans, -ufs, -usermux -
Utilities: -benchmarks, -boot, -bsdfsck, -fstests, -sutils, -ufs-fsck, -ufs-utils, -utils -
Boot code and system programs: -login, -config, -daemons, -serverboot -
Release scripts and packaging: -debian, -release -
Documentation: -doc -
Interface definitions: -hurd -
Support libraries: -libdiskfs, -libfshelp, -libftpconn, -libhurdbugaddr, -libihash, -libiohelp, -libnetfs, -libpager, -libpipe, -libports, -libps, -libshouldbeinlibc, -libstore, -libthreads, -libtrivfs -

GNU Mach

-The GNU -Mach ChangeLog covers all changes to GNU Mach and GNU -Mach 1 branch ChangeLog those on the gnumach-1-branch. -Changes before March 1997 are listed in ChangeLog.0 -and ChangeLog.00. -

MIG

-The MIG ChangeLog -covers all changes to MIG. - -

- -

- -[ - - - English -| Esperanto -| Spanish -] - -

- -

-Return to GNU's home page. -

- -Please send FSF & GNU inquiries & questions to - -gnu@gnu.org. -There are also other ways to -contact the FSF. -

- -Please send comments on these web pages to - -web-hurd@gnu.org, -send other questions to -gnu@gnu.org. -

-Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. -

-Updated: - -$Date$ $Author$ - -

- - diff --git a/unsorted/changelogs.html b/unsorted/changelogs.html new file mode 100644 index 00000000..7689484e --- /dev/null +++ b/unsorted/changelogs.html @@ -0,0 +1,107 @@ +[[meta copyright="Copyright © 2001, 2002, 2006, 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]]."]]"""]] + +

ChangeLogs

+As the Hurd sources are kept and maintained in a CVS repository that +is accessible via the web, you can follow the progress of development +closely. We maintain ChangeLogs, in which we record every change to +the source code at the time it is committed. The links below lead you +directly to the ChangeLog files in the Hurd and its associated packages. +

+If you want to follow the development of the Hurd closely, we suggest +that you subscribe to the commit-hurd mailing +list to which notifications about changes to the Hurd source code +are sent. The complete source +code is also available, of course. +

The Hurd

+The Hurd source tree contains many independent parts, and therefore +has one ChangeLog for each directory. There is one ChangeLog +in the main directory, and one in each of the following +subdirectories: +

Translators and other servers: +auth, +exec, +ext2fs, +ftpfs, +hostmux, +init, +isofs, +mach-defpager, +nfs, +nfsd, +pfinet, +pflocal, +proc, +storeio, +term, +tmpfs, +trans, +ufs, +usermux +
Utilities: +benchmarks, +boot, +bsdfsck, +fstests, +sutils, +ufs-fsck, +ufs-utils, +utils +
Boot code and system programs: +login, +config, +daemons, +serverboot +
Release scripts and packaging: +debian, +release +
Documentation: +doc +
Interface definitions: +hurd +
Support libraries: +libdiskfs, +libfshelp, +libftpconn, +libhurdbugaddr, +libihash, +libiohelp, +libnetfs, +libpager, +libpipe, +libports, +libps, +libshouldbeinlibc, +libstore, +libthreads, +libtrivfs +

GNU Mach

+The GNU +Mach ChangeLog covers all changes to GNU Mach and GNU +Mach 1 branch ChangeLog those on the gnumach-1-branch. +Changes before March 1997 are listed in ChangeLog.0 +and ChangeLog.00. +

MIG

+The MIG ChangeLog +covers all changes to MIG. -- cgit v1.2.3 From ef7f0326b971806ce9061a71cd1874b7e0c279d0 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 6 Nov 2008 12:37:49 +0100 Subject: Three more documents I don't know what to do with. --- byte-letter.txt | 25 ------ hurd-fs-org | 219 ----------------------------------------------- hurd-migr | 141 ------------------------------ unsorted/byte-letter.txt | 25 ++++++ unsorted/hurd-fs-org | 219 +++++++++++++++++++++++++++++++++++++++++++++++ unsorted/hurd-migr | 141 ++++++++++++++++++++++++++++++ 6 files changed, 385 insertions(+), 385 deletions(-) delete mode 100644 byte-letter.txt delete mode 100644 hurd-fs-org delete mode 100644 hurd-migr create mode 100644 unsorted/byte-letter.txt create mode 100644 unsorted/hurd-fs-org create mode 100644 unsorted/hurd-migr (limited to 'unsorted') diff --git a/byte-letter.txt b/byte-letter.txt deleted file mode 100644 index 20fa61a0..00000000 --- a/byte-letter.txt +++ /dev/null @@ -1,25 +0,0 @@ -Byte magazine published this in the `Letters' section -of the March '96 issue: - - Where's the GNU Hurd? - - The November 1995 articles "NT Roars - on the 604" and "CPU scorecards" were - quite welcome. But the Special Report on - operating systems did not mention GNU - Hurd. This OS is based on the Mach mi- - crokernel, and thus it has been essentially - ported to a wide variety of hardware plat- - forms--nearly as many as NetBSD. To - learn more about the Hurd, and especially - about its binary portability, visit http:// - www.cs.pdx.edu/~trent/gnu/hurd/. Con- - trary to what you say in the text box "Op- - erating-System Research: Dim or Bright - Future?" (page 116), microkernel tech- - nology has not been exploited to its max- - imum capability, as the Hurd philosophy - demonstrates. - - Todd Hutchinson - jasper@terra.3rdplanet.com diff --git a/hurd-fs-org b/hurd-fs-org deleted file mode 100644 index ba515623..00000000 --- a/hurd-fs-org +++ /dev/null @@ -1,219 +0,0 @@ -From: mib@duality.gnu.ai.mit.edu (Michael I. Bushnell, p/BSG) -Newsgroups: gnu.misc.discuss -Subject: Re: GNU vs. Linux FSSTND conflict? -Date: 13 Aug 1995 22:31:18 GMT -Organization: Free Software Foundation, Cambridge, MA -In-reply-to: Rick Niles's message of 13 Aug 1995 16:20:29 GMT - -In article <40l8od$ia9@news4.digex.net> Rick Niles - writes: - - Is there a conflict between the GNU Filesystem Structure and - the Linux Filesystem Structure (FSSTND)? - -What you point out is the trivial difference; there are significant -lossages in FSSTND, such as the absence of libexec... - - I've heard on this newsgroup that the GNU std. is to elminate - the use of /usr. So: - - I guess the first question is: Is this true? - -Yes. - - If it is how do you answer those who say the root part. should - be small and only enough to boot the system? And - the rest of the system should be on a separate part. (/usr) - -In GNU the directory /bin will be an amalgam of several directories; -this well be done by the use of a translator in the Hurd. (It will be -similar to BSD shadow filesystems.) - -So we have no need to confuse users by putting binaries in two -different places. We can put different binaries in different physical -locations without either forcing them to appear in different places or -creating a forest of symlinks. - -But the FSSTND's arguments are bogus even for Unixoid systems which do -force differently located files to have different directory names: - - o It is often mounted from very small media. For example, many Linux - users install and recover systems by mounting root off a RAM disk, - which is copied from a single 1.44M or 1.2M floppy disk. - -This is a non-issue. Obviously a floppy can only have a small number -of files, but that's totally irrelevant in deciding what should be on -root on a fully loaded system. - - o The root filesystem has many system-specific configuration files in - it. Possible examples include a kernel that is specific to the - system, a different hostname, etc. This means that the root - filesystem isn't always shareable between networked systems. - Keeping it small on networked systems minimizes the amount of space - lost on servers to unshareable files. It also allows workstations - with smaller local hard drives. - -It should be possible to require only the etc directory to be -per-system; there is no reason that bin and such should be non-shared -at all. - - o While you may have the root filesystem on a large partition, and - may be able to fill it to your heart's content, there will be - people with smaller partitions. If you have more files installed, - you may find incompatibilities with other systems using root - filesystems on smaller partitions. If you are a developer then you - may be turning your assumption into a problem for a large number of - users. - -This is totally incoherent, as far as I can tell. If someone can tell -me what it means, then maybe I could help. What sort of -incompatibilities are expected? - -Michael - - - -From: gord@enci.ucalgary.ca (Gord Matzigkeit) -Newsgroups: gnu.misc.discuss -Subject: Re: GNU vs. Linux FSSTND conflict? -Date: 14 Aug 1995 18:55:20 -0600 -In-reply-to: mib@duality.gnu.ai.mit.edu's message of 13 Aug 1995 22:31:18 GMT - ------BEGIN PGP SIGNED MESSAGE----- - -Hi! - ->>>>> "mib" == Michael I Bushnell, p/BSG writes: - - mib> In article <40l8od$ia9@news4.digex.net> Rick Niles - mib> writes: -[hack & slice] - - >> If it is how do you answer those who say the root - >> part. should be small and only enough to boot the system? And - >> the rest of the system should be on a separate part. (/usr) - - mib> In GNU the directory /bin will be an amalgam of several - mib> directories; this well be done by the use of a translator in the - mib> Hurd. (It will be similar to BSD shadow filesystems.) - -This is what I figured... my reply didn't get posted to USENET, -though, because our NNTP server has been down for the last day or two. - - mib> So we have no need to confuse users by putting binaries in two - mib> different places. We can put different binaries in different - mib> physical locations without either forcing them to appear in - mib> different places or creating a forest of symlinks. - -This is grand! One of my ideas that I mentioned to Rick was that I'm -currently using depot, and I see that the GNU union/shadowfs could -replace that. - -What depot does is manages symlinks for a "software environment" (a -more restricted version of what you have described). - -The way I think I'll be setting up my Hurd machine is to have all the -physical disks mounted under "/disk", each containing a fragment of -the filesystem. - -Now, my only concerns are: - -1) control files, as far as determining precedence, and what can and -cannot be shadowed (for collision resolution), and what is just -auxilliary info (like CVS directories in the site package, which -should not be mapped onto the software environment) - -2) packages. Is there some slick way to divide the filesystem into -"package pieces", like depot does? - -One suggestion to get (2), is that I could create an intermediate -directory, say "/package", that would be the union of various mounted -physical disks (under /disk), and would contain things like: - -emacs-19.30/bin -emacs-19.30/lib... -gcc-2.7.3/bin... -fileutils-5.8/man... -site/sbin/useful_perl_script - -et al. Then I would unionfs all the directories in the /package dir -onto the root filesystem. - -This would have most of the advantages I'm getting from depot, namely, -the ability to specify different precedences on different machines, -so that I can try out emacs-19.31 on one workstation without -disrupting the others. - -Is there a better way to do this? I do like the idea of three -different hierarchies for files (under /disk, where I can see what is -on each server; under /package, where I can see what is in each -package; the GNU standard dirs, where I actually use the files), but I -am hoping that there is something more elegant. Hmm. Maybe not. - - mib> It should be possible to require only the etc directory to be - mib> per-system; there is no reason that bin and such should be - mib> non-shared at all. - -This is one point (for security), that would mandate the use of config -files, so that the unionfs doesn't map /etc/some_important_file from -another server. - -This is yet another thing that I'm looking forward to. Thanks. ;) - -- --Gordon - -- -- -Gordon Matzigkeit | Heck, it was only a TOASTER... lighten up! -gord@enci.ucalgary.ca | PGP mail preferred... finger me for my key. -Keyprint: D5 66 08 E0 4D F4 D7 7B 8A C8 8A 9C 7F 39 25 A7 - ID 339ABEB9 - - ------BEGIN PGP SIGNATURE----- -Version: 2.6.2 -Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface - -iQCVAwUBMC/wcyFsfCEzmr65AQHubwP7BGVHqs9ACB8hFUqDdF2oWu/lLq1hW/Oa -qra2ZfcKfIZq9hIM4tLRJ0qCaiOVm5MGLgH7Yax+ZyOPb4K0fCObzk1XY5b0enhV -9SR70UZ7Qm7MXj+PFCp5lxvrNiaFXMbil0EN5FQEvH9kUp0ed1NWcaXGqTK6gezm -YBUumt2Zadk= -=6f2c ------END PGP SIGNATURE----- - - - - -From: mib@duality.gnu.ai.mit.edu (Michael I. Bushnell, p/BSG) -Newsgroups: gnu.misc.discuss -Subject: Re: GNU vs. Linux FSSTND conflict? -Date: 16 Aug 1995 14:43:47 GMT -In-reply-to: gord@enci.ucalgary.ca's message of 14 Aug 1995 18:55:20 -0600 - -In article gord@enci.ucalgary.ca (Gord Matzig -keit) writes: - - The way I think I'll be setting up my Hurd machine is to have all the - physical disks mounted under "/disk", each containing a fragment of - the filesystem. - -Our idea is to do something roughly like this. - - 1) control files, as far as determining precedence, and what can and - cannot be shadowed (for collision resolution), and what is just - auxilliary info (like CVS directories in the site package, which - should not be mapped onto the software environment) - -Yes, the relevant translator will support a *rich* set of semantics -for this kind of things specified by a control file. - - 2) packages. Is there some slick way to divide the filesystem into - "package pieces", like depot does? - -We're going to do this; rms and I have worked out a usable scheme that -meets all the necessary goals. - -The physical location of files has to be reflected by sharing rules -(see the GNU makefile standards); users have to be able to see all the -files relevant to a particular program easily; programs have to be -easily de-installed. We have a scheme that meets these three. - -Michael diff --git a/hurd-migr b/hurd-migr deleted file mode 100644 index ce36c86c..00000000 --- a/hurd-migr +++ /dev/null @@ -1,141 +0,0 @@ -Path: usenet.ee.pdx.edu!cs.uoregon.edu!sgiblab!swrinde!howland.reston.ans.net!E -U.net!Germany.EU.net!netmbx.de!sietec.de!news!jh -From: jh@poseidon.sietec.de (Jochen Roger Hayek) -Newsgroups: gnu.misc.discuss -Subject: HURD & migration facilities -Date: 24 Oct 1994 15:12:34 GMT -Organization: Sietec Systemtechnik, Berlin -Lines: 16 -Distribution: world -Message-ID: -Reply-To: Jochen.Roger.Hayek@sietec.de -NNTP-Posting-Host: sunmiet3.sietec.de - -I read an article from acm's sigops vol. 28, number 4 this weekend, having the -title: - - a brief survey of systems providing - process or object migration facilities - by Mark Nuttall - -I found it very instructive. - -I think process / object migration should be considered for HURD, too, -and it's important to look at that before supporting / emulating -UNIX's fork and inherited open file descriptors, -because those features might get contradictory if not carefully designed. - -Regards esp. to the HURD folks - -JH - -Path: usenet.ee.pdx.edu!cs.uoregon.edu!sgiblab!spool.mu.edu!bloom-beacon.mit.ed -u!ai-lab!life.ai.mit.edu!mib -From: mib@churchy.gnu.ai.mit.edu (Michael I Bushnell) -Newsgroups: gnu.misc.discuss -Subject: Re: HURD & migration facilities -Date: 24 Oct 1994 18:10:25 GMT -Organization: Free Software Foundation, Cambridge, MA -Lines: 27 -Distribution: world -Message-ID: -References: -NNTP-Posting-Host: churchy.gnu.ai.mit.edu -In-reply-to: jh@poseidon.sietec.de's message of 24 Oct 1994 15:12:34 - GMT - -In article jh@poseidon.sietec.de (Jochen -Roger Hayek) writes: - - I think process / object migration should be considered for HURD, too, - and it's important to look at that before supporting / emulating - UNIX's fork and inherited open file descriptors, - because those features might get contradictory if not carefully designed. - -Process migration is not a problem for the Hurd--it's a problem for -Mach. If a Mach task can be correctly migrated, then there is no -problem. - -However, I want to do more than that with the Hurd; I want to have a -collection of machines (I think I'll call it a ``Collective'') appear -as a single machine. (Shades of amoeba here.) - -This is the first (and harder) task--making a single global space of -pids, etc. - -The second (and easier) task is migration. - - -mib --- -+1 617 623 3248 (H) | En arche en ho logos, -+1 617 253 8568 (W) -+- kai ho logos en pros ton theon, -1105 Broadway | kai theos en ho logos. -Somerville, MA 02144 | Kai ho logos sarx egeneto, -mib@gnu.ai.mit.edu | kai eskenosen en hemin. - -Newsgroups: gnu.misc.discuss -Path: usenet.ee.pdx.edu!cs.uoregon.edu!reuter.cse.ogi.edu!psgrain!agora!hermes. -rdrop.com!erich -From: erich@uruk.org (Erich Boleyn) -Subject: Re: HURD & migration facilities -Sender: news@agora.rdrop.com (David Greenman) -Nntp-Posting-Host: uruk.org -Organization: RainDrop Laboratories -Message-ID: -References: - -In-Reply-To: mib@churchy.gnu.ai.mit.edu's message of 24 Oct 1994 18:10:25 GMT -Date: Sat, 29 Oct 1994 16:35:37 GMT -Lines: 50 - - -In article mib@churchy.gnu.ai.mit.ed -u (Michael I Bushnell) writes: - - Process migration is not a problem for the Hurd--it's a problem for - Mach. If a Mach task can be correctly migrated, then there is no - problem. - - However, I want to do more than that with the Hurd; I want to have a - collection of machines (I think I'll call it a ``Collective'') appear - as a single machine. (Shades of amoeba here.) - -Great! (I think we talked about this before...) - - This is the first (and harder) task--making a single global space of - pids, etc. - -This point seems somewhat questionable. Maybe we're thinking about -the same idea in the long run, but I don't think that migrating -data about the whole system around would be very useful... -I mean, you still want a very large collective to work, though it -could well get bogged down by the details of huge amounts of info. - -I think a more optimal (and more practical) approach would be to: - -Create a model of a "user context" that keeps track across multiple -machines what resources and programs a user is working with. - -There would also be publically known "services" that would be advertised. -Note that "advertising" is a specific activity that is usually not -performed, unless one desires to do so. - -Anything else is really of little or no concern except to a local group of -machines (for resource-balancing issues). So machines would automatically -keep in touch with other nearby machines, but it would be modulated by -distance. - -The big question is this (and for that matter, other models) is that -of authentication in some kind of reasonably reliable manner. - - The second (and easier) task is migration. - -Agreed. - -Erich - --- -Erich Stefan Boleyn \ Mad Genius wanna-be, CyberMuffin -Mathematician, Software Engineer \ slavering computer nerd -Internet E-mail: \ "Forget Artificial Intelligence, -Motto: "I'll live forever or die trying" \ I want the real thing!" diff --git a/unsorted/byte-letter.txt b/unsorted/byte-letter.txt new file mode 100644 index 00000000..20fa61a0 --- /dev/null +++ b/unsorted/byte-letter.txt @@ -0,0 +1,25 @@ +Byte magazine published this in the `Letters' section +of the March '96 issue: + + Where's the GNU Hurd? + + The November 1995 articles "NT Roars + on the 604" and "CPU scorecards" were + quite welcome. But the Special Report on + operating systems did not mention GNU + Hurd. This OS is based on the Mach mi- + crokernel, and thus it has been essentially + ported to a wide variety of hardware plat- + forms--nearly as many as NetBSD. To + learn more about the Hurd, and especially + about its binary portability, visit http:// + www.cs.pdx.edu/~trent/gnu/hurd/. Con- + trary to what you say in the text box "Op- + erating-System Research: Dim or Bright + Future?" (page 116), microkernel tech- + nology has not been exploited to its max- + imum capability, as the Hurd philosophy + demonstrates. + + Todd Hutchinson + jasper@terra.3rdplanet.com diff --git a/unsorted/hurd-fs-org b/unsorted/hurd-fs-org new file mode 100644 index 00000000..ba515623 --- /dev/null +++ b/unsorted/hurd-fs-org @@ -0,0 +1,219 @@ +From: mib@duality.gnu.ai.mit.edu (Michael I. Bushnell, p/BSG) +Newsgroups: gnu.misc.discuss +Subject: Re: GNU vs. Linux FSSTND conflict? +Date: 13 Aug 1995 22:31:18 GMT +Organization: Free Software Foundation, Cambridge, MA +In-reply-to: Rick Niles's message of 13 Aug 1995 16:20:29 GMT + +In article <40l8od$ia9@news4.digex.net> Rick Niles + writes: + + Is there a conflict between the GNU Filesystem Structure and + the Linux Filesystem Structure (FSSTND)? + +What you point out is the trivial difference; there are significant +lossages in FSSTND, such as the absence of libexec... + + I've heard on this newsgroup that the GNU std. is to elminate + the use of /usr. So: + + I guess the first question is: Is this true? + +Yes. + + If it is how do you answer those who say the root part. should + be small and only enough to boot the system? And + the rest of the system should be on a separate part. (/usr) + +In GNU the directory /bin will be an amalgam of several directories; +this well be done by the use of a translator in the Hurd. (It will be +similar to BSD shadow filesystems.) + +So we have no need to confuse users by putting binaries in two +different places. We can put different binaries in different physical +locations without either forcing them to appear in different places or +creating a forest of symlinks. + +But the FSSTND's arguments are bogus even for Unixoid systems which do +force differently located files to have different directory names: + + o It is often mounted from very small media. For example, many Linux + users install and recover systems by mounting root off a RAM disk, + which is copied from a single 1.44M or 1.2M floppy disk. + +This is a non-issue. Obviously a floppy can only have a small number +of files, but that's totally irrelevant in deciding what should be on +root on a fully loaded system. + + o The root filesystem has many system-specific configuration files in + it. Possible examples include a kernel that is specific to the + system, a different hostname, etc. This means that the root + filesystem isn't always shareable between networked systems. + Keeping it small on networked systems minimizes the amount of space + lost on servers to unshareable files. It also allows workstations + with smaller local hard drives. + +It should be possible to require only the etc directory to be +per-system; there is no reason that bin and such should be non-shared +at all. + + o While you may have the root filesystem on a large partition, and + may be able to fill it to your heart's content, there will be + people with smaller partitions. If you have more files installed, + you may find incompatibilities with other systems using root + filesystems on smaller partitions. If you are a developer then you + may be turning your assumption into a problem for a large number of + users. + +This is totally incoherent, as far as I can tell. If someone can tell +me what it means, then maybe I could help. What sort of +incompatibilities are expected? + +Michael + + + +From: gord@enci.ucalgary.ca (Gord Matzigkeit) +Newsgroups: gnu.misc.discuss +Subject: Re: GNU vs. Linux FSSTND conflict? +Date: 14 Aug 1995 18:55:20 -0600 +In-reply-to: mib@duality.gnu.ai.mit.edu's message of 13 Aug 1995 22:31:18 GMT + +-----BEGIN PGP SIGNED MESSAGE----- + +Hi! + +>>>>> "mib" == Michael I Bushnell, p/BSG writes: + + mib> In article <40l8od$ia9@news4.digex.net> Rick Niles + mib> writes: +[hack & slice] + + >> If it is how do you answer those who say the root + >> part. should be small and only enough to boot the system? And + >> the rest of the system should be on a separate part. (/usr) + + mib> In GNU the directory /bin will be an amalgam of several + mib> directories; this well be done by the use of a translator in the + mib> Hurd. (It will be similar to BSD shadow filesystems.) + +This is what I figured... my reply didn't get posted to USENET, +though, because our NNTP server has been down for the last day or two. + + mib> So we have no need to confuse users by putting binaries in two + mib> different places. We can put different binaries in different + mib> physical locations without either forcing them to appear in + mib> different places or creating a forest of symlinks. + +This is grand! One of my ideas that I mentioned to Rick was that I'm +currently using depot, and I see that the GNU union/shadowfs could +replace that. + +What depot does is manages symlinks for a "software environment" (a +more restricted version of what you have described). + +The way I think I'll be setting up my Hurd machine is to have all the +physical disks mounted under "/disk", each containing a fragment of +the filesystem. + +Now, my only concerns are: + +1) control files, as far as determining precedence, and what can and +cannot be shadowed (for collision resolution), and what is just +auxilliary info (like CVS directories in the site package, which +should not be mapped onto the software environment) + +2) packages. Is there some slick way to divide the filesystem into +"package pieces", like depot does? + +One suggestion to get (2), is that I could create an intermediate +directory, say "/package", that would be the union of various mounted +physical disks (under /disk), and would contain things like: + +emacs-19.30/bin +emacs-19.30/lib... +gcc-2.7.3/bin... +fileutils-5.8/man... +site/sbin/useful_perl_script + +et al. Then I would unionfs all the directories in the /package dir +onto the root filesystem. + +This would have most of the advantages I'm getting from depot, namely, +the ability to specify different precedences on different machines, +so that I can try out emacs-19.31 on one workstation without +disrupting the others. + +Is there a better way to do this? I do like the idea of three +different hierarchies for files (under /disk, where I can see what is +on each server; under /package, where I can see what is in each +package; the GNU standard dirs, where I actually use the files), but I +am hoping that there is something more elegant. Hmm. Maybe not. + + mib> It should be possible to require only the etc directory to be + mib> per-system; there is no reason that bin and such should be + mib> non-shared at all. + +This is one point (for security), that would mandate the use of config +files, so that the unionfs doesn't map /etc/some_important_file from +another server. + +This is yet another thing that I'm looking forward to. Thanks. ;) + +- --Gordon + +- -- +Gordon Matzigkeit | Heck, it was only a TOASTER... lighten up! +gord@enci.ucalgary.ca | PGP mail preferred... finger me for my key. +Keyprint: D5 66 08 E0 4D F4 D7 7B 8A C8 8A 9C 7F 39 25 A7 - ID 339ABEB9 + + +-----BEGIN PGP SIGNATURE----- +Version: 2.6.2 +Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface + +iQCVAwUBMC/wcyFsfCEzmr65AQHubwP7BGVHqs9ACB8hFUqDdF2oWu/lLq1hW/Oa +qra2ZfcKfIZq9hIM4tLRJ0qCaiOVm5MGLgH7Yax+ZyOPb4K0fCObzk1XY5b0enhV +9SR70UZ7Qm7MXj+PFCp5lxvrNiaFXMbil0EN5FQEvH9kUp0ed1NWcaXGqTK6gezm +YBUumt2Zadk= +=6f2c +-----END PGP SIGNATURE----- + + + + +From: mib@duality.gnu.ai.mit.edu (Michael I. Bushnell, p/BSG) +Newsgroups: gnu.misc.discuss +Subject: Re: GNU vs. Linux FSSTND conflict? +Date: 16 Aug 1995 14:43:47 GMT +In-reply-to: gord@enci.ucalgary.ca's message of 14 Aug 1995 18:55:20 -0600 + +In article gord@enci.ucalgary.ca (Gord Matzig +keit) writes: + + The way I think I'll be setting up my Hurd machine is to have all the + physical disks mounted under "/disk", each containing a fragment of + the filesystem. + +Our idea is to do something roughly like this. + + 1) control files, as far as determining precedence, and what can and + cannot be shadowed (for collision resolution), and what is just + auxilliary info (like CVS directories in the site package, which + should not be mapped onto the software environment) + +Yes, the relevant translator will support a *rich* set of semantics +for this kind of things specified by a control file. + + 2) packages. Is there some slick way to divide the filesystem into + "package pieces", like depot does? + +We're going to do this; rms and I have worked out a usable scheme that +meets all the necessary goals. + +The physical location of files has to be reflected by sharing rules +(see the GNU makefile standards); users have to be able to see all the +files relevant to a particular program easily; programs have to be +easily de-installed. We have a scheme that meets these three. + +Michael diff --git a/unsorted/hurd-migr b/unsorted/hurd-migr new file mode 100644 index 00000000..ce36c86c --- /dev/null +++ b/unsorted/hurd-migr @@ -0,0 +1,141 @@ +Path: usenet.ee.pdx.edu!cs.uoregon.edu!sgiblab!swrinde!howland.reston.ans.net!E +U.net!Germany.EU.net!netmbx.de!sietec.de!news!jh +From: jh@poseidon.sietec.de (Jochen Roger Hayek) +Newsgroups: gnu.misc.discuss +Subject: HURD & migration facilities +Date: 24 Oct 1994 15:12:34 GMT +Organization: Sietec Systemtechnik, Berlin +Lines: 16 +Distribution: world +Message-ID: +Reply-To: Jochen.Roger.Hayek@sietec.de +NNTP-Posting-Host: sunmiet3.sietec.de + +I read an article from acm's sigops vol. 28, number 4 this weekend, having the +title: + + a brief survey of systems providing + process or object migration facilities + by Mark Nuttall + +I found it very instructive. + +I think process / object migration should be considered for HURD, too, +and it's important to look at that before supporting / emulating +UNIX's fork and inherited open file descriptors, +because those features might get contradictory if not carefully designed. + +Regards esp. to the HURD folks + +JH + +Path: usenet.ee.pdx.edu!cs.uoregon.edu!sgiblab!spool.mu.edu!bloom-beacon.mit.ed +u!ai-lab!life.ai.mit.edu!mib +From: mib@churchy.gnu.ai.mit.edu (Michael I Bushnell) +Newsgroups: gnu.misc.discuss +Subject: Re: HURD & migration facilities +Date: 24 Oct 1994 18:10:25 GMT +Organization: Free Software Foundation, Cambridge, MA +Lines: 27 +Distribution: world +Message-ID: +References: +NNTP-Posting-Host: churchy.gnu.ai.mit.edu +In-reply-to: jh@poseidon.sietec.de's message of 24 Oct 1994 15:12:34 + GMT + +In article jh@poseidon.sietec.de (Jochen +Roger Hayek) writes: + + I think process / object migration should be considered for HURD, too, + and it's important to look at that before supporting / emulating + UNIX's fork and inherited open file descriptors, + because those features might get contradictory if not carefully designed. + +Process migration is not a problem for the Hurd--it's a problem for +Mach. If a Mach task can be correctly migrated, then there is no +problem. + +However, I want to do more than that with the Hurd; I want to have a +collection of machines (I think I'll call it a ``Collective'') appear +as a single machine. (Shades of amoeba here.) + +This is the first (and harder) task--making a single global space of +pids, etc. + +The second (and easier) task is migration. + + -mib +-- ++1 617 623 3248 (H) | En arche en ho logos, ++1 617 253 8568 (W) -+- kai ho logos en pros ton theon, +1105 Broadway | kai theos en ho logos. +Somerville, MA 02144 | Kai ho logos sarx egeneto, +mib@gnu.ai.mit.edu | kai eskenosen en hemin. + +Newsgroups: gnu.misc.discuss +Path: usenet.ee.pdx.edu!cs.uoregon.edu!reuter.cse.ogi.edu!psgrain!agora!hermes. +rdrop.com!erich +From: erich@uruk.org (Erich Boleyn) +Subject: Re: HURD & migration facilities +Sender: news@agora.rdrop.com (David Greenman) +Nntp-Posting-Host: uruk.org +Organization: RainDrop Laboratories +Message-ID: +References: + +In-Reply-To: mib@churchy.gnu.ai.mit.edu's message of 24 Oct 1994 18:10:25 GMT +Date: Sat, 29 Oct 1994 16:35:37 GMT +Lines: 50 + + +In article mib@churchy.gnu.ai.mit.ed +u (Michael I Bushnell) writes: + + Process migration is not a problem for the Hurd--it's a problem for + Mach. If a Mach task can be correctly migrated, then there is no + problem. + + However, I want to do more than that with the Hurd; I want to have a + collection of machines (I think I'll call it a ``Collective'') appear + as a single machine. (Shades of amoeba here.) + +Great! (I think we talked about this before...) + + This is the first (and harder) task--making a single global space of + pids, etc. + +This point seems somewhat questionable. Maybe we're thinking about +the same idea in the long run, but I don't think that migrating +data about the whole system around would be very useful... +I mean, you still want a very large collective to work, though it +could well get bogged down by the details of huge amounts of info. + +I think a more optimal (and more practical) approach would be to: + +Create a model of a "user context" that keeps track across multiple +machines what resources and programs a user is working with. + +There would also be publically known "services" that would be advertised. +Note that "advertising" is a specific activity that is usually not +performed, unless one desires to do so. + +Anything else is really of little or no concern except to a local group of +machines (for resource-balancing issues). So machines would automatically +keep in touch with other nearby machines, but it would be modulated by +distance. + +The big question is this (and for that matter, other models) is that +of authentication in some kind of reasonably reliable manner. + + The second (and easier) task is migration. + +Agreed. + +Erich + +-- +Erich Stefan Boleyn \ Mad Genius wanna-be, CyberMuffin +Mathematician, Software Engineer \ slavering computer nerd +Internet E-mail: \ "Forget Artificial Intelligence, +Motto: "I'll live forever or die trying" \ I want the real thing!" -- cgit v1.2.3 From 47d16b97b4d3f207b39f23a619e1c582ace2d476 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 23 Nov 2008 01:06:07 +0100 Subject: Assemble unsorted pages. --- Hurd/ABITransitionStatus.mdwn | 9 - Hurd/AptConfOffline.mdwn | 28 -- Hurd/BuildingHurdLiveCD.mdwn | 70 ----- Hurd/CrossHurd.mdwn | 99 ------- Hurd/CrossPlatformAliases.mdwn | 8 - Hurd/DebianX.mdwn | 130 --------- Hurd/DebianXorg.mdwn | 197 -------------- Hurd/DhcpClient.mdwn | 42 --- Hurd/DistributedServers.mdwn | 29 -- Hurd/ExtTwoSize.mdwn | 27 -- Hurd/ExtTwofsTranslator.mdwn | 4 - Hurd/FlashHurd.mdwn | 60 ----- Hurd/FtpfsTranslator.mdwn | 7 - Hurd/FunnyHurd.mdwn | 39 --- Hurd/FunnyHurd/CrystalAwards.jpg | Bin 13055 -> 0 bytes Hurd/FunnyHurd/HurdCarDeal.jpg | Bin 16144 -> 0 bytes Hurd/FunnyHurd/HurdExchange.gif | Bin 3078 -> 0 bytes Hurd/FunnyHurd/HurdLodge.jpg | Bin 38639 -> 0 bytes Hurd/FunnyHurd/HurdMagician.jpg | Bin 10703 -> 0 bytes Hurd/FunnyHurd/hurd-windows.gif | Bin 14799 -> 0 bytes Hurd/GNOME.mdwn | 11 - Hurd/GNUstep.mdwn | 64 ----- Hurd/GrantBowHurdPage.mdwn | 36 --- Hurd/GrantBowHurdPage/diagram.png | Bin 2139 -> 0 bytes Hurd/GrantBowHurdPage/diagram.xcf | Bin 5492 -> 0 bytes Hurd/HurdDevelopers.mdwn | 120 --------- Hurd/HurdOnL4.mdwn | 173 ------------ Hurd/HurdOnL4/menu.lst | 55 ---- Hurd/InstallNotes.mdwn | 295 --------------------- Hurd/InteractiveTranslators.mdwn | 31 --- Hurd/JoachimNilssonHurdPage.mdwn | 247 ----------------- Hurd/JoachimNilssonHurdPage/patch_kit.jpg | Bin 9469 -> 0 bytes Hurd/KernelCousinDebianHurd.mdwn | 3 - Hurd/KnownHurdLimits.mdwn | 20 -- Hurd/LuisBustamanteHurdPage.mdwn | 11 - Hurd/MakeImage.mdwn | 60 ----- Hurd/PosixThreads.mdwn | 21 -- Hurd/PppDaemon.mdwn | 6 - Hurd/RequirementsForLiveCD.mdwn | 54 ---- Hurd/SeenHurd.mdwn | 71 ----- Hurd/SeenHurd/lmf10_1999.jpg | Bin 63327 -> 0 bytes Hurd/SerialConsole.mdwn | 28 -- Hurd/Shopping.mdwn | 13 - Hurd/Translation.mdwn | 18 -- Hurd/TranslatorExamples.mdwn | 61 ----- Hurd/TranslatorPages.mdwn | 51 ---- Hurd/TranslatorWishList.mdwn | 193 -------------- Hurd/WebHome/hurd_sm_mf.png | Bin 1434 -> 0 bytes Hurd/WhoRunsGNU.mdwn | 31 --- Hurd/XattrHurd.mdwn | 5 - Hurd/Xfree86.mdwn | 109 -------- Hurd/ZallocPanics.mdwn | 43 --- Mach/AdvancedGrubUsage.mdwn | 42 --- Mach/BuildingOskitMach.mdwn | 190 ------------- Mach/BuildingOskitMach/modules-light.x86.pc | 236 ----------------- Mach/BuildingOskitMach/modules.x86.pc | 236 ----------------- Mach/OskitMach.mdwn | 64 ----- Mach/OskitMachPatches.mdwn | 10 - .../patch-gnumach_softclock-wagi.diff.gz | Bin 576 -> 0 bytes .../patch-gnumach_softint-wagi.diff.gz | Bin 1799 -> 0 bytes Mach/OskitMachStatusList.mdwn | 15 -- Mach/OskitPatches.mdwn | 67 ----- Mach/OskitPatches/patch-oskit-0.97-eepro.diff.gz | Bin 301 -> 0 bytes .../OskitPatches/patch-oskit-0.97-i_khavki.diff.gz | Bin 405 -> 0 bytes .../patch-oskit-0.97-jon_arney.diff.gz | Bin 282 -> 0 bytes .../OskitPatches/patch-oskit-0.97-kkraemer.diff.gz | Bin 367 -> 0 bytes .../patch-oskit-0.97-sbrk_hack.diff.gz | Bin 283 -> 0 bytes Mach/PortToL4.mdwn | 42 --- Mach/PosixSemaphores.mdwn | 13 - Mach/RemoteDebugOskitMach.mdwn | 195 -------------- unsorted/ABITransitionStatus.mdwn | 9 + unsorted/AdvancedGrubUsage.mdwn | 42 +++ unsorted/AptConfOffline.mdwn | 28 ++ unsorted/BuildingHurdLiveCD.mdwn | 70 +++++ unsorted/BuildingOskitMach.mdwn | 190 +++++++++++++ unsorted/BuildingOskitMach/modules-light.x86.pc | 236 +++++++++++++++++ unsorted/BuildingOskitMach/modules.x86.pc | 236 +++++++++++++++++ unsorted/CrossHurd.mdwn | 99 +++++++ unsorted/CrossPlatformAliases.mdwn | 8 + unsorted/DebianX.mdwn | 130 +++++++++ unsorted/DebianXorg.mdwn | 197 ++++++++++++++ unsorted/DhcpClient.mdwn | 42 +++ unsorted/DistributedServers.mdwn | 29 ++ unsorted/ExtTwoSize.mdwn | 27 ++ unsorted/ExtTwofsTranslator.mdwn | 4 + unsorted/FlashHurd.mdwn | 60 +++++ unsorted/FtpfsTranslator.mdwn | 7 + unsorted/FunnyHurd.mdwn | 39 +++ unsorted/FunnyHurd/CrystalAwards.jpg | Bin 0 -> 13055 bytes unsorted/FunnyHurd/HurdCarDeal.jpg | Bin 0 -> 16144 bytes unsorted/FunnyHurd/HurdExchange.gif | Bin 0 -> 3078 bytes unsorted/FunnyHurd/HurdLodge.jpg | Bin 0 -> 38639 bytes unsorted/FunnyHurd/HurdMagician.jpg | Bin 0 -> 10703 bytes unsorted/FunnyHurd/hurd-windows.gif | Bin 0 -> 14799 bytes unsorted/GNOME.mdwn | 11 + unsorted/GNUstep.mdwn | 64 +++++ unsorted/GrantBowHurdPage.mdwn | 36 +++ unsorted/GrantBowHurdPage/diagram.png | Bin 0 -> 2139 bytes unsorted/GrantBowHurdPage/diagram.xcf | Bin 0 -> 5492 bytes unsorted/HurdDevelopers.mdwn | 120 +++++++++ unsorted/HurdOnL4.mdwn | 173 ++++++++++++ unsorted/HurdOnL4/menu.lst | 55 ++++ unsorted/InteractiveTranslators.mdwn | 31 +++ unsorted/JoachimNilssonHurdPage.mdwn | 247 +++++++++++++++++ unsorted/JoachimNilssonHurdPage/patch_kit.jpg | Bin 0 -> 9469 bytes unsorted/KernelCousinDebianHurd.mdwn | 3 + unsorted/KnownHurdLimits.mdwn | 20 ++ unsorted/LuisBustamanteHurdPage.mdwn | 11 + unsorted/MakeImage.mdwn | 60 +++++ unsorted/OskitMach.mdwn | 64 +++++ unsorted/OskitMachPatches.mdwn | 10 + .../patch-gnumach_softclock-wagi.diff.gz | Bin 0 -> 576 bytes .../patch-gnumach_softint-wagi.diff.gz | Bin 0 -> 1799 bytes unsorted/OskitMachStatusList.mdwn | 15 ++ unsorted/OskitPatches.mdwn | 67 +++++ .../OskitPatches/patch-oskit-0.97-eepro.diff.gz | Bin 0 -> 301 bytes .../OskitPatches/patch-oskit-0.97-i_khavki.diff.gz | Bin 0 -> 405 bytes .../patch-oskit-0.97-jon_arney.diff.gz | Bin 0 -> 282 bytes .../OskitPatches/patch-oskit-0.97-kkraemer.diff.gz | Bin 0 -> 367 bytes .../patch-oskit-0.97-sbrk_hack.diff.gz | Bin 0 -> 283 bytes unsorted/PortToL4.mdwn | 42 +++ unsorted/PosixSemaphores.mdwn | 13 + unsorted/PosixThreads.mdwn | 21 ++ unsorted/PppDaemon.mdwn | 6 + unsorted/RemoteDebugOskitMach.mdwn | 195 ++++++++++++++ unsorted/RequirementsForLiveCD.mdwn | 54 ++++ unsorted/SeenHurd.mdwn | 71 +++++ unsorted/SeenHurd/lmf10_1999.jpg | Bin 0 -> 63327 bytes unsorted/SerialConsole.mdwn | 28 ++ unsorted/Shopping.mdwn | 13 + unsorted/Translation.mdwn | 18 ++ unsorted/TranslatorExamples.mdwn | 61 +++++ unsorted/TranslatorPages.mdwn | 51 ++++ unsorted/TranslatorWishList.mdwn | 193 ++++++++++++++ unsorted/WebHome/hurd_sm_mf.png | Bin 0 -> 1434 bytes unsorted/WhoRunsGNU.mdwn | 31 +++ unsorted/XattrHurd.mdwn | 5 + unsorted/Xfree86.mdwn | 109 ++++++++ unsorted/ZallocPanics.mdwn | 43 +++ 139 files changed, 3394 insertions(+), 3689 deletions(-) delete mode 100644 Hurd/ABITransitionStatus.mdwn delete mode 100644 Hurd/AptConfOffline.mdwn delete mode 100644 Hurd/BuildingHurdLiveCD.mdwn delete mode 100644 Hurd/CrossHurd.mdwn delete mode 100644 Hurd/CrossPlatformAliases.mdwn delete mode 100644 Hurd/DebianX.mdwn delete mode 100644 Hurd/DebianXorg.mdwn delete mode 100644 Hurd/DhcpClient.mdwn delete mode 100644 Hurd/DistributedServers.mdwn delete mode 100644 Hurd/ExtTwoSize.mdwn delete mode 100644 Hurd/ExtTwofsTranslator.mdwn delete mode 100644 Hurd/FlashHurd.mdwn delete mode 100644 Hurd/FtpfsTranslator.mdwn delete mode 100644 Hurd/FunnyHurd.mdwn delete mode 100644 Hurd/FunnyHurd/CrystalAwards.jpg delete mode 100644 Hurd/FunnyHurd/HurdCarDeal.jpg delete mode 100644 Hurd/FunnyHurd/HurdExchange.gif delete mode 100644 Hurd/FunnyHurd/HurdLodge.jpg delete mode 100644 Hurd/FunnyHurd/HurdMagician.jpg delete mode 100644 Hurd/FunnyHurd/hurd-windows.gif delete mode 100644 Hurd/GNOME.mdwn delete mode 100644 Hurd/GNUstep.mdwn delete mode 100644 Hurd/GrantBowHurdPage.mdwn delete mode 100644 Hurd/GrantBowHurdPage/diagram.png delete mode 100644 Hurd/GrantBowHurdPage/diagram.xcf delete mode 100644 Hurd/HurdDevelopers.mdwn delete mode 100644 Hurd/HurdOnL4.mdwn delete mode 100644 Hurd/HurdOnL4/menu.lst delete mode 100644 Hurd/InstallNotes.mdwn delete mode 100644 Hurd/InteractiveTranslators.mdwn delete mode 100644 Hurd/JoachimNilssonHurdPage.mdwn delete mode 100644 Hurd/JoachimNilssonHurdPage/patch_kit.jpg delete mode 100644 Hurd/KernelCousinDebianHurd.mdwn delete mode 100644 Hurd/KnownHurdLimits.mdwn delete mode 100644 Hurd/LuisBustamanteHurdPage.mdwn delete mode 100644 Hurd/MakeImage.mdwn delete mode 100644 Hurd/PosixThreads.mdwn delete mode 100644 Hurd/PppDaemon.mdwn delete mode 100644 Hurd/RequirementsForLiveCD.mdwn delete mode 100644 Hurd/SeenHurd.mdwn delete mode 100644 Hurd/SeenHurd/lmf10_1999.jpg delete mode 100644 Hurd/SerialConsole.mdwn delete mode 100644 Hurd/Shopping.mdwn delete mode 100644 Hurd/Translation.mdwn delete mode 100644 Hurd/TranslatorExamples.mdwn delete mode 100644 Hurd/TranslatorPages.mdwn delete mode 100644 Hurd/TranslatorWishList.mdwn delete mode 100644 Hurd/WebHome/hurd_sm_mf.png delete mode 100644 Hurd/WhoRunsGNU.mdwn delete mode 100644 Hurd/XattrHurd.mdwn delete mode 100644 Hurd/Xfree86.mdwn delete mode 100644 Hurd/ZallocPanics.mdwn delete mode 100644 Mach/AdvancedGrubUsage.mdwn delete mode 100644 Mach/BuildingOskitMach.mdwn delete mode 100644 Mach/BuildingOskitMach/modules-light.x86.pc delete mode 100644 Mach/BuildingOskitMach/modules.x86.pc delete mode 100644 Mach/OskitMach.mdwn delete mode 100644 Mach/OskitMachPatches.mdwn delete mode 100644 Mach/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz delete mode 100644 Mach/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz delete mode 100644 Mach/OskitMachStatusList.mdwn delete mode 100644 Mach/OskitPatches.mdwn delete mode 100644 Mach/OskitPatches/patch-oskit-0.97-eepro.diff.gz delete mode 100644 Mach/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz delete mode 100644 Mach/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz delete mode 100644 Mach/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz delete mode 100644 Mach/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz delete mode 100644 Mach/PortToL4.mdwn delete mode 100644 Mach/PosixSemaphores.mdwn delete mode 100644 Mach/RemoteDebugOskitMach.mdwn create mode 100644 unsorted/ABITransitionStatus.mdwn create mode 100644 unsorted/AdvancedGrubUsage.mdwn create mode 100644 unsorted/AptConfOffline.mdwn create mode 100644 unsorted/BuildingHurdLiveCD.mdwn create mode 100644 unsorted/BuildingOskitMach.mdwn create mode 100644 unsorted/BuildingOskitMach/modules-light.x86.pc create mode 100644 unsorted/BuildingOskitMach/modules.x86.pc create mode 100644 unsorted/CrossHurd.mdwn create mode 100644 unsorted/CrossPlatformAliases.mdwn create mode 100644 unsorted/DebianX.mdwn create mode 100644 unsorted/DebianXorg.mdwn create mode 100644 unsorted/DhcpClient.mdwn create mode 100644 unsorted/DistributedServers.mdwn create mode 100644 unsorted/ExtTwoSize.mdwn create mode 100644 unsorted/ExtTwofsTranslator.mdwn create mode 100644 unsorted/FlashHurd.mdwn create mode 100644 unsorted/FtpfsTranslator.mdwn create mode 100644 unsorted/FunnyHurd.mdwn create mode 100644 unsorted/FunnyHurd/CrystalAwards.jpg create mode 100644 unsorted/FunnyHurd/HurdCarDeal.jpg create mode 100644 unsorted/FunnyHurd/HurdExchange.gif create mode 100644 unsorted/FunnyHurd/HurdLodge.jpg create mode 100644 unsorted/FunnyHurd/HurdMagician.jpg create mode 100644 unsorted/FunnyHurd/hurd-windows.gif create mode 100644 unsorted/GNOME.mdwn create mode 100644 unsorted/GNUstep.mdwn create mode 100644 unsorted/GrantBowHurdPage.mdwn create mode 100644 unsorted/GrantBowHurdPage/diagram.png create mode 100644 unsorted/GrantBowHurdPage/diagram.xcf create mode 100644 unsorted/HurdDevelopers.mdwn create mode 100644 unsorted/HurdOnL4.mdwn create mode 100644 unsorted/HurdOnL4/menu.lst create mode 100644 unsorted/InteractiveTranslators.mdwn create mode 100644 unsorted/JoachimNilssonHurdPage.mdwn create mode 100644 unsorted/JoachimNilssonHurdPage/patch_kit.jpg create mode 100644 unsorted/KernelCousinDebianHurd.mdwn create mode 100644 unsorted/KnownHurdLimits.mdwn create mode 100644 unsorted/LuisBustamanteHurdPage.mdwn create mode 100644 unsorted/MakeImage.mdwn create mode 100644 unsorted/OskitMach.mdwn create mode 100644 unsorted/OskitMachPatches.mdwn create mode 100644 unsorted/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz create mode 100644 unsorted/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz create mode 100644 unsorted/OskitMachStatusList.mdwn create mode 100644 unsorted/OskitPatches.mdwn create mode 100644 unsorted/OskitPatches/patch-oskit-0.97-eepro.diff.gz create mode 100644 unsorted/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz create mode 100644 unsorted/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz create mode 100644 unsorted/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz create mode 100644 unsorted/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz create mode 100644 unsorted/PortToL4.mdwn create mode 100644 unsorted/PosixSemaphores.mdwn create mode 100644 unsorted/PosixThreads.mdwn create mode 100644 unsorted/PppDaemon.mdwn create mode 100644 unsorted/RemoteDebugOskitMach.mdwn create mode 100644 unsorted/RequirementsForLiveCD.mdwn create mode 100644 unsorted/SeenHurd.mdwn create mode 100644 unsorted/SeenHurd/lmf10_1999.jpg create mode 100644 unsorted/SerialConsole.mdwn create mode 100644 unsorted/Shopping.mdwn create mode 100644 unsorted/Translation.mdwn create mode 100644 unsorted/TranslatorExamples.mdwn create mode 100644 unsorted/TranslatorPages.mdwn create mode 100644 unsorted/TranslatorWishList.mdwn create mode 100644 unsorted/WebHome/hurd_sm_mf.png create mode 100644 unsorted/WhoRunsGNU.mdwn create mode 100644 unsorted/XattrHurd.mdwn create mode 100644 unsorted/Xfree86.mdwn create mode 100644 unsorted/ZallocPanics.mdwn (limited to 'unsorted') diff --git a/Hurd/ABITransitionStatus.mdwn b/Hurd/ABITransitionStatus.mdwn deleted file mode 100644 index 123e8f8c..00000000 --- a/Hurd/ABITransitionStatus.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -Several transitions have occured recently. - -* [ABI Switch](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00096.html) from April 17, 2002 - -* [Phase I accomplished](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00157.html) from April 26, 2002 - -* [status of the ABI transition](http://lists.debian.org/debian-hurd/2002/debian-hurd-200205/msg00242.html) from May 15, 2002 - --- [[Main/GrantBow]] - 15 May 2002 diff --git a/Hurd/AptConfOffline.mdwn b/Hurd/AptConfOffline.mdwn deleted file mode 100644 index c4cc85be..00000000 --- a/Hurd/AptConfOffline.mdwn +++ /dev/null @@ -1,28 +0,0 @@ - APT - { - /* This file belongs in Debian GNU/Hurd's /etc/apt/apt.conf.offline - and will be used when running Debian GNU/Linux. This is only - required when the GNU/Hurd does not have network access. */ - - 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 - assumes Debian GNU/Hurd mounted on /misc/hurd and /var mounted underneath this if necessary */ - - // State::lists should be here, the lists subdirectory. - State "/misc/hurd/var/lib/apt/"; - State::status "/misc/hurd/var/lib/dpkg/status"; - - // Binary caches will be stored locally - Cache::archives "/misc/hurd/var/cache/apt/archives/"; - Cache "/tmp/"; - - // Location of the source list. - Etc "/misc/hurd/etc/apt/"; - }; diff --git a/Hurd/BuildingHurdLiveCD.mdwn b/Hurd/BuildingHurdLiveCD.mdwn deleted file mode 100644 index e2082268..00000000 --- a/Hurd/BuildingHurdLiveCD.mdwn +++ /dev/null @@ -1,70 +0,0 @@ -# Recipes for bootable GNU Mach/Hurd Live CD - -## Greg's recipe - -In my attempts to get a bootable CD for the Hurd here's the recipe I followed, your's will be similar. I needed a grub-0.92, with a patch from , and version 1.16 of mkbimage (I don't exactly remember where I got that from). - -You can grab a copy of it at , which is a gzipped bootable \*.iso with the copy of the patched grub and the version of mkbimage I used. Here's the recipe I followed (under linux). - - # mkdir ./2.88floppy - # mkdir ./isodir - # cp grub/* 2.88floppy/boot/grub/ - # cp grub/* isodir/boot/grub/ - # cd 2.88floppy - # tar -cf ../floppyimg.tar * - # cd .. - # mkbimage -f floppyimg.tar -t 2.88 - # cp 2.88.image isodir/ - # mkisofs -r -b 2.88.image -c boot.catalog -o hurdcd.iso isodir/ - # cdrecord -v speed=4 dev=0,0,0 -data hurdcd.iso - -That was the recipe for using a floppy image. If you use the `-t hd` switch of `mkbimage`, you'll get an ext2fs El-Torito HD emulation image that can be any size (I've got one here 300+ MB). You can then use `root (hd0,0)` in Grub to boot something. Also, invoking `mkbimage` with no parameters will give you some additional help messages. - --- [[Main/GregBuchholz]] - 05 Nov 2003 - -## Another recipe for a bootable GNU CD - -[screenshot](http:///mycelium.afraid.org/Screenshot2.png) - -### What you'll need - -* A [stage2\_eltorito](http://mycelium.dyndns.org/stage2_eltorito) from [grub 0.95](http://www.gnu.org/software/grub) -* A [base system](http://www.update.uu.se/~ams/gnu/gnu-2004-12-04.tar.bz2) -* [iso9660fs.static](http:///mycelium.dyndns.org/iso9660fs.static) (this link is bought the farm) or just build your own, it should work with CVS - -### HowTo - - # mkdir iso - ..(at this point untar or setup base system) - # mkdir -p iso/boot/grub - # cp iso9660fs.static iso/hurd - # cp stage2_eltorito iso/boot/grub - ..(edit iso/boot/grub/grub.conf) - # mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \ - -boot-load-size 4 -boot-info-table -o livecd.iso iso/ - -**_Note:_** The following files must **\_NOT\_** be symlinks! - -* `/boot/gnumach` -* `/hurd/iso9660fs.static` -* `/hurd/exec` -* `/lib/ld.so.1` - -## Contents of grub.conf - - timeout 60 - default 0 - - title GNU/Hurd CD - #uppermem 523648 #this may need to be set - #root (cd) - kernel /boot/gnumach root=device:hd2 #set device to your cdrom device - module /hurd/iso9660fs.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) - -**_Note:_** The `root (cd)` line may prevent some computers from booting the livecd. - --- [[Main/AndrewResch]] - 22 Feb 2005 diff --git a/Hurd/CrossHurd.mdwn b/Hurd/CrossHurd.mdwn deleted file mode 100644 index d33d2a00..00000000 --- a/Hurd/CrossHurd.mdwn +++ /dev/null @@ -1,99 +0,0 @@ -This will eventually become an installation guide for the Debian crosshurd package (GNU/Hurd cross install only). However, for the time being I am setting it up as a diet version of Hurd/InstalNotes, adapted for crosshurd, adapted for me. - --- [[Main/JoachimNilsson]] - 14 Mar 2004 - -## Reserving partitions - -You need a swap and root partition, much like any other UNIX system. Two things to remember: - -1. Root partition still <2.0 GiB -2. Root partition: mke2fs -o hurd -b 4096 -L Carlsberg - -From a Debian GNU/Linux installation preparing install of GNU/Hurd on /dev/hdb2 reusing the Linux swap on /dev/hdb4. - - # mke2fs -o hurd -b 4096 -L Carlsberg /dev/hdb2 - -

- "Carlsberg. Probably the best beer in the world." -

- -## Bootstrapping - -After having installed the Debian crosshurd package you need to mount your newly created Hurd partition. - - mkdir /gnu - mount /dev/hdb2 /gnu - -Now, simply run the crosshurd program and follow the onscreen directions. **Do** select the usr symlink. - - crosshurd - -crosshurd burps a lot of unneeded information on screen and probably fails to install one or two files due to duplicates between GNU and Debian packages. Lets hope this mess is worked out some day. - -## Rebooting - -Before we reboot you must setup a Hurd entry in the menu.lst file of Grub. Do it like this and remember, **no trailing spaces**! - -The first two runs (reboots) you must run the Hurd in single-user mode! - - title GNU (kernel GNUmach 1.3) - root (hd1,1) - kernel /boot/gnumach.gz root=device:hd1s2 -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) - -The notation of Grub, and of the Hurd, can be somewhat bisarre on first sight. Consult the [[InstallNotes]] document and the Grub manual for a thorough explanation. - -N.B. the '-s' on the kernel line, it is "single user mode", which you need for the first two reboots. - -OK, reboot now. - -## First steps - -Set TERM variable and run native-install script. - - export TERM=mach - ./native-install - -At the end native-install wants you to reboot and run it again. Do so and remember to set the TERM variable as well. - -After the second reboot and native-install run you can remove the '-s' in the kernel line above and boot GNU/Hurd as a normal user. - -## Logging in - -Finally, a complete bootstrapped GNU system. - - login root - - export TERM=mach - - nano /etc/fstab - [add swap partition /dev/hd1s4] - - nano /etc/ttys - [remove all hashes to enable the new Hurd Console] - - settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0 - - dselect - -Now, do the old Debian thing of dancing with dselect for a couple of hours. - -Reboot and start the new [[Console]] - - login root - - console -d vga -d pc_kbd -d generic_speaker /dev/vcs - -Move around just like in Linux console, but with persistent scroll-back buffers for each console. - -## References - -* [[InstallNotes]] -* [[Network]] -* [[Console]] diff --git a/Hurd/CrossPlatformAliases.mdwn b/Hurd/CrossPlatformAliases.mdwn deleted file mode 100644 index 06a0e897..00000000 --- a/Hurd/CrossPlatformAliases.mdwn +++ /dev/null @@ -1,8 +0,0 @@ - # Aliases assume Debian GNU/Hurd mounted on /misc/hurd - # possibly via autofs /etc/auto.misc configuration and 'cd / && ln -s var/autofs/misc misc' - alias locatehurd="locate -d /misc/hurd/var/lib/locate/locatedb" - alias apt-cachehurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-cache" - alias apt-gethurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-get" - # dselect requires APT_CONFIG due to dselect apt method - alias dselecthurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline dselect --admindir /misc/hurd/var/lib/dpkg/" - alias dpkghurd="dpkg --root=/misc/hurd"= diff --git a/Hurd/DebianX.mdwn b/Hurd/DebianX.mdwn deleted file mode 100644 index 00692ca8..00000000 --- a/Hurd/DebianX.mdwn +++ /dev/null @@ -1,130 +0,0 @@ -# Setting up X on Debian GNU/Hurd - -#### Table Of Contents - -%TOC% - -This is a brief helper on how to setup X-Windows on Debian GNU/Hurd. - -Obviously this text is taken from the page but I was making such drastic changes, I didn't want to hack up that page. - -### Mouse & Keyboard - -See [[console]] for more details. - -You should instruct the Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: - - # console -d vga -d pc_kbd --repeat=kbd \ - -d pc_mouse --repeat=mouse --protocol=ps/2 -c /dev/cons /dev/vcs - -Symbolic links to repeaters should also be created: - - # ln -s /dev/cons/kbd /dev/kbd - # ln -s /dev/cons/mouse /dev/mouse - -### Selecting & Configuring Packages - -You will need several X packages. The `x-window-system-core` brings you most of what you need: - -* `xserver-xfree86` -* `xfonts-base` -* `xfonts-100dpi` -* `xfonts-75dpi` -* `xfonts-scalable` -* `xbase-clients` -* `xutils` -* `rxvt` -* ... as well as your window manager of choice: - * WindowMaker, `wmaker` - * FVWM, `fvwm` - * Blackbox, `blackbox` - * TWM, `twm` - -I know that twm and Window Maker work, however, I cannot attest to the other two. Also, Michael Banck has a working package for xfce4 for those of you that are interested. The link for the package is here: - - deb http://people.debian.org/~mbanck/hurd-xfce4/ ./ - -Thanks for that Michael!! - -You will probably need to create a .xsession file for xfce4 with the following command: - - exec /usr/bin/startxfce4 || exec xterm - -This will start the xfce4 desktop or dump to xterm if it fails to start. - -The recommended way of configuring X is using the `xserver-xfree86` debconf template, eg: - - # dpkg-reconfigure xserver-xfree86 - -It may be easier to just copy a working configuration from another operating system on the same computer and place it in `/etc/X11/XF86Config-4`, but this is discouraged as you would have to remove some sections by hand. - -**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. - -**_UPDATE 12/28/2004:_** Speedo is working on mine and is currently running. I do not have DRI enabled however. - -### Edit XF86Config-4 - -Now you have to edit the file manually to ensure that the mouse sections look like this: - - Section "InputDevice" - Identifier "Configured Mouse" - Driver "mouse" - Option "CorePointer" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - - Section "InputDevice" - Identifier "Generic Mouse" - Driver "mouse" - Option "SendCoreEvents" "true" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - -You may also enable the Emulate3Buttons option, but nothing else will work. - - Option "Emulate3Buttons" "true" - -**_WARNING:_** I cannot verify as of yet whether it was the "Emulate3Buttons" setting or the "ZAxisMapping" setting but I had to disable both in order to be able to move and resize windows. - -### Dynamic Linking - -The Hurd does not use `ld.so.conf`, it is necessary to add the following to `/etc/profile` to be sure that the libraries are found: - - LD_LIBRARY_PATH=/X11R6/lib:$LD_LIBRARY_PATH - -"This is a linker issue. GNU/Hurd expects that \`RPATH' is used, however, Debian takes certain measures to avoid this. Note that this does not cut it for suid binaries because of security implications. We expect to rectify this by using \`RUNPATH', which is specified in the new ELF standard." -- [Why does X not work?](http://www.gnu.org/software/hurd/faq.en.html#q4-8) - -**_CAVEAT 12/28/2004:_** I did not have to do this so can someone verify that this still needs to be done or was it fixed? Thanks! - -### Starting X - -Finally, run `startx` - -However, there are several caveats to be aware of: - -* `xterm` does not work correctly; try `rxvt`. - -**_UPDATE 12/28/2004_**: xterm works fine for me. - -* `update-menu` does not yet work. As such, there are no fine Debian menus. -* GNOME can now be ported with the new pthreads, but is still being worked on. Window Maker, TWM, Blackbox and FVWM all work. - -**_WARNING:_** If you get an error about opening the display or a permissions issue, you may need to run the following: - - # dpkg-reconfigure xserver-common - -change from "Console Users Only" to "Anybody" - -### Miscellaneous - -The dillo web browser does work, though it is not the greatest browser. - -For you xchat lovers like me, xchat will compile if you disable the python module. (The python module causes an assertion failure in pthreads if one of you guru's wants to fix and package. **hint,hint**) - -Good luck and enjoy! - ----- - --- [[Main/BarryDeFreese]] - 28 Dec 2004 diff --git a/Hurd/DebianXorg.mdwn b/Hurd/DebianXorg.mdwn deleted file mode 100644 index 1599c689..00000000 --- a/Hurd/DebianXorg.mdwn +++ /dev/null @@ -1,197 +0,0 @@ -# Setting up Xorg on Debian GNU/Hurd - -#### Table Of Contents - -%TOC% - -This is a brief helper on how to setup Xorg on Debian GNU/Hurd. - -Obviously this text is taken from the page but I was making such drastic changes, I didn't want to hack up that page. - -### Mouse & Keyboard - -See [[console]] for more details. - -You should instruct the Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: - - # console -d vga -d pc_kbd --repeat=kbd -d generic_speaker \ - -d pc_mouse --repeat=mouse --protocol=ps/2 -c /dev/vcs - -Symbolic links to repeaters should also be created: - - # ln -s /dev/cons/kbd /dev/kbd - # ln -s /dev/cons/mouse /dev/mouse - -### Selecting & Configuring Packages - -The `x-window-system-core` package brings you most of what you need for a base, plus you need to choose a window manager: - -* WindowMaker, `wmaker` -* FVWM, `fvwm` -* Blackbox, `blackbox` -* TWM, `twm` - -I know that Window Maker works, however, I cannot attest to the others. xfce4 might be temporarily broken. - -The recommended way of configuring X is using the `xserver-xorg` debconf template, eg: - - # dpkg-reconfigure xserver-xorg - -This currently seems to be broken in the Debian package so it may be easier to just copy a working configuration from another operating system on the same computer and place it in `/etc/X11/xorg.conf`. You need to edit the mouse settings by hand according to the below example, though. - -**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. - -**BDd: I cannot attest to this currently.** - -### Edit xorg.conf - -If you managed to get an xorg.conf autogenerated, make sure to have the mouse section read as follows: - - Section "InputDevice" - Identifier "Configured Mouse" - Driver "mouse" - Option "CorePointer" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - -Do not set the "Emulate3Button" or "ZAxisMapping" options, they do not work and break things. - -Here is an example of an xorg.conf using VESA at 800x600 that works on my Dell laptop: - - # /etc/X11/xorg.conf (xorg X Window System server configuration file) - # - # This file was generated by dexconf, the Debian X Configuration tool, using - # values from the debconf database. - # - # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. - # (Type "man /etc/X11/xorg.conf" at the shell prompt.) - # - # This file is automatically updated on xserver-xorg package upgrades *only* - # if it has not been modified since the last upgrade of the xserver-xorg - # package. - # - # If you have edited this file but would like it to be automatically updated - # again, run the following command: - # sudo dpkg-reconfigure -phigh xserver-xorg - - Section "Files" - FontPath "/usr/share/X11/fonts/misc" - FontPath "/usr/share/X11/fonts/cyrillic" - FontPath "/usr/share/X11/fonts/100dpi/:unscaled" - FontPath "/usr/share/X11/fonts/75dpi/:unscaled" - FontPath "/usr/share/X11/fonts/Type1" - FontPath "/usr/share/X11/fonts/CID" - FontPath "/usr/share/X11/fonts/100dpi" - FontPath "/usr/share/X11/fonts/75dpi" - # paths to defoma fonts - FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" - FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID" - EndSection - - Section "Module" - Load "GLcore" - Load "i2c" - Load "bitmap" - Load "ddc" - Load "extmod" - Load "freetype" - Load "glx" - Load "int10" - Load "type1" - Load "vbe" - EndSection - - Section "InputDevice" - Identifier "Generic Keyboard" - Driver "kbd" - Option "CoreKeyboard" - Option "XkbRules" "xorg" - Option "XkbModel" "pc104" - Option "XkbLayout" "us" - EndSection - - Section "InputDevice" - Identifier "Configured Mouse" - Driver "mouse" - Option "CorePointer" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - - Section "InputDevice" - Identifier "Synaptics Touchpad" - Driver "synaptics" - Option "SendCoreEvents" "true" - Option "Device" "/dev/psaux" - Option "Protocol" "auto-dev" - Option "HorizScrollDelta" "0" - EndSection - - Section "Device" - Identifier "Videocard0" - Driver "vesa" - EndSection - - Section "Monitor" - Identifier "Monitor0" - VendorName "Dell" - HorizSync 31.5 - 90.0 - VertRefresh 59.0 - 85.0 - Option "DPMS" - EndSection - - Section "Screen" - Identifier "Screen0" - Device "Videocard0" - Monitor "Monitor0" - DefaultDepth 24 - SubSection "Display" - Depth 1 - Modes "800x600" - EndSubSection - SubSection "Display" - Depth 4 - Modes "800x600" - EndSubSection - SubSection "Display" - Depth 8 - Modes "800x600" - EndSubSection - SubSection "Display" - Depth 15 - Modes "800x600" - EndSubSection - SubSection "Display" - Depth 16 - Modes "800x600" - EndSubSection - SubSection "Display" - Depth 24 - Modes "800x600" - EndSubSection - EndSection - - Section "DRI" - Mode 0666 - EndSection - -### Starting X - -Finally, run `startx` - -However, there are several caveats to be aware of: - -* `update-menu` does not yet work. As such, there are no fine Debian menus. - -**_WARNING:_** If you get an error about opening the display or a permissions issue, you may need to run the following: - - # dpkg-reconfigure x11-common - -change from "Console Users Only" to "Anybody" - -Good luck and enjoy! - ----- - --- [[Main/BarryDeFreese]] - 02 Mar 2006 diff --git a/Hurd/DhcpClient.mdwn b/Hurd/DhcpClient.mdwn deleted file mode 100644 index 442f4781..00000000 --- a/Hurd/DhcpClient.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -# DHCP and the Hurd - -According to the following thread, no port should be needed since all the patches that have been applied, including the one concerning the thread. In fact, the thread finishes without concluding whether the patch has been applied or not. You can grab it in the thread, anyway. - -[Link to thread](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html) - -The thread starts at Jan 4th 2005 until Jan 6th and is only retaken at April 14th in [this thread](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html). - --- [[Main/ThadeuCascardo]] - 29 Sep 2005 - -No DHCP client has been ported to the Hurd yet. - -[This](http://mail.gnu.org/archive/html/help-hurd/2003-10/msg00016.html) thread on help-hurd has a little more info on what's still needed for DHCP. - --- [[Main/GregBuchholz]] - 09 Oct 2003 - -Found this [message](http://mail.gnu.org/archive/html/bug-hurd/2003-08/msg00045.html) about DHCP capabilities in the Hurd encouraging. - --- [[Main/GregBuchholz]] - 03 Sep 2003 - -* Tom Hart began a [discussion ](http://mail.gnu.org/pipermail/help-hurd/2002-October/006643.html) of 14 posts in Oct 2002. - --- [[Main/GrantBow]] - 20 Oct 2002 - -The beginnings of a DHCP translator is available in the Hurd sources on Savannah: [hurd/trans/pump.c](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd/trans/pump.c?rev=1.3&content-type=text/vnd.viewcvs-markup) - -Unfortunately our current TCP/IP stack, the pfinet translator, lacks support for the AF\_PACKET interface as well as sending packets with an IP address of 0.0.0.0. - -Grant Bowman on bug-hurd: - - Herbert Xu (Pump maintainer) told me that to operate correctly, pump - uses the AF_PACKET interface which is only present in 2.2. - - Anyone else know the status of getting these compiled and functional? - -Neal Walfield on bug-hurd replies: - - > Anyone else know the status of getting these compiled and functional? - - We need to be able to send to the DHCP server with ip address 0.0.0.0. - --- [[Main/JoachimNilsson]] - 12 Nov 2002 diff --git a/Hurd/DistributedServers.mdwn b/Hurd/DistributedServers.mdwn deleted file mode 100644 index cb2dd5bc..00000000 --- a/Hurd/DistributedServers.mdwn +++ /dev/null @@ -1,29 +0,0 @@ -# Distributed Computing - -The [[Mach]] micro kernel was originally designed to run on symetric multi-processing (SMP) systems. Later, it was extended to allow for distributed OS support. A group of workstations with Mach can act as a single powerful SMP machine. Thus, Mach is also called a Single System Image (SSI). - -The Mach micro kernel provides a good infrastructure for distributed computing, including thread migration, inter-thread communition (both locally and remotely), load balancing and fault-tolerance. The Hurd, using Mach as a foundation, has great potential for distributed computing. Progress toward distributed kernel designs is proceeding within other projects as well. OpenMosix is a related projects for Linux kernels. You can reach it at: - -* -* -* - -OpenMosix patches specific Linux kernel versions to make them "distributed-enabled". However, since the Linux kernel is monolithic, patches must be updated with each new version of kernel. That can be extremely difficult due to the pace at which Linux kernels are currently developed. - -The Hurd architecture is better suited to distributed computing. Due to Hurd's server structure this is much more easily adapted. Efforts continue to evolve it's design not only on the Mach micro kernel but also work continues on a [[Mach/PortToL4]] micro kernel. - ----- - -## Document history - -Created. - --- [[Main/LaudneyRen]] - 29 Sep 2002 - -Various grammatical fixes and tidying up. - --- [[Main/JoachimNilsson]] - 29 Oct 2002 - -Updated for [[Mach]] web, reworded parts for more direct message. Added L4 link. - --- [[Main/GrantBow]] - 11 Jan 2003 diff --git a/Hurd/ExtTwoSize.mdwn b/Hurd/ExtTwoSize.mdwn deleted file mode 100644 index ec39781f..00000000 --- a/Hurd/ExtTwoSize.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -## Ext2 File system limitation - -This is a very common question. Many people have problems with the partition limit on Ext2 filesystems being very small by current standards. It feels smaller all the time as people have larger disks and often larger filesystems. It's worth mentioning that 64-bit machines (ia64, alpha) will not have this limitation. - -Note that, while the official CVS sources still suffer of this problem, recent (as of 2007) Debian GNU Hurd distributions **do not have this limit anymore**. Be happy. [July 2007 from debian-hurd](http://lists.debian.org/debian-hurd/2007/07/msg00087.html) - -* From the Hurd FAQ: [partition limit](http://www.gnu.org/software/hurd/faq.en.html#q2-6) - -**_Patch:_** - -[Release candidate 1](https://savannah.gnu.org/patch/?func=detailitem&item_id=2508) of the patch is uploaded in Savannah. - -**_Useful:_** - -Discussions on status and how to fix the problem: - -* [Febuary 2003](http://lists.debian.org/debian-hurd/2003/debian-hurd-200302/msg00016.html) -* [December 2002](http://mail.gnu.org/archive/html/bug-hurd/2002-12/msg00041.html) -* [March 2002 status](http://mail.gnu.org/archive/html/hurd-devel/2002-03/msg00030.html) and a [follow up](http://mail.gnu.org/archive/html/hurd-devel/2002-03/msg00035.html) -* [Nov 2001 status](http://mail.gnu.org/archive/html/hurd-devel/2001-11/msg00002.html) - -**_Maybe Useful:_** - -* (This link is broken. Have been unable to fix it. [[MauriceMcCarthy]] 2 Nov 2004.) -* - -(Searching Beowulf for '2Gb patch' seems to show this still present in the archive but somehow it is not accessible.) diff --git a/Hurd/ExtTwofsTranslator.mdwn b/Hurd/ExtTwofsTranslator.mdwn deleted file mode 100644 index d8f708fc..00000000 --- a/Hurd/ExtTwofsTranslator.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -* [[ExtTwoSize]] - information about the limitation of partition size -* [[XattrHurd]] - Supports Hurd ext2 format extensions on Linux, images at - --- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/Hurd/FlashHurd.mdwn b/Hurd/FlashHurd.mdwn deleted file mode 100644 index a6288afc..00000000 --- a/Hurd/FlashHurd.mdwn +++ /dev/null @@ -1,60 +0,0 @@ -# USB Flash Memory GNU/Hurd - -It would be nice if we had a bootable [USB flash drive](http://en.wikipedia.org/wiki/USB_key) Hurd like [[DamnSmallLinux]]. It would 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, a bootable Flash Hurd would enable us to have a native installer instead of relying on Linux. - -It could be installed in the USB using a [[hurd/running/Live_CD]] (using a script) - this is the Burned version - or directly downloading the iso files from the Internet - Unburned version -. One can use also [qemu] to run the [[hurd/running/Live_CD]] and them use the USB installation script. - -Here is an outline of the things that need to be done. Please add your comments and suggestions. - -## Requirements Outline - -### 1. We need to be able get a bootloader for USBs - -This is not much of a problem. I have already been successful (see below) in using [Grub](http://en.wikipedia.org/wiki/GRand%20Unified%20Bootloader) and the El-Torito HD emulation to boot [[GNUmach]] off a CD. There may be some minor tweaking of Grub code necessary to detect which device to use for booting (instead of having the user select their device (hd0,hd1,etc.) from the Grub menu). - -Using GRUB's stage2\_eltorito seems to work fine. - -### 2. We need a bootstrap filesystem translator - -This would be something like a statically linked iso9660fs translator. Compiling a statically linked iso9660fs translator is easy enough, though it doesn't boot. I don't currently know whether this is because the translator was never meant to be a bootstrap filesystem, or if there is a simple bug which has never been flushed out because the translator has never been used at boot time before. I've had trouble debugging this problem because I haven't yet figured out a way to use a remote gdb with gnumach. Theoretically you could use the "boot" command to overcome this problem, but "boot" for me mangles the terminal and exits in different manner than an actual boot. - -The iso9660fs translator works great, it just needs to be statically linked. - -### 3. We need a ramdisk to enable write access - -I think we could fake this with Farid Hajii's [memfs](http://www.fprintf.net/hurd/) translator and writing an ext2 filesystem to it. - -From the mem-fs README... - -> memfs-1 is a translator that provides a memory-based file of fixed size. This file can, just like bigfile, contain a regular filesystem. - -We could set a mem-fs translator anywhere on the CD you needed write access, including having softlinks to the contents of the root directory and chrooting to this new directory. - -For a quick and dirty memfs, you can do it right now with the following commands: - - # touch ./ramdisk - # touch ./tmpfs - # settrans -a ./ramdisk /hurd/storeio -Tcopy zero:50M - # /sbin/mke2fs -o hurd -b 4096 -F ./ramdisk - # settrans -a tmpfs /hurd/ext2fs.static ./ramdisk - # fsysopts --writable ./tmpfs - # cd tmpfs - # touch somenewfile - -Here we use two files ramdisk, and tmpfs that are already created on a readonly file system. For illustration purposes, they are touched beforehand. We run an active storeio translator on the ramdisk file to give us 50MB of RAM to work with, and then we make an ext2 filesystem on it. - -At this point we'd could copy the contents of the `/var` directory into the tmpfs, and then symlink `/var` to `/tmpfs/var`. The same goes for all other mutable dirs. - -This approach of putting an entire ext2 filesystem in a copy zero'd store has some drawbacks listed [here](http://lists.gnu.org/archive/html/bug-hurd/2000-12/msg00073.html). - -Those are the essentials. Here is a list of the things which would be nice to have for a USB Flash Memory. - -* Knoppix like script for starting up X and [[GraphicEnvironment]] s ([[FluxBox]], Gnome...) -* DHCP support for easy network setup -* Hardware autodetection (Kudzu). -* Knoppix like script for installing to the hard drive or to bootable USB pendrive . -* (add your favorite feature here) - -Here is a mailing-list [thread](http://lists.debian.org/debian-hurd/2003/debian-hurd-200308/msg00172.html) discussing some of these issues. - --- [[Main/GregBuchholz]] - 21 Oct 2003 -- [[Main/NagromNamreh]] - 29 Jan 2004 diff --git a/Hurd/FtpfsTranslator.mdwn b/Hurd/FtpfsTranslator.mdwn deleted file mode 100644 index 528a10f2..00000000 --- a/Hurd/FtpfsTranslator.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -ftpfs lets you access ftp servers via the filesystem. For detailed usage information use `/hurd/ftpfs --help` and `/hurd/ftpfs --usage`. - -### hostmux - -ftpfs ist best used with [[HostmuxTranslator]] - --- [[Main/PatrickStrasser]] - 13 Jul 2004 diff --git a/Hurd/FunnyHurd.mdwn b/Hurd/FunnyHurd.mdwn deleted file mode 100644 index 1653ec77..00000000 --- a/Hurd/FunnyHurd.mdwn +++ /dev/null @@ -1,39 +0,0 @@ -## Fun stuff ripped from the Internet - - - - - - - - - - - - - - -

%ATTACHURL%/hurd-windows.gif Hurd Windows, availble from http://www.hurd.com	%ATTACHURL%/HurdExchange.gif Exchange your Hurd at http://www.thunderinghurd.com
%ATTACHURL%/HurdCarDeal.jpg ... and we can of course also offer you a great deal on this -91 Chevy! :-)	%ATTACHURL%/HurdLodge.jpg The many perks of being a Hurd user also includes our own ski lodge! Hurd House - - Knotty pine kitchen - Spacious kitchen & living room with loft - Leather couch and love seat with a TV & VCR - Outdoor Jacuzzi - Spacious master bedroom/bath upstairs - Twin beds in one room / queen bed in another - -
%ATTACHURL%/HurdMagician.jpg From http://www.magicposters.com/buy/h-k.html	%ATTACHURL%/CrystalAwards.jpg "Wow dude, I saw the Debian Swirl logo on last nights Crystal Awards!"

- ----- - -These images and links are only here to serve as a comic relief to this site. It is **not** the intention to humiliate the people, corporations or organizations behind these factual sites. - -If your [company] name or organization is listed here and you do not approve you can remove yourself simply by clicking on the "Edit" button. In the login window that appears you enter _TWikiGuest_ as username and _guest_ as password. - ----- - -### Comments - -Created the page. - --- [[Main/JoachimNilsson]] - 09 Nov 2002 diff --git a/Hurd/FunnyHurd/CrystalAwards.jpg b/Hurd/FunnyHurd/CrystalAwards.jpg deleted file mode 100644 index 2daac850..00000000 Binary files a/Hurd/FunnyHurd/CrystalAwards.jpg and /dev/null differ diff --git a/Hurd/FunnyHurd/HurdCarDeal.jpg b/Hurd/FunnyHurd/HurdCarDeal.jpg deleted file mode 100644 index 9f533384..00000000 Binary files a/Hurd/FunnyHurd/HurdCarDeal.jpg and /dev/null differ diff --git a/Hurd/FunnyHurd/HurdExchange.gif b/Hurd/FunnyHurd/HurdExchange.gif deleted file mode 100644 index bbbb4844..00000000 Binary files a/Hurd/FunnyHurd/HurdExchange.gif and /dev/null differ diff --git a/Hurd/FunnyHurd/HurdLodge.jpg b/Hurd/FunnyHurd/HurdLodge.jpg deleted file mode 100644 index d13562f5..00000000 Binary files a/Hurd/FunnyHurd/HurdLodge.jpg and /dev/null differ diff --git a/Hurd/FunnyHurd/HurdMagician.jpg b/Hurd/FunnyHurd/HurdMagician.jpg deleted file mode 100644 index 5ef6509a..00000000 Binary files a/Hurd/FunnyHurd/HurdMagician.jpg and /dev/null differ diff --git a/Hurd/FunnyHurd/hurd-windows.gif b/Hurd/FunnyHurd/hurd-windows.gif deleted file mode 100644 index 5ca7dd74..00000000 Binary files a/Hurd/FunnyHurd/hurd-windows.gif and /dev/null differ diff --git a/Hurd/GNOME.mdwn b/Hurd/GNOME.mdwn deleted file mode 100644 index 1dbef091..00000000 --- a/Hurd/GNOME.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -![gnome-hurd.png](http://people.debian.org/~mbanck/media/gnome-hurd.png) - -GNOME can now be ported with the new [[Pthreads]], but is still being worked on.The packages are at - -deb ./ - -The caveats: - -Some applications are not yet built, not even all the ones from gnome-core. 'apt-get install gnome-applets gnome-control-center gnome-icon-theme gnome-panel gnome-session metacity nautilus scrollkeeper' (along with the above APT source) should get you started. - -See also: [[Xfree86]]. diff --git a/Hurd/GNUstep.mdwn b/Hurd/GNUstep.mdwn deleted file mode 100644 index 95b2a622..00000000 --- a/Hurd/GNUstep.mdwn +++ /dev/null @@ -1,64 +0,0 @@ -# Setting up GNUstep on the Hurd - -GNUstep is not available on the Debian distribution for GNU/Hurd, but it can be built manually. This is, how to do it. - -#### Prerequisites - -This packages should already be installed (Debian package names in brackets): ffcall (libffcall1, libffcall1-dev), libffi (libffi4), libffi4-dev, openssl (openssl), libtiff (libtiff4), libpng (libpng12-0, libpng3), libjpg (libjpeg62), libxml (libxml1, libxml2, libxml2-dev & dependencies), xslt (libxslt1.1, libxslt1-dev & dependencies), ssl (libssl0.9.8, libssl-dev), libungif4-dev libungif4g, aspell (libaspell15, libaspell-dev, aspell & apspell-[for your language, e. g. en]) windowmaker (wmaker), Objective-C-Compiler (gobjc and depending packages) - -#### Getting the sources - -To do an up-to-date-installation, download the daily snapshot from GNUstep into one new directory and unzip/untar them: - - wget ftp://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2 - -#### Building GNUstep - -Everything needed for the GNUstep base system is included into the expanded tarball. This is how to build it: - -Do the following installation as root! - - cd core/make - ./configure - make && make install - cd .. - . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh (see the dot at the begin!) - cd ../base - ./configure - Edit the file Headers/Additions/GNUstepBase/config.h and add "#define BROKEN_SO_REUSEADDR 1" somewhere - make && make install - cd ../gui - ./configure - make && make install - cd ../back - make && make install - -Now, you've built the GNUstep base system. When you want to start a GNUstep application later or want to build one, open a bash shell and enter this command: - - . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh - -This sets some necessary environment variables. - -#### Building GNUstep apps - -You can find some GNUstep applications here: - -and here: [http://mediawiki.gnustep.org/index.php/Main\_Page](http://mediawiki.gnustep.org/index.php/Main_Page) - -#### Known problems - -##### GNUMail - -After starting GNUMail, you can only once get mails from a pop3-server. If you want to fetch mails again, you have to restart it. - -##### GWorkspace 0.8 - -GWorkspace 0.8 expects a /etc/mtab file. If you want to use it, you must manually make this file. - -Example for a /etc/mtab file: - - /dev/hd0s1 / ext2 rw 1 1 - ----- - --- Thomas Schlesinger - 03 Mar 2006 diff --git a/Hurd/GrantBowHurdPage.mdwn b/Hurd/GrantBowHurdPage.mdwn deleted file mode 100644 index 89af3ada..00000000 --- a/Hurd/GrantBowHurdPage.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -Here are some notes on my current Hurd activity. - -I am also unable to get my PCI NE-2000 clone network card working. The driver loads but no routes are possible and therefore no packets get to the network. This is actually a DE-220 NIC that I started to discuss on hurd-help. Here's the actual change I made to gnumach-20020421/linux/dev/drivers/net/Space.c - - static struct device eth0_dev = { - "eth0", 0, 0, 0, 0, 0x240, 10, 0, 0, 0, ð1_dev, ethif_probe }; - -Cheers, - --- [[Main/GrantBow]] - 13 May 2002 - -Booting OSKit-Mach mysteriously works now! Yeah! I didn't even change anything! - -My problems now is how to get my second machine's (hd0,2) (/dev/hda3 for linux folks) partitionto bre recognized by Grub. When I try 'root (hd0,2)' grub spits back 'Filesystem type unknown, partition type 0x83'. This is a standard ext2 /boot partition from my test Progeny install. I even removed the partition, added it back, fsck.ext2 and moved the files back. It still doesn't see the -filesystem-. Very strange. This prevents me from using my second machine right now. - -If anyone knows more about these items, please add your comments below with your signature. - --- [[Main/GrantBow]] - 16 May 2002 - -PLEASE read these once. They are worth the effort. - -* [How To Ask Questions The Smart Way](http://www.tuxedo.org/~esr/faqs/smart-questions.html) - -* [How To Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) \* - -\*[Lincoln Portrait](http://www.people.virginia.edu/~skd9r/409/portrait.html) transcript - amazingly applicable to open source ideals. - -I am working on a page describing the [[Distrib/GNUDebianBuildProcess]]. - -I also created some very very rough images for use in explaining the Hurd and it's relationship with GNU Mach and Oskit Mach. - --- [[Main/GrantBow]] - 30 May 2002 - -* [[ATTACHURLdiagramxcf]]: Diagram - Gimp file - -* Diagram - PNG file:
![diagram.png](%ATTACHURLPATH%/diagram.png) diff --git a/Hurd/GrantBowHurdPage/diagram.png b/Hurd/GrantBowHurdPage/diagram.png deleted file mode 100644 index c8b29047..00000000 Binary files a/Hurd/GrantBowHurdPage/diagram.png and /dev/null differ diff --git a/Hurd/GrantBowHurdPage/diagram.xcf b/Hurd/GrantBowHurdPage/diagram.xcf deleted file mode 100644 index 76396410..00000000 Binary files a/Hurd/GrantBowHurdPage/diagram.xcf and /dev/null differ diff --git a/Hurd/HurdDevelopers.mdwn b/Hurd/HurdDevelopers.mdwn deleted file mode 100644 index 1a43a2b8..00000000 --- a/Hurd/HurdDevelopers.mdwn +++ /dev/null @@ -1,120 +0,0 @@ -Here's an unofficial list of Hurd developers and what they are working on. This is very unofficial. - -* [Marcus Brinkmann](http://www.marcus-brinkmann.de) - GNU Hurd Project maintainer, Debian GNU/Hurd Port Manager, fakeroot, oskit console -* [Thomas Bushnell, BSG](http://www.mit.edu/~tb/) - Primary architect, design issues and debugging help -* [Roland McGrath](http://www.frob.com), [resum�](http://www.apocalypse.org/pub/u/roland/resume.html) - GLibC, GCC-3.1, fakeroot (with fakeauth and settrans --chroot) -* Jeff Bailey - turtle autobuilder, gcc-3.1 -* [Igor Khavkine](http://alcor.concordia.ca/~i_khavki/) -* [Gordon Matzigkeit](http://www.fig.org/gord/) - -* Alexandra "[Bunny](http://www.hurd-bunny.tk)" - graphic designer, Hurd promotion -* Alfred M. Szmidt (ams) - -* Daniel (Chillywilly) Baumann - GNU Enterprise Application Server, GNU Common C++ -* [[Main/GrantBow]] - TWiki, promotion -* Jae - fatfs, possibly smbfs -* [[Main/JoachimNilsson]], [[Hurd/JoachimNilssonHurdPage]] - TWiki, OSKit upgrades (currently ATA-100 patches). -* [[Main/JamesAMorrison]] - porting, kernel interface cleanups, [hurd-extras](http://savannah.gnu.org/projects/hurdextras/) -* Neal Walfield - pthreads, documentation, debugging, #hurd admin, log & bot maintainer -* [[Main/NickRusnov]] - mtab & [[Distrib/PortingIssues]] -* Niels M�ller - kernel debugging -* [[Main/OgnyanKulev]] - [[ExtTwoSize]] patch -* Paul Emsley - [Kernel Cousin Debian Hurd](http://kt.zork.net/debian-hurd/latest.html) -* Philip Charles - [ISO CD-images](http://www.copyleft.co.nz/hurd.html) -* Ryan Golbeck - porting. -* [[Main/SamLauzon]] (Indes) - Installer, Sound(!), Bunny mocking -* [[Main/SimonLaw]] - [Kernel Cousin Debian Hurd](http://kt.zork.net/debian-hurd/latest.html) and [[Hurd/KernelCousinDebianHurd]] -* [[Main/WolfgangJ]] - documentation, promotion -* [[Main/DerekDavies]] - OSKit work -* [Daniel Wagner](http://www.vis.ethz.ch/~wagi/) (wagi) - [pcmcia support for OSKit](http://savannah.nongnu.org/projects/oskit/) - -If we got any names wrong, please accept our apologies. - - ---- - -

Acknowledgements

- -

We wish a warm ``Thank GNU'' to everybody who has helped in the -development of the Hurd. Here is a categorized list of people who -made significant contributions. If we have omitted anybody, we -apologize... please let us know so that we can update this list! - -

Hurd software

Mark Kettenis: many GNU C library and Hurd bug fixes and updates
Miles Bader: paid by the FSF to help make the Hurd usable as a standalone system, - wrote several important translators
OKUJI Yoshinori: many gnumach bug fixes and updates
Roland McGrath: paid by the FSF to design and implement the GNU C library for the Hurd, - as well as many Hurd features, current Hurd C library maintainer
Thomas Bushnell, BSG (formerly Michael I. Bushnell): paid by the FSF as primary architect of the Hurd, current Hurd maintainer
UCHIYAMA Yasushi: ported XFree86 to the Hurd

Debian GNU/Hurd

Gordon Matzigkeit: paid by the FSF as a liason from GNU to Debian
Marcus Brinkmann: bootstrapped the Debian GNU/Hurd base set and many packages, liason - from Debian to GNU
Santiago Vila: support for cross-compiling Debian packages

Documentation

Derek Upham: wrote the original GNU Hurd FAQ
Gordon Matzigkeit: reorganized and updated the GNU Hurd Reference Manual for release 0.3 -
Matthew C. Vernon: wrote the ``Idiot's Guide'' for getting started with the Hurd
Matthias Pfisterer: reorganized and updated the web site in early 1999
Stephen L. Favor: current FAQ maintainer
Trent Fisher: wrote the original version of the Hurd pages

- -Copyright (C) 1999, 2007 Free Software Foundation, Inc., -59 Temple Place - Suite 330, Boston, MA 02111, USA - -Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. - ---- - -Thank GNU to everybody who has contributed to the Hurd's development! - -

kaz Kojima - ported the Hurd to the MIPS - R3000 and R4000 processors. - -
- OKUJI Yoshinori maintains a set of Japanese - Hurd pages. - -
UCHIYAMA Yasushi has ported - XFree86 to the Hurd. - -

- -Copyright (C) 1998 Free Software Foundation, Inc., -59 Temple Place - Suite 330, Boston, MA 02111, USA - -Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. diff --git a/Hurd/HurdOnL4.mdwn b/Hurd/HurdOnL4.mdwn deleted file mode 100644 index 79e7a714..00000000 --- a/Hurd/HurdOnL4.mdwn +++ /dev/null @@ -1,173 +0,0 @@ -# GNU/Hurd on L4 wiki - -## Introduction - -This page is a place for information pertaining to the efforts towards realizing the migration and porting of the [[Hurd]] such that it uses the [L4 Microkernel](http://l4ka.org/). The GNU/Hurd Operating System, sometimes just referred to as the _GNU Operating System_ is a rich and robust collection of programs and utilities which enable you to use your computer to do usefull and or entertaining things. The intent is that most any applicable software package available on the [GNU Website](http://www.gnu.org) (and many others also) will be able to be compiled and run under the resultant operating system. - -At this point (06/20/2004) this is not yet possible. Indeed, the preliminary foundations are still being developed. Nevertheless, this is a volunteer created operating system so those with the knowledge, interest, and spare time are encouraged to study and if possible contribute to the project. - -In [CVS module hurd-l4](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/), there is a [comprehensive list of items that need to be done](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/TODO). - -## Components of the System - -### The L4 Microkernel - -The kernel of an operating system is a fundamental program which provides essential resources from the hardware of the computer to other programs. A kernel typically runs all the time and remains resident in main memory. The amount of functionality and resources which it provides vary tremendously. The [L4 Microkernel](http://l4ka.org/) is an attempt to create a very small high performace core which provides basic memory management, task and context switching, and little else. - -### The Hurd - -The [Hurd](http://www.gnu.org/software/hurd/hurd.html) is a conglomeration of servers and programs which add additional functionality to a microkernel such that it is capable of utilizing additional hardware resources of the computer. It also provides a compatibility layer such that compiling higher level programs is essentially transparent; i.e. when you write a C program and compile it, you need only include standard headers and libraries and for all intents and purposes your generic program will build and run and you need never resort to unportable coding or access to hardware specific methods. - -For a typical user, The Hurd is intended to silently work in the background providing the services and infrastructure which are lacking in the microkernel but are required for higher level programs and libraries to operate. - -### GNU Programs - -For the user, this is what is desired: to run [GNU Software](http://www.gnu.org/). These programs provide a full featured, robust, and extremely effective operating system. A L4/Hurd system should be capable of compiling and executing most any software package available from GNU with little or no modification. - -Some readers may be familiar with GNU/Linux systems. When GNU/L4 is complete it should highly resemble the functionality of such systems as L4 and Hurd effectively replace the Linux kernel. The bulk of the software should be expected to run much as it does presently under the Linux kernel (or gnumach based GNU/Hurd systems). - -## Preparations - -### Build System - -There are no precompiled binaries for Hurd on L4 that I am aware of, so you will need to be able to compile the source code packages in order to experiment with it. While L4Ka will likely build on a variety of compilers and systems, the Hurd may prove troublesome unless it is built using recent GNU compilers and tools. - -I recently used [Debian Unstable](http://www.debian.org) (Sarge) with GNU gcc version 3.3, autoconf version 2.50, and automake version 1.8 to build the system with good results, although other similarly equipped systems with a good development environment, such as [Gentoo](http://www.gentoo.org) or [Slackware](http://www.slackware.com) are reported to work fine also. - -Generally, I would recommend building the packages using any very up-to-date GNU development system. I'm not going to say that you can't compile them using more exotic platforms, but I wouldn't be overly hopefull about it. I have no idea if Pistachio can be compiled under current gnuMach/Hurd systems it might be interesting to try it. - -### Making a Home for L4/Hurd - -Obviously you want to have a home for this little embryonic operating system. Currently, mine is using about 5M for the binaries and headers. If you want the source to reside with the binaries, then allow perhaps another 50M or so, but this is purely optional. - -At the moment, Hurd on L4 can't even see your hard drive, so all you need is a directory on some partition which is visible to the GRUB bootloader. A `/l4hurd` directory on your existing GNU/Linux system is probably fine for now. - -Howevever, if you have some spare disk space or an unused partition, you could optionally create a small partition for the system. This is totally unnecessary at the moment because L4/Hurd lacks hard disk drivers right now, but it is an option. Assuming that you have made some partition **X** with linux _fdisk_, set it to type 83 - Linux and use the following command to initialize it with the classic Hurd extensions: - - - -As noted, this is purely optional, in fact right now you can use any filesystem that GRUB can understand. You can even use TFTP to netboot the system. My current setup takes about 5M for the full install so obviously you don't need much space for this. - -### Boot Loader - -Just like regular GNU/Hurd, you need to use [GNU GRUB](http://www.gnu.org/software/grub/), the _GRand Unified Bootloader_ in order to boot the system. Hopefully you already have it installed, in which case adding the commands for L4/Hurd to your `menu.lst` is quite trivial. - -If you don't have GRUB installed, then you should probably take some time to get it set up. A good place to look for help is on the regular [Debian GNU/Hurd Installation Page](http://www.debian.org/ports/hurd/hurd-install) at the **3\. The Boot Loader** section. - -This is probably a bit superfluous, but you can even display a snazzy little graphic of some type on your GRUB boot menu. Here's a snip from the header of my `menu.lst` which demonstrates how to do this. - - # menu for grub - splashimage (hd0,0)/boot/grub/debian.xpm - foreground bfbfe7 - background 3f3f7f - -In the above example, my `debian.xpm` is just a 640x480 graphic in xpm format (which you can easily create with GIMP). It does add a bit of pizazz to your boot screen :-) - -In fact, I will attach a sample copy of my `menu.lst` here. It has lots of examples for booting a variety of operating systems in it. Remember that my hard drive partitions are unique to my system. - -* [[ATTACHURLmenulst]]: Sample GRUB boot menu - -## Building Hurd on L4 - -### L4Ka Pistachio - -#### Getting the Sources - -I used the latest version of L4Ka, Pistachio version 0.4. It can be obtained from the following website: - -[L4Ka Pistachio Home](http://l4ka.org/projects/pistachio/) - -#### Compiling - -Pistachio is designed to be compiled in a build directory which is independant from the source directory, so you need to create your build directory after unpacking the tarball. Furthermore, you need to pass a couple of special parameters to the configure program to set it up for use with Hurd. Here is what I did on my ia32 system: - -Note: I have my installation set up in `/l4hurd` and I am starting from within the Pistachio source top-level directory. - - $ mkdir build - $ cd build - Building and installing user-level libraries and servers/applications - $ ../user/configure --with-s0-linkbase=0x40000 --prefix=/l4hurd - $ make - $ make install - Building and installing the kernel - $ make -C ../kernel BUILDDIR=`pwd`/kernel - $ cd kernel - $ make menuconfig - $ make - $ mkdir /l4hurd/boot - $ cp ia32-kernel /l4hurd/boot - -Hopefully everything worked and there were no problems. As usual, if the build fails then scrutinize the output from `configure` and install any missing libraries or development packages. - -### CVS l4hurd - -#### Getting the sources - - You need to pull the L4 Hurd sources from the CVS tree on Savannah. The CVS access page is [The GNU/Hurd - CVS (module hurd-l4)](http://savannah.gnu.org/cvs/?group=hurd). In a nutshell, the following commands should retrieve the sources for you: - - $ cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co hurd-l4 - -#### Compiling - -Take a look at the README, compiling should be quite simple on any state of the art GNU development system. As per the README, and for my example, you would: - - $ autoreconf -f -i -s - $ ./configure --enable-maintainer-mode --prefix=/l4hurd - $ make - $ make install - $ strip physmem/physmem - - $ mkdir /l4hurd/boot - $ cp laden/laden /l4hurd/boot - $ cp wortel/wortel /l4hurd/boot - $ cp physmem/physmem /l4hurd/boot - -Currently (2004/08/09), physmem needs to be stripped to to avoid a memory conflict with wortel; this requirement may be fixed in the future. - -In my case it was slightly more complicated as Debian uses a wrapper system to enable the use of multiple versions of the GNU Autotools. In this case, the trick is to utilize some environment variables on the command line as follows: - - $ ACLOCAL=aclocal-1.8 AUTOMAKE=automake-1.8 autoreconf -f -i -s - -As above, hopefully this will compile cleanly; otherwise, scroll up, read any error messages, and correct them by installing required packages of the proper version. Any bad compilation problems are most likely due to you either missing or using a wrong version of something. - -## Installing - -The binaries are now installed into `/l4hurd`. All that remains is to add an entry into GRUB's `menu.lst` in order to test it out. Here's an example from my system where I have `/l4hurd` on `/dev/hda9` in my Linux system: - - title GNU Hurd on L4Ka Pistachio 0.4 - root (hd0,8) - kernel /boot/laden -D - module /boot/ia32-kernel - module /libexec/l4/sigma0 - module /boot/wortel -D - module /boot/physmem -D - module /boot/physmem - module /boot/physmem - module /boot/physmem - module /boot/physmem - -It might strike you a little odd that there are five physmem modules. This is done because wortel currently (2004/08/09) expects exactly five modules and the other modules (like the task server, auth server, etc.) have not been implemented yet. Therefore the physmem module is used as a dummy module. - -## Booting - -For me at least, I got some nifty messages and then it dropped into a simple debugging mode. As far as I know, thats all there is right now. - -Read, build, learn, code... - ---todo: add more here. - -## Experimenting - -Well, thats why you did all of this, certainly not to do anything else. Use that debugger and get experimenting. - ---todo: things to do wth the debugger - -## Conclusion - -If you followed these steps, you most likely have built and booted the latest version of Hurd on L4. I would encourage you to subscribe to the mailing list at the following URL and help in the efforts to get this nifty system up to speed: - -[l4-hurd mailing list](http://lists.gnu.org/mailman/listinfo/l4-hurd) - -And finally, this is a wiki, meaning that **you** have the ability to edit and modify this page. If you want to fix something, add more information, new sub-pages, whatever, feel free to do so. This is a great way to get a doc base up fast and keep it current, so use it like its supposed to be and have fun with Hurd on L4! - --- [[Main/BDouglasHilton]] - 20 Jun 2004 diff --git a/Hurd/HurdOnL4/menu.lst b/Hurd/HurdOnL4/menu.lst deleted file mode 100644 index 3129ea74..00000000 --- a/Hurd/HurdOnL4/menu.lst +++ /dev/null @@ -1,55 +0,0 @@ -# menu for grub -splashimage (hd0,0)/boot/grub/debian.xpm -foreground bfbfe7 -background 3f3f7f - -timeout 30 -default 0 - -title Debian Sid with Linux kernel 2.6.5 -root (hd0,1) -kernel /vmlinuz root=/dev/hda2 vga=0x318 - -title Debian Sid with old kernel -root (hd0,1) -kernel /vmlinuz.old root=/dev/hda2 vga=9 - -title Microsoft Windows 2000 -rootnoverify (hd0,3) -chainloader (hd0,3)+1 - -title FreeDOS BETA 8.0 -root (hd0,0) -chainloader +1 - -title GNU Hurd on L4Ka Pistachio 0.4 -root (hd0,8) -kernel /boot/laden -D -module /boot/ia32-kernel -module /libexec/l4/sigma0 -module /boot/wortel -D -module /boot/physmem - -title Debian GNU/Hurd (gnumach) -root (hd0,7) -kernel /boot/kernel.gz root=device:hd0s8 -module /hurd/ext2fs.static --readonly \ - --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 Debian GNU/Hurd (oskit-mach) -# root (hd3,0) -# kernel /boot/kernel-ide -- root=hd0s1 -# 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 device ${root-device} $(task-create) $(task-resume) -# module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - -# title Debian GNU/Hurd (oskit-mach w/ remote debugging) -# root (hd3,0) -# kernel /boot/kernel-ide -d GDB_COM=1 BAUD=9600 -- root=hd0s1 -# 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 device ${root-device} $(task-create) $(task-resume) -# module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - diff --git a/Hurd/InstallNotes.mdwn b/Hurd/InstallNotes.mdwn deleted file mode 100644 index 2fc7958a..00000000 --- a/Hurd/InstallNotes.mdwn +++ /dev/null @@ -1,295 +0,0 @@ -Items of interest during install not mentioned elsewhere include the following. Arranged in the same order as Neal Walfield's [install guide](http://web.walfield.org/papers/hurd-installation-guide/english/hurd-install-guide.html). - -**_Currently, [Debian's installation instructions](http://www.debian.org/ports/hurd/hurd-install) are the most up-to-date._**
Note the mirrors mentioned on debian.org have no hurd iso's. The iso's can be found on several mirrors:
\* [Main mirror](http://ftp.debian-ports.org/debian-cd/)
\* [French mirror I](ftp://ftp.eila.jussieu.fr/pub/Debian-CD/)
\* [French mirror II](ftp://ftp.duckcorp.org/hurdfr/hurd/)
\* [Canada mirror](http://www.superunprivileged.org/debian-cd/)
- -## Table of Contents - -%TOC% - -## 1. Overview - Where we are going - -There are currently four methods to install GNU - -1. Tarball - Neal Walfield's [guide](http://web.walfield.org/papers/hurd-installation-guide/english/hurd-install-guide.html) is excellent and available in several formats. It is the guide that the Hurd community always references first. The GNU official [installation page](http://www.gnu.org/software/hurd/install.html) is the canonical reference. See [[Distrib/TarballNotesHome]] for more info. -2. [[Distrib/BochsEmulator]] is an x86 emulator similar to the propietary [[Distrib/VmWare]] (which is not supported). See the [[Distrib/BochsEmulator]] page for more info. The Bochs project hosts a preinstalled GNU image that is periodicaly updated. You can get the latest one [here](http://sourceforge.net/project/showfiles.php?group_id=12580). -3. [CD-ROM iso images](http://www.debian.org/ports/hurd/hurd-cd) CD-ROM installs are becoming more and more popular. The CDs are based on the most current tarball at release time. See [[Distrib/CDNotesHome]] for more info. -4. The [crosshurd](http://packages.debian.org/crosshurd/) Debian package, which can be used instead of a tarball to install the base system. This is the recommended way to proceed. - -* References to a `cross-install` script can nowadays be completely ignored by anyone not a maintainer. It is only used when creating a new tarball. - -## 2. Real Estate or Finding A Home - -For those who do not happen to have an available partition or an extra hard drive, this can be the longest step. In this case, we will need to repartition the hard drive. One solution is to use GNU's partition editor, Parted. It features not only basic partition editing, but also partition resizing and moving functions. It can be found at . The manual is quite complete and includes several tutorials. Also there's a frontend called [nparted](http://packages.debian.org/unstable/utils/nparted.html) to simplify usage. - -The Hurd can only support partition sizes of up to approximately one gigabyte; anything much larger than this will not work. This limitation is a design decision that was made several years ago in which the file system server maps the entire partition into virtual memory. As the amount of virtual memory available on an ia32 is only four gigabytes of which only two gigabytes are available to the application and, of that, a significant portion is reserved for the code, the stack and the heap, the final, maximum contiguous virtual memory area that is left is generally about one gigabyte. This limitation is scheduled to be remove. Several other items, however, currently have a slightly higher priority. - -Having said that, a single one gigabyte partition is more than enough for a working system. Many, however, prefer at least two partitions: one for a root partition and another for a home partition. This latter scheme is highly advised for developers interested in debugging Hurd servers. - -The Hurd supports several extensions to the ext2fs file system format. Foremost among these are passive translators and a fourth set of permission bits for unknown users. In order to take advantage of these features, however, the owner of the partition must be set to Hurd. `mke2fs`, unless specifically overridden on the command line, will set the owner to whatever system core it is running on. As the Hurd will diligently respect this setting, we must be careful to set this appropriately or the Hurd may fail in subtle ways. Be aware that even if a file system is owned by a particular system core, others may still use it; they just may not be able to use certain extensions. - -To create a file system, we use `mke2fs` and pass it `-o hurd` to designate the Hurd as the owner of the new file system. For instance: - - mke2fs -o hurd /dev/DEVICE - -**_Note:_** You may wish to add a `-b 4096` option to `mke2fs` (the default is chosen depending on the size of the partition, and the support for block size 1024 is buggy). The command to check the block size is `tune2fs -l /dev/hda9` under GNU/Linux. - -## 3. The Boot Loader - Getting GRUB - -GRUB is the bootloader of the GNU system, and it's currently the only one that supports the multiboot standard, necessary to boot the Hurd. - -A word about GRUB. Unlike traditional boot loaders on the x86, such as LILO, GRUB is very powerful. It has a command line interface, bootp, dummy terminal support and a plethora of other features. In addition, it can boot most any operating system. If you have ever booted an alpha or sparc, you will understand what GRUB can do. Therefore, do not be scared: GRUB is better. You will like it. You will not go back. - -To find GRUB, visit . Here, there is a source tarball and a floppy image. If you choose to download the tarball, it is a normal configure, make and make install. Included is a wonderfully complete manual on how GRUB works. Read it. If, on the other hand, you choose to download the floppy image, it is sufficient to dump it to a floppy disk to get a working GRUB: - - dd if=grub-boot-VERSION.image of=/dev/fd0 - -You can always install GRUB onto your hard drive at a later date. - -For instructions on using GRUB, see either the info documentation or the quick reference notes on this wiki: - -* [[Distrib/GrubNotes]] - quick reference - -## 4. Cross Install - Cross Installing GNU - -The recommended way to cross install the Hurd is by using the [crosshurd](http://packages.debian.org/crosshurd) Debian package. Unfortunately, it's broken right now (2003-10-10), so you'll have to use the old tarball method. - -Download the base system `gnu.tar.gz` from or . - -The tarball is setup to extract everything into the current directory. After mounting the partition and changing to the mount point, we just need to extract the archive. In the following example, we assume that the root partition is mounted on `/gnu`. - - cd /gnu - tar --same-owner -xvzpf ~/gnu.tar.gz - -**_NOTE:_** This should NOT be confused with the `cross-install` script method. It is only used by maintainers when creating a new tarball. - -## 5. Booting GNU - -Now things are setup to boot GNU for the first time. Verify that the GRUB boot disk is in the drive and reboot. If all goes well, a GRUB menu will be displayed. Hit c for the GRUB command line. - -First, the root file system needs to be set. GRUB uses a partition nomenclature that is a bit different from either GNU or GNU/Linux: both IDE and SCSI drives are named `(hdN)`. `N` is the drive number (zero based) as reported by the BIOS. That is, GRUB makes no distinction between IDE and SCSI disks. The partitions, like the disks, are also indexed numerically from zero: `(hdN,M)`. If this sounds bad, relax: GRUB is also helpful. - -To determine on which file system a particular file resides, one method is to use the find command. When issued this command, GRUB searches on each file system for the specified file and prints where is was found. Here we search for the kernel, `/boot/gnumach.gz`. - - grub> find /boot/gnumach.gz - (hd0,0) - -As we can see, GRUB is indicating that `/boot/gnumach.gz` is on `(hd0,0)`. Thus, we set the root respectively: - - grub> root (hd0,0) - Filesystem type is ext2fs, partition type 0x83 - -Next, GNU Mach needs to be loaded. In addition to loading the binary, at least one option, the root partition, must be specified. This will be used by the Hurd itself. As such, it must be in terms that the Hurd can understand. - -GNU Mach labels disks starting at zero. IDE drives are prefixed with hd, while SCSI disks are prefixed with sd. Like GNU/Linux, drives are number by their position on the controller. For instance, the primary master is `hd0` and the secondary slave is `hd3`. Partitions use the BSD slice naming convention, and append `sM` to the drive name to indicate a given partition. Note that `M` is a one, not zero, based index. The slice number is simple to calculate: just increment what you used for GRUB by one. - -Since the Hurd has not yet been configured, it must be run in single user mode. Adding a `-s` to the kernel command line is all that is required. - -Thus, continuing with the above example and assuming that the first drive in the master on the secondary controller, we would have: - - grub> kernel /boot/gnumach.gz root=device:hd2s1 -s - [Multiboot-elf, ...] - -NOTE: If after running this command you see GRUB Error 28, according to the [GRUB Troubleshooting](http://www.gnu.org/software/grub/manual/grub.html#Troubleshooting) documentation, you may need to tell grub that you have more memory by using the uppermem command. For example, if you have 256MB of RAM and running **displaymem** within GRUB shows that you have less memory than that, you can type **uppermem 262144** to tell GRUB about the additional memory. - -Next, the root file system server and the exec server must be loaded. This is done using GRUB's boot module capability. The parameters are the semantics by which the kernel passes some important values to the servers. - - grub> module /hurd/ext2fs.static \ - --multiboot-command-line=${kernel-command-line} \ - --host-priv-port=${host-port} \ - --device-master-port=${device-port} \ - --exec-server-task=${exec-task} -T typed ${root} \ - $(task-create) $(task-resume) - - [Multiboot-module 0x1c4000, 0x2cfe6a bytes] - grub> module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) - [Multiboot-module 0x494000, 0x27afe bytes] - -**_Important:_** each module string should be asingle separate line _or_ line wrapped with a backslash at the end of each line. Remember to make sure there are **_no trailing spaces!_** Adding this to GRUB's `menu.lst` file as soon as possible is advised. - -Finally, GNU can be booted: - - grub> boot - -Sit back and watch the messages. This is actually more important than one might think as there is a bug in GNU Mach whereby hitting a key during the boot process causes the kernel to panic. - -If GNU fails to boot, it could be due to shared IRQs: GNU Mach does not play well with these. You can verify your situation by looking at, for instance, the `/proc/interrupts` file under GNU/Linux. Also, as GNU Mach does not support loadable kernel modules, many of the drivers are compiled into the default kernel. If you have old peripherals, this can be a significant problem: a device may respond badly to a probe intended for a different device. Building a new kernel with only the required devices drivers will usually solve this problem. GNU Mach is easily cross compiled. If you are running Debian, try the `gcc-i386-gnu` package. - -If this does not help, explore the resources listed at the end of this document. Finally, ask on the appropriate mailing list. - -There are some cavaets to the boot process: - -* **IMPORTANT!** Remember when first booting into your freshly un-tarred distribution, you must pass the `-s` option to `/boot/gnumach.gz`. Failure to do so means that you won't get single-user mode. -* **IMPORTANT2!** Add the `--readonly` flag to the file system server in your GRUB `menu.lst` file. This is a work-around to get `fsck` working properly. Don't forget, everything must be on ONE line, or ended with a backslash! -* **IMPORTANT3!** If you have created the filesystem with a later version of e2fsprogs than the one installed in the tarball, it **might** happen that fsck fails and you can't boot multiuser. The workaround is to copy `/bin/true` into `/sbin/e2fsck` and `/sbin/fsck.ext2`, then boot multiuser and install the latest e2fsprogs. - - title GNU (kernel GNUmach 1.3) - root (hdX,Y) - kernel /boot/gnumach.gz root=device:hdXs(Y+1) - module /hurd/ext2fs.static --readonly \ - --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) - -Where `hdX,Y` is the appropriate hard disk and partition number, in GRUB format. `hdXs(Y+1)` is the GNUmach format - because Mach partitions start at 1, unlike GRUB partitions that start on 0 (zero). - -It is important that each module string is only a single separate line, or by escaping the EOL (end of line) with a back slash. Remember though to make sure there are **_no trailing spaces!_** - -**_GRUB floppy and iso images:_** These are available from . These have been built with the correct strings and only the root and boot partitions names need to be editied. - -## 6. Native Install - Finishing the Installation - -Once a prompt comes up, and any time that the the Hurd is in single user mode, it is necessary to set the terminal type: - - export TERM=mach - -(Repeat this each time you boot in single user mode) - -Be warned that CONTROL-C and family will not work in single user mode. - -We can now run the native-install script. This will configure the packages and set up several important translators: - - ./native-install - -Right before the script terminates, it will indicate that it needs to be run a second time. Follow its instructions and reboot using the reboot command. Again, go into single user mode. - -Now it is advisable to enable swap. The mach kernel dislikes running without swap and is unlikely to last through the installation, especially on systems with little physical RAM. Although you can enable swap later on after running `./native-install` for the second time, turning swap on early increases your probability of getting there. - -This will start the default pager, create a device corresponding to the swap partition, and turn swap on on that partition: - - /hurd/mach-defpager - cd /dev - ./MAKEDEV hdXsY - swapon /dev/hdXsY - cd / - -**IMPORTANT!** When enabling swap please be very sure that the partition really is swap. If you point `swapon` to a data partition it will use that for swap, overwriting any data you may have there. - -Now run `./native-install` for the second time and go through a series of prompts. - -Next, edit `/etc/fstab` to add the home partition and swap space. By default, `nano` is the only editor installed by the the base distribution (not `ae` nor `vi`). It is very important that swap space be used: the Hurd will be an order of magnitude more stable. Note that the Hurd can transparently share a swap partition with Linux, the kernel, but will happily page to any device including a raw partition such as your home partition. - -Here is an example `/etc/fstab` file: - - # - /dev/hd2s1 / ext2 rw 0 1 - /dev/hd2s2 /home ext2 rw 0 2 - /dev/hd2s3 none swap sw 0 0 - -Remember to create any devices using the `MAKEDEV` command. - -When you first boot, your `/home` directory will _not_ be auto-mounted. You must set a passive translator on that node to access that partition. The correct syntax for this is:
`settrans -p /home /hurd/ext2fs /dev/hd2s2` - -To mount an nfs partition, use the nfs translator. When run as non-root, the translator will connect, for obvious reasons, to the nfs server on a port above 1024. For this to succeed under GNU/Linux, the insecure option must be added to the export line. Here is an example `/etc/exports` file: - - /home 192.168.1.2(rw,insecure) - -To mount this from a GNU box: - - settrans -cgap /home /hurd/nfs 192.168.1.1:/home - -## 7. Configuration - Making the System Usable - -**NOTE**: _If you are using the Debian distribution of Hurd, you also **want** to read_ **_Debian [[running/debian/after_install]]_** - -* After you install, you'll want to do several _important_ things: - * Run `passwd` to give the root user a password. By default, root does not have one. - * Run `adduser` to give yourself a user account. _Do not_ use root indiscriminately. - * Run `MAKEDEV` to create devices in `/dev` for your hard disk and other required devices. - * Since the Hurd does not use `ld.so.conf`, you will want to specify where the X Window System keeps its libraries. Do this by adding the following line to your `/etc/profile`:
`export LD_LIBRARY_PATH='/lib:/usr/X11R6/lib'` - * run `/etc/cron.daily/find` to allow `locate` to function. - -* [[Network]] - * Hopefully Mach will recognize your hardware. If it doesn't you have to recompile in most cases. - * copy over your `/etc/resolv.conf` from GNU/Linux to allow your DNS to resolve correctly. - -* Prepare system for new packages.If you are running Debian GNU/Hurd: - * a recommended `/etc/apt/sources.list`:

deb  unreleased main
 deb  unstable main 
 deb-src  unstable main

- * a newer `/etc/apt/sources.list`:

deb  unstable main contrib
 deb-src  unstable main contrib
 deb  unreleased main
 deb-src  unreleased main

- * There are some extremely useful cross-platform 'apt' tricks that can be used to get packages when using Debian GNU/Linux (possibly others) for installation on GNU. This is especially useful if your GNUMach doesn't recognize your network card. The steps are covered in the file `/usr/share/doc/apt-doc/offline` which has been used by several Hurd developers successfully. - * create an `/etc/apt/apt.conf.offline` like [[AptConfOffline]]. - * consider setting up a few [[CrossPlatformAliases]] for use under Debian GNU/Linux while the Debian GNU/Hurd partitions are mounted. - * select the `apt` method from within dselect. - -* [[Xfree86]] - -* New packages - Hopefully you are able to get your network working but since the default GNUMach is only configured for a few ethernet cards you may need to recompile your GNUMach to get it working with your network hardward. - * Install these extremely useful packages - * `dialog` -- Debconf uses this for interactivity. You should install this first to allow you to configure other packages as they are installed. - * It's a very good idea to bring your packages up to date by running: `apt-get update && apt-get dist-upgrade` - * Some recommended packages - * `screen` -- A terminal multiplexer is important because the Hurd does not yet have virtual consoles. Runs with GNU/Linux too. - * `anacron` -- good to run cron jobs for a machine that is not on all the time. - * `emacs21` -- a powerful editor. - * `cvs` -- Concurrent Version System, you'll probably need this soon. - * `bzip2, zip, unzip` -- compression tools. - * `build-essential` -- preparing to build software. - * `gnu-standards` -- GNU coding and package standards. - -* Some packages use an erroneous dependency on `libc6-dev`. This is incorrect because libc6 is specific to GNU/Linux. The corresponding package for GNU is `libc0.3-dev`. If you find a package that is uninstallable due to a `libc6[-dev]` dependency, please send a bug report with a patch that fixes it. It is important that you don't hack your package system to workaround such problems, because that way you won't be able to spot them when they arrive. See the [[Distrib/PortingIssues]] for details about the problem and [[Distrib/BtsFiling]] for details on sending bug reports. -* Edit your `/etc/inetd.conf` and comment out all the services you don't need. Services that probably don't need to be running are `ftp`, `telnet`, `shell`, `login`, and `exec`. -* There appears to be a bug in `libnss-db` that causes networking to fail. To work around this edit `/etc/nsswitch.conf` and remove the `db` entries. (See ) - -## 8. Final Words - The FAQ - -* [[FAQ]] - More than frequently asked questions - -* [Hurd FAQ](http://web.walfield.org/papers/hurd-faq/) - -* [[KnownHurdLimits]] - Limitations of the GNU operating system - -## 9. Works Cited - Referenced Materials - -On Sept 20, 2002 [[Main/DeepakGoel]] (a self-proclaimed newbie) posted a link to his personal [step-by-step installation](http://24.197.159.102/~deego/pub/hurd/install-guide/install.txt). The parent directory has additional material. - -Tarball Notes: [[Distrib/TarballNotes20020816]] [[Distrib/TarballNotes20020523]] - -CD-ROM Notes: [[Distrib/CDNotesJ2]] - -Others who wish to post summaries of their installation experiences are encouraged to do so. The installer methods, package dependencies and file locations frequently do change without warning. - ----- - -## Licensing - - This work is based on the hard work by [countless Hurd users](http://web.walfield.org/papers/hurd-installation-guide/THANKS), documented and maintained by Neal H. Walfield. See the original for both reference and its licensing at - -The license for Neals work is under the [GNU GPL](http://web.walfield.org/papers/hurd-installation-guide/COPYING). However, in the Hurd Wiki license all content under the GNU FDL. (Unless the topic is mostly code or otherwise stated in the text.) - -There are currently issues to be resolved around this matter, as far as I understand at least. Until an agreement can be reached this text, and the unclear status of this topic, will remain. The suggestion is to do something like this: - -

[[InstallGuide]]: Neals Install Guide in its original form
[[InstallNotes]]: Or [[InstallGuideErrata]] with all user input and additions

- -There are several obvious issues with this as I can see - -1. The [[InstallGuide]] must be kept editable by a select few people to avoid the current situation from repeating itself. -2. This loops back and kicks us in the butt because then we get: - 1. Synchronization problems with the original work - 2. Bottle necks: The people with edit access are too busy to synchronize with Neals guide - 3. Diverging guides -3. Annoyed users, we break the tradition of freely editable wiki content and we also have two guides saying different things. - --- [[Main/JoachimNilsson]] - 29 Dec 2002 - -## Blame annotations - - -- [[Main/SimonLaw]] - 29 May 2002
-- [[Main/GrantBow]] - 13 Oct 2002
-- [[Main/JoachimNilsson]] - 14 Nov 2002
-- [[Main/RobertMillan]] - 21 Nov 2002
- -First effort at straightening out the formatting mess ... added references to Neals' original, which this topic has become heavily based on. - --- [[Main/JoachimNilsson]] - 19 Dec 2002
- -Updated to the latest short-comings in the Hurd. - --- [[Main/OgnyanKulev]] - 11 Oct 2003 - --- [[Main/TWikiGuest]] - 07 Dec 2003 () - -Updated iso information diff --git a/Hurd/InteractiveTranslators.mdwn b/Hurd/InteractiveTranslators.mdwn deleted file mode 100644 index 9a0ca7e2..00000000 --- a/Hurd/InteractiveTranslators.mdwn +++ /dev/null @@ -1,31 +0,0 @@ -The following text is from mail by Hurd architect Thomas Bushnell: - -> Thread moved over to bug-hurd since it's about design and not Debian GNU/Hurd per se. Alfred Szmidt had pointed out that a dpkg installation translator (one where you copy a .deb into a directory to install it into the system) cannot be easily written, because Debian package installation scripts are sometimes interactive. -> -> I said that this was a deficiency in the design of the Hurd, and that it would be good to fix it (ultimately) by creating user interaction context widgets which can be passed to servers so that they can safely and securely interact with the user when necessary. -> -> Alfred M. Szmidt writes: -> -> > I think you mean that it is a shortcoming in the design of things that are not or cannot be interactive, filesystems being one such example. I can see it infront of me: stat() poping up a dialog asking me to do something each time it gets called... -> -> No, it's a shortcoming in the design of the Hurd, because many times it **can** be interactive. Of course we don't want stat prompting you ever time it's called, but that's not an excuse for preventing stat from ever prompting you at all. We use all kinds of programs that can be interactive, and needless prompts are bugs, easily fixed. -> -> Please, don't lecture me about the Hurd being perfect; it's not. And this is a shortcoming that can someday be fixed, so we shouldn't pretend it's not a problem. It is. A friend at the AI lab once gave the following dream as an example of a well-functioning system: -> -> You walk up to the workstation and start a complex memory intensive ray-tracing program. It runs out of memory and swap space on the workstation. A dialog pops up informing you of the situation and giving several options: suspend the job until later, kill it, and so forth. (Notice that Unix and the Hurd both simply kill the process or the system here, because the discovery that swap is gone happens so low down that all context has been lost.) -> -> You put a disk in the drive. After putting the disk in, without you doing anything in the dialog, a new option comes up, "I notice you just put a disk in; do you want to use this for additional swap?" You say yes. The process now continues, with part of the swap being on the disk. (Notice that Unix and the Hurd don't make connections like this, having one driver know that something **else** in the system might be waiting for this resource and offering it for use.) -> -> In the middle of the task, you hit the button on the drive and out pops the disk. A notifier pops up on the screen, saying that the necessary swap for your process has been removed from the system, and so the job has been suspended until later, and giving you the option of killing it. You say "OK" (that is, you do not say to kill it), and then you log out. (Note that Unix and the Hurd cannot carry on at all in such a case; failure to satisfy a page-in fault results in utter disaster, not clean behavior. Also, neither control carefully which data is paged to which devices, because all interaction context is gone when pageout decisions are being made, so if you have started paging on this disk, you have probably started paging all kinds of essential system services on it too.) -> -> A week later, you walk up to a different workstation in the cluster, and pop in your disk. The system says, "I notice you have a suspended job that was using this disk for swap space" and allows you to resume it where you left off. (Notice that this requires close interaction between the workstations in the cluster, combined with more driver-level cleverness.) -> -> Now that's a well-functioning system. It requires careful bookkeeping of context, knowledge about how to usefully interact with the user from deep in the bowels of the system, and so forth. The Hurd has the capacity for this kind of thing, because user servers can do arbitrary things, unlike kernel routines in Unix. But we must figure out how to give them all the necessary information about their context. -> -> When I designed the filesystem protocols and the structure of the system, I did not consider this kind of flexibility. I had only the simplest kinds of filesystem translators in mind, ones which were just like Unix filesystems but supporting formats like tar and ar in addition to the typical mass-storage types. It was only a little later that I realized union and shadow translators would be a nice thing (and BSD picked up the idea after I explained it at a Boulder BSD conference). Keeping track of who is using which swap space? Now **that** would be clever, and would be very very nice to have. -> -> The reason that filesystems do not have user context is because I was not sufficiently far-sighted at the time to realize the full flexibility of the translator concept I had created. Now that we know more about that flexibility, it would be nice to start figuring out how to improve it. -> -> Thomas - --- [[Main/OgnyanKulev]] - 21 Mar 2005 diff --git a/Hurd/JoachimNilssonHurdPage.mdwn b/Hurd/JoachimNilssonHurdPage.mdwn deleted file mode 100644 index e4dde2b9..00000000 --- a/Hurd/JoachimNilssonHurdPage.mdwn +++ /dev/null @@ -1,247 +0,0 @@ - - - - - - - - - -

-	Edit this page
%ATTACHURL%/patch_kit.jpg	Table of Contents %TOC%

- -## Introduction - -This page serves as a simple project page for me. I use it to list my personal Hurd related projects, currently only OSKit related. If you wish to comment on my work, do so in [[TWiki/GoodStyle]], preferably at the bottom of this page. - -The OSKit work is based on the St. Patrick's Day release, snapshot 20020317. - -These patches are available through the [Savannah OSKit project](http://savannah.gnu.org/projects/oskit/) Hopefully they will also be integrated into the main tree at Utah. - -## Progress - -**_2005-02-05:_** Sorry, these pages are now dead. It turned out that my spare time actually was limited. I have a family with a second child due in August — so it's unlikely that I'll ever go back to working with these patches. However, I plan on joining the [[HurdOnL4]] project, possibly to help with drivers, since that's what I do at work mostly. - -**_2003-04-17:_** I've become a bit distracted lately from my Hurd related projects. My work has consumed a lot of time, as have my personal life (I'm about to become a dad! :). But don't worry, I have been working quietly in the background anyway - the OSKit patches have been integrated into the Savannah OSKit project and a new [[TWiki/GnuSkin]] release has been made. - -There is one thing now, only one little thing that I want to have finished before the summer. My Promise ATA-100 controller - support for it in [[Mach/OskitMach]]. Any spare time I find I'll spend on getting that one up and running. - -## Current Project - -I'm working on importing the Linux ATA-100 drivers to the OSKit. Using patches by Linux ATA guy, Andr� Hedrick. [ATA-100 patches](http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.20/). - -At my help I now have [[Main/OgnyanKulev]], he will test a few ATA-100 cards he has access to. - -[[Main/JoachimNilsson]]: - -* HighPoint HPT366 ATA-66 -* Promise PDC202XX ATA-100 - -[[Main/OgnyanKulev]]: - -* Promise PDC202XX -* Intel 82801BA -* Silicon Image CMD649 - -### OSKit - ATA-100 Support - -I have used the Linux 2.2.22 patch as the base and added the Linux ide-2.2.20.01102002 patch on top. Integration is now complete, testing have started. An alpha quality release is available below, if you want to help out with testing or be on the bleeding edge of things, please contact me via email. - - - - - - - - - - - - - - -

Part	Brief description	DIFF	Date
2.2.22-ATA (ALPHA)	Adds ATA-100/66 capabilities (alpha release)	patch-oskit-linux-2.2.22-ATA-alpha.diff.gz	Jan 3, 2003

- -**_Comments:_** - -* Progress is slow. - * Off-board chipsets seem more difficult ... - * PIIX chipset works, tuning included. - ----- - -## Previous Projects - -### OSKit - "New" Linux NIC drivers - -"New" means simply to add more of the drivers existing in Linux 2.2.X that don't exist in the OSKit today. - -To test any of the work in this project you first need to upgrade the OSKit to Linux 2.2.22 (or later) using my patches below. The first stage deals with network drivers, 10 and 100 Mbps. Gigabit ethernet I have no possibility to test ... so they are **not** included. - -I may, at a later date, also include updates to drivers by Donald Becker. See the drivers at - - - - - - - - - - - - - - -

Part	Brief description	DIFF	Date
2.2.22-NET	Adds more Linux NIC drivers	patch-oskit-linux-2.2.22-net.diff.gz	Dec 26, 2002

- -**_Added NICs:_** - -* 3Com 3c515 -* D-Link DE-600, DE-620 -* Davicom DM9102(A)/DM9132/DM9801 -* N2k-PCi, NE2000 PCI-based cards -* PCNet32 -* RealTek RTL8139 -* SiS 900/7016 -* ThunderLAN -* VIA Rhine - -### OSKit - Upgrade existing Linux drivers - - The OSKit itslef is currently at Linux version 2.2.12 for most of its drivers. The objective of this project was to upgrade to 2.2.22. I will of course also provide upgrades to upcoming revisions of the 2.2.x series, but they have a low priority right now. Please note: - -* The patches are cummulative, i.e., you only need one. -* The patches only upgrade existing OSKit drivers, they don't add support for new ones. Unlike the corresponding Linux patches. - -To build [[Mach/OskitMach]] you also need some other [[Mach/OskitPatches]]. As well as two unofficial GNUmach2 patches. See Daniel Wagners post to bug-hurd, , or the [[Mach/OskitMachPatches]]. - -**_Tested NICs:_** - -Testbed: Intel AL440LX mobo 128MiB RAM (only 64MiB detected by Grub 0.93). - -* Digital Equipment Corp. Etherworks Turbo PCI Controller DE435 - digital Tulip 21040-AA -* 3Com 3C905B-TXNM Fast Etherlink XL PCI - Parallel Tasking II 3Com 40-0483-004 -* RTL8139 - -**_Untested NICs:_** - -These I have and will test eventually - -* Western Digital 10 Mbps ISA - WD8003EBT -* SMC Ultra 16 ISA -* NE1000/2000 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Part	Brief description	DIFF	Date	Verified?
2.2.13	Upgrade from Linux 2.2.12 to 2.2.13	patch-oskit-linux-2.2.13.diff.gz	Oct 27, 2002	Yes (1)
2.2.14	Upgrade from Linux 2.2.12 to 2.2.14	patch-oskit-linux-2.2.14.diff.gz	Oct 30, 2002	Yes (1)
2.2.15	Upgrade from Linux 2.2.12 to 2.2.15	patch-oskit-linux-2.2.15.diff.gz	Oct 31, 2002	Yes (1)
2.2.16	Upgrade from Linux 2.2.12 to 2.2.16	patch-oskit-linux-2.2.16.diff.gz	Oct 31, 2002	Yes (1)
2.2.17	Upgrade from Linux 2.2.12 to 2.2.17	patch-oskit-linux-2.2.17.diff.gz	Nov 1, 2002	Yes (1)
2.2.18	Upgrade from Linux 2.2.12 to 2.2.18	patch-oskit-linux-2.2.18.diff.gz	Nov 1, 2002	Yes (1)
2.2.19	Upgrade from Linux 2.2.12 to 2.2.19	patch-oskit-linux-2.2.19.diff.gz	Nov 4, 2002	Yes (1)
2.2.20	Upgrade from Linux 2.2.12 to 2.2.20	patch-oskit-linux-2.2.20.diff.gz	Nov 5, 2002	Yes (1)
2.2.21	Upgrade from Linux 2.2.12 to 2.2.21	patch-oskit-linux-2.2.21.diff.gz	Nov 5, 2002	Yes (1)
2.2.22	Upgrade from Linux 2.2.12 to 2.2.22	patch-oskit-linux-2.2.22.diff.gz	Nov 5, 2002	Yes (1)
2.2.23	Upgrade from Linux 2.2.12 to 2.2.23	[[][patch-oskit-linux-2.2.23.diff.gz]]	Not yet

- -**_Notes:_** - -1. Yes, the patch has been tested using the latest CVS version (HEAD) of GNUmach. Verified means that I have verified that GNUmach can be built, booted successfully (using IDE and various NICs). - -## Future Work - -1. Try to enable GNUmach to use the [[TWiki/FreeBSD]] drivers in the OSKit. -2. Port a simple DHCP client (udhcp perhaps?). -3. Enable the sound drivers in the OSKit -- port a useful sound daemon. -4. SMP support for GNUmach2 - Current OSKit is broken. - -### [[TWiki/FreeBSD]] NIC drivers for GNUmach - - I have looked into this a bit. The PCI drivers are initialized from the PCI probe. GNUmach v2 uses the Linux PCI stuff which means the [[TWiki/FreeBSD]] probe will not run - this is probably solved in some ingenious way in the OSKit, maybe the COM interfaces, but I've yet to find out more about that. - ----- - - Feel free to contact me if you have any comments or suggestions. - --- [[Main/JoachimNilsson]] - Feb 19th 2003 - -## Comments - -Go Joachim! Great work! - --- [[Main/GrantBow]] - 11 Nov 2002 diff --git a/Hurd/JoachimNilssonHurdPage/patch_kit.jpg b/Hurd/JoachimNilssonHurdPage/patch_kit.jpg deleted file mode 100644 index da5cc147..00000000 Binary files a/Hurd/JoachimNilssonHurdPage/patch_kit.jpg and /dev/null differ diff --git a/Hurd/KernelCousinDebianHurd.mdwn b/Hurd/KernelCousinDebianHurd.mdwn deleted file mode 100644 index 1ff8a698..00000000 --- a/Hurd/KernelCousinDebianHurd.mdwn +++ /dev/null @@ -1,3 +0,0 @@ -[Kernel Traffic](http://www.kerneltraffic.org/) publishes newsletters that track the technical developments of various projects of the Free and Open Source world. [Newsletters for the Hurd development](http://www.kerneltraffic.org/debian-hurd/archives.html) were published, but not anymore. - -Updated status. -- [[Main/OgnyanKulev]] - 18 Sep 2004 diff --git a/Hurd/KnownHurdLimits.mdwn b/Hurd/KnownHurdLimits.mdwn deleted file mode 100644 index 51d66b50..00000000 --- a/Hurd/KnownHurdLimits.mdwn +++ /dev/null @@ -1,20 +0,0 @@ -* ~1.5 GB ext2 file system size limit - * The problem is fixed in the Debian GNU/Hurd distribution but not the official sources, see [this email](http://lists.debian.org/debian-hurd/2007/07/msg00087.html) - * See [[ExtTwoSize]] - -* Many Unsupported Devices. - * See [[Mach/HardwareCompatabilityList]] - -* Entropy. Mach does not yet gather entropy and thus there are no /dev/random and /dev/urandom nodes. - There are needed by OpenSSH. - * In progress, see [[translator/random]] - -* No DHCP client - * promising information [Jan 2005](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html), needs an update - * See [[DhcpClient]] - need to update TCP/IP server. - -* Missing bits of POSIX - * See [[Distrib/SystemAPILimits]] - -* Stability issues - * [[ZallocPanics]] diff --git a/Hurd/LuisBustamanteHurdPage.mdwn b/Hurd/LuisBustamanteHurdPage.mdwn deleted file mode 100644 index abbf1531..00000000 --- a/Hurd/LuisBustamanteHurdPage.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -Nothing much to see right now, I'll add some stuff I'm working in the near future! :) - -Cheers, - --- [[Main/LuisBustamante]] - 16 May 2002 - -After making some trivial/incorrect patches (thanks Neal :) for building um-pppd with gcc 3.0.4 in Debian (see [\#147085](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147085&repeatmerged=yes)) this weekend I'll finally give it a try, I got an external modem... anyway serial drivers seem to be broken in GNUmach iirc, I won't get much more than 300b/s :). - -Keep Hurding! - --- [[Main/LuisBustamante]] - 17 May 2002 diff --git a/Hurd/MakeImage.mdwn b/Hurd/MakeImage.mdwn deleted file mode 100644 index 95b928c4..00000000 --- a/Hurd/MakeImage.mdwn +++ /dev/null @@ -1,60 +0,0 @@ -## Make a disk image - -This is just a reminder to myself currently. - - /bin/dd if=/dev/zero of=gnu.img count=224000 - /sbin/sfdisk -C 58 -H 16 -S 63 -D gnu.img< Install GNU/Hurd - - mkdir image - mount /dev/loop0 image - cd image/ - /usr/share/crosshurd/makehurddir.sh `pwd` i386 gnu - cd .. - umount image - losetup -d /dev/loop0 - -## Make Boot ISO - -I use this for testing OSKit... - - mkdir -p iso/boot/grub - cp /lib/grub/i386-pc/stage2_eltorito iso/boot/grub/ - cp oskit-mach.gz iso/boot/ - cat >iso/boot/grub/menu.lst << EOF - title GNUmach 2.0 (OSKit-Mach) - root (cd) - kernel /boot/oskit-mach.gz root=device:hd0s1 -- - root (hd0,0) - 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-2.3.2.so /hurd/exec $(exec-task=task-create) - - title GNU/Hurd (GNUmach 1.3) - root (hd0,0) - kernel /boot/gnumach.gz root=device:hd0s1 - 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) - - EOF - mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 \ - -boot-info-table -o grub.iso iso - -## Booting Qemu - - qemu -user-net -isa -boot d -cdrom grub.iso -hda gnu.img - -The switch `-isa` is for current gnumach.gz on hda. - --- [[Main/JoachimNilsson]] - 11 Apr 2005 diff --git a/Hurd/PosixThreads.mdwn b/Hurd/PosixThreads.mdwn deleted file mode 100644 index f031b56f..00000000 --- a/Hurd/PosixThreads.mdwn +++ /dev/null @@ -1,21 +0,0 @@ -## POSIX Threads for the Hurd - -One of the features the Hurd has been lacking up til now is support for POSIX threads, pthreads. It has been the show stopper for porting many useful applications and has sometimes been pointed out as one of the bigger problems with the GNU operating system. - -In 2002 however, all this came to an end when Neal Walfield implemented libpthreads for his work on L4 and decided to also make it work on GNUmach. - -Information on the library can be found on Neals web site. - -* - -## Previous Attempts - -Plans to implement pthreads for the Hurd has existed since, at least, 1999. Mark Kettenis [1] began work that was supposed to be useful on Linux as well. His work was continued by Igor Khavikine [2], who implemented most of it. Igor could however not continue his work so it was picked up by Jeroen Dekkers [3] and Ryan Golbeck. Their work can be found on Savannah, . - -1. -2. -3. - ----- - -Initial version -- [[Main/JoachimNilsson]] - 03 Nov 2002 diff --git a/Hurd/PppDaemon.mdwn b/Hurd/PppDaemon.mdwn deleted file mode 100644 index f667d449..00000000 --- a/Hurd/PppDaemon.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -There is no PPP solution present for the Hurd. - -* Filed Debian [um-ppp bug](http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no\&bug=147085) -* Clemmitt [asked about um-pppd](http://mail.gnu.org/pipermail/help-hurd/2002-October/006664.html) in this thread of 9 posts beginning Oct 10, 2002. - --- [[Main/GrantBow]] - 20 Oct 2002 diff --git a/Hurd/RequirementsForLiveCD.mdwn b/Hurd/RequirementsForLiveCD.mdwn deleted file mode 100644 index 03bd3884..00000000 --- a/Hurd/RequirementsForLiveCD.mdwn +++ /dev/null @@ -1,54 +0,0 @@ -# Requirements for a GNU/Hurd Live CD - -Here is an outline of the things that need to be done for producing a Live CD for the Hurd. Please add your comments and suggestions. - -## 1. We need to be able get a bootloader for CDs - -This is not much of a problem. I have already been successful (see below) in using [Grub](http://en.wikipedia.org/wiki/GRand Unified Bootloader) and the El-Torito HD emulation to boot [[GNUmach]] off a CD. There may be some minor tweaking of Grub code necessary to detect which device to use for booting (instead of having the user select their device (hd0,hd1,etc.) from the Grub menu). - -Using GRUB's stage2\_eltorito seems to work fine. - -## 2. We need a bootstrap filesystem translator - -This would be something like a statically linked iso9660fs translator. Compiling a statically linked iso9660fs translator is easy enough, though it doesn't boot. I don't currently know whether this is because the translator was never meant to be a bootstrap filesystem, or if there is a simple bug which has never been flushed out because the translator has never been used at boot time before. I've had trouble debugging this problem because I haven't yet figured out a way to use a remote gdb with gnumach. Theoretically you could use the "boot" command to overcome this problem, but "boot" for me mangles the terminal and exits in different manner than an actual boot. - -The iso9660fs translator works great, it just needs to be statically linked. - -## 3. We need a ramdisk to enable write access - -I think we could fake this with Farid Hajii's [memfs](http://www.fprintf.net/hurd/) translator and writing an ext2 filesystem to it. - -From the mem-fs README... - -> memfs-1 is a translator that provides a memory-based file of fixed size. This file can, just like bigfile, contain a regular filesystem. - -We could set a mem-fs translator anywhere on the CD you needed write access, including having softlinks to the contents of the root directory and chrooting to this new directory. - -For a quick and dirty memfs, you can do it right now with the following commands: - - # touch ./ramdisk - # touch ./tmpfs - # settrans -a ./ramdisk /hurd/storeio -Tcopy zero:50M - # /sbin/mke2fs -o hurd -b 4096 -F ./ramdisk - # settrans -a tmpfs /hurd/ext2fs.static ./ramdisk - # fsysopts --writable ./tmpfs - # cd tmpfs - # touch somenewfile - -Here we use two files ramdisk, and tmpfs that are already created on a readonly file system. For illustration purposes, they are touched beforehand. We run an active storeio translator on the ramdisk file to give us 50MB of RAM to work with, and then we make an ext2 filesystem on it. - -At this point we'd could copy the contents of the `/var` directory into the tmpfs, and then symlink `/var` to `/tmpfs/var`. The same goes for all other mutable dirs. - -This approach of putting an entire ext2 filesystem in a copy zero'd store has some drawbacks listed [here](http://lists.gnu.org/archive/html/bug-hurd/2000-12/msg00073.html). - -Those are the essentials. Here is a list of the things which would be nice to have for a Live-CD. - -* Knoppix like script for starting up X and [[GraphicEnvironment]] s ([[FluxBox]], Gnome...) -* DHCP support for easy network setup -* Hardware autodetection (Kudzu). -* Knoppix like script for installing to the hard drive or to bootable USB pendrive . -* (add your favorite feature here) - -Here is a mailing-list [thread](http://lists.debian.org/debian-hurd/2003/debian-hurd-200308/msg00172.html) discussing some of these issues. - --- [[Main/GregBuchholz]] - 21 Oct 2003 -- [[Main/NagromNamreh]] - 29 Jan 2004 diff --git a/Hurd/SeenHurd.mdwn b/Hurd/SeenHurd.mdwn deleted file mode 100644 index be9e1aba..00000000 --- a/Hurd/SeenHurd.mdwn +++ /dev/null @@ -1,71 +0,0 @@ -# Hurd Sightings - -#### Table Of Contents - -%TOC% - -## Hurd People Sightings - -

[[Mailing_lists]]: Available mailing lists
[[IRC]]: -
[[WhoRunsGNU]]: -
[[HurdDevelopers]]: Who's who?
[[PersonalHurdPages]]: Users with Hurd wiki pages
[[UserGroups]]: Canadian, French & Russian
[[community/Meetings]]: Meetings with Hurd developer attendance.
[[community/Orkut]]: online "community" of interest - 89 members and counting
[[community/LiveJournal]]: online community

- -## Hurd Press Sightings - -Here's a page for links that specifically talk about the Hurd in some way. See also, [[FunnyHurd]]. - -### Searching the Word "Hurd" in Some Famous Sites - -* [OSNews.com](http://www.osnews.com/search.php?search=hurd) -* [Slashdot.org](http://slashdot.org/search.pl?query=hurd) -* [KernelTrap.org](http://kerneltrap.com/index.php?or=6,16,40) -* [DebianPlanet.org](http://www.debianplanet.org/module.php?mod=search&edit%5Btype%5D%5Bnode%5D=1&keys=hurd) -* [Hungarian Unix portal](http://www.hup.hu/modules.php?name=News&new_topic=65) (in Hungarian) - -### Single Articles - -* [Interview with Hurd developer Marcus Brinkmann](http://portal.wikinerds.org/brinkmann-interview-mar2005) by Wikinerds Portal -* [A historic first step for the GNU/HURD-L4 microkernel port](http://portal.wikinerds.org/gnu-hurd-l4-first-program) by Wikinerds Portal -* [Interviews: Linus Torvalds: "Desktop Market has already started"](http://linuxtimes.net/modules.php?name=News&file=article&sid=145), in Linux Times, the viability of the Hurd is discussed a bit. -* [The Answer Gang 88: Linux Kernel Maintainability: Bees Can't Fly](http://www.linuxgazette.com/issue88/tag/3.html), in Linux Gazette, March 2003, issue 88. -* [Renaming Linux](http://www.infomaticsonline.co.uk/News/1135403) article on GNU OS (Hurd is a strongly related issue) - Sept 26, 2002 -* GNU's new [GNU/Linux FAQ](http://www.gnu.org/gnu/gnu-linux-faq.html) - Sept 24, 2002 -* [Debian Weekly News](http://www.debian.org/News/weekly/2002/37/) on Sarge & Hurd - Sept 24, 2002 -* Debian Release Manager Anthony Towns [notes on Sarge](http://lists.debian.org/debian-devel-announce-0209/msg00004.html) & Hurd - Sept 28, 2002 -* [New Console](http://www.kerneltrap.org/node.php?id=420) - Kernel Trap, Sept 18, 2002 -* [Radio CSJ](http://pagina.de/radiocsj) 104.5 FM discussions during "error 404" show - [Universidad Cat�olica de Chile](http://www.puc.cl) (Macul, Santiago, Chile), June 2002 -* [New GNU Hurd Kernel Released](http://slashdot.org/article.pl?sid=02/05/30/1547250&mode=nested&tid=117) [_sic_] - Slashdot, May 30, 2002 -* [GNU Mach 1.3 released!](http://www.debianplanet.org/article.php?sid=680&mode=thread&order=0&thold=0) - Debian Planet, May 29, 2002 -* [Running Hurd Under [[Distrib/BochsEmulator]] x86 Emulator](http://www.debianplanet.org/article.php?sid=673&mode=thread&order=0&thold=0) - Debian Planet, May 12, 2002 -* [Hurd-i386 gets new GLibc core](http://www.debianplanet.org/article.php?sid=668&mode=thread&order=0) by Jeff Bailey - Debian Planet, May 3, 2002 -* [IDG](http://www.idg.net/ic_829012_4394_1-3921.html) - IDG, March 11, 2002 -* [Interview with Neal Walfield](http://kerneltrap.org/article.php?sid=375) - Kernel Trap, Nov 12, 2001 - -### On Cover Pages - -* [freeX #4 2000](http://www.cul.de/data/freex42000inh.pdf) (PDF) - _Die andere Systemphilosophie_ auf Marcus Brinkmann - -%ATTACHURL%/freex42000cg.jpg - -* Linux Magazine France 10 - -%ATTACHURL%/lmf10\_1999.jpg diff --git a/Hurd/SeenHurd/lmf10_1999.jpg b/Hurd/SeenHurd/lmf10_1999.jpg deleted file mode 100644 index 85332658..00000000 Binary files a/Hurd/SeenHurd/lmf10_1999.jpg and /dev/null differ diff --git a/Hurd/SerialConsole.mdwn b/Hurd/SerialConsole.mdwn deleted file mode 100644 index e4e5324d..00000000 --- a/Hurd/SerialConsole.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -# Grub - -To enable serial console support in Grub, you'll need to add a variation of the following to the top of your menu.lst: - - serial --unit=0 - terminal --timeout=2 serial console - -The first line enables the serial console on the first serial port (use --unit=1 to use the second). The second tells Grub to use either the serial console or the vga display on the first one on which input is sensed within two seconds of executing this command. If no input is detected, Grub defaults to the first which in this case is the serial console. - -# Hurd - -You'll first need to create a serial port device. Change to /dev and execute the following as root: - - ./MAKEDEV com0 - -Then add the following to /etc/ttys: - - com0 "/libexec/getty 9600" xterm-color on secure trusted console - -runttys won't automatically reread /etc/ttys. You need to send it a SIGHUP. - -If you are running your serial console on the second serial port, replace com0 with com1. - -# Using the Serial Port - -minicom is popular but sredird has a more integrated feel. - --- [[NealWalfield]] - 12 Dec 2005 diff --git a/Hurd/Shopping.mdwn b/Hurd/Shopping.mdwn deleted file mode 100644 index d9806e93..00000000 --- a/Hurd/Shopping.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -Here are some e-shops from which you can buy stuff: T-Shirts and others. Free Software Foundation Inc. doesn't get percent from these sells. - -* [CafePress](http://www.cafeshops.com/hurd) - --- [[Main/OgnyanKulev]] - 11 Feb 2004 - -Wait, so they are making money off the Hurd and not giving any to the FSF? Uh.... - --- [[Main/GrantBow]] - 27 Feb 2004 - -OK, It was kind a stupid to add this sentence. What about removing it all this sentence? - --- [[Main/OgnyanKulev]] - 27 Feb 2004 diff --git a/Hurd/Translation.mdwn b/Hurd/Translation.mdwn deleted file mode 100644 index a5f78aa5..00000000 --- a/Hurd/Translation.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -\* [[HurdCn]]: - -\* [[HurdNl]]: - -\* [[HurdPl]] : - -\* [[HurdEo]]: - -\* [[HurdHe]] : - -\* [[HurdEs]]: - -\* [[HurdFr]]: - -\* [[HurdIt]]: - -\* [[HurdRu]]: - diff --git a/Hurd/TranslatorExamples.mdwn b/Hurd/TranslatorExamples.mdwn deleted file mode 100644 index 0c2e5741..00000000 --- a/Hurd/TranslatorExamples.mdwn +++ /dev/null @@ -1,61 +0,0 @@ -## Introduction - -Translators are probably the most known feature of the Hurd, the first thing you should show when doing a demo. - -## run - -Couldn't manage to compile it, but allows you to do nice things with eg. fortune. - -## ftpfs - -hurd:~# settrans -c ftp /hurd/ftpfs 128.101.80.131:/ - -hurd:~# cd ftp - -hurd:~/ftp# ls - -debian debian-archive lost+found - -hurd:~/ftp# cd debian - -hurd:~/ftp/debian# ls - -README README.mirrors.txt doc ls-lR.patch.gz - -README.CD-manufacture README.non-US indices pool - -README.html README.pgp ls-lR project - -README.mirrors.html dists ls-lR.gz tools - -hurd:~/ftp/debian# cp README ~ - -hurd:~/ftp/debian# - -You have to specify the server address with its IP, or your computer will buy a farm or something. - -## ftpfs and hostmux - -currently (28/02/2004) not working, but should be. - -hurd:~# settrans -c ftp /hurd/hostmux /hurd/ftpfs / - -hurd:~# cd ftp - -hurd:~/ftp# cd ftp.debian.org - --bash: cd: ftp.debian.org: Computer bought the farm - -hurd:~/ftp# host ftp.debian.org - -ftp.debian.org A 128.101.80.131 - -ftp.debian.org A 208.185.25.38 - -hurd:~/ftp# cd 128.101.80.131 - --bash: cd: 128.101.80.131: Computer bought the farm - -## Articles about translators - -* [The GNU Hurd - Translators by Gael le Mignot](http://kilobug.free.fr/hurd/pres-en/html/node8.html) diff --git a/Hurd/TranslatorPages.mdwn b/Hurd/TranslatorPages.mdwn deleted file mode 100644 index 8e954521..00000000 --- a/Hurd/TranslatorPages.mdwn +++ /dev/null @@ -1,51 +0,0 @@ -

[[NeighborHurd]]: A concept possible with microkernels.
[[InteractiveTranslators]]: Translators that interact with user
[[TranslatorExamples]]: Examples of what you can do with translators
[[TranslatorWishList]]: Interesting file translator ideas

Budi Rahardjo: http://hurd.indocisc.com, contact at budi@research.indociscNOSPAM.com
[[Main/JamesAMorrison]]: http://hurd.dyndns.org - -seems to be offline -- [[Community/weblogs/ArneBab]] - 2008-09-02

- -### Testing and developer installations - -Installations for testing purposes are listed as [[public_hurd_boxen]]. - -These also contain the wiki server. diff --git a/Hurd/XattrHurd.mdwn b/Hurd/XattrHurd.mdwn deleted file mode 100644 index d3856c1b..00000000 --- a/Hurd/XattrHurd.mdwn +++ /dev/null @@ -1,5 +0,0 @@ -Roland McGrath has made [Linux support for Hurd's extensions to ext2 via Extended Attributes (xattr) interface](http://lists.gnu.org/archive/html/bug-hurd/2004-02/msg00108.html). This is important because it allows Hurd to be completely cross-installed in Linux. - -Michael Banck made some Debian precompiled Linux kernel packages that allow [using this xattr-hurd](http://lists.debian.org/debian-hurd/2004/09/msg00036.html). - --- [[Main/OgnyanKulev]] - 18 Sep 2004 diff --git a/Hurd/Xfree86.mdwn b/Hurd/Xfree86.mdwn deleted file mode 100644 index 617508e5..00000000 --- a/Hurd/Xfree86.mdwn +++ /dev/null @@ -1,109 +0,0 @@ -# Setup XFree86 in GNU - -#### Table Of Content - -%TOC% - -This is a brief helper on how to setup X-Window on GNU. - -### Mouse & Keyboard - -See [[console]] for more details. - -First, set up the keyboard translator. Using `/hurd/kbd` and `/hurd/mouse` is not supported. You should instruct Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: - - # console -d vga -d pc_kbd --repeat=kbd -d generic_speaker \ - -d pc_mouse --repeat=mouse --protocol=ps/2 --console-node=/dev/cons /dev/vcs - -Symbolic links to repeaters should be created too: - - # ln -s /dev/cons/kbd /dev - # ln -s /dev/cons/mouse /dev - -### Selecting & Configuring Packages - -You will need several X packages. The `x-window-system-core` brings you most of what you need: - -* `xserver-xfree86` -* `xfonts-base` -* `xfonts-100dpi` -* `xfonts-75dpi` -* `xfonts-scalable` -* `xbase-clients` -* `xutils` -* `rxvt` -* ... as well as your window manager of choice: - * WindowMaker, `wmaker` - * FVWM, `fvwm` - * Blackbox, `blackbox` - * TWM, `twm` - -The recommended way of configuring X is using the `xserver-xfree86` debconf template, eg: - - # dpkg-reconfigure xserver-xfree86 - -It may be easier to just copy a working configuration from another operation system on the same computer and place it in `/etc/X11/XF86Config-4`, but this is discouraged as you would have to remove some sections by hand. - -**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. - -### Edit XF86Config-4 - -Now you have to edit the file manually to ensure that the mouse sections look like this: - - Section "InputDevice" - Identifier "Configured Mouse" - Driver "mouse" - Option "CorePointer" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - - Section "InputDevice" - Identifier "Generic Mouse" - Driver "mouse" - Option "SendCoreEvents" "true" - Option "Device" "/dev/mouse" - Option "Protocol" "osmouse" - EndSection - -You may also enable the Emulate3Buttons option, but nothing else will work. - - Option "Emulate3Buttons" "true" - -### Dynamic Linking - -The Hurd does not use `ld.so.conf`, it is necessary to add the following to `/etc/profile` to be sure that the libraries are found: - - LD_LIBRARY_PATH=/X11R6/lib:$LD_LIBRARY_PATH - -"This is a linker issue. GNU/Hurd expects that \`RPATH' is used, however, Debian takes certain measures to avoid this. Note that this does not cut it for suid binaries because of security implications. We expect to rectify this by using \`RUNPATH', which is specified in the new ELF standard." -- [Why does X not work?](http://www.gnu.org/software/hurd/faq.en.html#q4-8) - -### Starting X - -Finally, run - -`startx` - -However, there are several caveats to be aware of: - -* `xterm` does not work correctly; try `rxvt`. -* `update-menu` does not yet work. As such, there are no fine Debian menus. -* GNOME can now be ported with the new pthreads, but is still being worked on. [[WindowMaker]], [[TWM]], [[Blackbox]] and [[FVWM]] all work. - -### Graphical Environment - -See [[GNOME]] in Hurd . (?) - ----- - -Created. -- [[Main/RobertMillan]] - 21 Nov 2002 - -Some text formatting. -- [[Main/OgnyanKulev]] - 05 Dec 2002 - -Dito. -- [[Main/JoachimNilsson]] - 12 Jan 2003 - -`/hurd/kbd` is no longer supported. -- [[Main/OgnyanKulev]] - 11 Aug 2004 - -`/hurd/mouse` is deprecated. -- [[Main/OgnyanKulev]] - 21 Sep 2004 - --c /dev/cons is now --console-note=/dev/cons -- Sven 01 May 2005 diff --git a/Hurd/ZallocPanics.mdwn b/Hurd/ZallocPanics.mdwn deleted file mode 100644 index 0b00d7ec..00000000 --- a/Hurd/ZallocPanics.mdwn +++ /dev/null @@ -1,43 +0,0 @@ -The Hurd sometimes crashes with a kernel panic saying someting like: "Panic: zalloc failed: zone map exhausted". - -These panics are generally caused by some kind of kernel resource exhaustion, but there are several differnt reasons for that. - -It used to happen very often under heavy disk load (like large compile jobs), or in a reproducible test case by opening a large number of ports to /dev/null and then closing them all very quickly. The reason for this particular problem has been identified a while back: The multithreaded Hurd servers create a new worker thread whenever a new request (RPC) comes in while all existing threads are busy. When the server is hammered with lots of requests -- which happens both under heavy disk load, and when quickly closing many ports to one server -- it will create an absurd number of threads, causing the resource exhaustion. - -The Debian hurd package contains a patch by k0ro (Sergio Lopez), which fixes this by limiting the amount of created threads in a rather simplistic but very effective manner. This patch however hasn't been included in upstream CVS so far. A more elegant solution, suitable for upstream inclusion, would be desirable. - -Some panics still seem to happen in very specific situations, like the one described at . These are probably the result of bugs that cause port leaks, accidental fork bombs, or similar problems. - -In principle, resource exhaustion can also happen by normal use, though this is rather unlikely in the absence of bugs or malicious programs. Nevertheless, all these problems could be avoided (or limited in effect) by introducing some limits on number of processes per user, number of threads and ports per process/user etc. - -Trying to track down causes for the panics, I got some interesting results. (UPDATE: Many of my original observations were clearly related to the server thread explosion problem. To avoid confusion, I now removed these, as this is no longer an open issue.) - -* It all started with someone (probably azeem) mentioning that builing some package always crashes Hurd at the same stage of the Debian packaging process (UPDATE: Almost all of these panics when building packages were a result of the thread explosion and don't happen anymore.) -* Someone (maybe he himself) pointed out that this stage is characterized by many processes being quickly created and destroyed -* Someone else (probably hde) started some experimenting, to get a reproducible test case -* He realized that just starting and killing five child processes in quick succession suffices to kill some Hurd systems -* I tried to confirm this, but it turned out my system is more robust - -As I could never reproduce the problem with a small number of quickly killed processes, I can't say whether this problem still exists. While I could reproduce such an effect with first opening and then very quickly closing many ports (which is more or less what happens when quickly killing many processes), I needed really large numbers of processes/ports for that. The thread throtteling patch fixed my test case; but it seems unlikely that killing only five processes could have caused a thread explosion, so maybe hde's observation was a different problem really... - -I started various other experiments with creating child processes (fork bombs), resulting in a number of interesting observations: - -* Just forking a large number of processes crashes the Hurd reliably (not surprising) -* The number of processes at which the panic occurs is very constant (typicallly +-2) under stable conditions, as long as forking doesn't happen too fast -* The exact number depends on various conditions: - * Run directly from the Mach console, it's around 1040 on my machine (given enough RAM); however, it drops to 940 when started through a raw ssh session, and to 990 when run under screen through ssh (TODO: check number of ports open per process depending on how it is started) UPDATE: In a later test, I got somewhat larger numbers (don't remember exactly, but well above 1000), but still very constant between successive runs. Not sure what effected this change. - * It doesn't depend on whether normal user or root - * With only 128 MiB of RAM, the numbers drop slightly (like 100 less or so); no further change between 256 and 384 MiB - * Lowering zone\_map\_size in mach/kern/zalloc.c reduces the numbers (quite exactly half from 8 MiB to 4 MiB) - * There seems to be some saturation near 16 MiB however: The difference between 8 MiB and 16 MiB is significantly smaller - * Also, with 8 MiB or 4 MiB, the difference between console/ssh/screen becomes much more apparent (500 vs. 800, 250 vs. 400) - * With more than 16 MiB, Mach doesn't even boot -* Creating the processes very fast results in a sooner and less predictable crash (TODO: Check whether this is still the case with thread throtteling?) -* Creating processes recursively (fork only one child which forks the next one etc.) results in faster crash -* rpcinfo shows that child processes have more ports open by default, which is very likely the reason for the above observation -* Opening many ports from a few processes doesn't usually cause a system crash; there are only lots of open() failures and translator faults once some limit is reached... Seems the zalloc-full condition is better caught on open() than on fork() (TODO: investigate this further, with different memory sizes, different zone\_map\_size, different kinds of resources using zalloc etc.) -* After opening/leaking lots of ports to /dev/null (32768 it seems), the NULL translator somehow becomes disfunctional, and a new instance is started - -While most of these Observations clearly show an exhaustion of kernel memory which is not surprising, some of the oddities seem to indicate problems that might deserve further investigation. - --- antrik (Last update: 12 Apr 2007) diff --git a/Mach/AdvancedGrubUsage.mdwn b/Mach/AdvancedGrubUsage.mdwn deleted file mode 100644 index 8e307b4f..00000000 --- a/Mach/AdvancedGrubUsage.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -## Advanced Grub - -[Grub](http://www.gnu.org/software/grub/) is a capable boot loader. This document is intended to capture some of its most interesting features and try to explain them a bit better than the texinfo documentation. - -### Debian Grub - -The Debian grub packages do not have networking enabled, so you have to apt-get the source, modify the debian/rules file to include --enable-network-card and dpkg-buildpackage to get a .deb of grub that supports TFTP. - -1. cd /usr/src/debian -2. apt-get source grub -3. cd grub-\_VERSION\_ -4. Add `--enable-tulip` or similar for your NIC to the `./configure` line of the `configure-stamp` target in the `debian/rules` file. -5. `dpkg-buildpackage` (as `root`) -6. `cd ..` -7. `dpkg -i grub*.deb` -8. cp /lib/grub/\_ARCH\_/\* /boot/grub/, e.g., _ARCH_ is `i386-pc` -9. Edit your `/boot/grub/menu.lst` (see below) -10. If your boot disk is `/dev/hda` ==> `grub-install (hd0)` - -### TFTP Boot - -Using trivial ftp to load a kernel is one of the best features of Grub. Here is how it is done. - -The `menu.lst` can look something like this: - - ifconfig --address=192.168.1.2 --server=192.168.1.1 - root (nd) - kernel /gnu/boot/oskit-mach.gz root=device:hd0s2 -- - root (hd0,1) - 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) - -**Note: Make sure there are NO spaces after the trailing backslases (\\)!!** - -For more information on GNUmach modules lines and installation setup, see [[Hurd/InstallNotes]] - --- [[Main/JoachimNilsson]] - 13 Apr 2005 diff --git a/Mach/BuildingOskitMach.mdwn b/Mach/BuildingOskitMach.mdwn deleted file mode 100644 index 334b0669..00000000 --- a/Mach/BuildingOskitMach.mdwn +++ /dev/null @@ -1,190 +0,0 @@ -## HowTo Build OSKit-Mach - - - - - - -

%TOC%

Introduction

This is a brief "HowTO build OSKit-Mach" (a.k.a GNUmach 2.0). It covers everything from getting the latest sources of both the OSKit and the GNUmach kernel, down to building and debugging them.

To be able to actually make use of your recently checked out CVS version of the GNUMach kernel & c:o you need a GNU system of gnu-20020816.tar.gz or later. See [[Distrib/TarballNotesHome]] for more info.

- -## Getting your hands on the source - -First you need to checkout the relevant sources. It comes in various flavours and the recommended way is to checkout from CVS. - -### The OSKit Sources - -**_Note:_** The [Savannah OSKit](http://savannah.gnu.org/projects/oskit/) project is the recommended source today of the OSKit. Its CVS tree holds the official sources and all known patches, plus a few others. - -**_Official Sources:_** - -* St. Patricks day 2002 release: - -* Valentine's day 2001 release: - -**_Official Patches:_** - -* Download useful [[OskitPatches]] or on the nearest Debian FTP. - -**_Savannah CVS:_** - -The recommended document for accessing the Savannah OSKit CVS is - -The following command should get the sources for you: - - $ export CVS_RSH="ssh" - $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/oskit co oskit - -Note: if you get a message about RSA/DSA keys, please go check it here: - -### GNUmach & Mig Sources - -The recommended document for accessing the Hurd CVS on Savannah is at - -Remember to set up you environment to use 'ssh' for cvs: - - $ export CVS_RSH="ssh" - -Note: if you get a message about RSA/DSA keys when using cvs commands, please go check it here: - -**_Gnu Mach:_** - -All development, apart from critical bug fixes, is done on the upcoming 2.0 release (OSKit/Mach). A potentially confusing point is that the code for OSKit/Mach (as opposed to the 1.X release, aka "GNU Mach") is now on the `TRUNK` of the 'gnumach' CVS module. In the past the trunk was 1.X (GNU Mach) and 2.0 (OSKit/Mach) was a branch. - - $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co gnumach - -In case you have been tracking the oskit-branch and want to move to the current `HEAD` branch you can issue the following instead to update your tree. - - $ cd - $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd update -Pd -A - -Where `` can be `gnumach`, `oskit-mach`, or similar. The `-A` is what moves you from a branch to the default (in this case HEAD), but without forcing a specific tag. `-P` Prunes your local copy from stale directories and `-d` creates new directories for you. - -**_The Hurd servers:_** - -In case you want to build the Hurd servers as well, you can check them out with: - - $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co hurd - -**_Inteface generator:_** - -See the [[microkernel/mach/MIG]] for more information. - -Check it out using - - $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co mig - -## Building - -The recommended versions of GCC are - -

For the OSKit: GCC 2.95.X
For GNUmach and MiG: GCC 3.2

- -### The OSKit - -Do _not_ forget to apply all known [[OskitPatches]] before starting the build! This does not apply if you use the OSKit from [Savannah](http://savannah.gnu.org/). - -The attached [[ATTACHURLmodulesx86pc]], or [[ATTACHURLmodules-lightx86pc]], is an example setup, your needs may vary but this one works for standard COTS PC's. Now, how to configure and build the OSKit. - - $ cd oskit-20020317/ - $ mkdir build - $ cd build - $ CC=gcc-2.95 \ - CFLAGS="-g" \ - ../configure --prefix=/usr/local \ - --enable-debug \ - --enable-modulefile=modules-light.x86.pc - $ make - $ sudo make install - -Comment: Barry deFreese - -For you newbies like me, I had problems using `modules.x86.pc.full` and `modules.x86.pc`. There seems to be problems with `examples/dyntest`. Make sure you pull down and use the [[ATTACHURLmodules-lightx86pc]]. - -Comment: Luis Miguel - -I needed to apply another patch that is not in CVS yet. The patch is in this [message](http://mail.gnu.org/archive/html/bug-hurd/2003-06/msg00054.html) in the bug-hurd mailing list. - -### Mach Interface Generator - -To build any Mach kernel you need an interface generator, MiG. To be on the safe side, use the CVS version. If you use Debian, you can install package [mig-i386-gnu](http://packages.debian.org/mig-i386-gnu). If you don't use Debian or want to compile MiG by yourself on Linux/\*BSD system, you must first install Mach headers. In Mach directory do: - - $ mkdir build - $ cd build - $ ../configure --prefix=/usr/local # Default prefix is / ! - $ sudo make -k install-headers # -k is for ignoring errors - -Now you are ready to compile and install MiG (commands are in Mig's source directory): - - $ automake --add-missing # sometimes it's needed - $ mkdir build - $ cd build - $ ../configure - $ make - $ sudo make install - -### GNUmach 2.0 (OSKit-Mach) - -Unlike its half sister, the OSKit-Mach kernel does _not_ need a cross compiler. The regular gcc for your x86 Linux system does just fine. However, you might want to use gcc 3.2 with the latest and greatest CVS version of Mach. - -**_Configuring:_** - - $ cd gnumach - $ mkdir build - $ cd build - $ MIG=/usr/local/bin/mig \ - CC=gcc-3.2 \ - CFLAGS="-g -O2" \ - OSKIT_LIBDIR=/usr/local/lib/oskit \ - ../configure --prefix=/gnu - -Comment: Barry deFreese - -I updated `CFLAGS` to `CFLAGS="-g -O2"`. Using just `-O` I was getting errors in the `machine_init` function. For newbies like me, the `-g` is only needed if you want to enable debugging. The `-O2` is Oh 2, not Zero 2. - -**_Building:_** - -Instead of using `make kernel` to build kernel, in OSKit-Mach you have to use make kernel-DRIVERS, where DRIVERS is DRIVER+DRIVER+...+DRIVER (a list of drivers separated by `+`). DRIVER can be one of: - -* `ide` -* `floppy` -* ethernet\_ETHDRV where ETHDRV is taken from `oskit/oskit/dev/linux_ethernet.h`. -* scsi\_SCSIDRV where SCSIDRV is taken from `oskit/oskit/dev/linux_scsi.h`. - -Thus, to build a IDE capable kernel with 3Com Vortex Boomerang support you use the following: - - $ make kernel-ide+ethernet_vortex - $ sudo make install - $ sudo gzip -f /gnu/boot/oskit-mach - -If the `make` command complains about missing dependencies, then you haven't passed correct `OSKIT_LIBDIR` variable to the `configure` script. Or you can use the patch below and pass something like `--with-oskit=/usr/local` to `configure`. - -Comment: Barry deFreese - -If you receive an error like `No rule to make target Kernel-ide...`, there is a patch for an issue with finding the oskit libraries. Then run `configure` on gnumach again with the option `--with-oskit=/path/to/oskit/libraries`. - -The patch can be found here: [gnumach-oskit-path.patch](http://www.vis.ethz.ch/~wagi/hurd/gnumach/gnumach-oskit-path.patch) Thanks wagi!! - -Don't use both `--with-oskit` and `OSKIT_LIBDIR`. Choose one of these methods. - -If you want to use tftp to download the kernel from Grub and don't care about the symbols I recommend either stripping or removing the `--enable-debug` and `-g` statements. - -## Debugging - -See the [[Mach/RemoteDebugOskitMach]] page. - -## Attachments - -* [[ATTACHURLmodulesx86pc]]: Configures modules to build in OSKit. -> Compared to 21May04 CVS, this adds SMP but omits the random module which was added to CVS in Jan03. - -* [[ATTACHURLmodules-lightx86pc]]: Lighter version of required modules. Used for building GNUmach with OSKit, i.e. OSKit/Mach. -> Compared to the above config, this omits the Linux, MSDOS, -> -> NetBoot, and PXE loader support, bootp support, OSKit on UNIX support, some thread-safe library versions, the address map manager, fsread, fsnamespace/\{fsn,fsn\_r\}, fudp, memdebug, memfs, smp, POSIX threads, svm, uvm, the Simple Process Library, realtime support, FreeBSD devices and code, linux/fs, the UDP library, **the sets of x86 and UNIX example kernels**, the testsuite, and the security server. **The new random module is also not configured.** diff --git a/Mach/BuildingOskitMach/modules-light.x86.pc b/Mach/BuildingOskitMach/modules-light.x86.pc deleted file mode 100644 index 07818cc5..00000000 --- a/Mach/BuildingOskitMach/modules-light.x86.pc +++ /dev/null @@ -1,236 +0,0 @@ -## -## OSKit Module configuration file. -## -## Comments are ignored, non-commented words should be -## OSKit directories to include in the build. -## -## Libraries are built in the order defined in this -## file. -## -## Specify this file with the --with-modulesfile= -## option to configure. By default the file 'modules' -## in the OSKit source directory is used. -## - -### Always include this module (the header files) -oskit - -### The flask module must be compiled before -### most of the other modules. -### It is currently a required module. -flask - -### Builds the documentation (Utah only) -#doc - - -### --- Required components - -### The C Runtime (the magic that calls 'main') (required) -crt - -knit/c - -### Various bits of kernel magic (required) -kern - -### List Memory Manager (required) -lmm - -### The Client OS library (required) -clientos - - -### --- Boot Adaptors - -### Build the multiboot compliant boot adaptor -### Requires that ld support '-format binary' (checked) -boot/multiboot - -### Build the Linux boot adaptor -### Requires ld support '-oformat binary' (checked) -#boot/linux - -### Build the MSDOS boot adaptor (??) -## Requires ld support '-oformat msdos' (checked) -#boot/dos - -### Build the BSD boot adaptor -### Requires some sort of a.out linker (checked) -#boot/bsd - -### The NetBoot Meta-kernel -#boot/net - -### Build the PXE compliant boot loader -#boot/pxe - -### --- OSKit-on-UNIX support libraries. -#unix - -### --- C Libraries - -### A minimal standard C library -libc - -### A much more complete standard C library -posix/sys - -### Thread-safe version of the previous -#posix/sys_r - - -### --- Miscellaneous utility libraries - -### Address Map Manager -#amm - -### Library for contacting a bootp server -#bootp - -### Com IIDs library (required for most kernels) -com - -### For groking disk partitions -diskpart - -### Include the Dynamic Packet Filter library -#dpf/dpf - -### Exec library for loading linked executables -exec - -### Read-only access to a number of filesystems -#fsread - -### Filesystem name parsing library -#fsnamespace/fsn - -### Same as above, but multithread safe -#fsnamespace/fsn_r - -### Fake UDP library (Only supports UDP send) -#fudp - -### Include the Hierarchical Packet Fair Queueing module -#hpfq - -### The Memdebug library -#memdebug - -### The memory file system -#memfs - -### SMP support (believed to be broken) -#smp -## the SMP example -#examples/x86/smp ### requires smp - -### POSIX threads -#threads - -### Simple Virtual Memory -#svm - -### UVM -#uvm/uvm - -### Simple Process Library -#uvm/sproc -### the sproc example -#examples/x86/sproc ### requires sproc - -### --- Startup Library - -### Simpler functions for initializing OSKit subsystems -### NOTE: this drags in almost every other library. -#startup - - -### --- Devices, Networks and Filesystems - -### The device layer glue. Depends on lmm and kern -### Required for any kernel that uses OSKit devices. -dev - -### Realtime support. Needed for realtime threads and for GPROF. -#realtime - -### Devices and code stolen from FreeBSD -#freebsd/dev -#freebsd/net_flask -#freebsd/net -#freebsd/libm -#freebsd/libc -#freebsd/libc_r - -### Include Run-time linker support. This must come after freebsd build -#rtld -## The rltd example -#examples/dyntest ### requires rtld - -### Stuff stolen from Linux -linux/dev -#linux/fs - -### Stuff stolen from NetBSD -#netbsd/fs - -### SVGA video library -#video/svgalib -### SVGA-related examples -#examples/x86/video_svga ### requires video/svgalib - -### X11 video library -#x11/client -#x11/video -### X11-related examples -#examples/x86/video_x11 ### requires x11/video - -### The zlib compression library -#zlib - -### The UDP library. More complete than fudp, but not totally complete. -#udp - -### The Utah testbed TMCP communication library and examples -#tmcp -#examples/tmcp - -### The NetDisk kernel. -## Requires the zlib compression library. -## Requires the udp library. -#netdisk - -### --- Scripts and build/debug utilities - -### Includes the CPU-oskit-gcc wrapper. -unsupported - - -### --- Additional stuff that must be at or near the end of the build - - -### Sets of example kernels -#examples/x86 -#examples/x86/extended -#examples/x86/threads - -### Building the example kernels as host-build binaries with unix-mode -### emulation. NOTE: These will only be built if you are compiling -### the OSKit with unixmode support (and on Linux or FreeBSD). -#examples/unix -#examples/unix/extended -#examples/unix/threads - -### The OSKit test infrastructure -#testsuite - -### The security server -#security -## security server example kernel -#examples/x86/security ### requires security - -### The Mad MPEG audio decoder library and example -#libmad -#libmad/minimad diff --git a/Mach/BuildingOskitMach/modules.x86.pc b/Mach/BuildingOskitMach/modules.x86.pc deleted file mode 100644 index bb27aca3..00000000 --- a/Mach/BuildingOskitMach/modules.x86.pc +++ /dev/null @@ -1,236 +0,0 @@ -## -## OSKit Module configuration file. -## -## Comments are ignored, non-commented words should be -## OSKit directories to include in the build. -## -## Libraries are built in the order defined in this -## file. -## -## Specify this file with the --with-modulesfile= -## option to configure. By default the file 'modules' -## in the OSKit source directory is used. -## - -### Always include this module (the header files) -oskit - -### The flask module must be compiled before -### most of the other modules. -### It is currently a required module. -flask - -### Builds the documentation (Utah only) -#doc - - -### --- Required components - -### The C Runtime (the magic that calls 'main') (required) -crt - -knit/c - -### Various bits of kernel magic (required) -kern - -### List Memory Manager (required) -lmm - -### The Client OS library (required) -clientos - - -### --- Boot Adaptors - -### Build the multiboot compliant boot adaptor -### Requires that ld support '-format binary' (checked) -boot/multiboot - -### Build the Linux boot adaptor -### Requires ld support '-oformat binary' (checked) -boot/linux - -### Build the MSDOS boot adaptor (??) -## Requires ld support '-oformat msdos' (checked) -#boot/dos - -### Build the BSD boot adaptor -### Requires some sort of a.out linker (checked) -#boot/bsd - -### The NetBoot Meta-kernel -boot/net - -### Build the PXE compliant boot loader -#boot/pxe - -### --- OSKit-on-UNIX support libraries. -unix - -### --- C Libraries - -### A minimal standard C library -libc - -### A much more complete standard C library -posix/sys - -### Thread-safe version of the previous -posix/sys_r - - -### --- Miscellaneous utility libraries - -### Address Map Manager -amm - -### Library for contacting a bootp server -bootp - -### Com IIDs library (required for most kernels) -com - -### For groking disk partitions -diskpart - -### Include the Dynamic Packet Filter library -#dpf/dpf - -### Exec library for loading linked executables -exec - -### Read-only access to a number of filesystems -fsread - -### Filesystem name parsing library -fsnamespace/fsn - -### Same as above, but multithread safe -fsnamespace/fsn_r - -### Fake UDP library (Only supports UDP send) -fudp - -### Include the Hierarchical Packet Fair Queueing module -#hpfq - -### The Memdebug library -memdebug - -### The memory file system -memfs - -### SMP support (believed to be broken) -smp -## the SMP example -examples/x86/smp ### requires smp - -### POSIX threads -threads - -### Simple Virtual Memory -svm - -### UVM -uvm/uvm - -### Simple Process Library -uvm/sproc -### the sproc example -examples/x86/sproc ### requires sproc - -### --- Startup Library - -### Simpler functions for initializing OSKit subsystems -### NOTE: this drags in almost every other library. -startup - - -### --- Devices, Networks and Filesystems - -### The device layer glue. Depends on lmm and kern -### Required for any kernel that uses OSKit devices. -dev - -### Realtime support. Needed for realtime threads and for GPROF. -realtime - -### Devices and code stolen from FreeBSD -freebsd/dev -#freebsd/net_flask -freebsd/net -freebsd/libm -freebsd/libc -freebsd/libc_r - -### Include Run-time linker support. This must come after freebsd build -#rtld -## The rltd example -#examples/dyntest ### requires rtld - -### Stuff stolen from Linux -linux/dev -linux/fs - -### Stuff stolen from NetBSD -netbsd/fs - -### SVGA video library -#video/svgalib -### SVGA-related examples -#examples/x86/video_svga ### requires video/svgalib - -### X11 video library -#x11/client -#x11/video -### X11-related examples -#examples/x86/video_x11 ### requires x11/video - -### The zlib compression library -#zlib - -### The UDP library. More complete than fudp, but not totally complete. -udp - -### The Utah testbed TMCP communication library and examples -#tmcp -#examples/tmcp - -### The NetDisk kernel. -## Requires the zlib compression library. -## Requires the udp library. -#netdisk - -### --- Scripts and build/debug utilities - -### Includes the CPU-oskit-gcc wrapper. -unsupported - - -### --- Additional stuff that must be at or near the end of the build - - -### Sets of example kernels -examples/x86 -examples/x86/extended -examples/x86/threads - -### Building the example kernels as host-build binaries with unix-mode -### emulation. NOTE: These will only be built if you are compiling -### the OSKit with unixmode support (and on Linux or FreeBSD). -examples/unix -examples/unix/extended -examples/unix/threads - -### The OSKit test infrastructure -testsuite - -### The security server -security -## security server example kernel -examples/x86/security ### requires security - -### The Mad MPEG audio decoder library and example -#libmad -#libmad/minimad diff --git a/Mach/OskitMach.mdwn b/Mach/OskitMach.mdwn deleted file mode 100644 index c28f2d89..00000000 --- a/Mach/OskitMach.mdwn +++ /dev/null @@ -1,64 +0,0 @@ -[[toc ]] - -* [[OskitMachStatusList]]: Status and TODO list (deb status) -* [[OskitMachPatches]]: Bleeding edge patches -* [[OskitPatches]]: Useful patches for the OSKit -* [[BuildingOskitMach]]: How to build your own GNUmach kernel -* [[RemoteDebugOskitMach]]: How to use gdb to remote debug the GNUmach kernel - - -## About - -OSKit-Mach began as a branch of the GNUMach 1.2 kernel, but since the release of GNU Mach 1.3, OSKit-Mach has been merged as the new GNUMach 2.x mainline. The [[history]] page tells a more interesting story including other operating systems who use Mach in their kernels. - -GNU Mach 2.0 makes use of the drivers provided by [the OSKit](http://www.cs.utah.edu/flux/oskit/) from [the Flux Research Group](http://www.cs.utah.edu/flux/). The OSKit provided a neat driver base where both [[TWiki/FreeBSD]] and Linux (2.2.12) drivers are made available to [Mach](http://www-2.cs.cmu.edu/afs/cs/project/mach/public/www/mach.html) and thus the Hurd. However, OSKit isn't maintained anymore. - -## Status - -The OSKit-Mach version of GNUmach is today (2005) more or less defunct. Nobody -is working on it. Few people ever got it running, and by now there are also -problems building with recent toolchains. Instead, the Hurd developers now -concentrate on completely different microkernels (Coyotos being the current -favourite), as well as on improving the original GNU Mach 1.x codebase. (See -also [[microkernel/mach/gnumach/projects]].) - -The [[mailing_lists]], or the [[IRC]] is, like always, the best source of more -current information. - -There also exist other efforts: - -* [OSKit and OSKit-Mach PPC Port](http://es.gnu.org/~jemarch/ppc-oskit/) - Maintained by [Jos� Marchesi](mailto:jemarch AT gnu DOT org) - -* [OSKit-Mach Alpha Port](http://savannah.gnu.org/projects/gnumach-alpha/). - This work has been integrated into the actual OSkit cvs tree at utah. - -## Building - -First you need to get the latest OSKit release and, preferrably, the latest CVS version of GNUmach. Take a look at the following [tutorial](http://www.etherhogz.org/doc/oskit-mach.html) to get started. Or the locally kept version, [[BuildingOskitMach]]. - -## Starting - -You start Oskit-Mach almost the same way as the old 1.x version of GNUmach. Using [[Hurd/GrubNotes]] an entry can look like this: - - title GNUmach 1.90 (CVS) - root (hd0,1) - kernel /boot/oskit-mach.gz root=device:hd0s2 -- - 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) - -_Remember_ to ensure that there are no trailing spaces after the backslashes on the lines above if you copy-paste this into your menu.list file. - -## Bugs - -We have bugs, just like any other software product. To get around the more nasty ones you can apply the unofficial patches found on - -* [[OskitMachPatches]] - -## Debugging - -See Igor Khavkine's, [i\_khavki@alcor.concordiaNOSPAM.ca](mailto:i_khavki@alcor.concordiaNOSPAM.ca), excellent help to [remote debug oskit-mach over a serial line](http://www.etherhogz.org/doc/oskit-boot.txt), or the local [[RemoteDebugOskitMach]]. - diff --git a/Mach/OskitMachPatches.mdwn b/Mach/OskitMachPatches.mdwn deleted file mode 100644 index c1e1b068..00000000 --- a/Mach/OskitMachPatches.mdwn +++ /dev/null @@ -1,10 +0,0 @@ -## GNUmach2 (oskit-mach) Patches - -The following patches are here for your convenience only. They are probably not accepted yet and should thus only be used by people working on the bleeding edge of ... oh well, use at your own risk. :-) - -**_Daniel Wagner:_** - -* Fix GNUmach2 panic related to buggy softint handling [[ATTACHURLpatch-gnumach_softint-wagidiffgz]] -* Eliminate GNUmach2 assertion that triggers a bug [[ATTACHURLpatch-gnumach_assertion-wagidiffgz]] - -- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/Mach/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz b/Mach/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz deleted file mode 100644 index 3d57b43a..00000000 Binary files a/Mach/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz and /dev/null differ diff --git a/Mach/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz b/Mach/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz deleted file mode 100644 index 215706b3..00000000 Binary files a/Mach/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz and /dev/null differ diff --git a/Mach/OskitMachStatusList.mdwn b/Mach/OskitMachStatusList.mdwn deleted file mode 100644 index f62e0686..00000000 --- a/Mach/OskitMachStatusList.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -**NOTE**: As of March 2006, nobody is using or working on OSKit-Mach. Consider below text for historic reference only. - -The only thing that is needed before we will switch to the OSKit-Mach variant of GNU Mach is the missing console: OSKit-Mach has no console in the kernel, so we need an implementation in user space. Marcus Brinkmann is writing a console implementation with a client-server design, Unicode support and lots of other goodies. The server is working, the ncurses client is working (which is useful for testing and results in something similar to screen) and the VGA client is the one missing component. A part of the code for it already exists; it will share some code with the ncurses client via a console-client library. After it works, some testing of OSKit-Mach will also be needed. - --- [[Main/WolfgangJ]] - 24 Jul 2002 - -There was quite a bit of coding and testing in September as described in several [bug-hurd threads](http://mail.gnu.org/pipermail/bug-hurd/2002-September/thread.html). - -Unfortunately this work still needs to be ported from GNUmach 1.3 (commonly used today) to GNUmach 2.0 (a.k.a OSKit-Mach). - --- [[Main/GrantBow]] - 07 Oct 2002 - -There should now exist a working console-client for [[OskitMach]] as well. - --- [[Main/JoachimNilsson]] - 28 Nov 2002 diff --git a/Mach/OskitPatches.mdwn b/Mach/OskitPatches.mdwn deleted file mode 100644 index d189bb6d..00000000 --- a/Mach/OskitPatches.mdwn +++ /dev/null @@ -1,67 +0,0 @@ -## Table of Contents - -%TOC% - -## Flux OS Toolkit - -[The OSKit](http://www.cs.utah.edu/flux/oskit/) is a framework and a set of libraries for building and extending operating systems developed by [the Flux Project](http://www.cs.utah.edu/flux/). - -**_Note:_** All of these patches, and more, are now avilable directly through the [Savannah OSKit](http://savannah.gnu.org/projects/oskit/) project. This is also the recommended source today of the OSKit, especially if you want to use it with GNUmach2. - -## OSKit 2001-02-14 - -These are extra patches for people who, for some reason, use the 2001 version of the OSKit. - -* Patrick Tullman [[ATTACHURLpatch-oskit-097-tullmandiffgz]] - -* This patch is necessary to get the `--enable-indirect-osenv` flag to the configure script. The flag is enabled by default for OSKit 2002-03-17 and later. Kevin Kraemer [[ATTACHURLpatch-oskit-097-kkraemerdiffgz]] - -## OSKit 2002-03-17 - -**_Critical Patches:_** - -Here are the patches critical to get [[OskitMach]] running. These are absolutely essential to get a working Mach kernel. Many of these patches are included with the Debian distribution of the OSKit. - -* Igor Khavkine [[ATTACHURLpatch-oskit-097-i_khavkidiffgz]] - -* Famous removal of only one line in sbrk-hack.c - needed for people with newer libc's (e.g. Debian Woody) [[ATTACHURLpatch-oskit-097-sbrk_hackdiffgz]] - -* Jonathan S. Arney - Important patch to diskpart library. Without it you cannot activate swap in oskit-mach. [[ATTACHURLpatch-oskit-097-jon_arneydiffgz]] - -* Richard Kreuter's [patches](http://anduril.rutgers.edu/richard/oskit/) ([announcement](ftp://flux.cs.utah.edu/flux/oskit/mail/html/oskit-users/msg01560.html)). Needed when your Hurd partition is embedded inside an extended partition created by Windows. The patches also include: - * support for extended partitions with lba - * support for 16-entry BSD disklabels, as are supported by recent Net- and [[TWiki/FreeBSD]] kernels. - * support for the recognition of NetBSD's slice id (169) in the BIOS partition table. - -**_Cosmetic Patches:_** - -* Kevin Kraemer - Removes annoying debug output from eepro.c driver. [[ATTACHURLpatch-oskit-097-eeprodiffgz]] - -* Ognyan Kulev - Reduce warnings when compiling with GCC 3.2. - -**_New Functionality:_** - -* [Roland McGrath](http://www.frob.com/) - [i8042 support](http://mail.gnu.org/archive/html/bug-hurd/2002-10/msg00146.html). Thread continues at - -* Daniel Wagner - PCMCIA support. ([instructions](http://www.vis.ethz.ch/~wagi/hurd/oskit/readme.txt)) - -* [[Main/JoachimNilsson]] - See [[Hurd/JoachimNilssonHurdPage]] - * Upgrade to Linux 2.2.22 drivers - * More Linux NIC drivers - * **_Soon:_** ATA-100 patches (α-release available) - -* [[Main/DerekDavies]] - [OSKit Entropy patch](http://www.ddavies.net/oskit-entropy/). A Linux entropy driver, see [bug-hurd posting](http://mail.gnu.org/archive/html/bug-hurd/2003-01/msg00000.html) for more information. - ----- - -## Comments - -Divided this growing topic into sections.
-- [[Main/JoachimNilsson]] 19 Nov 2002 - -Updates by [[Main/OgnyanKulev]] -- 19 Nov 2002 - -All small patches are as attachments now. -- [[Main/OgnyanKulev]] - 16 Dec 2002 - -Minor updates, also, added Davids Entropy patch -- [[Main/JoachimNilsson]] - 03 Jan 2003 - -Fixed some gnu mail links -- [[Main/MattGrant]] - 26 Feb 2003 diff --git a/Mach/OskitPatches/patch-oskit-0.97-eepro.diff.gz b/Mach/OskitPatches/patch-oskit-0.97-eepro.diff.gz deleted file mode 100644 index 80d94f3f..00000000 Binary files a/Mach/OskitPatches/patch-oskit-0.97-eepro.diff.gz and /dev/null differ diff --git a/Mach/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz b/Mach/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz deleted file mode 100644 index 2e322de9..00000000 Binary files a/Mach/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz and /dev/null differ diff --git a/Mach/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz b/Mach/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz deleted file mode 100644 index aaf1475a..00000000 Binary files a/Mach/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz and /dev/null differ diff --git a/Mach/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz b/Mach/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz deleted file mode 100644 index 7d75a34e..00000000 Binary files a/Mach/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz and /dev/null differ diff --git a/Mach/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz b/Mach/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz deleted file mode 100644 index 2fef6632..00000000 Binary files a/Mach/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz and /dev/null differ diff --git a/Mach/PortToL4.mdwn b/Mach/PortToL4.mdwn deleted file mode 100644 index fb7f0004..00000000 --- a/Mach/PortToL4.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -**_The Hurd-L4 port has an [official page](http://www.gnu.org/software/hurd/hurd-l4.html) with more up-to-date information_** -- [[Main/OgnyanKulev]] - 05 Feb 2005 - -A group of one being led by Neal H. Walfield is working on porting the Hurd to the pistachio version of the L4 microkernel. This second generation microkernel provides a significantly different API than the one offered by the Mach microkernel, a first generation microkernel. One of the primary goals of the project, outside of porting the Hurd to L4, is to reevaluate the current Hurd abstractions and consider how they can be modified to be more general. - -I have no web page describing my efforts. There is a mailing list[1]. - -[1] - --- Neal Walfield, 18 Sep 2002 - -Neal noted [1] that there are licensing issues being worked out so no code is yet released. His work was performed in the summer of 2002 at Karlsruhe. - -[1] - --- [[Main/GrantBow]] - 21 Sep 2002 - -There are several important pages that are of interest for the L4 & hurd communities. - -* Main L4 home page - -* Hurd on L4 - -* Hurd on L4 - -* - --- [[Main/GrantBow]] - 22 May 2002 - - - --- [[Main/GrantBow]] - 24 Oct 2002 - -There was [discussion in October 2002](http://mail.gnu.org/pipermail/l4-hurd/2002-October/000727.html) about the differences between Hurd on Mach and Hurd on L4 with some interesting URLs. In the thread Okuji [responds](http://mail.gnu.org/pipermail/l4-hurd/2002-October/000728.html) confirming his document is two years old and outdated by the directions that Neal is taking in furthering this effort. The URLs in that email might be helpful to those learning more about Hurd and L4 ideas that were considered yet abandoned. - --- [[Main/GrantBow]] - 04 Jan 2003 - -A "Porting GNU Hurd to L4" website: - -* - --- [[Main/SebastianGabriel]] - 29 Sep 2003 - -The only valid L4-Hurd link on is - --- [[Main/JoachimNilsson]] - 29 Sep 2003 diff --git a/Mach/PosixSemaphores.mdwn b/Mach/PosixSemaphores.mdwn deleted file mode 100644 index be5586bd..00000000 --- a/Mach/PosixSemaphores.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -Posix Semaphores are an optional part of pthreads. There is currently an implementation for Neal Walfields libpthread, which is included in the hurd sources tree. This implemention uses a mutex and a condition variable. The implmentation is in the mailing list archives at [ [http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html](http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html)](http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html). - -Neal does not want to use this implementation because it adds the overhead of a condition variable. The condition variable imposes the following penalties: 1 extra spinlock/unlock 1 an extra call to a pthread cleanup function. - -The first penalty has virtually no cost because we know that we will never spin trying to get this spin lock because we already have a mutex lock outside the condition variable serializing accesses to the condition variable. - -The second may be more of a performance penalty, but it saves reimplmenting the code in pt-cond-signal.c pt-cond-wait.c, and pthread-timedwait.c . - --- [[Main/JamesAMorrison]] - 19 Jan 2003 - -Moved page to Mach web. - --- [[Main/GrantBow]] - 21 Jan 2003 diff --git a/Mach/RemoteDebugOskitMach.mdwn b/Mach/RemoteDebugOskitMach.mdwn deleted file mode 100644 index c260ce25..00000000 --- a/Mach/RemoteDebugOskitMach.mdwn +++ /dev/null @@ -1,195 +0,0 @@ -# Remote Debug GNUmach - -# Table of Contents - -%TOC% - -# Booting oskit-mach with a serial console - -**Original Author:** Igor Khavkine **Last Updated:** Mon Jul 30 17:58:55 EDT 2001 - ----- - -## Introduction - -This document now has a wider audience. The OSKit branch of GNUmach has been merged with the main branch, HEAD. Please note that the instructions here are not tested with the latest stable release, GNUmach 1.3. - -Here you will find out how to access, build, bootstrap and debug the latest CVS version of the GNUmach kernel (the OSKit based 2.x series of GNUmach). - -## Why? - -Because it's covenient. If you have a second computer, but not a second monitor or keyboard, you can connect your second box to your main one using null-modem serial cables. Once that is done, you can configure the GRUB bootloader to use the serial port when starting up and boot [GNUmach](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/gnumach/?only_with_tag=HEAD) (a.k.a [[OskitMach]]) without having to switch monitor cables or type blindly at a second keyboard. - -Also, [[OskitMach]] supports the GDB remote debugging protocol over a serial line. This way it is now possible to debug the running kernel relatively unobtrusively, because the debugger will not be running on the same machine. - -## How? - -First you need some equipment: two computers, each one should have at least one (two is preferable) free serial port(s) and one (or two) null-modem serial cable(s). - -While developing the kernel it might also be a good idea to use grub to get the Mach kernel via tftp from the same server you do the remote debugging and building on. This way you don't need to reboot the target to copy or build a new kernel on its hard drive. See the [[AdvancedGrubUsage]] document for more information on this. - -Last you need to follow the instructions given below. - -1. The first step is to the get source for oskit-mach and OSKit. - Currently the [St. Patrick's day release](ftp://flux.cs.utah.edu/flux/oskit/oskit-20020317.tar.gz), 2002-03-17, of the OSKit is the latest. Get the sources and compile them yourself, compile OSKit with debugging symbols if that is what you need. If you encounter errors while compiling, try removing anything that has to do with `unix` or `examples` from the file `modules.x86.pc`. - Then you need to get the sources for oskit-mach version of the GNU Mach kernel, available from the GNU CVS repository[3]. Previously you needed to check out the `gnumach` module with the flag `-roskit-branch`. Today the 2.0 branch of GNU Mach resides on the HEAD branch, so you don't have to provide any specifc branch information to get the correct version. Use the update command with `-rHEAD` to move from the oskit-branch to the HEAD branch. - Again now is your chance to compile oskit-mach with debugging symbols. - (More detailed instructions can be found in [[BuildingOskitMach]].) -2. Now you need to setup GRUB on your second box so it accepts input from a serial port while booting up. This is simple to do by adding the following lines to your `menu.lst` file, before any of the menu entries: - serial --unit=0 --speed=9600 - terminal serial - Unit refers to the serial port you wish to use (0 is COM1), and speed is optional. For more information see the GRUB documentation. -3. You need to make sure that your main box has the necessary utilities to communicate with your second box over a serial line. You can use a terminal emulator like _minicom_(1), _seyon_(1), _tip_(1), or a simple serial communication program _cu_(1) which comes with the GNU uucp package. Or if you feel really lazy you can use this hack: - stty raw - cat > /dev/ttyS1 # in one terminal window - cat /dev/ttyS1 # in a second terminal window -4. Now you have to make sure your computer has an at least partially setup Hurd partition. You can find instructions how to do that here [4,5]. Copy the oskit-mach kernel binary compressed with gzip to `/boot/oskit-mach.gz` and use the following command line[1] to boot it from GRUB: - kernel /boot/oskit-mach.gz -h CONS_COM=1 -d GDB_COM=2 BAUD=9600 root=device:hd0s2 -- -

-h

use serial console:

CONS_COM=1 (COM1)
CONS_COM=2 (COM2)
CONS_COM=3 (COM3)
CONS_COM=4 (COM4)

-d

enable serial port debugging, optional

GDB_COM=2

use a different port other then CONS_COM, default is to use the same as CONS_COM

BAUD=9600

use this baud rate, optional, default is 9600

--

delimits the arguments passed to the oskit from those to the kernel

root=device:hd0s2

tell gnumach which is your root partition, in this case it's hd0s2

-5. Now I suggest that you familiarize yourself with [the GDB documentation](http://vmlinux.org/doc/gdb/), especially on remote debugging. If you pass the `-d` boot flag to oskit-mach, then it will automatically insert a breakpoint at main() and wait for further instructions from GDB over the serial line. Here's a simple example of how to attach GDB to a remote target over a serial line: - $ script # record the debugging session - $ gdb # assume you're in the oskit-mach build dir. - (gdb) file kernel - (gdb) set remotebaud 9600 - (gdb) target remote /dev/ttyS1 - [...gdb attached, blah, blah, blah...] - (gdb) break panic - (gdb) continue - (gdb) continue - [...] - (gdb) quit - $ ^D # finish recording the session - This way you can catch any kernel panics (except for the really nasty ones and try to debug them). - I've noticed that once Mach is running under GDB, pressing C-c from GDB will not suspend it, this makes it hard to set additional breakpoints after the kernel is running. So optionally you can modify Mach to add a dummy system call that will be used only for setting breakpoints, and make a small program that calls it, you can use it whenever you want to pause the kernel and examine something under GDB. An example of how to do this is attached in Appendix A. - -TODO: OSKit overrides interrupts 1 and 3 in kern/x86/gate\_init.c:gate\_init. A patch that skips src->vector `= 1 || =` 3 have to be prepared and attached to this page. More robust solution is to make OSKit/GNUMach recognize when it's debugged and change vector table accordingly. - -Now you're all set to do some serious kernel hacking. I hope more people will take advantage of this opportunity. - -## Appendix A - -TODO: Move inline diff and code into 2 attached files: one for patching GNU Mach, and one for gdb-break.c. - -Apply this patch to oskit-mach to add a dummy system call: - - --- gdb-stub.diff --- - Index: kern/syscall_sw.c - =================================================================== - RCS file: /cvs/gnumach/kern/syscall_sw.c,v - retrieving revision 1.1.1.1.2.2 - diff -u -r1.1.1.1.2.2 syscall_sw.c - --- kern/syscall_sw.c 2001/04/05 06:52:47 1.1.1.1.2.2 - +++ kern/syscall_sw.c 2001/07/30 21:45:14 - @@ -98,6 +98,8 @@ - extern kern_return_t syscall_fipc_recv(); - #endif /* FIPC */ - - +/*XXX*/extern kern_return_t gdb_break_stub (); - + - mach_trap_t mach_trap_table[] = { - MACH_TRAP(kern_invalid, 0), /* 0 */ /* Unix */ - MACH_TRAP(kern_invalid, 0), /* 1 */ /* Unix */ - @@ -283,7 +285,14 @@ - MACH_TRAP(kern_invalid, 0), /* 126 */ - MACH_TRAP(kern_invalid, 0), /* 127 */ - MACH_TRAP(kern_invalid, 0), /* 128 */ - - MACH_TRAP(kern_invalid, 0), /* 129 */ - + MACH_TRAP(gdb_break_stub, 1), /* 129 */ - }; - - +volatile int gdb_break_stub (void *addr) /*XXX*/ - +{ - + void *dummy; - + dummy = addr; - + return 0; - +} - + - int mach_trap_count = (sizeof(mach_trap_table) / sizeof(mach_trap_table[0])); - --- end --- - -When starting an oskit-mach debug session with GDB set a break point at `gdb_break_stub`. Then use this program to invoke the system call when desired: - - --- gdb-break.c --- - /* Compile with: gcc -o gdb-break gdb-break.c gdb-break-stub.S */ - - #include - - #include - #include - - extern int gdb_break_stub (void *addr); - - int main () - { - kern_return_t err; - - err = gdb_break_stub (&main); - printf ("result from syscall: %s\n", strerror(err)); - - return 0; - } - --- end --- - --- gdb-break-stub.S --- - #include - - kernel_trap(gdb_break_stub,-129,1) - --- end --- - -## References - -* [1] OSKit documentation, section 1.6.3. -* [2] -* [3] -* [4] -* [5] - - vim:ts=8:tw=72:sw=8: - ----- - -This HowTo is (C) Copyright 2001 Igor Khavkine. - -Minor additions and grammatical fixups by [[JoachimNilsson]]. - --- [[Main/JoachimNilsson]] - 14 May 2002 - -Additions on booting GNU Mach via TFTP - --- [[Main/JoachimNilsson]] - 13 Jun 2002 - -Text formatting. - --- [[Main/OgnyanKulev]] - 16 Dec 2002 diff --git a/unsorted/ABITransitionStatus.mdwn b/unsorted/ABITransitionStatus.mdwn new file mode 100644 index 00000000..123e8f8c --- /dev/null +++ b/unsorted/ABITransitionStatus.mdwn @@ -0,0 +1,9 @@ +Several transitions have occured recently. + +* [ABI Switch](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00096.html) from April 17, 2002 + +* [Phase I accomplished](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00157.html) from April 26, 2002 + +* [status of the ABI transition](http://lists.debian.org/debian-hurd/2002/debian-hurd-200205/msg00242.html) from May 15, 2002 + +-- [[Main/GrantBow]] - 15 May 2002 diff --git a/unsorted/AdvancedGrubUsage.mdwn b/unsorted/AdvancedGrubUsage.mdwn new file mode 100644 index 00000000..8e307b4f --- /dev/null +++ b/unsorted/AdvancedGrubUsage.mdwn @@ -0,0 +1,42 @@ +## Advanced Grub + +[Grub](http://www.gnu.org/software/grub/) is a capable boot loader. This document is intended to capture some of its most interesting features and try to explain them a bit better than the texinfo documentation. + +### Debian Grub + +The Debian grub packages do not have networking enabled, so you have to apt-get the source, modify the debian/rules file to include --enable-network-card and dpkg-buildpackage to get a .deb of grub that supports TFTP. + +1. cd /usr/src/debian +2. apt-get source grub +3. cd grub-\_VERSION\_ +4. Add `--enable-tulip` or similar for your NIC to the `./configure` line of the `configure-stamp` target in the `debian/rules` file. +5. `dpkg-buildpackage` (as `root`) +6. `cd ..` +7. `dpkg -i grub*.deb` +8. cp /lib/grub/\_ARCH\_/\* /boot/grub/, e.g., _ARCH_ is `i386-pc` +9. Edit your `/boot/grub/menu.lst` (see below) +10. If your boot disk is `/dev/hda` ==> `grub-install (hd0)` + +### TFTP Boot + +Using trivial ftp to load a kernel is one of the best features of Grub. Here is how it is done. + +The `menu.lst` can look something like this: + + ifconfig --address=192.168.1.2 --server=192.168.1.1 + root (nd) + kernel /gnu/boot/oskit-mach.gz root=device:hd0s2 -- + root (hd0,1) + 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) + +**Note: Make sure there are NO spaces after the trailing backslases (\\)!!** + +For more information on GNUmach modules lines and installation setup, see [[Hurd/InstallNotes]] + +-- [[Main/JoachimNilsson]] - 13 Apr 2005 diff --git a/unsorted/AptConfOffline.mdwn b/unsorted/AptConfOffline.mdwn new file mode 100644 index 00000000..c4cc85be --- /dev/null +++ b/unsorted/AptConfOffline.mdwn @@ -0,0 +1,28 @@ + APT + { + /* This file belongs in Debian GNU/Hurd's /etc/apt/apt.conf.offline + and will be used when running Debian GNU/Linux. This is only + required when the GNU/Hurd does not have network access. */ + + 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 + assumes Debian GNU/Hurd mounted on /misc/hurd and /var mounted underneath this if necessary */ + + // State::lists should be here, the lists subdirectory. + State "/misc/hurd/var/lib/apt/"; + State::status "/misc/hurd/var/lib/dpkg/status"; + + // Binary caches will be stored locally + Cache::archives "/misc/hurd/var/cache/apt/archives/"; + Cache "/tmp/"; + + // Location of the source list. + Etc "/misc/hurd/etc/apt/"; + }; diff --git a/unsorted/BuildingHurdLiveCD.mdwn b/unsorted/BuildingHurdLiveCD.mdwn new file mode 100644 index 00000000..e2082268 --- /dev/null +++ b/unsorted/BuildingHurdLiveCD.mdwn @@ -0,0 +1,70 @@ +# Recipes for bootable GNU Mach/Hurd Live CD + +## Greg's recipe + +In my attempts to get a bootable CD for the Hurd here's the recipe I followed, your's will be similar. I needed a grub-0.92, with a patch from , and version 1.16 of mkbimage (I don't exactly remember where I got that from). + +You can grab a copy of it at , which is a gzipped bootable \*.iso with the copy of the patched grub and the version of mkbimage I used. Here's the recipe I followed (under linux). + + # mkdir ./2.88floppy + # mkdir ./isodir + # cp grub/* 2.88floppy/boot/grub/ + # cp grub/* isodir/boot/grub/ + # cd 2.88floppy + # tar -cf ../floppyimg.tar * + # cd .. + # mkbimage -f floppyimg.tar -t 2.88 + # cp 2.88.image isodir/ + # mkisofs -r -b 2.88.image -c boot.catalog -o hurdcd.iso isodir/ + # cdrecord -v speed=4 dev=0,0,0 -data hurdcd.iso + +That was the recipe for using a floppy image. If you use the `-t hd` switch of `mkbimage`, you'll get an ext2fs El-Torito HD emulation image that can be any size (I've got one here 300+ MB). You can then use `root (hd0,0)` in Grub to boot something. Also, invoking `mkbimage` with no parameters will give you some additional help messages. + +-- [[Main/GregBuchholz]] - 05 Nov 2003 + +## Another recipe for a bootable GNU CD + +[screenshot](http:///mycelium.afraid.org/Screenshot2.png) + +### What you'll need + +* A [stage2\_eltorito](http://mycelium.dyndns.org/stage2_eltorito) from [grub 0.95](http://www.gnu.org/software/grub) +* A [base system](http://www.update.uu.se/~ams/gnu/gnu-2004-12-04.tar.bz2) +* [iso9660fs.static](http:///mycelium.dyndns.org/iso9660fs.static) (this link is bought the farm) or just build your own, it should work with CVS + +### HowTo + + # mkdir iso + ..(at this point untar or setup base system) + # mkdir -p iso/boot/grub + # cp iso9660fs.static iso/hurd + # cp stage2_eltorito iso/boot/grub + ..(edit iso/boot/grub/grub.conf) + # mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot \ + -boot-load-size 4 -boot-info-table -o livecd.iso iso/ + +**_Note:_** The following files must **\_NOT\_** be symlinks! + +* `/boot/gnumach` +* `/hurd/iso9660fs.static` +* `/hurd/exec` +* `/lib/ld.so.1` + +## Contents of grub.conf + + timeout 60 + default 0 + + title GNU/Hurd CD + #uppermem 523648 #this may need to be set + #root (cd) + kernel /boot/gnumach root=device:hd2 #set device to your cdrom device + module /hurd/iso9660fs.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) + +**_Note:_** The `root (cd)` line may prevent some computers from booting the livecd. + +-- [[Main/AndrewResch]] - 22 Feb 2005 diff --git a/unsorted/BuildingOskitMach.mdwn b/unsorted/BuildingOskitMach.mdwn new file mode 100644 index 00000000..334b0669 --- /dev/null +++ b/unsorted/BuildingOskitMach.mdwn @@ -0,0 +1,190 @@ +## HowTo Build OSKit-Mach + + + + + + +

%TOC%

Introduction

This is a brief "HowTO build OSKit-Mach" (a.k.a GNUmach 2.0). It covers everything from getting the latest sources of both the OSKit and the GNUmach kernel, down to building and debugging them.

+ +## Getting your hands on the source + +First you need to checkout the relevant sources. It comes in various flavours and the recommended way is to checkout from CVS. + +### The OSKit Sources + +**_Note:_** The [Savannah OSKit](http://savannah.gnu.org/projects/oskit/) project is the recommended source today of the OSKit. Its CVS tree holds the official sources and all known patches, plus a few others. + +**_Official Sources:_** + +* St. Patricks day 2002 release: + +* Valentine's day 2001 release: + +**_Official Patches:_** + +* Download useful [[OskitPatches]] or on the nearest Debian FTP. + +**_Savannah CVS:_** + +The recommended document for accessing the Savannah OSKit CVS is + +The following command should get the sources for you: + + $ export CVS_RSH="ssh" + $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/oskit co oskit + +Note: if you get a message about RSA/DSA keys, please go check it here: + +### GNUmach & Mig Sources + +The recommended document for accessing the Hurd CVS on Savannah is at + +Remember to set up you environment to use 'ssh' for cvs: + + $ export CVS_RSH="ssh" + +Note: if you get a message about RSA/DSA keys when using cvs commands, please go check it here: + +**_Gnu Mach:_** + +All development, apart from critical bug fixes, is done on the upcoming 2.0 release (OSKit/Mach). A potentially confusing point is that the code for OSKit/Mach (as opposed to the 1.X release, aka "GNU Mach") is now on the `TRUNK` of the 'gnumach' CVS module. In the past the trunk was 1.X (GNU Mach) and 2.0 (OSKit/Mach) was a branch. + + $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co gnumach + +In case you have been tracking the oskit-branch and want to move to the current `HEAD` branch you can issue the following instead to update your tree. + + $ cd + $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd update -Pd -A + +Where `` can be `gnumach`, `oskit-mach`, or similar. The `-A` is what moves you from a branch to the default (in this case HEAD), but without forcing a specific tag. `-P` Prunes your local copy from stale directories and `-d` creates new directories for you. + +**_The Hurd servers:_** + +In case you want to build the Hurd servers as well, you can check them out with: + + $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co hurd + +**_Inteface generator:_** + +See the [[microkernel/mach/MIG]] for more information. + +Check it out using + + $ cvs -z3 -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/hurd co mig + +## Building + +The recommended versions of GCC are + +

For the OSKit: GCC 2.95.X
For GNUmach and MiG: GCC 3.2

+ +### The OSKit + +Do _not_ forget to apply all known [[OskitPatches]] before starting the build! This does not apply if you use the OSKit from [Savannah](http://savannah.gnu.org/). + +The attached [[ATTACHURLmodulesx86pc]], or [[ATTACHURLmodules-lightx86pc]], is an example setup, your needs may vary but this one works for standard COTS PC's. Now, how to configure and build the OSKit. + + $ cd oskit-20020317/ + $ mkdir build + $ cd build + $ CC=gcc-2.95 \ + CFLAGS="-g" \ + ../configure --prefix=/usr/local \ + --enable-debug \ + --enable-modulefile=modules-light.x86.pc + $ make + $ sudo make install + +Comment: Barry deFreese + +For you newbies like me, I had problems using `modules.x86.pc.full` and `modules.x86.pc`. There seems to be problems with `examples/dyntest`. Make sure you pull down and use the [[ATTACHURLmodules-lightx86pc]]. + +Comment: Luis Miguel + +I needed to apply another patch that is not in CVS yet. The patch is in this [message](http://mail.gnu.org/archive/html/bug-hurd/2003-06/msg00054.html) in the bug-hurd mailing list. + +### Mach Interface Generator + +To build any Mach kernel you need an interface generator, MiG. To be on the safe side, use the CVS version. If you use Debian, you can install package [mig-i386-gnu](http://packages.debian.org/mig-i386-gnu). If you don't use Debian or want to compile MiG by yourself on Linux/\*BSD system, you must first install Mach headers. In Mach directory do: + + $ mkdir build + $ cd build + $ ../configure --prefix=/usr/local # Default prefix is / ! + $ sudo make -k install-headers # -k is for ignoring errors + +Now you are ready to compile and install MiG (commands are in Mig's source directory): + + $ automake --add-missing # sometimes it's needed + $ mkdir build + $ cd build + $ ../configure + $ make + $ sudo make install + +### GNUmach 2.0 (OSKit-Mach) + +Unlike its half sister, the OSKit-Mach kernel does _not_ need a cross compiler. The regular gcc for your x86 Linux system does just fine. However, you might want to use gcc 3.2 with the latest and greatest CVS version of Mach. + +**_Configuring:_** + + $ cd gnumach + $ mkdir build + $ cd build + $ MIG=/usr/local/bin/mig \ + CC=gcc-3.2 \ + CFLAGS="-g -O2" \ + OSKIT_LIBDIR=/usr/local/lib/oskit \ + ../configure --prefix=/gnu + +Comment: Barry deFreese + +I updated `CFLAGS` to `CFLAGS="-g -O2"`. Using just `-O` I was getting errors in the `machine_init` function. For newbies like me, the `-g` is only needed if you want to enable debugging. The `-O2` is Oh 2, not Zero 2. + +**_Building:_** + +Instead of using `make kernel` to build kernel, in OSKit-Mach you have to use make kernel-DRIVERS, where DRIVERS is DRIVER+DRIVER+...+DRIVER (a list of drivers separated by `+`). DRIVER can be one of: + +* `ide` +* `floppy` +* ethernet\_ETHDRV where ETHDRV is taken from `oskit/oskit/dev/linux_ethernet.h`. +* scsi\_SCSIDRV where SCSIDRV is taken from `oskit/oskit/dev/linux_scsi.h`. + +Thus, to build a IDE capable kernel with 3Com Vortex Boomerang support you use the following: + + $ make kernel-ide+ethernet_vortex + $ sudo make install + $ sudo gzip -f /gnu/boot/oskit-mach + +If the `make` command complains about missing dependencies, then you haven't passed correct `OSKIT_LIBDIR` variable to the `configure` script. Or you can use the patch below and pass something like `--with-oskit=/usr/local` to `configure`. + +Comment: Barry deFreese + +If you receive an error like `No rule to make target Kernel-ide...`, there is a patch for an issue with finding the oskit libraries. Then run `configure` on gnumach again with the option `--with-oskit=/path/to/oskit/libraries`. + +The patch can be found here: [gnumach-oskit-path.patch](http://www.vis.ethz.ch/~wagi/hurd/gnumach/gnumach-oskit-path.patch) Thanks wagi!! + +Don't use both `--with-oskit` and `OSKIT_LIBDIR`. Choose one of these methods. + +If you want to use tftp to download the kernel from Grub and don't care about the symbols I recommend either stripping or removing the `--enable-debug` and `-g` statements. + +## Debugging + +See the [[Mach/RemoteDebugOskitMach]] page. + +## Attachments + +* [[ATTACHURLmodulesx86pc]]: Configures modules to build in OSKit. +> Compared to 21May04 CVS, this adds SMP but omits the random module which was added to CVS in Jan03. + +* [[ATTACHURLmodules-lightx86pc]]: Lighter version of required modules. Used for building GNUmach with OSKit, i.e. OSKit/Mach. +> Compared to the above config, this omits the Linux, MSDOS, +> +> NetBoot, and PXE loader support, bootp support, OSKit on UNIX support, some thread-safe library versions, the address map manager, fsread, fsnamespace/\{fsn,fsn\_r\}, fudp, memdebug, memfs, smp, POSIX threads, svm, uvm, the Simple Process Library, realtime support, FreeBSD devices and code, linux/fs, the UDP library, **the sets of x86 and UNIX example kernels**, the testsuite, and the security server. **The new random module is also not configured.** diff --git a/unsorted/BuildingOskitMach/modules-light.x86.pc b/unsorted/BuildingOskitMach/modules-light.x86.pc new file mode 100644 index 00000000..07818cc5 --- /dev/null +++ b/unsorted/BuildingOskitMach/modules-light.x86.pc @@ -0,0 +1,236 @@ +## +## OSKit Module configuration file. +## +## Comments are ignored, non-commented words should be +## OSKit directories to include in the build. +## +## Libraries are built in the order defined in this +## file. +## +## Specify this file with the --with-modulesfile= +## option to configure. By default the file 'modules' +## in the OSKit source directory is used. +## + +### Always include this module (the header files) +oskit + +### The flask module must be compiled before +### most of the other modules. +### It is currently a required module. +flask + +### Builds the documentation (Utah only) +#doc + + +### --- Required components + +### The C Runtime (the magic that calls 'main') (required) +crt + +knit/c + +### Various bits of kernel magic (required) +kern + +### List Memory Manager (required) +lmm + +### The Client OS library (required) +clientos + + +### --- Boot Adaptors + +### Build the multiboot compliant boot adaptor +### Requires that ld support '-format binary' (checked) +boot/multiboot + +### Build the Linux boot adaptor +### Requires ld support '-oformat binary' (checked) +#boot/linux + +### Build the MSDOS boot adaptor (??) +## Requires ld support '-oformat msdos' (checked) +#boot/dos + +### Build the BSD boot adaptor +### Requires some sort of a.out linker (checked) +#boot/bsd + +### The NetBoot Meta-kernel +#boot/net + +### Build the PXE compliant boot loader +#boot/pxe + +### --- OSKit-on-UNIX support libraries. +#unix + +### --- C Libraries + +### A minimal standard C library +libc + +### A much more complete standard C library +posix/sys + +### Thread-safe version of the previous +#posix/sys_r + + +### --- Miscellaneous utility libraries + +### Address Map Manager +#amm + +### Library for contacting a bootp server +#bootp + +### Com IIDs library (required for most kernels) +com + +### For groking disk partitions +diskpart + +### Include the Dynamic Packet Filter library +#dpf/dpf + +### Exec library for loading linked executables +exec + +### Read-only access to a number of filesystems +#fsread + +### Filesystem name parsing library +#fsnamespace/fsn + +### Same as above, but multithread safe +#fsnamespace/fsn_r + +### Fake UDP library (Only supports UDP send) +#fudp + +### Include the Hierarchical Packet Fair Queueing module +#hpfq + +### The Memdebug library +#memdebug + +### The memory file system +#memfs + +### SMP support (believed to be broken) +#smp +## the SMP example +#examples/x86/smp ### requires smp + +### POSIX threads +#threads + +### Simple Virtual Memory +#svm + +### UVM +#uvm/uvm + +### Simple Process Library +#uvm/sproc +### the sproc example +#examples/x86/sproc ### requires sproc + +### --- Startup Library + +### Simpler functions for initializing OSKit subsystems +### NOTE: this drags in almost every other library. +#startup + + +### --- Devices, Networks and Filesystems + +### The device layer glue. Depends on lmm and kern +### Required for any kernel that uses OSKit devices. +dev + +### Realtime support. Needed for realtime threads and for GPROF. +#realtime + +### Devices and code stolen from FreeBSD +#freebsd/dev +#freebsd/net_flask +#freebsd/net +#freebsd/libm +#freebsd/libc +#freebsd/libc_r + +### Include Run-time linker support. This must come after freebsd build +#rtld +## The rltd example +#examples/dyntest ### requires rtld + +### Stuff stolen from Linux +linux/dev +#linux/fs + +### Stuff stolen from NetBSD +#netbsd/fs + +### SVGA video library +#video/svgalib +### SVGA-related examples +#examples/x86/video_svga ### requires video/svgalib + +### X11 video library +#x11/client +#x11/video +### X11-related examples +#examples/x86/video_x11 ### requires x11/video + +### The zlib compression library +#zlib + +### The UDP library. More complete than fudp, but not totally complete. +#udp + +### The Utah testbed TMCP communication library and examples +#tmcp +#examples/tmcp + +### The NetDisk kernel. +## Requires the zlib compression library. +## Requires the udp library. +#netdisk + +### --- Scripts and build/debug utilities + +### Includes the CPU-oskit-gcc wrapper. +unsupported + + +### --- Additional stuff that must be at or near the end of the build + + +### Sets of example kernels +#examples/x86 +#examples/x86/extended +#examples/x86/threads + +### Building the example kernels as host-build binaries with unix-mode +### emulation. NOTE: These will only be built if you are compiling +### the OSKit with unixmode support (and on Linux or FreeBSD). +#examples/unix +#examples/unix/extended +#examples/unix/threads + +### The OSKit test infrastructure +#testsuite + +### The security server +#security +## security server example kernel +#examples/x86/security ### requires security + +### The Mad MPEG audio decoder library and example +#libmad +#libmad/minimad diff --git a/unsorted/BuildingOskitMach/modules.x86.pc b/unsorted/BuildingOskitMach/modules.x86.pc new file mode 100644 index 00000000..bb27aca3 --- /dev/null +++ b/unsorted/BuildingOskitMach/modules.x86.pc @@ -0,0 +1,236 @@ +## +## OSKit Module configuration file. +## +## Comments are ignored, non-commented words should be +## OSKit directories to include in the build. +## +## Libraries are built in the order defined in this +## file. +## +## Specify this file with the --with-modulesfile= +## option to configure. By default the file 'modules' +## in the OSKit source directory is used. +## + +### Always include this module (the header files) +oskit + +### The flask module must be compiled before +### most of the other modules. +### It is currently a required module. +flask + +### Builds the documentation (Utah only) +#doc + + +### --- Required components + +### The C Runtime (the magic that calls 'main') (required) +crt + +knit/c + +### Various bits of kernel magic (required) +kern + +### List Memory Manager (required) +lmm + +### The Client OS library (required) +clientos + + +### --- Boot Adaptors + +### Build the multiboot compliant boot adaptor +### Requires that ld support '-format binary' (checked) +boot/multiboot + +### Build the Linux boot adaptor +### Requires ld support '-oformat binary' (checked) +boot/linux + +### Build the MSDOS boot adaptor (??) +## Requires ld support '-oformat msdos' (checked) +#boot/dos + +### Build the BSD boot adaptor +### Requires some sort of a.out linker (checked) +#boot/bsd + +### The NetBoot Meta-kernel +boot/net + +### Build the PXE compliant boot loader +#boot/pxe + +### --- OSKit-on-UNIX support libraries. +unix + +### --- C Libraries + +### A minimal standard C library +libc + +### A much more complete standard C library +posix/sys + +### Thread-safe version of the previous +posix/sys_r + + +### --- Miscellaneous utility libraries + +### Address Map Manager +amm + +### Library for contacting a bootp server +bootp + +### Com IIDs library (required for most kernels) +com + +### For groking disk partitions +diskpart + +### Include the Dynamic Packet Filter library +#dpf/dpf + +### Exec library for loading linked executables +exec + +### Read-only access to a number of filesystems +fsread + +### Filesystem name parsing library +fsnamespace/fsn + +### Same as above, but multithread safe +fsnamespace/fsn_r + +### Fake UDP library (Only supports UDP send) +fudp + +### Include the Hierarchical Packet Fair Queueing module +#hpfq + +### The Memdebug library +memdebug + +### The memory file system +memfs + +### SMP support (believed to be broken) +smp +## the SMP example +examples/x86/smp ### requires smp + +### POSIX threads +threads + +### Simple Virtual Memory +svm + +### UVM +uvm/uvm + +### Simple Process Library +uvm/sproc +### the sproc example +examples/x86/sproc ### requires sproc + +### --- Startup Library + +### Simpler functions for initializing OSKit subsystems +### NOTE: this drags in almost every other library. +startup + + +### --- Devices, Networks and Filesystems + +### The device layer glue. Depends on lmm and kern +### Required for any kernel that uses OSKit devices. +dev + +### Realtime support. Needed for realtime threads and for GPROF. +realtime + +### Devices and code stolen from FreeBSD +freebsd/dev +#freebsd/net_flask +freebsd/net +freebsd/libm +freebsd/libc +freebsd/libc_r + +### Include Run-time linker support. This must come after freebsd build +#rtld +## The rltd example +#examples/dyntest ### requires rtld + +### Stuff stolen from Linux +linux/dev +linux/fs + +### Stuff stolen from NetBSD +netbsd/fs + +### SVGA video library +#video/svgalib +### SVGA-related examples +#examples/x86/video_svga ### requires video/svgalib + +### X11 video library +#x11/client +#x11/video +### X11-related examples +#examples/x86/video_x11 ### requires x11/video + +### The zlib compression library +#zlib + +### The UDP library. More complete than fudp, but not totally complete. +udp + +### The Utah testbed TMCP communication library and examples +#tmcp +#examples/tmcp + +### The NetDisk kernel. +## Requires the zlib compression library. +## Requires the udp library. +#netdisk + +### --- Scripts and build/debug utilities + +### Includes the CPU-oskit-gcc wrapper. +unsupported + + +### --- Additional stuff that must be at or near the end of the build + + +### Sets of example kernels +examples/x86 +examples/x86/extended +examples/x86/threads + +### Building the example kernels as host-build binaries with unix-mode +### emulation. NOTE: These will only be built if you are compiling +### the OSKit with unixmode support (and on Linux or FreeBSD). +examples/unix +examples/unix/extended +examples/unix/threads + +### The OSKit test infrastructure +testsuite + +### The security server +security +## security server example kernel +examples/x86/security ### requires security + +### The Mad MPEG audio decoder library and example +#libmad +#libmad/minimad diff --git a/unsorted/CrossHurd.mdwn b/unsorted/CrossHurd.mdwn new file mode 100644 index 00000000..d33d2a00 --- /dev/null +++ b/unsorted/CrossHurd.mdwn @@ -0,0 +1,99 @@ +This will eventually become an installation guide for the Debian crosshurd package (GNU/Hurd cross install only). However, for the time being I am setting it up as a diet version of Hurd/InstalNotes, adapted for crosshurd, adapted for me. + +-- [[Main/JoachimNilsson]] - 14 Mar 2004 + +## Reserving partitions + +You need a swap and root partition, much like any other UNIX system. Two things to remember: + +1. Root partition still <2.0 GiB +2. Root partition: mke2fs -o hurd -b 4096 -L Carlsberg + +From a Debian GNU/Linux installation preparing install of GNU/Hurd on /dev/hdb2 reusing the Linux swap on /dev/hdb4. + + # mke2fs -o hurd -b 4096 -L Carlsberg /dev/hdb2 + +

+ "Carlsberg. Probably the best beer in the world." +

+ +## Bootstrapping + +After having installed the Debian crosshurd package you need to mount your newly created Hurd partition. + + mkdir /gnu + mount /dev/hdb2 /gnu + +Now, simply run the crosshurd program and follow the onscreen directions. **Do** select the usr symlink. + + crosshurd + +crosshurd burps a lot of unneeded information on screen and probably fails to install one or two files due to duplicates between GNU and Debian packages. Lets hope this mess is worked out some day. + +## Rebooting + +Before we reboot you must setup a Hurd entry in the menu.lst file of Grub. Do it like this and remember, **no trailing spaces**! + +The first two runs (reboots) you must run the Hurd in single-user mode! + + title GNU (kernel GNUmach 1.3) + root (hd1,1) + kernel /boot/gnumach.gz root=device:hd1s2 -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) + +The notation of Grub, and of the Hurd, can be somewhat bisarre on first sight. Consult the [[InstallNotes]] document and the Grub manual for a thorough explanation. + +N.B. the '-s' on the kernel line, it is "single user mode", which you need for the first two reboots. + +OK, reboot now. + +## First steps + +Set TERM variable and run native-install script. + + export TERM=mach + ./native-install + +At the end native-install wants you to reboot and run it again. Do so and remember to set the TERM variable as well. + +After the second reboot and native-install run you can remove the '-s' in the kernel line above and boot GNU/Hurd as a normal user. + +## Logging in + +Finally, a complete bootstrapped GNU system. + + login root + + export TERM=mach + + nano /etc/fstab + [add swap partition /dev/hd1s4] + + nano /etc/ttys + [remove all hashes to enable the new Hurd Console] + + settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0 + + dselect + +Now, do the old Debian thing of dancing with dselect for a couple of hours. + +Reboot and start the new [[Console]] + + login root + + console -d vga -d pc_kbd -d generic_speaker /dev/vcs + +Move around just like in Linux console, but with persistent scroll-back buffers for each console. + +## References + +* [[InstallNotes]] +* [[Network]] +* [[Console]] diff --git a/unsorted/CrossPlatformAliases.mdwn b/unsorted/CrossPlatformAliases.mdwn new file mode 100644 index 00000000..06a0e897 --- /dev/null +++ b/unsorted/CrossPlatformAliases.mdwn @@ -0,0 +1,8 @@ + # Aliases assume Debian GNU/Hurd mounted on /misc/hurd + # possibly via autofs /etc/auto.misc configuration and 'cd / && ln -s var/autofs/misc misc' + alias locatehurd="locate -d /misc/hurd/var/lib/locate/locatedb" + alias apt-cachehurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-cache" + alias apt-gethurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-get" + # dselect requires APT_CONFIG due to dselect apt method + alias dselecthurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline dselect --admindir /misc/hurd/var/lib/dpkg/" + alias dpkghurd="dpkg --root=/misc/hurd"= diff --git a/unsorted/DebianX.mdwn b/unsorted/DebianX.mdwn new file mode 100644 index 00000000..00692ca8 --- /dev/null +++ b/unsorted/DebianX.mdwn @@ -0,0 +1,130 @@ +# Setting up X on Debian GNU/Hurd + +#### Table Of Contents + +%TOC% + +This is a brief helper on how to setup X-Windows on Debian GNU/Hurd. + +Obviously this text is taken from the page but I was making such drastic changes, I didn't want to hack up that page. + +### Mouse & Keyboard + +See [[console]] for more details. + +You should instruct the Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: + + # console -d vga -d pc_kbd --repeat=kbd \ + -d pc_mouse --repeat=mouse --protocol=ps/2 -c /dev/cons /dev/vcs + +Symbolic links to repeaters should also be created: + + # ln -s /dev/cons/kbd /dev/kbd + # ln -s /dev/cons/mouse /dev/mouse + +### Selecting & Configuring Packages + +You will need several X packages. The `x-window-system-core` brings you most of what you need: + +* `xserver-xfree86` +* `xfonts-base` +* `xfonts-100dpi` +* `xfonts-75dpi` +* `xfonts-scalable` +* `xbase-clients` +* `xutils` +* `rxvt` +* ... as well as your window manager of choice: + * WindowMaker, `wmaker` + * FVWM, `fvwm` + * Blackbox, `blackbox` + * TWM, `twm` + +I know that twm and Window Maker work, however, I cannot attest to the other two. Also, Michael Banck has a working package for xfce4 for those of you that are interested. The link for the package is here: + + deb http://people.debian.org/~mbanck/hurd-xfce4/ ./ + +Thanks for that Michael!! + +You will probably need to create a .xsession file for xfce4 with the following command: + + exec /usr/bin/startxfce4 || exec xterm + +This will start the xfce4 desktop or dump to xterm if it fails to start. + +The recommended way of configuring X is using the `xserver-xfree86` debconf template, eg: + + # dpkg-reconfigure xserver-xfree86 + +It may be easier to just copy a working configuration from another operating system on the same computer and place it in `/etc/X11/XF86Config-4`, but this is discouraged as you would have to remove some sections by hand. + +**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. + +**_UPDATE 12/28/2004:_** Speedo is working on mine and is currently running. I do not have DRI enabled however. + +### Edit XF86Config-4 + +Now you have to edit the file manually to ensure that the mouse sections look like this: + + Section "InputDevice" + Identifier "Configured Mouse" + Driver "mouse" + Option "CorePointer" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + + Section "InputDevice" + Identifier "Generic Mouse" + Driver "mouse" + Option "SendCoreEvents" "true" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + +You may also enable the Emulate3Buttons option, but nothing else will work. + + Option "Emulate3Buttons" "true" + +**_WARNING:_** I cannot verify as of yet whether it was the "Emulate3Buttons" setting or the "ZAxisMapping" setting but I had to disable both in order to be able to move and resize windows. + +### Dynamic Linking + +The Hurd does not use `ld.so.conf`, it is necessary to add the following to `/etc/profile` to be sure that the libraries are found: + + LD_LIBRARY_PATH=/X11R6/lib:$LD_LIBRARY_PATH + +"This is a linker issue. GNU/Hurd expects that \`RPATH' is used, however, Debian takes certain measures to avoid this. Note that this does not cut it for suid binaries because of security implications. We expect to rectify this by using \`RUNPATH', which is specified in the new ELF standard." -- [Why does X not work?](http://www.gnu.org/software/hurd/faq.en.html#q4-8) + +**_CAVEAT 12/28/2004:_** I did not have to do this so can someone verify that this still needs to be done or was it fixed? Thanks! + +### Starting X + +Finally, run `startx` + +However, there are several caveats to be aware of: + +* `xterm` does not work correctly; try `rxvt`. + +**_UPDATE 12/28/2004_**: xterm works fine for me. + +* `update-menu` does not yet work. As such, there are no fine Debian menus. +* GNOME can now be ported with the new pthreads, but is still being worked on. Window Maker, TWM, Blackbox and FVWM all work. + +**_WARNING:_** If you get an error about opening the display or a permissions issue, you may need to run the following: + + # dpkg-reconfigure xserver-common + +change from "Console Users Only" to "Anybody" + +### Miscellaneous + +The dillo web browser does work, though it is not the greatest browser. + +For you xchat lovers like me, xchat will compile if you disable the python module. (The python module causes an assertion failure in pthreads if one of you guru's wants to fix and package. **hint,hint**) + +Good luck and enjoy! + +---- + +-- [[Main/BarryDeFreese]] - 28 Dec 2004 diff --git a/unsorted/DebianXorg.mdwn b/unsorted/DebianXorg.mdwn new file mode 100644 index 00000000..1599c689 --- /dev/null +++ b/unsorted/DebianXorg.mdwn @@ -0,0 +1,197 @@ +# Setting up Xorg on Debian GNU/Hurd + +#### Table Of Contents + +%TOC% + +This is a brief helper on how to setup Xorg on Debian GNU/Hurd. + +Obviously this text is taken from the page but I was making such drastic changes, I didn't want to hack up that page. + +### Mouse & Keyboard + +See [[console]] for more details. + +You should instruct the Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: + + # console -d vga -d pc_kbd --repeat=kbd -d generic_speaker \ + -d pc_mouse --repeat=mouse --protocol=ps/2 -c /dev/vcs + +Symbolic links to repeaters should also be created: + + # ln -s /dev/cons/kbd /dev/kbd + # ln -s /dev/cons/mouse /dev/mouse + +### Selecting & Configuring Packages + +The `x-window-system-core` package brings you most of what you need for a base, plus you need to choose a window manager: + +* WindowMaker, `wmaker` +* FVWM, `fvwm` +* Blackbox, `blackbox` +* TWM, `twm` + +I know that Window Maker works, however, I cannot attest to the others. xfce4 might be temporarily broken. + +The recommended way of configuring X is using the `xserver-xorg` debconf template, eg: + + # dpkg-reconfigure xserver-xorg + +This currently seems to be broken in the Debian package so it may be easier to just copy a working configuration from another operating system on the same computer and place it in `/etc/X11/xorg.conf`. You need to edit the mouse settings by hand according to the below example, though. + +**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. + +**BDd: I cannot attest to this currently.** + +### Edit xorg.conf + +If you managed to get an xorg.conf autogenerated, make sure to have the mouse section read as follows: + + Section "InputDevice" + Identifier "Configured Mouse" + Driver "mouse" + Option "CorePointer" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + +Do not set the "Emulate3Button" or "ZAxisMapping" options, they do not work and break things. + +Here is an example of an xorg.conf using VESA at 800x600 that works on my Dell laptop: + + # /etc/X11/xorg.conf (xorg X Window System server configuration file) + # + # This file was generated by dexconf, the Debian X Configuration tool, using + # values from the debconf database. + # + # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. + # (Type "man /etc/X11/xorg.conf" at the shell prompt.) + # + # This file is automatically updated on xserver-xorg package upgrades *only* + # if it has not been modified since the last upgrade of the xserver-xorg + # package. + # + # If you have edited this file but would like it to be automatically updated + # again, run the following command: + # sudo dpkg-reconfigure -phigh xserver-xorg + + Section "Files" + FontPath "/usr/share/X11/fonts/misc" + FontPath "/usr/share/X11/fonts/cyrillic" + FontPath "/usr/share/X11/fonts/100dpi/:unscaled" + FontPath "/usr/share/X11/fonts/75dpi/:unscaled" + FontPath "/usr/share/X11/fonts/Type1" + FontPath "/usr/share/X11/fonts/CID" + FontPath "/usr/share/X11/fonts/100dpi" + FontPath "/usr/share/X11/fonts/75dpi" + # paths to defoma fonts + FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" + FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID" + EndSection + + Section "Module" + Load "GLcore" + Load "i2c" + Load "bitmap" + Load "ddc" + Load "extmod" + Load "freetype" + Load "glx" + Load "int10" + Load "type1" + Load "vbe" + EndSection + + Section "InputDevice" + Identifier "Generic Keyboard" + Driver "kbd" + Option "CoreKeyboard" + Option "XkbRules" "xorg" + Option "XkbModel" "pc104" + Option "XkbLayout" "us" + EndSection + + Section "InputDevice" + Identifier "Configured Mouse" + Driver "mouse" + Option "CorePointer" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + + Section "InputDevice" + Identifier "Synaptics Touchpad" + Driver "synaptics" + Option "SendCoreEvents" "true" + Option "Device" "/dev/psaux" + Option "Protocol" "auto-dev" + Option "HorizScrollDelta" "0" + EndSection + + Section "Device" + Identifier "Videocard0" + Driver "vesa" + EndSection + + Section "Monitor" + Identifier "Monitor0" + VendorName "Dell" + HorizSync 31.5 - 90.0 + VertRefresh 59.0 - 85.0 + Option "DPMS" + EndSection + + Section "Screen" + Identifier "Screen0" + Device "Videocard0" + Monitor "Monitor0" + DefaultDepth 24 + SubSection "Display" + Depth 1 + Modes "800x600" + EndSubSection + SubSection "Display" + Depth 4 + Modes "800x600" + EndSubSection + SubSection "Display" + Depth 8 + Modes "800x600" + EndSubSection + SubSection "Display" + Depth 15 + Modes "800x600" + EndSubSection + SubSection "Display" + Depth 16 + Modes "800x600" + EndSubSection + SubSection "Display" + Depth 24 + Modes "800x600" + EndSubSection + EndSection + + Section "DRI" + Mode 0666 + EndSection + +### Starting X + +Finally, run `startx` + +However, there are several caveats to be aware of: + +* `update-menu` does not yet work. As such, there are no fine Debian menus. + +**_WARNING:_** If you get an error about opening the display or a permissions issue, you may need to run the following: + + # dpkg-reconfigure x11-common + +change from "Console Users Only" to "Anybody" + +Good luck and enjoy! + +---- + +-- [[Main/BarryDeFreese]] - 02 Mar 2006 diff --git a/unsorted/DhcpClient.mdwn b/unsorted/DhcpClient.mdwn new file mode 100644 index 00000000..442f4781 --- /dev/null +++ b/unsorted/DhcpClient.mdwn @@ -0,0 +1,42 @@ +# DHCP and the Hurd + +According to the following thread, no port should be needed since all the patches that have been applied, including the one concerning the thread. In fact, the thread finishes without concluding whether the patch has been applied or not. You can grab it in the thread, anyway. + +[Link to thread](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html) + +The thread starts at Jan 4th 2005 until Jan 6th and is only retaken at April 14th in [this thread](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html). + +-- [[Main/ThadeuCascardo]] - 29 Sep 2005 + +No DHCP client has been ported to the Hurd yet. + +[This](http://mail.gnu.org/archive/html/help-hurd/2003-10/msg00016.html) thread on help-hurd has a little more info on what's still needed for DHCP. + +-- [[Main/GregBuchholz]] - 09 Oct 2003 + +Found this [message](http://mail.gnu.org/archive/html/bug-hurd/2003-08/msg00045.html) about DHCP capabilities in the Hurd encouraging. + +-- [[Main/GregBuchholz]] - 03 Sep 2003 + +* Tom Hart began a [discussion ](http://mail.gnu.org/pipermail/help-hurd/2002-October/006643.html) of 14 posts in Oct 2002. + +-- [[Main/GrantBow]] - 20 Oct 2002 + +The beginnings of a DHCP translator is available in the Hurd sources on Savannah: [hurd/trans/pump.c](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd/trans/pump.c?rev=1.3&content-type=text/vnd.viewcvs-markup) + +Unfortunately our current TCP/IP stack, the pfinet translator, lacks support for the AF\_PACKET interface as well as sending packets with an IP address of 0.0.0.0. + +Grant Bowman on bug-hurd: + + Herbert Xu (Pump maintainer) told me that to operate correctly, pump + uses the AF_PACKET interface which is only present in 2.2. + + Anyone else know the status of getting these compiled and functional? + +Neal Walfield on bug-hurd replies: + + > Anyone else know the status of getting these compiled and functional? + + We need to be able to send to the DHCP server with ip address 0.0.0.0. + +-- [[Main/JoachimNilsson]] - 12 Nov 2002 diff --git a/unsorted/DistributedServers.mdwn b/unsorted/DistributedServers.mdwn new file mode 100644 index 00000000..cb2dd5bc --- /dev/null +++ b/unsorted/DistributedServers.mdwn @@ -0,0 +1,29 @@ +# Distributed Computing + +The [[Mach]] micro kernel was originally designed to run on symetric multi-processing (SMP) systems. Later, it was extended to allow for distributed OS support. A group of workstations with Mach can act as a single powerful SMP machine. Thus, Mach is also called a Single System Image (SSI). + +The Mach micro kernel provides a good infrastructure for distributed computing, including thread migration, inter-thread communition (both locally and remotely), load balancing and fault-tolerance. The Hurd, using Mach as a foundation, has great potential for distributed computing. Progress toward distributed kernel designs is proceeding within other projects as well. OpenMosix is a related projects for Linux kernels. You can reach it at: + +* +* +* + +OpenMosix patches specific Linux kernel versions to make them "distributed-enabled". However, since the Linux kernel is monolithic, patches must be updated with each new version of kernel. That can be extremely difficult due to the pace at which Linux kernels are currently developed. + +The Hurd architecture is better suited to distributed computing. Due to Hurd's server structure this is much more easily adapted. Efforts continue to evolve it's design not only on the Mach micro kernel but also work continues on a [[Mach/PortToL4]] micro kernel. + +---- + +## Document history + +Created. + +-- [[Main/LaudneyRen]] - 29 Sep 2002 + +Various grammatical fixes and tidying up. + +-- [[Main/JoachimNilsson]] - 29 Oct 2002 + +Updated for [[Mach]] web, reworded parts for more direct message. Added L4 link. + +-- [[Main/GrantBow]] - 11 Jan 2003 diff --git a/unsorted/ExtTwoSize.mdwn b/unsorted/ExtTwoSize.mdwn new file mode 100644 index 00000000..ec39781f --- /dev/null +++ b/unsorted/ExtTwoSize.mdwn @@ -0,0 +1,27 @@ +## Ext2 File system limitation + +This is a very common question. Many people have problems with the partition limit on Ext2 filesystems being very small by current standards. It feels smaller all the time as people have larger disks and often larger filesystems. It's worth mentioning that 64-bit machines (ia64, alpha) will not have this limitation. + +Note that, while the official CVS sources still suffer of this problem, recent (as of 2007) Debian GNU Hurd distributions **do not have this limit anymore**. Be happy. [July 2007 from debian-hurd](http://lists.debian.org/debian-hurd/2007/07/msg00087.html) + +* From the Hurd FAQ: [partition limit](http://www.gnu.org/software/hurd/faq.en.html#q2-6) + +**_Patch:_** + +[Release candidate 1](https://savannah.gnu.org/patch/?func=detailitem&item_id=2508) of the patch is uploaded in Savannah. + +**_Useful:_** + +Discussions on status and how to fix the problem: + +* [Febuary 2003](http://lists.debian.org/debian-hurd/2003/debian-hurd-200302/msg00016.html) +* [December 2002](http://mail.gnu.org/archive/html/bug-hurd/2002-12/msg00041.html) +* [March 2002 status](http://mail.gnu.org/archive/html/hurd-devel/2002-03/msg00030.html) and a [follow up](http://mail.gnu.org/archive/html/hurd-devel/2002-03/msg00035.html) +* [Nov 2001 status](http://mail.gnu.org/archive/html/hurd-devel/2001-11/msg00002.html) + +**_Maybe Useful:_** + +* (This link is broken. Have been unable to fix it. [[MauriceMcCarthy]] 2 Nov 2004.) +* + +(Searching Beowulf for '2Gb patch' seems to show this still present in the archive but somehow it is not accessible.) diff --git a/unsorted/ExtTwofsTranslator.mdwn b/unsorted/ExtTwofsTranslator.mdwn new file mode 100644 index 00000000..d8f708fc --- /dev/null +++ b/unsorted/ExtTwofsTranslator.mdwn @@ -0,0 +1,4 @@ +* [[ExtTwoSize]] - information about the limitation of partition size +* [[XattrHurd]] - Supports Hurd ext2 format extensions on Linux, images at + +-- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/unsorted/FlashHurd.mdwn b/unsorted/FlashHurd.mdwn new file mode 100644 index 00000000..a6288afc --- /dev/null +++ b/unsorted/FlashHurd.mdwn @@ -0,0 +1,60 @@ +# USB Flash Memory GNU/Hurd + +It would be nice if we had a bootable [USB flash drive](http://en.wikipedia.org/wiki/USB_key) Hurd like [[DamnSmallLinux]]. It would 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, a bootable Flash Hurd would enable us to have a native installer instead of relying on Linux. + +It could be installed in the USB using a [[hurd/running/Live_CD]] (using a script) - this is the Burned version - or directly downloading the iso files from the Internet - Unburned version -. One can use also [qemu] to run the [[hurd/running/Live_CD]] and them use the USB installation script. + +Here is an outline of the things that need to be done. Please add your comments and suggestions. + +## Requirements Outline + +### 1. We need to be able get a bootloader for USBs + +This is not much of a problem. I have already been successful (see below) in using [Grub](http://en.wikipedia.org/wiki/GRand%20Unified%20Bootloader) and the El-Torito HD emulation to boot [[GNUmach]] off a CD. There may be some minor tweaking of Grub code necessary to detect which device to use for booting (instead of having the user select their device (hd0,hd1,etc.) from the Grub menu). + +Using GRUB's stage2\_eltorito seems to work fine. + +### 2. We need a bootstrap filesystem translator + +This would be something like a statically linked iso9660fs translator. Compiling a statically linked iso9660fs translator is easy enough, though it doesn't boot. I don't currently know whether this is because the translator was never meant to be a bootstrap filesystem, or if there is a simple bug which has never been flushed out because the translator has never been used at boot time before. I've had trouble debugging this problem because I haven't yet figured out a way to use a remote gdb with gnumach. Theoretically you could use the "boot" command to overcome this problem, but "boot" for me mangles the terminal and exits in different manner than an actual boot. + +The iso9660fs translator works great, it just needs to be statically linked. + +### 3. We need a ramdisk to enable write access + +I think we could fake this with Farid Hajii's [memfs](http://www.fprintf.net/hurd/) translator and writing an ext2 filesystem to it. + +From the mem-fs README... + +> memfs-1 is a translator that provides a memory-based file of fixed size. This file can, just like bigfile, contain a regular filesystem. + +We could set a mem-fs translator anywhere on the CD you needed write access, including having softlinks to the contents of the root directory and chrooting to this new directory. + +For a quick and dirty memfs, you can do it right now with the following commands: + + # touch ./ramdisk + # touch ./tmpfs + # settrans -a ./ramdisk /hurd/storeio -Tcopy zero:50M + # /sbin/mke2fs -o hurd -b 4096 -F ./ramdisk + # settrans -a tmpfs /hurd/ext2fs.static ./ramdisk + # fsysopts --writable ./tmpfs + # cd tmpfs + # touch somenewfile + +Here we use two files ramdisk, and tmpfs that are already created on a readonly file system. For illustration purposes, they are touched beforehand. We run an active storeio translator on the ramdisk file to give us 50MB of RAM to work with, and then we make an ext2 filesystem on it. + +At this point we'd could copy the contents of the `/var` directory into the tmpfs, and then symlink `/var` to `/tmpfs/var`. The same goes for all other mutable dirs. + +This approach of putting an entire ext2 filesystem in a copy zero'd store has some drawbacks listed [here](http://lists.gnu.org/archive/html/bug-hurd/2000-12/msg00073.html). + +Those are the essentials. Here is a list of the things which would be nice to have for a USB Flash Memory. + +* Knoppix like script for starting up X and [[GraphicEnvironment]] s ([[FluxBox]], Gnome...) +* DHCP support for easy network setup +* Hardware autodetection (Kudzu). +* Knoppix like script for installing to the hard drive or to bootable USB pendrive . +* (add your favorite feature here) + +Here is a mailing-list [thread](http://lists.debian.org/debian-hurd/2003/debian-hurd-200308/msg00172.html) discussing some of these issues. + +-- [[Main/GregBuchholz]] - 21 Oct 2003 -- [[Main/NagromNamreh]] - 29 Jan 2004 diff --git a/unsorted/FtpfsTranslator.mdwn b/unsorted/FtpfsTranslator.mdwn new file mode 100644 index 00000000..528a10f2 --- /dev/null +++ b/unsorted/FtpfsTranslator.mdwn @@ -0,0 +1,7 @@ +ftpfs lets you access ftp servers via the filesystem. For detailed usage information use `/hurd/ftpfs --help` and `/hurd/ftpfs --usage`. + +### hostmux + +ftpfs ist best used with [[HostmuxTranslator]] + +-- [[Main/PatrickStrasser]] - 13 Jul 2004 diff --git a/unsorted/FunnyHurd.mdwn b/unsorted/FunnyHurd.mdwn new file mode 100644 index 00000000..1653ec77 --- /dev/null +++ b/unsorted/FunnyHurd.mdwn @@ -0,0 +1,39 @@ +## Fun stuff ripped from the Internet + + + + + + + + + + + + + + +

%ATTACHURL%/hurd-windows.gif Hurd Windows, availble from http://www.hurd.com	%ATTACHURL%/HurdExchange.gif Exchange your Hurd at http://www.thunderinghurd.com
%ATTACHURL%/HurdCarDeal.jpg ... and we can of course also offer you a great deal on this -91 Chevy! :-)	%ATTACHURL%/HurdLodge.jpg The many perks of being a Hurd user also includes our own ski lodge! Hurd House + + Knotty pine kitchen + Spacious kitchen & living room with loft + Leather couch and love seat with a TV & VCR + Outdoor Jacuzzi + Spacious master bedroom/bath upstairs + Twin beds in one room / queen bed in another + +
%ATTACHURL%/HurdMagician.jpg From http://www.magicposters.com/buy/h-k.html	%ATTACHURL%/CrystalAwards.jpg "Wow dude, I saw the Debian Swirl logo on last nights Crystal Awards!"

+ +---- + +These images and links are only here to serve as a comic relief to this site. It is **not** the intention to humiliate the people, corporations or organizations behind these factual sites. + +If your [company] name or organization is listed here and you do not approve you can remove yourself simply by clicking on the "Edit" button. In the login window that appears you enter _TWikiGuest_ as username and _guest_ as password. + +---- + +### Comments + +Created the page. + +-- [[Main/JoachimNilsson]] - 09 Nov 2002 diff --git a/unsorted/FunnyHurd/CrystalAwards.jpg b/unsorted/FunnyHurd/CrystalAwards.jpg new file mode 100644 index 00000000..2daac850 Binary files /dev/null and b/unsorted/FunnyHurd/CrystalAwards.jpg differ diff --git a/unsorted/FunnyHurd/HurdCarDeal.jpg b/unsorted/FunnyHurd/HurdCarDeal.jpg new file mode 100644 index 00000000..9f533384 Binary files /dev/null and b/unsorted/FunnyHurd/HurdCarDeal.jpg differ diff --git a/unsorted/FunnyHurd/HurdExchange.gif b/unsorted/FunnyHurd/HurdExchange.gif new file mode 100644 index 00000000..bbbb4844 Binary files /dev/null and b/unsorted/FunnyHurd/HurdExchange.gif differ diff --git a/unsorted/FunnyHurd/HurdLodge.jpg b/unsorted/FunnyHurd/HurdLodge.jpg new file mode 100644 index 00000000..d13562f5 Binary files /dev/null and b/unsorted/FunnyHurd/HurdLodge.jpg differ diff --git a/unsorted/FunnyHurd/HurdMagician.jpg b/unsorted/FunnyHurd/HurdMagician.jpg new file mode 100644 index 00000000..5ef6509a Binary files /dev/null and b/unsorted/FunnyHurd/HurdMagician.jpg differ diff --git a/unsorted/FunnyHurd/hurd-windows.gif b/unsorted/FunnyHurd/hurd-windows.gif new file mode 100644 index 00000000..5ca7dd74 Binary files /dev/null and b/unsorted/FunnyHurd/hurd-windows.gif differ diff --git a/unsorted/GNOME.mdwn b/unsorted/GNOME.mdwn new file mode 100644 index 00000000..1dbef091 --- /dev/null +++ b/unsorted/GNOME.mdwn @@ -0,0 +1,11 @@ +![gnome-hurd.png](http://people.debian.org/~mbanck/media/gnome-hurd.png) + +GNOME can now be ported with the new [[Pthreads]], but is still being worked on.The packages are at + +deb ./ + +The caveats: + +Some applications are not yet built, not even all the ones from gnome-core. 'apt-get install gnome-applets gnome-control-center gnome-icon-theme gnome-panel gnome-session metacity nautilus scrollkeeper' (along with the above APT source) should get you started. + +See also: [[Xfree86]]. diff --git a/unsorted/GNUstep.mdwn b/unsorted/GNUstep.mdwn new file mode 100644 index 00000000..95b2a622 --- /dev/null +++ b/unsorted/GNUstep.mdwn @@ -0,0 +1,64 @@ +# Setting up GNUstep on the Hurd + +GNUstep is not available on the Debian distribution for GNU/Hurd, but it can be built manually. This is, how to do it. + +#### Prerequisites + +This packages should already be installed (Debian package names in brackets): ffcall (libffcall1, libffcall1-dev), libffi (libffi4), libffi4-dev, openssl (openssl), libtiff (libtiff4), libpng (libpng12-0, libpng3), libjpg (libjpeg62), libxml (libxml1, libxml2, libxml2-dev & dependencies), xslt (libxslt1.1, libxslt1-dev & dependencies), ssl (libssl0.9.8, libssl-dev), libungif4-dev libungif4g, aspell (libaspell15, libaspell-dev, aspell & apspell-[for your language, e. g. en]) windowmaker (wmaker), Objective-C-Compiler (gobjc and depending packages) + +#### Getting the sources + +To do an up-to-date-installation, download the daily snapshot from GNUstep into one new directory and unzip/untar them: + + wget ftp://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2 + +#### Building GNUstep + +Everything needed for the GNUstep base system is included into the expanded tarball. This is how to build it: + +Do the following installation as root! + + cd core/make + ./configure + make && make install + cd .. + . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh (see the dot at the begin!) + cd ../base + ./configure + Edit the file Headers/Additions/GNUstepBase/config.h and add "#define BROKEN_SO_REUSEADDR 1" somewhere + make && make install + cd ../gui + ./configure + make && make install + cd ../back + make && make install + +Now, you've built the GNUstep base system. When you want to start a GNUstep application later or want to build one, open a bash shell and enter this command: + + . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh + +This sets some necessary environment variables. + +#### Building GNUstep apps + +You can find some GNUstep applications here: + +and here: [http://mediawiki.gnustep.org/index.php/Main\_Page](http://mediawiki.gnustep.org/index.php/Main_Page) + +#### Known problems + +##### GNUMail + +After starting GNUMail, you can only once get mails from a pop3-server. If you want to fetch mails again, you have to restart it. + +##### GWorkspace 0.8 + +GWorkspace 0.8 expects a /etc/mtab file. If you want to use it, you must manually make this file. + +Example for a /etc/mtab file: + + /dev/hd0s1 / ext2 rw 1 1 + +---- + +-- Thomas Schlesinger - 03 Mar 2006 diff --git a/unsorted/GrantBowHurdPage.mdwn b/unsorted/GrantBowHurdPage.mdwn new file mode 100644 index 00000000..89af3ada --- /dev/null +++ b/unsorted/GrantBowHurdPage.mdwn @@ -0,0 +1,36 @@ +Here are some notes on my current Hurd activity. + +I am also unable to get my PCI NE-2000 clone network card working. The driver loads but no routes are possible and therefore no packets get to the network. This is actually a DE-220 NIC that I started to discuss on hurd-help. Here's the actual change I made to gnumach-20020421/linux/dev/drivers/net/Space.c + + static struct device eth0_dev = { + "eth0", 0, 0, 0, 0, 0x240, 10, 0, 0, 0, ð1_dev, ethif_probe }; + +Cheers, + +-- [[Main/GrantBow]] - 13 May 2002 + +Booting OSKit-Mach mysteriously works now! Yeah! I didn't even change anything! + +My problems now is how to get my second machine's (hd0,2) (/dev/hda3 for linux folks) partitionto bre recognized by Grub. When I try 'root (hd0,2)' grub spits back 'Filesystem type unknown, partition type 0x83'. This is a standard ext2 /boot partition from my test Progeny install. I even removed the partition, added it back, fsck.ext2 and moved the files back. It still doesn't see the -filesystem-. Very strange. This prevents me from using my second machine right now. + +If anyone knows more about these items, please add your comments below with your signature. + +-- [[Main/GrantBow]] - 16 May 2002 + +PLEASE read these once. They are worth the effort. + +* [How To Ask Questions The Smart Way](http://www.tuxedo.org/~esr/faqs/smart-questions.html) + +* [How To Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) \* + +\*[Lincoln Portrait](http://www.people.virginia.edu/~skd9r/409/portrait.html) transcript - amazingly applicable to open source ideals. + +I am working on a page describing the [[Distrib/GNUDebianBuildProcess]]. + +I also created some very very rough images for use in explaining the Hurd and it's relationship with GNU Mach and Oskit Mach. + +-- [[Main/GrantBow]] - 30 May 2002 + +* [[ATTACHURLdiagramxcf]]: Diagram - Gimp file + +* Diagram - PNG file:
![diagram.png](%ATTACHURLPATH%/diagram.png) diff --git a/unsorted/GrantBowHurdPage/diagram.png b/unsorted/GrantBowHurdPage/diagram.png new file mode 100644 index 00000000..c8b29047 Binary files /dev/null and b/unsorted/GrantBowHurdPage/diagram.png differ diff --git a/unsorted/GrantBowHurdPage/diagram.xcf b/unsorted/GrantBowHurdPage/diagram.xcf new file mode 100644 index 00000000..76396410 Binary files /dev/null and b/unsorted/GrantBowHurdPage/diagram.xcf differ diff --git a/unsorted/HurdDevelopers.mdwn b/unsorted/HurdDevelopers.mdwn new file mode 100644 index 00000000..1a43a2b8 --- /dev/null +++ b/unsorted/HurdDevelopers.mdwn @@ -0,0 +1,120 @@ +Here's an unofficial list of Hurd developers and what they are working on. This is very unofficial. + +* [Marcus Brinkmann](http://www.marcus-brinkmann.de) - GNU Hurd Project maintainer, Debian GNU/Hurd Port Manager, fakeroot, oskit console +* [Thomas Bushnell, BSG](http://www.mit.edu/~tb/) - Primary architect, design issues and debugging help +* [Roland McGrath](http://www.frob.com), [resum�](http://www.apocalypse.org/pub/u/roland/resume.html) - GLibC, GCC-3.1, fakeroot (with fakeauth and settrans --chroot) +* Jeff Bailey - turtle autobuilder, gcc-3.1 +* [Igor Khavkine](http://alcor.concordia.ca/~i_khavki/) +* [Gordon Matzigkeit](http://www.fig.org/gord/) + +* Alexandra "[Bunny](http://www.hurd-bunny.tk)" - graphic designer, Hurd promotion +* Alfred M. Szmidt (ams) - +* Daniel (Chillywilly) Baumann - GNU Enterprise Application Server, GNU Common C++ +* [[Main/GrantBow]] - TWiki, promotion +* Jae - fatfs, possibly smbfs +* [[Main/JoachimNilsson]], [[Hurd/JoachimNilssonHurdPage]] - TWiki, OSKit upgrades (currently ATA-100 patches). +* [[Main/JamesAMorrison]] - porting, kernel interface cleanups, [hurd-extras](http://savannah.gnu.org/projects/hurdextras/) +* Neal Walfield - pthreads, documentation, debugging, #hurd admin, log & bot maintainer +* [[Main/NickRusnov]] - mtab & [[Distrib/PortingIssues]] +* Niels M�ller - kernel debugging +* [[Main/OgnyanKulev]] - [[ExtTwoSize]] patch +* Paul Emsley - [Kernel Cousin Debian Hurd](http://kt.zork.net/debian-hurd/latest.html) +* Philip Charles - [ISO CD-images](http://www.copyleft.co.nz/hurd.html) +* Ryan Golbeck - porting. +* [[Main/SamLauzon]] (Indes) - Installer, Sound(!), Bunny mocking +* [[Main/SimonLaw]] - [Kernel Cousin Debian Hurd](http://kt.zork.net/debian-hurd/latest.html) and [[Hurd/KernelCousinDebianHurd]] +* [[Main/WolfgangJ]] - documentation, promotion +* [[Main/DerekDavies]] - OSKit work +* [Daniel Wagner](http://www.vis.ethz.ch/~wagi/) (wagi) - [pcmcia support for OSKit](http://savannah.nongnu.org/projects/oskit/) + +If we got any names wrong, please accept our apologies. + + +--- + +

Acknowledgements

+ +

We wish a warm ``Thank GNU'' to everybody who has helped in the +development of the Hurd. Here is a categorized list of people who +made significant contributions. If we have omitted anybody, we +apologize... please let us know so that we can update this list! + +

Hurd software

Mark Kettenis: many GNU C library and Hurd bug fixes and updates
Miles Bader: paid by the FSF to help make the Hurd usable as a standalone system, + wrote several important translators
OKUJI Yoshinori: many gnumach bug fixes and updates
Roland McGrath: paid by the FSF to design and implement the GNU C library for the Hurd, + as well as many Hurd features, current Hurd C library maintainer
Thomas Bushnell, BSG (formerly Michael I. Bushnell): paid by the FSF as primary architect of the Hurd, current Hurd maintainer
UCHIYAMA Yasushi: ported XFree86 to the Hurd

Debian GNU/Hurd

Gordon Matzigkeit: paid by the FSF as a liason from GNU to Debian
Marcus Brinkmann: bootstrapped the Debian GNU/Hurd base set and many packages, liason + from Debian to GNU
Santiago Vila: support for cross-compiling Debian packages

Documentation

Derek Upham: wrote the original GNU Hurd FAQ
Gordon Matzigkeit: reorganized and updated the GNU Hurd Reference Manual for release 0.3 +
Matthew C. Vernon: wrote the ``Idiot's Guide'' for getting started with the Hurd
Matthias Pfisterer: reorganized and updated the web site in early 1999
Stephen L. Favor: current FAQ maintainer
Trent Fisher: wrote the original version of the Hurd pages

+ +Copyright (C) 1999, 2007 Free Software Foundation, Inc., +59 Temple Place - Suite 330, Boston, MA 02111, USA + +Verbatim copying and distribution of this entire article is +permitted in any medium, provided this notice is preserved. + +--- + +Thank GNU to everybody who has contributed to the Hurd's development! + +

kaz Kojima + ported the Hurd to the MIPS + R3000 and R4000 processors. + +
+ OKUJI Yoshinori maintains a set of Japanese + Hurd pages. + +
UCHIYAMA Yasushi has ported + XFree86 to the Hurd. + +

+ +Copyright (C) 1998 Free Software Foundation, Inc., +59 Temple Place - Suite 330, Boston, MA 02111, USA + +Verbatim copying and distribution of this entire article is +permitted in any medium, provided this notice is preserved. diff --git a/unsorted/HurdOnL4.mdwn b/unsorted/HurdOnL4.mdwn new file mode 100644 index 00000000..79e7a714 --- /dev/null +++ b/unsorted/HurdOnL4.mdwn @@ -0,0 +1,173 @@ +# GNU/Hurd on L4 wiki + +## Introduction + +This page is a place for information pertaining to the efforts towards realizing the migration and porting of the [[Hurd]] such that it uses the [L4 Microkernel](http://l4ka.org/). The GNU/Hurd Operating System, sometimes just referred to as the _GNU Operating System_ is a rich and robust collection of programs and utilities which enable you to use your computer to do usefull and or entertaining things. The intent is that most any applicable software package available on the [GNU Website](http://www.gnu.org) (and many others also) will be able to be compiled and run under the resultant operating system. + +At this point (06/20/2004) this is not yet possible. Indeed, the preliminary foundations are still being developed. Nevertheless, this is a volunteer created operating system so those with the knowledge, interest, and spare time are encouraged to study and if possible contribute to the project. + +In [CVS module hurd-l4](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/), there is a [comprehensive list of items that need to be done](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/TODO). + +## Components of the System + +### The L4 Microkernel + +The kernel of an operating system is a fundamental program which provides essential resources from the hardware of the computer to other programs. A kernel typically runs all the time and remains resident in main memory. The amount of functionality and resources which it provides vary tremendously. The [L4 Microkernel](http://l4ka.org/) is an attempt to create a very small high performace core which provides basic memory management, task and context switching, and little else. + +### The Hurd + +The [Hurd](http://www.gnu.org/software/hurd/hurd.html) is a conglomeration of servers and programs which add additional functionality to a microkernel such that it is capable of utilizing additional hardware resources of the computer. It also provides a compatibility layer such that compiling higher level programs is essentially transparent; i.e. when you write a C program and compile it, you need only include standard headers and libraries and for all intents and purposes your generic program will build and run and you need never resort to unportable coding or access to hardware specific methods. + +For a typical user, The Hurd is intended to silently work in the background providing the services and infrastructure which are lacking in the microkernel but are required for higher level programs and libraries to operate. + +### GNU Programs + +For the user, this is what is desired: to run [GNU Software](http://www.gnu.org/). These programs provide a full featured, robust, and extremely effective operating system. A L4/Hurd system should be capable of compiling and executing most any software package available from GNU with little or no modification. + +Some readers may be familiar with GNU/Linux systems. When GNU/L4 is complete it should highly resemble the functionality of such systems as L4 and Hurd effectively replace the Linux kernel. The bulk of the software should be expected to run much as it does presently under the Linux kernel (or gnumach based GNU/Hurd systems). + +## Preparations + +### Build System + +There are no precompiled binaries for Hurd on L4 that I am aware of, so you will need to be able to compile the source code packages in order to experiment with it. While L4Ka will likely build on a variety of compilers and systems, the Hurd may prove troublesome unless it is built using recent GNU compilers and tools. + +I recently used [Debian Unstable](http://www.debian.org) (Sarge) with GNU gcc version 3.3, autoconf version 2.50, and automake version 1.8 to build the system with good results, although other similarly equipped systems with a good development environment, such as [Gentoo](http://www.gentoo.org) or [Slackware](http://www.slackware.com) are reported to work fine also. + +Generally, I would recommend building the packages using any very up-to-date GNU development system. I'm not going to say that you can't compile them using more exotic platforms, but I wouldn't be overly hopefull about it. I have no idea if Pistachio can be compiled under current gnuMach/Hurd systems it might be interesting to try it. + +### Making a Home for L4/Hurd + +Obviously you want to have a home for this little embryonic operating system. Currently, mine is using about 5M for the binaries and headers. If you want the source to reside with the binaries, then allow perhaps another 50M or so, but this is purely optional. + +At the moment, Hurd on L4 can't even see your hard drive, so all you need is a directory on some partition which is visible to the GRUB bootloader. A `/l4hurd` directory on your existing GNU/Linux system is probably fine for now. + +Howevever, if you have some spare disk space or an unused partition, you could optionally create a small partition for the system. This is totally unnecessary at the moment because L4/Hurd lacks hard disk drivers right now, but it is an option. Assuming that you have made some partition **X** with linux _fdisk_, set it to type 83 - Linux and use the following command to initialize it with the classic Hurd extensions: + + + +As noted, this is purely optional, in fact right now you can use any filesystem that GRUB can understand. You can even use TFTP to netboot the system. My current setup takes about 5M for the full install so obviously you don't need much space for this. + +### Boot Loader + +Just like regular GNU/Hurd, you need to use [GNU GRUB](http://www.gnu.org/software/grub/), the _GRand Unified Bootloader_ in order to boot the system. Hopefully you already have it installed, in which case adding the commands for L4/Hurd to your `menu.lst` is quite trivial. + +If you don't have GRUB installed, then you should probably take some time to get it set up. A good place to look for help is on the regular [Debian GNU/Hurd Installation Page](http://www.debian.org/ports/hurd/hurd-install) at the **3\. The Boot Loader** section. + +This is probably a bit superfluous, but you can even display a snazzy little graphic of some type on your GRUB boot menu. Here's a snip from the header of my `menu.lst` which demonstrates how to do this. + + # menu for grub + splashimage (hd0,0)/boot/grub/debian.xpm + foreground bfbfe7 + background 3f3f7f + +In the above example, my `debian.xpm` is just a 640x480 graphic in xpm format (which you can easily create with GIMP). It does add a bit of pizazz to your boot screen :-) + +In fact, I will attach a sample copy of my `menu.lst` here. It has lots of examples for booting a variety of operating systems in it. Remember that my hard drive partitions are unique to my system. + +* [[ATTACHURLmenulst]]: Sample GRUB boot menu + +## Building Hurd on L4 + +### L4Ka Pistachio + +#### Getting the Sources + +I used the latest version of L4Ka, Pistachio version 0.4. It can be obtained from the following website: + +[L4Ka Pistachio Home](http://l4ka.org/projects/pistachio/) + +#### Compiling + +Pistachio is designed to be compiled in a build directory which is independant from the source directory, so you need to create your build directory after unpacking the tarball. Furthermore, you need to pass a couple of special parameters to the configure program to set it up for use with Hurd. Here is what I did on my ia32 system: + +Note: I have my installation set up in `/l4hurd` and I am starting from within the Pistachio source top-level directory. + + $ mkdir build + $ cd build + Building and installing user-level libraries and servers/applications + $ ../user/configure --with-s0-linkbase=0x40000 --prefix=/l4hurd + $ make + $ make install + Building and installing the kernel + $ make -C ../kernel BUILDDIR=`pwd`/kernel + $ cd kernel + $ make menuconfig + $ make + $ mkdir /l4hurd/boot + $ cp ia32-kernel /l4hurd/boot + +Hopefully everything worked and there were no problems. As usual, if the build fails then scrutinize the output from `configure` and install any missing libraries or development packages. + +### CVS l4hurd + +#### Getting the sources + + You need to pull the L4 Hurd sources from the CVS tree on Savannah. The CVS access page is [The GNU/Hurd - CVS (module hurd-l4)](http://savannah.gnu.org/cvs/?group=hurd). In a nutshell, the following commands should retrieve the sources for you: + + $ cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co hurd-l4 + +#### Compiling + +Take a look at the README, compiling should be quite simple on any state of the art GNU development system. As per the README, and for my example, you would: + + $ autoreconf -f -i -s + $ ./configure --enable-maintainer-mode --prefix=/l4hurd + $ make + $ make install + $ strip physmem/physmem + + $ mkdir /l4hurd/boot + $ cp laden/laden /l4hurd/boot + $ cp wortel/wortel /l4hurd/boot + $ cp physmem/physmem /l4hurd/boot + +Currently (2004/08/09), physmem needs to be stripped to to avoid a memory conflict with wortel; this requirement may be fixed in the future. + +In my case it was slightly more complicated as Debian uses a wrapper system to enable the use of multiple versions of the GNU Autotools. In this case, the trick is to utilize some environment variables on the command line as follows: + + $ ACLOCAL=aclocal-1.8 AUTOMAKE=automake-1.8 autoreconf -f -i -s + +As above, hopefully this will compile cleanly; otherwise, scroll up, read any error messages, and correct them by installing required packages of the proper version. Any bad compilation problems are most likely due to you either missing or using a wrong version of something. + +## Installing + +The binaries are now installed into `/l4hurd`. All that remains is to add an entry into GRUB's `menu.lst` in order to test it out. Here's an example from my system where I have `/l4hurd` on `/dev/hda9` in my Linux system: + + title GNU Hurd on L4Ka Pistachio 0.4 + root (hd0,8) + kernel /boot/laden -D + module /boot/ia32-kernel + module /libexec/l4/sigma0 + module /boot/wortel -D + module /boot/physmem -D + module /boot/physmem + module /boot/physmem + module /boot/physmem + module /boot/physmem + +It might strike you a little odd that there are five physmem modules. This is done because wortel currently (2004/08/09) expects exactly five modules and the other modules (like the task server, auth server, etc.) have not been implemented yet. Therefore the physmem module is used as a dummy module. + +## Booting + +For me at least, I got some nifty messages and then it dropped into a simple debugging mode. As far as I know, thats all there is right now. + +Read, build, learn, code... + +--todo: add more here. + +## Experimenting + +Well, thats why you did all of this, certainly not to do anything else. Use that debugger and get experimenting. + +--todo: things to do wth the debugger + +## Conclusion + +If you followed these steps, you most likely have built and booted the latest version of Hurd on L4. I would encourage you to subscribe to the mailing list at the following URL and help in the efforts to get this nifty system up to speed: + +[l4-hurd mailing list](http://lists.gnu.org/mailman/listinfo/l4-hurd) + +And finally, this is a wiki, meaning that **you** have the ability to edit and modify this page. If you want to fix something, add more information, new sub-pages, whatever, feel free to do so. This is a great way to get a doc base up fast and keep it current, so use it like its supposed to be and have fun with Hurd on L4! + +-- [[Main/BDouglasHilton]] - 20 Jun 2004 diff --git a/unsorted/HurdOnL4/menu.lst b/unsorted/HurdOnL4/menu.lst new file mode 100644 index 00000000..3129ea74 --- /dev/null +++ b/unsorted/HurdOnL4/menu.lst @@ -0,0 +1,55 @@ +# menu for grub +splashimage (hd0,0)/boot/grub/debian.xpm +foreground bfbfe7 +background 3f3f7f + +timeout 30 +default 0 + +title Debian Sid with Linux kernel 2.6.5 +root (hd0,1) +kernel /vmlinuz root=/dev/hda2 vga=0x318 + +title Debian Sid with old kernel +root (hd0,1) +kernel /vmlinuz.old root=/dev/hda2 vga=9 + +title Microsoft Windows 2000 +rootnoverify (hd0,3) +chainloader (hd0,3)+1 + +title FreeDOS BETA 8.0 +root (hd0,0) +chainloader +1 + +title GNU Hurd on L4Ka Pistachio 0.4 +root (hd0,8) +kernel /boot/laden -D +module /boot/ia32-kernel +module /libexec/l4/sigma0 +module /boot/wortel -D +module /boot/physmem + +title Debian GNU/Hurd (gnumach) +root (hd0,7) +kernel /boot/kernel.gz root=device:hd0s8 +module /hurd/ext2fs.static --readonly \ + --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 Debian GNU/Hurd (oskit-mach) +# root (hd3,0) +# kernel /boot/kernel-ide -- root=hd0s1 +# 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 device ${root-device} $(task-create) $(task-resume) +# module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) + +# title Debian GNU/Hurd (oskit-mach w/ remote debugging) +# root (hd3,0) +# kernel /boot/kernel-ide -d GDB_COM=1 BAUD=9600 -- root=hd0s1 +# 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 device ${root-device} $(task-create) $(task-resume) +# module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) + diff --git a/unsorted/InteractiveTranslators.mdwn b/unsorted/InteractiveTranslators.mdwn new file mode 100644 index 00000000..9a0ca7e2 --- /dev/null +++ b/unsorted/InteractiveTranslators.mdwn @@ -0,0 +1,31 @@ +The following text is from mail by Hurd architect Thomas Bushnell: + +> Thread moved over to bug-hurd since it's about design and not Debian GNU/Hurd per se. Alfred Szmidt had pointed out that a dpkg installation translator (one where you copy a .deb into a directory to install it into the system) cannot be easily written, because Debian package installation scripts are sometimes interactive. +> +> I said that this was a deficiency in the design of the Hurd, and that it would be good to fix it (ultimately) by creating user interaction context widgets which can be passed to servers so that they can safely and securely interact with the user when necessary. +> +> Alfred M. Szmidt writes: +> +> > I think you mean that it is a shortcoming in the design of things that are not or cannot be interactive, filesystems being one such example. I can see it infront of me: stat() poping up a dialog asking me to do something each time it gets called... +> +> No, it's a shortcoming in the design of the Hurd, because many times it **can** be interactive. Of course we don't want stat prompting you ever time it's called, but that's not an excuse for preventing stat from ever prompting you at all. We use all kinds of programs that can be interactive, and needless prompts are bugs, easily fixed. +> +> Please, don't lecture me about the Hurd being perfect; it's not. And this is a shortcoming that can someday be fixed, so we shouldn't pretend it's not a problem. It is. A friend at the AI lab once gave the following dream as an example of a well-functioning system: +> +> You walk up to the workstation and start a complex memory intensive ray-tracing program. It runs out of memory and swap space on the workstation. A dialog pops up informing you of the situation and giving several options: suspend the job until later, kill it, and so forth. (Notice that Unix and the Hurd both simply kill the process or the system here, because the discovery that swap is gone happens so low down that all context has been lost.) +> +> You put a disk in the drive. After putting the disk in, without you doing anything in the dialog, a new option comes up, "I notice you just put a disk in; do you want to use this for additional swap?" You say yes. The process now continues, with part of the swap being on the disk. (Notice that Unix and the Hurd don't make connections like this, having one driver know that something **else** in the system might be waiting for this resource and offering it for use.) +> +> In the middle of the task, you hit the button on the drive and out pops the disk. A notifier pops up on the screen, saying that the necessary swap for your process has been removed from the system, and so the job has been suspended until later, and giving you the option of killing it. You say "OK" (that is, you do not say to kill it), and then you log out. (Note that Unix and the Hurd cannot carry on at all in such a case; failure to satisfy a page-in fault results in utter disaster, not clean behavior. Also, neither control carefully which data is paged to which devices, because all interaction context is gone when pageout decisions are being made, so if you have started paging on this disk, you have probably started paging all kinds of essential system services on it too.) +> +> A week later, you walk up to a different workstation in the cluster, and pop in your disk. The system says, "I notice you have a suspended job that was using this disk for swap space" and allows you to resume it where you left off. (Notice that this requires close interaction between the workstations in the cluster, combined with more driver-level cleverness.) +> +> Now that's a well-functioning system. It requires careful bookkeeping of context, knowledge about how to usefully interact with the user from deep in the bowels of the system, and so forth. The Hurd has the capacity for this kind of thing, because user servers can do arbitrary things, unlike kernel routines in Unix. But we must figure out how to give them all the necessary information about their context. +> +> When I designed the filesystem protocols and the structure of the system, I did not consider this kind of flexibility. I had only the simplest kinds of filesystem translators in mind, ones which were just like Unix filesystems but supporting formats like tar and ar in addition to the typical mass-storage types. It was only a little later that I realized union and shadow translators would be a nice thing (and BSD picked up the idea after I explained it at a Boulder BSD conference). Keeping track of who is using which swap space? Now **that** would be clever, and would be very very nice to have. +> +> The reason that filesystems do not have user context is because I was not sufficiently far-sighted at the time to realize the full flexibility of the translator concept I had created. Now that we know more about that flexibility, it would be nice to start figuring out how to improve it. +> +> Thomas + +-- [[Main/OgnyanKulev]] - 21 Mar 2005 diff --git a/unsorted/JoachimNilssonHurdPage.mdwn b/unsorted/JoachimNilssonHurdPage.mdwn new file mode 100644 index 00000000..e4dde2b9 --- /dev/null +++ b/unsorted/JoachimNilssonHurdPage.mdwn @@ -0,0 +1,247 @@ + + + + + + + + + +

+	Edit this page
%ATTACHURL%/patch_kit.jpg	Table of Contents %TOC%

+ +## Introduction + +This page serves as a simple project page for me. I use it to list my personal Hurd related projects, currently only OSKit related. If you wish to comment on my work, do so in [[TWiki/GoodStyle]], preferably at the bottom of this page. + +The OSKit work is based on the St. Patrick's Day release, snapshot 20020317. + +These patches are available through the [Savannah OSKit project](http://savannah.gnu.org/projects/oskit/) Hopefully they will also be integrated into the main tree at Utah. + +## Progress + +**_2005-02-05:_** Sorry, these pages are now dead. It turned out that my spare time actually was limited. I have a family with a second child due in August — so it's unlikely that I'll ever go back to working with these patches. However, I plan on joining the [[HurdOnL4]] project, possibly to help with drivers, since that's what I do at work mostly. + +**_2003-04-17:_** I've become a bit distracted lately from my Hurd related projects. My work has consumed a lot of time, as have my personal life (I'm about to become a dad! :). But don't worry, I have been working quietly in the background anyway - the OSKit patches have been integrated into the Savannah OSKit project and a new [[TWiki/GnuSkin]] release has been made. + +There is one thing now, only one little thing that I want to have finished before the summer. My Promise ATA-100 controller - support for it in [[Mach/OskitMach]]. Any spare time I find I'll spend on getting that one up and running. + +## Current Project + +I'm working on importing the Linux ATA-100 drivers to the OSKit. Using patches by Linux ATA guy, Andr� Hedrick. [ATA-100 patches](http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.20/). + +At my help I now have [[Main/OgnyanKulev]], he will test a few ATA-100 cards he has access to. + +[[Main/JoachimNilsson]]: + +* HighPoint HPT366 ATA-66 +* Promise PDC202XX ATA-100 + +[[Main/OgnyanKulev]]: + +* Promise PDC202XX +* Intel 82801BA +* Silicon Image CMD649 + +### OSKit - ATA-100 Support + +I have used the Linux 2.2.22 patch as the base and added the Linux ide-2.2.20.01102002 patch on top. Integration is now complete, testing have started. An alpha quality release is available below, if you want to help out with testing or be on the bleeding edge of things, please contact me via email. + + + + + + + + + + + + + + +

Part	Brief description	DIFF	Date
2.2.22-ATA (ALPHA)	Adds ATA-100/66 capabilities (alpha release)	patch-oskit-linux-2.2.22-ATA-alpha.diff.gz	Jan 3, 2003

+ +**_Comments:_** + +* Progress is slow. + * Off-board chipsets seem more difficult ... + * PIIX chipset works, tuning included. + +---- + +## Previous Projects + +### OSKit - "New" Linux NIC drivers + +"New" means simply to add more of the drivers existing in Linux 2.2.X that don't exist in the OSKit today. + +To test any of the work in this project you first need to upgrade the OSKit to Linux 2.2.22 (or later) using my patches below. The first stage deals with network drivers, 10 and 100 Mbps. Gigabit ethernet I have no possibility to test ... so they are **not** included. + +I may, at a later date, also include updates to drivers by Donald Becker. See the drivers at + + + + + + + + + + + + + + +

Part	Brief description	DIFF	Date
2.2.22-NET	Adds more Linux NIC drivers	patch-oskit-linux-2.2.22-net.diff.gz	Dec 26, 2002

+ +**_Added NICs:_** + +* 3Com 3c515 +* D-Link DE-600, DE-620 +* Davicom DM9102(A)/DM9132/DM9801 +* N2k-PCi, NE2000 PCI-based cards +* PCNet32 +* RealTek RTL8139 +* SiS 900/7016 +* ThunderLAN +* VIA Rhine + +### OSKit - Upgrade existing Linux drivers + + The OSKit itslef is currently at Linux version 2.2.12 for most of its drivers. The objective of this project was to upgrade to 2.2.22. I will of course also provide upgrades to upcoming revisions of the 2.2.x series, but they have a low priority right now. Please note: + +* The patches are cummulative, i.e., you only need one. +* The patches only upgrade existing OSKit drivers, they don't add support for new ones. Unlike the corresponding Linux patches. + +To build [[Mach/OskitMach]] you also need some other [[Mach/OskitPatches]]. As well as two unofficial GNUmach2 patches. See Daniel Wagners post to bug-hurd, , or the [[Mach/OskitMachPatches]]. + +**_Tested NICs:_** + +Testbed: Intel AL440LX mobo 128MiB RAM (only 64MiB detected by Grub 0.93). + +* Digital Equipment Corp. Etherworks Turbo PCI Controller DE435 - digital Tulip 21040-AA +* 3Com 3C905B-TXNM Fast Etherlink XL PCI - Parallel Tasking II 3Com 40-0483-004 +* RTL8139 + +**_Untested NICs:_** + +These I have and will test eventually + +* Western Digital 10 Mbps ISA - WD8003EBT +* SMC Ultra 16 ISA +* NE1000/2000 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Part	Brief description	DIFF	Date	Verified?
2.2.13	Upgrade from Linux 2.2.12 to 2.2.13	patch-oskit-linux-2.2.13.diff.gz	Oct 27, 2002	Yes (1)
2.2.14	Upgrade from Linux 2.2.12 to 2.2.14	patch-oskit-linux-2.2.14.diff.gz	Oct 30, 2002	Yes (1)
2.2.15	Upgrade from Linux 2.2.12 to 2.2.15	patch-oskit-linux-2.2.15.diff.gz	Oct 31, 2002	Yes (1)
2.2.16	Upgrade from Linux 2.2.12 to 2.2.16	patch-oskit-linux-2.2.16.diff.gz	Oct 31, 2002	Yes (1)
2.2.17	Upgrade from Linux 2.2.12 to 2.2.17	patch-oskit-linux-2.2.17.diff.gz	Nov 1, 2002	Yes (1)
2.2.18	Upgrade from Linux 2.2.12 to 2.2.18	patch-oskit-linux-2.2.18.diff.gz	Nov 1, 2002	Yes (1)
2.2.19	Upgrade from Linux 2.2.12 to 2.2.19	patch-oskit-linux-2.2.19.diff.gz	Nov 4, 2002	Yes (1)
2.2.20	Upgrade from Linux 2.2.12 to 2.2.20	patch-oskit-linux-2.2.20.diff.gz	Nov 5, 2002	Yes (1)
2.2.21	Upgrade from Linux 2.2.12 to 2.2.21	patch-oskit-linux-2.2.21.diff.gz	Nov 5, 2002	Yes (1)
2.2.22	Upgrade from Linux 2.2.12 to 2.2.22	patch-oskit-linux-2.2.22.diff.gz	Nov 5, 2002	Yes (1)
2.2.23	Upgrade from Linux 2.2.12 to 2.2.23	[[][patch-oskit-linux-2.2.23.diff.gz]]	Not yet

+ +**_Notes:_** + +1. Yes, the patch has been tested using the latest CVS version (HEAD) of GNUmach. Verified means that I have verified that GNUmach can be built, booted successfully (using IDE and various NICs). + +## Future Work + +1. Try to enable GNUmach to use the [[TWiki/FreeBSD]] drivers in the OSKit. +2. Port a simple DHCP client (udhcp perhaps?). +3. Enable the sound drivers in the OSKit -- port a useful sound daemon. +4. SMP support for GNUmach2 - Current OSKit is broken. + +### [[TWiki/FreeBSD]] NIC drivers for GNUmach + + I have looked into this a bit. The PCI drivers are initialized from the PCI probe. GNUmach v2 uses the Linux PCI stuff which means the [[TWiki/FreeBSD]] probe will not run - this is probably solved in some ingenious way in the OSKit, maybe the COM interfaces, but I've yet to find out more about that. + +---- + + Feel free to contact me if you have any comments or suggestions. + +-- [[Main/JoachimNilsson]] - Feb 19th 2003 + +## Comments + +Go Joachim! Great work! + +-- [[Main/GrantBow]] - 11 Nov 2002 diff --git a/unsorted/JoachimNilssonHurdPage/patch_kit.jpg b/unsorted/JoachimNilssonHurdPage/patch_kit.jpg new file mode 100644 index 00000000..da5cc147 Binary files /dev/null and b/unsorted/JoachimNilssonHurdPage/patch_kit.jpg differ diff --git a/unsorted/KernelCousinDebianHurd.mdwn b/unsorted/KernelCousinDebianHurd.mdwn new file mode 100644 index 00000000..1ff8a698 --- /dev/null +++ b/unsorted/KernelCousinDebianHurd.mdwn @@ -0,0 +1,3 @@ +[Kernel Traffic](http://www.kerneltraffic.org/) publishes newsletters that track the technical developments of various projects of the Free and Open Source world. [Newsletters for the Hurd development](http://www.kerneltraffic.org/debian-hurd/archives.html) were published, but not anymore. + +Updated status. -- [[Main/OgnyanKulev]] - 18 Sep 2004 diff --git a/unsorted/KnownHurdLimits.mdwn b/unsorted/KnownHurdLimits.mdwn new file mode 100644 index 00000000..51d66b50 --- /dev/null +++ b/unsorted/KnownHurdLimits.mdwn @@ -0,0 +1,20 @@ +* ~1.5 GB ext2 file system size limit + * The problem is fixed in the Debian GNU/Hurd distribution but not the official sources, see [this email](http://lists.debian.org/debian-hurd/2007/07/msg00087.html) + * See [[ExtTwoSize]] + +* Many Unsupported Devices. + * See [[Mach/HardwareCompatabilityList]] + +* Entropy. Mach does not yet gather entropy and thus there are no /dev/random and /dev/urandom nodes. + There are needed by OpenSSH. + * In progress, see [[translator/random]] + +* No DHCP client + * promising information [Jan 2005](http://lists.gnu.org/archive/html/bug-hurd/2005-01/msg00025.html), needs an update + * See [[DhcpClient]] - need to update TCP/IP server. + +* Missing bits of POSIX + * See [[Distrib/SystemAPILimits]] + +* Stability issues + * [[ZallocPanics]] diff --git a/unsorted/LuisBustamanteHurdPage.mdwn b/unsorted/LuisBustamanteHurdPage.mdwn new file mode 100644 index 00000000..abbf1531 --- /dev/null +++ b/unsorted/LuisBustamanteHurdPage.mdwn @@ -0,0 +1,11 @@ +Nothing much to see right now, I'll add some stuff I'm working in the near future! :) + +Cheers, + +-- [[Main/LuisBustamante]] - 16 May 2002 + +After making some trivial/incorrect patches (thanks Neal :) for building um-pppd with gcc 3.0.4 in Debian (see [\#147085](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147085&repeatmerged=yes)) this weekend I'll finally give it a try, I got an external modem... anyway serial drivers seem to be broken in GNUmach iirc, I won't get much more than 300b/s :). + +Keep Hurding! + +-- [[Main/LuisBustamante]] - 17 May 2002 diff --git a/unsorted/MakeImage.mdwn b/unsorted/MakeImage.mdwn new file mode 100644 index 00000000..95b928c4 --- /dev/null +++ b/unsorted/MakeImage.mdwn @@ -0,0 +1,60 @@ +## Make a disk image + +This is just a reminder to myself currently. + + /bin/dd if=/dev/zero of=gnu.img count=224000 + /sbin/sfdisk -C 58 -H 16 -S 63 -D gnu.img< Install GNU/Hurd + + mkdir image + mount /dev/loop0 image + cd image/ + /usr/share/crosshurd/makehurddir.sh `pwd` i386 gnu + cd .. + umount image + losetup -d /dev/loop0 + +## Make Boot ISO + +I use this for testing OSKit... + + mkdir -p iso/boot/grub + cp /lib/grub/i386-pc/stage2_eltorito iso/boot/grub/ + cp oskit-mach.gz iso/boot/ + cat >iso/boot/grub/menu.lst << EOF + title GNUmach 2.0 (OSKit-Mach) + root (cd) + kernel /boot/oskit-mach.gz root=device:hd0s1 -- + root (hd0,0) + 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-2.3.2.so /hurd/exec $(exec-task=task-create) + + title GNU/Hurd (GNUmach 1.3) + root (hd0,0) + kernel /boot/gnumach.gz root=device:hd0s1 + 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) + + EOF + mkisofs -R -b boot/grub/stage2_eltorito -no-emul-boot -boot-load-size 4 \ + -boot-info-table -o grub.iso iso + +## Booting Qemu + + qemu -user-net -isa -boot d -cdrom grub.iso -hda gnu.img + +The switch `-isa` is for current gnumach.gz on hda. + +-- [[Main/JoachimNilsson]] - 11 Apr 2005 diff --git a/unsorted/OskitMach.mdwn b/unsorted/OskitMach.mdwn new file mode 100644 index 00000000..c28f2d89 --- /dev/null +++ b/unsorted/OskitMach.mdwn @@ -0,0 +1,64 @@ +[[toc ]] + +* [[OskitMachStatusList]]: Status and TODO list (deb status) +* [[OskitMachPatches]]: Bleeding edge patches +* [[OskitPatches]]: Useful patches for the OSKit +* [[BuildingOskitMach]]: How to build your own GNUmach kernel +* [[RemoteDebugOskitMach]]: How to use gdb to remote debug the GNUmach kernel + + +## About + +OSKit-Mach began as a branch of the GNUMach 1.2 kernel, but since the release of GNU Mach 1.3, OSKit-Mach has been merged as the new GNUMach 2.x mainline. The [[history]] page tells a more interesting story including other operating systems who use Mach in their kernels. + +GNU Mach 2.0 makes use of the drivers provided by [the OSKit](http://www.cs.utah.edu/flux/oskit/) from [the Flux Research Group](http://www.cs.utah.edu/flux/). The OSKit provided a neat driver base where both [[TWiki/FreeBSD]] and Linux (2.2.12) drivers are made available to [Mach](http://www-2.cs.cmu.edu/afs/cs/project/mach/public/www/mach.html) and thus the Hurd. However, OSKit isn't maintained anymore. + +## Status + +The OSKit-Mach version of GNUmach is today (2005) more or less defunct. Nobody +is working on it. Few people ever got it running, and by now there are also +problems building with recent toolchains. Instead, the Hurd developers now +concentrate on completely different microkernels (Coyotos being the current +favourite), as well as on improving the original GNU Mach 1.x codebase. (See +also [[microkernel/mach/gnumach/projects]].) + +The [[mailing_lists]], or the [[IRC]] is, like always, the best source of more +current information. + +There also exist other efforts: + +* [OSKit and OSKit-Mach PPC Port](http://es.gnu.org/~jemarch/ppc-oskit/) - Maintained by [Jos� Marchesi](mailto:jemarch AT gnu DOT org) + +* [OSKit-Mach Alpha Port](http://savannah.gnu.org/projects/gnumach-alpha/). - This work has been integrated into the actual OSkit cvs tree at utah. + +## Building + +First you need to get the latest OSKit release and, preferrably, the latest CVS version of GNUmach. Take a look at the following [tutorial](http://www.etherhogz.org/doc/oskit-mach.html) to get started. Or the locally kept version, [[BuildingOskitMach]]. + +## Starting + +You start Oskit-Mach almost the same way as the old 1.x version of GNUmach. Using [[Hurd/GrubNotes]] an entry can look like this: + + title GNUmach 1.90 (CVS) + root (hd0,1) + kernel /boot/oskit-mach.gz root=device:hd0s2 -- + 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) + +_Remember_ to ensure that there are no trailing spaces after the backslashes on the lines above if you copy-paste this into your menu.list file. + +## Bugs + +We have bugs, just like any other software product. To get around the more nasty ones you can apply the unofficial patches found on + +* [[OskitMachPatches]] + +## Debugging + +See Igor Khavkine's, [i\_khavki@alcor.concordiaNOSPAM.ca](mailto:i_khavki@alcor.concordiaNOSPAM.ca), excellent help to [remote debug oskit-mach over a serial line](http://www.etherhogz.org/doc/oskit-boot.txt), or the local [[RemoteDebugOskitMach]]. + diff --git a/unsorted/OskitMachPatches.mdwn b/unsorted/OskitMachPatches.mdwn new file mode 100644 index 00000000..c1e1b068 --- /dev/null +++ b/unsorted/OskitMachPatches.mdwn @@ -0,0 +1,10 @@ +## GNUmach2 (oskit-mach) Patches + +The following patches are here for your convenience only. They are probably not accepted yet and should thus only be used by people working on the bleeding edge of ... oh well, use at your own risk. :-) + +**_Daniel Wagner:_** + +* Fix GNUmach2 panic related to buggy softint handling [[ATTACHURLpatch-gnumach_softint-wagidiffgz]] +* Eliminate GNUmach2 assertion that triggers a bug [[ATTACHURLpatch-gnumach_assertion-wagidiffgz]] + +- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/unsorted/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz b/unsorted/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz new file mode 100644 index 00000000..3d57b43a Binary files /dev/null and b/unsorted/OskitMachPatches/patch-gnumach_softclock-wagi.diff.gz differ diff --git a/unsorted/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz b/unsorted/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz new file mode 100644 index 00000000..215706b3 Binary files /dev/null and b/unsorted/OskitMachPatches/patch-gnumach_softint-wagi.diff.gz differ diff --git a/unsorted/OskitMachStatusList.mdwn b/unsorted/OskitMachStatusList.mdwn new file mode 100644 index 00000000..f62e0686 --- /dev/null +++ b/unsorted/OskitMachStatusList.mdwn @@ -0,0 +1,15 @@ +**NOTE**: As of March 2006, nobody is using or working on OSKit-Mach. Consider below text for historic reference only. + +The only thing that is needed before we will switch to the OSKit-Mach variant of GNU Mach is the missing console: OSKit-Mach has no console in the kernel, so we need an implementation in user space. Marcus Brinkmann is writing a console implementation with a client-server design, Unicode support and lots of other goodies. The server is working, the ncurses client is working (which is useful for testing and results in something similar to screen) and the VGA client is the one missing component. A part of the code for it already exists; it will share some code with the ncurses client via a console-client library. After it works, some testing of OSKit-Mach will also be needed. + +-- [[Main/WolfgangJ]] - 24 Jul 2002 + +There was quite a bit of coding and testing in September as described in several [bug-hurd threads](http://mail.gnu.org/pipermail/bug-hurd/2002-September/thread.html). + +Unfortunately this work still needs to be ported from GNUmach 1.3 (commonly used today) to GNUmach 2.0 (a.k.a OSKit-Mach). + +-- [[Main/GrantBow]] - 07 Oct 2002 + +There should now exist a working console-client for [[OskitMach]] as well. + +-- [[Main/JoachimNilsson]] - 28 Nov 2002 diff --git a/unsorted/OskitPatches.mdwn b/unsorted/OskitPatches.mdwn new file mode 100644 index 00000000..d189bb6d --- /dev/null +++ b/unsorted/OskitPatches.mdwn @@ -0,0 +1,67 @@ +## Table of Contents + +%TOC% + +## Flux OS Toolkit + +[The OSKit](http://www.cs.utah.edu/flux/oskit/) is a framework and a set of libraries for building and extending operating systems developed by [the Flux Project](http://www.cs.utah.edu/flux/). + +**_Note:_** All of these patches, and more, are now avilable directly through the [Savannah OSKit](http://savannah.gnu.org/projects/oskit/) project. This is also the recommended source today of the OSKit, especially if you want to use it with GNUmach2. + +## OSKit 2001-02-14 + +These are extra patches for people who, for some reason, use the 2001 version of the OSKit. + +* Patrick Tullman [[ATTACHURLpatch-oskit-097-tullmandiffgz]] + +* This patch is necessary to get the `--enable-indirect-osenv` flag to the configure script. The flag is enabled by default for OSKit 2002-03-17 and later. Kevin Kraemer [[ATTACHURLpatch-oskit-097-kkraemerdiffgz]] + +## OSKit 2002-03-17 + +**_Critical Patches:_** + +Here are the patches critical to get [[OskitMach]] running. These are absolutely essential to get a working Mach kernel. Many of these patches are included with the Debian distribution of the OSKit. + +* Igor Khavkine [[ATTACHURLpatch-oskit-097-i_khavkidiffgz]] + +* Famous removal of only one line in sbrk-hack.c - needed for people with newer libc's (e.g. Debian Woody) [[ATTACHURLpatch-oskit-097-sbrk_hackdiffgz]] + +* Jonathan S. Arney - Important patch to diskpart library. Without it you cannot activate swap in oskit-mach. [[ATTACHURLpatch-oskit-097-jon_arneydiffgz]] + +* Richard Kreuter's [patches](http://anduril.rutgers.edu/richard/oskit/) ([announcement](ftp://flux.cs.utah.edu/flux/oskit/mail/html/oskit-users/msg01560.html)). Needed when your Hurd partition is embedded inside an extended partition created by Windows. The patches also include: + * support for extended partitions with lba + * support for 16-entry BSD disklabels, as are supported by recent Net- and [[TWiki/FreeBSD]] kernels. + * support for the recognition of NetBSD's slice id (169) in the BIOS partition table. + +**_Cosmetic Patches:_** + +* Kevin Kraemer - Removes annoying debug output from eepro.c driver. [[ATTACHURLpatch-oskit-097-eeprodiffgz]] + +* Ognyan Kulev - Reduce warnings when compiling with GCC 3.2. + +**_New Functionality:_** + +* [Roland McGrath](http://www.frob.com/) - [i8042 support](http://mail.gnu.org/archive/html/bug-hurd/2002-10/msg00146.html). Thread continues at + +* Daniel Wagner - PCMCIA support. ([instructions](http://www.vis.ethz.ch/~wagi/hurd/oskit/readme.txt)) + +* [[Main/JoachimNilsson]] - See [[Hurd/JoachimNilssonHurdPage]] + * Upgrade to Linux 2.2.22 drivers + * More Linux NIC drivers + * **_Soon:_** ATA-100 patches (α-release available) + +* [[Main/DerekDavies]] - [OSKit Entropy patch](http://www.ddavies.net/oskit-entropy/). A Linux entropy driver, see [bug-hurd posting](http://mail.gnu.org/archive/html/bug-hurd/2003-01/msg00000.html) for more information. + +---- + +## Comments + +Divided this growing topic into sections.
-- [[Main/JoachimNilsson]] 19 Nov 2002 + +Updates by [[Main/OgnyanKulev]] -- 19 Nov 2002 + +All small patches are as attachments now. -- [[Main/OgnyanKulev]] - 16 Dec 2002 + +Minor updates, also, added Davids Entropy patch -- [[Main/JoachimNilsson]] - 03 Jan 2003 + +Fixed some gnu mail links -- [[Main/MattGrant]] - 26 Feb 2003 diff --git a/unsorted/OskitPatches/patch-oskit-0.97-eepro.diff.gz b/unsorted/OskitPatches/patch-oskit-0.97-eepro.diff.gz new file mode 100644 index 00000000..80d94f3f Binary files /dev/null and b/unsorted/OskitPatches/patch-oskit-0.97-eepro.diff.gz differ diff --git a/unsorted/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz b/unsorted/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz new file mode 100644 index 00000000..2e322de9 Binary files /dev/null and b/unsorted/OskitPatches/patch-oskit-0.97-i_khavki.diff.gz differ diff --git a/unsorted/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz b/unsorted/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz new file mode 100644 index 00000000..aaf1475a Binary files /dev/null and b/unsorted/OskitPatches/patch-oskit-0.97-jon_arney.diff.gz differ diff --git a/unsorted/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz b/unsorted/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz new file mode 100644 index 00000000..7d75a34e Binary files /dev/null and b/unsorted/OskitPatches/patch-oskit-0.97-kkraemer.diff.gz differ diff --git a/unsorted/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz b/unsorted/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz new file mode 100644 index 00000000..2fef6632 Binary files /dev/null and b/unsorted/OskitPatches/patch-oskit-0.97-sbrk_hack.diff.gz differ diff --git a/unsorted/PortToL4.mdwn b/unsorted/PortToL4.mdwn new file mode 100644 index 00000000..fb7f0004 --- /dev/null +++ b/unsorted/PortToL4.mdwn @@ -0,0 +1,42 @@ +**_The Hurd-L4 port has an [official page](http://www.gnu.org/software/hurd/hurd-l4.html) with more up-to-date information_** -- [[Main/OgnyanKulev]] - 05 Feb 2005 + +A group of one being led by Neal H. Walfield is working on porting the Hurd to the pistachio version of the L4 microkernel. This second generation microkernel provides a significantly different API than the one offered by the Mach microkernel, a first generation microkernel. One of the primary goals of the project, outside of porting the Hurd to L4, is to reevaluate the current Hurd abstractions and consider how they can be modified to be more general. + +I have no web page describing my efforts. There is a mailing list[1]. + +[1] + +-- Neal Walfield, 18 Sep 2002 + +Neal noted [1] that there are licensing issues being worked out so no code is yet released. His work was performed in the summer of 2002 at Karlsruhe. + +[1] + +-- [[Main/GrantBow]] - 21 Sep 2002 + +There are several important pages that are of interest for the L4 & hurd communities. + +* Main L4 home page - +* Hurd on L4 - +* Hurd on L4 - +* + +-- [[Main/GrantBow]] - 22 May 2002 + + + +-- [[Main/GrantBow]] - 24 Oct 2002 + +There was [discussion in October 2002](http://mail.gnu.org/pipermail/l4-hurd/2002-October/000727.html) about the differences between Hurd on Mach and Hurd on L4 with some interesting URLs. In the thread Okuji [responds](http://mail.gnu.org/pipermail/l4-hurd/2002-October/000728.html) confirming his document is two years old and outdated by the directions that Neal is taking in furthering this effort. The URLs in that email might be helpful to those learning more about Hurd and L4 ideas that were considered yet abandoned. + +-- [[Main/GrantBow]] - 04 Jan 2003 + +A "Porting GNU Hurd to L4" website: + +* + +-- [[Main/SebastianGabriel]] - 29 Sep 2003 + +The only valid L4-Hurd link on is + +-- [[Main/JoachimNilsson]] - 29 Sep 2003 diff --git a/unsorted/PosixSemaphores.mdwn b/unsorted/PosixSemaphores.mdwn new file mode 100644 index 00000000..be5586bd --- /dev/null +++ b/unsorted/PosixSemaphores.mdwn @@ -0,0 +1,13 @@ +Posix Semaphores are an optional part of pthreads. There is currently an implementation for Neal Walfields libpthread, which is included in the hurd sources tree. This implemention uses a mutex and a condition variable. The implmentation is in the mailing list archives at [ [http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html](http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html)](http://mail.gnu.org/archive/html/bug-hurd/2002-11/msg00316.html). + +Neal does not want to use this implementation because it adds the overhead of a condition variable. The condition variable imposes the following penalties: 1 extra spinlock/unlock 1 an extra call to a pthread cleanup function. + +The first penalty has virtually no cost because we know that we will never spin trying to get this spin lock because we already have a mutex lock outside the condition variable serializing accesses to the condition variable. + +The second may be more of a performance penalty, but it saves reimplmenting the code in pt-cond-signal.c pt-cond-wait.c, and pthread-timedwait.c . + +-- [[Main/JamesAMorrison]] - 19 Jan 2003 + +Moved page to Mach web. + +-- [[Main/GrantBow]] - 21 Jan 2003 diff --git a/unsorted/PosixThreads.mdwn b/unsorted/PosixThreads.mdwn new file mode 100644 index 00000000..f031b56f --- /dev/null +++ b/unsorted/PosixThreads.mdwn @@ -0,0 +1,21 @@ +## POSIX Threads for the Hurd + +One of the features the Hurd has been lacking up til now is support for POSIX threads, pthreads. It has been the show stopper for porting many useful applications and has sometimes been pointed out as one of the bigger problems with the GNU operating system. + +In 2002 however, all this came to an end when Neal Walfield implemented libpthreads for his work on L4 and decided to also make it work on GNUmach. + +Information on the library can be found on Neals web site. + +* + +## Previous Attempts + +Plans to implement pthreads for the Hurd has existed since, at least, 1999. Mark Kettenis [1] began work that was supposed to be useful on Linux as well. His work was continued by Igor Khavikine [2], who implemented most of it. Igor could however not continue his work so it was picked up by Jeroen Dekkers [3] and Ryan Golbeck. Their work can be found on Savannah, . + +1. +2. +3. + +---- + +Initial version -- [[Main/JoachimNilsson]] - 03 Nov 2002 diff --git a/unsorted/PppDaemon.mdwn b/unsorted/PppDaemon.mdwn new file mode 100644 index 00000000..f667d449 --- /dev/null +++ b/unsorted/PppDaemon.mdwn @@ -0,0 +1,6 @@ +There is no PPP solution present for the Hurd. + +* Filed Debian [um-ppp bug](http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no\&bug=147085) +* Clemmitt [asked about um-pppd](http://mail.gnu.org/pipermail/help-hurd/2002-October/006664.html) in this thread of 9 posts beginning Oct 10, 2002. + +-- [[Main/GrantBow]] - 20 Oct 2002 diff --git a/unsorted/RemoteDebugOskitMach.mdwn b/unsorted/RemoteDebugOskitMach.mdwn new file mode 100644 index 00000000..c260ce25 --- /dev/null +++ b/unsorted/RemoteDebugOskitMach.mdwn @@ -0,0 +1,195 @@ +# Remote Debug GNUmach + +# Table of Contents + +%TOC% + +# Booting oskit-mach with a serial console + +**Original Author:** Igor Khavkine **Last Updated:** Mon Jul 30 17:58:55 EDT 2001 + +---- + +## Introduction + +This document now has a wider audience. The OSKit branch of GNUmach has been merged with the main branch, HEAD. Please note that the instructions here are not tested with the latest stable release, GNUmach 1.3. + +Here you will find out how to access, build, bootstrap and debug the latest CVS version of the GNUmach kernel (the OSKit based 2.x series of GNUmach). + +## Why? + +Because it's covenient. If you have a second computer, but not a second monitor or keyboard, you can connect your second box to your main one using null-modem serial cables. Once that is done, you can configure the GRUB bootloader to use the serial port when starting up and boot [GNUmach](http://savannah.gnu.org/cgi-bin/viewcvs/hurd/gnumach/?only_with_tag=HEAD) (a.k.a [[OskitMach]]) without having to switch monitor cables or type blindly at a second keyboard. + +Also, [[OskitMach]] supports the GDB remote debugging protocol over a serial line. This way it is now possible to debug the running kernel relatively unobtrusively, because the debugger will not be running on the same machine. + +## How? + +First you need some equipment: two computers, each one should have at least one (two is preferable) free serial port(s) and one (or two) null-modem serial cable(s). + +While developing the kernel it might also be a good idea to use grub to get the Mach kernel via tftp from the same server you do the remote debugging and building on. This way you don't need to reboot the target to copy or build a new kernel on its hard drive. See the [[AdvancedGrubUsage]] document for more information on this. + +Last you need to follow the instructions given below. + +1. The first step is to the get source for oskit-mach and OSKit. + Currently the [St. Patrick's day release](ftp://flux.cs.utah.edu/flux/oskit/oskit-20020317.tar.gz), 2002-03-17, of the OSKit is the latest. Get the sources and compile them yourself, compile OSKit with debugging symbols if that is what you need. If you encounter errors while compiling, try removing anything that has to do with `unix` or `examples` from the file `modules.x86.pc`. + Then you need to get the sources for oskit-mach version of the GNU Mach kernel, available from the GNU CVS repository[3]. Previously you needed to check out the `gnumach` module with the flag `-roskit-branch`. Today the 2.0 branch of GNU Mach resides on the HEAD branch, so you don't have to provide any specifc branch information to get the correct version. Use the update command with `-rHEAD` to move from the oskit-branch to the HEAD branch. + Again now is your chance to compile oskit-mach with debugging symbols. + (More detailed instructions can be found in [[BuildingOskitMach]].) +2. Now you need to setup GRUB on your second box so it accepts input from a serial port while booting up. This is simple to do by adding the following lines to your `menu.lst` file, before any of the menu entries: + serial --unit=0 --speed=9600 + terminal serial + Unit refers to the serial port you wish to use (0 is COM1), and speed is optional. For more information see the GRUB documentation. +3. You need to make sure that your main box has the necessary utilities to communicate with your second box over a serial line. You can use a terminal emulator like _minicom_(1), _seyon_(1), _tip_(1), or a simple serial communication program _cu_(1) which comes with the GNU uucp package. Or if you feel really lazy you can use this hack: + stty raw + cat > /dev/ttyS1 # in one terminal window + cat /dev/ttyS1 # in a second terminal window +4. Now you have to make sure your computer has an at least partially setup Hurd partition. You can find instructions how to do that here [4,5]. Copy the oskit-mach kernel binary compressed with gzip to `/boot/oskit-mach.gz` and use the following command line[1] to boot it from GRUB: + kernel /boot/oskit-mach.gz -h CONS_COM=1 -d GDB_COM=2 BAUD=9600 root=device:hd0s2 -- +

-h

use serial console:

CONS_COM=1 (COM1)
CONS_COM=2 (COM2)
CONS_COM=3 (COM3)
CONS_COM=4 (COM4)

-d

enable serial port debugging, optional

GDB_COM=2

use a different port other then CONS_COM, default is to use the same as CONS_COM

BAUD=9600

use this baud rate, optional, default is 9600

--

delimits the arguments passed to the oskit from those to the kernel

root=device:hd0s2

tell gnumach which is your root partition, in this case it's hd0s2

+5. Now I suggest that you familiarize yourself with [the GDB documentation](http://vmlinux.org/doc/gdb/), especially on remote debugging. If you pass the `-d` boot flag to oskit-mach, then it will automatically insert a breakpoint at main() and wait for further instructions from GDB over the serial line. Here's a simple example of how to attach GDB to a remote target over a serial line: + $ script # record the debugging session + $ gdb # assume you're in the oskit-mach build dir. + (gdb) file kernel + (gdb) set remotebaud 9600 + (gdb) target remote /dev/ttyS1 + [...gdb attached, blah, blah, blah...] + (gdb) break panic + (gdb) continue + (gdb) continue + [...] + (gdb) quit + $ ^D # finish recording the session + This way you can catch any kernel panics (except for the really nasty ones and try to debug them). + I've noticed that once Mach is running under GDB, pressing C-c from GDB will not suspend it, this makes it hard to set additional breakpoints after the kernel is running. So optionally you can modify Mach to add a dummy system call that will be used only for setting breakpoints, and make a small program that calls it, you can use it whenever you want to pause the kernel and examine something under GDB. An example of how to do this is attached in Appendix A. + +TODO: OSKit overrides interrupts 1 and 3 in kern/x86/gate\_init.c:gate\_init. A patch that skips src->vector `= 1 || =` 3 have to be prepared and attached to this page. More robust solution is to make OSKit/GNUMach recognize when it's debugged and change vector table accordingly. + +Now you're all set to do some serious kernel hacking. I hope more people will take advantage of this opportunity. + +## Appendix A + +TODO: Move inline diff and code into 2 attached files: one for patching GNU Mach, and one for gdb-break.c. + +Apply this patch to oskit-mach to add a dummy system call: + + --- gdb-stub.diff --- + Index: kern/syscall_sw.c + =================================================================== + RCS file: /cvs/gnumach/kern/syscall_sw.c,v + retrieving revision 1.1.1.1.2.2 + diff -u -r1.1.1.1.2.2 syscall_sw.c + --- kern/syscall_sw.c 2001/04/05 06:52:47 1.1.1.1.2.2 + +++ kern/syscall_sw.c 2001/07/30 21:45:14 + @@ -98,6 +98,8 @@ + extern kern_return_t syscall_fipc_recv(); + #endif /* FIPC */ + + +/*XXX*/extern kern_return_t gdb_break_stub (); + + + mach_trap_t mach_trap_table[] = { + MACH_TRAP(kern_invalid, 0), /* 0 */ /* Unix */ + MACH_TRAP(kern_invalid, 0), /* 1 */ /* Unix */ + @@ -283,7 +285,14 @@ + MACH_TRAP(kern_invalid, 0), /* 126 */ + MACH_TRAP(kern_invalid, 0), /* 127 */ + MACH_TRAP(kern_invalid, 0), /* 128 */ + - MACH_TRAP(kern_invalid, 0), /* 129 */ + + MACH_TRAP(gdb_break_stub, 1), /* 129 */ + }; + + +volatile int gdb_break_stub (void *addr) /*XXX*/ + +{ + + void *dummy; + + dummy = addr; + + return 0; + +} + + + int mach_trap_count = (sizeof(mach_trap_table) / sizeof(mach_trap_table[0])); + --- end --- + +When starting an oskit-mach debug session with GDB set a break point at `gdb_break_stub`. Then use this program to invoke the system call when desired: + + --- gdb-break.c --- + /* Compile with: gcc -o gdb-break gdb-break.c gdb-break-stub.S */ + + #include + + #include + #include + + extern int gdb_break_stub (void *addr); + + int main () + { + kern_return_t err; + + err = gdb_break_stub (&main); + printf ("result from syscall: %s\n", strerror(err)); + + return 0; + } + --- end --- + --- gdb-break-stub.S --- + #include + + kernel_trap(gdb_break_stub,-129,1) + --- end --- + +## References + +* [1] OSKit documentation, section 1.6.3. +* [2] +* [3] +* [4] +* [5] + + vim:ts=8:tw=72:sw=8: + +---- + +This HowTo is (C) Copyright 2001 Igor Khavkine. + +Minor additions and grammatical fixups by [[JoachimNilsson]]. + +-- [[Main/JoachimNilsson]] - 14 May 2002 + +Additions on booting GNU Mach via TFTP + +-- [[Main/JoachimNilsson]] - 13 Jun 2002 + +Text formatting. + +-- [[Main/OgnyanKulev]] - 16 Dec 2002 diff --git a/unsorted/RequirementsForLiveCD.mdwn b/unsorted/RequirementsForLiveCD.mdwn new file mode 100644 index 00000000..03bd3884 --- /dev/null +++ b/unsorted/RequirementsForLiveCD.mdwn @@ -0,0 +1,54 @@ +# Requirements for a GNU/Hurd Live CD + +Here is an outline of the things that need to be done for producing a Live CD for the Hurd. Please add your comments and suggestions. + +## 1. We need to be able get a bootloader for CDs + +This is not much of a problem. I have already been successful (see below) in using [Grub](http://en.wikipedia.org/wiki/GRand Unified Bootloader) and the El-Torito HD emulation to boot [[GNUmach]] off a CD. There may be some minor tweaking of Grub code necessary to detect which device to use for booting (instead of having the user select their device (hd0,hd1,etc.) from the Grub menu). + +Using GRUB's stage2\_eltorito seems to work fine. + +## 2. We need a bootstrap filesystem translator + +This would be something like a statically linked iso9660fs translator. Compiling a statically linked iso9660fs translator is easy enough, though it doesn't boot. I don't currently know whether this is because the translator was never meant to be a bootstrap filesystem, or if there is a simple bug which has never been flushed out because the translator has never been used at boot time before. I've had trouble debugging this problem because I haven't yet figured out a way to use a remote gdb with gnumach. Theoretically you could use the "boot" command to overcome this problem, but "boot" for me mangles the terminal and exits in different manner than an actual boot. + +The iso9660fs translator works great, it just needs to be statically linked. + +## 3. We need a ramdisk to enable write access + +I think we could fake this with Farid Hajii's [memfs](http://www.fprintf.net/hurd/) translator and writing an ext2 filesystem to it. + +From the mem-fs README... + +> memfs-1 is a translator that provides a memory-based file of fixed size. This file can, just like bigfile, contain a regular filesystem. + +We could set a mem-fs translator anywhere on the CD you needed write access, including having softlinks to the contents of the root directory and chrooting to this new directory. + +For a quick and dirty memfs, you can do it right now with the following commands: + + # touch ./ramdisk + # touch ./tmpfs + # settrans -a ./ramdisk /hurd/storeio -Tcopy zero:50M + # /sbin/mke2fs -o hurd -b 4096 -F ./ramdisk + # settrans -a tmpfs /hurd/ext2fs.static ./ramdisk + # fsysopts --writable ./tmpfs + # cd tmpfs + # touch somenewfile + +Here we use two files ramdisk, and tmpfs that are already created on a readonly file system. For illustration purposes, they are touched beforehand. We run an active storeio translator on the ramdisk file to give us 50MB of RAM to work with, and then we make an ext2 filesystem on it. + +At this point we'd could copy the contents of the `/var` directory into the tmpfs, and then symlink `/var` to `/tmpfs/var`. The same goes for all other mutable dirs. + +This approach of putting an entire ext2 filesystem in a copy zero'd store has some drawbacks listed [here](http://lists.gnu.org/archive/html/bug-hurd/2000-12/msg00073.html). + +Those are the essentials. Here is a list of the things which would be nice to have for a Live-CD. + +* Knoppix like script for starting up X and [[GraphicEnvironment]] s ([[FluxBox]], Gnome...) +* DHCP support for easy network setup +* Hardware autodetection (Kudzu). +* Knoppix like script for installing to the hard drive or to bootable USB pendrive . +* (add your favorite feature here) + +Here is a mailing-list [thread](http://lists.debian.org/debian-hurd/2003/debian-hurd-200308/msg00172.html) discussing some of these issues. + +-- [[Main/GregBuchholz]] - 21 Oct 2003 -- [[Main/NagromNamreh]] - 29 Jan 2004 diff --git a/unsorted/SeenHurd.mdwn b/unsorted/SeenHurd.mdwn new file mode 100644 index 00000000..be9e1aba --- /dev/null +++ b/unsorted/SeenHurd.mdwn @@ -0,0 +1,71 @@ +# Hurd Sightings + +#### Table Of Contents + +%TOC% + +## Hurd People Sightings + +

[[Mailing_lists]]: Available mailing lists
[[IRC]]: +
[[WhoRunsGNU]]: +
[[HurdDevelopers]]: Who's who?
[[PersonalHurdPages]]: Users with Hurd wiki pages
[[UserGroups]]: Canadian, French & Russian
[[community/Meetings]]: Meetings with Hurd developer attendance.
[[community/Orkut]]: online "community" of interest - 89 members and counting
[[community/LiveJournal]]: online community

+ +## Hurd Press Sightings + +Here's a page for links that specifically talk about the Hurd in some way. See also, [[FunnyHurd]]. + +### Searching the Word "Hurd" in Some Famous Sites + +* [OSNews.com](http://www.osnews.com/search.php?search=hurd) +* [Slashdot.org](http://slashdot.org/search.pl?query=hurd) +* [KernelTrap.org](http://kerneltrap.com/index.php?or=6,16,40) +* [DebianPlanet.org](http://www.debianplanet.org/module.php?mod=search&edit%5Btype%5D%5Bnode%5D=1&keys=hurd) +* [Hungarian Unix portal](http://www.hup.hu/modules.php?name=News&new_topic=65) (in Hungarian) + +### Single Articles + +* [Interview with Hurd developer Marcus Brinkmann](http://portal.wikinerds.org/brinkmann-interview-mar2005) by Wikinerds Portal +* [A historic first step for the GNU/HURD-L4 microkernel port](http://portal.wikinerds.org/gnu-hurd-l4-first-program) by Wikinerds Portal +* [Interviews: Linus Torvalds: "Desktop Market has already started"](http://linuxtimes.net/modules.php?name=News&file=article&sid=145), in Linux Times, the viability of the Hurd is discussed a bit. +* [The Answer Gang 88: Linux Kernel Maintainability: Bees Can't Fly](http://www.linuxgazette.com/issue88/tag/3.html), in Linux Gazette, March 2003, issue 88. +* [Renaming Linux](http://www.infomaticsonline.co.uk/News/1135403) article on GNU OS (Hurd is a strongly related issue) - Sept 26, 2002 +* GNU's new [GNU/Linux FAQ](http://www.gnu.org/gnu/gnu-linux-faq.html) - Sept 24, 2002 +* [Debian Weekly News](http://www.debian.org/News/weekly/2002/37/) on Sarge & Hurd - Sept 24, 2002 +* Debian Release Manager Anthony Towns [notes on Sarge](http://lists.debian.org/debian-devel-announce-0209/msg00004.html) & Hurd - Sept 28, 2002 +* [New Console](http://www.kerneltrap.org/node.php?id=420) - Kernel Trap, Sept 18, 2002 +* [Radio CSJ](http://pagina.de/radiocsj) 104.5 FM discussions during "error 404" show - [Universidad Cat�olica de Chile](http://www.puc.cl) (Macul, Santiago, Chile), June 2002 +* [New GNU Hurd Kernel Released](http://slashdot.org/article.pl?sid=02/05/30/1547250&mode=nested&tid=117) [_sic_] - Slashdot, May 30, 2002 +* [GNU Mach 1.3 released!](http://www.debianplanet.org/article.php?sid=680&mode=thread&order=0&thold=0) - Debian Planet, May 29, 2002 +* [Running Hurd Under [[Distrib/BochsEmulator]] x86 Emulator](http://www.debianplanet.org/article.php?sid=673&mode=thread&order=0&thold=0) - Debian Planet, May 12, 2002 +* [Hurd-i386 gets new GLibc core](http://www.debianplanet.org/article.php?sid=668&mode=thread&order=0) by Jeff Bailey - Debian Planet, May 3, 2002 +* [IDG](http://www.idg.net/ic_829012_4394_1-3921.html) - IDG, March 11, 2002 +* [Interview with Neal Walfield](http://kerneltrap.org/article.php?sid=375) - Kernel Trap, Nov 12, 2001 + +### On Cover Pages + +* [freeX #4 2000](http://www.cul.de/data/freex42000inh.pdf) (PDF) - _Die andere Systemphilosophie_ auf Marcus Brinkmann + +%ATTACHURL%/freex42000cg.jpg + +* Linux Magazine France 10 + +%ATTACHURL%/lmf10\_1999.jpg diff --git a/unsorted/SeenHurd/lmf10_1999.jpg b/unsorted/SeenHurd/lmf10_1999.jpg new file mode 100644 index 00000000..85332658 Binary files /dev/null and b/unsorted/SeenHurd/lmf10_1999.jpg differ diff --git a/unsorted/SerialConsole.mdwn b/unsorted/SerialConsole.mdwn new file mode 100644 index 00000000..e4e5324d --- /dev/null +++ b/unsorted/SerialConsole.mdwn @@ -0,0 +1,28 @@ +# Grub + +To enable serial console support in Grub, you'll need to add a variation of the following to the top of your menu.lst: + + serial --unit=0 + terminal --timeout=2 serial console + +The first line enables the serial console on the first serial port (use --unit=1 to use the second). The second tells Grub to use either the serial console or the vga display on the first one on which input is sensed within two seconds of executing this command. If no input is detected, Grub defaults to the first which in this case is the serial console. + +# Hurd + +You'll first need to create a serial port device. Change to /dev and execute the following as root: + + ./MAKEDEV com0 + +Then add the following to /etc/ttys: + + com0 "/libexec/getty 9600" xterm-color on secure trusted console + +runttys won't automatically reread /etc/ttys. You need to send it a SIGHUP. + +If you are running your serial console on the second serial port, replace com0 with com1. + +# Using the Serial Port + +minicom is popular but sredird has a more integrated feel. + +-- [[NealWalfield]] - 12 Dec 2005 diff --git a/unsorted/Shopping.mdwn b/unsorted/Shopping.mdwn new file mode 100644 index 00000000..d9806e93 --- /dev/null +++ b/unsorted/Shopping.mdwn @@ -0,0 +1,13 @@ +Here are some e-shops from which you can buy stuff: T-Shirts and others. Free Software Foundation Inc. doesn't get percent from these sells. + +* [CafePress](http://www.cafeshops.com/hurd) + +-- [[Main/OgnyanKulev]] - 11 Feb 2004 + +Wait, so they are making money off the Hurd and not giving any to the FSF? Uh.... + +-- [[Main/GrantBow]] - 27 Feb 2004 + +OK, It was kind a stupid to add this sentence. What about removing it all this sentence? + +-- [[Main/OgnyanKulev]] - 27 Feb 2004 diff --git a/unsorted/Translation.mdwn b/unsorted/Translation.mdwn new file mode 100644 index 00000000..a5f78aa5 --- /dev/null +++ b/unsorted/Translation.mdwn @@ -0,0 +1,18 @@ +\* [[HurdCn]]: + +\* [[HurdNl]]: + +\* [[HurdPl]] : + +\* [[HurdEo]]: + +\* [[HurdHe]] : + +\* [[HurdEs]]: + +\* [[HurdFr]]: + +\* [[HurdIt]]: + +\* [[HurdRu]]: + diff --git a/unsorted/TranslatorExamples.mdwn b/unsorted/TranslatorExamples.mdwn new file mode 100644 index 00000000..0c2e5741 --- /dev/null +++ b/unsorted/TranslatorExamples.mdwn @@ -0,0 +1,61 @@ +## Introduction + +Translators are probably the most known feature of the Hurd, the first thing you should show when doing a demo. + +## run + +Couldn't manage to compile it, but allows you to do nice things with eg. fortune. + +## ftpfs + +hurd:~# settrans -c ftp /hurd/ftpfs 128.101.80.131:/ + +hurd:~# cd ftp + +hurd:~/ftp# ls + +debian debian-archive lost+found + +hurd:~/ftp# cd debian + +hurd:~/ftp/debian# ls + +README README.mirrors.txt doc ls-lR.patch.gz + +README.CD-manufacture README.non-US indices pool + +README.html README.pgp ls-lR project + +README.mirrors.html dists ls-lR.gz tools + +hurd:~/ftp/debian# cp README ~ + +hurd:~/ftp/debian# + +You have to specify the server address with its IP, or your computer will buy a farm or something. + +## ftpfs and hostmux + +currently (28/02/2004) not working, but should be. + +hurd:~# settrans -c ftp /hurd/hostmux /hurd/ftpfs / + +hurd:~# cd ftp + +hurd:~/ftp# cd ftp.debian.org + +-bash: cd: ftp.debian.org: Computer bought the farm + +hurd:~/ftp# host ftp.debian.org + +ftp.debian.org A 128.101.80.131 + +ftp.debian.org A 208.185.25.38 + +hurd:~/ftp# cd 128.101.80.131 + +-bash: cd: 128.101.80.131: Computer bought the farm + +## Articles about translators + +* [The GNU Hurd - Translators by Gael le Mignot](http://kilobug.free.fr/hurd/pres-en/html/node8.html) diff --git a/unsorted/TranslatorPages.mdwn b/unsorted/TranslatorPages.mdwn new file mode 100644 index 00000000..8e954521 --- /dev/null +++ b/unsorted/TranslatorPages.mdwn @@ -0,0 +1,51 @@ +

[[NeighborHurd]]: A concept possible with microkernels.
[[InteractiveTranslators]]: Translators that interact with user
[[TranslatorExamples]]: Examples of what you can do with translators
[[TranslatorWishList]]: Interesting file translator ideas

+ +Here are the translators that currently exist: + +* [[AuthTranslator]] +* [[CrashTranslator]] +* [[ExecTranslator]] +* [[ExtTwofsTranslator]] - (actually named ext2fs) Ext2 filesystems, also ext2fs.static +* [[FifoTranslator]] - also [[NewfifoTranslator]] (actually named new-fifo) +* [[FirmlinkTranslator]] +* [[FtpfsTranslator]] - ftp as a filesystem +* [[FwdTranslator]] +* [[HelloTranslator]] - also [[HellomtTranslator]] (actually named hello-mt) +* [[HostmuxTranslator]] +* [[IfsockTranslator]] +* [[InitTranslator]] +* [[IsofsTranslator]] +* [[KbdTranslator]] +* [[MachdefpagerTranslator]] - (actually named mach-defpager) +* [[hurd/translator/magic]] +* [[MouseTranslator]] +* [[NfsTranslator]] +* [[NullTranslator]] +* [[PasswordTranslator]] +* [[PfinetTranslator]] - also [[PflocalTranslator]] +* [[ProcTranslator]] +* [[SmbfsTranslator]] +* [[StoreioTranslator]] +* [[StreamioTranslator]] +* [[SymlinkTranslator]] +* [[TermTranslator]] +* [[TmpfsTranslator]] +* [[UfsTranslator]] - also ufs.static +* [[UsermuxTranslator]] + +Here are the contributed translators: + +* [[CryptTranslator]] - + +This is an old list and might need some updating, please check if you have a Hurd system that this list is accurate. + +-- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/unsorted/TranslatorWishList.mdwn b/unsorted/TranslatorWishList.mdwn new file mode 100644 index 00000000..38bd87d9 --- /dev/null +++ b/unsorted/TranslatorWishList.mdwn @@ -0,0 +1,193 @@ +## Introduction + +The idea behind file system translators is a powerful concept which hasn't recieved much attention in the mainstream computing world. So here is a list of interesting translators I've been able to dream up. I'm sure there are many more ideas floating around out there, so add them to the list! + +The [ferris project](http://witme.sourceforge.net/libferris.web/features.html) has some great ideas and code in the area of userspace dynamic filesystems, as has the [FUSE project](http://fuse.sourceforge.net/). + +## Audio\_cdfs + +A translator which produces a directory of \*.wav files when you have an audio CD in the drive. + +## Ogg + +This translator could be a sub-directory of the Audio\_cdfs translator and it would translate the \*.wav files into Ogg Vorbis/MP3 format. + +## CDDB + +Of course it would be a lot nicer if the above two translators didn't name their files something worthless like track001.ogg. So we would want a translator which would hook up with a database on the web and produce meaningful file names. + +## Crypto + +A cryptographic/steganographic seem like a nice match with the concept of user-land file systems. I like the idea of something like `settrans -a /secure stegfs --mpeg file001.mpg` + +## Revision control + +All of the empty space on your drive is now being wasted. Why not have a revision control translator which tracks changes to your documents? See also [this guy](http://www.linuxjournal.com/article.php?sid=5976). And then you'd do something like `cd /time-machine/2003/sept/14/` to see what your system looked like on the 14th of septempber 2003. + +## CVSFS + +See [cvsFS for Linux](http://cvsfs.sourceforge.net/). This provides a package which presents the CVS contents as mountable file system. It allows to view the versioned files as like they were ordinary files on a disk. There is also a possibility to check in/out some files for editing. A read-only version has been written by Stefan Siegl and is available at [Berlios](http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cvsfs4hurd/cvsfs/). + +## tar and gzip + +Rumor has it that they are on the way. Actually, a tar + gzip/bzip2 translator does exist (although it hasn't been used much...) : see [the Hurdextras project](http://savannah.nongnu.org/projects/hurdextras/) on Savannah. + +## ROM + +How about a translator which makes it look like you can write to read only media (like CDs), or change files which I don't have permission to change. This translator would make it seem like you could copy files to places where you normally couldn't. Think about combining this translator with the ftp translator and the tar and gzip translators. (cd /ftp/gnu.org/gnome.tar.gz/writes\_allowed; make install). It could be that unionfs does this very thing. + +## Super\_FIFO + +It's like a named pipe which is smart enough to start a process everytime something new tries to read from it. For example, let's say I have a script that reads in a JPEG image and spits out a smaller thumbnail \*.jpg to STDOUT. With a standard fifo (`mknod -p fifo`) this would almost works (`script big.jpg > fifo`). But what if there are two processes trying to read the fifo at once? Ick. And of course the standard way only works once without rerunning the command. I'm not quite sure what the syntax should look like, but I'm sure someone out there has a great idea waiting to happen. + +## Perl + +Perl is a wonderful language for hacking together something useful in a short amount of time. No concept is complete without being able to use it in a perl one-liner. And that goes for Hurd translators too. Right? + + #!/usr/bin/perl + use Hurd::translator; + + #file named "two" can produce an endless supply of twos, etc. (a la /dev/zero) + my $i=0; + for $filename ([zero one two three four]) + { + $libtrivfsread_codehash{$filename}= + sub{ $num_bytes=shift; my $data=$i; return chr($data) x $num_bytes; }; + #that's a hash of references to closures + $i++; + } + translator_startup(); + +A Perl translator has been started by [John Edwin Tobey](http://john-edwin-tobey.org/Hurd/) (pith). + +## Source code + +Here's a crazy thought. How about a translator for source code. You have a C source file like `hello.c` which is your normal everyday file. But there's a translator sitting underneath, so when you `cd hello.c` you get a directory with files like `main()` which represent the subroutines in `hello.c`. And of course you should be able to edit/remove those and have it modify the original source. + +## Libraries + +Here's an [idea](http://www.circlemud.org/~jelson/software/fusd/docs/node13.html) from the people making [userspace drivers in Linux](http://www.circlemud.org/~jelson/software/fusd/): + +* "One particularly interesting application of FUSD that we've found very useful is as a way to let regular user-space libraries export device file APIs. For example, imagine you had a library which factored large composite numbers. Typically, it might have a C interface--say, a function called `int *factorize(int bignum)`. With FUSD, it's possible to create a device file interface--say, a device called `/dev/factorize` to which clients can `write(2)` a big number, then `read(2)` back its factors. + +* This may sound strange, but device file APIs have at least three advantages over a typical library API. First, it becomes much more language independent--any language that can make system calls can access the factorization library. Second, the factorization code is running in a different address space; if it crashes, it won't crash or corrupt the caller. Third, and most interestingly, it is possible to use `select(2)` to wait for the factorization to complete. `select(2)` would make it easy for a client to factor a large number while remaining responsive to other events that might happen in the meantime. In other words, FUSD allows normal user-space libraries to integrate seamlessly with UNIX's existing, POSIX-standard event notification interface: `select(2)`." + +## Mail + +Am I off my rocker, or does an IMAP/POP translator sound like a good idea? It would make your remote mail servers look like local ones. Or what about a translator that makes a mbox format mail spool look like a directory. Can anyone think of a good use for an SMTP translator? + +## UUEncode + +How about a UUEncode translator for those places you can only store ASCII. Combine this with a NNTP translator and store your data in someone's Usenet archive. Or since, (as far as I know), there are no size limitations on file names in the Hurd, why not have a filesystem translator whose underlying store is a file name. (Now ls becomes cat). + +## Computation + +This is from the revenge of the command-line department. Make a directory translator whose contents are a result of the computation specified in the directory name. Here's an example... + + $ settrans -a /comp /hurd/computationfs + $ cd "/comp/3+4" + $ ls -l + total 0 + -rw-r--r-- 1 nobody users 0 Oct 16 11:41 7 + $ + $ cd "/comp/sqrt(2)" + $ ls -l + total 0 + -rw-r--r-- 1 nobody users 0 Oct 16 11:42 1.4142135623731 + $ + +...etc. Now think about your favorite GUI HTML editor and using File->Open on the following directory name, ``"/comp/for i in $( find / -name *.html ); do ln -s $i `basename $i`;done"`` Which would produce a directory listing with soft links to all of the \*.html files on your system. You could have all of the comforts of the shell from within that little File->Open dialog box. + +## Other + +Just found Wolfgang J�hrling's translator [wishlist](http://www.8ung.at/shell/trans.html). + +## Bochs + +A translator which works with [Bochs](http://bochs.sourceforge.net/) disk images would be nice. + +## Rollover + +A translator that uses a circular buffer to store log files. The translated node only contains the last N (mega,kilo)bytes. + +## Birthday + +A translator that provides an interface into the birthday program. + +You can cat your calendar, eg. bd/calendar/today bd/calendar/this-week or bd/calendar/this-month. + +And you could write new events into files located in bd/events/DATE/event-name. + +DATE is of the format the birthday expects DD/MM/YYYY. + +The contents of the file are any or none of the following birthday options: ann (An anniversary), bd (A birthday), ev (Some other event), wN (Warn N days in advance of date), toDATE (Event lasts until this DATE), forDAYS (Event runs for DAYS). + +You can optionally just edit the bd/birthdays file if you want to edit the configuration file by hand. It might make sense to write changes from bd/birthdays into ~/.birthdays. + + $ settrans -c bd /hurd/birthday -f ~/.birthdays + $ ls bd/ + birthdays calendar events + $ find bd -print + bd + bd/calendar + bd/calendar/daily + bd/calendar/this-week + bd/calendar/this-month + bd/events + bd/birthdays + $ + +## LVM + +A translator to access block devices from Linux's [Logical Volume Management](http://www.tldp.org/HOWTO/LVM-HOWTO/) would be an useful addition. + + # settrans -cap /dev/VolumeGroup0 /hurd/lvm /dev/PhysicalVolume0 /dev/PhysicalVolume1 ... + # ls /dev/VolumeGroup0/ + home + var + # settrans -cap /home /hurd/ext2fs /dev/VolumeGroup0/home + # settrans -cap /var /hurd/ext2fs /dev/VolumeGroup0/var + +Probably both [LVM2](http://sourceware.org/lvm2/) and the [Device-mapper](http://sourceware.org/dm/) need to be ported. + +## bridging translator + +A [bridging](http://bridge.sourceforge.net/faq.html) translator could improve the Hurd's networking facilities. + + # settrans -cap /dev/br0 /hurd/bridge -i eth0 -i eth1 ... + # settrans -cap /servers/socket/2 /hurd/pfinet -i /dev/br0 -a ... -g ... -m ... + +Perhaps Linux's bridging code and [utilities](http://bridge.sourceforge.net/) can be ported (or glued in) or code from one of the BSDs. + +## SSH translator + +Presenting remote file systems through SSH similar to what gnome-vfs does. + +## SMB translator + +Presenting remote file systems through Samba similar to what gnome-vfs does. Guiseppe Scrivano has worked on this and smbfs is available at [hurdextras](http://savannah.nongnu.org/cgi-bin/viewcvs/hurdextras/smbfs/). + +## Crontab translator + +Presenting a user's crontab in a filesystem where cron entries are files. + +## globlink + +Firmlink to a file according to a filename matching pattern. When a file goes away, the next file that is matched is automatically linked to. + + $ settrans -ac libfoo.so /hurd/globlink '/lib/libfoo*' + +## alphabetfs + +Organize a large group of files by their first letter. Present one subdirectory for each letter in the alphabet. + +## fsysoptsctl + +Send an fsysopts command to a set of translators. When you have a directory full of translators and you want to send each of them the same runtime option, this translator can do it for you. + + $ settrans -ac all /hurd/fsysoptsctl '/tmp/mystuff/*' + $ fsysopts all --update + +---- + +-- [[Main/GregBuchholz]] - updated 17 Oct 2003 diff --git a/unsorted/WebHome/hurd_sm_mf.png b/unsorted/WebHome/hurd_sm_mf.png new file mode 100644 index 00000000..26bb78b5 Binary files /dev/null and b/unsorted/WebHome/hurd_sm_mf.png differ diff --git a/unsorted/WhoRunsGNU.mdwn b/unsorted/WhoRunsGNU.mdwn new file mode 100644 index 00000000..ad1685b7 --- /dev/null +++ b/unsorted/WhoRunsGNU.mdwn @@ -0,0 +1,31 @@ +## Who runs GNU in production? + +On an official [GNU Project](http://www.gnu.org/gnu/thegnuproject.html) page I found a quote, attributed to Rabbi Hillel: + +> If I am not for myself, who will be for me? +> +>
+> +> If I am only for myself, what am I? +> +>
+> +> If not now, when? + +There are many now using test installations of Debian GNU/Hurd for testing and development. This page is set aside to list those sites using full GNU systems (GNU/Hurd) for non-testing and non-development purposes. + +## I run GNU! + +

Budi Rahardjo: http://hurd.indocisc.com, contact at budi@research.indociscNOSPAM.com
[[Main/JamesAMorrison]]: http://hurd.dyndns.org - +seems to be offline -- [[Community/weblogs/ArneBab]] - 2008-09-02

+ +### Testing and developer installations + +Installations for testing purposes are listed as [[public_hurd_boxen]]. + +These also contain the wiki server. diff --git a/unsorted/XattrHurd.mdwn b/unsorted/XattrHurd.mdwn new file mode 100644 index 00000000..d3856c1b --- /dev/null +++ b/unsorted/XattrHurd.mdwn @@ -0,0 +1,5 @@ +Roland McGrath has made [Linux support for Hurd's extensions to ext2 via Extended Attributes (xattr) interface](http://lists.gnu.org/archive/html/bug-hurd/2004-02/msg00108.html). This is important because it allows Hurd to be completely cross-installed in Linux. + +Michael Banck made some Debian precompiled Linux kernel packages that allow [using this xattr-hurd](http://lists.debian.org/debian-hurd/2004/09/msg00036.html). + +-- [[Main/OgnyanKulev]] - 18 Sep 2004 diff --git a/unsorted/Xfree86.mdwn b/unsorted/Xfree86.mdwn new file mode 100644 index 00000000..617508e5 --- /dev/null +++ b/unsorted/Xfree86.mdwn @@ -0,0 +1,109 @@ +# Setup XFree86 in GNU + +#### Table Of Content + +%TOC% + +This is a brief helper on how to setup X-Window on GNU. + +### Mouse & Keyboard + +See [[console]] for more details. + +First, set up the keyboard translator. Using `/hurd/kbd` and `/hurd/mouse` is not supported. You should instruct Hurd console to repeat keyboard events to `/dev/cons/kbd`, and mouse events to `/dev/cons/mouse`: + + # console -d vga -d pc_kbd --repeat=kbd -d generic_speaker \ + -d pc_mouse --repeat=mouse --protocol=ps/2 --console-node=/dev/cons /dev/vcs + +Symbolic links to repeaters should be created too: + + # ln -s /dev/cons/kbd /dev + # ln -s /dev/cons/mouse /dev + +### Selecting & Configuring Packages + +You will need several X packages. The `x-window-system-core` brings you most of what you need: + +* `xserver-xfree86` +* `xfonts-base` +* `xfonts-100dpi` +* `xfonts-75dpi` +* `xfonts-scalable` +* `xbase-clients` +* `xutils` +* `rxvt` +* ... as well as your window manager of choice: + * WindowMaker, `wmaker` + * FVWM, `fvwm` + * Blackbox, `blackbox` + * TWM, `twm` + +The recommended way of configuring X is using the `xserver-xfree86` debconf template, eg: + + # dpkg-reconfigure xserver-xfree86 + +It may be easier to just copy a working configuration from another operation system on the same computer and place it in `/etc/X11/XF86Config-4`, but this is discouraged as you would have to remove some sections by hand. + +**_IMPORTANT:_** when you configure X, make sure you do **NOT** enable the `speedo` and `dri` modules because they are currently broken. + +### Edit XF86Config-4 + +Now you have to edit the file manually to ensure that the mouse sections look like this: + + Section "InputDevice" + Identifier "Configured Mouse" + Driver "mouse" + Option "CorePointer" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + + Section "InputDevice" + Identifier "Generic Mouse" + Driver "mouse" + Option "SendCoreEvents" "true" + Option "Device" "/dev/mouse" + Option "Protocol" "osmouse" + EndSection + +You may also enable the Emulate3Buttons option, but nothing else will work. + + Option "Emulate3Buttons" "true" + +### Dynamic Linking + +The Hurd does not use `ld.so.conf`, it is necessary to add the following to `/etc/profile` to be sure that the libraries are found: + + LD_LIBRARY_PATH=/X11R6/lib:$LD_LIBRARY_PATH + +"This is a linker issue. GNU/Hurd expects that \`RPATH' is used, however, Debian takes certain measures to avoid this. Note that this does not cut it for suid binaries because of security implications. We expect to rectify this by using \`RUNPATH', which is specified in the new ELF standard." -- [Why does X not work?](http://www.gnu.org/software/hurd/faq.en.html#q4-8) + +### Starting X + +Finally, run + +`startx` + +However, there are several caveats to be aware of: + +* `xterm` does not work correctly; try `rxvt`. +* `update-menu` does not yet work. As such, there are no fine Debian menus. +* GNOME can now be ported with the new pthreads, but is still being worked on. [[WindowMaker]], [[TWM]], [[Blackbox]] and [[FVWM]] all work. + +### Graphical Environment + +See [[GNOME]] in Hurd . (?) + +---- + +Created. -- [[Main/RobertMillan]] - 21 Nov 2002 + +Some text formatting. -- [[Main/OgnyanKulev]] - 05 Dec 2002 + +Dito. -- [[Main/JoachimNilsson]] - 12 Jan 2003 + +`/hurd/kbd` is no longer supported. -- [[Main/OgnyanKulev]] - 11 Aug 2004 + +`/hurd/mouse` is deprecated. -- [[Main/OgnyanKulev]] - 21 Sep 2004 + +-c /dev/cons is now --console-note=/dev/cons -- Sven 01 May 2005 diff --git a/unsorted/ZallocPanics.mdwn b/unsorted/ZallocPanics.mdwn new file mode 100644 index 00000000..0b00d7ec --- /dev/null +++ b/unsorted/ZallocPanics.mdwn @@ -0,0 +1,43 @@ +The Hurd sometimes crashes with a kernel panic saying someting like: "Panic: zalloc failed: zone map exhausted". + +These panics are generally caused by some kind of kernel resource exhaustion, but there are several differnt reasons for that. + +It used to happen very often under heavy disk load (like large compile jobs), or in a reproducible test case by opening a large number of ports to /dev/null and then closing them all very quickly. The reason for this particular problem has been identified a while back: The multithreaded Hurd servers create a new worker thread whenever a new request (RPC) comes in while all existing threads are busy. When the server is hammered with lots of requests -- which happens both under heavy disk load, and when quickly closing many ports to one server -- it will create an absurd number of threads, causing the resource exhaustion. + +The Debian hurd package contains a patch by k0ro (Sergio Lopez), which fixes this by limiting the amount of created threads in a rather simplistic but very effective manner. This patch however hasn't been included in upstream CVS so far. A more elegant solution, suitable for upstream inclusion, would be desirable. + +Some panics still seem to happen in very specific situations, like the one described at . These are probably the result of bugs that cause port leaks, accidental fork bombs, or similar problems. + +In principle, resource exhaustion can also happen by normal use, though this is rather unlikely in the absence of bugs or malicious programs. Nevertheless, all these problems could be avoided (or limited in effect) by introducing some limits on number of processes per user, number of threads and ports per process/user etc. + +Trying to track down causes for the panics, I got some interesting results. (UPDATE: Many of my original observations were clearly related to the server thread explosion problem. To avoid confusion, I now removed these, as this is no longer an open issue.) + +* It all started with someone (probably azeem) mentioning that builing some package always crashes Hurd at the same stage of the Debian packaging process (UPDATE: Almost all of these panics when building packages were a result of the thread explosion and don't happen anymore.) +* Someone (maybe he himself) pointed out that this stage is characterized by many processes being quickly created and destroyed +* Someone else (probably hde) started some experimenting, to get a reproducible test case +* He realized that just starting and killing five child processes in quick succession suffices to kill some Hurd systems +* I tried to confirm this, but it turned out my system is more robust + +As I could never reproduce the problem with a small number of quickly killed processes, I can't say whether this problem still exists. While I could reproduce such an effect with first opening and then very quickly closing many ports (which is more or less what happens when quickly killing many processes), I needed really large numbers of processes/ports for that. The thread throtteling patch fixed my test case; but it seems unlikely that killing only five processes could have caused a thread explosion, so maybe hde's observation was a different problem really... + +I started various other experiments with creating child processes (fork bombs), resulting in a number of interesting observations: + +* Just forking a large number of processes crashes the Hurd reliably (not surprising) +* The number of processes at which the panic occurs is very constant (typicallly +-2) under stable conditions, as long as forking doesn't happen too fast +* The exact number depends on various conditions: + * Run directly from the Mach console, it's around 1040 on my machine (given enough RAM); however, it drops to 940 when started through a raw ssh session, and to 990 when run under screen through ssh (TODO: check number of ports open per process depending on how it is started) UPDATE: In a later test, I got somewhat larger numbers (don't remember exactly, but well above 1000), but still very constant between successive runs. Not sure what effected this change. + * It doesn't depend on whether normal user or root + * With only 128 MiB of RAM, the numbers drop slightly (like 100 less or so); no further change between 256 and 384 MiB + * Lowering zone\_map\_size in mach/kern/zalloc.c reduces the numbers (quite exactly half from 8 MiB to 4 MiB) + * There seems to be some saturation near 16 MiB however: The difference between 8 MiB and 16 MiB is significantly smaller + * Also, with 8 MiB or 4 MiB, the difference between console/ssh/screen becomes much more apparent (500 vs. 800, 250 vs. 400) + * With more than 16 MiB, Mach doesn't even boot +* Creating the processes very fast results in a sooner and less predictable crash (TODO: Check whether this is still the case with thread throtteling?) +* Creating processes recursively (fork only one child which forks the next one etc.) results in faster crash +* rpcinfo shows that child processes have more ports open by default, which is very likely the reason for the above observation +* Opening many ports from a few processes doesn't usually cause a system crash; there are only lots of open() failures and translator faults once some limit is reached... Seems the zalloc-full condition is better caught on open() than on fork() (TODO: investigate this further, with different memory sizes, different zone\_map\_size, different kinds of resources using zalloc etc.) +* After opening/leaking lots of ports to /dev/null (32768 it seems), the NULL translator somehow becomes disfunctional, and a new instance is started + +While most of these Observations clearly show an exhaustion of kernel memory which is not surprising, some of the oddities seem to indicate problems that might deserve further investigation. + +-- antrik (Last update: 12 Apr 2007) -- cgit v1.2.3 From 601bba64b7b2b4e5c499ea4258bb89743133ff5a Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 13 Jan 2009 22:02:28 +0100 Subject: Remove some pages. --- unsorted/CrossPlatformAliases.mdwn | 8 ---- unsorted/ExtTwofsTranslator.mdwn | 4 -- unsorted/FtpfsTranslator.mdwn | 7 ---- unsorted/HurdWikiCopyrightDiscuss.mdwn | 69 ---------------------------------- unsorted/HurdWikiMove.mdwn | 55 --------------------------- unsorted/HurdWnpp.mdwn | 19 ---------- unsorted/Translation.mdwn | 18 --------- 7 files changed, 180 deletions(-) delete mode 100644 unsorted/CrossPlatformAliases.mdwn delete mode 100644 unsorted/ExtTwofsTranslator.mdwn delete mode 100644 unsorted/FtpfsTranslator.mdwn delete mode 100644 unsorted/HurdWikiCopyrightDiscuss.mdwn delete mode 100644 unsorted/HurdWikiMove.mdwn delete mode 100644 unsorted/HurdWnpp.mdwn delete mode 100644 unsorted/Translation.mdwn (limited to 'unsorted') diff --git a/unsorted/CrossPlatformAliases.mdwn b/unsorted/CrossPlatformAliases.mdwn deleted file mode 100644 index 06a0e897..00000000 --- a/unsorted/CrossPlatformAliases.mdwn +++ /dev/null @@ -1,8 +0,0 @@ - # Aliases assume Debian GNU/Hurd mounted on /misc/hurd - # possibly via autofs /etc/auto.misc configuration and 'cd / && ln -s var/autofs/misc misc' - alias locatehurd="locate -d /misc/hurd/var/lib/locate/locatedb" - alias apt-cachehurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-cache" - alias apt-gethurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline apt-get" - # dselect requires APT_CONFIG due to dselect apt method - alias dselecthurd="APT_CONFIG=/misc/hurd/etc/apt/apt.conf.offline dselect --admindir /misc/hurd/var/lib/dpkg/" - alias dpkghurd="dpkg --root=/misc/hurd"= diff --git a/unsorted/ExtTwofsTranslator.mdwn b/unsorted/ExtTwofsTranslator.mdwn deleted file mode 100644 index d8f708fc..00000000 --- a/unsorted/ExtTwofsTranslator.mdwn +++ /dev/null @@ -1,4 +0,0 @@ -* [[ExtTwoSize]] - information about the limitation of partition size -* [[XattrHurd]] - Supports Hurd ext2 format extensions on Linux, images at - --- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/unsorted/FtpfsTranslator.mdwn b/unsorted/FtpfsTranslator.mdwn deleted file mode 100644 index 528a10f2..00000000 --- a/unsorted/FtpfsTranslator.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -ftpfs lets you access ftp servers via the filesystem. For detailed usage information use `/hurd/ftpfs --help` and `/hurd/ftpfs --usage`. - -### hostmux - -ftpfs ist best used with [[HostmuxTranslator]] - --- [[Main/PatrickStrasser]] - 13 Jul 2004 diff --git a/unsorted/HurdWikiCopyrightDiscuss.mdwn b/unsorted/HurdWikiCopyrightDiscuss.mdwn deleted file mode 100644 index ffa0b17b..00000000 --- a/unsorted/HurdWikiCopyrightDiscuss.mdwn +++ /dev/null @@ -1,69 +0,0 @@ -How about that notice from [[Main/PeterThoeny]]? Why don't we change the [[Hurd/WebPreferences]] for the Hurd web to say "Copyright (c) 2002 Free Software Foundation", instead of the usual "... the contributing authors". I think that would make the information we put in here easier to move around among different webs (not only Wikified ones...). Perhaps also add a notice on licensing? Like this: - - "Copyright (C) 2001, 2002 Free Software Foundation, Inc., - 59 Temple Place - Suite 330, Boston, MA 02111, USA - - Verbatim copying and distribution of this entire article is - permitted in any medium, provided this notice is preserved." - - Submitting material to the Hurd Wiki not only assigns the copyrights - to the Free Software Foundation it also put the material itself under - the GNU FDL, http://www.gnu.org/licenses/fdl.html - --- [[Main/JoachimNilsson]] - 14 May 2002 - -Don't do this - the material will not be assigned to the FSF until every contributor signed a paper form and filed it with the FSF. - -So simply claiming something is (C) FSF will not make it to be so, and it will not only have no effect, but also be confusing. - -Wiki has authentication, this is good. However, unless you have paper forms, all contributions remain with the original author. - -And if you had papers, you would have to disallow or moderate guest account contributions and either filter them out or change the copyright notice when they are filled in. This makes reusing Wiki-evolved content in free software projects by the FSF difficult btw, so don't expect major wiki-evolved content to be included in FSF manuals or so (this is not a problem, as long as everyone is aware of this limitation and keeps it in mind). - --- Marcus Brinkmann (no, not a Wiki-Name :) - -So what you are saying is basically this: - -1. We cannot assign the copyright to the FSF without the _paper_ work. -2. We _can_ use content from the FSF (as long as we keep all copyright information, of course), but any content evolved from this is unusable for GNU manuals. -3. Even if every newly registered user (and [[Main/TWikiGuest]] is disabled completely for the Hurd Web) agrees to our terms that agreement is useless without the _paper_ work. - -Oh, there is of course all the RCS diffs ... would that help, if we would like to have the Wiki content in GNU manuals? - --- [[Main/JoachimNilsson]] - 14 May 2002 - -If you have papers signed by the contributors, then any Guest added words (less than 10 lines?) can be filtered out of the Wiki using RCS. This is acceptable for GNU code, if I recall correctly. You may have to re-writen certain portions of the Wiki to use FSF contributed work only, though. - --- [[Main/SimonLaw]] - 16 May 2002 - -There seems to be a confusion of FDL vis-a-vis copyright-assignment here. FDL is like the all-important Step 1 which protects this content from being non-free. Copyright assignment is an Optional Step 2. - -Step2's not being feasible does not mean that we can't take Step 1. - -90% of GPL'ed software out there does not take Step 2. Step 2 helps by involving FSF in case someone violates our Step 1--the copyright itself. But i don't see why we cannot take Step 1 atleast. - --- [[Main/DeepakGoel]] - 01 Oct 2002 - -After an email discussion a while ago now between myself, Grant Bowman, RMS and Marcus Brinkmann the following results where achieved: - -* Copyright assignment can indeed be done without the extensive paperwork. - -* To implement this on a Wiki some provisions must be fulfilled: - * The user must **_actively_** select a checkbox or similar. - * The text to the checkbox can be _"I approve to also assign the copyrights of my work to the FSF"_ - -* This practise can be implemented today in the U.S., but in the EU there are still some things that need to be ironed out. Different countries still have differences in copyright law. However, the Swedish laws, where the Hurd wiki is located, do allow such a practise. - -The first step, mentioned above by [[Main/DeepakGoel]] we have now taken. The Hurd wiki is now licensed under the GNU FDL. The second step, assigning copyright will take a bit longer since the Perl scripts making out the TWiki engine must be altered. Also, we must first make sure that we all want to take the second step - we will also need to get the approval of assigning copyright of older material by those editors. - --- [[Main/JoachimNilsson]] - 01 Jan 2003 - -I don't feel taking the next step of copyright assignment is necessary, but I'm not opposed to it either. My concerns revolve around encouraging a wider participation and not actively putting up more barriers. Not many folks contribute as it is, unfortunately. - --- [[Main/GrantBow]] - 03 Jan 2003 - -Good, I've been hesitating too. Then there's no need for me to rush into getting the architecture of it working just yet. - -As it is right now, with at least the licensing (the FDL) in place, I'm quite content. - --- [[Main/JoachimNilsson]] - 03 Jan 2003 diff --git a/unsorted/HurdWikiMove.mdwn b/unsorted/HurdWikiMove.mdwn deleted file mode 100644 index 084e0ff2..00000000 --- a/unsorted/HurdWikiMove.mdwn +++ /dev/null @@ -1,55 +0,0 @@ -Many thanks to [[Main/JoachimNilsson]] for his work to establish and help update this Hurd Wiki! You have been extremely kind with your efforts in creating the new GNU skin and all of the expected and unexpected administrative work that's been needed to establish this Wiki. - -Now that the site is established, the traffic levels are growing and the value of the site is evident. This will affect the current host since its bandwidth is quite limited. Therefore a new permanent host must be located. We would like it to offer the following: - -* Free bandwidth -* At least one GiB of quota -* Availability 24/7 -* Shell access for at least one person for administrational purposes -* Possibly in the U.S. due to "click-n-approve" copyright assignment of material to the FSF (see [[HurdWikiCopyrightDiscuss]]). -* Regular backups -* Other? - -Comment on this page or email the maintainer - -Potential places to move Hurd Twiki to in order of preference: - -* savannah.gnu.org -* Some other \*.gnu.org site -* Other site in the U.S. or country with similar copyright laws. - ----- - -I favor removing gnu.org from the above list. There are copyright issues that are technically impossible to address in the way that RMS wants copyright assigned to all content hosted on gnu.org. While we probably could bend over backwards to accomodate it, fundamentally I think that this and other potential problems are not worth the effort of making this Hurd Twiki an official part of the GNU project. - -Technically I think that savannah.gnu.org might be possible but I will defer to others for a decision from this perspective. Assuming it's possible, I think we may have similar problems as above. - -I favor looking for another solution, an "other". - --- [[Main/GrantBow]] - 22 Sep 2002 - -Refactoring and updating. - -The copyright issues we have to straighten out anyway. If someone wants to make a CD set of the "manual" we have created here and that content later on gets misused we need to defend our rights. Using the GNU [[GNU/FreeDocumentationLicense]] and assigning the copyright to the FSF will help us achieve this. The FSF can fight for us instead of all the writers trying to get together. - --- [[Main/JoachimNilsson]] - 23 Oct 2002 - -Joachim, how are we doing on bandwidth usage? Is it growing, decreasing, about the same? What measure should we be looking at to keep an eye on the situation? I am sure lots of people really appreciate your hosting this site for free. I'm of course one of them! - --- [[Main/GrantBow]] - 01 Jan 2003 - -I have [the statistics](http://hurd.gnufans.org/webalizer/) under observation and thus far it looks very good. There really isn't much traffic at all, [compared to](http://vmlinux.org/webalizer/) the machine we host gnufans.org on. One tenth of the traffic to vmlinux.org. - -Occasionally I talk to one of the guys at [QuickNet](http://www.quicknet.se) about the hosting and our (vmlinux.org's) bandwidth usage. He has assured me that there is no problem at all, in fact, they have increased the overall capacity of their hosting capabilites, so now our traffic is no more than a drop in the ocean to them. :) - -I'll keep you (all) informed if there is any change in status of the hosting. - -Furthermore, I've been looking into the copyright assignment issues we talked about a while ago now. It seems RMS is right. At least in Sweden transfer of copyright can be made by a user in the way he descibed in the email conversation we had. The provision is that the user must **_actively_** select a checkbox or similar which says something like: - -* _"I hereby assign the copyrights of my work to the FSF"_ - -This means that the copyright is also owned by the FSF, the original author can never lose his rights to a work. The copyright assignment is useful when there is a license violation, bacause then the FSF can fight on behalf of the copyright owners without having to ask them all. - -Well, this post somewhat "nullifies" many of the claims made at the beginning of this topic. Maybe I should refactor it a bit to better suit the current circumstances? - --- [[Main/JoachimNilsson]] - 01 Jan 2003 diff --git a/unsorted/HurdWnpp.mdwn b/unsorted/HurdWnpp.mdwn deleted file mode 100644 index 49e069de..00000000 --- a/unsorted/HurdWnpp.mdwn +++ /dev/null @@ -1,19 +0,0 @@ -While Debian Developers and users use the official [WNPP](http://www.debian.org/devel/wnpp/) (Work Needed and Prospective Packages) page, a system of special bugs in the [Debian Bug Tracking System](http://bugs.debian.org/), this page is intended to give another location (and method) for giving feedback and provide status for developers of the Hurd. Please simply add a package name, the person's name sho's porting it, possibly with URL or as a separate page if you have relevant notes on the package. - -This data is for porting purposes only. Any conflict between the Debian BTS data and the data here should be resolved in favor of the Debian BTS. It's hoped this page will allow people to keep notes on packages that need some care. - -Packages in need of porting help: - -* Ported packages up for adoption - -* Ported orphaned packages - -* Packages currently being ported - -* Rewritten/replaced packages - * fakeroot - [status](http://mail.gnu.org/pipermail/bug-hurd/2002-May/008322.html) - -* Requested packages - * [Entropy Gathering Daemon](http://bugs.debian.org/145498) - Mako Hill - --- created 19 May 2002 diff --git a/unsorted/Translation.mdwn b/unsorted/Translation.mdwn deleted file mode 100644 index a5f78aa5..00000000 --- a/unsorted/Translation.mdwn +++ /dev/null @@ -1,18 +0,0 @@ -\* [[HurdCn]]: - -\* [[HurdNl]]: - -\* [[HurdPl]] : - -\* [[HurdEo]]: - -\* [[HurdHe]] : - -\* [[HurdEs]]: - -\* [[HurdFr]]: - -\* [[HurdIt]]: - -\* [[HurdRu]]: - -- cgit v1.2.3 From 27d13175ccd378e4d3531176276475dd84af5fed Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 19 Jan 2009 13:09:16 +0100 Subject: Move some pages, remove others that are either out of date or whose content is duplicated somewhere else. --- grub.mdwn | 72 ++++++++++++ grub/tftp_boot.mdwn | 42 +++++++ hurd/libstore.mdwn | 6 +- hurd/running/debian/CrossInstall.mdwn | 2 +- hurd/running/debian/after_install.mdwn | 2 +- hurd/running/distrib.mdwn | 4 +- hurd/running/qemu.mdwn | 2 +- hurd/translator.mdwn | 124 +-------------------- hurd/translator/wishlist_1.mdwn | 129 ++++++++++++++++++++++ hurd/translator/wishlist_2.mdwn | 189 ++++++++++++++++++++++++++++++++ unsorted/ABITransitionStatus.mdwn | 9 -- unsorted/AdvancedGrubUsage.mdwn | 42 ------- unsorted/AptConfOffline.mdwn | 28 ----- unsorted/BootProcess.mdwn | 36 ------ unsorted/GNOME.mdwn | 11 -- unsorted/GrubNotes.mdwn | 70 ------------ unsorted/InstallNotes.mdwn | 2 +- unsorted/InstallTips.mdwn | 2 +- unsorted/LuisBustamanteHurdPage.mdwn | 11 -- unsorted/NewMachHistory.mdwn | 27 ----- unsorted/OskitMach.mdwn | 2 +- unsorted/PppDaemon.mdwn | 6 - unsorted/TranslatorExamples.mdwn | 61 ----------- unsorted/TranslatorPages.mdwn | 51 --------- unsorted/TranslatorWishList.mdwn | 193 --------------------------------- 25 files changed, 449 insertions(+), 674 deletions(-) create mode 100644 grub.mdwn create mode 100644 grub/tftp_boot.mdwn create mode 100644 hurd/translator/wishlist_1.mdwn create mode 100644 hurd/translator/wishlist_2.mdwn delete mode 100644 unsorted/ABITransitionStatus.mdwn delete mode 100644 unsorted/AdvancedGrubUsage.mdwn delete mode 100644 unsorted/AptConfOffline.mdwn delete mode 100644 unsorted/BootProcess.mdwn delete mode 100644 unsorted/GNOME.mdwn delete mode 100644 unsorted/GrubNotes.mdwn delete mode 100644 unsorted/LuisBustamanteHurdPage.mdwn delete mode 100644 unsorted/NewMachHistory.mdwn delete mode 100644 unsorted/PppDaemon.mdwn delete mode 100644 unsorted/TranslatorExamples.mdwn delete mode 100644 unsorted/TranslatorPages.mdwn delete mode 100644 unsorted/TranslatorWishList.mdwn (limited to 'unsorted') diff --git a/grub.mdwn b/grub.mdwn new file mode 100644 index 00000000..a63ad181 --- /dev/null +++ b/grub.mdwn @@ -0,0 +1,72 @@ +# [GRUB](http://www.gnu.org/software/grub/) + +This section complements the [[InstallNotes]] with complete information regarding the GRUB boot loader. The syntax is different from Lilo's and so to scratch my own itch I'm creating this quick reference. The [Grub manual](http://www.gnu.org/software/grub/manual/grub.html) is another good reference. + +* update-grub is **Debian specific** and very nice. It will automatically create a /boot/grub/menu.lst file for the kernels in /boot/. It will also append a manually configured set for other partitions like the GNU/Hurd. +* grub-floppy is a **Debian specific** boot floppy creation script. +* mkbimage is a **Debian specific** boot disk image creation script. +* contains a Debian packaged makefile for creating CD & floppy images. Looks like it doesn't work properly. If you fix it, please send patches to the maintainer. +* essential GRUB commands & disk syntax + * root + * kernel + * module + * boot +* sample file + + title GNU/Linux + root (hd0,11) + kernel /boot/vmlinuz-2.4.18 root=/dev/hda12 ro + initrd /boot/initrd.img-2.4.18 + savedefault + + title GNU + root (hd0,15) + kernel /boot/oskit-mach root=device:hd0s16 -- + 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) + savedefault + + title DOS + rootnoverify (hd0,0) + chainloader +1 + +-- [[Main/GrantBow]] - 01 Oct 2002
-- [[Main/GrantBow]] - 22 Dec 2002 + +Another example, just as good, but a lot easier to read. The backslash at the end of each line is to "escape" the enter-key. So make sure there are no spaces following the backslashes! + + title GNU/Linux (Linux 2.4.18) + root (hd0,11) + kernel /boot/vmlinuz-2.4.18 root=/dev/hda12 ro + initrd /boot/initrd.img-2.4.18 + savedefault + + title GNUmach 1.3 + root (hd0,1) + kernel /boot/gnumach.gz root=device:hd0s2 + module /hurd/ext2fs.static --readonly \ + --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 GNUmach 1.90 (CVS) + root (hd0,1) + kernel /boot/oskit-mach.gz root=device:hd0s2 -- + module /hurd/ext2fs.static --readonly \ + --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) + +Note the differences between GNUmach and OSKit-Mach. The latter **needs** the two dashes after the root specification! + +-- [[Main/JoachimNilsson]] - 09 Nov 2002 diff --git a/grub/tftp_boot.mdwn b/grub/tftp_boot.mdwn new file mode 100644 index 00000000..8e307b4f --- /dev/null +++ b/grub/tftp_boot.mdwn @@ -0,0 +1,42 @@ +## Advanced Grub + +[Grub](http://www.gnu.org/software/grub/) is a capable boot loader. This document is intended to capture some of its most interesting features and try to explain them a bit better than the texinfo documentation. + +### Debian Grub + +The Debian grub packages do not have networking enabled, so you have to apt-get the source, modify the debian/rules file to include --enable-network-card and dpkg-buildpackage to get a .deb of grub that supports TFTP. + +1. cd /usr/src/debian +2. apt-get source grub +3. cd grub-\_VERSION\_ +4. Add `--enable-tulip` or similar for your NIC to the `./configure` line of the `configure-stamp` target in the `debian/rules` file. +5. `dpkg-buildpackage` (as `root`) +6. `cd ..` +7. `dpkg -i grub*.deb` +8. cp /lib/grub/\_ARCH\_/\* /boot/grub/, e.g., _ARCH_ is `i386-pc` +9. Edit your `/boot/grub/menu.lst` (see below) +10. If your boot disk is `/dev/hda` ==> `grub-install (hd0)` + +### TFTP Boot + +Using trivial ftp to load a kernel is one of the best features of Grub. Here is how it is done. + +The `menu.lst` can look something like this: + + ifconfig --address=192.168.1.2 --server=192.168.1.1 + root (nd) + kernel /gnu/boot/oskit-mach.gz root=device:hd0s2 -- + root (hd0,1) + 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) + +**Note: Make sure there are NO spaces after the trailing backslases (\\)!!** + +For more information on GNUmach modules lines and installation setup, see [[Hurd/InstallNotes]] + +-- [[Main/JoachimNilsson]] - 13 Apr 2005 diff --git a/hurd/libstore.mdwn b/hurd/libstore.mdwn index ab649ebc..6b81691b 100644 --- a/hurd/libstore.mdwn +++ b/hurd/libstore.mdwn @@ -1,4 +1,5 @@ -[[meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] +[[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 @@ -31,3 +32,6 @@ device node below `/dev`... At you can find some effort to make some crypto store. + +At , another package +can be found. diff --git a/hurd/running/debian/CrossInstall.mdwn b/hurd/running/debian/CrossInstall.mdwn index 9a07424e..1cde150c 100644 --- a/hurd/running/debian/CrossInstall.mdwn +++ b/hurd/running/debian/CrossInstall.mdwn @@ -34,7 +34,7 @@ Now the program starts retrieving all the necessary base packages. ### Preparing to reboot -When all packages have been extracted we must prepare [[GrubNotes]] 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. +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) diff --git a/hurd/running/debian/after_install.mdwn b/hurd/running/debian/after_install.mdwn index b795fd2b..4cdcaea9 100644 --- a/hurd/running/debian/after_install.mdwn +++ b/hurd/running/debian/after_install.mdwn @@ -35,7 +35,7 @@ In order to use DHCP, you need to install the `dhcp-client` package and run `dhc 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 the [[GrubNotes]] for this. +you. See [[GRUB]]'s page for this. # Setup `apt-get` diff --git a/hurd/running/distrib.mdwn b/hurd/running/distrib.mdwn index b0a6badd..935c0c2d 100644 --- a/hurd/running/distrib.mdwn +++ b/hurd/running/distrib.mdwn @@ -30,8 +30,8 @@

[[GrubNotes]]: A quick reference and explanation. There's also a topic for the new [[GrubConf]].
[[GRUB]]: A quick reference and explanation.

diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn index 7e4816f5..f13ef5c8 100644 --- a/hurd/running/qemu.mdwn +++ b/hurd/running/qemu.mdwn @@ -23,7 +23,7 @@ volunteers and may not have been tested extensively. # What is Needed to create a QEMU image 1. First thing is to install [[/QEMU]]. -2. A [grub](http://www.gnu.org/software/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 an renamed to `floppy.img`. Alternatively, the Debian grub-disk package (up till version 0.97-28) is fine as well. +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 an 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. diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn index 0823f0db..0cfcc5fa 100644 --- a/hurd/translator.mdwn +++ b/hurd/translator.mdwn @@ -73,123 +73,7 @@ available. * ... -# Translator wishlist - -* [[devfs]] - -* FUSE(fuse.sourceforge.net/) compatilbility library. : just modify FUSE apps a and compile little to work as translator :-) - -* File Finder. (uses find, grep, a combination or a custom command (htdig, mp3 info) - * Files found will be available under one directory and then can be used like a normal directory - * usefull to generate Albums, Share only resulting files over the et, etc.. - * The filefinder can be scheduled or can be connected over some ipc like dbus to the VFS system if any to keep a watch for new files. - -* GNOKII, BitPim and openobex as translators - * grep through your SMSs! - * share your addressbook! - * "Attach" that funny SMS/MMS to your email. - * "svn commit" your joke collection :-D - -* Real Language Translator [[br]] - * cat /usr/translator/de-en/usr/share/doc/something.txt should take /usr/share/doc/something.txt , submit it to google's website and bring back results. - -* Mozilla Bookmarks = del.ici.ous - * Need more explanation ? ;-) - -* - * having a directory structure for a file can allow to "svn commit" the hnb document in a more "node-safe" manner, thus allowing multiple people to work on the same hnb document. - * This must be fairly easy as HNB can already export to XML and XMLfs already exists. - -* DavFS - * Just setup a 'WebDav share' as a directory. The implimentation of the protocol is already available in nautilus and konqueror. - -* Compiled form of your project - * you have your project in /somedir/project with source in /somedir/project/src .. /somedir/project/bin should always have the compiled version.. is it possible? - * The source has to have a MakeFile. - * creating /somedir/project/bin-somearch should aotomatically crosscompile - * Seems feasible for a small project. - -* Report generation FrameWork - an idea to be hugged by app developers..not kernel developers. - * You have financial data in some Spreadsheet like format in /yourFinance directory - * You add report templates to /yourFinance/repTemplates - * Once you save data in /yourFinance the next cat /yourFinance/reports/areportname will give you an uptodate report. - * This will be usefull for any purpose including serving by static page web servers, sharing over samba/nfs/ftp etc.! - * The advantage is any save to the spreadsheet will update the report.. not just from one software. - -* SVN (Subversion suite) - * like [[cvsfs]]. /svndir/version/version-no should automatically have subversion - * I think it is nice to write a generalised version control system framework library which will help in writing version control translators and other tools easily. - -* Flexi-acls - * First of all - Can this be done? : A translator bound to a directory must be able to access the contents of the directory which would have been accessible in the absence of the translator.. - * This will enable to wirte translators that can implement custom "Access Control Lists". Just imagine having advanced ACLs even if underlying FileSystem is dumb! Imagine changing the type of ACLs implemented with Just two commands - one to unattach previous translator and the next to attach a different ACL translator! The ACLs themselves may be stored in a different directory - -* The translator manager! - * Some translators will need to be inserted automatically - like for eg: hardware drivers .. - * Each hardware translator will pubish its capabilities. - * The "top" translator will query the capabilities of different hardware and match capabilities with the "slave" translators. That is it's only Job. - * The control is then handed over to the slave translator. - * The ranking not only looks who can handle the "most" capabilites of the hardware. If it finds that multiple translators can handle the same hardware, It will use other parameters to choose between them.. like may be the size in memory? The revision date? Stability (inferred from version number)? And to go to the extreme, the profiling data of the driver ;-P - * Advantage : The best driver wins! - -* An eg. Skip it if you understood the above :-): - * You have a driver that can handle VGA + SVGA + Super3d acceleration + Particle graphics + Works for nvidea card. - * You have a driver that can handle SVGA + VGA . - * You have a driver that can handle VGA. - * Case 1: Your card: A VGA card with some extra fonts.. - * First the VGA driver will be quireied .. ok can handle essential capability. - * Next SVGA driver: can handle but has extra module.. unnecassary weight . - * The Nvidia driver: can handle , but again unnecassary weight : ruled out. - * Winner : VGA driver: - * Case 2: Your card An SVGA card: - * First the VGA driver will be quireied .. ok can handle one essential capability. - * Next SVGA driver: can handle essential and one extra capability no extra weight.. - * The Nvidia driver: can handle , but unnecassary weight : ruled out. - * Winner : SVGA driver.. - * Case 3 : You have an VGA .. but no VGA driver .. then the SVGA driver would win. - -* Sound Server - * /ahsa - stands for Advanced HURD sound architecture :-) Just a temporary name .. for fun. - * /ahsa/out - directory wich will hold "plug"s where apllications come and join the server .. see below. - * /ahsa/out/mixer - main mixer - * /ahsa/out/nextfree - the file when "cat"ed gives the number of the next free plug - * /ahsa/plugins/ - info about available plugins - * /ahsa/out/[1..n]/ - dynamically generated directories for applications to plug on.. - * /ahsa/out/[1..n]/data this is where you should do a "cat somerawsoundfile>/ahsa/out/`cat /ahsa/nextfree`/data" - * /ahsa/out/[1..n]/plugins - the plugin stack .. volume is also a plugin.. - * /ahsa/out/[1..n]/plugins/[1..m]/ - echo "plugin param1 param2 param3" > /ahsa/out/[1..n]/plugins/`cat /ahsa/out/[1..n]/plugins/nextfree`/add - * /ahsa/out/[1..n]/plugins/[1..m]/params/{param1.. paramn} - * /ahsa/out/[1..n]/data.out - can be catted to get data processed through the server - * /ahsa/in - similar to /ahsa/out .. with except for an extra file to choose input devices. - * /ahsa/devs/{1..n} - devices detected .. can be dynamic .. there are usb soundcards and and midi devices. - * /ahsa/out/[1..n]/plugins/[1..m]/0/params/dev - * Dont get tempted for :/ahsa/out/[1..n]/params/{rate, channels, and other stuff} - * that goes into /ahsa/out/[1..n]/plugins/0/params if /ahsa/out/[1..n]/plugins/0/detected == "headerless audio" - * There are a lot more things I can continue about the "sound server" .. The Ideas simply dont seem to exhaust.. - * Some features/advantages - * set output's translator plugin as ordinary text -- have text to speech conversion done by sound server! - * Create and apply plugin presets by simply copying directories! - * Me getting dizzy thinking of the zillion more advantages. - * If you are really doing some ordinary output , all you need to do is "cat" data into next free "plug" and everything will be autodetected including the format of the data and sent to the final sound "merge"r - * Dizzy ... - -* /usr/share/menu !!!! extension for package management idea .. - * cat mymenuitem.menu >> /usr/share/menu/menu - * cat /usr/share/menu/debian/kde ... :-) - -* Spam/Malware Control - * /usr/antimalware/ - put your mail here.. it will automatically be scanned. when finished it will vanish from here .. - * /usr/antimalware/clean - ... and pop out from here - * /usr/antimalware/malware - or here. - -* NetDevice - * !JustImagine(tm)... settrans -ac /netdevices /hurd/netdevfs - [ host | net ] - * One can access device files remotely - * This could be acheived by allowing translators talk to one another over a network - * This will need translators to catch and handle ioctls (if there is such a thing in HURD). - * The device server which will listen to requests from the translators can be run even on a Linux machine!!! - * !JustImagine(tm)... accessing the crwriter/webcam on that GNU/Linux machine on the network using cdrecord of your local hurd machine! - * !JustImagine(tm)... running GNU/HURD on a minimalistic GNU/Linux(but with all the drivers) through a specially modified and optimised Qemu. The device server runs on the host machine, and the client translators access over the virtual network created by Qemu. You got most of the drivers for free! - -* Emacs File VFS - * I came to know from my Emacs loving friend that there are lots of VFS handlers in Emacs.. I was wondering if there can be translator which can tap into these Emacs VFS handlers. +# Translator Wishlists + + * [[wishlist_1]] + * [[wishlist_2]] diff --git a/hurd/translator/wishlist_1.mdwn b/hurd/translator/wishlist_1.mdwn new file mode 100644 index 00000000..6a4d591a --- /dev/null +++ b/hurd/translator/wishlist_1.mdwn @@ -0,0 +1,129 @@ +[[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]]."]]"""]] + +* [[devfs]] + +* FUSE(fuse.sourceforge.net/) compatilbility library. : just modify FUSE apps a and compile little to work as translator :-) + +* File Finder. (uses find, grep, a combination or a custom command (htdig, mp3 info) + * Files found will be available under one directory and then can be used like a normal directory + * usefull to generate Albums, Share only resulting files over the et, etc.. + * The filefinder can be scheduled or can be connected over some ipc like dbus to the VFS system if any to keep a watch for new files. + +* GNOKII, BitPim and openobex as translators + * grep through your SMSs! + * share your addressbook! + * "Attach" that funny SMS/MMS to your email. + * "svn commit" your joke collection :-D + +* Real Language Translator [[br]] + * cat /usr/translator/de-en/usr/share/doc/something.txt should take /usr/share/doc/something.txt , submit it to google's website and bring back results. + +* Mozilla Bookmarks = del.ici.ous + * Need more explanation ? ;-) + +* + * having a directory structure for a file can allow to "svn commit" the hnb document in a more "node-safe" manner, thus allowing multiple people to work on the same hnb document. + * This must be fairly easy as HNB can already export to XML and XMLfs already exists. + +* DavFS + * Just setup a 'WebDav share' as a directory. The implimentation of the protocol is already available in nautilus and konqueror. + +* Compiled form of your project + * you have your project in /somedir/project with source in /somedir/project/src .. /somedir/project/bin should always have the compiled version.. is it possible? + * The source has to have a MakeFile. + * creating /somedir/project/bin-somearch should aotomatically crosscompile + * Seems feasible for a small project. + +* Report generation FrameWork - an idea to be hugged by app developers..not kernel developers. + * You have financial data in some Spreadsheet like format in /yourFinance directory + * You add report templates to /yourFinance/repTemplates + * Once you save data in /yourFinance the next cat /yourFinance/reports/areportname will give you an uptodate report. + * This will be usefull for any purpose including serving by static page web servers, sharing over samba/nfs/ftp etc.! + * The advantage is any save to the spreadsheet will update the report.. not just from one software. + +* SVN (Subversion suite) + * like [[cvsfs]]. /svndir/version/version-no should automatically have subversion + * I think it is nice to write a generalised version control system framework library which will help in writing version control translators and other tools easily. + +* Flexi-acls + * First of all - Can this be done? : A translator bound to a directory must be able to access the contents of the directory which would have been accessible in the absence of the translator.. + * This will enable to wirte translators that can implement custom "Access Control Lists". Just imagine having advanced ACLs even if underlying FileSystem is dumb! Imagine changing the type of ACLs implemented with Just two commands - one to unattach previous translator and the next to attach a different ACL translator! The ACLs themselves may be stored in a different directory + +* The translator manager! + * Some translators will need to be inserted automatically - like for eg: hardware drivers .. + * Each hardware translator will pubish its capabilities. + * The "top" translator will query the capabilities of different hardware and match capabilities with the "slave" translators. That is it's only Job. + * The control is then handed over to the slave translator. + * The ranking not only looks who can handle the "most" capabilites of the hardware. If it finds that multiple translators can handle the same hardware, It will use other parameters to choose between them.. like may be the size in memory? The revision date? Stability (inferred from version number)? And to go to the extreme, the profiling data of the driver ;-P + * Advantage : The best driver wins! + +* An eg. Skip it if you understood the above :-): + * You have a driver that can handle VGA + SVGA + Super3d acceleration + Particle graphics + Works for nvidea card. + * You have a driver that can handle SVGA + VGA . + * You have a driver that can handle VGA. + * Case 1: Your card: A VGA card with some extra fonts.. + * First the VGA driver will be quireied .. ok can handle essential capability. + * Next SVGA driver: can handle but has extra module.. unnecassary weight . + * The Nvidia driver: can handle , but again unnecassary weight : ruled out. + * Winner : VGA driver: + * Case 2: Your card An SVGA card: + * First the VGA driver will be quireied .. ok can handle one essential capability. + * Next SVGA driver: can handle essential and one extra capability no extra weight.. + * The Nvidia driver: can handle , but unnecassary weight : ruled out. + * Winner : SVGA driver.. + * Case 3 : You have an VGA .. but no VGA driver .. then the SVGA driver would win. + +* Sound Server + * /ahsa - stands for Advanced HURD sound architecture :-) Just a temporary name .. for fun. + * /ahsa/out - directory wich will hold "plug"s where apllications come and join the server .. see below. + * /ahsa/out/mixer - main mixer + * /ahsa/out/nextfree - the file when "cat"ed gives the number of the next free plug + * /ahsa/plugins/ - info about available plugins + * /ahsa/out/[1..n]/ - dynamically generated directories for applications to plug on.. + * /ahsa/out/[1..n]/data this is where you should do a "cat somerawsoundfile>/ahsa/out/`cat /ahsa/nextfree`/data" + * /ahsa/out/[1..n]/plugins - the plugin stack .. volume is also a plugin.. + * /ahsa/out/[1..n]/plugins/[1..m]/ - echo "plugin param1 param2 param3" > /ahsa/out/[1..n]/plugins/`cat /ahsa/out/[1..n]/plugins/nextfree`/add + * /ahsa/out/[1..n]/plugins/[1..m]/params/{param1.. paramn} + * /ahsa/out/[1..n]/data.out - can be catted to get data processed through the server + * /ahsa/in - similar to /ahsa/out .. with except for an extra file to choose input devices. + * /ahsa/devs/{1..n} - devices detected .. can be dynamic .. there are usb soundcards and and midi devices. + * /ahsa/out/[1..n]/plugins/[1..m]/0/params/dev + * Dont get tempted for :/ahsa/out/[1..n]/params/{rate, channels, and other stuff} + * that goes into /ahsa/out/[1..n]/plugins/0/params if /ahsa/out/[1..n]/plugins/0/detected == "headerless audio" + * There are a lot more things I can continue about the "sound server" .. The Ideas simply dont seem to exhaust.. + * Some features/advantages + * set output's translator plugin as ordinary text -- have text to speech conversion done by sound server! + * Create and apply plugin presets by simply copying directories! + * Me getting dizzy thinking of the zillion more advantages. + * If you are really doing some ordinary output , all you need to do is "cat" data into next free "plug" and everything will be autodetected including the format of the data and sent to the final sound "merge"r + * Dizzy ... + +* /usr/share/menu !!!! extension for package management idea .. + * cat mymenuitem.menu >> /usr/share/menu/menu + * cat /usr/share/menu/debian/kde ... :-) + +* Spam/Malware Control + * /usr/antimalware/ - put your mail here.. it will automatically be scanned. when finished it will vanish from here .. + * /usr/antimalware/clean - ... and pop out from here + * /usr/antimalware/malware - or here. + +* NetDevice + * !JustImagine(tm)... settrans -ac /netdevices /hurd/netdevfs - [ host | net ] + * One can access device files remotely + * This could be acheived by allowing translators talk to one another over a network + * This will need translators to catch and handle ioctls (if there is such a thing in HURD). + * The device server which will listen to requests from the translators can be run even on a Linux machine!!! + * !JustImagine(tm)... accessing the crwriter/webcam on that GNU/Linux machine on the network using cdrecord of your local hurd machine! + * !JustImagine(tm)... running GNU/HURD on a minimalistic GNU/Linux(but with all the drivers) through a specially modified and optimised Qemu. The device server runs on the host machine, and the client translators access over the virtual network created by Qemu. You got most of the drivers for free! + +* Emacs File VFS + * I came to know from my Emacs loving friend that there are lots of VFS handlers in Emacs.. I was wondering if there can be translator which can tap into these Emacs VFS handlers. diff --git a/hurd/translator/wishlist_2.mdwn b/hurd/translator/wishlist_2.mdwn new file mode 100644 index 00000000..3ea68999 --- /dev/null +++ b/hurd/translator/wishlist_2.mdwn @@ -0,0 +1,189 @@ +## Introduction + +The idea behind file system translators is a powerful concept which hasn't recieved much attention in the mainstream computing world. So here is a list of interesting translators I've been able to dream up. I'm sure there are many more ideas floating around out there, so add them to the list! + +The [ferris project](http://witme.sourceforge.net/libferris.web/features.html) has some great ideas and code in the area of userspace dynamic filesystems, as has the [FUSE project](http://fuse.sourceforge.net/). + +## Audio\_cdfs + +A translator which produces a directory of \*.wav files when you have an audio CD in the drive. + +## Ogg + +This translator could be a sub-directory of the Audio\_cdfs translator and it would translate the \*.wav files into Ogg Vorbis/MP3 format. + +## CDDB + +Of course it would be a lot nicer if the above two translators didn't name their files something worthless like track001.ogg. So we would want a translator which would hook up with a database on the web and produce meaningful file names. + +## Crypto + +A cryptographic/steganographic seem like a nice match with the concept of user-land file systems. I like the idea of something like `settrans -a /secure stegfs --mpeg file001.mpg` + +## Revision control + +All of the empty space on your drive is now being wasted. Why not have a revision control translator which tracks changes to your documents? See also [this guy](http://www.linuxjournal.com/article.php?sid=5976). And then you'd do something like `cd /time-machine/2003/sept/14/` to see what your system looked like on the 14th of septempber 2003. + +## CVSFS + +See [cvsFS for Linux](http://cvsfs.sourceforge.net/). This provides a package which presents the CVS contents as mountable file system. It allows to view the versioned files as like they were ordinary files on a disk. There is also a possibility to check in/out some files for editing. A read-only version has been written by Stefan Siegl and is available at [Berlios](http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cvsfs4hurd/cvsfs/). + +## tar and gzip + +Rumor has it that they are on the way. Actually, a tar + gzip/bzip2 translator does exist (although it hasn't been used much...) : see [the Hurdextras project](http://savannah.nongnu.org/projects/hurdextras/) on Savannah. + +## ROM + +How about a translator which makes it look like you can write to read only media (like CDs), or change files which I don't have permission to change. This translator would make it seem like you could copy files to places where you normally couldn't. Think about combining this translator with the ftp translator and the tar and gzip translators. (cd /ftp/gnu.org/gnome.tar.gz/writes\_allowed; make install). It could be that unionfs does this very thing. + +## Super\_FIFO + +It's like a named pipe which is smart enough to start a process everytime something new tries to read from it. For example, let's say I have a script that reads in a JPEG image and spits out a smaller thumbnail \*.jpg to STDOUT. With a standard fifo (`mknod -p fifo`) this would almost works (`script big.jpg > fifo`). But what if there are two processes trying to read the fifo at once? Ick. And of course the standard way only works once without rerunning the command. I'm not quite sure what the syntax should look like, but I'm sure someone out there has a great idea waiting to happen. + +## Perl + +Perl is a wonderful language for hacking together something useful in a short amount of time. No concept is complete without being able to use it in a perl one-liner. And that goes for Hurd translators too. Right? + + #!/usr/bin/perl + use Hurd::translator; + + #file named "two" can produce an endless supply of twos, etc. (a la /dev/zero) + my $i=0; + for $filename ([zero one two three four]) + { + $libtrivfsread_codehash{$filename}= + sub{ $num_bytes=shift; my $data=$i; return chr($data) x $num_bytes; }; + #that's a hash of references to closures + $i++; + } + translator_startup(); + +A Perl translator has been started by [John Edwin Tobey](http://john-edwin-tobey.org/Hurd/) (pith). + +## Source code + +Here's a crazy thought. How about a translator for source code. You have a C source file like `hello.c` which is your normal everyday file. But there's a translator sitting underneath, so when you `cd hello.c` you get a directory with files like `main()` which represent the subroutines in `hello.c`. And of course you should be able to edit/remove those and have it modify the original source. + +## Libraries + +Here's an [idea](http://www.circlemud.org/~jelson/software/fusd/docs/node13.html) from the people making [userspace drivers in Linux](http://www.circlemud.org/~jelson/software/fusd/): + +* "One particularly interesting application of FUSD that we've found very useful is as a way to let regular user-space libraries export device file APIs. For example, imagine you had a library which factored large composite numbers. Typically, it might have a C interface--say, a function called `int *factorize(int bignum)`. With FUSD, it's possible to create a device file interface--say, a device called `/dev/factorize` to which clients can `write(2)` a big number, then `read(2)` back its factors. + +* This may sound strange, but device file APIs have at least three advantages over a typical library API. First, it becomes much more language independent--any language that can make system calls can access the factorization library. Second, the factorization code is running in a different address space; if it crashes, it won't crash or corrupt the caller. Third, and most interestingly, it is possible to use `select(2)` to wait for the factorization to complete. `select(2)` would make it easy for a client to factor a large number while remaining responsive to other events that might happen in the meantime. In other words, FUSD allows normal user-space libraries to integrate seamlessly with UNIX's existing, POSIX-standard event notification interface: `select(2)`." + +## Mail + +Am I off my rocker, or does an IMAP/POP translator sound like a good idea? It would make your remote mail servers look like local ones. Or what about a translator that makes a mbox format mail spool look like a directory. Can anyone think of a good use for an SMTP translator? + +## UUEncode + +How about a UUEncode translator for those places you can only store ASCII. Combine this with a NNTP translator and store your data in someone's Usenet archive. Or since, (as far as I know), there are no size limitations on file names in the Hurd, why not have a filesystem translator whose underlying store is a file name. (Now ls becomes cat). + +## Computation + +This is from the revenge of the command-line department. Make a directory translator whose contents are a result of the computation specified in the directory name. Here's an example... + + $ settrans -a /comp /hurd/computationfs + $ cd "/comp/3+4" + $ ls -l + total 0 + -rw-r--r-- 1 nobody users 0 Oct 16 11:41 7 + $ + $ cd "/comp/sqrt(2)" + $ ls -l + total 0 + -rw-r--r-- 1 nobody users 0 Oct 16 11:42 1.4142135623731 + $ + +...etc. Now think about your favorite GUI HTML editor and using File->Open on the following directory name, ``"/comp/for i in $( find / -name *.html ); do ln -s $i `basename $i`;done"`` Which would produce a directory listing with soft links to all of the \*.html files on your system. You could have all of the comforts of the shell from within that little File->Open dialog box. + +## Other + +Just found Wolfgang J�hrling's translator [wishlist](http://www.8ung.at/shell/trans.html). + +## Bochs + +A translator which works with [Bochs](http://bochs.sourceforge.net/) disk images would be nice. + +## Rollover + +A translator that uses a circular buffer to store log files. The translated node only contains the last N (mega,kilo)bytes. + +## Birthday + +A translator that provides an interface into the birthday program. + +You can cat your calendar, eg. bd/calendar/today bd/calendar/this-week or bd/calendar/this-month. + +And you could write new events into files located in bd/events/DATE/event-name. + +DATE is of the format the birthday expects DD/MM/YYYY. + +The contents of the file are any or none of the following birthday options: ann (An anniversary), bd (A birthday), ev (Some other event), wN (Warn N days in advance of date), toDATE (Event lasts until this DATE), forDAYS (Event runs for DAYS). + +You can optionally just edit the bd/birthdays file if you want to edit the configuration file by hand. It might make sense to write changes from bd/birthdays into ~/.birthdays. + + $ settrans -c bd /hurd/birthday -f ~/.birthdays + $ ls bd/ + birthdays calendar events + $ find bd -print + bd + bd/calendar + bd/calendar/daily + bd/calendar/this-week + bd/calendar/this-month + bd/events + bd/birthdays + $ + +## LVM + +A translator to access block devices from Linux's [Logical Volume Management](http://www.tldp.org/HOWTO/LVM-HOWTO/) would be an useful addition. + + # settrans -cap /dev/VolumeGroup0 /hurd/lvm /dev/PhysicalVolume0 /dev/PhysicalVolume1 ... + # ls /dev/VolumeGroup0/ + home + var + # settrans -cap /home /hurd/ext2fs /dev/VolumeGroup0/home + # settrans -cap /var /hurd/ext2fs /dev/VolumeGroup0/var + +Probably both [LVM2](http://sourceware.org/lvm2/) and the [Device-mapper](http://sourceware.org/dm/) need to be ported. + +## bridging translator + +A [bridging](http://bridge.sourceforge.net/faq.html) translator could improve the Hurd's networking facilities. + + # settrans -cap /dev/br0 /hurd/bridge -i eth0 -i eth1 ... + # settrans -cap /servers/socket/2 /hurd/pfinet -i /dev/br0 -a ... -g ... -m ... + +Perhaps Linux's bridging code and [utilities](http://bridge.sourceforge.net/) can be ported (or glued in) or code from one of the BSDs. + +## SSH translator + +Presenting remote file systems through SSH similar to what gnome-vfs does. + +## SMB translator + +Presenting remote file systems through Samba similar to what gnome-vfs does. Guiseppe Scrivano has worked on this and smbfs is available at [hurdextras](http://savannah.nongnu.org/cgi-bin/viewcvs/hurdextras/smbfs/). + +## Crontab translator + +Presenting a user's crontab in a filesystem where cron entries are files. + +## globlink + +Firmlink to a file according to a filename matching pattern. When a file goes away, the next file that is matched is automatically linked to. + + $ settrans -ac libfoo.so /hurd/globlink '/lib/libfoo*' + +## alphabetfs + +Organize a large group of files by their first letter. Present one subdirectory for each letter in the alphabet. + +## fsysoptsctl + +Send an fsysopts command to a set of translators. When you have a directory full of translators and you want to send each of them the same runtime option, this translator can do it for you. + + $ settrans -ac all /hurd/fsysoptsctl '/tmp/mystuff/*' + $ fsysopts all --update diff --git a/unsorted/ABITransitionStatus.mdwn b/unsorted/ABITransitionStatus.mdwn deleted file mode 100644 index 123e8f8c..00000000 --- a/unsorted/ABITransitionStatus.mdwn +++ /dev/null @@ -1,9 +0,0 @@ -Several transitions have occured recently. - -* [ABI Switch](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00096.html) from April 17, 2002 - -* [Phase I accomplished](http://lists.debian.org/debian-hurd/2002/debian-hurd-200204/msg00157.html) from April 26, 2002 - -* [status of the ABI transition](http://lists.debian.org/debian-hurd/2002/debian-hurd-200205/msg00242.html) from May 15, 2002 - --- [[Main/GrantBow]] - 15 May 2002 diff --git a/unsorted/AdvancedGrubUsage.mdwn b/unsorted/AdvancedGrubUsage.mdwn deleted file mode 100644 index 8e307b4f..00000000 --- a/unsorted/AdvancedGrubUsage.mdwn +++ /dev/null @@ -1,42 +0,0 @@ -## Advanced Grub - -[Grub](http://www.gnu.org/software/grub/) is a capable boot loader. This document is intended to capture some of its most interesting features and try to explain them a bit better than the texinfo documentation. - -### Debian Grub - -The Debian grub packages do not have networking enabled, so you have to apt-get the source, modify the debian/rules file to include --enable-network-card and dpkg-buildpackage to get a .deb of grub that supports TFTP. - -1. cd /usr/src/debian -2. apt-get source grub -3. cd grub-\_VERSION\_ -4. Add `--enable-tulip` or similar for your NIC to the `./configure` line of the `configure-stamp` target in the `debian/rules` file. -5. `dpkg-buildpackage` (as `root`) -6. `cd ..` -7. `dpkg -i grub*.deb` -8. cp /lib/grub/\_ARCH\_/\* /boot/grub/, e.g., _ARCH_ is `i386-pc` -9. Edit your `/boot/grub/menu.lst` (see below) -10. If your boot disk is `/dev/hda` ==> `grub-install (hd0)` - -### TFTP Boot - -Using trivial ftp to load a kernel is one of the best features of Grub. Here is how it is done. - -The `menu.lst` can look something like this: - - ifconfig --address=192.168.1.2 --server=192.168.1.1 - root (nd) - kernel /gnu/boot/oskit-mach.gz root=device:hd0s2 -- - root (hd0,1) - 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) - -**Note: Make sure there are NO spaces after the trailing backslases (\\)!!** - -For more information on GNUmach modules lines and installation setup, see [[Hurd/InstallNotes]] - --- [[Main/JoachimNilsson]] - 13 Apr 2005 diff --git a/unsorted/AptConfOffline.mdwn b/unsorted/AptConfOffline.mdwn deleted file mode 100644 index c4cc85be..00000000 --- a/unsorted/AptConfOffline.mdwn +++ /dev/null @@ -1,28 +0,0 @@ - APT - { - /* This file belongs in Debian GNU/Hurd's /etc/apt/apt.conf.offline - and will be used when running Debian GNU/Linux. This is only - required when the GNU/Hurd does not have network access. */ - - 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 - assumes Debian GNU/Hurd mounted on /misc/hurd and /var mounted underneath this if necessary */ - - // State::lists should be here, the lists subdirectory. - State "/misc/hurd/var/lib/apt/"; - State::status "/misc/hurd/var/lib/dpkg/status"; - - // Binary caches will be stored locally - Cache::archives "/misc/hurd/var/cache/apt/archives/"; - Cache "/tmp/"; - - // Location of the source list. - Etc "/misc/hurd/etc/apt/"; - }; diff --git a/unsorted/BootProcess.mdwn b/unsorted/BootProcess.mdwn deleted file mode 100644 index 17f7bba7..00000000 --- a/unsorted/BootProcess.mdwn +++ /dev/null @@ -1,36 +0,0 @@ -Describes the GNU/Hurd boot process. - -# Bootloader - -[GRUB](http://www.gnu.org/software/grub/) (GRand Unified Bootloader) is the default (and as far as I know the only supported ) bootloader for GNU/Hurd and is the initial process. - -GRUB can be used for booting multiple Operating Systems on a given machine. Device naming convention for GRUB is different than that of the Hurd. Where the first partition on the primary IDE drive in GNU/Hurd is hd0s1, in GRUB it is (hd0,0). In the case of GNU/Hurd, the first thing that GRUB loads is kernel image. - -Here is a copy of GNU/Hurd multi-user entry from menu.lst. The first two lines are primarily informational and are what get displayed on the GRUB boot menu. - - # Entry 2: 1st partition on first HDD - title GNU/Hurd (IDE 1st partition - hd0s1 multi-user) - root (hd0,0) - kernel /boot/gnumach.gz root=device:hd0s1 - 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) - -**_N.B. the escaped new lines above should end in only a back slash, no spaces!_** - -The line "root (hd0,0)" tells GRUB where to look for the root partition. Notice that the (hd0,0) is using GRUB naming conventions. - -The next line loads the gnumach kernel image itself. Notice here the root=device:hd0s1 argument. This is now using GNU/Hurd device naming convention, telling the Hurd where the root partition exists. - ----- - --- [[Main/BarryDeFreese]] - 29 May 2003 - -Minor formatting and edit check. - -On a side note. The actual description of the GNU/Hurd boot process is a good idea but keeping duplicated information to a bare minimum must be the guide line for a "book" like this. See other topics for more information on Grub configuration for instance. - --- [[Main/JoachimNilsson]] - 30 May 2003 diff --git a/unsorted/GNOME.mdwn b/unsorted/GNOME.mdwn deleted file mode 100644 index 1dbef091..00000000 --- a/unsorted/GNOME.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -![gnome-hurd.png](http://people.debian.org/~mbanck/media/gnome-hurd.png) - -GNOME can now be ported with the new [[Pthreads]], but is still being worked on.The packages are at - -deb ./ - -The caveats: - -Some applications are not yet built, not even all the ones from gnome-core. 'apt-get install gnome-applets gnome-control-center gnome-icon-theme gnome-panel gnome-session metacity nautilus scrollkeeper' (along with the above APT source) should get you started. - -See also: [[Xfree86]]. diff --git a/unsorted/GrubNotes.mdwn b/unsorted/GrubNotes.mdwn deleted file mode 100644 index b0b1fdf5..00000000 --- a/unsorted/GrubNotes.mdwn +++ /dev/null @@ -1,70 +0,0 @@ -This section complements the [[InstallNotes]] with complete information regarding the GRUB boot loader. The syntax is different from Lilo's and so to scratch my own itch I'm creating this quick reference. The [Grub manual](http://www.gnu.org/software/grub/manual/grub.html) is another good reference. - -* update-grub is **Debian specific** and very nice. It will automatically create a /boot/grub/menu.lst file for the kernels in /boot/. It will also append a manually configured set for other partitions like the GNU/Hurd. -* grub-floppy is a **Debian specific** boot floppy creation script. -* mkbimage is a **Debian specific** boot disk image creation script. -* contains a Debian packaged makefile for creating CD & floppy images. Looks like it doesn't work properly. If you fix it, please send patches to the maintainer. -* essential GRUB commands & disk syntax - * root - * kernel - * module - * boot -* sample file - - title GNU/Linux - root (hd0,11) - kernel /boot/vmlinuz-2.4.18 root=/dev/hda12 ro - initrd /boot/initrd.img-2.4.18 - savedefault - - title GNU - root (hd0,15) - kernel /boot/oskit-mach root=device:hd0s16 -- - 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) - savedefault - - title DOS - rootnoverify (hd0,0) - chainloader +1 - --- [[Main/GrantBow]] - 01 Oct 2002
-- [[Main/GrantBow]] - 22 Dec 2002 - -Another example, just as good, but a lot easier to read. The backslash at the end of each line is to "escape" the enter-key. So make sure there are no spaces following the backslashes! - - title GNU/Linux (Linux 2.4.18) - root (hd0,11) - kernel /boot/vmlinuz-2.4.18 root=/dev/hda12 ro - initrd /boot/initrd.img-2.4.18 - savedefault - - title GNUmach 1.3 - root (hd0,1) - kernel /boot/gnumach.gz root=device:hd0s2 - module /hurd/ext2fs.static --readonly \ - --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 GNUmach 1.90 (CVS) - root (hd0,1) - kernel /boot/oskit-mach.gz root=device:hd0s2 -- - module /hurd/ext2fs.static --readonly \ - --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) - -Note the differences between GNUmach and OSKit-Mach. The latter **needs** the two dashes after the root specification! - --- [[Main/JoachimNilsson]] - 09 Nov 2002 diff --git a/unsorted/InstallNotes.mdwn b/unsorted/InstallNotes.mdwn index 49dcd53d..1cdfca9c 100644 --- a/unsorted/InstallNotes.mdwn +++ b/unsorted/InstallNotes.mdwn @@ -47,7 +47,7 @@ You can always install GRUB onto your hard drive at a later date. For instructions on using GRUB, see either the info documentation or the quick reference notes on this wiki: -* [[Distrib/GrubNotes]] - quick reference +* [[GRUB]] - quick reference ## 4. Cross Install - Cross Installing GNU diff --git a/unsorted/InstallTips.mdwn b/unsorted/InstallTips.mdwn index a735fbf7..c9f5bdc2 100644 --- a/unsorted/InstallTips.mdwn +++ b/unsorted/InstallTips.mdwn @@ -60,7 +60,7 @@ now mount the floppy and copy the files to your partition you may also wish to put my menu.lst file in your grub directory which can be obtained here you will need to edit it to include a -s at the end of the line starting with kernel. Be sure modify the partition numbers, my system is using the third partition of the second harddrive. -More detailed samples for grub config files can be found at the [[GrubNotes]] +More detailed samples for GRUB config files can be found at the [[GRUB]] page. To install grub reboot using the grub floppy and issue: diff --git a/unsorted/LuisBustamanteHurdPage.mdwn b/unsorted/LuisBustamanteHurdPage.mdwn deleted file mode 100644 index abbf1531..00000000 --- a/unsorted/LuisBustamanteHurdPage.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -Nothing much to see right now, I'll add some stuff I'm working in the near future! :) - -Cheers, - --- [[Main/LuisBustamante]] - 16 May 2002 - -After making some trivial/incorrect patches (thanks Neal :) for building um-pppd with gcc 3.0.4 in Debian (see [\#147085](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147085&repeatmerged=yes)) this weekend I'll finally give it a try, I got an external modem... anyway serial drivers seem to be broken in GNUmach iirc, I won't get much more than 300b/s :). - -Keep Hurding! - --- [[Main/LuisBustamante]] - 17 May 2002 diff --git a/unsorted/NewMachHistory.mdwn b/unsorted/NewMachHistory.mdwn deleted file mode 100644 index 562d1cac..00000000 --- a/unsorted/NewMachHistory.mdwn +++ /dev/null @@ -1,27 +0,0 @@ -# Table of Contents - -%TOC% - -# Early beginnings - -GNUMach is based on Mach4 from University of Utah, which in turn is based on Mach3 from Carnegie-Mellon University. The last release of Mach4 was the [UK22 release](http://www.cs.utah.edu/flux/mach4-i386/html/mach4-UK22.html). - -The oskit-mach version of GNU Mach was presented in November 1999 by Roland McGrath. The purpose of the port was to get better hardware support through new drivers and platform code available in the OSKit. - -On May 27 2002, after the Gnumach 1.3 release, Roland McGrath merged OSKit-Mach onto the HEAD of CVS making it the Gnumach 2.x mainline. - -# Status of the project - -GNU Mach 1.3 was released in May 2002, and features advanced boot script support, support for large disks (>= 10GB) and an improved console. - -GNU Mach is used as the default microkernel in the GNU/Hurd system. It is compatible with other popular Mach distributions. The device drivers for block devices and network cards are taken from Linux 2.0.x kernel versions, and so a broad range of common hardware is supported. - -However, the Linux device drivers have been improved greatly since the 2.0.x version, and a new version of GNU Mach based on the OSKit library is being worked on, which uses newer drivers and in general has cleaner machine specific support code. - ----- - -Copyright (C) 2001 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA - -Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. - --- [[Main/JoachimNilsson]] - 24 Oct 2002 diff --git a/unsorted/OskitMach.mdwn b/unsorted/OskitMach.mdwn index c28f2d89..b5b92d68 100644 --- a/unsorted/OskitMach.mdwn +++ b/unsorted/OskitMach.mdwn @@ -37,7 +37,7 @@ First you need to get the latest OSKit release and, preferrably, the latest CVS ## Starting -You start Oskit-Mach almost the same way as the old 1.x version of GNUmach. Using [[Hurd/GrubNotes]] an entry can look like this: +You start Oskit-Mach almost the same way as the old 1.x version of GNUmach. Using [[GRUB]] an entry can look like this: title GNUmach 1.90 (CVS) root (hd0,1) diff --git a/unsorted/PppDaemon.mdwn b/unsorted/PppDaemon.mdwn deleted file mode 100644 index f667d449..00000000 --- a/unsorted/PppDaemon.mdwn +++ /dev/null @@ -1,6 +0,0 @@ -There is no PPP solution present for the Hurd. - -* Filed Debian [um-ppp bug](http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no\&bug=147085) -* Clemmitt [asked about um-pppd](http://mail.gnu.org/pipermail/help-hurd/2002-October/006664.html) in this thread of 9 posts beginning Oct 10, 2002. - --- [[Main/GrantBow]] - 20 Oct 2002 diff --git a/unsorted/TranslatorExamples.mdwn b/unsorted/TranslatorExamples.mdwn deleted file mode 100644 index 0c2e5741..00000000 --- a/unsorted/TranslatorExamples.mdwn +++ /dev/null @@ -1,61 +0,0 @@ -## Introduction - -Translators are probably the most known feature of the Hurd, the first thing you should show when doing a demo. - -## run - -Couldn't manage to compile it, but allows you to do nice things with eg. fortune. - -## ftpfs - -hurd:~# settrans -c ftp /hurd/ftpfs 128.101.80.131:/ - -hurd:~# cd ftp - -hurd:~/ftp# ls - -debian debian-archive lost+found - -hurd:~/ftp# cd debian - -hurd:~/ftp/debian# ls - -README README.mirrors.txt doc ls-lR.patch.gz - -README.CD-manufacture README.non-US indices pool - -README.html README.pgp ls-lR project - -README.mirrors.html dists ls-lR.gz tools - -hurd:~/ftp/debian# cp README ~ - -hurd:~/ftp/debian# - -You have to specify the server address with its IP, or your computer will buy a farm or something. - -## ftpfs and hostmux - -currently (28/02/2004) not working, but should be. - -hurd:~# settrans -c ftp /hurd/hostmux /hurd/ftpfs / - -hurd:~# cd ftp - -hurd:~/ftp# cd ftp.debian.org - --bash: cd: ftp.debian.org: Computer bought the farm - -hurd:~/ftp# host ftp.debian.org - -ftp.debian.org A 128.101.80.131 - -ftp.debian.org A 208.185.25.38 - -hurd:~/ftp# cd 128.101.80.131 - --bash: cd: 128.101.80.131: Computer bought the farm - -## Articles about translators - -* [The GNU Hurd - Translators by Gael le Mignot](http://kilobug.free.fr/hurd/pres-en/html/node8.html) diff --git a/unsorted/TranslatorPages.mdwn b/unsorted/TranslatorPages.mdwn deleted file mode 100644 index 8e954521..00000000 --- a/unsorted/TranslatorPages.mdwn +++ /dev/null @@ -1,51 +0,0 @@ -

[[NeighborHurd]]: A concept possible with microkernels.
[[InteractiveTranslators]]: Translators that interact with user
[[TranslatorExamples]]: Examples of what you can do with translators
[[TranslatorWishList]]: Interesting file translator ideas

- -Here are the translators that currently exist: - -* [[AuthTranslator]] -* [[CrashTranslator]] -* [[ExecTranslator]] -* [[ExtTwofsTranslator]] - (actually named ext2fs) Ext2 filesystems, also ext2fs.static -* [[FifoTranslator]] - also [[NewfifoTranslator]] (actually named new-fifo) -* [[FirmlinkTranslator]] -* [[FtpfsTranslator]] - ftp as a filesystem -* [[FwdTranslator]] -* [[HelloTranslator]] - also [[HellomtTranslator]] (actually named hello-mt) -* [[HostmuxTranslator]] -* [[IfsockTranslator]] -* [[InitTranslator]] -* [[IsofsTranslator]] -* [[KbdTranslator]] -* [[MachdefpagerTranslator]] - (actually named mach-defpager) -* [[hurd/translator/magic]] -* [[MouseTranslator]] -* [[NfsTranslator]] -* [[NullTranslator]] -* [[PasswordTranslator]] -* [[PfinetTranslator]] - also [[PflocalTranslator]] -* [[ProcTranslator]] -* [[SmbfsTranslator]] -* [[StoreioTranslator]] -* [[StreamioTranslator]] -* [[SymlinkTranslator]] -* [[TermTranslator]] -* [[TmpfsTranslator]] -* [[UfsTranslator]] - also ufs.static -* [[UsermuxTranslator]] - -Here are the contributed translators: - -* [[CryptTranslator]] - - -This is an old list and might need some updating, please check if you have a Hurd system that this list is accurate. - --- [[Main/GrantBow]] - 03 Mar 2004 diff --git a/unsorted/TranslatorWishList.mdwn b/unsorted/TranslatorWishList.mdwn deleted file mode 100644 index 38bd87d9..00000000 --- a/unsorted/TranslatorWishList.mdwn +++ /dev/null @@ -1,193 +0,0 @@ -## Introduction - -The idea behind file system translators is a powerful concept which hasn't recieved much attention in the mainstream computing world. So here is a list of interesting translators I've been able to dream up. I'm sure there are many more ideas floating around out there, so add them to the list! - -The [ferris project](http://witme.sourceforge.net/libferris.web/features.html) has some great ideas and code in the area of userspace dynamic filesystems, as has the [FUSE project](http://fuse.sourceforge.net/). - -## Audio\_cdfs - -A translator which produces a directory of \*.wav files when you have an audio CD in the drive. - -## Ogg - -This translator could be a sub-directory of the Audio\_cdfs translator and it would translate the \*.wav files into Ogg Vorbis/MP3 format. - -## CDDB - -Of course it would be a lot nicer if the above two translators didn't name their files something worthless like track001.ogg. So we would want a translator which would hook up with a database on the web and produce meaningful file names. - -## Crypto - -A cryptographic/steganographic seem like a nice match with the concept of user-land file systems. I like the idea of something like `settrans -a /secure stegfs --mpeg file001.mpg` - -## Revision control - -All of the empty space on your drive is now being wasted. Why not have a revision control translator which tracks changes to your documents? See also [this guy](http://www.linuxjournal.com/article.php?sid=5976). And then you'd do something like `cd /time-machine/2003/sept/14/` to see what your system looked like on the 14th of septempber 2003. - -## CVSFS - -See [cvsFS for Linux](http://cvsfs.sourceforge.net/). This provides a package which presents the CVS contents as mountable file system. It allows to view the versioned files as like they were ordinary files on a disk. There is also a possibility to check in/out some files for editing. A read-only version has been written by Stefan Siegl and is available at [Berlios](http://cvs.berlios.de/cgi-bin/viewcvs.cgi/cvsfs4hurd/cvsfs/). - -## tar and gzip - -Rumor has it that they are on the way. Actually, a tar + gzip/bzip2 translator does exist (although it hasn't been used much...) : see [the Hurdextras project](http://savannah.nongnu.org/projects/hurdextras/) on Savannah. - -## ROM - -How about a translator which makes it look like you can write to read only media (like CDs), or change files which I don't have permission to change. This translator would make it seem like you could copy files to places where you normally couldn't. Think about combining this translator with the ftp translator and the tar and gzip translators. (cd /ftp/gnu.org/gnome.tar.gz/writes\_allowed; make install). It could be that unionfs does this very thing. - -## Super\_FIFO - -It's like a named pipe which is smart enough to start a process everytime something new tries to read from it. For example, let's say I have a script that reads in a JPEG image and spits out a smaller thumbnail \*.jpg to STDOUT. With a standard fifo (`mknod -p fifo`) this would almost works (`script big.jpg > fifo`). But what if there are two processes trying to read the fifo at once? Ick. And of course the standard way only works once without rerunning the command. I'm not quite sure what the syntax should look like, but I'm sure someone out there has a great idea waiting to happen. - -## Perl - -Perl is a wonderful language for hacking together something useful in a short amount of time. No concept is complete without being able to use it in a perl one-liner. And that goes for Hurd translators too. Right? - - #!/usr/bin/perl - use Hurd::translator; - - #file named "two" can produce an endless supply of twos, etc. (a la /dev/zero) - my $i=0; - for $filename ([zero one two three four]) - { - $libtrivfsread_codehash{$filename}= - sub{ $num_bytes=shift; my $data=$i; return chr($data) x $num_bytes; }; - #that's a hash of references to closures - $i++; - } - translator_startup(); - -A Perl translator has been started by [John Edwin Tobey](http://john-edwin-tobey.org/Hurd/) (pith). - -## Source code - -Here's a crazy thought. How about a translator for source code. You have a C source file like `hello.c` which is your normal everyday file. But there's a translator sitting underneath, so when you `cd hello.c` you get a directory with files like `main()` which represent the subroutines in `hello.c`. And of course you should be able to edit/remove those and have it modify the original source. - -## Libraries - -Here's an [idea](http://www.circlemud.org/~jelson/software/fusd/docs/node13.html) from the people making [userspace drivers in Linux](http://www.circlemud.org/~jelson/software/fusd/): - -* "One particularly interesting application of FUSD that we've found very useful is as a way to let regular user-space libraries export device file APIs. For example, imagine you had a library which factored large composite numbers. Typically, it might have a C interface--say, a function called `int *factorize(int bignum)`. With FUSD, it's possible to create a device file interface--say, a device called `/dev/factorize` to which clients can `write(2)` a big number, then `read(2)` back its factors. - -* This may sound strange, but device file APIs have at least three advantages over a typical library API. First, it becomes much more language independent--any language that can make system calls can access the factorization library. Second, the factorization code is running in a different address space; if it crashes, it won't crash or corrupt the caller. Third, and most interestingly, it is possible to use `select(2)` to wait for the factorization to complete. `select(2)` would make it easy for a client to factor a large number while remaining responsive to other events that might happen in the meantime. In other words, FUSD allows normal user-space libraries to integrate seamlessly with UNIX's existing, POSIX-standard event notification interface: `select(2)`." - -## Mail - -Am I off my rocker, or does an IMAP/POP translator sound like a good idea? It would make your remote mail servers look like local ones. Or what about a translator that makes a mbox format mail spool look like a directory. Can anyone think of a good use for an SMTP translator? - -## UUEncode - -How about a UUEncode translator for those places you can only store ASCII. Combine this with a NNTP translator and store your data in someone's Usenet archive. Or since, (as far as I know), there are no size limitations on file names in the Hurd, why not have a filesystem translator whose underlying store is a file name. (Now ls becomes cat). - -## Computation - -This is from the revenge of the command-line department. Make a directory translator whose contents are a result of the computation specified in the directory name. Here's an example... - - $ settrans -a /comp /hurd/computationfs - $ cd "/comp/3+4" - $ ls -l - total 0 - -rw-r--r-- 1 nobody users 0 Oct 16 11:41 7 - $ - $ cd "/comp/sqrt(2)" - $ ls -l - total 0 - -rw-r--r-- 1 nobody users 0 Oct 16 11:42 1.4142135623731 - $ - -...etc. Now think about your favorite GUI HTML editor and using File->Open on the following directory name, ``"/comp/for i in $( find / -name *.html ); do ln -s $i `basename $i`;done"`` Which would produce a directory listing with soft links to all of the \*.html files on your system. You could have all of the comforts of the shell from within that little File->Open dialog box. - -## Other - -Just found Wolfgang J�hrling's translator [wishlist](http://www.8ung.at/shell/trans.html). - -## Bochs - -A translator which works with [Bochs](http://bochs.sourceforge.net/) disk images would be nice. - -## Rollover - -A translator that uses a circular buffer to store log files. The translated node only contains the last N (mega,kilo)bytes. - -## Birthday - -A translator that provides an interface into the birthday program. - -You can cat your calendar, eg. bd/calendar/today bd/calendar/this-week or bd/calendar/this-month. - -And you could write new events into files located in bd/events/DATE/event-name. - -DATE is of the format the birthday expects DD/MM/YYYY. - -The contents of the file are any or none of the following birthday options: ann (An anniversary), bd (A birthday), ev (Some other event), wN (Warn N days in advance of date), toDATE (Event lasts until this DATE), forDAYS (Event runs for DAYS). - -You can optionally just edit the bd/birthdays file if you want to edit the configuration file by hand. It might make sense to write changes from bd/birthdays into ~/.birthdays. - - $ settrans -c bd /hurd/birthday -f ~/.birthdays - $ ls bd/ - birthdays calendar events - $ find bd -print - bd - bd/calendar - bd/calendar/daily - bd/calendar/this-week - bd/calendar/this-month - bd/events - bd/birthdays - $ - -## LVM - -A translator to access block devices from Linux's [Logical Volume Management](http://www.tldp.org/HOWTO/LVM-HOWTO/) would be an useful addition. - - # settrans -cap /dev/VolumeGroup0 /hurd/lvm /dev/PhysicalVolume0 /dev/PhysicalVolume1 ... - # ls /dev/VolumeGroup0/ - home - var - # settrans -cap /home /hurd/ext2fs /dev/VolumeGroup0/home - # settrans -cap /var /hurd/ext2fs /dev/VolumeGroup0/var - -Probably both [LVM2](http://sourceware.org/lvm2/) and the [Device-mapper](http://sourceware.org/dm/) need to be ported. - -## bridging translator - -A [bridging](http://bridge.sourceforge.net/faq.html) translator could improve the Hurd's networking facilities. - - # settrans -cap /dev/br0 /hurd/bridge -i eth0 -i eth1 ... - # settrans -cap /servers/socket/2 /hurd/pfinet -i /dev/br0 -a ... -g ... -m ... - -Perhaps Linux's bridging code and [utilities](http://bridge.sourceforge.net/) can be ported (or glued in) or code from one of the BSDs. - -## SSH translator - -Presenting remote file systems through SSH similar to what gnome-vfs does. - -## SMB translator - -Presenting remote file systems through Samba similar to what gnome-vfs does. Guiseppe Scrivano has worked on this and smbfs is available at [hurdextras](http://savannah.nongnu.org/cgi-bin/viewcvs/hurdextras/smbfs/). - -## Crontab translator - -Presenting a user's crontab in a filesystem where cron entries are files. - -## globlink - -Firmlink to a file according to a filename matching pattern. When a file goes away, the next file that is matched is automatically linked to. - - $ settrans -ac libfoo.so /hurd/globlink '/lib/libfoo*' - -## alphabetfs - -Organize a large group of files by their first letter. Present one subdirectory for each letter in the alphabet. - -## fsysoptsctl - -Send an fsysopts command to a set of translators. When you have a directory full of translators and you want to send each of them the same runtime option, this translator can do it for you. - - $ settrans -ac all /hurd/fsysoptsctl '/tmp/mystuff/*' - $ fsysopts all --update - ----- - --- [[Main/GregBuchholz]] - updated 17 Oct 2003 -- cgit v1.2.3 From e9e35680bf651139ee6ce153e0aaa7308ab01ca5 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sat, 28 Mar 2009 20:40:32 +0100 Subject: provide more details for PATH_MAX --- unsorted/PortingIssues.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'unsorted') diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn index ff63bda3..03980ef3 100644 --- a/unsorted/PortingIssues.mdwn +++ b/unsorted/PortingIssues.mdwn @@ -51,15 +51,15 @@ If you get Bad File Descriptor error when trying to read from a file (or accessi ## `PATH_MAX` / `MAX_PATH` / `MAXPATHLEN` -Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX incompatibility. If there is no upper limit on the length of a path (as its the case for GNU), this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use `sysconf()` to query the length at runtime. If `sysconf()` returns -1, you have to use `realloc()` to allocate the needed memory dynamically. +Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX incompatibility. If there is no upper limit on the length of a path (as its the case for GNU), this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use `sysconf()` to query the length at runtime. If `sysconf()` returns -1, you have to use `realloc()` to allocate the needed memory dynamically. Usually it is thus simpler to just use dynamic allocation. Sometimes the amount is actually known. Else, a geometrically growing loop can be used: for instance, see [Alioth patch](http://alioth.debian.org/tracker/download.php/30628/410472/303735/1575/cpulimit-path-max-fix.patch). Note that in some cases there are GNU extensions that just work fine: when the `__GLIBC__` macro is defined, `getcwd()` calls can be just replaced by `get_current_dir_name()` calls. ## `ARG_MAX` -Same as `PATH_MAX`. There is no limit on the number of arguments. +Same rationale as `PATH_MAX`. There is no limit on the number of arguments. ## `IOV_MAX` -Same as `PATH_MAX`. There is no limit on the number of iovec items. +Same rationale as `PATH_MAX`. There is no limit on the number of iovec items. ## `MAXHOSTNAMELEN` -- cgit v1.2.3 From 714738c3aa0d5625cc7dccf0e8c3f1414b8930c6 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 5 Apr 2009 18:39:14 +0200 Subject: unsorted/PortingIssues -> hurd/porting/guidelines --- community/gsoc/project_ideas/maxpath.mdwn | 2 +- hurd/faq/old-stuff.mdwn | 2 +- hurd/porting/guidelines.mdwn | 281 +++++++++++++++++++++++++ hurd/running/debian/GnuDebianRelationship.mdwn | 4 +- hurd/running/distrib.mdwn | 2 +- unsorted/PortingIssues.mdwn | 270 ------------------------ 6 files changed, 286 insertions(+), 275 deletions(-) create mode 100644 hurd/porting/guidelines.mdwn delete mode 100644 unsorted/PortingIssues.mdwn (limited to 'unsorted') diff --git a/community/gsoc/project_ideas/maxpath.mdwn b/community/gsoc/project_ideas/maxpath.mdwn index 992b91ee..d78297d5 100644 --- a/community/gsoc/project_ideas/maxpath.mdwn +++ b/community/gsoc/project_ideas/maxpath.mdwn @@ -33,7 +33,7 @@ by `char *foo`, and using dynamic memory allocation, i.e. e.g. a loop that tries geometrically growing sizes. Sometimes this is tricky, but more often not very hard. Sometimes it is even trivial because the GNU system has proper replacements. See the corresponding section of the -[[Porting_issues_page|unsorted/PortingIssues]] for more details. With a bit of +[[porting_guidelines_page|hurd/porting/guidelines]] for more details. With a bit of practice, it should be easily possible to fix several programs per day. The goal of this project is to fix the PATH_MAX and related problems in a diff --git a/hurd/faq/old-stuff.mdwn b/hurd/faq/old-stuff.mdwn index 1bcc09a0..e4132d50 100644 --- a/hurd/faq/old-stuff.mdwn +++ b/hurd/faq/old-stuff.mdwn @@ -28,7 +28,7 @@ If you still have problems, do not hesitate to make use of the [[mailing_lists]] * These are different versions of the Mach microkernel that supports the Hurd that runs on top of it. For more info, see [[Mach]] * **_What software is available for GNU?_** - * Most packages from [Debian](http://www.debian.org/) [GNU/Linux](http://www.gnu.org/gnu/linux-and-gnu.html) which aren't linux-specific ([Packages That Won't Be Ported](http://www.debian.org/ports/hurd/hurd-devel-debian)) are expected to work on GNU/Hurd too. See the database in . Programs which need pthreads, including [GNOME](http://www.gnome.org), [KDE](http://www.kde.org), [Mozilla](http://www.mozilla.org), [OpenOffice](http://www.openoffice.org), [SDL](http://www.libsdl.org), etc. are being worked on currently using Neal Walfields libpthreads. See the [[Distrib/PortingIssues]] document for some common build problems and their solutions. + * Most packages from [Debian](http://www.debian.org/) [GNU/Linux](http://www.gnu.org/gnu/linux-and-gnu.html) which aren't linux-specific ([Packages That Won't Be Ported](http://www.debian.org/ports/hurd/hurd-devel-debian)) are expected to work on GNU/Hurd too. See the database in . Programs which need pthreads, including [GNOME](http://www.gnome.org), [KDE](http://www.kde.org), [Mozilla](http://www.mozilla.org), [OpenOffice](http://www.openoffice.org), [SDL](http://www.libsdl.org), etc. are being worked on currently using Neal Walfields libpthreads. See the [[porting/guidelines]] document for some common build problems and their solutions. * If you can't fetch a package with "apt-get install ", try building it from source: "apt-get source && cd <package\_dir> && debian/rules binary". * As of January 2007, 50% of Debian packages have been ported on the Hurd. Of course, bug testing is welcome. diff --git a/hurd/porting/guidelines.mdwn b/hurd/porting/guidelines.mdwn new file mode 100644 index 00000000..ee27c9be --- /dev/null +++ b/hurd/porting/guidelines.mdwn @@ -0,0 +1,281 @@ +[[meta copyright="Copyright © 2002, 2003, 2005, 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]]."]]"""]] + +## Table of Contents + +%TOC% + +## Overview + +This is a recompilation of common porting problems and their solutions. Information is gathered from the following sources: + +* [Debian GNU/Hurd port guidelines](http://www.debian.org/ports/hurd/hurd-devel-debian) + +* [James Morrison's GNU/Hurd pages](http://hurd.dyndns.org/) + +as well as other misc. sources. + +First of all, see [[BtsFiling]] if you need instructions on manipulating [Debian](http://www.debian.org/) source packages and submitting patches to their [Bug Tracking System](http://bugs.debian.org/). + +## System API limitations + +Sometimes building or running a program will fail due to bugs in the system API implementation (in Glibc and the Hurd). Make sure you check this list and know them before porting, otherwise you'll end up debugging something just to find out its an already known bug. + +We maintain a separate Wiki page for information on these bugs, see [[Distrib/SystemAPILimits]] + +If you think you can fix any of them and send a patch to the debian BTS, that'd be much appreciated. You may ask in for details or questions on the bug. + +## Undefined `bits/confname.h` macros (`PIPE_BUF`, ...) + +If macro `XXX` is undefined, but macro `_SC_XXX` or `_PC_XXX` is defined in `bits/confname.h`, you probably need to use `sysconf`, `pathconf` or `fpathconf` to obtain it dynamicaly. + +The following macros have been found in this offending situation (add more if you find them): `PIPE_BUF` + +An example with `sysconf`: (when you find a `sysconf` offending macro, put a better example) + + #ifndef XXX + #define XXX sysconf(_SC_XXX) + #endif + /* offending code using XXX follows */ + +An example with `fpathconf`: + + #ifdef PIPE_BUF + read(fd, buff, PIPE_BUF - 1); + #else + read(fd, buff, fpathconf(fd, _PC_PIPE_BUF) - 1); + #endif + /* note we can't #define PIPE_BUF, because it depends + on the "fd" variable */ + +## Bad File Descriptor + +If you get Bad File Descriptor error when trying to read from a file (or accessing it at all), check the `open()` invocation. The second argument is the access method. If it is a hard coded number instead of a symbol defined in the standard header files, the code is screwed and should be fixed to either use `O_RDONLY`, `O_WRONLY` or `O_RDWR`. This bug was observed in the `fortunes` and `mtools` packages for example. + +## `PATH_MAX` / `MAX_PATH` / `MAXPATHLEN` + +Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX incompatibility. If there is no upper limit on the length of a path (as its the case for GNU), this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use `sysconf()` to query the length at runtime. If `sysconf()` returns -1, you have to use `realloc()` to allocate the needed memory dynamically. Usually it is thus simpler to just use dynamic allocation. Sometimes the amount is actually known. Else, a geometrically growing loop can be used: for instance, see [Alioth patch](http://alioth.debian.org/tracker/download.php/30628/410472/303735/1575/cpulimit-path-max-fix.patch). Note that in some cases there are GNU extensions that just work fine: when the `__GLIBC__` macro is defined, `getcwd()` calls can be just replaced by `get_current_dir_name()` calls. + +## `ARG_MAX` + +Same rationale as `PATH_MAX`. There is no limit on the number of arguments. + +## `IOV_MAX` + +Same rationale as `PATH_MAX`. There is no limit on the number of iovec items. + +## `MAXHOSTNAMELEN` + +Same as `PATH_MAX`. When you find a `gethostname()` function, which acts on a static buffer, you can replace it with Neal's [xgethostname function](http://ftp.walfield.org/pub/people/neal/xgethostname/) which returns the hostname as a dynamic buffer. For example: + +Buggy code: + + char localhost[MAXHOSTNAMELEN]; + ... + gethostname(localhost, sizeof(localhost)); + +Fixed code: + + #include "xgethostname.h" + ... + char *localhost; + ... + localhost = xgethostname(); + if (! localhost) + { + perror ("xgethostname"); + return ERROR; + } + ... + /* use LOCALHOST. */ + free (localhost); + +## `NOFILE` + +Replace with `getrlimit(RLIMIT_NOFILE,...)` + +## GNU specific `#define` + +If you need to include specific code for GNU/Hurd using `#if` ... `#endif`, then you can use the `__GNU__` symbol to do so. But think (at least) thrice! before doing so. In most situations, this is completely unnecessary and will create more problems than it may solve. Better ask on the mailing list how to do it right if you can't think of a better solution. + +## `sys_errlist[]` vs. `strerror()` + +If a program has only support for `sys_errlist[]` you will have to do some work to make it compile on GNU, which has dropped support for it and does only provide `strerror()`. Steinar Hamre writes about `strerror()`: + +`strerror()` should be used because: + +* It is the modern, POSIX way. +* It is localized. +* It handles invalid signals/numbers out of range. (better errorhandling and not a buffer-overflow-candidate/security risk) + +`strerror()` should always be used if it is available. Unfortunaly there are still some old non-POSIX systems that do not have `strerror()`, only `sys_errlist[]`. + +Today, only supporting `strerror()` is far better than only supporting `sys_errlist[]`. The best (from a portability viewpoint), however is supporting both. For configure.in, you will need: + + AC_CHECK_FUNCS(strerror) + +To `config.h.in`, you need to add: + + #undef HAVE_STRERROR + +Then something like: + + #ifndef HAVE_STRERROR + static char * + private_strerror (errnum) + int errnum; + { + extern char *sys_errlist[]; + extern int sys_nerr; + + if (errnum > 0 && errnum <= sys_nerr) + return sys_errlist[errnum]; + + return "Unknown system error"; + } + #define strerror private_strerror + #endif /* HAVE_STRERROR */ + +You can for example look in the latest coreutils (the above is a simplified version of what I found there.) Patches should of course be sent to upstream maintainers, this is very useful even for systems with a working `sys_errlist[]`. + +Of course, if you don't care about broken systems (like MS-DOG) not supporting `strerror()` you can just replace `sys_errlist[]` directly (upstream might not accept your patch, but debian should have no problem) + +## C++, `error_t` and `E*` + +On the Hurd, `error_t` is an enumeration of the `E*` constants. However, C++ +does not like `E*` integer macros being directly assigned to that enumeration. In short, replace + + error_t err = EINTR; + +by + + error_t err = error_t(EINTR); + +## Filenames ending in a slash \`/' + +Those are evil if they don't exist and you want to name a directory this way. For example, `mkdir foobar/` will not work on GNU. This is POSIX compatible. POSIX says that the path of a directory may have slashes appended to it. But the directory does not exist yet, so the path does not refer to a directory, and hence trailing slashes are not guaranteed to work. Just drop the slashes, and you're fine. + +## Missing `termio.h` + +Change it to use `termios.h` (check for it properly with autoconf `HAVE_TERMIOS_H` or the `__GLIBC__` macro) + +Also, change calls to `ioctl(fd, TCGETS, ...)` and `ioctl(fd, TCSETS, ...)` with `tcgetattr(fd, ...)` and `tcsetattr(fd, ...)`. + +## `AC_HEADER_TERMIO` + +The autoconf check for `AC_HEADER_TERMIO` tryes to check for termios, but it's only really checking for termio in `termios.h`. It is better to use `AC_CHECK_HEADERS(termio.h termios.h)` + +## missing `_IOT` + +This comes from ioctls. Fixing this is easy if the structure members can be expressed by using the _IOT() macro, else it's simply impossible... See `bits/termios.h` for an instance: + +`#define _IOT_termios /* Hurd ioctl type field. */ \ + _IOT (_IOTS (tcflag_t), 4, _IOTS (cc_t), NCCS, _IOTS (speed_t), 2)` + +because `struct termios` holds 4 members of type `tcflag_ts`, then `NCCS` +members of type `cc_tsi` and finaly 2 members of type `speed_ts`. + +As you can see, this limits the number of kinds of members to 3, and in +addition to that (see the bitfield described in `ioctls.h`), the third +kind of member is limited to 3 members. However, since at the API +compatibility layer you are generally allowed to reorder fields in +structures, you can usually manage to fit into these limits. + +Note: if a field member is a pointer, then the ioctl can't be expressed +this way, and that makes sense, since the server you're talking to +doesn't have direct access to your memory. Ways other than ioctls must +then be found. + +## `SA_SIGINFO` + +Not implemented, packages may be fixed for working around this: use void sighandler(int num) prototype and sa_handler field. + +## `SOL_IP` + +Not implemented yet. + +## `HZ` + +Linuxish and doesn't even make sense since the value may vary according to the running kernel. Should use `sysconf(_SC_CLK_TCK)` or `CLK_TCK` instead. + +## `SIOCDEVPRIVATE` + +Oh, we should probably provide it. + +## `MAP_NORESERVE` + +Not POSIX, but we could implement it. + +## `O_DIRECT` + +Long story to implement. + +## `PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP` + +We could easily provide it; + +## `PTHREAD_STACK_MIN` + +We should actually provide it. + +## `linux/types.h` or `asm/types.h` + +These are not POSIX, `sys/types.h` and `stdint.h` should be used instead. + +## `iopl` + +Not supported. Try to replace with `ioperm(0, 65536, 1)` (conditionned with `__GNU__` as that will not work in Linux). + +## `semget`, `sem_open` + +Not implemented, will always fail. Use `sem_init()` instead if possible. + +## `net/if_arp.h`, `net/ethernet.h`, etc. + +Not implemented, not POSIX. Try to disable the feature in the package. + +## broken libc6 dependency + +Some packages use an erroneous dependency on `libc6-dev`. This is incorrect because `libc6` is specific to GNU/Linux. The corresponding package for GNU is `libc0.3-dev` but other OSes will have different ones. You can locate the problem in the `debian/control` file of the source tree. Typical solutions include detecting the OS using `dpkg-architecture` and hardcoding the soname, or better, use a logical OR. eg: `libc6-dev | libc0.3-dev | libc-dev`. The `libc-dev` is a virtual package that works for any soname but you have to put it only as the last option. + +---- + +## ChangeLog + +-- [[Main/TWikiGuest]] - 13 Jan 2005 + +Fix xgethostname example. - Neal + +-- [[Main/RobertMillan]] - 22 Jul 2002 + +Formatting and minor grammatical fixes. + +-- [[Main/JoachimNilsson]] - 09 Sep 2002 + +Added more examples and misc semantical fixes. + +-- [[Main/RobertMillan]] - 05 Oct 2002 + +Added `xgethostname` example. + +-- [[Main/RobertMillan]] - 15 Nov 2002 + +Added broken libc6 dependency + +-- [[Main/RobertMillan]] - 21 Nov 2002 + +Text formatting. + +-- Ognyan Kulev - 12 Mar 2003 + +Added `ioctl` entry. + +-- [[Main/RobertMillan]] - 19 Mar 2003 diff --git a/hurd/running/debian/GnuDebianRelationship.mdwn b/hurd/running/debian/GnuDebianRelationship.mdwn index ede808c8..94fd6265 100644 --- a/hurd/running/debian/GnuDebianRelationship.mdwn +++ b/hurd/running/debian/GnuDebianRelationship.mdwn @@ -2,11 +2,11 @@ I have hesitated in starting this page due to the sensitive nature of this relat This is a work in progress. Please email me directly if you have comments or suggestions. -* Debian Advantages of Hurd [[Distrib/PortingIssues]] Efforts +* 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 [[Distrib/PortingIssues]] Efforts +* Debian Disadvantages of Hurd [porting/guidelines]] Efforts * Perceived zealous GNU and FSF promotion. * Hurd Port Advantages of Debian diff --git a/hurd/running/distrib.mdwn b/hurd/running/distrib.mdwn index 935c0c2d..607b50af 100644 --- a/hurd/running/distrib.mdwn +++ b/hurd/running/distrib.mdwn @@ -68,7 +68,7 @@ about getting applications to work (if possible).

[[PortingIssues]] FAQ
[[porting/guidelines]] FAQ: What does it take to move a piece of Debian packaged software to the GNU/Hurd port?

diff --git a/unsorted/PortingIssues.mdwn b/unsorted/PortingIssues.mdwn deleted file mode 100644 index 03980ef3..00000000 --- a/unsorted/PortingIssues.mdwn +++ /dev/null @@ -1,270 +0,0 @@ -## Table of Contents - -%TOC% - -## Overview - -This is a recompilation of common porting problems and their solutions. Information is gathered from the following sources: - -* [Debian GNU/Hurd port guidelines](http://www.debian.org/ports/hurd/hurd-devel-debian) - -* [James Morrison's GNU/Hurd pages](http://hurd.dyndns.org/) - -as well as other misc. sources. - -First of all, see [[BtsFiling]] if you need instructions on manipulating [Debian](http://www.debian.org/) source packages and submitting patches to their [Bug Tracking System](http://bugs.debian.org/). - -## System API limitations - -Sometimes building or running a program will fail due to bugs in the system API implementation (in Glibc and the Hurd). Make sure you check this list and know them before porting, otherwise you'll end up debugging something just to find out its an already known bug. - -We maintain a separate Wiki page for information on these bugs, see [[Distrib/SystemAPILimits]] - -If you think you can fix any of them and send a patch to the debian BTS, that'd be much appreciated. You may ask in for details or questions on the bug. - -## Undefined `bits/confname.h` macros (`PIPE_BUF`, ...) - -If macro `XXX` is undefined, but macro `_SC_XXX` or `_PC_XXX` is defined in `bits/confname.h`, you probably need to use `sysconf`, `pathconf` or `fpathconf` to obtain it dynamicaly. - -The following macros have been found in this offending situation (add more if you find them): `PIPE_BUF` - -An example with `sysconf`: (when you find a `sysconf` offending macro, put a better example) - - #ifndef XXX - #define XXX sysconf(_SC_XXX) - #endif - /* offending code using XXX follows */ - -An example with `fpathconf`: - - #ifdef PIPE_BUF - read(fd, buff, PIPE_BUF - 1); - #else - read(fd, buff, fpathconf(fd, _PC_PIPE_BUF) - 1); - #endif - /* note we can't #define PIPE_BUF, because it depends - on the "fd" variable */ - -## Bad File Descriptor - -If you get Bad File Descriptor error when trying to read from a file (or accessing it at all), check the `open()` invocation. The second argument is the access method. If it is a hard coded number instead of a symbol defined in the standard header files, the code is screwed and should be fixed to either use `O_RDONLY`, `O_WRONLY` or `O_RDWR`. This bug was observed in the `fortunes` and `mtools` packages for example. - -## `PATH_MAX` / `MAX_PATH` / `MAXPATHLEN` - -Every unconditionalized use of `PATH_MAX`, `MAX_PATH` or `MAXPATHLEN` is a POSIX incompatibility. If there is no upper limit on the length of a path (as its the case for GNU), this symbol is not defined in any header file. Instead, you need to either use a different implementation that does not rely on the length of a string or use `sysconf()` to query the length at runtime. If `sysconf()` returns -1, you have to use `realloc()` to allocate the needed memory dynamically. Usually it is thus simpler to just use dynamic allocation. Sometimes the amount is actually known. Else, a geometrically growing loop can be used: for instance, see [Alioth patch](http://alioth.debian.org/tracker/download.php/30628/410472/303735/1575/cpulimit-path-max-fix.patch). Note that in some cases there are GNU extensions that just work fine: when the `__GLIBC__` macro is defined, `getcwd()` calls can be just replaced by `get_current_dir_name()` calls. - -## `ARG_MAX` - -Same rationale as `PATH_MAX`. There is no limit on the number of arguments. - -## `IOV_MAX` - -Same rationale as `PATH_MAX`. There is no limit on the number of iovec items. - -## `MAXHOSTNAMELEN` - -Same as `PATH_MAX`. When you find a `gethostname()` function, which acts on a static buffer, you can replace it with Neal's [xgethostname function](http://ftp.walfield.org/pub/people/neal/xgethostname/) which returns the hostname as a dynamic buffer. For example: - -Buggy code: - - char localhost[MAXHOSTNAMELEN]; - ... - gethostname(localhost, sizeof(localhost)); - -Fixed code: - - #include "xgethostname.h" - ... - char *localhost; - ... - localhost = xgethostname(); - if (! localhost) - { - perror ("xgethostname"); - return ERROR; - } - ... - /* use LOCALHOST. */ - free (localhost); - -## `NOFILE` - -Replace with `getrlimit(RLIMIT_NOFILE,...)` - -## GNU specific `#define` - -If you need to include specific code for GNU/Hurd using `#if` ... `#endif`, then you can use the `__GNU__` symbol to do so. But think (at least) thrice! before doing so. In most situations, this is completely unnecessary and will create more problems than it may solve. Better ask on the mailing list how to do it right if you can't think of a better solution. - -## `sys_errlist[]` vs. `strerror()` - -If a program has only support for `sys_errlist[]` you will have to do some work to make it compile on GNU, which has dropped support for it and does only provide `strerror()`. Steinar Hamre writes about `strerror()`: - -`strerror()` should be used because: - -* It is the modern, POSIX way. -* It is localized. -* It handles invalid signals/numbers out of range. (better errorhandling and not a buffer-overflow-candidate/security risk) - -`strerror()` should always be used if it is available. Unfortunaly there are still some old non-POSIX systems that do not have `strerror()`, only `sys_errlist[]`. - -Today, only supporting `strerror()` is far better than only supporting `sys_errlist[]`. The best (from a portability viewpoint), however is supporting both. For configure.in, you will need: - - AC_CHECK_FUNCS(strerror) - -To `config.h.in`, you need to add: - - #undef HAVE_STRERROR - -Then something like: - - #ifndef HAVE_STRERROR - static char * - private_strerror (errnum) - int errnum; - { - extern char *sys_errlist[]; - extern int sys_nerr; - - if (errnum > 0 && errnum <= sys_nerr) - return sys_errlist[errnum]; - - return "Unknown system error"; - } - #define strerror private_strerror - #endif /* HAVE_STRERROR */ - -You can for example look in the latest coreutils (the above is a simplified version of what I found there.) Patches should of course be sent to upstream maintainers, this is very useful even for systems with a working `sys_errlist[]`. - -Of course, if you don't care about broken systems (like MS-DOG) not supporting `strerror()` you can just replace `sys_errlist[]` directly (upstream might not accept your patch, but debian should have no problem) - -## C++, `error_t` and `E*` - -On the Hurd, `error_t` is an enumeration of the `E*` constants. However, C++ -does not like `E*` integer macros being directly assigned to that enumeration. In short, replace - - error_t err = EINTR; - -by - - error_t err = error_t(EINTR); - -## Filenames ending in a slash \`/' - -Those are evil if they don't exist and you want to name a directory this way. For example, `mkdir foobar/` will not work on GNU. This is POSIX compatible. POSIX says that the path of a directory may have slashes appended to it. But the directory does not exist yet, so the path does not refer to a directory, and hence trailing slashes are not guaranteed to work. Just drop the slashes, and you're fine. - -## Missing `termio.h` - -Change it to use `termios.h` (check for it properly with autoconf `HAVE_TERMIOS_H` or the `__GLIBC__` macro) - -Also, change calls to `ioctl(fd, TCGETS, ...)` and `ioctl(fd, TCSETS, ...)` with `tcgetattr(fd, ...)` and `tcsetattr(fd, ...)`. - -## `AC_HEADER_TERMIO` - -The autoconf check for `AC_HEADER_TERMIO` tryes to check for termios, but it's only really checking for termio in `termios.h`. It is better to use `AC_CHECK_HEADERS(termio.h termios.h)` - -## missing `_IOT` - -This comes from ioctls. Fixing this is easy if the structure members can be expressed by using the _IOT() macro, else it's simply impossible... See `bits/termios.h` for an instance: - -`#define _IOT_termios /* Hurd ioctl type field. */ \ - _IOT (_IOTS (tcflag_t), 4, _IOTS (cc_t), NCCS, _IOTS (speed_t), 2)` - -because `struct termios` holds 4 members of type `tcflag_ts`, then `NCCS` -members of type `cc_tsi` and finaly 2 members of type `speed_ts`. - -As you can see, this limits the number of kinds of members to 3, and in -addition to that (see the bitfield described in `ioctls.h`), the third -kind of member is limited to 3 members. However, since at the API -compatibility layer you are generally allowed to reorder fields in -structures, you can usually manage to fit into these limits. - -Note: if a field member is a pointer, then the ioctl can't be expressed -this way, and that makes sense, since the server you're talking to -doesn't have direct access to your memory. Ways other than ioctls must -then be found. - -## `SA_SIGINFO` - -Not implemented, packages may be fixed for working around this: use void sighandler(int num) prototype and sa_handler field. - -## `SOL_IP` - -Not implemented yet. - -## `HZ` - -Linuxish and doesn't even make sense since the value may vary according to the running kernel. Should use `sysconf(_SC_CLK_TCK)` or `CLK_TCK` instead. - -## `SIOCDEVPRIVATE` - -Oh, we should probably provide it. - -## `MAP_NORESERVE` - -Not POSIX, but we could implement it. - -## `O_DIRECT` - -Long story to implement. - -## `PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP` - -We could easily provide it; - -## `PTHREAD_STACK_MIN` - -We should actually provide it. - -## `linux/types.h` or `asm/types.h` - -These are not POSIX, `sys/types.h` and `stdint.h` should be used instead. - -## `iopl` - -Not supported. Try to replace with `ioperm(0, 65536, 1)` (conditionned with `__GNU__` as that will not work in Linux). - -## `semget`, `sem_open` - -Not implemented, will always fail. Use `sem_init()` instead if possible. - -## `net/if_arp.h`, `net/ethernet.h`, etc. - -Not implemented, not POSIX. Try to disable the feature in the package. - -## broken libc6 dependency - -Some packages use an erroneous dependency on `libc6-dev`. This is incorrect because `libc6` is specific to GNU/Linux. The corresponding package for GNU is `libc0.3-dev` but other OSes will have different ones. You can locate the problem in the `debian/control` file of the source tree. Typical solutions include detecting the OS using `dpkg-architecture` and hardcoding the soname, or better, use a logical OR. eg: `libc6-dev | libc0.3-dev | libc-dev`. The `libc-dev` is a virtual package that works for any soname but you have to put it only as the last option. - ----- - -## ChangeLog - --- [[Main/TWikiGuest]] - 13 Jan 2005 - -Fix xgethostname example. - Neal - --- [[Main/RobertMillan]] - 22 Jul 2002 - -Formatting and minor grammatical fixes. - --- [[Main/JoachimNilsson]] - 09 Sep 2002 - -Added more examples and misc semantical fixes. - --- [[Main/RobertMillan]] - 05 Oct 2002 - -Added `xgethostname` example. - --- [[Main/RobertMillan]] - 15 Nov 2002 - -Added broken libc6 dependency - --- [[Main/RobertMillan]] - 21 Nov 2002 - -Text formatting. - --- Ognyan Kulev - 12 Mar 2003 - -Added `ioctl` entry. - --- [[Main/RobertMillan]] - 19 Mar 2003 -- cgit v1.2.3 From e016e16505f5b97959dba8edc05411ce17bd7b67 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 5 Apr 2009 18:44:10 +0200 Subject: unsorted/SystemAPILimits -> hurd/porting/system_api_limitations --- hurd/porting/guidelines.mdwn | 2 +- hurd/porting/system_api_limitations.mdwn | 41 ++++++++++++++++++++++++++++++++ hurd/running/distrib.mdwn | 2 +- unsorted/SystemAPILimits.mdwn | 30 ----------------------- 4 files changed, 43 insertions(+), 32 deletions(-) create mode 100644 hurd/porting/system_api_limitations.mdwn delete mode 100644 unsorted/SystemAPILimits.mdwn (limited to 'unsorted') diff --git a/hurd/porting/guidelines.mdwn b/hurd/porting/guidelines.mdwn index ee27c9be..f37a17e2 100644 --- a/hurd/porting/guidelines.mdwn +++ b/hurd/porting/guidelines.mdwn @@ -29,7 +29,7 @@ First of all, see [[BtsFiling]] if you need instructions on manipulating [Debian Sometimes building or running a program will fail due to bugs in the system API implementation (in Glibc and the Hurd). Make sure you check this list and know them before porting, otherwise you'll end up debugging something just to find out its an already known bug. -We maintain a separate Wiki page for information on these bugs, see [[Distrib/SystemAPILimits]] +We maintain a separate Wiki page for information on these bugs, see [[System_API_Limitations]] If you think you can fix any of them and send a patch to the debian BTS, that'd be much appreciated. You may ask in for details or questions on the bug. diff --git a/hurd/porting/system_api_limitations.mdwn b/hurd/porting/system_api_limitations.mdwn new file mode 100644 index 00000000..d536f764 --- /dev/null +++ b/hurd/porting/system_api_limitations.mdwn @@ -0,0 +1,41 @@ +[[meta copyright="Copyright © 2003, 2004, 2005, 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]]."]]"""]] + +## API Limitations of the GNU system + +---- + +Sometimes building or running a program will fail due to bugs in the system API implementation (in Glibc and the Hurd). Make sure you check this list and know them before porting, otherwise you'll end up debugging something just to find out its an already known bug. + +Taken from the bug lists in debian BTS. If you find more of them (and it is clear in the bug log that it is a bug), please add them to the list below. See: + +* ([source](http://packages.qa.debian.org/h/hurd.html) and [binary](http://packages.debian.org/hurd) debs not synchronized) +* ([binary](http://packages.debian.org/hurd-dev)) +* ([source](http://packages.qa.debian.org/g/glibc.html) & [binary](http://packages.debian.org/libc0.3) debs) +* ([binary](http://packages.debian.org/libc0.3-dev)) + +---- + +These are the known system API limits that have porting implications. + +**_[\#47998](http://bugs.debian.org/47998): `msgget` IPC not implemented_** + +**_[\#184565](http://bugs.debian.org/184565): libc0.3: missing shm\* functions (from ``)_**
**breaks:** cdrtools
**error:** warning: shm\* is not implemented and will always fail + +**_[\#190581](http://bugs.debian.org/190581): nice() doesn't work_**
**breaks:** coreutils
**error:** `nice()` doesn't take effect on some situations + +**_[\#187391](http://bugs.debian.org/187391): libc0.3-dev: `sockaddr_un.sun_path` can't be assigned a `const char *` when compiling with g++_**
**breaks:** fam, gail
**status:** maybe this should be in [[PortingIssues]] (see _long_ bug log) + +**_[\#190367](http://bugs.debian.org/190367): libc0.3-dev: `fcntl` `F_GETLK` not implemented (`ENOSYS`)_**
**breaks:** gnome-session (and others) from running
**error:** misc lock-related errors + +-- [[Main/RobertMillan]] - 01 May 2003 + +Text formatting.
-- [[Main/OgnyanKulev]] - 02 May 2003 diff --git a/hurd/running/distrib.mdwn b/hurd/running/distrib.mdwn index 607b50af..77736a45 100644 --- a/hurd/running/distrib.mdwn +++ b/hurd/running/distrib.mdwn @@ -95,7 +95,7 @@ about getting applications to work (if possible). * GNU [Coding Standards](http://www.gnu.org/prep/standards.html) * [[TestSuites]] - Posix, Perl, results feedback, etc. * [[Documentation]] -* [[SystemAPILimits]] +* [[System_API_Limitations]] * [[CodeAnnouncements]] - Recent coding projects related to the Hurd

[[IRC]]
[[WhoRunsGNU]]: -
[[HurdDevelopers]]: Who's who?
[[PersonalHurdPages]]