268
268
entries in cpio archives.
275
format is mis-named, as it uses a simple checksum and
276
not a cyclic redundancy check.
278
The old binary format is limited to 16 bits for user id,
279
group id, device, and inode numbers.
280
It is limited to 4 gigabyte file sizes.
282
The old ASCII format is limited to 18 bits for
283
the user id, group id, device, and inode numbers.
284
It is limited to 8 gigabyte file sizes.
286
The new ASCII format is limited to 4 gigabyte file sizes.
288
None of the cpio formats store user or group names,
289
which are essential when moving files between systems with
290
dissimilar user or group numbering.
292
Especially when writing older cpio variants, it may be necessary
293
to map actual device/inode values to synthesized values that
294
fit the available fields.
295
With very large filesystems, this may be necessary even for
327
301
The character format was adopted as part of
328
302
IEEE Std 1003.1-1988 (``POSIX.1'').
329
303
XXX when did "newc" appear? Who invented it? When did HP come out with their variant? When did Sun introduce ACLs and extended attributes? XXX
308
format is mis-named, as it uses a simple checksum and
309
not a cyclic redundancy check.
311
The old binary format is limited to 16 bits for user id,
312
group id, device, and inode numbers.
313
It is limited to 4 gigabyte file sizes.
315
The old ASCII format is limited to 18 bits for
316
the user id, group id, device, and inode numbers.
317
It is limited to 8 gigabyte file sizes.
319
The new ASCII format is limited to 4 gigabyte file sizes.
321
None of the cpio formats store user or group names,
322
which are essential when moving files between systems with
323
dissimilar user or group numbering.
325
Especially when writing older cpio variants, it may be necessary
326
to map actual device/inode values to synthesized values that
327
fit the available fields.
328
With very large filesystems, this may be necessary even for