Kirill A. Korinsky <kir...@korins.ky> writes: > On Tue, 10 Dec 2024 20:10:51 +0100, > Divan Santana <di...@santanas.co.za> wrote: >> >> Secondly question, is it possible from the rescue environment to edit >> the real /etc/fstab file? Because it would be handy for me in some >> cases to do so without booting from the install image. >> > > I just double checked bsd.rd from amd64 snapshot, and it seems that both, > bsd.rd from installer and "single mode" has ed which is text editor.
I did see ed was there. But I wasn't sure how to mount the system as rw. Because it's mounted at / as ro. I guess I could try mount it additionally at /mnt as rw, not sure if that'd work. >> Another question, is there a Linux like fstab option of 'nofail' for >> OpenBSD? It seems like there isn't, because for me, it would be handy >> to specify that for my /data mount. >> > > Let me quote man fsck(8): > > It is normally used in the script rc(8) during automatic reboot. If no > file systems are specified, fsck reads the file fstab(5) to determine > which file systems to check and in what order. Only partitions in fstab > that are mounted “rw” or “ro” and that have non-zero pass numbers are > checked. File systems with pass number 1 (normally just the root file > system) are checked one at a time. OK, good point. But if there is a file system listed in fstab with pass option of 0, it will skip a fsck on boot but it will still attempt to mount the file system I think. Therefore it's not quite the same as the Linux mount option of nofail, which allows the system to boot normally even if the file system is able to mounted on boot.
