Hi.
On Mon, 2005-03-21 at 20:33, Stefan Seyfried wrote:
> Hi,
>
> Nigel Cunningham wrote:
>
> > On Mon, 2005-03-21 at 11:17, Matthew Garrett wrote:
>
> >> It's trivial to do this in userspace - just have an app in initramfs
>
> > It's not that trivial.
>
> > - Your image might not be stored i
Hi,
Nigel Cunningham wrote:
> On Mon, 2005-03-21 at 11:17, Matthew Garrett wrote:
>> It's trivial to do this in userspace - just have an app in initramfs
> It's not that trivial.
> - Your image might not be stored in a swap partition. For Suspend2, it
> can potentially in a swap file or (soon)
Hi.
On Mon, 2005-03-21 at 18:38, Stefan Seyfried wrote:
> Nigel Cunningham wrote:
> > Hi.
> >
> > On Sun, 2005-03-20 at 08:29, Pavel Machek wrote:
>
> >> boot with "noresume", then mkswap.
> >
> > Yuck! Why panic when you know what is needed? A better solution is to
>
> Ok, so let's
>
> pri
Nigel Cunningham wrote:
> Hi.
>
> On Sun, 2005-03-20 at 08:29, Pavel Machek wrote:
>> boot with "noresume", then mkswap.
>
> Yuck! Why panic when you know what is needed? A better solution is to
Ok, so let's
printk("You booted another kernel than you suspended with.\n");
printk("You have
Hi.
On Mon, 2005-03-21 at 11:17, Matthew Garrett wrote:
> Nigel Cunningham <[EMAIL PROTECTED]> wrote:
>
> > Yuck! Why panic when you know what is needed? A better solution is to
> > tell the user they've messed up and given them the option to (1) reboot
> > and try another kernel or (2) have swsu
Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> Yuck! Why panic when you know what is needed? A better solution is to
> tell the user they've messed up and given them the option to (1) reboot
> and try another kernel or (2) have swsusp restore the original swap
> signature and continue booting. This
Hi.
On Sun, 2005-03-20 at 08:29, Pavel Machek wrote:
> On So 19-03-05 12:20:35, Russell Miller wrote:
> > On Saturday 19 March 2005 05:26, Pavel Machek wrote:
> >
> > > Checking that would be hard, but you might want to provide patch to check
> > > last-mounted dates of filesystems and panic if t
On Saturday 19 March 2005 13:29, Pavel Machek wrote:
> On So 19-03-05 12:20:35, Russell Miller wrote:
> > On Saturday 19 March 2005 05:26, Pavel Machek wrote:
> > > Checking that would be hard, but you might want to provide patch to
> > > check last-mounted dates of filesystems and panic if they ch
On So 19-03-05 12:20:35, Russell Miller wrote:
> On Saturday 19 March 2005 05:26, Pavel Machek wrote:
>
> > Checking that would be hard, but you might want to provide patch to check
> > last-mounted dates of filesystems and panic if they changed.
> > Pavel
>
> Then how
On Saturday 19 March 2005 05:26, Pavel Machek wrote:
> Checking that would be hard, but you might want to provide patch to check
> last-mounted dates of filesystems and panic if they changed.
> Pavel
Then how would you fix it? There'd also have to be a way to reset
Hi!
> Hello, I experienced a pretty nasty problem a couple of days back:
>
> I ran 2.6.11-ck1 and built 2.6.11-ck2. The last thing I did before
> booting the new kernel was to suspend-to-disk the old kernel
> (something I usually do as I'm working on this laptop).
> I ran the new kernel a coupl
Hi.
The simplest solution is to mkswap your swap partitions during boot.
Nigel
On Sat, 2005-03-19 at 03:28, Erik Andrén wrote:
> Hello, I experienced a pretty nasty problem a couple of days back:
>
> I ran 2.6.11-ck1 and built 2.6.11-ck2. The last thing I did before
> booting the new kernel wa
Erik Andrén wrote:
> My question is: Why isn't there a check before resuming a
> suspend-to-disk image if the system has booted another kernel since the
> suspend to prevent this kind of hassle?
Just provide a patch which does this. Hint: this is highly nontrivial.
If you boot a kernel, that do
Hello, I experienced a pretty nasty problem a couple of days back:
I ran 2.6.11-ck1 and built 2.6.11-ck2. The last thing I did before
booting the new kernel was to suspend-to-disk the old kernel (something
I usually do as I'm working on this laptop).
I ran the new kernel a couple of days and deci
14 matches
Mail list logo