diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2019-07-27 11:06:50 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2019-07-27 11:06:50 +0200 |
| commit | 07368fe41963b31b37a250555ea5542381cdb9fa (patch) | |
| tree | 01177be2914f431ce9daa837acbb300346fa0a8f | |
| parent | e2027a822b2e2db39a19c8290b756a6d92674a44 (diff) | |
Fix typos (gnu.org RT #1409669)
(from th_g)
| -rw-r--r-- | microkernel/mach/gnumach/hardware_compatibility_list.mdwn | 4 | ||||
| -rw-r--r-- | user/jkoenig/d-i.mdwn | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn index 460c8aba..d7387d4c 100644 --- a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn +++ b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn @@ -17,7 +17,7 @@ GNU Mach current only supports the `x86` (alias `ia32` or `i386`) architecture. `amd64` systems seem to be troublesome more often than not. This is probably related to the same (chipset-related) problems we often see with recent machines; but it seems that `amd64` ones use problematic chipsets particularily -often. So far we haven't heard of similar problems with Intel's eqivalent +often. So far we haven't heard of similar problems with Intel's equivalent `ix64` (or `EM64T` as it used to be called) -- but maybe that just means fewer people tried running the Hurd on such machines :-) @@ -123,5 +123,5 @@ Some people couldn't get these hardware combinations to work with Hurd. The present Debian GNU/Hurd installer itself runs on Hurd, so failure on the installer may mean that the hardware is uncompatible with Hurd. * ASUS P5A motherboard and AMD K6-2 333MHz CPU - doesn't boot -* ASUS P2B-LS motherboard with an Intel PII-MMX 400 MHz CPU - this board had a defective onboard NIC (that could not be disable in BIOS) and working 3COM Etherlink III NIC in a PCI bus slot. This combination worked with GNU/Linux. The 3COM NIC is known to work with the Hurd. However, while gnumach/Hurd will boot on this system, it is confused by the defective onboard NIC and unable to use the 3COM NIC. Attempting to start networking generates a continous stream of eth0 and eth1 reset messages on the console that renders the system unusable. +* ASUS P2B-LS motherboard with an Intel PII-MMX 400 MHz CPU - this board had a defective onboard NIC (that could not be disable in BIOS) and working 3COM Etherlink III NIC in a PCI bus slot. This combination worked with GNU/Linux. The 3COM NIC is known to work with the Hurd. However, while gnumach/Hurd will boot on this system, it is confused by the defective onboard NIC and unable to use the 3COM NIC. Attempting to start networking generates a continuous stream of eth0 and eth1 reset messages on the console that renders the system unusable. * ASrock 775Twins-HDTV with a Pentium D 810 (533 MGz FSB/2600GHz core -- information no longer present on intel's site). Doesn't boot. diff --git a/user/jkoenig/d-i.mdwn b/user/jkoenig/d-i.mdwn index 9721b928..225debec 100644 --- a/user/jkoenig/d-i.mdwn +++ b/user/jkoenig/d-i.mdwn @@ -350,7 +350,7 @@ it works great and it's beautiful** * use busybox from my osports-debian branch (see link above) * tweak the d-i image build scripts * the symlink /lib/ld.so -> ld.so.1 needs to be created somehow - (youpi mentionned it being the job of libc0.3-udeb I think) + (youpi mentioned it being the job of libc0.3-udeb I think) * fix the poll() issue in libdebian-installer (patch to be submitted soon), also there is some hurd doxygen short-circuiting stuff |