From 50edfaff1fe9d3309b34358ec0c62d3c3354bc75 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 17 Mar 2013 13:10:14 +0100 Subject: small fixes: titles, details --- faq/2_gib_partition_limit.mdwn | 2 +- faq/debugging_inside_glibc.mdwn | 2 +- faq/debugging_translators.mdwn | 2 +- faq/df.mdwn | 2 ++ faq/eata.mdwn | 2 ++ faq/fuse_support.mdwn | 4 +--- faq/kernel_logs.mdwn | 4 +++- faq/off.mdwn | 2 +- faq/ram_limit.mdwn | 2 +- faq/sharing_the_user_space.mdwn | 6 +++--- faq/still_useful.mdwn | 7 +++++-- faq/xserver-common.mdwn | 2 +- 12 files changed, 22 insertions(+), 15 deletions(-) (limited to 'faq') diff --git a/faq/2_gib_partition_limit.mdwn b/faq/2_gib_partition_limit.mdwn index 195191cb..726605f9 100644 --- a/faq/2_gib_partition_limit.mdwn +++ b/faq/2_gib_partition_limit.mdwn @@ -8,6 +8,6 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -[[!meta title="2 GiB Partition Limit"]] +[[!meta title="Is there still a 2 GiB Partition Limit ?"]] The 2 GiB limit has been removed in Debian GNU/Hurd. diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn index 91b71d64..6f2d4ee3 100644 --- a/faq/debugging_inside_glibc.mdwn +++ b/faq/debugging_inside_glibc.mdwn @@ -9,7 +9,7 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -To get [[debugging]] information for glibc, you need to install the +In Debian, to get [[debugging]] information for glibc, you need to install the `libc0.3-dbg` package. At the place [[debugging/GDB]] looks for debugging symbols by default (`/usr/lib/debug/lib/`), Debian's `libc0.3-dbg` stores only the frame unwind information used for backtracing. If you want to step into diff --git a/faq/debugging_translators.mdwn b/faq/debugging_translators.mdwn index 262fd6aa..7a90a7e0 100644 --- a/faq/debugging_translators.mdwn +++ b/faq/debugging_translators.mdwn @@ -9,7 +9,7 @@ is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] In order to [[debug|debugging]] translators and being able to step into glibc -during it, you need the `hurd-dbg` and `libc0.3-dbg` packages installed. +during it, on Debian you need the `hurd-dbg` and `libc0.3-dbg` packages installed. If you need to debug the initialization of the translator, start the translator like diff --git a/faq/df.mdwn b/faq/df.mdwn index bbd3a7b9..51de2b6c 100644 --- a/faq/df.mdwn +++ b/faq/df.mdwn @@ -8,6 +8,8 @@ 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="Why doesn't df work?"]] + There is no `/etc/mtab` (due to dynamic translator startup, its content is hard to define actually, see [[the mtab GSoC project idea|community/gsoc/project_ideas/mtab]]), diff --git a/faq/eata.mdwn b/faq/eata.mdwn index fa7dbdec..411a1b16 100644 --- a/faq/eata.mdwn +++ b/faq/eata.mdwn @@ -8,6 +8,8 @@ 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/fuse_support.mdwn b/faq/fuse_support.mdwn index 3a442427..8867d954 100644 --- a/faq/fuse_support.mdwn +++ b/faq/fuse_support.mdwn @@ -11,6 +11,4 @@ License|/fdl]]."]]"""]] [[!meta title="Does Hurd support FUSE?"]] -There is a start of work on implementing a [[FUSE|hurd/libfuse]] library on Hurd; -currently, it still does provide all the functionalities needed to make -FUSE filesystems compile or work correctly, so it is not generally usable yet. +There is a start of work on implementing a [[FUSE|hurd/libfuse]] library on Hurd; its support is not updated to the latest version, but at least some fuse filesystems do work already. diff --git a/faq/kernel_logs.mdwn b/faq/kernel_logs.mdwn index 93df42bb..0c9e05a0 100644 --- a/faq/kernel_logs.mdwn +++ b/faq/kernel_logs.mdwn @@ -11,4 +11,6 @@ License|/fdl]]."]]"""]] [[!meta title="dmesg, kernel logs"]] -There is no `dmesg` command: the kernel does not keep a buffer of its messages. syslog however dumps them into `/var/log/dmesg`, so you can simply cat that. +There is no `dmesg` command, since the kernel does not keep a buffer of its +messages. syslog however dumps them into `/var/log/dmesg`, so you can simply cat +that. diff --git a/faq/off.mdwn b/faq/off.mdwn index 8c90d53e..48e6bcc7 100644 --- a/faq/off.mdwn +++ b/faq/off.mdwn @@ -8,7 +8,7 @@ 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="How am I supposed to shut my Hurd system down?"]] +[[!meta title="shutdown does not work, How am I supposed to shut my Hurd system down?"]] The GNU/Hurd does not use SYSV runlevels, so commands like diff --git a/faq/ram_limit.mdwn b/faq/ram_limit.mdwn index 458a047d..4043203e 100644 --- a/faq/ram_limit.mdwn +++ b/faq/ram_limit.mdwn @@ -11,7 +11,7 @@ License|/fdl]]."]]"""]] [[!meta title="830 MiB RAM Limit"]] -Just like any 32bit OS without bad tricks, GNU Mach does not cope well with lots +Just like any 32bit OS without bad tricks, GNU Mach can not cope well with lots of memory. Latest versions of the Debian `gnumach` package will limit themselves to around 1.7 GiB of memory. If you want more, you can twiddle the `VM_MAX_ADDRESS` limit between kernelland and userland in `i386/include/mach/i386/vm_param.h`. diff --git a/faq/sharing_the_user_space.mdwn b/faq/sharing_the_user_space.mdwn index ec880827..8702470a 100644 --- a/faq/sharing_the_user_space.mdwn +++ b/faq/sharing_the_user_space.mdwn @@ -8,11 +8,11 @@ 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]]."]]"""]] -*Question:* Could it be possible to have a system installation where you can +[[!meta title=" Could it be possible to have a system installation where you can dual-boot using either the [[Linux]] kernel, or the GNU Hurd, so that -everything but the kernel is shared? +everything but the kernel is shared?]] -*Answer:* Given that both Linux and GNU Hurd are using the [[ELF]] binary +Given that both Linux and GNU Hurd are using the [[ELF]] binary format, this could indeed be made possible, if all programs agreed to rely on only one abstraction layer, for example the standard C library ([[glibc]]). (Additionally, for example for [[system call]]s that are not covered by glibc diff --git a/faq/still_useful.mdwn b/faq/still_useful.mdwn index bffeaebd..919eb9d4 100644 --- a/faq/still_useful.mdwn +++ b/faq/still_useful.mdwn @@ -8,8 +8,10 @@ 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]]."]]"""]] -what are the advantages with the Hurd over Linux, in general of course, nothing -in depth +[[!meta title="Why is the Hurd useful?"]] + +What are the advantages with the Hurd over Linux? (In general of course, nothing +in depth) > Flexibility for the user: > @@ -30,6 +32,7 @@ in depth >> entirely doable now in Linux with FUSE or things like it. >>> Nowadays, at LAST, yes, partly. +>>> And only on machines where fuse is enabled. Is it enabled on the servers you have an account on? >> I'm not sure if an ftp filesystem has been implemented for FUSE yet, but its >> definately doable; and loopback filesystems like in your second example have diff --git a/faq/xserver-common.mdwn b/faq/xserver-common.mdwn index 3420154c..460c6e55 100644 --- a/faq/xserver-common.mdwn +++ b/faq/xserver-common.mdwn @@ -9,7 +9,7 @@ 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="normal users can't start X"]] +[[!meta title="Normal users can't start X"]] You need to run `dpkg-reconfigure x11-common` and select `Anybody` for starting X as there is no way to detect console users currently. -- cgit v1.2.3