Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Velocipede Rider
Velocipede Rider
@ruari@velocipederider.com  ·  activity timestamp 3 days ago

I got bored and reverse engineered how SCO #cpio is able to store such large files in their archives when the newc format only officially supports 4GiB file entries.

I am not a coder, so I just made some files with cpio from the Heirloom Toolset and looked at them in hexdump.

#rpm packages use #newc for payload and have the same 4 GiB individual limit. Maybe they should adopt this extension. The they can have up to 9 EiB entries, which should be good enough. 🤪

https://gist.github.com/ruario/b02c762c95d6521d5df4f798cd795318

  • Copy link
  • Flag this post
  • Block
Velocipede Rider
Velocipede Rider
@ruari@velocipederider.com replied  ·  activity timestamp 3 days ago

SCO is not the only vendor to extend cpio to support bigger files. The Heirloom pax man page has details

https://heirloom.sourceforge.net/man/pax.1.html

The SCO extension is interesting because

1. It is an extension to newc (used by rpm and initramfs)
2. The extensions only kicks in when needed. It does not introduce an entirely new format.

pax.1

  • Copy link
  • Flag this comment
  • Block
Velocipede Rider
Velocipede Rider
@ruari@velocipederider.com replied  ·  activity timestamp 3 days ago

And besides those listed in the Heirloom pax man page, afio also extended the POSIX (odc) cpio format to allow for bigger files and other such stuff.

https://github.com/kholtman/afio

(see the references to their 'Large ASCII' format)

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct