Re: (hurd) Installable desktop environments

Narcis Garcia, le ven. 16 juin 2023 10:29:15 +0200, a ecrit: > El 16/6/23 a les 8:26, Samuel Thibault ha escrit: > > Narcis Garcia, le ven. 16 juin 2023 07:56:51 +0200, a ecrit: > > > After tasksel stage (Xfce selected), and a veery loong time to retrieve > > > > Th

Re: (hurd) Installable desktop environments

Narcis Garcia, le ven. 16 juin 2023 11:09:27 +0200, a ecrit: > El 16/6/23 a les 10:38, Samuel Thibault ha escrit: > > Narcis Garcia, le ven. 16 juin 2023 10:29:15 +0200, a ecrit: > > > El 16/6/23 a les 8:26, Samuel Thibault ha escrit: > > > > Narcis Garcia, le ven.

Re: How can i help?

Hello, Marius Gripsgard, le jeu. 15 juin 2023 23:04:16 +, a ecrit: > I'm a soon to be DD (only awaiting approval) Welcome! > How can i help out? what are the most pressing issue? Some Debian-specific development information is collected on: https://www.debian.org/ports/hurd/hurd-devel-debi

Re: Everything's broken (was: Debian GNU/Hurd 2023 released!)

Hello, Sergey Bugaev, le mer. 14 juin 2023 18:40:15 +0300, a ecrit: > > And most people just forgetting that it's just the same with *any* > > OS that doesn't have a huge testing team. Any departure from what is > > actually tested will get issues, very obviously. One just can't test the > > whole

Re: Everything's broken (was: Debian GNU/Hurd 2023 released!)

Sergey Bugaev, le jeu. 15 juin 2023 11:52:24 +0300, a ecrit: > On Thu, Jun 15, 2023 at 2:14 AM Samuel Thibault > wrote: > > > Well, if there was, say, a call for pre-release testing, > > > > Well, Debian did ask for testing. > > > > I guess I should exp

Re: Everything's broken (was: Debian GNU/Hurd 2023 released!)

Sergey Bugaev, le jeu. 15 juin 2023 11:52:24 +0300, a ecrit: > On Thu, Jun 15, 2023 at 2:14 AM Samuel Thibault > wrote: > > > So the installed system is not to blame, it must be that the installer > > > is corrupting the FS somehow. > > > > Possibly some mi

Re: usr/libexec/console-run: /dev/console: Read-only file system

Marcin Laszewski, le sam. 24 juin 2023 22:03:45 +0200, a ecrit: > I've added 'set -v -x' to /etc/hurd/runsystem.sysv and I see executed > commands. > The 'pipe' error occures between '# Check boot flags' and '#Start the > default pager'. > As I understand I have to launch 'shell' before it, and ru

Re: usr/libexec/console-run: /dev/console: Read-only file system

Marcin Laszewski, le dim. 25 juin 2023 21:44:06 +0200, a ecrit: > 2023-06-25 17:10 GMT+02:00, Samuel Thibault : > > Marcin Laszewski, le sam. 24 juin 2023 22:03:45 +0200, a ecrit: > >> (...) > >> The 'pipe' error occures between '# Check boot flags'

Re: jemalloc's Hurd patch

Hello, Faidon Liambotis, le lun. 17 juil. 2023 00:24:42 +0300, a ecrit: > On Tue, May 16, 2023 at 06:31:58PM +0300, Faidon Liambotis wrote: > > On Tue, May 16, 2023 at 05:22:44PM +0200, Samuel Thibault wrote: > > > For information, I have completed and submitted jemall

Re: jemalloc's Hurd patch

Hello, Faidon Liambotis, le ven. 18 août 2023 06:42:48 +0300, a ecrit: > On Mon, Aug 07, 2023 at 11:02:14AM +0200, Samuel Thibault wrote: > > I had work pending to fix that, I have now done it, and will commit it. > > With that done, the testsuite does pass indeed. > > Thank

More memory with PAE

Hello, FI, apparently I managed to fix the last bugs concerning PAE execution, it works fine on my box, thus opening the path for >4GiB memory even on i386. Concerning rumpdisk, I had to fix it to allow PAE, so don't run a PAE kernel without installing the hurd package >= 1:0.9.git20230520-4+b1.

Re: More memory with PAE

Samuel Thibault, le mer. 30 août 2023 01:36:57 +0200, a ecrit: > Concerning rumpdisk, I had to fix it to allow PAE, so don't run a PAE > kernel without installing the hurd package >= 1:0.9.git20230520-4+b1. (which is not available yet, it'll get built once rumpkernel gets

