FreeBSD 13 fossil server warnings regarding /dev/null and /dev/urandom
(1) By JesseMeyer on 2022-01-13 21:14:39 [source]
Upon visiting my Fossil's Server Administration page, the following warnings are displayed at the top.
WARNING: Device "/dev/null" is not available for reading and writing.
WARNING: Device "/dev/urandom" is not available for reading. This means that the pseudo-random number generator used by SQLite will be poorly seeded.
How do I correct these? I suspect this may have to do with jail access differences between Linux and FreeBSD 13.
(2) By Kirill M (Kirill) on 2022-01-13 21:32:16 in reply to 1 [link] [source]
So you are running Fossil chrooted, and there's no /dev in the chroot directory. (jail is chroot on steroids...)
IIRC FreeBSD has devfs, make sure it's mounted as /dev under Fossil's chroot. Also, if my memory serves me right, there are some rc.conf parameters to control that -- devfs rules or something.
(3) By Warren Young (wyoung) on 2022-01-13 22:14:35 in reply to 1 [link] [source]
(4) By Kirill M (Kirill) on 2022-01-13 23:13:35 in reply to 3 [link] [source]
On FreeBSD there's mounting of devfs and then hiding most of the devices using some devfs rules.
Here're clues from my 2017 backup from one of my FreeBSD systems:
$ grep devfs fstab
null /var/spool/postfix/dev devfs rw 0 0
null /local/ksync/dev devfs rw 0 0
$ cat devfs.rules
#
# devfs.rules
#
[chroot=10]
add include $devfsrules_hide_all
add include $devfsrules_unhide_basic
$ grep devfs rc.conf
devfs_set_rulesets="/var/spool/postfix/dev=chroot /local/ksync/dev=chroot"