From: superiums <superiums@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Data loose on lvm after reboot
Date: Tue, 22 Nov 2022 15:00:33 +0100 [thread overview]
Message-ID: <20221122140033.6EhLZWyGgoQeiZM0GLiPxEtkZLUMeGQPTCXK1gwUfNg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40589@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/40589#issuecomment-1323723547
Comment:
> Do you have `elogind` installed and enabled?
yes , elogind was installed, and started.
but the service was not enabled.
maybe started by greetd.
> ~`/dev/shm` is used by the shared-memory interface and not intended for direct use by users.~ In general, you should never mount thing inside `/dev`.
>
> Edit: turns out `/dev/shm` is just a tmpfs mount and is intended for users to store things guaranteed not to be on disk (this seems like a poorly developed concept, because you shouldn't expect any particular storage behavior based solely on where you save and read files), but that has no bearing on the recommendation against mounting things under `/dev/`
thank you very much!
next prev parent reply other threads:[~2022-11-22 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 3:04 [ISSUE] " superiums
2022-11-19 20:17 ` ahesford
2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
2022-11-20 9:11 ` superiums
2022-11-20 12:36 ` ahesford
2022-11-21 7:06 ` superiums
2022-11-21 8:32 ` sgn
2022-11-21 13:02 ` [ISSUE] [CLOSED] " ahesford
2022-11-21 13:02 ` ahesford
2022-11-21 14:58 ` ahesford
2022-11-22 14:00 ` superiums
2022-11-22 14:00 ` superiums [this message]
2022-11-22 14:01 ` superiums
2022-11-22 14:13 ` sgn
2022-11-23 4:47 ` superiums
2022-11-23 4:49 ` superiums
2022-11-23 7:33 ` sgn
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=20221122140033.6EhLZWyGgoQeiZM0GLiPxEtkZLUMeGQPTCXK1gwUfNg@z \
--to=superiums@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).