Re: jemalloc's Hurd patch

Hello, Samuel Thibault, le ven. 18 août 2023 16:10:39 +0200, a ecrit: > Faidon Liambotis, le ven. 18 août 2023 06:42:48 +0300, a ecrit: > > On Mon, Aug 07, 2023 at 11:02:14AM +0200, Samuel Thibault wrote: > > > I had work pending to fix that, I have now done it, and will com

Re: expect eats all the ptys

Hello, Craig Small, le jeu. 07 sept. 2023 22:25:37 +1000, a ecrit: > spawn creates a new process and links the ptys, wait waits for the process to > die, if you change the "spawn true" to "spawn sleep 2" you'll see the script > slow down. > > The script completes, ps shows no lurking scripts or t

Re: expect eats all the ptys

Samuel Thibault, le jeu. 07 sept. 2023 16:55:33 +0200, a ecrit: > Craig Small, le jeu. 07 sept. 2023 22:25:37 +1000, a ecrit: > > spawn creates a new process and links the ptys, wait waits for the process > > to > > die, if you change the "spawn true" to "

Re: expect eats all the ptys

Hello, Craig Small, le ven. 08 sept. 2023 16:26:35 +1000, a ecrit: > In other news, procps 4.0.4 should work on Hurd. I removed a PATH_MAX and > fixed > the library to not use /proc/sys for Linux version. Great :D > I'm actually going to look at the procfs first, being the procps/psmisc > auth

Re: jemalloc's Hurd patch

Faidon Liambotis, le mar. 12 sept. 2023 19:03:30 +0300, a ecrit: > > I have uploaded version 2.37-8~0 on debian-ports's unreleased, so it's > > available on buildds as well. I have upgraded exodar. > > I just uploaded jemalloc 5.3.0-2 containing the updated Hurd patch. I > first tried a test build

Re: 64bit startup

Hello, Good news! It seems I fixed the bug that was making my 64bit VM crashing quite often. The problem was that when receiving a message from userland, ipc_kmsg_get would allocate a kernel buffer with the same size as the userland message. But since we may expand the 32bit port names into 64bit

Re: Adding hurd-amd64 on debian-ports?

Hello, Aurelien Jarno, le jeu. 11 mai 2023 21:49:07 +0200, a ecrit: > On 2023-05-02 22:01, Samuel Thibault wrote: > > Could you create a debian-ports repo for hurd-amd64? > > > > Yes, that is coming out :) > > > > For now we have not tested a whole debi

Re: 64bit startup

Hello, Some update on the 64bit port: - The debian-ports archive now has enough packages to bootstrap a chroot. - A 64bit debian buildd is getting set up, not much work is left there. - The hurd-amd64 wanna-build infrastructure is to be set up in the coming days. *but* Building packages is not

Re: 64bit startup

jbra...@dismail.de, le mer. 25 oct. 2023 03:40:16 +, a ecrit: > >> lol... and > > > > Exactly. So what? > > > > Some folks have witty humor and appreciate the nostalgia. Others don't. > > > > If you don't like my posts, then plonk me. > > > > Jeff >

Re: 64bit startup

t; > >> On 25 Oct 2023, at 02:26, Jeffrey Walton wrote: > > >>> > > >>> On Tue, Oct 24, 2023 at 6:21 PM Samuel Thibault > > >>> wrote: > > >>>> > > >>>> Some update on the 64bit port: > > >>>&

Re: 64bit startup

jbra...@dismail.de, le mer. 25 oct. 2023 11:52:02 +, a ecrit: > October 25, 2023 3:43 AM, "Samuel Thibault" wrote: > > jbra...@dismail.de, le mer. 25 oct. 2023 03:40:16 +, a ecrit: > > > >> Or maybe GCC is partly at fault for the > >> Hurd'

Re: 64bit startup

Samuel Thibault, le mer. 25 oct. 2023 14:05:35 +0200, a ecrit: > jbra...@dismail.de, le mer. 25 oct. 2023 11:52:02 +, a ecrit: > > October 25, 2023 3:43 AM, "Samuel Thibault" wrote: > > > jbra...@dismail.de, le mer. 25 oct. 2023 03:40:16 +, a ecrit: > > &

Re: 64bit startup

