On 04/20/10 10:35, Dave Miner wrote:
On 04/20/10 01:23 PM, Adam Leventhal wrote:
Hey Dave,
Was there any thought given to how one would generate an install for
a 32-bit only system? Conversely, could one build an install image
that was only designed to boot 64-bit? This could be useful, for
example, to minimize the size of a netboot image.
Faceting package contents as 32- vs. 64-bit should be most of the
work, followed by expressing that facet into the installation process.
It sounds like you're suggesting that this would require some
modification to the manifests, is that right? Can you provide some
examples of either how this has been done or how it could be done?
Right, the package manifests would need to tag the objects with the
correct facets; I'd think a couple of transform rules to pkgmogrify
could do most of the work. Then in DC or AI we'd need to set those
facets in creating the image. I'm not aware of any use of faceting yet
in the system, though, so examples are scarce :-)
You can always change the facets after initial installation of packages.
pkgmogrify could indeed handle modifying the manifests pretty easily.
It's prob. not worth trying to untangle isaexec stuff.
Note that 32 bit components would need to be shipped for userland
regardless of kernel being 64 bit only.
I'd tag 32 bit and 64 bit kernel components, and 64 bit userland.
something like
facet.isa.kernel.32bit
facet.isa.kernel.64bit
facet.isa.user.64bit
There's no point in tagging 32 bit user programs as it is not
possible to build a running system w/o them.
You could then set image facets to exclude stuff as desired.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
