Re: upgrading to jessie on container with old kernel

To: Ondřej Surý <ondrej@sury.org>, debian-devel@lists.debian.org
Subject: Re: upgrading to jessie on container with old kernel
From: Brian May <brian@microcomaustralia.com.au>
Date: Wed, 13 May 2015 01:04:13 +0000
Message-id: <[🔎] CAA0ZO6AWCX-bkYGH2Y-kBkCVTAGBOUmEHo176E6Ui03xUi-58w@mail.gmail.com>
In-reply-to: <[🔎] 1431426213.2625424.266506865.2E703CE3@webmail.messagingengine.com>
References: <[🔎] CAA0ZO6Cs2_b0V_txf6eYj6AgiuNkG3dfrD-WsCQa2izhqmq+kg@mail.gmail.com> <[🔎] 20150503034751.GC53630@gwolf.org> <[🔎] 1431426213.2625424.266506865.2E703CE3@webmail.messagingengine.com>

On Tue, 12 May 2015 at 20:23 Ondřej Surý <ondrej@sury.org> wrote:

That's probably not true in a general case, since I am running LXC on
jessie (LXC+systemd in host and systemd in guest) and I have been
running this with backported systemd and lxc on wheezy before jessie was
release.

Perhaps it might be a true for hosts not running systemd?

If the host is already running systemd, then obviously your kernel must have the required support for systemd already, and you won't have any problems.

Reply to:

References:
- upgrading to jessie on container with old kernel
  - From: Brian May <brian@microcomaustralia.com.au>
- Re: upgrading to jessie on container with old kernel
  - From: Gunnar Wolf <gwolf@gwolf.org>
- Re: upgrading to jessie on container with old kernel
  - From: Ondřej Surý <ondrej@sury.org>

Prev by Date: Bug#785160: ITP: debian-hamradio -- Debian Hamradio Pure Blend Metapackages
Next by Date: Bug#785166: ITP: golang-bmizerany-assert -- Assertions library for Go tests
Previous by thread: Re: upgrading to jessie on container with old kernel
Next by thread: Bug#784026: ITP: python-spur -- Run commands and manipulate files locally or over SSH using the same interface
Index(es):
- Date
- Thread