You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like for Grml to provide a way to chain boot into memtest86. I believe this is possible based on articles from the Tails project which experimented with using memtest86 to wipe memory and are currently chain-loading something (sdmem, perhaps?) with kexec to provide safe memory erasure.
I have also seen articles here and there about people doing exactly this: chain loading memtest86 from kexec. The advantage of this approach is that (a) it's faster and (b) we can trigger it from the user environment automatically. While it is possible to use the grub-reboot command to select a new entry to automatically boot another system, this won't work for readonly, netbooted or "ram resident" Grml instances, as those changes will be lost on reboot.
Therefore, it would be useful to be able to chain-load into memtest86. This would be a key component of the stressant project I am working on.
The text was updated successfully, but these errors were encountered:
I would like for Grml to provide a way to chain boot into memtest86. I believe this is possible based on articles from the Tails project which experimented with using memtest86 to wipe memory and are currently chain-loading something (sdmem, perhaps?) with kexec to provide safe memory erasure.
I have also seen articles here and there about people doing exactly this: chain loading memtest86 from kexec. The advantage of this approach is that (a) it's faster and (b) we can trigger it from the user environment automatically. While it is possible to use the grub-reboot command to select a new entry to automatically boot another system, this won't work for readonly, netbooted or "ram resident" Grml instances, as those changes will be lost on reboot.
Therefore, it would be useful to be able to chain-load into memtest86. This would be a key component of the stressant project I am working on.
The text was updated successfully, but these errors were encountered: