ports/166666: qjail update -b remove uglyporthack
Herbert Vojčík
herby at mailbox.sk
Thu Apr 5 11:10:02 UTC 2012
>Number: 166666
>Category: ports
>Synopsis: qjail update -b remove uglyporthack
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 05 11:10:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Herbert Vojčík
>Release: 9.0-RELEASE
>Organization:
>Environment:
FreeBSD devel 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
perl is not able to start (for example, build of ffmpeg fails) in jail managed by qjail after when 'qjail update -b' was executed.
>How-To-Repeat:
In host, install qjail.
In host, create a jail under qjail
In a jail, install perl.
In a jail, perl works (though it was not able to install /usr/bin/perl link; but qjail employs "uglyperlhack" technique by supplying /usr/bin/perl -> /usr/local/bin/perl symlink in advance).
In host, run 'qjail -b update' as root (this recopies basejail /usr/bin/ from the host)
In a jail, everything works but perl (which lost /usr/bin/perl symlink due to update).
>Fix:
Update qjail script so that it reinstates perluglyhack at the end of 'qjail update -b'.
(in general, need for uglyperlhack could be mitigated by using unionfs instead of nullfs to mount /usr/jails/jailname/basejail into /usr/jails/basejail. This would fix _any_ changes outside /usr/local in a way that it saves them per jail and reuses them in subsequent starts; it saves them into jail's basejail directory using unionfs)
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list