diff options
Diffstat (limited to 'faq')
| -rw-r--r-- | faq/2_gib_partition_limit.mdwn | 4 | ||||
| -rw-r--r-- | faq/apt_umount.mdwn | 28 | ||||
| -rw-r--r-- | faq/drivers.mdwn | 27 | ||||
| -rw-r--r-- | faq/fd.mdwn | 21 | ||||
| -rw-r--r-- | faq/fsck.mdwn (renamed from faq/sudo.mdwn) | 18 | ||||
| -rw-r--r-- | faq/libpthread_dlopen.mdwn | 12 | ||||
| -rw-r--r-- | faq/off.mdwn | 30 | ||||
| -rw-r--r-- | faq/old_faq.txt | 12 | ||||
| -rw-r--r-- | faq/software.mdwn | 2 |
9 files changed, 43 insertions, 111 deletions
diff --git a/faq/2_gib_partition_limit.mdwn b/faq/2_gib_partition_limit.mdwn index 6b48cc5f..210d8afb 100644 --- a/faq/2_gib_partition_limit.mdwn +++ b/faq/2_gib_partition_limit.mdwn @@ -11,9 +11,9 @@ License|/fdl]]."]]"""]] [[!tag faq/support]] -[[!meta title="Is there still a 2 GiB Partition Limit?"]] +[[!meta title="Is there still a 2 GiB ext2fs disk partition limit?"]] -The 2 GiB limit has been removed in Debian GNU/Hurd. +The 2 GiB limit has been removed. IDE disk drivers however currently do not support more than 2^28 sectors, i.e. 128GiB. diff --git a/faq/apt_umount.mdwn b/faq/apt_umount.mdwn deleted file mode 100644 index c8dc3eb4..00000000 --- a/faq/apt_umount.mdwn +++ /dev/null @@ -1,28 +0,0 @@ -[[!meta copyright="Copyright © 2007, 2008, 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]]."]]"""]] - -[[!tag faq/debian]] - -[[!meta title="apt: unmount cdroms"]] - -You can add a shell script umount so that apt can automatically unmount cdroms. - - #!/bin/sh - # Filename: /usr/bin/umount - - settrans -fg "$@" - -Give executable permission to the script. - - # chmod +x /usr/bin/umount - -In `/etc/fstab` add a trailing `/` after cdrom like `/cdrom/` since apt uses a -trailing `/`. diff --git a/faq/drivers.mdwn b/faq/drivers.mdwn index 57ed7ea9..50bd4542 100644 --- a/faq/drivers.mdwn +++ b/faq/drivers.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2009, 2013 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2009, 2013, 2015 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 @@ -10,18 +11,18 @@ License|/fdl]]."]]"""]] [[!tag faq/support faq/_important]] -[[!meta title="What drivers does GNU/Hurd have?"]] +[[!meta title="what hardware is supported? What drivers does GNU/Hurd have?"]] + +Currently, for disks Mach integrates old drivers from Linux through some +[[community/gsoc/project_ideas/driver_glue_code]], which provide +IDE disk support, and we have an AHCI driver which provides [[SATA +support|faq/sata_disk_drives]]. For network boards, we use the [[DDE]] toolkit +to run linux 2.6.32 drivers in userland processes, which provides both long-term +support for new hardware and safety against driver bugs. Note however that we +have of course not tested all drivers, we obviously don't even have all kinds of +hardware. So we can not promise that they will all work. What probably +works for sure is what we usually use: the rtl8139 and e1000 drivers for +instance. Firmware loading is not implemented yet. -Currently, for disks Mach integrates drivers from Linux 2.0 through some -[[community/gsoc/project_ideas/driver_glue_code]]. As it's very old, that -limits hardware support a lot, of course. For network boards, we use the -[[DDE]] toolkit to run linux 2.6.32 drivers in userland processes, -which provides both long-term support for new hardware and safety against driver -bugs. Firmware loading is however not implemented yet. [[microkernel/mach/gnumach/ports/Xen]] is also supported, both blkfront and netfront. - -Note however that we have of course not tested all drivers, we obviously don't -even have all kinds of hardware. So we can not promise that they will all -work. What probably works for sure is what we usually use: the rtl8139 or e1000 -drivers for instance. diff --git a/faq/fd.mdwn b/faq/fd.mdwn deleted file mode 100644 index bae611f8..00000000 --- a/faq/fd.mdwn +++ /dev/null @@ -1,21 +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]]."]]"""]] - -[[!tag faq/open_issues]] - -[[!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. - -To avoid it, you can as well remove `/dev/fd0` (do you really have a floppy -around you anyway?) diff --git a/faq/sudo.mdwn b/faq/fsck.mdwn index 3e2a76e7..b50d6953 100644 --- a/faq/sudo.mdwn +++ b/faq/fsck.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2014 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 @@ -8,9 +9,16 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] -[[!tag faq/running]] +[[!tag faq/open_issues]] -[[!meta title="dhclient, halt, mke2fs not available through sudo su"]] +[[!meta title="fsck shows a lot of errors"]] -Debian GNU/Hurd's ``sudo su`` does not add `/sbin` into `PATH`, unlike Linux has -been doing since recently. One has to use ``sudo su -`` . +Quite a few of them are actually benign: + + /dev/hd0s1: Deleted inode 95849 has zero dtime. FIXED. + +see [[open_issues/ext2fs_dtime]] + + /dev/hd0s1: i_file_acl_hi for inode 81872 (/proc) is 32, shoud be 0. + +see [[open_issues/e2fsck_i_file_acl_hi]] diff --git a/faq/libpthread_dlopen.mdwn b/faq/libpthread_dlopen.mdwn index 94d091a4..3b365fad 100644 --- a/faq/libpthread_dlopen.mdwn +++ b/faq/libpthread_dlopen.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2013, 2014, 2015 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 @@ -14,12 +15,13 @@ License|/fdl]]."]]"""]] Some applications don't themselves link against libpthread, but then load plugins which do link against libpthread. This means internally switching from -single-threading to multi-threading, which is [[not yet -supported|open_issues/libpthread_dlopen]] by our [[/libpthread]], and results -in errors such as: +single-threading to multi-threading, which is only supported since libc0.3 +2.19-16~2. Previously, it would result in errors such as: ./pthread/../sysdeps/generic/pt-mutex-timedlock.c:70: __pthread_mutex_timedlock_internal: Assertion `__pthread_threads' failed. -This can be worked around by making the application link against libpthread (i.e. not only the plugin, but also the main binary), or without recompiling by explicitly pre-loading libpthread, for example: +This could be worked around by making the application link against libpthread (i.e. not only the plugin, but also the main binary), or without recompiling by explicitly pre-loading libpthread, for example: $ LD_PRELOAD=/lib/i386-gnu/libpthread.so.0.3 [application] + +But it should now be gone, simply upgrade libc0.3. diff --git a/faq/off.mdwn b/faq/off.mdwn deleted file mode 100644 index 4d012449..00000000 --- a/faq/off.mdwn +++ /dev/null @@ -1,30 +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]]."]]"""]] - -[[!tag faq/running]] - -[[!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 - - # shutdown -h now - -will not work. Simply use the equivalent shortcuts - - # halt - # reboot - -to respectively shutdown and reboot Hurd, provided natively, -instead of from SYSV runlevels. - -[[!tag open_issue_gnumach]] -GNU Mach does not have APM or ACPI support, so it will just stop with -`In tight loop: hit ctl-alt-del to reboot`, and you can switch off the -system. diff --git a/faq/old_faq.txt b/faq/old_faq.txt index e370277e..7946062e 100644 --- a/faq/old_faq.txt +++ b/faq/old_faq.txt @@ -219,9 +219,9 @@ prompt. ?? How do I enable color on the console? {NHW} If you are using the GNU Mach microkernel, you can set your -terminal to `mach-color'. For instance: +terminal to `mach-gnu-color'. For instance: - # export TERM=mach-color + # export TERM=mach-gnu-color ?? How can I enable virtual consoles? @@ -238,15 +238,15 @@ then hitting C-A-<backspace> will exit it. ?? What is the status of X? {MB} It works! The packages are available at any Debian ftp mirror. -XFree86 4.0.2 is available, as are some of the v3 servers. Instructions +Xorg is available, as are some of the v3 servers. Instructions on how to use the packages are in the mailing list archive (link follow later). ?? What are these strange pids `0`, `2', `3', `4`, and `5`? -{MB,ST} Zero is the `proc` processus server (and thus does not really have a pid -:) ) Two is the kernel, three is the root filesystem server, four is the `exec` -server (which handles starting programs), five is the `auth` server (which +{MB,ST} Zero is the kernel, one is the root filesystem server, two is the +`exec` server (which handles starting programs), three is the init process, four +is the `proc` processus server, five is the `auth` server (which handles user authentication). ?? Why does `ps aux' give me strange output? diff --git a/faq/software.mdwn b/faq/software.mdwn index 4ab7bbfc..719e123c 100644 --- a/faq/software.mdwn +++ b/faq/software.mdwn @@ -13,7 +13,7 @@ License|/fdl]]."]]"""]] [[!meta title="What software is available for GNU?"]] -As of March 2013, 78% of all [Debian](http://www.debian.org/) +As of March 2014, 79% of all [Debian](http://www.debian.org/) [packages](http://packages.debian.org/) are available for [[Debian GNU/Hurd|hurd/running/debian]]. Of course, testing and bug fixing is welcome, as we have obviously not tested all of them. |