Re: [zones-discuss] zone p2v proposal
On Mon, Dec 8, 2008 at 9:43 AM, Jerry Jelinek gerald.jeli...@sun.com wrote: The native brand installer will accept the following new arguments: -a {path} - specifies a path to an archive to unpack into the zone -d {path} - specifies a path to a tree of files as the source for the installation. -p- preserve system configuration (either -p or -u required). -s- install silently -u- sys-unconfig(1M) the zone after installing it -v- verbose output from the install process The -p, -s, -u and -v options are only allowed when -a or -d is provided. If -a or -d is not given, then the zone is installed using the existing mechanism. Can an option be added to not make another copy of the data? That is, if I have already gotten the bits in place on disk that I am happy with, please don't copy them again (mv and zfs set mountpoint are OK if needed). Usage scenarios: 1) I restored a physical system from backups and need to attach it as a zone. For example mkdir /zones/oops metainit d1234 -p d50 8G echo /dev/md/dsk/d1234 /dev/md/rdsk/d1234 /zones/oops ufs 1 yes - /etc/vfstab mount /zones/oops chmod 700 /zones/oops mkdir /zones/oops/root use your favorite backup/restore tool to restore to /zones/oops/root p2v it 2) Create zones as clones of / zfs snapshot rpool/ROOT/snv_...@zonemaster zfs clone rpool/ROOT/snv_1...@zonemaster rpool/zones/new mkdir /zones/new/root mv /zones/new/* /zones/new/root p2v it, with sys-unconfig -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Package minimization question
Christine, From the package list I assume you are running Solaris 10, not OpenSolaris. I suppose you can leave out the X11-related packages, but it isn't a valid assumption that a headless system doesn't need these packages. X11 applications can be remotely displayed using X protocol, or via Xvnc to a system with a framebuffer. Since you state that other systems you've built have worked so far, I guess you've got your answer. --Glenn Christine Tran wrote: Cross-posted, pardon me for duplicates. I'm building a system starting with SUNWCrnet, it needs zones and TX. Using the fine Solaris Package Companion tool, I'm down to the following: [C] SUNWCzoneXXSolaris Zones [P] SUNWzoner PASSEDSolaris Zones (Root) [P] SUNWzoneu XXSolaris Zones (Usr) x [P] SUNWadmfrSystem Network Administration Framework Configuration x [P] SUNWadmfwSystem Network Administration Framework x [P] SUNWctplsPortable layout services for Complex Text Layout support x [P] SUNWdtcorSolaris Desktop /usr/dt filesystem anchor x [P] SUNWj5rt JDK 5.0 Runtime Env. (1.5.0_14) x [P] SUNWmfrunMotif RunTime Kit x [P] SUNWpool Resource Pools x [P] SUNWpoolrResource Pools (Root) x [P] SUNWxwdv X Windows System Window Drivers x [P] SUNWxwfntX Window System platform required fonts x [P] SUNWxwiceX Window System Inter-Client Exchange (ICE) Components x [P] SUNWxwplrX Window System platform software configuration x [P] SUNWxwpltX Window System platform software x [P] SUNWxwrtlX Window System Graphics Runtime Library Links in /usr /lib [C] SUNWCts XXSolaris Trusted Extensions [P] SUNWtsgXXTrusted Extensions global [P] SUNWtsuXXTrusted Extensions, (Usr) [P] SUNWtsrXXTrusted Extensions, (Root) x [P] SUNWctplsPortable layout services for Complex Text Layout support x [P] SUNWdtbasCDE application basic runtime environment x [P] SUNWdtcorSolaris Desktop /usr/dt filesystem anchor x [P] SUNWmfrunMotif RunTime Kit x [P] SUNWxwcftX Window System common (not required) fonts x [P] SUNWxwdv X Windows System Window Drivers x [P] SUNWxwfntX Window System platform required fonts x [P] SUNWxwiceX Window System Inter-Client Exchange (ICE) Components x [P] SUNWxwoptX Window System Optional Clients x [P] SUNWxwplrX Window System platform software configuration x [P] SUNWxwpltX Window System platform software x [P] SUNWxwrtlX Window System Graphics Runtime Library Links in /usr /lib The x indicates missing packages not in SUNWCrnet. I wonder if the X Window, Motif, CDE and Text Layout is *really* necessary. I don't have a problem adding pools and the two admin packages. Other boxes built without these packages have worked fine so far. However, eventually they will need support, and I don't want to be in that place where I have to explain why a headless box that runs no graphics needs X, and un-supportability. Thanks! CT ___ security-discuss mailing list security-disc...@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Package minimization question
Christine Tran wrote: Cross-posted, pardon me for duplicates. I'm building a system starting with SUNWCrnet, it needs zones and TX. x [P] SUNWj5rt JDK 5.0 Runtime Env. (1.5.0_14) [...] I wonder if the X Window, Motif, CDE and Text Layout is *really* necessary. I don't have a problem adding pools and the two admin packages. Other boxes built without these packages have worked fine so far. However, eventually they will need support, and I don't want to be in that place where I have to explain why a headless box that runs no graphics needs X, and un-supportability. I would guess that the Java Runtime is the reason for the dependencies on the X, Motif CDE library packages, since there aren't separate packages for Just enough JRE to run-non-GUI Java apps and JRE support for Java GUI apps. Those libraries are for X clients, so would also be needed if you want to ssh to the machine and remote display a GUI app back to another computer - if you're on Solaris 10 or later, the X servers for local display are in SUNWxorg-server and SUNWxsun-server, which didn't appear to be in your list. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zone p2v proposal
On Fri, Dec 12, 2008 at 6:45 PM, Jerry Jelinek gerald.jeli...@sun.com wrote: Mike Gerdts wrote: On Mon, Dec 8, 2008 at 9:43 AM, Jerry Jelinek gerald.jeli...@sun.com wrote: The native brand installer will accept the following new arguments: -a {path} - specifies a path to an archive to unpack into the zone -d {path} - specifies a path to a tree of files as the source for the installation. -p- preserve system configuration (either -p or -u required). -s- install silently -u- sys-unconfig(1M) the zone after installing it -v- verbose output from the install process The -p, -s, -u and -v options are only allowed when -a or -d is provided. If -a or -d is not given, then the zone is installed using the existing mechanism. Can an option be added to not make another copy of the data? That is, if I have already gotten the bits in place on disk that I am happy with, please don't copy them again (mv and zfs set mountpoint are OK if needed). Mike, I'll think about that. What if -d {zonepath} just skipped the copy of the bits? Thanks, Jerry That sounds reasonable. This seems to imply that the argument to -d will be a directory that has a subdirectory named root which is the actual root of the thing to be turned into a zone. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org