diff options
Diffstat (limited to 'faq')
| -rw-r--r-- | faq/2_gib_partition_limit.mdwn | 4 | ||||
| -rw-r--r-- | faq/drivers.mdwn | 5 | ||||
| -rw-r--r-- | faq/emacs.mdwn | 15 | ||||
| -rw-r--r-- | faq/fd.mdwn | 3 | ||||
| -rw-r--r-- | faq/sata_disk_drives.mdwn | 8 | ||||
| -rw-r--r-- | faq/slow.mdwn | 3 | ||||
| -rw-r--r-- | faq/still_useful.mdwn | 3 |
7 files changed, 32 insertions, 9 deletions
diff --git a/faq/2_gib_partition_limit.mdwn b/faq/2_gib_partition_limit.mdwn index 3fd43793..6b48cc5f 100644 --- a/faq/2_gib_partition_limit.mdwn +++ b/faq/2_gib_partition_limit.mdwn @@ -15,4 +15,6 @@ License|/fdl]]."]]"""]] The 2 GiB limit has been removed in Debian GNU/Hurd. -Disk drivers however currently do not support more than 2^32 sectors, i.e. 2TiB. +IDE disk drivers however currently do not support more than 2^28 sectors, i.e. 128GiB. + +The AHCI disk driver supports up to 2^32 sectors, i.e. 2TiB. diff --git a/faq/drivers.mdwn b/faq/drivers.mdwn index 197d47b7..57ed7ea9 100644 --- a/faq/drivers.mdwn +++ b/faq/drivers.mdwn @@ -17,8 +17,9 @@ Currently, for disks Mach integrates drivers from Linux 2.0 through some 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. [[microkernel/mach/gnumach/ports/Xen]] is also supported, both blkfront -and netfront. +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 diff --git a/faq/emacs.mdwn b/faq/emacs.mdwn new file mode 100644 index 00000000..4542c666 --- /dev/null +++ b/faq/emacs.mdwn @@ -0,0 +1,15 @@ +[[!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/running]] + +[[!meta title="Emacs says /dev/tty is not a tty"]] + +Old versions of emacs used to have this issue. This is fixed in emacs24. diff --git a/faq/fd.mdwn b/faq/fd.mdwn index e0fefc66..bae611f8 100644 --- a/faq/fd.mdwn +++ b/faq/fd.mdwn @@ -16,3 +16,6 @@ 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/sata_disk_drives.mdwn b/faq/sata_disk_drives.mdwn index 70560f12..4864e35b 100644 --- a/faq/sata_disk_drives.mdwn +++ b/faq/sata_disk_drives.mdwn @@ -12,8 +12,6 @@ License|/fdl]]."]]"""]] [[!meta title="Are SATA disk drives supported?"]] -GNU Mach does not support SATA disk drives (`/dev/sda` etc. in GNU/Linux) -natively, so using `device:sd0s1` will not work, as sd* devices are for SCSI -drives only. -The only way to get those drives to work is to put them into compatibility mode -in the BIOS, if such an option exists. GNU Mach will then recognize them as hda etc. +Until recently, GNU Mach did not support SATA disk drives (`/dev/sda` etc. in GNU/Linux) natively, the only way to get those drives to work used to be to put them into compatibility mode in the BIOS, if such an option exists. GNU Mach will then recognize them as hd etc. + +An AHCI driver has been added on 10th May 2013, which should bring support for a wide range of SATA controlers. Please however make sure to configure the BIOS in AHCI mode (as opposed to RAID mode). diff --git a/faq/slow.mdwn b/faq/slow.mdwn index be01e882..80c4ed00 100644 --- a/faq/slow.mdwn +++ b/faq/slow.mdwn @@ -22,7 +22,8 @@ hold. The main reason for slowness is *not* because of the overhead of RPCs. It's mostly simply because less care has been done on implementing what makes Linux -fast: intelligent read-ahead, carefully-tuned page cache, etc. +fast: intelligent read-ahead, carefully-tuned page cache, etc. or even just +missing DMA support for your disk controller. There is no ground reason this can not be achieved on GNU/Hurd, it has just not been a priority until now (first make it work, then make it work fast). We are diff --git a/faq/still_useful.mdwn b/faq/still_useful.mdwn index 60149a2b..8d7e3f28 100644 --- a/faq/still_useful.mdwn +++ b/faq/still_useful.mdwn @@ -20,6 +20,9 @@ develop custom replacements for them. Users will be able to write and use their own file systems, their own `exec' servers, or their own network protocols if they like, all without disturbing other users. +A [[series of interesting examples|hurd/documentation/translator_primer]] is +available. + The Linux kernel has now been modified to allow user-level file systems, so there is proof that people will actually use features such as these. It will be much easier to do under the Hurd, however, |