IRC channel logs

<Guest96>is the Wikipedia article on the Hurd accurate?

<sneek>Guest96, you have 2 messages!

<sneek>Guest96, nckx says: [to the Guest dealing with bcachefs] No, it is not expected that it's mounted read-only or root-only, and there's nothing in Guix that would do that (bug or not AFAIK). This isn't FUSE with its weird semantics. In your case I would first triple-check that my permissions are correct—it's perfectly possible to chmod a file system to allow writes by root only, no bugs required.

<sneek>Guest96, nckx says: [to the Guest dealing with bcachefs] Also, probably best to move this to help-guix@.

<Guest96>I noticed for the Gentoo GNU Hurd on QEMU root was originally mounted as read only, is that a bug or a security feature?

<azeem>Guest96: which part of the Wikipedia article do you think is inacurrate?

<Guest96>None of it, I was just wondering before I consider reading it

<azeem>last time I read it it was pretty accurate, if a bit outdated

<azeem>but also not extremely enlightning I'd say

<Guest96>alright, thanks

<sam_>Guest96: I don't think it's supposed to be, we have it setup to remount it

<sam_>if that didn't happen, something went wrong, would need to see more to debug it

<Guest96>yeah it didn't remount, when I ran dispatch-conf it tried to write over some read only files and I think that fucked up the system

<Guest96>the translators started failing after that and then the whole thing broke

<Guest96>I wouldnt know how it broke at a low level, but I do think it had something to do with disk-space permissions

<Guest96>or file permissions I guess is a better term

<sam_>I can't really say more without seeing some output but I suspect you booted it and then shut it down uncleanly and then the fs got corrupted

<Guest96>I put my trust into reboot and power off to shut it down just fine, would I have to do any more than that?

<Guest96>also the emerge --sync process took like 8 times longer than it usually does on a normal install

<Guest96>I think that was because of the emulation but idk, it was painfully slow

<Guest96>I'm assuming that is normal due to its experimental nature but I thought I'd still mention it

<sam_>I think reboot/poweroff would be okay, so indeed not that

<Guest96>it started breaking right after I ran dispatch-conf

<sam_>interesting

<sam_>i'll try to reproduce it but i may need a bit more

<Guest96>I decided to update some configuration files, I can't remember them exactly but I remember one of them having boot in the name

<sam_>it would be most helpful if you could recreate it with a new image and write down what you did if you can reproduce it, as the specifics will matter, but i will try as well

<Guest96>I cant as of right now but I could try to recall all I did, I was on a debian system with KDE and I downloaded and installed QEMU and the Gentoo hurd AMD64 QEMU image

<Guest96>after that I ran QEMU with the image,I don't remember the exact hardware allocation settings but they were pretty modest, I didnt do anything crazy

<Guest96>after it booted I used the shell script provided to get internet connectivity

<sam_>you ran emerge --sync, do you remember what you did before dispatch-conf? i expect emerging some things which led to d-c having changes to make

<Guest96>i remember seeing a notification that portage needed updating so after syncing the system I reemerged it

<Guest96>I didn't mess with the permissions or any low level file relating functions at all before it broke

<Guest96>the internet connection took a bit to start as well I remember but ultimately worked

<sam_>thanks, will try repro

<Guest96>alright

IRC channel logs

2026-05-07.log