Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Mar 2004 14:44:28 +0100
From:      Eirik Oeverby <ltning-freebsd-current@anduin.net>
To:        Andy Hilker <ah@crypta.net>
Cc:        current@freebsd.org
Subject:   Re: Jails in -CURRENT
Message-ID:  <1078407868.91467.47.camel@eirik.unicore.no>
In-Reply-To: <20040304130111.GA69263@mail.crypta.net>
References:  <1078394634.91467.0.camel@eirik.unicore.no> <20040304130111.GA69263@mail.crypta.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2004-03-04 at 14:01 +0100, Andy Hilker wrote:

> Hi,
> 
> > I can give you an outline of what my script does, then it'll be
> > for you to judge if it can be called a 'jail management' tool.. ;)
> 
> I have written a similar shell script:
> - config file for all jails
> - config file for mounts in jails
> - stop/start all and individual jails
> - stopping a jail identifies all procs and kill them. I think in
> current that could be better made with jexec.  
> - list procs and mounts
> 
> I am mounting binaries etc. ro from Host System. Only configuration,
> homes etc. are individual per jail.
> Updating is much easier.

Does this mean that the installed software in the jail is 'fixed'? I.e.
installed software on host == installed software in jail? Or do you only
r-o mount /bin, /sbin, /usr/bin, etc. etc.? I've been considering such
an approach, and have already started making it an option in my script,
however wether or not this is wanted depends highly on how it's
implemented and what use you have for the jails.
Obviously in a jail that is acting as a true 'virtual server', this will
be less than optimal.

> > Future plans include finding a way to inject processes into jails 
> 
> In FreeBSD-Current no problem: jls / jexec
> 
> If anyone interested, maybe someone could merge both shell scripts,
> picking the good things and discarding the bugs ;)

Good idea. Where can I find yours? I'm trying to write a manpage for
mine, then I'll pack it up and throw it up on my website. I will
probably put together a port aswell, but I have no idea how to proceed
with that ;)

/Eirik

> 
> bye,
> Andy
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1078407868.91467.47.camel>