diff options
| -rw-r--r-- | contributing.mdwn | 6 | ||||
| -rw-r--r-- | faq/2_gib_partition_limit.mdwn | 4 | ||||
| -rw-r--r-- | hurd/running/debian/qemu_image.mdwn | 2 |
3 files changed, 6 insertions, 6 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index 9403e670..6666e242 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -160,9 +160,8 @@ packages](http://people.debian.org/~sthibault/hurd-i386/failed_packages.txt). This is the list of tasks that we *want* to address soon, starting with the most pressing: -* Fix shell output pipe replacement issue on amd64, see -[discussion](https://lists.gnu.org/archive/html/bug-hurd/2023-10/msg00062.html). - - This means adding an `i386x_float_state` and `i386_XFLOAT_STATE` thread status, that glibc would be able to use along `i386_REGS_SEGS_STATE` and `i386_FLOAT_STATE` in `_hurd_setup_sighandler` and `sigtreturn.c`. The structure would contain the `fp_save_kind`. That'll actually be needed both on `i386` and `x86_64` actually, to fix SSE use against signals in general. +* Finish fixing shell output pipe replacement issue on amd64, see +[discussion](https://lists.gnu.org/archive/html/bug-hurd/2025-04/msg00021.html). * Check the [packages build failures differences](https://people.debian.org/~sthibault/hurd-amd64/failed_diff.txt) between hurd-i386 and hurd-amd64: they are failing on hurd-amd64 but are successful on hurd-i386. Possibly it's just a mere missing `s/hurd-i386/hurd-any/` in the debian/ directory, or a new bug that actually also affects hurd-i386 if you rebuild the package there now, but possibly it's a more profound issue in the amd64 port. * On amd64, fix crash-core * On amd64, fix running posixtestsuite (not necessarily fixing the tests themselves, but at least make sure it doesn't crash the box ; it could still be useful to compare the output on 32bit and 64bit are the same with the same gnumach/hurd/glibc). @@ -194,6 +193,7 @@ This is the list of tasks that we *want* to address soon, starting with the most * Fix building `wayland`. * Port `python-procps`. * Implement a `rumpnet`. + * A first version was committed, with just the wm support is included. The phy lib is there but not the if_* drivers. * Implement a `rumpfs`. * Fix `SMP` support. diff --git a/faq/2_gib_partition_limit.mdwn b/faq/2_gib_partition_limit.mdwn index fa5105bd..654379a3 100644 --- a/faq/2_gib_partition_limit.mdwn +++ b/faq/2_gib_partition_limit.mdwn @@ -15,8 +15,8 @@ License|/fdl]]."]]"""]] The 2 GiB ext2fs limit has been removed. -IDE disk drivers however currently do not support more than 2^28 sectors, i.e. 128GiB. +IDE disk drivers (`hd*`) however currently do not support more than 2^28 sectors, i.e. 128GiB. -The gnumach AHCI disk driver supports up to 2^48 sectors, i.e. 128PiB, but the device interface supports only 2^32 sectors, i.e. 2TiB. +The gnumach AHCI disk driver (`sd*`) and rumpkernel drivers (`wd*`) support up to 2^48 sectors, i.e. 128PiB, but the device interface supports only 2^32 sectors, i.e. 2TiB. You can have a bigger disk, you just should not put disk partitions beyond these limits for the drivers to be able to read from them. diff --git a/hurd/running/debian/qemu_image.mdwn b/hurd/running/debian/qemu_image.mdwn index 8409bc8c..c6da1555 100644 --- a/hurd/running/debian/qemu_image.mdwn +++ b/hurd/running/debian/qemu_image.mdwn @@ -42,7 +42,7 @@ Optionally you may use `--curses` to keep your keyboard layout. If need be modpr Note that if you do not have a command named `kvm`, you can try something across the lines of: - $ qemu-system-i386 --enable-kvm -drive cache=writeback,file=$(echo debian-hurd-*.img) -net user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000 + $ qemu-system-i386 --enable-kvm -m 2G -drive cache=writeback,file=$(echo debian-hurd-*.img) -net user,hostfwd=tcp:127.0.0.1:2222-:22 -net nic,model=e1000 Or, if your machine does not allow for KVM acceleration, omit `--enable-kvm` from the command. |