From: rdslw <rdslw@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux5.15 package install scripts fails if /boot is mounted on vfat fstype
Date: Thu, 02 Nov 2023 17:21:54 +0100 [thread overview]
Message-ID: <20231102162154.BdKXgbf08S8FT4qKPkVMla_uGKGjmarANsosoBgKrWc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47011@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
New comment by rdslw on void-packages repository
https://github.com/void-linux/void-packages/issues/47011#issuecomment-1791057531
Comment:
@Duncaen @classabbyamp I do use different /boot mount flags, so this might be the problem. Let me know any tests you want to do it.
```
$> grep boot /etc/fstab ~
LABEL=ESP /boot vfat rw,relatime,fmask=0117,dmask=0007,gid=10,iocharset=iso8859-1,codepage=437,shortname=mixed,errors=remount-ro 0 2
$> mount |grep boot ~
/dev/nvme0n1p1 on /boot type vfat (rw,relatime,gid=10,fmask=0117,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
```
next prev parent reply other threads:[~2023-11-02 16:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:01 [ISSUE] " rdslw
2023-11-01 18:19 ` Duncaen
2023-11-01 18:26 ` Duncaen
2023-11-01 18:38 ` rdslw
2023-11-01 18:43 ` classabbyamp
2023-11-01 18:59 ` rdslw
2023-11-01 19:02 ` rdslw
2023-11-01 19:09 ` Duncaen
2023-11-01 19:10 ` Duncaen
2023-11-01 19:24 ` Duncaen
2023-11-01 19:24 ` Duncaen
2023-11-01 19:25 ` classabbyamp
2023-11-01 19:25 ` Duncaen
2023-11-02 16:21 ` rdslw [this message]
2023-11-02 23:20 ` Duncaen
2023-11-02 23:20 ` Duncaen
2023-11-02 23:25 ` Duncaen
2023-11-02 23:26 ` Duncaen
2023-11-03 8:07 ` rdslw
2023-12-03 1:01 ` [ISSUE] [CLOSED] " ahesford
2023-12-03 1:01 ` ahesford
2024-01-13 10:32 ` rdslw
2024-01-13 11:08 ` Duncaen
2024-01-13 12:02 ` rdslw
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=20231102162154.BdKXgbf08S8FT4qKPkVMla_uGKGjmarANsosoBgKrWc@z \
--to=rdslw@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).