Samuel Thibault <samuel.thiba...@gnu.org> writes: > Joshua Branson, le ven. 25 oct. 2024 22:28:30 -0400, a ecrit: >> - Starting X issue: This one took me a while to figure out. The Hurd >> automatically runs fsck on your filesystems at boot, and it fixes >> all issues without user intervention! BUT sometimes it is unable to >> automatically rid the filesystem of corruption, and the Hurd will >> mount your filesystem/s readonly. > > That's a concern, not just for X. Normally (and in the past I believe it > was behaving that way), you'd either get / mounted read-write even if > with error, or get an emergency shell, which thus allows you to fsck by > hand. That should just be fixed in initscripts.
I have seen that emergency shell in real hardware! And it does work! I'll try to take a look at the debian initscripts. That's sysvinit stuff right? and it would be easy to test. Suppose you have one partition "/". You could set the passive translator setting to readonly, etc. # fsysopts / --readonly # reboot What should the initscript do in this situation? Change the login message from "This is the Hurd" message to "/ is mounted readonly. Please insert a Debian installer CD and to manually fsck '/'." Something like that? Joshua -- Joshua Branson Sent from the Hurd
