On Thu, 7 May 2015 at 14:43 Brian May br...@microcomaustralia.com.au
wrote:
Looks like my system is still using wheezy/pve which has somewhat old
packages; will need to change that to wheezy/pve-no-subscription and update
as soon as I can.
So I upgraded my kernel, at first glance it seems a
On Tue, 12 May 2015 at 20:23 Ondřej Surý ond...@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
On Sun, May 3, 2015, at 05:47, Gunnar Wolf wrote:
Brian May dijo [Sat, May 02, 2015 at 09:39:50AM +]:
Hello,
If I upgrade a Jessie openvz container on my proxmox box, systemd fails to
start up. This is no surprise, the kernel seems to be rather old:
root@scrooge:/# uname -a
On Mon, 4 May 2015 at 19:12 Florian Ernst florian_er...@gmx.net wrote:
root@vzhost04:/usr/local/users/support/fe# apt-cache policy
pve-kernel-2.6.32-37-pve
pve-kernel-2.6.32-37-pve:
Installed: 2.6.32-150
Candidate: 2.6.32-150
Version table:
*** 2.6.32-150 0
500
On Sun, May 03, 2015 at 04:34:18AM +, Brian May wrote:
On Sat, 2 May 2015 at 23:33 Bastian Blank wa...@debian.org wrote:
Yes, there is a pve kernel available containing a backport of this
missing piece. I think it is something like -36.
Ah, thanks for the hint. I hadn't checked yet
On Sun, May 3, 2015 at 12:38 PM, Brian May wrote:
What package should I file it against? systemd?
Yes, systemd.
What about other packages that call systemctl in postinst/postrm scripts
without first checking that systemd is operational? Is the fault in the
script that calls systemctl, or
On Sun, 3 May 2015 15:20:11 +0800, Paul Wise p...@debian.org wrote:
On Sun, May 3, 2015 at 12:38 PM, Brian May wrote:
What about other packages that call systemctl in postinst/postrm scripts
without first checking that systemd is operational? Is the fault in the
script that calls systemctl, or
Hello,
If I upgrade a Jessie openvz container on my proxmox box, systemd fails to
start up. This is no surprise, the kernel seems to be rather old:
root@scrooge:/# uname -a
Linux scrooge 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST 2013 i686
GNU/Linux
Obviously, I should have set things up not
Hi Marco
On Sat, May 02, 2015 at 03:05:35PM +0200, Marco d'Itri wrote:
On May 02, Brian May br...@microcomaustralia.com.au wrote:
If I upgrade a Jessie openvz container on my proxmox box, systemd fails to
start up. This is no surprise, the kernel seems to be rather old:
Indeed. Did you
On Sat, May 2, 2015 at 5:39 PM, Brian May wrote:
Is this the thing I should be filling bug reports about?
I think so yes.
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On May 02, Brian May br...@microcomaustralia.com.au wrote:
If I upgrade a Jessie openvz container on my proxmox box, systemd fails to
start up. This is no surprise, the kernel seems to be rather old:
Indeed. Did you check if a newer PVE kernel maybe has a backport of the
features needed to use
On Sat, 2 May 2015 at 23:33 Bastian Blank wa...@debian.org wrote:
Yes, there is a pve kernel available containing a backport of this
missing piece. I think it is something like -36.
I had a look, but couldn't find anything like that. Only thing I could find
is this reference from last year,
On Sun, 3 May 2015 at 13:47 Gunnar Wolf gw...@gwolf.org wrote:
Once that package is installed, your containers will run just
fine. And if you forgot to install it and upgraded only to find your
systems not starting up, you can chroot and install it.
Yes, that is basically what I did. Seems
On Sat, 2 May 2015 at 21:36 Paul Wise p...@debian.org wrote:
On Sat, May 2, 2015 at 5:39 PM, Brian May wrote:
Is this the thing I should be filling bug reports about?
I think so yes.
What package should I file it against? systemd?
What about other packages that call systemctl in
Brian May dijo [Sat, May 02, 2015 at 09:39:50AM +]:
Hello,
If I upgrade a Jessie openvz container on my proxmox box, systemd fails to
start up. This is no surprise, the kernel seems to be rather old:
root@scrooge:/# uname -a
Linux scrooge 2.6.32-26-pve #1 SMP Mon Oct 14 08:22:20 CEST
15 matches
Mail list logo
