public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Memory cards and deleting files.
Date: Mon, 22 Jun 2020 08:19:28 -0500	[thread overview]
Message-ID: <a2e39e7e-0a16-1ffc-fd16-5a16f82ca7a6@gmail.com> (raw)
In-Reply-To: <20200622121212.66b9603b@digimed.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

Neil Bothwick wrote:
> On Mon, 22 Jun 2020 06:56:43 -0400, Walter Dnes wrote:
>
>>> The SD standard says >33G should use exFAT, this is why many devices
>>> state they only support cards up to 32G. The really mean they only
>>> support FAT. My Dashcam is like this but it happily works with a 128G
>>> card, once I reformatted it with FAT.  
>>   Warning; that still does not change the fact that each individual file
>> cannot exceed 4G in size on regular FAT.
> That's right, but a device designed to work with only FAT should never
> try to save larger files. Any such devices I have used tend to split
> videos into chunks of 1GB or smaller.
>
>


So if I bought a 64GB card, I forced it to be formatted with FAT on say
my Linux box here, it would work in my trail cameras anyway?  It makes
sense.  It would seem it is more of a file system issue since accessing
a device shouldn't be affected my its capacity, well, maybe some
exceptions.  My trail camera may only support FAT which is only found on
32GB and smaller.  I can get that. 

To be honest, even tho I leave that thing out there sometimes for months
without checking it, and it takes a ton of pics, I don't recall it even
going over a couple GBs or so.  Even the one that takes videos doesn't
store a lot of data.  I don't think I'd buy that expensive a card but
still, interesting that it is a option.  I'm thinking even my Canon
camera can handle this.  That's a lot of pics tho. 

I never thought about this this way. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2136 bytes --]

  reply	other threads:[~2020-06-22 13:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 17:09 [gentoo-user] Memory cards and deleting files Dale
2020-06-20 22:14 ` Neil Bothwick
2020-06-20 23:08   ` Wols Lists
2020-06-20 23:11     ` Michael
2020-06-20 23:26       ` Wols Lists
2020-06-21 11:52         ` Michael
2020-06-22 10:28           ` Neil Bothwick
2020-06-22 10:56             ` Walter Dnes
2020-06-22 11:12               ` Neil Bothwick
2020-06-22 13:19                 ` Dale [this message]
2020-06-22 13:46                   ` Neil Bothwick
2020-06-22 15:04                     ` Dale
2020-06-22 18:25                   ` antlists
2020-06-22 18:50                     ` Dale
2020-06-22 19:34                       ` antlists
2020-06-22 20:35                         ` Dale
2020-06-22 18:25               ` antlists
2020-06-22 18:52                 ` Dale
2020-06-22 19:22                 ` Neil Bothwick
2020-06-22 19:40                   ` antlists
2020-06-22 20:42                     ` Neil Bothwick
2020-06-23 15:49                       ` antlists
2020-06-21 12:23       ` Dale
2020-06-21 12:32 ` Franz Fellner
2020-06-21 14:21   ` Dale
2020-06-21 14:50     ` Franz Fellner
2020-06-21 16:17       ` John Covici
2020-06-21 16:55         ` Dale
2020-06-22 10:30         ` Neil Bothwick
2020-06-22 13:47           ` [gentoo-user] " 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=a2e39e7e-0a16-1ffc-fd16-5a16f82ca7a6@gmail.com \
    --to=rdalek1967@gmail.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