- Thread Starter
- #26
I accidentally broke my installation of BSD yesterday, but I will consider commenting it out, now that I know a little bit more about it.
I accidentally broke my installation of BSD yesterday, but I will consider commenting it out, now that I know a little bit more about it.
Try to add back:
So, it seems as though enabling fsck in rc.conf isn't really that useful, and it would be better to manually run it when the system prompts me to do so. I admit, I have a lot to learn, and I should probably start looking at the Handbook some more.
link cd0 cdrom
link cd0 dvd
perm acd* 0660
perm cd* 0660
perm da* 0660
perm pass* 0660
perm xpt* 0660
perm uscanner* 0660
perm video* 0660
perm tuner* 0660
perm devstat 0444
own /dev/cd0 x:operator
perm /dev/cd0 0660
own vboxnetctl root:vboxusers
perm vboxnetctl 0660So just to be clear, I will add the below line back into my rc.conf file, and then the above rules that you sent me will go into /etc/devfs.rules
devfs_system_ruleset="system"[devfsrules_system=10]
... your config
Aghh....I wish that I would have known about Ventoy earlier. Last year I installed FreeBSD on a spare drive I had lying around, but I screwed things up when I tried to use the same version of Grub which boots my Kubuntu installation. I think that the Freebsd appeared on the menu below Windows and Linux, but when I tried to boot it, nothing. Later I reconfigured the sata cables to make my BSD harddrive the primary harddrive in the boot order, but still nothing. I don't know what happened, but it appears that the version of Grub I had on my system to boot Linux must have somehow wiped out the boot files for FreeBSD, and after that, I just put last years project on hold for a while.
Just to make certain that I understand things, if my /etc/rc.conf file contains the below line
devfsrules_system=10Try to think like a computer
No it does not.
#!/bin/sh
#
#
# PROVIDE: fsck
# REQUIRE: swap
# KEYWORD: nojail
. /etc/rc.subr
name="fsck"
desc="Run file system checks"
start_cmd="fsck_start"
stop_cmd=":"
fsck_start()
{
if [ "$autoboot" = no ]; then
echo "Fast boot: skipping disk checks."
elif [ ! -r /etc/fstab ]; then
echo "Warning! No /etc/fstab: skipping disk checks."
elif [ "$autoboot" = yes ]; then
# During fsck ignore SIGQUIT
trap : 3
startmsg "Starting file system checks:"
# Background fsck can only be run with -p
if checkyesno background_fsck; then
fsck -F -p
else
fsck ${fsck_flags}
fi
err=$?
if [ ${err} -eq 3 ]; then
echo "Warning! Some of the devices might not be" \
"available; retrying"
root_hold_wait
startmsg "Restarting file system checks:"
# Background fsck can only be run with -p
if checkyesno background_fsck; then
fsck -F -p
else
fsck ${fsck_flags}
fi
err=$?
fi
case ${err} in
0)
;;
2)
stop_boot
;;
4)
echo "Rebooting..."
reboot
echo "Reboot failed; help!"
stop_boot
;;
8|16)
if checkyesno fsck_y_enable; then
echo "File system preen failed, trying fsck -y ${fsck_y_flags}"
fsck -y ${fsck_y_flags}
case $? in
0)
;;
*)
echo "Automatic file system check failed; help!"
stop_boot
;;
esac
else
echo "Automatic file system check failed; help!"
stop_boot
fi
;;
12)
echo "Boot interrupted."
stop_boot
;;
130)
stop_boot
;;
*)
echo "Unknown error ${err}; help!"
stop_boot
;;
esac
fi
}
load_rc_config $name
# doesn't make sense to run in a svcj
fsck_svcj="NO"
run_rc_command "$1"If you are booting off UFS, then fsck will run. I didn't say it will do a full scan of anything, but even if it doesn't, it still has to run to check that the appropriate file systems are clean.