| 1 |
On Mon, Aug 18, 2014 at 2:21 PM, J. Roeleveld <joost@××××××××.org> wrote: |
| 2 |
> |
| 3 |
> In cases like that I would do either of the following: |
| 4 |
> |
| 5 |
> 1) Run it inside a VM |
| 6 |
> 2) run it inside a chroot |
| 7 |
> |
| 8 |
> That way you can easily keep everything updated except for that application. |
| 9 |
|
| 10 |
Or better still run it inside a container. Gives you most of the |
| 11 |
benefits of both a VM and a chroot. It isn't as isolated as a VM, but |
| 12 |
it is more isolated than just running the thing on your system. It is |
| 13 |
also easy to bind-mount your home directory if that is helpful. A |
| 14 |
container replaces the entire userspace, potentially including init as |
| 15 |
well. So, as long as your kernel is compatible and you're not doing |
| 16 |
anything too crazy with devices, this should solve your compatibility |
| 17 |
issues. |
| 18 |
|
| 19 |
-- |
| 20 |
Rich |
Archives