Live data from Hacker News

Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

aruljohn.com

101–109 of 109 posts

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#101
post #11

Earlier quoted context omitted.

It would at least be nice if there was a way to keep apple users from shitting all over the filesystem with remote mounts and ds_store files. Perhaps by automatically unmounting if one is detected.

At least with Samba you can use the "veto files" and "delete veto files" global directives to deal with those, I personally use the following for veto files: /._*/.AppleDB/.AppleDouble/.AppleDesktop/:2eDS_Store/Network Trash Folder/Temporary Items/TheVolumeSettingsFolder/.@__thumb/.@__desc/:2e*/.@__qini/.Qsync/.@upload_cache/.qsync/.qsync_sn/.@qsys/.digest/ I understand that I may loose resource forks, but that isn't…

unfortunately this is mostly people ssh mounting.

I think I can probably write a ebpf rule to avoid writing them though. Or disconnect their sessions. Or modify the .DS_Store to change the finder background to something amusing.

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#102
post #72

The title seems misleading. These are not errors. They are simply warnings about extended attributes being ignored when extracting files, which seems completely fine to me, and creating the tar without those extended attributes has exactly the same outcome, but throws away the metadata at archive time instead of extraction time. Furthermore, this is not an Apple/macOS issue. The tool used is bsdtar, so it would also…

It's unfortunate there was never a standardization around how to print different "levels" of messages. Imagine how nice things could be if we had a standard system call for the equivalent of log level, early on!

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#103
post #15

Earlier quoted context omitted.

thumbs.db and those weird MS alternative stream files for recording origination. filesystem attributes are for decorating files with meaning. Anything else that attempts to use filesystems in "interesting" ways is silly. Apple and MS really ought to consider why they do this sort of fragile, idiosyncratic nonsense.

But... thumbs.db is precisely not an "attempt to use filesystems in "interesting" ways" — it's literally a just hidden file with previews stored in it. Storing the preview in the alternative stream of the file with the picture itself would be "an interesting way".

Put it in $ProgramData for system-wide usage or whatever the user version is for individuals.

A hidden file is exactly what I said initially - a daft local decoration. Instead of using a stream, this one uses an attribute instead.

Put your data where it makes sense on the filesystem but don't dump arbitrary databases of information on there utilizing filesystem attributes because that is incredibly fragile.

thumbs.db only makes sense if the client is Windows (and only from a particular version onwards, until it doesn't). In the real world (starting with my laptop, running Ubuntu) it does not make any sense at all and is just a pain.

I don't want to see your thumbs.db or your weird ~{temp office files} either. Why do you insist on crapping on my nice neat file system?

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#104

Earlier quoted context omitted.

But... thumbs.db is precisely not an "attempt to use filesystems in "interesting" ways" — it's literally a just hidden file with previews stored in it. Storing the preview in the alternative stream of the file with the picture itself would be "an interesting way".

And .DS_Store is just your folder level preferences in Finder. If you don’t use Finder they won’t be created

Yes. And truthfully, I try to remember to only ever navigate my project folders (particularly those under revision control) using command line and/or IDE folder views.

But eventually, for whatever reason, I use Finder to go looking into a directory structure and bam, now I have .DS_Store. gitignore takes care of it, I know, but still, it's annoying.

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#105

Earlier quoted context omitted.

Tar on linux will. e.g. selinux attrs and other xattrs. Open question, is it worth attempting to main these semantics between mac and linux.

No, I just assume apple will break the behavior when they want to.

I'm downvoted, but why you cowards.

Why is this assumption incorrect, apple have a long history of breaking away from standards when it doesn't suit them.

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#106
post #85

Earlier quoted context omitted.

Agreed, but why not just finishing setting it up? Or do people own Apple TVs without iPhones? That never occurred to me since a large part of the value prop is phone integration

What integrations do you use? I can't really think of what I would miss on the Apple TV if I switched from iPhone. I rarely use AirPlay, disable Photos for in-house privacy reasons, and… oh yeah, the remote control for keyboard, volume, and navigation via iPhone is neat! I think the Apple TV is just a strong product on its own.

I use screen mirroring, a lot. Guess I’m in the minority around here. Really nice projecting your phone on a massive OLED to multitask on the phone. Or even pair programming and conference calls you can mirror the phone to TV for the call while coding on the laptop.

I use my Apple TV like it’s a big iPad stuck to the wall. Because that’s basically what it is. I honestly had no idea so many people just buy it to stream the same content on every other platform

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#107

Earlier quoted context omitted.

But... thumbs.db is precisely not an "attempt to use filesystems in "interesting" ways" — it's literally a just hidden file with previews stored in it. Storing the preview in the alternative stream of the file with the picture itself would be "an interesting way".

Put it in $ProgramData for system-wide usage or whatever the user version is for individuals. A hidden file is exactly what I said initially - a daft local decoration. Instead of using a stream, this one uses an attribute instead. Put your data where it makes sense on the filesystem but don't dump arbitrary databases of information on there utilizing filesystem attributes because that is incredibly fragile. thumbs.db…

> Put your data where it makes sense on the filesystem

Right near the data it's derived from is the most obvious place, you know, and makes sense for most of the application developers (it may not "make sense" for you but so what).

> Why do you insist on crapping on my nice neat file system?

"Your" neat file system? What a quaint notion. Two thirds of the hierarchy inside of your $HOME belongs to the OS you use and the tools you use (not "your OS" and "your tools" — just because you use something doesn't make it yours, you know). Your data is yours, of course, but the disk space belongs to the system harness first, and to you second, and the same applies to the file and directory organization.

Or at least that seems to be the prevailing attitude of most of the software.

> thumbs.db only makes sense if the client is Windows (and only from a particular version onwards, until it doesn't). In the real world (starting with my laptop, running Ubuntu) it does not make any sense at all and is just a pain.

Wait, didn't Nautilus use to read thumbs.db if it was present in the folder? Or am I thinking of some other file manager?

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#108

Earlier quoted context omitted.

No, I just assume apple will break the behavior when they want to.

I'm downvoted, but why you cowards. Why is this assumption incorrect, apple have a long history of breaking away from standards when it doesn't suit them.

[flagged]

Re: Tar Files Created on macOS Display Errors When Extracting on Linux (2024)

#109
post #85

Earlier quoted context omitted.

What integrations do you use? I can't really think of what I would miss on the Apple TV if I switched from iPhone. I rarely use AirPlay, disable Photos for in-house privacy reasons, and… oh yeah, the remote control for keyboard, volume, and navigation via iPhone is neat! I think the Apple TV is just a strong product on its own.

I use screen mirroring, a lot. Guess I’m in the minority around here. Really nice projecting your phone on a massive OLED to multitask on the phone. Or even pair programming and conference calls you can mirror the phone to TV for the call while coding on the laptop. I use my Apple TV like it’s a big iPad stuck to the wall. Because that’s basically what it is. I honestly had no idea so many people just buy it to strea…

Everyone I know who has or had an Apple TV used it primarily as a streaming device, just as they would use a Google TV device, or a Roku.
Post reply on HN