Sergey Bugaev, le mer. 25 oct. 2023 16:29:29 +0300, a ecrit: > On Wed, Oct 25, 2023 at 2:52 PM wrote: > > > > October 25, 2023 3:43 AM, "Samuel Thibault" wrote: > > > > > jbra...@dismail.de, le mer. 25 oct. 2023 03:40:16 +, a ecrit: > > &g

Re: 64bit startup

Samuel Thibault, le mer. 25 oct. 2023 14:55:36 +0200, a ecrit: > Samuel Thibault, le mer. 25 oct. 2023 14:05:35 +0200, a ecrit: > > jbra...@dismail.de, le mer. 25 oct. 2023 11:52:02 +, a ecrit: > > > October 25, 2023 3:43 AM, "Samuel Thibault" > > > wrot

Re: 64bit startup

Samuel Thibault, le mer. 25 oct. 2023 00:04:33 +0200, a ecrit: > Building packages is not very stable. I have been trying to build > gcc-13 for a couple of weeks, without success so far. There are various > failures, most often odd errors in the libtool script, which are a sign > tha

Re: 64bit startup

Samuel Thibault, le ven. 27 oct. 2023 00:42:06 +0200, a ecrit: > Samuel Thibault, le mer. 25 oct. 2023 14:55:36 +0200, a ecrit: > > Samuel Thibault, le mer. 25 oct. 2023 14:05:35 +0200, a ecrit: > > > jbra...@dismail.de, le mer. 25 oct. 2023 11:52:02 +, a ecrit: > > &

Re: 64bit startup

