On 05/ 5/10 03:49 PM, Jack Schwartz wrote:
...
On 05/ 5/10 10:07 AM, Dave Miner wrote:
I expected that moving /var/pkg would involve it no longer being a
sparse set of links on the boot archive but instead a single link at
the top into a fully read-only copy on solarismisc.zlib. Why is this
approach better, as it seems to leave us with lots of non-writeable
areas in /var/pkg still (and consumes more space on the archive than
the single link would)? A nit that find/cpio is generally preferred
over cp -r since it preserves sparse files. Also, you should be
preserving modes and modification times, which your cp usage does not.
Lots of points here:
1) /var/pkg cannot be completely read-only. pkg requires some of the
files to be RW in order to install new packages. This, combined with how
pkg updates its catalogs is the underlying cause of this whole problem.
2) Which non-writeable areas in /var/pkg are left? I do an rm -rf on
/var/pkg after copying the contents to /tmp. There is only the single
symbolic link to /tmp/pkg remaining in the boot_archive.
As a reminder:
/var/pkg is off limits to all external consumers. It is a project
private area, and for all intents and purposes, the entire area must be
writeable if you want to perform package operations.
If I understand jack's change correctly, it would be the right one, in
that a set of links will not work as expected. A single link for the
/var/pkg directory might, although I haven't tested it personally.
Cheers,
-Shawn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
