jail devfs openpty
Peter Vereshagin
peter at vereshagin.org
Mon Jan 26 03:33:25 PST 2009
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 lpt0 mixer0 random ttyp1 ttyp3 ttyp5 zero
log lpt0.ctl null ttyp0 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.questions at rachie.is-a-geek.net> => To freebsd-questions at 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
More information about the freebsd-questions
mailing list