Samuel Thibault, le ven. 27 oct. 2023 08:48:19 +0200, a ecrit: > while [ "$(echo -n `echo internal/reflectlite.s-gox | sed -e 's/s-gox/gox/' > ` )" = internal/reflectlite.gox ] ; do : ; done For now, I could reproduce with time while [ "$(echo -n `echo a` )&q

Re: 64bit startup

Samuel Thibault, le dim. 29 oct. 2023 23:27:22 +0100, a ecrit: > Samuel Thibault, le ven. 27 oct. 2023 08:48:19 +0200, a ecrit: > > while [ "$(echo -n `echo internal/reflectlite.s-gox | sed -e > > 's/s-gox/gox/' ` )" = internal/reflectlite.gox ] ; do : ; d

Re: 64bit startup

Samuel Thibault, le lun. 30 oct. 2023 18:35:03 +0100, a ecrit: > Samuel Thibault, le dim. 29 oct. 2023 23:27:22 +0100, a ecrit: > > Samuel Thibault, le ven. 27 oct. 2023 08:48:19 +0200, a ecrit: > > > while [ "$(echo -n `echo internal/reflectlite.s-gox | sed

Re: 64bit startup

Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > Samuel Thibault, le lun. 30 oct. 2023 18:35:03 +0100, a ecrit: > > Samuel Thibault, le dim. 29 oct. 2023 23:27:22 +0100, a ecrit: > > > Samuel Thibault, le ven. 27 oct. 2023 08:48:19 +0200, a ecrit: > > >

Re: 64bit startup

Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > Samuel Thibault, le lun. 30 oct. 2023 18:35:03 +0100, a ecrit: > > > Samuel Thibault, le dim. 29 oct. 2023 23:27:22 +0100, a ecrit: > > >

Re: 64bit startup

Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > Samuel Thibault, le lun. 30 oct. 2023 18:35:03 +0100, a ecrit: > > > Samuel Thibault, le dim. 29 oct. 2023 23:27:22 +0100, a ecrit: > > >

Re: 64bit startup

Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > > (it looks like there are memory leaks in proc, its vminfo keeps > > &g

Re: 64bit startup

Samuel Thibault, le mer. 01 nov. 2023 15:35:00 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > > > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > >

Re: proc leaking

Samuel Thibault, le mer. 01 nov. 2023 15:35:00 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > > > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > >

Re: proc leaking

Samuel Thibault, le mer. 01 nov. 2023 16:06:57 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 15:35:00 +0100, a ecrit: > > Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > > > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > > >

Re: proc leaking

Sergey Bugaev, le mer. 01 nov. 2023 23:18:01 +0300, a ecrit: > On Wed, Nov 1, 2023 at 9:17 PM Samuel Thibault > wrote: > > I tracked it a bit, it seems that libport is not always cleaning > > structures from the proc class. Below is the tracing that we get for > > inst

Re: Clang stack alignment on i386-gnu

Sergey Bugaev, le sam. 04 nov. 2023 20:25:13 +0300, a ecrit: > This piece of code in Clang appears to be the culprit, > but note that I'm entirely unfamiliar with the LLVM code base: > > // Stack alignment is 16 bytes on Darwin, Linux, kFreeBSD, NaCl, and for all > // 64-bit targets. On Solar

Re: libssh2 builds on Hurd

Hello, Amos Jeffries, le lun. 06 nov. 2023 23:34:43 +1300, a ecrit: > On hurd-amd64 there is a successful build of the same code with no sign of > MAXPATHLEN being problematic. > > AFAIK there has been no change to make that macro meaningful in Hurd. So > what gives? It was built with nocheck, t

Re: 64bit startup

Hello, Flávio Cruz, le dim. 05 nov. 2023 23:17:49 -0500, a ecrit: > On Tue, Oct 31, 2023 at 9:14 PM Samuel Thibault <[1]samuel.thiba...@gnu.org> > wrote: > > > Realizing only now by reading the __mach_msg_destroy assembly... > > > >     un

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

ing it? Oh, indeed, that's an OS-specific thing that shouldn't be done on cross-execution :) I have commited the attached (untested) patch to the debian hurd repo. Samuel commit 8692df6707fd5d8e2533dd90bc740d422b02584f Author: Samuel Thibault Date: Sat Nov 18 11:30:35 2023 +0100 hurd

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Hello, Johannes Schauer Marin Rodrigues, le dim. 19 nov. 2023 07:45:16 +0100, a ecrit: > So I downloaded > https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/debian-hurd.img.tar.gz > and extracted /boot/gnumach-1.8-486.gz from it. I tried the following but it > seems to get stuck and only p

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Johannes Schauer Marin Rodrigues, le dim. 19 nov. 2023 11:57:07 +0100, a ecrit: > Would you also have handy what argument I'd have to pass to connect the serial > terminal with the login tty to QEMU's serial device so that I can run this > without graphic mode? You can add in -append: console=com0

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Johannes Schauer Marin Rodrigues, le dim. 19 nov. 2023 11:57:07 +0100, a ecrit: > The command above and the advice to extract ext2fs.static and exec.static > should be put on some wiki page, I think. It's the eternal problem with documentation: sometimes it doesn't even exist, sometimes people don

Re: proc leaking

Hello, Samuel Thibault, le mer. 01 nov. 2023 16:06:57 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 15:35:00 +0100, a ecrit: > > Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > > > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: >

Re: Source for grub 2.06-13+hurd.2 ?

Hello, Martin-Éric Racine, le lun. 27 nov. 2023 09:35:19 +0200, a ecrit: > The Hurd kernel in unstable wants a GRUB version higher than > 2.06-13+hurd.2 yet neither unstable or experimental have that. Where > can I find it? It is available in snapshot: http://snapshot.debian.org/package/grub2/ ht

Bug#1057004: gcc-13: hurd-amd64 support

diff --git a/debian/patches/hurd-amd64.diff b/debian/patches/hurd-amd64.diff new file mode 100644 index 000..e7288ea --- /dev/null +++ b/debian/patches/hurd-amd64.diff @@ -0,0 +1,127 @@ +commit 5707e9db9c398d311defc80c5b7822c9a07ead60 +Author: Samuel Thibault +Date: Sat May 6 13:50:36

Re: keyboard configuration fails

Hello, Martin-Éric Racine, le dim. 26 nov. 2023 16:19:58 +0200, a ecrit: > The installer failed to configure the keyboard, which shows with > incorrect symbols when typing in my user name at account creation. Which item did you choose in the boot menu? Which layout did you select? Samuel

Re: keyboard configuration fails

Martin-Éric Racine, le mer. 29 nov. 2023 01:55:23 +0200, a ecrit: > On Tue, Nov 28, 2023 at 11:13 PM Samuel Thibault wrote: > > Martin-Éric Racine, le dim. 26 nov. 2023 16:19:58 +0200, a ecrit: > > > The installer failed to configure the keyboard, which shows with > >

Re: keyboard configuration fails

Martin-Éric Racine, le mer. 29 nov. 2023 11:26:07 +0200, a ecrit: > On Wed, Nov 29, 2023 at 11:22 AM Samuel Thibault wrote: > > > > Martin-Éric Racine, le mer. 29 nov. 2023 01:55:23 +0200, a ecrit: > > > On Tue, Nov 28, 2023 at 11:13 PM Samuel Thibault > > >

Re: keyboard configuration fails

Hello, Martin-Éric Racine, le jeu. 30 nov. 2023 12:23:47 +0200, a ecrit: > Damn lists.debian's Reply-To... Please keep me in CC. Ah, sorry, it's not the list's fault, but I told my mailer to avoid Cc because most people are already subscribed to debian development lists. > but the Hurd console d

Re: poweroff support on Hurd?

Hello, Martin-Éric Racine, le lun. 04 déc. 2023 12:16:59 +0200, a ecrit: > ACPI support. I noticed during bootup that an ACPI server is launched, > but issuing "exec sudo poweroff" merely halts the system; it doesn't > send an ACPI poweroff at the end of the shutdown process. > > Is there any way

Re: poweroff support on Hurd?

Martin-Éric Racine, le lun. 04 déc. 2023 14:08:05 +0200, a ecrit: > > Martin-Éric Racine, le lun. 04 déc. 2023 12:16:59 +0200, a ecrit: > > > ACPI support. I noticed during bootup that an ACPI server is launched, > > > but issuing "exec sudo poweroff" merely halts the system; it doesn't > > > send

Re: poweroff support on Hurd?

Martin-Éric Racine, le lun. 04 déc. 2023 14:30:55 +0200, a ecrit: > As for the console, it doesn't show much since it's too busy clearing > the screen while changing the font You can disable the hurd console in /etc/defaults/hurd-console. > Speaking of the console, logging in via that doesn't set

Re: poweroff support on Hurd?

Martin-Éric Racine, le lun. 04 déc. 2023 14:44:54 +0200, a ecrit: > On Mon, Dec 4, 2023 at 2:40 PM Samuel Thibault wrote: > > Martin-Éric Racine, le lun. 04 déc. 2023 14:30:55 +0200, a ecrit: > > > As for the console, it doesn't show much since it's too busy cle

Re: poweroff support on Hurd?

Martin-Éric Racine, le lun. 04 déc. 2023 14:30:55 +0200, a ecrit: > On Mon, Dec 4, 2023 at 2:14 PM Samuel Thibault wrote: > > > > Martin-Éric Racine, le lun. 04 déc. 2023 14:08:05 +0200, a ecrit: > > > > Martin-Éric Racine, le lun. 04 déc. 2023 12:16:59 +0200, a ecrit

Re: Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

Hello, Thorsten Glaser, le mer. 06 déc. 2023 12:16:27 +0100, a ecrit: > On Wed, 6 Dec 2023, Chris Hofstaedtler wrote: > >I have zero knowledge about hurd, but it looks like[1] hwclock is built > >with CMOS support on hurd. So maybe it could work? > > Maybe it just needs a different config? > >

Re: poweroff support on Hurd?

Martin-Éric Racine, le mar. 05 déc. 2023 10:48:57 +0200, a ecrit: > On Mon, Dec 4, 2023 at 1:48 PM Samuel Thibault wrote: > > Martin-Éric Racine, le lun. 04 déc. 2023 12:16:59 +0200, a ecrit: > > > ACPI support. I noticed during bootup that an ACPI server is launched, > >

Re: poweroff support on Hurd?

Martin-Éric Racine, le jeu. 07 déc. 2023 08:16:34 +0200, a ecrit: > On Thu, Dec 7, 2023 at 2:13 AM Samuel Thibault wrote: > > Martin-Éric Racine, le mar. 05 déc. 2023 10:48:57 +0200, a ecrit: > > > On Mon, Dec 4, 2023 at 1:48 PM Samuel Thibault > > > wrote: > &g

Re: poweroff support on Hurd?

Martin-Éric Racine, le jeu. 07 déc. 2023 11:31:44 +0200, a ecrit: > On Thu, Dec 7, 2023 at 11:26 AM Samuel Thibault wrote: > > > > Martin-Éric Racine, le jeu. 07 déc. 2023 08:16:34 +0200, a ecrit: > > > On Thu, Dec 7, 2023 at 2:13 AM Samuel Thibault > > > wrot

Re: poweroff support on Hurd?

Wojciech (Voitek) Aniszewski, le jeu. 07 déc. 2023 14:23:35 +0100, a ecrit: > wojciech@saiph:~$ showtrans /servers/shutdown > /hurd/shutdown > wojciech@saiph:~$ showtrans /servers/acpi > /hurd/acpi > wojciech@saiph:~$ showtrans ls /servers/acpi/tables > APIC BOOT FACP MCFG SSDT SSDT SSDT TC

Re: Patch series to avoid message resizing for x86_64 (v2)

Hello, Samuel Thibault, le dim. 17 déc. 2023 23:53:56 +0100, a ecrit: > Flavio Cruz, le jeu. 14 déc. 2023 01:02:27 -0500, a ecrit: > > Sending the updated patch series with the warnings fixed. The only > > difference is in the glibc patch (added a cast when calling > > cle

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Hello, Johannes Schauer Marin Rodrigues, le sam. 25 nov. 2023 00:17:35 +0100, a ecrit: > Quoting Matthias Geiger (2023-11-24 23:56:11) > > I see. I was merely wondering if there was an easy way to test hurd builds > > locally without having to run a VM, > > If you want to compile software, then i

Re: 64bit startup

Hello, I'm still stuck without being able to start packages building for hurd-amd64 due to this unreliability. Sergey Bugaev, le mar. 31 oct. 2023 10:09:17 +0300, a ecrit: > On Mon, Oct 30, 2023 at 1:27 AM Samuel Thibault > wrote: > > time while [ "$(echo -n `echo a`

Re: 64bit startup

Sergey Bugaev, le mer. 03 janv. 2024 11:17:53 +0300, a ecrit: > I guess this is where I ask (consistent with the subject line) about > how I would run the x86_64 system (to reproduce & debug this). You probably want to start with the pre-built images I have linked from the wiki page. > I've tried

Re: 64bit startup

Luca, le mer. 03 janv. 2024 20:07:00 +0100, a ecrit: > Il 03/01/24 09:17, Sergey Bugaev ha scritto: > > How are you running it? Should I still be using a ramdisk image and > > not rumpdisk? > > Recently I've been installing hurd-amd64 on another disk of my hurd-i386 vm > and booting from that. Bas

Re: 64bit startup

Sergey Bugaev, le mer. 03 janv. 2024 21:56:54 +0300, a ecrit: > perhaps I need to try two of them in parallel and some I/O-heavy > workload in the background, as you're saying. Yes, that's needed to raise the probability of the bug. > Could it be that the two strings are actually different (somet

Bug#1059986: dpkg: Please add hurd-arm64 case

Package: dpkg Version: 1.22.2 Severity: normal User: debian-hurd@lists.debian.org Usertags: hurd Hello, aarch64-gnu support is coming too :) Could you add a hurd-amd64 case in dpkg? Thanks, Samuel -- Package-specific info: This system uses merged-usr-via-aliased-dirs, going behind dpkg's back,

Re: Bug#1059986: dpkg: Please add hurd-arm64 case

Hello, Guillem Jover, le jeu. 04 janv. 2024 20:23:02 +0100, a ecrit: > but even though I've seen already some toolchain patches flying by, > AFAIUI there's still no GNU Mach support, so I think I'd prefer to > wait until that materializes, Ok. > as per the FAQ entry on new ports. I don't think t

Re: 64bit startup

Hello, Sergey Bugaev, le jeu. 04 janv. 2024 22:21:11 +0300, a ecrit: > On Thu, Jan 4, 2024 at 10:57 AM Samuel Thibault > wrote: > > Sergey Bugaev, le mer. 03 janv. 2024 21:56:54 +0300, a ecrit: > > > perhaps I need to try two of them in parallel and some I/O-heavy

Re: 64bit startup

Sergey Bugaev, le ven. 05 janv. 2024 12:06:13 +0300, a ecrit: > > I use > > > > while true ; do apt install --reinstall wdiff ; done > > That did it! I can now reliably reproduce this. > > (I assume you don't mind my box constantly banging on your repo.) It's people.debian.org, it's meant for th

Re: 64bit startup

Samuel Thibault, le jeu. 04 janv. 2024 08:57:51 +0100, a ecrit: > Sergey Bugaev, le mer. 03 janv. 2024 21:56:54 +0300, a ecrit: > > perhaps I need to try two of them in parallel and some I/O-heavy > > workload in the background, as you're saying. > > Yes, that's nee

Re: 64bit startup

Sergey Bugaev, le ven. 05 janv. 2024 21:12:48 +0300, a ecrit: > I'm not seeing hurd-dbg / hurd-libs-dbg packages in your repo. Yes, my repo is built from the rebootstrap scripts, which drop debug etc. only for creating a booting system. For proper packages, use the usual deb.debian.org debian-por

Re: 64bit startup

Sergey Bugaev, le ven. 05 janv. 2024 21:12:48 +0300, a ecrit: > Also I can't help but notice that the hurd package (i.e the translator > binaries) is still not being built as PIE, This is not actually specific to 64bit. This was set explicitly in 2016 in debian/rules, tests welcome to check whethe

Re: 64bit startup

Luca, le sam. 06 janv. 2024 00:42:35 +0100, a ecrit: > Il 05/01/24 19:12, Sergey Bugaev ha scritto: > > /servers/crash-dump-core crashes on the memset () call in > > hurd:exec/elfcore.c:fetch_thread_fpregset (); the (*fpregs) pointer is > > NULL. The caller passes fpregs = ¬e.data.pr_fpreg, where n

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Hello, Johannes Schauer Marin Rodrigues, le jeu. 11 janv. 2024 00:12:09 +0100, a ecrit: > The util-linux problem is no surprise because less fails to install when > investigating that issue I noticed the version of less is 487 which is the > version from old-old-stable. Is that plausible? It has

Re: dhcpcd: FTBFS on Hurd

Joshua Branson, le mer. 17 janv. 2024 12:09:30 -0500, a ecrit: > Also may I ask why Debian is switching to dhcpcd? Just curious. Because ISC is not maintaining its dhcp software any more. Samuel

Re: Give-back request davix 0.8.5-1+b1 gnu-hurd

Hello, Mattias Ellert, le lun. 29 janv. 2024 08:53:44 +0100, a ecrit: > The build of davix 0.8.5-1+b1 failed on hurd-i386 due to bug 1061610, > which is a bug in debhelper 13.12. Could you retry the build with > debhelper 13.13? > > https://buildd.debian.org/status/package.php?p=davix > > https:

Re: hurd-amd64 is missing from wanna-build graphs

Hello, marius, le mer. 31 janv. 2024 19:05:07 +, a ecrit: > I noticed that hurd-amd64 is mssing from wanna-build graphs, is this > something that we want? If so i can propose a patch to the wb team Since the hurd-amd64 buildd is not unleashed yet, it won't be useful anyway :) better wait for

Re: hurd-amd64 is missing from wanna-build graphs

Amos Jeffries, le jeu. 01 févr. 2024 20:46:27 +1300, a ecrit: > On 1/02/24 11:07, Samuel Thibault wrote: > > marius, le mer. 31 janv. 2024 19:05:07 +, a ecrit: > > > I noticed that hurd-amd64 is mssing from wanna-build graphs, is this > > > something that we want?

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Hello, Johannes Schauer Marin Rodrigues, le mer. 07 févr. 2024 18:07:21 +0100, a ecrit: > if [ "$(uname -s)" = "Linux" ]; then > update-alternatives --install /usr/bin/pager pager /bin/more 50 \ > --slave /usr/share/man/man1/pager.1.gz pager.1.gz \ > /usr/share/ma

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Johannes Schauer Marin Rodrigues, le jeu. 08 févr. 2024 00:04:25 +0100, a ecrit: > Quoting Samuel Thibault (2024-02-07 23:32:34) > > > So I manually created the empty files /servers/exec, /servers/startup and > > > /dev/console as it is done by debootstrap her

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Johannes Schauer Marin Rodrigues, le jeu. 08 févr. 2024 10:04:51 +0100, a ecrit: > On 2024-02-08 00:13, Samuel Thibault wrote: > > Johannes Schauer Marin Rodrigues, le jeu. 08 févr. 2024 00:04:25 +0100, > > a ecrit: > > > I'm probably missing more customizations to mak

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Johannes Schauer Marin Rodrigues, le jeu. 08 févr. 2024 08:12:51 +0100, a ecrit: > So this is missing entries for /etc/hurd/runsystem.sysv. The hurd.postinst > only > sets up the entry for runsystem.gnu at priority 5. So I looked at the > initscripts.postinst from sysvinit and that one also calls

Bug#1063642: gcc-13: Fix disabling go and m2 according to OS

Package: gcc-13 Version: 13.2.0-13 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hello, There was a typo in rules.defs concerning go_no_systems and m2_no_systems: they are still compared against DEB_TARGET_ARCH_OS, while their content is gnu-system-like (kfreeb

Bug#1063643: gcc-14: Fix disabling go and m2 according to OS

Source: gcc-14 Version: 14-20240201-3 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hello, There was a typo in rules.defs concerning go_no_systems and m2_no_systems: they are still compared against DEB_TARGET_ARCH_OS, while their content is gnu-system-like (kfr

time_t-related transition coming

Hello, Just to warn: the upload of the t64 packages is about to come into Debian, that'll be a very big transition, so in the meanwhile the sid distribution will be essentially uninstallable and non-upgradable. Please bear with us while the world gets rebuilt ;) Samuel

Bug#1065456: python3.11: Please don't enable dtrace on hurd

Package: python3.11 Version: 3.11.8-1 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hello, python3.11 currently fails to build on hurd-any because debian/rules enables dtrace, which is not available on hurd-any. Could you apply the attached patch that fixes th

Bug#1066932: gcc-14: Please enable m2 on hurd-any

Source: gcc-14 Version: 14-20240303-1 Severity: normal Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hello, Now that upstream has fixed the m2 portability (available in the 20240303 snapshot), could you enable m2 on hurd-any, as the attached patch does? Thanks, Samuel -- System

Re: How connect Translator /hurd/ftpfs with a non anonimous ftp account with user and passwd

Hello, Jose Luis Alarcon Sanchez, le dim. 17 mars 2024 18:34:29 +0100, a ecrit: > The 'test' work exactly as the text say, and i did ls on the GNU FTP, but i > want to introduce here my > question: Can this be done also with a ftp server that requires an user name > and password?. I have my accou

Re: How connect Translator /hurd/ftpfs with a non anonimous ftp account with user and passwd

Alexandre Garreau-Capitanio, le dim. 17 mars 2024 19:29:56 +0100, a ecrit: > On 17/03/2024 18:48, Samuel Thibault wrote: > > SERVER can be a hostname, in which case anonymous ftp is used, or may > > include a user and password like `USER:PASSWORD@HOST' (the `:PASSWORD&#

Re: How connect Translator /hurd/ftpfs with a non anonimous ftp account with user and passwd

Jose Luis Alarcon Sanchez, le dim. 17 mars 2024 20:13:13 +0100, a ecrit: > On Sun, Mar 17, 2024 at 06:48:17PM +0100, Samuel Thibault wrote: > > Hello, > > > > Jose Luis Alarcon Sanchez, le dim. 17 mars 2024 18:34:29 +0100, a ecrit: > > > The 'test' work exac

Re: Hard Disk size limits on GNU Hurd

Hello, Jose Luis Alarcon Sanchez, le ven. 22 mars 2024 12:31:04 +0100, a ecrit: > Several years ago there was a limit in the size of the hard disks that Hurd > could manage. If i'm not wrong, i think it was 5 Gb. or so. > > Is still this limit working right now?, or can i create a disk image (for

Re: Hard Disk size limits on GNU Hurd

Hello, Tanguy LE CARROUR, le ven. 22 mars 2024 13:33:59 +0100, a ecrit: > Quoting Samuel Thibault (2024-03-22 12:37:33) > > Jose Luis Alarcon Sanchez, le ven. 22 mars 2024 12:31:04 +0100, a ecrit: > > > Several years ago there was a limit in the size of the hard disks that >

Re: ntpdate : Depends: ntpsec-ntpdate but it is not installable

Hello, Jose Luis Alarcon Sanchez, le dim. 24 mars 2024 13:31:22 +0100, a ecrit: > What's the situation with the package ntpsec-ntpdate?. Is there a fix > possible?. I volunteer, if i am able. Waiting for instructions to follow. Fixing the build to at least support the step adjustment should be re

smp and pae kernels

Hello In the latest gnumach upload, I have added smp and pae variants of the kernel. pae should be relatively fine and allow to access more than 3G memory. smp is completely experimental, and needs fixing here and there, it seems like irq routing, notably, needs fixes, but at least people can easi

Re: creating Hurd chroots on Linux using DPKG_ROOT chrootless mode

Hello, Johannes Schauer Marin Rodrigues, le mer. 10 avril 2024 10:09:02 +0200, a ecrit: > So I tried the whole thing again and we got a new blocker: > > https://buildd.debian.org/status/package.php?p=fakeroot I'm not sure why it's a blocker? Is the previous fakeroot version not enough? > Do you

Re: smp i386 kernels

Maite Gamper, le dim. 19 mai 2024 16:41:41 +0200, a ecrit: > But I've noticed that "gnumach-image-1.8-486-smp" > seems to contain a uniprocessor kernel in sid,  the > files seem to be identical. Oops, there must have been some mistake in the build scripts, I'll have a look. > I've heard that mach

<    1   2   3   4   5   6   7   8   9   10   >