public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] Adding swap space to the encrypted partition
Date: Mon, 10 Jun 2024 10:59:04 +0200	[thread overview]
Message-ID: <2bd98a44-7974-4969-8e4f-c33db4f3edb3@siemens.com> (raw)
In-Reply-To: <7313.1717714182247115411@lists.cip-project.org>

Hi John,

On 6/7/24 12:49 AM, JohnW via lists.cip-project.org wrote:
> Hi Quirin,
> 
> I attempted to add a swap space within the wks file. However it created 
> a swap space outside the encrypted partition.

yes this is expected you would need to add the swap partition to the 
list of partition(variable CRYPT_PARTITIONS) to be encrypted. This would
also require to modify /etc/fstab.

Could be a swap file an alternative?

Best regards
Quirin
> 
> We have devices that does not have large RAM where the swap space is 
> needed to keep things running, so it is necessary for us to include a 
> swap space within our partition.

> 
> Regards,
> John
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#16131): https://lists.cip-project.org/g/cip-dev/message/16131
> Mute This Topic: https://lists.cip-project.org/mt/106372674/1753640
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129121/1753640/1405269326/xyzzy [quirin.gylstorff@siemens.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


  reply	other threads:[~2024-06-10  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 16:51 Adding swap space to the encrypted partition JohnW
2024-06-06  8:17 ` [cip-dev] " Gylstorff Quirin
2024-06-06 22:49   ` JohnW
2024-06-10  8:59     ` Gylstorff Quirin [this message]
2024-06-10 18:46       ` JohnW
2024-06-11  3:31         ` JohnW
2024-06-11  5:37           ` [cip-dev] " quirin.gylstorff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2bd98a44-7974-4969-8e4f-c33db4f3edb3@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox