From 38cfa89677eabc85fc23e31e24cee85fb1ecfa54 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 13 Apr 2013 10:36:54 +0200 Subject: Rework FAQ machinery to be based on tags instead of filenames. --- faq/issues/bad_hypermeta_data.mdwn | 15 ------------ faq/issues/eata.mdwn | 15 ------------ faq/issues/fd.mdwn | 16 ------------- faq/issues/got_a_db_prompt.mdwn | 34 ---------------------------- faq/issues/native-install_doesnt_finish.mdwn | 24 -------------------- 5 files changed, 104 deletions(-) delete mode 100644 faq/issues/bad_hypermeta_data.mdwn delete mode 100644 faq/issues/eata.mdwn delete mode 100644 faq/issues/fd.mdwn delete mode 100644 faq/issues/got_a_db_prompt.mdwn delete mode 100644 faq/issues/native-install_doesnt_finish.mdwn (limited to 'faq/issues') diff --git a/faq/issues/bad_hypermeta_data.mdwn b/faq/issues/bad_hypermeta_data.mdwn deleted file mode 100644 index bc960e30..00000000 --- a/faq/issues/bad_hypermeta_data.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -If you get the error `bad hypermeta data` when trying to mount an ext3 -partition from GNU/Linux, that is usually because the file system has not been -unmounted cleanly (maybe GNU/Linux got suspended to disk) and the Hurd cannot -mount it as ext2 without checking. Either boot back into GNU/Linux and unmount -it or you can try to run `fsck.ext3` from GNU/Hurd directly. diff --git a/faq/issues/eata.mdwn b/faq/issues/eata.mdwn deleted file mode 100644 index b9b0565a..00000000 --- a/faq/issues/eata.mdwn +++ /dev/null @@ -1,15 +0,0 @@ -[[!meta copyright="Copyright © 2010, 2013 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] - -[[!meta title="Boot seems to get stuck at EATA probing"]] - -In some virtual machines (e.g. VirtualBox), "probing eata on XXX" may be -quite long. This is apparently due to poor efficiency of the virtualizer, not -Mach. There is no such issue on real hardware or using qemu/kvm. diff --git a/faq/issues/fd.mdwn b/faq/issues/fd.mdwn deleted file mode 100644 index 514ab378..00000000 --- a/faq/issues/fd.mdwn +++ /dev/null @@ -1,16 +0,0 @@ -[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="I'm getting I/O eror, dev 02:00, sector 0"]] - -dev 02:00 is the floppy drive. This message simply means that reading the floppy -was attempted, but no floppy disk was inserted, so it failed. It commonly -happens during installer disk detection, or grub setup, and is completely -harmless. diff --git a/faq/issues/got_a_db_prompt.mdwn b/faq/issues/got_a_db_prompt.mdwn deleted file mode 100644 index ad99c515..00000000 --- a/faq/issues/got_a_db_prompt.mdwn +++ /dev/null @@ -1,34 +0,0 @@ -[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!meta title="Help, I've just gotten a db> prompt"]] - -If you see a `db>` prompt on the console, something unexpected and bad happened -inside the [[GNU Mach kernel|microkernel/mach/gnumach]], which it cannot -recover from. (Think of it as the equivalent of a [[!wikipedia -Linux_kernel_oops]], for example.) The `db>` prompt is actually the GNU Mach -kernel debugger waiting for your commands. For example, you can then reboot -the system by issuing the `reboot` command, or if you want to help analyze the -problem, start by typing in the `trace` command, which will display the -function call trace leading to the crash: - - 0x8007cf1(8088488,5e,40000008,2aa008,0) - 0x80071bc(0,0,0,0,0) - 0x8006831(24fe00,2000,b,800,0) - -This can be decyphered by using: - - $ addr2line -i -f -e /boot/gnumach 0x8007cf1 0x80071bc 0x8006831 - -You can then [[send us|contact_us]] the whole results of the `trace` and the -`addr2line` commands, as well as -the exact version of the GNU Mach kernel you were running, for further -investigation. More information about the [[GNU Mach -debugger|microkernel/mach/gnumach/debugging]] is available. diff --git a/faq/issues/native-install_doesnt_finish.mdwn b/faq/issues/native-install_doesnt_finish.mdwn deleted file mode 100644 index a852e1dd..00000000 --- a/faq/issues/native-install_doesnt_finish.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -Copying baseGNU to the virtual disk works. Even booting got through but when I -try to run native-install it never gets to the very end. First time it froze on -*sed* package, the other time on *sysv-rc*. - -> How much memory did you configure for the [[QEMU]] system? It may simply be -> -- I've seen this myself -- that the system runs out of memory, as at the -> native-install stage (I think at least) swap is not yet configured and -> enabled. What I've been doing is: boot (with -s), MAKEDEV hdWHATEVER in -> /dev/ for the swap device, run /hurd/mach-defpager, followed by swapon -> /dev/hdWHATEVER. Does this help? - ->> Thank You very much, more memory solved the freezing. - -[[!tag open_issue_hurd]] -- cgit v1.2.3