some of the system ebuilds for freebsd fail in a freebsd jail because you can't use chflags. Reproducible: Always Steps to Reproduce: the following wrapper solved my problem but a more permanent solution, like jail detection, is needed. (forgive my poor regex. i'm sure the job could be done with one search and replace rather than two.) first rename /usr/bin/install to /usr/bin/install.real and enter the following as /usr/bin/install and chmod +x #!/bin/bash newargs=`echo $@ | sed -e "s/ \-f [^ ]* / /" -e "s/ \-f[^ ]* / /"` /usr/bin/install.real $newargs
Not respecting flags is not really an option.
this needs to be fixed. chflags is not required. if you want to have gentoo/freebsd matter AT ALL you need to make it's features work. I'm willing to continue to report bugs on gentoo/freebsd only if they are taken seriously. BOTTOM LINE: if it doesn't work in a jail, it isn't freebsd. Fix it or rename your project.
(In reply to comment #0) > some of the system ebuilds for freebsd fail in a freebsd jail because you can't > use chflags. Why? What's the error?
not all jail providers allow chflags in their jails. The default setting for chflags in jails is OFF. as in DISALLOW.
sysctl security.jail.chflags_allowed will return if chflags is allowed to be used. if not allowed: security.jail.chflags_allowed: 0 if allowed: security.jail.chflags_allowed: 1 mind you even if it is allowed in a jail, it doesn't do anything... it just makes the function always return 0.
(In reply to comment #4) > not all jail providers allow chflags in their jails. That's kinda your problem.
um... no... it's standard procedure in the freebsd world... freebsd itself works when chflags is off, gentoo/freebsd should too... or it can't really call itself freebsd at all...
(In reply to comment #5) > mind you even if it is allowed in a jail, it doesn't do anything... it just > makes the function always return 0. Isn't that in effect what your above wrapper does? (In reply to comment #7) > um... no... it's standard procedure in the freebsd world... freebsd itself > works when chflags is off, gentoo/freebsd should too... or it can't really call > itself freebsd at all... No, we call it Gentoo/FreeBSD. Or did you expect the FreeBSD rc system to work here as well?
