Hello,

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3 would make some -dev packages
removed. The rebuilds for these packages are ongoing, you just need to
wait for a few days, all you'll be able to upgrade libc0.3-dev to 2.34-3 without having to remove some -dev packages.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3 would make some -dev packages
removed. The rebuilds for these packages are ongoing, you just need to
wait for a few days, all you'll be able to upgrade libc0.3-dev to 2.34-3 without having to remove some -dev packages.

Hello,

I've upgraded on darnassus.sceen.net and the system cannot boot properly
any more. I'm unable to diagnose at this time.

--
Richard Braun

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly
any more.

Oh? I'm not getting the issue on my box.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly any more.

Oh? I'm not getting the issue on my box.

But it happens on exodar too indeed. The boot CD there allows to chroot
into the system. I tried dpkg-reconfigure hurd, that didn't help.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Samuel Thibault, le mar. 09 août 2022 23:43:46 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 16:37:24 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly
any more.

Oh? I'm not getting the issue on my box.

But it happens on exodar too indeed. The boot CD there allows to chroot into the system. I tried dpkg-reconfigure hurd, that didn't help.

I managed to make exodar boot again by copying by hand from glibc 2.33 ld.so.1 libc.so.0.3 (and libdl.so.0.3 libutil.so.0.3 libpthread.so.0.3 libnss* but that was for later startup issues).

On darnassus I could look at show all tasks, there are

- gnumach
- pci-arbiter
- rumpdisk
- ext2fs
- exec
- startup
- proc
- auth
- console-run
- /bin/sh

so everything seems to be going fine, except that runsystem.gnu doesn't actually start, on exodar I wasn't even getting the echos that I had
added to the script.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Samuel Thibault, le mar. 09 août 2022 16:37:24 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly any more.

Oh? I'm not getting the issue on my box.

But it happens on exodar too indeed. The boot CD there allows to chroot
into the system. I tried dpkg-reconfigure hurd, that didn't help.

I managed to make exodar boot again by copying by hand from glibc 2.33
ld.so.1 libc.so.0.3 (and libdl.so.0.3 libutil.so.0.3 libpthread.so.0.3
libnss* but that was for later startup issues).

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Samuel Thibault, le mar. 09 août 2022 16:37:24 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is
that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly any more.

Oh? I'm not getting the issue on my box.

But it happens on exodar too indeed. The boot CD there allows to chroot
into the system. I tried dpkg-reconfigure hurd, that didn't help.

Ok, now I see the issue, it's indeed on basically all boxes except mine
because I tinkered with /dev/random.

There is a funky initialization loop with glibc 2.34:

- glibc initialization calls getrandom()
- getrandom() checks whether the process has a __trivfs_server_name
variable, to check whether it points to "random", in that case it just
returns early
- getrandom() opens /dev/urandom or /dev/random
- the /dev/{u,}random translator auto-starts

I had introduced the second step to avoid that very loop. But currently
the hurd boxes are configured to use a random-hurd.sh shell scripts that
starts the /hurd/random translator with proper parameters. That was
meant to make the hurd translator configurable, but it is here bringing
more harm than good.

Also, glibc tries to open files in /proc, and thus /hurd/random startup
would trigger starting procfs, and its glibc initialization would try to
open /dev/urandom, and we get the loop.

I'm thus having a look at removing that random alternative and the
auto-started /proc, to simplify the system startup.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

Samuel Thibault, le jeu. 18 août 2022 22:11:03 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 16:37:24 +0200, a ecrit:

Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:

Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:

On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:

There's a glibc transition which is ongoing, whose consequence is that upgrading libc0.3-dev to 2.34-3

I've upgraded on darnassus.sceen.net and the system cannot boot properly
any more.

Oh? I'm not getting the issue on my box.

But it happens on exodar too indeed. The boot CD there allows to chroot into the system. I tried dpkg-reconfigure hurd, that didn't help.

Ok, now I see the issue, it's indeed on basically all boxes except mine because I tinkered with /dev/random.

I have uploaded hurd version 1:0.9.git20220301-2 which sort things out.

If you have a system which is hosed, you can easily make it boot again
with

rm /dev/random /dev/urandom

and then it should boot fine, and you can upgrade hurd to version 1:0.9.git20220301-2 and let it recreate them.

I will uploaded another glibc 2.34 which adds a Breaks so that upgrading
to it will also upgrade the hurd package alongside.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)