Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #181812 > unrolled thread
| Started by | Marion <marion@facts.com> |
|---|---|
| First post | 2025-01-31 17:48 +0000 |
| Last post | 2025-02-02 22:54 +0000 |
| Articles | 20 on this page of 166 — 15 participants |
Back to article view | Back to alt.comp.os.windows-10
Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-01-31 17:48 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-01-31 19:09 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 19:26 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-01-31 21:18 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-01-31 23:19 +0100
The "label" command (Was: Clever helpful suggestion for portable memory using Windows &) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:24 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-01-31 22:25 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:38 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-01-31 23:39 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:48 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Quincy the fifth <quincythefifth@telekom.net> - 2025-02-01 00:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 06:03 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-02-01 10:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:45 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:51 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 00:07 +1000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-04-26 21:37 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:23 +1000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-04-27 14:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 14:55 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 19:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 20:54 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:21 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 14:43 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 00:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 01:59 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:06 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-03 13:28 +0100
What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-03 13:09 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 14:34 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors knuttle <keith_nuttle@yahoo.com> - 2025-02-03 10:47 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:30 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Newyana2 <newyana@invalid.nospam> - 2025-02-03 15:15 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:25 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Newyana2 <newyana@invalid.nospam> - 2025-02-05 09:32 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 20:46 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:39 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Paul <nospam@needed.invalid> - 2025-02-03 15:42 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 22:40 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:45 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-04 15:41 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:18 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:05 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Paul <nospam@needed.invalid> - 2025-02-05 20:04 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:17 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 21:02 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:47 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:28 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-08 10:18 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 23:35 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-10 08:47 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-10 10:55 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-11 01:00 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-13 19:59 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-13 22:15 +0000
[OT] Storage technology "back then" (was Re: What is an animal or an SSD drive? [...]) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-14 02:10 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-18 11:56 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-18 21:55 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-21 09:12 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-21 23:35 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-25 18:27 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-25 18:25 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:53 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 13:10 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-26 15:02 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-25 20:28 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:54 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:49 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-21 14:12 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:27 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-27 10:29 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 04:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 05:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 06:05 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 21:34 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 00:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 09:42 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:54 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-08 04:22 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:07 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 23:42 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 02:21 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:05 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 09:59 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 19:12 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:30 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 11:31 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 14:27 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 14:35 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:21 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-06 23:58 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 05:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 10:30 +0100
Editing binary data with editors - or is there no difference of text and binary? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-07 10:57 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 11:44 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-07 14:39 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 19:39 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:26 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 18:12 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 23:14 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:50 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:27 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:21 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:07 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:20 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 05:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-01 16:34 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-01 16:29 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:10 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 15:44 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 10:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 15:14 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-04 10:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-04 13:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-04 19:51 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-04 23:12 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 15:24 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:50 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 16:04 +0100
[meta] posting mistake Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 16:26 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-02 16:29 +0000
ext4 on Android (Was: blah, blah, blah...) gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-02 16:37 +0000
Re: ext4 on Android (Was: blah, blah, blah...) Jeff Layman <Jeff@invalid.invalid> - 2025-02-03 09:14 +0000
ext4 on Android (Was: blah, blah, blah...) "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 15:16 +0100
Re: ext4 on Android (Was: blah, blah, blah...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:59 +0000
Re: ext4 on Android Frank Slootweg <this@ddress.is.invalid> - 2025-02-04 10:23 +0000
Re: ext4 on Android (Was: blah, blah, blah...) Marion <marion@facts.com> - 2025-02-04 22:48 +0000
Re: ext4 on Android (Was: blah, blah, blah...) "Carlos E.R." <robin_listas@es.invalid> - 2025-02-25 23:16 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-03 19:00 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 22:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-05 18:50 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-05 14:26 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-06 20:50 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-03 19:58 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-04 01:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-04 00:24 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-04 21:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-04 22:11 +0000
External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 02:24 +0100
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-04 22:06 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 04:41 +0000
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 04:43 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 02:10 -0500
Re: External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 17:40 +0100
Re: External media file systems (was Re: ...) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-05 18:50 +0000
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:11 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 20:59 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 03:04 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 22:48 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 21:00 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-06 16:20 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 22:42 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-07 00:44 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 06:00 +0000
Re: External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 17:38 +0100
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:06 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:56 +0000
A little bit of discussion between Janis and me (Was: Stupid suggestion(s) for "portable" "memory" using Windows & Android "editors") gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-02 14:53 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 20:59 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 22:54 +0000
Page 7 of 9 — ← Prev page 1 2 3 4 5 6 [7] 8 9 Next page →
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-02 15:24 +0100 |
| Message-ID | <vnnv7i$nmrk$1@dont-email.me> |
| In reply to | #181862 |
On 01.02.2025 17:29, Kenny McCormack wrote: > In article <vnletd$5l96$1@dont-email.me>, > Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote: > ... >> (I probably shouldn't engage in this thread - and not only because it >> got aggressive recently - because it seems (partly?) a Windows issue, >> given the mention of 'C:', 'D:' and such crap later in this thread; >> but I'm curious...) > > Calling drive letters "crap" isn't "aggressive" ? I wouldn't think so, but maybe we have a different view on that. What I meant and was addressing was the _ad hominem_ aggressivity. (It wouldn't have occurred to me that calling a technical mis-design "crap" would be considered aggressive.) I think that personal "Die fucking troll, Die." [from "Quincy the fifth"] is something vastly different than "Feature C: D: is crap." > > Anyway, given that this is a cross-posted thread, it would be useful to > know from which group you are reading/responding. I often give this info > myself when responding to cross-posts. > > My guess it that, like me, you are reading in comp.editors. The point of > this observation is that this thread (whatever it does eventually turn out > to really be about) is really more of an Android/Windows thing, and is only > tangentially related to editors. If you're coming from a primarily Unix > (aka, Linux) background, a lot of it will look weird. I don't understand > it myself, but I am inferring (just from reading this thread) that there > are weirdnesses in both Android and Windows that give rise to the issues > that Arlen is trying to address. > > Neither you nor I are familiar with these weirdnesses and problems, because > we both come primarily from Unix/Linux backgrounds - where such things > simply don't exist. Well, I worked in the past also in DOS and Windows environments. And I seem to recall that there were some sorts/variant of "links" available (but I might be misremembering). And Android is a Linux (Unix) based OS so I'd expect that such primitive and basic mechanisms are nor removed from this OS. But I don't know; so if it's not applicable readers may just dismiss my hint. Janis
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-02-02 15:50 +0100 |
| Message-ID | <9ad47lx1dr.ln2@Telcontar.valinor> |
| In reply to | #181893 |
On 2025-02-02 15:24, Janis Papanagnou wrote: > On 01.02.2025 17:29, Kenny McCormack wrote: >> In article <vnletd$5l96$1@dont-email.me>, >> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote: >> ... >>> (I probably shouldn't engage in this thread - and not only because it >>> got aggressive recently - because it seems (partly?) a Windows issue, >>> given the mention of 'C:', 'D:' and such crap later in this thread; >>> but I'm curious...) >> >> Calling drive letters "crap" isn't "aggressive" ? > > I wouldn't think so, but maybe we have a different view on that. What I > meant and was addressing was the _ad hominem_ aggressivity. (It wouldn't > have occurred to me that calling a technical mis-design "crap" would be > considered aggressive.) Some people do. I was called to attention and maybe banned from a Linux forum for such an opinion. I assume because developers and packagers are part of the community, and calling a software crap is insulting the developer who might be reading and is working gratis. > I think that personal "Die fucking troll, Die." > [from "Quincy the fifth"] is something vastly different than "Feature > C: D: is crap." > >> >> Anyway, given that this is a cross-posted thread, it would be useful to >> know from which group you are reading/responding. I often give this info >> myself when responding to cross-posts. >> >> My guess it that, like me, you are reading in comp.editors. The point of >> this observation is that this thread (whatever it does eventually turn out >> to really be about) is really more of an Android/Windows thing, and is only >> tangentially related to editors. If you're coming from a primarily Unix >> (aka, Linux) background, a lot of it will look weird. I don't understand >> it myself, but I am inferring (just from reading this thread) that there >> are weirdnesses in both Android and Windows that give rise to the issues >> that Arlen is trying to address. >> >> Neither you nor I are familiar with these weirdnesses and problems, because >> we both come primarily from Unix/Linux backgrounds - where such things >> simply don't exist. > > Well, I worked in the past also in DOS and Windows environments. And I > seem to recall that there were some sorts/variant of "links" available > (but I might be misremembering). And Android is a Linux (Unix) based OS > so I'd expect that such primitive and basic mechanisms are nor removed > from this OS. But I don't know; so if it's not applicable readers may > just dismiss my hint. Android is *nix based, yes, but uses an MsDOS filesystem (FAT). -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-02 16:04 +0100 |
| Message-ID | <vno1hv$o4le$1@dont-email.me> |
| In reply to | #181895 |
On 02.02.2025 15:50, Carlos E.R. wrote: > On 2025-02-02 15:24, Janis Papanagnou wrote: >> On 01.02.2025 17:29, Kenny McCormack wrote: >>> In article <vnletd$5l96$1@dont-email.me>, >>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote: >>> ... >>>> (I probably shouldn't engage in this thread - and not only because it >>>> got aggressive recently - because it seems (partly?) a Windows issue, >>>> given the mention of 'C:', 'D:' and such crap later in this thread; >>>> but I'm curious...) >>> >>> Calling drive letters "crap" isn't "aggressive" ? >> >> I wouldn't think so, but maybe we have a different view on that. What I >> meant and was addressing was the _ad hominem_ aggressivity. (It wouldn't >> have occurred to me that calling a technical mis-design "crap" would be >> considered aggressive.) That is understandable. - Though the guy who invented the "device letters" concept (40+ years ago!) probably doesn't mind (anymore) even if he'd take that (unjustified) as _personal_ offense, which it obviously isn't. > > Some people do. I was called to attention and maybe banned from a Linux > forum for such an opinion. I assume because developers and packagers are > part of the community, and calling a software crap is insulting the > developer who might be reading and is working gratis. Valuing a complete software package is again another thing. (Yet, still not a personal thing.) >> [...] > > Android is *nix based, yes, but uses an MsDOS filesystem (FAT). Yes, I know. For some reasons inferiors concepts are invented and they also don't die once they've got widely spread. Janis
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-02 16:26 +0100 |
| Subject | [meta] posting mistake |
| Message-ID | <vno2rh$ocjc$1@dont-email.me> |
| In reply to | #181897 |
(Sorry, I misplaced my answer to the quote wrongly above the text in my previous post. - Hope the intention was clear anyway.)
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-02-02 16:29 +0000 |
| Message-ID | <vnoa2f.qag.1@ID-201911.user.individual.net> |
| In reply to | #181897 |
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
> On 02.02.2025 15:50, Carlos E.R. wrote:
[...]
> > Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>
> Yes, I know. For some reasons inferiors concepts are invented and
> they also don't die once they've got widely spread.
To be clear, Android's native filesystem is not FAT (but ext4), but if
you use a (Micro)SD-card in an Android device (which is partly the
subject of this ... ahem ... 'thread'), then the filesystem on that card
is FAT (assuming it's not used as an extension of Internal Storage
('disk' space)).
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-02-02 16:37 +0000 |
| Subject | ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <vno70l$3oqv3$1@news.xmission.com> |
| In reply to | #181900 |
In article <vnoa2f.qag.1@ID-201911.user.individual.net>,
Frank Slootweg <this@ddress.is.invalid> wrote:
>Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
>> On 02.02.2025 15:50, Carlos E.R. wrote:
>[...]
>
>> > Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>>
>> Yes, I know. For some reasons inferiors concepts are invented and
>> they also don't die once they've got widely spread.
>
> To be clear, Android's native filesystem is not FAT (but ext4), but if
>you use a (Micro)SD-card in an Android device (which is partly the
>subject of this ... ahem ... 'thread'), then the filesystem on that card
>is FAT (assuming it's not used as an extension of Internal Storage
>('disk' space)).
Yes, all true. Interestingly, at least the one time I tested this, when I
formatted an SD card to ext4, then inserted it into a phone, it did not
recognize it. Odd, because obviously, it *can* recognized ext4
filesystems. But it only seems to be able to do FAT on the SD card.
--
"Only a genius could lose a billion dollars running a casino."
"You know what they say: the house always loses."
"When life gives you lemons, don't pay taxes."
"Grab 'em by the p***y!"
[toc] | [prev] | [next] | [standalone]
| From | Jeff Layman <Jeff@invalid.invalid> |
|---|---|
| Date | 2025-02-03 09:14 +0000 |
| Subject | Re: ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <vnq1cr$15n0f$2@dont-email.me> |
| In reply to | #181901 |
On 02/02/2025 16:37, Kenny McCormack wrote:
> In article <vnoa2f.qag.1@ID-201911.user.individual.net>,
> Frank Slootweg <this@ddress.is.invalid> wrote:
>> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
>>> On 02.02.2025 15:50, Carlos E.R. wrote:
>> [...]
>>
>>>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>>>
>>> Yes, I know. For some reasons inferiors concepts are invented and
>>> they also don't die once they've got widely spread.
>>
>> To be clear, Android's native filesystem is not FAT (but ext4), but if
>> you use a (Micro)SD-card in an Android device (which is partly the
>> subject of this ... ahem ... 'thread'), then the filesystem on that card
>> is FAT (assuming it's not used as an extension of Internal Storage
>> ('disk' space)).
>
> Yes, all true. Interestingly, at least the one time I tested this, when I
> formatted an SD card to ext4, then inserted it into a phone, it did not
> recognize it. Odd, because obviously, it *can* recognized ext4
> filesystems. But it only seems to be able to do FAT on the SD card.
Interesting. I didn't know about the FAT/ext4 file system issue.
Seems the latest high-capacity cards (SDXC, SDUC) use exFAT
(<https://en.wikipedia.org/wiki/SD_card>). Actually, SDXC cards have
been around for quite a time; those should be recognisable in a phone.
What make/age of phone was yours?
--
Jeff
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-02-03 15:16 +0100 |
| Subject | ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <anv67lxvvv.ln2@Telcontar.valinor> |
| In reply to | #181900 |
On 2025-02-02 17:29, Frank Slootweg wrote:
> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
>> On 02.02.2025 15:50, Carlos E.R. wrote:
> [...]
>
>>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>>
>> Yes, I know. For some reasons inferiors concepts are invented and
>> they also don't die once they've got widely spread.
>
> To be clear, Android's native filesystem is not FAT (but ext4), but if
> you use a (Micro)SD-card in an Android device (which is partly the
> subject of this ... ahem ... 'thread'), then the filesystem on that card
> is FAT (assuming it's not used as an extension of Internal Storage
> ('disk' space)).
Are you sure it is ext4?
On old phones, when connected to computer, the internal storage was
taken over directly by the computer, and it did appear to be FAT.
--
Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-03 21:59 +0000 |
| Subject | Re: ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <vnre8s$1fpir$3@dont-email.me> |
| In reply to | #181928 |
On Mon, 3 Feb 2025 15:16:42 +0100, Carlos E.R. wrote: > On old phones, when connected to computer, the internal storage was > taken over directly by the computer, and it did appear to be FAT. You’re thinking MTP. My old phone supports that as well. It’s a file-level protocol, so it doesn’t expose the internal storage at the sector level. My even older phone let the microSD card be accessed by an external computer directly at the sector level. That was in FAT format, but it was separate from the phone’s internal storage. No Android phone is going to expose its OS installation area for any external access at the sector level.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-02-04 10:23 +0000 |
| Subject | Re: ext4 on Android |
| Message-ID | <vnstb7.12cs.1@ID-201911.user.individual.net> |
| In reply to | #181928 |
> On 2025-02-02 17:29, Frank Slootweg wrote:
> > Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
> >> On 02.02.2025 15:50, Carlos E.R. wrote:
> > [...]
> >
> >>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
> >>
> >> Yes, I know. For some reasons inferiors concepts are invented and
> >> they also don't die once they've got widely spread.
> >
> > To be clear, Android's native filesystem is not FAT (but ext4), but if
> > you use a (Micro)SD-card in an Android device (which is partly the
> > subject of this ... ahem ... 'thread'), then the filesystem on that card
> > is FAT (assuming it's not used as an extension of Internal Storage
> > ('disk' space)).
>
> Are you sure it is ext4?
Not really sure, but that's the most common answer when you do a
Google search. I found it strange that the Wikipedia page on Android
doesn't seem to mention its native filesystem. I've seen an official
reference about which filesystems it supports [1], but not which one it
uses.
So if someone has an official reference as to which filesystem
Android uses, i.e. its native filesystem, that would be nice.
> On old phones, when connected to computer, the internal storage was
> taken over directly by the computer, and it did appear to be FAT.
I think that was a virtual filesystem layer, i.e. presenting the
native filesystem as an FAT filesystem, so that could be accessed by the
outside world, because the outside world, especially Windows, could not
generally handle anything other than FAT.
[1]
<https://source.android.com/docs/core/architecture/android-kernel-file-system-support>
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-02-04 22:48 +0000 |
| Subject | Re: ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <vnu5go$10k3$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #181928 |
On Mon, 3 Feb 2025 15:16:42 +0100, Carlos E.R. wrote :
>>>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>>>
>>> Yes, I know. For some reasons inferiors concepts are invented and
>>> they also don't die once they've got widely spread.
>>
>> To be clear, Android's native filesystem is not FAT (but ext4), but if
>> you use a (Micro)SD-card in an Android device (which is partly the
>> subject of this ... ahem ... 'thread'), then the filesystem on that card
>> is FAT (assuming it's not used as an extension of Internal Storage
>> ('disk' space)).
>
> Are you sure it is ext4?
>
> On old phones, when connected to computer, the internal storage was
> taken over directly by the computer, and it did appear to be FAT.
I just looked it up, and I'm more confused after doing so than before.
<https://developer.android.com/training/data-storage>
The section on Data and file storage doesn't explicitly state "the" native
Android file system, it implies that ext4 and f2fs are core to the system
due to their use in internal storage and system partitions.
That sounded good until I found descriptions of the kernel code, which
ultimately dictates file system support but it requires technical expertise
to make sense of - which I don't have.
<https://www.google.com/search?q=https://source.android.com/docs/core/architecture/filesystems>
It seems maybe perhaps Android uses different file systems for different
purposes (i.e., perhaps for system, data, cache, or external storage)???
I'm more confused now than before I looked it up, so if anyone can make
sense of those two references, please let the rest of us in on the secret.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-02-25 23:16 +0100 |
| Subject | Re: ext4 on Android (Was: blah, blah, blah...) |
| Message-ID | <m3s19lxun3.ln2@Telcontar.valinor> |
| In reply to | #181974 |
On 2025-02-04 23:48, Marion wrote:
> On Mon, 3 Feb 2025 15:16:42 +0100, Carlos E.R. wrote :
>
>
>>>>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT).
>>>>
>>>> Yes, I know. For some reasons inferiors concepts are invented and
>>>> they also don't die once they've got widely spread.
>>>
>>> To be clear, Android's native filesystem is not FAT (but ext4),
>>> but if
>>> you use a (Micro)SD-card in an Android device (which is partly the
>>> subject of this ... ahem ... 'thread'), then the filesystem on that card
>>> is FAT (assuming it's not used as an extension of Internal Storage
>>> ('disk' space)).
>>
>> Are you sure it is ext4?
>>
>> On old phones, when connected to computer, the internal storage was
>> taken over directly by the computer, and it did appear to be FAT.
>
> I just looked it up, and I'm more confused after doing so than before.
> <https://developer.android.com/training/data-storage>
This link describes features the filesystem must have, but they don't
say which filesystem they use. Thus it can be "something else".
>
> The section on Data and file storage doesn't explicitly state "the" native
> Android file system, it implies that ext4 and f2fs are core to the system
> due to their use in internal storage and system partitions.
>
> That sounded good until I found descriptions of the kernel code, which
> ultimately dictates file system support but it requires technical expertise
> to make sense of - which I don't have. <https://www.google.com/search?
> q=https://source.android.com/docs/core/architecture/filesystems>
>
> It seems maybe perhaps Android uses different file systems for different
> purposes (i.e., perhaps for system, data, cache, or external storage)???
>
> I'm more confused now than before I looked it up, so if anyone can make
> sense of those two references, please let the rest of us in on the secret.
<https://source.android.com/docs/core/architecture/android-kernel-file-system-support>
says they support these:
exfat (supported in kernel 5.10 and later)
ext4
f2fs
fuse
incfs
Vfat
EROFS
I'm guessing the choice is up to the manufacturer.
--
Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-03 21:57 +0000 |
| Message-ID | <vnre3s$1fpir$2@dont-email.me> |
| In reply to | #181900 |
I’m sure you can format an SD card or USB stick with a Linux-native filesystem like ext4, stick it into your Android device, and have it recognized.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-02-03 19:00 +0000 |
| Message-ID | <slrnvq242k.3cd70.candycanearter07@candydeb.host.invalid> |
| In reply to | #181897 |
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote at 15:04 this Sunday (GMT): > On 02.02.2025 15:50, Carlos E.R. wrote: [snip] >> Android is *nix based, yes, but uses an MsDOS filesystem (FAT). > > Yes, I know. For some reasons inferiors concepts are invented and > they also don't die once they've got widely spread. > > Janis It's hard to stop momentum, sometimes. Windows refusing to switch to a different FS for external medium also doesn't help. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-03 22:01 +0000 |
| Message-ID | <vnrebh$1fpir$4@dont-email.me> |
| In reply to | #181930 |
On Mon, 3 Feb 2025 19:00:02 -0000 (UTC), candycanearter07 wrote: > It's hard to stop momentum, sometimes. Windows refusing to switch to a > different FS for external medium also doesn't help. The problems are all with the inflexibility of Windows itself. Instead of having a pluggable VFS layer that is agnostic to different filesystem formats, Linux-style, too many of its filesystem features are specifically tied to one filesystem format, namely NTFS.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-02-05 18:50 +0000 |
| Message-ID | <slrnvq7cjr.1u0ps.candycanearter07@candydeb.host.invalid> |
| In reply to | #181938 |
Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 22:01 this Monday (GMT): > On Mon, 3 Feb 2025 19:00:02 -0000 (UTC), candycanearter07 wrote: > >> It's hard to stop momentum, sometimes. Windows refusing to switch to a >> different FS for external medium also doesn't help. > > The problems are all with the inflexibility of Windows itself. Instead of > having a pluggable VFS layer that is agnostic to different filesystem > formats, Linux-style, too many of its filesystem features are specifically > tied to one filesystem format, namely NTFS. Yeah, and then making the OS reliant on those systems. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-02-05 14:26 -0500 |
| Message-ID | <vo0e0v$2h21c$1@dont-email.me> |
| In reply to | #182011 |
On Wed, 2/5/2025 1:50 PM, candycanearter07 wrote: > Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 22:01 this Monday (GMT): >> On Mon, 3 Feb 2025 19:00:02 -0000 (UTC), candycanearter07 wrote: >> >>> It's hard to stop momentum, sometimes. Windows refusing to switch to a >>> different FS for external medium also doesn't help. >> >> The problems are all with the inflexibility of Windows itself. Instead of >> having a pluggable VFS layer that is agnostic to different filesystem >> formats, Linux-style, too many of its filesystem features are specifically >> tied to one filesystem format, namely NTFS. > > > Yeah, and then making the OS reliant on those systems. > There have been cases made by Microsoft, where in the documentation it would claim a certain thing would only work on NTFS. And then an external dev would turn around and make it work on FAT32. Not every one of those declarations is for real. As for "every feature", the audience here are mostly desktop users and not server users. The server side has a few features we don't see here. I'm not in a position to give an authoritative overview of every filesystem nook and cranny. The OS has Windows Overlay File system, and that's a technique for saving space on a tablet (and its tiny eMMC storage). Paul Paul
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-06 00:16 +0000 |
| Message-ID | <vo0v03$2k46v$4@dont-email.me> |
| In reply to | #182012 |
On Wed, 5 Feb 2025 14:26:23 -0500, Paul wrote: > There have been cases made by Microsoft, where in the documentation it > would claim a certain thing would only work on NTFS. And then an > external dev would turn around and make it work on FAT32. Here’s one big one: every time I point out the old “Microsoft thinks 26 drive letters ought to be enough for anybody” limitation, someone tries to claim that Windows lets you use mount points instead of drive letters, *nix-style. But then it turns out that mount points are an NTFS-specific feature, that don’t work with other filesystems. > As for "every feature", the audience here are mostly desktop users and > not server users. The server side has a few features we don't see here. Then there are those of us that are workstation users. Remember workstations? Think of them as “desktops” with “server” features integrated. The “desktop”/“server” separation was created as a marketing stratagem by companies like Microsoft, deliberately crippling the “desktop” capabilities so they could squeeze extra revenue out of customers wanting “server” features. Such a distinction didn’t exist in the Unix world before Microsoft came along. And it doesn’t exist in the Linux world today.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-02-06 20:50 +0000 |
| Message-ID | <slrnvqa84m.t2vt.candycanearter07@candydeb.host.invalid> |
| In reply to | #182020 |
Lawrence D'Oliveiro <ldo@nz.invalid> wrote at 00:16 this Thursday (GMT): > On Wed, 5 Feb 2025 14:26:23 -0500, Paul wrote: > >> There have been cases made by Microsoft, where in the documentation it >> would claim a certain thing would only work on NTFS. And then an >> external dev would turn around and make it work on FAT32. > > Here’s one big one: every time I point out the old “Microsoft thinks 26 > drive letters ought to be enough for anybody” limitation, someone tries to > claim that Windows lets you use mount points instead of drive letters, > *nix-style. But then it turns out that mount points are an NTFS-specific > feature, that don’t work with other filesystems. I remember them being not worth the effort to do, since you had to do it every time you plugged in the drive. Then again, I haven't used Windows in a while, so I might be misremembering. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-02-03 19:58 -0500 |
| Message-ID | <vnroo1$1hv2k$1@dont-email.me> |
| In reply to | #181930 |
On Mon, 2/3/2025 2:00 PM, candycanearter07 wrote: > Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote at 15:04 this Sunday (GMT): >> On 02.02.2025 15:50, Carlos E.R. wrote: > [snip] >>> Android is *nix based, yes, but uses an MsDOS filesystem (FAT). >> >> Yes, I know. For some reasons inferiors concepts are invented and >> they also don't die once they've got widely spread. >> >> Janis > > > It's hard to stop momentum, sometimes. Windows refusing to switch to a > different FS for external medium also doesn't help. > On hardware, partition tables exist, to give a "hint" what subset of file systems might be involved. The 0x07 for example, might be NTFS/HPFS/ExFAT. You then have to look at the first sector in the partition, to determine what it is exactly. There weren't enough codes to go around, which is why the codes today, lack the precision they once had. On GPT, a partition type could be declared as a Basic Data Type, then you again have to check the header sector for the details. On Windows, you see the BLKID and the GUID. On Linux, the gdisk utility hides the GUID (ugly) string and shows you some fake (pseudo) codes, such as 0x0700 for a Basic Data Partition. But once you get into the GPT partition table with your hex editor, you'll see that the two entries do not involve "0x0700". Hardware devices do not need to have a partition table. You can lay a file system into a hardware device without one. Then the OS has to try all of its filesystem types, for a match on the header sector. SD cards have certain expectations of filesystems, based on what wears the SD the least. That's how FAT32 or ExFAT get on the card. Journaled filesystems are a non-preferred choice. Neither NTFS nor EXT4 are preferred for an SD. I don't know what the OS policy is, when the OS discovers a filesystem outside [FAT32, ExFAT]. FAT32 is needed because the devices could be larger ones. Maybe at some point in the past, an SD had a small enough capacity that FAT12 or FAT16 would work. You can use the "disktype" utility on Linux, to indicate what is on a hardware device. I use the Cygwin version of that utility on Windows for that purpose. sudo disktype /dev/sda disktype.exe /dev/sda # because it's Cygwin, it uses a non-Windows namespace I would take the SD out of my camera right now and run it, but it's just going to be a raw FAT32. My camera isn't new enough to know what ExFAT is. And you don't even *format* an SD on your desktop OS. If you're using it in a camera, it is the responsibility of a camera menu item to "format" inserted media. This ensures first and foremost, that the media works in the camera. The computer end has a lot more flexibility regarding access. But based on what cameras do to SD, there isn't going to be a problem mounting an SD that was formatted by the camera. The behavior could also change, depending on the device used. Maybe when a camera with an SD is plugged in, a different handler (PTP/MPT) handles the camera end, than when a USB stick with SD hole in it, presents an SD. These are experiments you can run, as an experienced forensic expert :-) Someone with a wider collection of hardware, can run these experiments for me. I don't have any MTP devices, I also don't have any smartphone to play with. Paul
[toc] | [prev] | [next] | [standalone]
Page 7 of 9 — ← Prev page 1 2 3 4 5 6 [7] 8 9 Next page →
Back to top | Article view | alt.comp.os.windows-10
csiph-web