Re: jail devfs openpty
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. And, I'm still in question how should I delete the ruleset once added for devfs. Thanks all. 2009/01/25 17:08:14 -0900 Mel fbsd.questi...@rachie.is-a-geek.net = To freebsd-questions@freebsd.org : 73! Peter -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail devfs openpty
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 ttyp5 zero log lpt0.ctlnullttyp0 ttyp2 ttyp4 urandom # script script: openpty: Resource temporarily unavailable # exit exit # devfs -m /jailpath/dev rule apply path pty* unhide # chroot /jailpath/ # script script: openpty: Permission denied # exit exit # devfs -m /jailpath/dev rule apply path * unhide devfs rule: unknown argument: Desktop # devfs -m /jailpath/dev rule apply type tty unhide # chroot /jailpath/ # script Script started, output file is typescript # exit Script done, output file is typescript # exit exit # === Now this seem to work, after the reboot. Although I'd like to ask if I used the major/minor numbers for temporary rules when portupgraded the 5/6 systems, what kind of rule I should specify to avoid 'openpty' reason of script(1) failure? Which tty devices does it use? You may see I try the path pty* and path ttyp* without that luck though. Major/minor numbers are gone since some of 6.X. 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 am doing the portupgrade inside my jail. M I see that script(1) have no permission on openpty. M I deleted all the devfs rules on tha jail's /dev both by hand and by M deleting the ruleset string in master's rc.conf. So i stopped jail and M mounted devfs by hand. Started jail. It appears to work, the portupgrade. I M suppose that if mounted with /etc/rc.d/jail the devfs has some tweak that M makes it different from mounted by hand. M M Are you sure that's the problem? M When going inside a jail with jexec(8) there is no /dev/tty. You have to login M using ssh to get fully functional tty's. M M -- M Mel M M Problem with today's modular software: they start with the modules M and never get to the software part. 73! Peter -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail devfs openpty
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) . done] ** Port marked as IGNORE: mail/cclient: is forbidden: multiple vulnerabilities http://www.vuxml.org/freebsd/a6713190-dfea-11dd-a765-0030843d3802.html http://www.vuxml.org/freebsd/69a20ce4-dfee-11dd-a765-0030843d3802.html --- Upgrade of mail/courier-imap started at: Mon, 26 Jan 2009 15:59:40 +0400 --- Upgrading 'courier-imap-4.3.1,2' to 'courier-imap-4.4.1,2' (mail/courier-imap) --- Build of mail/courier-imap started at: Mon, 26 Jan 2009 15:59:40 +0400 --- Building '/usr/ports/mail/courier-imap' script: openpty: Permission denied === Same as with script(1) by hand now. I do all this in chroot. No difference if under gnu screen or in ttyv4. 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 am doing the portupgrade inside my jail. M I see that script(1) have no permission on openpty. M I deleted all the devfs rules on tha jail's /dev both by hand and by M deleting the ruleset string in master's rc.conf. So i stopped jail and M mounted devfs by hand. Started jail. It appears to work, the portupgrade. I M suppose that if mounted with /etc/rc.d/jail the devfs has some tweak that M makes it different from mounted by hand. M M Are you sure that's the problem? M When going inside a jail with jexec(8) there is no /dev/tty. You have to login M using ssh to get fully functional tty's. M M -- M Mel M M Problem with today's modular software: they start with the modules M and never get to the software part. 73! Peter -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail devfs openpty
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 am doing the portupgrade inside my jail. M I see that script(1) have no permission on openpty. M I deleted all the devfs rules on tha jail's /dev both by hand and by M deleting the ruleset string in master's rc.conf. So i stopped jail and M mounted devfs by hand. Started jail. It appears to work, the portupgrade. I M suppose that if mounted with /etc/rc.d/jail the devfs has some tweak that M makes it different from mounted by hand. M M Are you sure that's the problem? M When going inside a jail with jexec(8) there is no /dev/tty. You have to login M using ssh to get fully functional tty's. M M -- M Mel M M Problem with today's modular software: they start with the modules M and never get to the software part. 73! Peter -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: jail devfs openpty
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 jail and mounted devfs by hand. Started jail. It appears to work, the portupgrade. I suppose that if mounted with /etc/rc.d/jail the devfs has some tweak that makes it different from mounted by hand. Are you sure that's the problem? When going inside a jail with jexec(8) there is no /dev/tty. You have to login using ssh to get fully functional tty's. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
