From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] busybox: add an inittab entry to activate swap
Date: Tue, 12 Jun 2018 14:58:59 +0200 [thread overview]
Message-ID: <87a7s06u0c.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180611060016.20755-4-casantos@datacom.com.br> (Carlos Santos's message of "Mon, 11 Jun 2018 03:00:15 -0300")
>>>>> "Carlos" == Carlos Santos <casantos@datacom.com.br> writes:
> There is a call to swapoff in the shutdown sequence, so call "swapon -a"
> on startup. As stated in the swapon man page,
> All devices marked as "swap" in /etc/fstab are made available, except
> for those with the "noauto" option. Devices that are already being
> used as swap are silently skipped.
> So even if the system has some init script to start/stop swap (e.g. from
> a rootfs ovelay) calling swapon/swapoff would be harmless.
I guess an explicit swapon <device> after swapon -a (with an entry for
<device> in /etc/fstab) will fail with an error message, but OK - That
is easy to fix if that happens.
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-06-12 12:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 6:00 [Buildroot] [PATCH 0/4] synchronize initab files and enable swap on startup Carlos Santos
2018-06-11 6:00 ` [Buildroot] [PATCH 1/4] sysvinit: reduce number of mkdir calls in inittab Carlos Santos
2018-06-12 9:22 ` Peter Korsgaard
2018-06-17 15:54 ` Peter Korsgaard
2018-06-11 6:00 ` [Buildroot] [PATCH 2/4] sysvinit: add an inittab entry to activate swap Carlos Santos
2018-06-12 12:56 ` Peter Korsgaard
2018-06-17 15:54 ` Peter Korsgaard
2018-06-11 6:00 ` [Buildroot] [PATCH 3/4] busybox: " Carlos Santos
2018-06-12 12:58 ` Peter Korsgaard [this message]
2018-06-17 15:54 ` Peter Korsgaard
2018-06-11 6:00 ` [Buildroot] [PATCH 4/4] board/synopsys: synchronize custom inittab with BusyBox' one Carlos Santos
2018-06-12 13:01 ` Peter Korsgaard
2018-06-17 15:54 ` Peter Korsgaard
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=87a7s06u0c.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.