From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] m.2 nvme stick not what I was expecting at all.
Date: Tue, 25 Feb 2025 17:00:59 +0000 [thread overview]
Message-ID: <2301845.iZASKD2KPV@rogueboard> (raw)
In-Reply-To: <12640654.O9o76ZdvQC@cube>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Tuesday, 25 February 2025 14:48:52 Greenwich Mean Time Peter Humphrey
wrote:
> On Monday 24 February 2025 22:48:26 Greenwich Mean Time Frank Steinmetzger
>
> wrote:
> > You need a common denominator. ExFat is a good candidate, methinks, as it
> > won’t give any issues with file permissions. Since I’ve never held an iOS
> > device in my hands, I have no idea about what FS they support. But the
> > answer should be just a short DuckDuck away. :)
>
> I tried exfat on a USB M.2 drive at the weekend. I tripped over soft links:
> I keep a plain copy of /etc with the other tar files for ease of use, and
> of course the run-level entries are all links.
>
> Yes, permissions are fine, but special files are not - not soft links,
> anyway.
As I understand it neither FAT nor exFAT are POSIX-compatible and Linux
permissions will not translate across. Both will acquire the ownership of
whoever mounts the filesystem - e.g.:
- udisks/GUI will mount them under the ownership of the user executing the
mounting action in userspace;
- mount command on the CLI will mount them as root.
Any changed ACLs will not survive a remount.
ACLs are possible with NTFS, but they will not translate 1:1 with MSWindows.
I recall with the ntfs-3g driver you had to add a a file in the root
directory, or each subdirectory(?), to specify some basic access rights. I am
not sure how it works with the in-kernel driver today.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-25 17:02 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:58 [gentoo-user] m.2 nvme stick not what I was expecting at all Dale
2025-02-24 19:20 ` Jack
2025-02-24 19:49 ` Dale
2025-02-24 19:40 ` Mark Knecht
2025-02-24 19:41 ` Rich Freeman
2025-02-24 19:53 ` Dale
2025-02-24 20:00 ` Rich Freeman
2025-02-24 20:34 ` Dale
2025-02-24 20:02 ` eric
2025-02-24 20:11 ` Mark Knecht
2025-02-24 20:44 ` Dale
2025-02-24 22:48 ` Frank Steinmetzger
2025-02-25 3:56 ` Dale
2025-02-25 10:08 ` Michael
2025-02-25 11:00 ` Dale
2025-02-25 11:16 ` Michael
2025-02-25 15:57 ` Dale
2025-02-25 17:05 ` Rich Freeman
2025-02-25 19:00 ` Michael
2025-02-25 19:18 ` Rich Freeman
2025-02-25 20:39 ` Michael
2025-02-25 22:16 ` Frank Steinmetzger
2025-02-25 14:48 ` Peter Humphrey
2025-02-25 17:00 ` Michael [this message]
2025-02-24 22:13 ` Frank Steinmetzger
2025-02-25 4:20 ` Dale
2025-02-25 8:18 ` Wols Lists
2025-02-25 14:07 ` [gentoo-user] " Grant Edwards
2025-02-25 8:20 ` [gentoo-user] " Wols Lists
2025-02-25 11:09 ` Dale
2025-02-25 12:26 ` Dale
2025-02-25 15:04 ` Rich Freeman
2025-02-25 15:32 ` Dale
2025-02-25 16:29 ` Rich Freeman
2025-02-25 17:26 ` Dale
2025-02-25 17:41 ` Rich Freeman
2025-02-26 14:43 ` Dale
2025-02-26 16:38 ` Michael
2025-02-26 20:34 ` Dale
2025-02-26 20:48 ` Mark Knecht
2025-02-25 20:19 ` Wol
2025-02-25 20:21 ` Michael
2025-02-25 21:34 ` Frank Steinmetzger
2025-02-26 7:52 ` Wols Lists
2025-02-26 16:44 ` Michael
2025-02-26 18:03 ` Wol
2025-02-26 18:05 ` Rich Freeman
2025-02-26 18:42 ` Wol
2025-02-26 19:26 ` Rich Freeman
2025-02-26 19:47 ` Wols Lists
2025-02-26 19:56 ` Rich Freeman
2025-02-26 21:25 ` Wol
2025-02-26 22:37 ` Michael
2025-02-26 16:41 ` Michael
2025-02-28 5:43 ` Dale
2025-02-28 16:40 ` [gentoo-user] " Grant Edwards
2025-03-02 16:01 ` Dale
2025-03-02 22:06 ` Frank Steinmetzger
2025-03-02 22:39 ` Dale
2025-03-03 3:01 ` Grant Edwards
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=2301845.iZASKD2KPV@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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