It appeared to work after rule apply unhide. Will find out more. Just how to
delete or view the ruleset? Thanks.
Seem to get on it. Looks like it's not very obvious. The cure was:
===
devfs -m /jailpath/dev rule -s 5 add type tty unhide
===
the unobvious for me was to put -s in the right place.
You'll never silence the voice of the voiceless, Mel!
Probably that was caused by overall instability of my 7.1 system:
===
# devfs -m /jailpath/dev rule apply path ttyp* unhide
# chroot /jailpath/
# ls /dev
dsp0.1 lpt0mixer0 random ttyp1
ttyp3
You'll never silence the voice of the voiceless, Mel!
Sorry the script(1) did work, but stopped since the portupgrade tried it:
===
# portupgrade -varRp
--- Session started at: Mon, 26 Jan 2009 15:58:54 +0400
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 190 packages found
(-0 +1)
It appeared to work after rule apply unhide. Will find out more. Just how to
delete or view the ruleset? Thanks.
2009/01/25 17:08:14 -0900 Mel fbsd.questi...@rachie.is-a-geek.net = To
freebsd-questions@freebsd.org :
M On Sunday 25 January 2009 02:25:17 Peter Vereshagin wrote:
M Hello,
M
M I
Hello,
I am doing the portupgrade inside my jail.
I see that script(1) have no permission on openpty.
I deleted all the devfs rules on tha jail's /dev both by hand and by deleting
the ruleset string in master's rc.conf.
So i stopped jail and mounted devfs by hand. Started jail. It appears to
On Sunday 25 January 2009 02:25:17 Peter Vereshagin wrote:
Hello,
I am doing the portupgrade inside my jail.
I see that script(1) have no permission on openpty.
I deleted all the devfs rules on tha jail's /dev both by hand and by
deleting the ruleset string in master's rc.conf. So i stopped
