Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

aruljohn.com

Post reply on HN
Print view View original

81–90 of 109 posts

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

#81

Post by noisem4ker »

kstrauser wrote: post #22
Joker_vD wrote: post #16

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".

Agreed. Where else would you put that stuff? It’s gotta go somewhere, and this is the least surprising place IMO. Anywhere else would have to be a parallel store that follows filesystem mounts and unmounts, renaming directories, etc so that it alway perfectly mirrors the thing it’s configuring.

> Where else would you put that stuff?

A "Centralized thumbnail cache" in the user profile folder, where it's been for a long while.

https://en.wikipedia.org/wiki/Windows_thumbnail_cache

> so that it alway perfectly mirrors

Who cares? It's a cache.

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

#83

Post by rrvsh »

dented42 wrote: post #42
amarant wrote: post #20

Earlier quoted context omitted.

Nixos has a pretty solid solution to this issue: key your dependencies with checksums of the content. That way you get the best of both worlds: you always get the exact version you want, and you can share a copy of that exact version with other software that wants to use that exact version too!

So it sounds like you don’t get the exact version you want because metadata is thrown away.

It's a checksum not the content itself

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

#84

Post by [deleted] »

adrian_b wrote: post #73
LatencyKills wrote: post #2

Ex-Apple engineer here. This is, for better or worse, just the way Apple approaches this type of problem. From Apple's perspective, this is the way to preserve Finder / Gatekeeper / metadata semantics. It avoids silent data loss when round-tripping archives between Macs. This behavior also maintains consistency with copyfile(3) (as well as the Archive Utility behavior). Apple treats tar less like “portable Unix inter…

Yes, I completely disagree with TFA. The problem described in TFA is not specific to Apple, but the same problem appears when archiving any decent filesystem that has been designed during the last 3 decades and not a half of century ago, including all Linux file systems. The problem described in TFA is not caused by Apple, but by the author using an obsolete tar program and not being aware of this. The traditional ta…

[deleted]

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

#85

Post by jooize »

fingerlocks wrote: post #70
dwattttt wrote: post #66

Earlier quoted context omitted.

They could control their own Apple TVs to allow that dialogue to be dismissed via the TV controls.

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.

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

#86

Post by Arainach »

fingerlocks wrote: post #70
dwattttt wrote: post #66

Earlier quoted context omitted.

They could control their own Apple TVs to allow that dialogue to be dismissed via the TV controls.

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

No, the value prop is a streaming device with a clean UX not filled with ads. My phone (which is not an iPhone) has nothing to do with it. Apple TV is a far better YouTube device than Google TV. It's also the best device for Plex, Netflix, and all the streaming apps.

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

#88

Post by ktm5j »

seba_dos1 wrote: post #44

> Why does it have those extra files? > For some reason Very informative!

They aren't even files.. they're just file metadata called extended attributes. This problem has nothing to do with tar either, it's about differences between the OS filesystems. Really nothing to see here IMO.

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

#89

Post by pjmlp »

messe wrote: post #38
matheusmoreira wrote: post #8

Earlier quoted context omitted.

It's a good attitude to have, in my opinion. Portability is overrated. Linux developers should be doing a lot more of this. We should be making everything work better for us without caring how it's going to impact other irrelevant platforms. Let the people who actually care about those platforms worry about such things.

> Linux developers should be doing a lot more of this. We should be making everything work better for us without caring how it's going to impact other irrelevant platforms Linux developers already do. Using a BSD can already be a pain in the arse, thanks to (often poorly thought out) Linux-isms cropping up everywhere.

Many have a tendency to mix GNU/Linux with UNIX, unfortunely.

Which is why I enjoy at least on embedded we are having plenty of choice between FreeRTOS, NuttX, and plenty others.

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

#90

Post by Cockbrand »

I don't see the issue here. Some filesystems store data in several streams, and have been doing so for decades. GNU tar gives warnings about stuff it doesn't know, and which can be ignored without a problem. If you haven't ever seen a different *nix system than Linux, this may be a surprise, but it should be taken as an opportunity to learn something new and move on.
Post reply on HN