Ben Milman | 15 Jun 2012 02:12
Favicon

New ports jails issues

Hi, 


So I tried to get a ports jail to install and run under the new Warden. I opened the jail terminal only to find that /usr/ports was empty. A 'portsnap fetch' within the jail failed. When I checked /usr/ports on the outer system it was empty, I must have forgotten to include it at install time. After performing 'portsnap fetch extract' on the outer system, a new ports jail with the ports tree included worked as expected. I presume that the ports checkbox in the new jail wizard causes the ports tree from the outer system to be copied into the jail? If that's the case, I have some objections: That doesn't take into account the possibility of the outer ports tree being missing or modified, and there is no warning for cases like what I experienced.

I didn't look into what caused portsnap to fail within the jail, but that might be a related or unrelated issue.

Thanks,
Ben
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Kris Moore | 15 Jun 2012 16:17
Gravatar

Re: New ports jails issues

On 06/14/2012 20:12, Ben Milman wrote:
Hi, 

So I tried to get a ports jail to install and run under the new Warden. I opened the jail terminal only to find that /usr/ports was empty. A 'portsnap fetch' within the jail failed. When I checked /usr/ports on the outer system it was empty, I must have forgotten to include it at install time. After performing 'portsnap fetch extract' on the outer system, a new ports jail with the ports tree included worked as expected. I presume that the ports checkbox in the new jail wizard causes the ports tree from the outer system to be copied into the jail? If that's the case, I have some objections: That doesn't take into account the possibility of the outer ports tree being missing or modified, and there is no warning for cases like what I experienced.

I didn't look into what caused portsnap to fail within the jail, but that might be a related or unrelated issue.

Thanks,
Ben


_______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing

I've just improved this, so that it will checkout ports from portsnap instead of just copying from /usr/ports. Also, it will now display warnings if it fails. Ditto with system sources.

-- Kris Moore PC-BSD Software iXsystems
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Lars Engels | 15 Jun 2012 18:25

Re: New ports jails issues

On Fri, Jun 15, 2012 at 10:17:32AM -0400, Kris Moore wrote:
> On 06/14/2012 20:12, Ben Milman wrote:
> > Hi, 
> >
> > So I tried to get a ports jail to install and run under the new
> > Warden. I opened the jail terminal only to find that /usr/ports was
> > empty. A 'portsnap fetch' within the jail failed. When I checked
> > /usr/ports on the outer system it was empty, I must have forgotten to
> > include it at install time. After performing 'portsnap fetch extract'
> > on the outer system, a new ports jail with the ports tree included
> > worked as expected. I presume that the ports checkbox in the new jail
> > wizard causes the ports tree from the outer system to be copied into
> > the jail? If that's the case, I have some objections: That doesn't
> > take into account the possibility of the outer ports tree being
> > missing or modified, and there is no warning for cases like what I
> > experienced.
> >
> > I didn't look into what caused portsnap to fail within the jail, but
> > that might be a related or unrelated issue.
> >
> > Thanks,
> > Ben
> >
> >
> > _______________________________________________
> > Testing mailing list
> > Testing@...
> > http://lists.pcbsd.org/mailman/listinfo/testing
> 
> I've just improved this, so that it will checkout ports from portsnap
> instead of just copying from /usr/ports. Also, it will now display
> warnings if it fails. Ditto with system sources.

Could you make the fetch job optional? If you create a couple of (port-)
jails it always needs to fetch the whole ports tree.
It would be nice to select:

[ ] Copy Ports Tree from host system
[ ] Download current Ports Tree from the internet
[ ] Use the host system's Ports Tree (via nullmount)
[ ] Don't install a Ports Tree

BTW copying /usr/ports is not enough. If you want to use portsnap you
also need /var/db/portsnap.
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Lars Engels | 12 Jul 2012 21:46

Re: New ports jails issues

