On Mon, Oct 30, 2006 at 12:26:55PM +0100, Rafael J. Wysocki wrote:
> > Well, but if some data structures are different than the tmpfs driver thinks
> > they are, the kernel could oops/panic at umount, couldn't it?
>
> Yes, it could, but they won't be. After a successful resume the tmpfs will
> be
On Mon, Oct 30, 2006 at 12:14:30PM +, Matej Cepl wrote:
> Why not for swap? OK, except that suspend cannot work :-). Does it
> mean that I should switch to inserting password for swap?
yes, that's necessary. luks is nice for managing the passwords.
Jason
-
Tim Dijkstra scripst:
>> is something like that possible. Suspend writes to (then encrypted with
>> /dev/urandom key) image of the frozen memory, so how can resume decrypt
> Random key?
Why not for swap? OK, except that suspend cannot work :-). Does it mean
that I should switch to inserting passw
On Monday, 30 October 2006 12:08, Stefan Seyfried wrote:
> On Mon, Oct 30, 2006 at 11:57:47AM +0100, Rafael J. Wysocki wrote:
> > On Monday, 30 October 2006 09:37, Stefan Seyfried wrote:
> > > On Mon, Oct 30, 2006 at 12:20:50AM +0100, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > Unfortunat
On Mon, Oct 30, 2006 at 11:57:47AM +0100, Rafael J. Wysocki wrote:
> On Monday, 30 October 2006 09:37, Stefan Seyfried wrote:
> > On Mon, Oct 30, 2006 at 12:20:50AM +0100, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > Unfortunately in its current form s2disk causes the access time of the
> > > r
On Monday, 30 October 2006 09:37, Stefan Seyfried wrote:
> On Mon, Oct 30, 2006 at 12:20:50AM +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > Unfortunately in its current form s2disk causes the access time of the
> > resume
> > device special file to be updated after the suspend image has been cr
On Mon, Oct 30, 2006 at 10:36:46AM +0100, Tim Dijkstra wrote:
> On Mon, 30 Oct 2006 00:20:50 +0100
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > Unfortunately in its current form s2disk causes the access time of the
> > resume
> > device special file to be updated after the suspend image
On Mon, Oct 30, 2006 at 10:36:59AM +0100, Einon wrote:
> Hi!
>
> I checked what you asked. Rebooted my notebook in text-only (single)
> mode, and tried the s2ram with all the parameter variations shown on
> the documentation page. The result was the same every time:
>
> suspended into ram success
Hi!
I checked what you asked. Rebooted my notebook in text-only (single)
mode, and tried the s2ram with all the parameter variations shown on
the documentation page. The result was the same every time:
suspended into ram successfully, but when I pressed a key on the
keyboad (my bios does not "fee
On Mon, 30 Oct 2006 00:20:50 +0100
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> Unfortunately in its current form s2disk causes the access time of the resume
> device special file to be updated after the suspend image has been created,
> which is potentially dangerous.
Why is that dangerous?
On Sun, 29 Oct 2006 23:15:15 + (UTC)
"Matej Cepl" <[EMAIL PROTECTED]> wrote:
> Jason Lunz scripst:
> > Yes, it works just fine. I've been running a laptop with dm-crypt on
> > swap and root for months now - only /boot is unencrypted.
>
> That's cool -- more I am thinking about that more I don
On Mon, Oct 30, 2006 at 12:20:50AM +0100, Rafael J. Wysocki wrote:
> Hi,
>
> Unfortunately in its current form s2disk causes the access time of the resume
> device special file to be updated after the suspend image has been created,
> which is potentially dangerous.
>
> We can fix this by mountin
On Thu, Oct 26, 2006 at 02:38:12AM +0300, sir_j wrote:
> hi Stefan.
> I can't configure suspend to ram
> Here is output of tool s2ram
>
>
> sirj:/home/sir_j# s2ram
> Machine is unknown.
> This machine can be ident
On Sat, Oct 21, 2006 at 09:18:47PM +0200, Philip Frei wrote:
> Hi,
>
> I've got an Asus S5200N notebook:
> This machine can be identified by:
> sys_vendor = "ASUSTeK Computer Inc."
> sys_product = "S5N "
> sys_version = "1.0 "
> bios_version = "0213
>
> I f
On Sat, Oct 28, 2006 at 10:50:06AM +0200, Einon wrote:
> Hi!
>
> My machine is not recognised by default, but works fine with
> s2ram -f, so here is a small report:
>
> Gericom Bellagio 1540
>
> misato:~# s2ram
> Machine is unknown.
> This machine can be identified by:
> sys_vendor = "Ger
15 matches
Mail list logo
