Received, thanks.
I'm used to hack on three devices one OpenBSD, one Mac and the tablet so the
FAT is useful and always the last resort. However yes ext2 it could be an idea.
However get OpenBSD improved is always my favorite option.
-- Nowarez Market
Dec 5, 2023 19:25:55 Noth :
> Have you tr
Hello,
Have you tried mounting with the -l flag? Otherwise I'd recommend
using ext2fs instead of FAT32. Android will handle it natively, and
OpenBSD can mount that read/write (on a sdXi mountpoint, like FAT32).
Cheers,
Noth
On 05/12/2023 16:46, Nowarez Market wrote:
:-)
so what is techi
People have already explained to you
that 8 + 1 + 3 is less than 255.
Can you kindly shut the fuck up already?
On Dec 05 13:59:11, my2...@has.im wrote:
> Thanks for the reply.
>
> Absolutely perceived, I haven't counted them. But I counted the 8.3 format
> for true:
> all the info contained in
On Tue, 5 Dec 2023 16:46:38 +0100 (GMT+01:00), Nowarez Market wrote:
> so what is techinal explanation of the happening and the cut off to 8.3 ?
Well, for the given title, 8.3 yields:
"Tcl_Tk 8.5 P", but I imagine, for this case, that what it might do is
see an eight character filename and a dot
You are fantastic. Next thread I will take you also the 8.3 filename examples
with screenshots of the last three chars.
( don't stop to report guys! )
-- Nowarez Market
Dec 5, 2023 17:16:32 Amelia A Lewis :
> Have you, perhaps, misdiagnosed
> the problem?
-- Nowarez Market
:-)
so what is techinal explanation of the happening and the cut off to 8.3 ?
-- Nowarez Market
Dec 5, 2023 14:48:49 Anders Andersson :
> $ echo "Tcl_Tk 8.5 Programming Cookbook -- Bert Wheeler -- 2011 --
> Packt -- 9781849512992 -- 9ed273d2c640e4ae4761242a2c28d31c -- Capitan
> Cloud Ebook Repo
On Tue, Dec 5, 2023 at 2:01 PM Nowarez Market wrote:
>
> Thanks for the reply.
>
> Absolutely perceived, I haven't counted them. But I counted the 8.3 format
> for true:
> all the info contained in my ebook title was lost (but experimenting it is no
> problem).
>
> Now I checked better. Indeed i
Thanks for the reply.
Absolutely perceived, I haven't counted them. But I counted the 8.3 format for
true:
all the info contained in my ebook title was lost (but experimenting it is no
problem).
Now I checked better. Indeed it is Opera web browser that is able to save on
Android 11 exceeding
t
On Mon, Dec 4, 2023 at 12:03 PM Michael Hekeler wrote:
>
> > > To be honest I don't understand the problem you described.
> >
> > It is simple, when you come from Android (tested Android 11 tablet) with
> > file names exceeding the FAT spec
> > these are cut to 8.3 format in OpenBSD.
>
>
> You me
I limit myself to report the problem of my system. And the problem of OpenBSD in
this case is the easie to let me lose the info contained in the filenames
coming from Android.
Then the fix doesn't depend on my attitude.
== Nowarez Market
Dec 4, 2023 11:59:23 Michael Hekeler :
>>> To be honest
> > To be honest I don't understand the problem you described.
>
> It is simple, when you come from Android (tested Android 11 tablet) with file
> names exceeding the FAT spec
> these are cut to 8.3 format in OpenBSD.
You mean android allows to create filenames >255 on FAT32?
Then you should re
Michael Hekeler :
> To be honest I don't understand the problem you described.
It is simple, when you come from Android (tested Android 11 tablet) with file
names exceeding the FAT spec
these are cut to 8.3 format in OpenBSD. Android doesn't give any hint on the
situation because it is somewhat
>
> There is also some ironic stuff behind these happenings: if you have
> the possibility to check your lost long file names you will discover
> that the most significant information are contained in the first 99 chars.
>
>
> Nowarez Market wrote:
>
> >
> > Clearly the problem is that from t
There is also some ironic stuff behind these happenings: if you have
the possibility to check your lost long file names you will discover
that the most significant information are contained in the first 99 chars.
Nowarez Market wrote:
>
> Clearly the problem is that from the user prospective
Clearly the problem is that from the user prospective in these kind
of events all the information contained in the longer file names are
lost.
A file copy from Android is always completely transparent to the user,
anyhow. Android open behavior "doesn't help" copping with these long
names: if I
Hello,
I have a fat32 usb stick that I use to transfer files
from/to my Android tablet since years.
I just want to drop the hint that Android manage
to render the file names exceeding 255 chars offering
the user the long form anyway while OpenBSD strictly
apply the FAT specs rendering these file
16 matches
Mail list logo
