On Fri, Aug 24, 2012 at 12:17:08PM -0400, Alan Stern wrote:
> I need some help with a problem.
>
> I'm currently using Fedora 16, but without a display manager. I log
> into a text-mode VT (usually tty1) and run startx manually. The
> display uses tty7 and works fine.
>
> But systemd isn't awar
I need some help with a problem.
I'm currently using Fedora 16, but without a display manager. I log
into a text-mode VT (usually tty1) and run startx manually. The
display uses tty7 and works fine.
But systemd isn't aware of it, or at least, isn't aware that my login
session now owns tty7. F
On Thu, 2012-08-23 at 17:46 +0100, Alan Cox wrote:
> > IMO, the driver probing path is allowed to sleep, so looks request
> firmware
> > should be allowed inside .probe().
>
> I'm not convinced about that. It can sleep but its holding various
> locks
> in most cases, and it looks like that can end
Proper handling of reboot() syscall issued from the inside of a container
was always supported by OpenVZ kernels. More to say, OpenVZ relies on the fact
that container calls reboot in order to distinguish between shutdown and
reboot-- in the latter case container is being restarted.
This patch bri
From: Kir Kolyshkin
Proper handling of reboot() syscall issued from the inside of a container
was always supported by OpenVZ kernels. More to say, OpenVZ relies on the fact
that container calls reboot in order to distinguish between shutdown and
reboot-- in the latter case container is being rest
