Casper.Dik at Sun.COM writes:
>
>
> >This can be circumvent by using mmap(). Mandrake had such a patch
> >which removed the memory limitation.
> >
> >IMO there is no reason why pbzip2 can't replace bzip2.
>
>
> Only if it works; apparently in the code as it is, there is such a defect,
> correct? (It will not bunzip files larger than fits in the virtual memory)
If it just installs alongside the existing bzip2, isn't this project
in conflict with PSARC 1991/061? In particular, we said this:
The rule we agreed to is:
Each component of the system can appear in only one package.
[...]
A component is not really (only) a binary piece of the system. We
don't want two products taking the same source code, with their own
slightly different hacks, and shipping it. We also don't want two
products taking completely different source code and shipping it under
the same name.
This project seems to run afoul of at least that first part.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
