> But not from userland. Tar is used en masse, cpio isn't.
Red hat uses cpio all over the place. RPM is cpio based, and the drivers in a
Red Hat boot disk or driver disk are in a cpio file as well (and their cdrom
boot process uses the same code, so that's also cpio). This almost certainly
means Mandrake uses the same stuff, and between the two of them we are over
50% of both the Linux installed base, new sales, and new installs. (Take
your pick of what you want to measure.)
Yeah, cpio is a pain and change to use, but so is tar. You're just used to
it. To get the behavior you want creating a tarball, your option list is
probably something like "tar cvjfpC tarball.tbz dirname .". Hands up
everybody who thinks cvjfpC is intuitive? Yes you could instead do "cd
dirname; tar cvp * | bzip2 > tarball.tbz" if that strikes you as more
newbie-friendly. (This is assuming you know that that "v" goes to stderr
rather than standard out when it detects that stdout has been redirected, but
then you had to know to use "." rather than "*" for obvious reasons. :)
And of course this is assuming you're using gnu tar (which still doesn't
officially support bzip by the way, j support was a patch last I checked).
The older versions wanted a dash before the options list. (Try the version
of tar in busybox sometime...)
> It's the only reason to use tar over cpio...I feel it's a
> good one.
By that logic, people should stick with windows. :)
The objection is "people shouldn't have to learn a new tool when upgrading to
a new kernel". A tool that has been around since the 1970's, I'm might
add...
Rob
-- http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad, CmdrTaco, liquid nitrogen ice cream, and caffienated jello. Well why not?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/