On Fri, Jun 15, 2012 at 06:25:18PM +0200, Lars Engels wrote:
> On Fri, Jun 15, 2012 at 10:17:32AM -0400, Kris Moore wrote:
> > On 06/14/2012 20:12, Ben Milman wrote:
> > > Hi, 
> > >
> > > So I tried to get a ports jail to install and run under the new
> > > Warden. I opened the jail terminal only to find that /usr/ports was
> > > empty. A 'portsnap fetch' within the jail failed. When I checked
> > > /usr/ports on the outer system it was empty, I must have forgotten to
> > > include it at install time. After performing 'portsnap fetch extract'
> > > on the outer system, a new ports jail with the ports tree included
> > > worked as expected. I presume that the ports checkbox in the new jail
> > > wizard causes the ports tree from the outer system to be copied into
> > > the jail? If that's the case, I have some objections: That doesn't
> > > take into account the possibility of the outer ports tree being
> > > missing or modified, and there is no warning for cases like what I
> > > experienced.
> > >
> > > I didn't look into what caused portsnap to fail within the jail, but
> > > that might be a related or unrelated issue.
> > >
> > > Thanks,
> > > Ben
> > >
> > >
> > > _______________________________________________
> > > Testing mailing list
> > > Testing@...
> > > http://lists.pcbsd.org/mailman/listinfo/testing
> > 
> > I've just improved this, so that it will checkout ports from portsnap
> > instead of just copying from /usr/ports. Also, it will now display
> > warnings if it fails. Ditto with system sources.
> 
> Could you make the fetch job optional? If you create a couple of (port-)
> jails it always needs to fetch the whole ports tree.
> It would be nice to select:
> 
> [ ] Copy Ports Tree from host system
> [ ] Download current Ports Tree from the internet
> [ ] Use the host system's Ports Tree (via nullmount)
> [ ] Don't install a Ports Tree
> 
> BTW copying /usr/ports is not enough. If you want to use portsnap you
> also need /var/db/portsnap.

Kris, did you take a look at this already? :)
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing
Kris Moore | 13 Jul 2012 15:46
Gravatar

Re: New ports jails issues

On 07/12/2012 15:46, Lars Engels wrote:
On Fri, Jun 15, 2012 at 06:25:18PM +0200, Lars Engels wrote:
On Fri, Jun 15, 2012 at 10:17:32AM -0400, Kris Moore wrote:
On 06/14/2012 20:12, Ben Milman wrote:
Hi, So I tried to get a ports jail to install and run under the new Warden. I opened the jail terminal only to find that /usr/ports was empty. A 'portsnap fetch' within the jail failed. When I checked /usr/ports on the outer system it was empty, I must have forgotten to include it at install time. After performing 'portsnap fetch extract' on the outer system, a new ports jail with the ports tree included worked as expected. I presume that the ports checkbox in the new jail wizard causes the ports tree from the outer system to be copied into the jail? If that's the case, I have some objections: That doesn't take into account the possibility of the outer ports tree being missing or modified, and there is no warning for cases like what I experienced. I didn't look into what caused portsnap to fail within the jail, but that might be a related or unrelated issue. Thanks, Ben _______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing
I've just improved this, so that it will checkout ports from portsnap instead of just copying from /usr/ports. Also, it will now display warnings if it fails. Ditto with system sources.
Could you make the fetch job optional? If you create a couple of (port-) jails it always needs to fetch the whole ports tree. It would be nice to select: [ ] Copy Ports Tree from host system [ ] Download current Ports Tree from the internet [ ] Use the host system's Ports Tree (via nullmount) [ ] Don't install a Ports Tree BTW copying /usr/ports is not enough. If you want to use portsnap you also need /var/db/portsnap.
Kris, did you take a look at this already? :)

_______________________________________________ Testing mailing list Testing-Fhbtn2kkCAMmbxgs1yVkuA@public.gmane.org http://lists.pcbsd.org/mailman/listinfo/testing

Yes, I did briefly, and eventually that is what is going to happen. That, along with being able to queue up the creation of X number of jails. I just didn't have the time to get it in before 9.1-BETA1. Once we get 9.1 out the door, I'll be working on that, among other features :)

-- Kris Moore PC-BSD Software iXsystems
_______________________________________________
Testing mailing list
Testing@...
http://lists.pcbsd.org/mailman/listinfo/testing

Gmane