To: ncunningham@linuxmail.org, pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: Suspend 2 merge: 35/51: Code always built in to the kernel.
In-Reply-To: <1101427035.27250.161.camel@desktop.cunninghams>
References: <1101292194.5805.180.camel@desktop.cunninghams> <1101298112.5805.330.camel@desktop.cunninghams> <20041125233243.GB2909@elf.ucw.cz> <20041125233243.GB2909@elf.ucw.cz> <1101427035.27250.161.camel@desktop.cunninghams>
Date: Sat, 27 Nov 2004 02:19:15 +0000
Message-Id: <E1CXsB9-00022M-00@chiark.greenend.org.uk>
From: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 938
Lines: 20

Nigel Cunningham <ncunningham@linuxmail.org> wrote:

> You want your cake and to eat it too? :> We don't want to warn the user
> before they shoot themselves in the foot, but not loudly enough that
> they can't help notice and choose to do something before the damage is
> done?

We have userspace to do this, surely? Make the standard method of
triggering resume involve an initrd, and have a small application that
does sanity checks before the resume. In case of failure, have it prompt
the user. As long as it doesn't do bad things to the filesystem,
there's no danger. There's no reason to do this in the kernel.

-- 
Matthew Garrett | mjg59-chiark.mail.linux-rutgers.kernel@srcf.ucam.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/