devfs rules own

sossego

sossego

Retired from the forums
Devfs rules own: unknown is the last line that comes up during the boot process.
I commented out tty8 on /etc/ttys and added aio_load, if_tap and if_tun were enabled, kqemu was uncommented in /etc/rc.conf.
I need a few documents from the slice such as the vbox build patch and rules, the Xorg.conf, and a few shell scripts.

Any reference or link to correct this is appreciated.
Thanks beforehand for any help.
 
How do I remove or add a comment when neither vi nor a tty can be accessed?
 
Is it necessary to echo the entire entry into devfs.rules or just the line that needs to be replaced?
 
Livefs doesn't work. No tty available. System mounts only as ro.
Okay, what am I doing wrong here?
 
Yes.
It always stops with "devfs rules: unknown command: own"
I even tried safe mode but am having trouble mounting the volume to write to it.
 
Solved.
Mounting the device in the following modes didn't work
"mount -u -f -w /dev/path"
Seems that you can't mount /rescue and /etc at the same time.
You get the 'vi: No terminal database found"

I had to mount in the following manner:
"mount /"
" mount /usr"
"mount /var"
Found the solution on the mailing list.
Thanks, everyone, for the help.
 
Standard command sequence in single user:
Code: 
fsck -p
mount -u -o rw /
# if needing vi
mount /usr
mount /var
fsck -p will throw errors if filesystem can't be marked clean at which point you'll have to use fsck -y.
 
true, but there's been some flipping back and forth about whether to use flags or -o keyword in mount, through all that I kept on using -o rw knowing it would hit quite some anger if support for it were removed :p

The consensus now seems to be again to use -o keyword rather then single letter flags, looking at -current's manpage for mount_nfs.

Either way, -o rw or -w makes indeed no difference.
 
You must log in or register to reply here.
Back
Top