On Fri, Nov 23, 2012 at 10:41:20AM +0100, Tomasz Torcz wrote: > On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote: > > > Any ideas? > > > > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a > > universal problem. I also use getty on the serial port, with no local > > modifications. > > > > I believe the requirement for a 3.4 (or something) kernel came in 188 > > for some logging bits, although I'm not sure. systemd should work > > just fine without it, though. > > v189 NEWS: > > * Support for reading kernel messages from /proc/kmsg has now > been removed. If you want kernel messages in the journal > make sure to run a recent kernel (>= 3.5) that supports > reading structured messages from /dev/kmsg (see above).
Okay, that doesn't sound very much like a general incompatibility. The way I read that, the worst that will happen on older kernels is that kernel messages don't make it to the journal. But the boot process shouldn't be hanging because of it. Thierry
pgp7PBZnrWkMu.pgp
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
