Re: can't mount sdf1 in stretch, gparted claims its fat32

To: debian-user@lists.debian.org
Subject: Re: can't mount sdf1 in stretch, gparted claims its fat32
From: Michael Stone <mstone@debian.org>
Date: Tue, 4 Feb 2020 11:24:56 -0500
Message-id: <[🔎] b7d48b4a-476a-11ea-9b6a-00163eeb5320@msgid.mathom.us>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: <[🔎] 202002041106.10014.gheskett@shentel.net>
References: <[🔎] 202002031240.20085.gheskett@shentel.net> <[🔎] 202002040038.04226.gheskett@shentel.net> <[🔎] uo5ogg-is2.ln1@anthive.com> <[🔎] 202002041106.10014.gheskett@shentel.net>

On Tue, Feb 04, 2020 at 11:06:10AM -0500, Gene Heskett wrote:

Me too, so I usually label the permanent stuff at least. UUID's can and
will change for no detectable reason.

For those reading along or finding this in search results: no,filesystem UUIDs don't change for no detectable reason. Don't implementanything based on this theory.

Reply to:

Follow-Ups:
- Re: can't mount sdf1 in stretch, gparted claims its fat32
  - From: Greg Wooledge <wooledg@eeg.ccf.org>
- Why I don't like UUIDs (Re: can't mount sdf1 in stretch, gparted claims its fat32)
  - From: Stefan Monnier <monnier@iro.umontreal.ca>

References:
- can't mount sdf1 in stretch, gparted claims its fat32
  - From: Gene Heskett <gheskett@shentel.net>
- Re: can't mount sdf1 in stretch, gparted claims its fat32
  - From: Gene Heskett <gheskett@shentel.net>
- Re: can't mount sdf1 in stretch, gparted claims its fat32
  - From: songbird <songbird@anthive.com>
- Re: can't mount sdf1 in stretch, gparted claims its fat32
  - From: Gene Heskett <gheskett@shentel.net>

Prev by Date: systemd logging stopped
Next by Date: Re: can't mount sdf1 in stretch, gparted claims its fat32
Previous by thread: Re: can't mount sdf1 in stretch, gparted claims its fat32
Next by thread: Re: can't mount sdf1 in stretch, gparted claims its fat32
Index(es):
- Date
- Thread