Hi > Where do I find the failsafe image? Is it something that is independently downloadable, or is it something that gets constructed as a side effect of installing other packages?
It's part of standard Solaris since (I think) Solaris 10 Update 7 or an recent version of Solaris Nevada: root at v240:~# du -hs /platform/sun4u/failsafe 178M /platform/sun4u/failsafe Hmm, just checked on my Solaris x86 machines and did not find a failsafe image there (I never used it before on x86) .. Do you use SPARC or x86? regards Bernd Maule Mark wrote: > Ugh, I forgot to pursue that. Where do I find the failsafe image? Is > it something that is independently downloadable, or is it something > that gets constructed as a side effect of installing other packages? > > PS: 700mb is not that big in a normal system, but my environment will > be diskless, and I want as much memory as possible for custom > applications. In addition, I am not going to be running anything over > NFS, so everything must fit into memory. > > thanks > Mark > > ------------------------------------------------------------------------ > *From:* Bernd Schemmer <Bernd.Schemmer at gmx.de> > *To:* Mark Maule <mark_maule at yahoo.com> > *Cc:* distribution-discuss at opensolaris.org > *Sent:* Wed, December 16, 2009 12:55:49 PM > *Subject:* Re: [distribution-discuss] packages for minimal custom boot > archive > > Hi, > > > >>This seems like a better idea, to populate an archive using minimal > packages, and then remove bits and pieces that I don't need. However, > what I found is that the "minimal" milax archive is over 700mb! > > > 700 MB is not yet that big ... did you try to use the failsafe image and > add the packages you need? > > regards > > Bernd > > Mark Maule wrote: > > Hi: > > > > I'm attempting to build a minimal boot archive for an appliance. > The running image needs to exist in ram (no disk), and so I'm hoping > to put together a boot archive that will bring up a writeable > ram-based root. Initially I was trying to do this by pulling bits and > pieces out of the on-nv proto/... directory, and I got to the point of > booting, but once I started to bring in the various smf pieces, it > became intractable. > > > > My next attempt was to start with a minimal set of packages (using > milax as a model) as suggested in this thread: > http://opensolaris.org/jive/thread.jspa?threadID=119913&tstart=0 > <http://opensolaris.org/jive/thread.jspa?threadID=119913&tstart=0> > > > > This seems like a better idea, to populate an archive using minimal > packages, and then remove bits and pieces that I don't need. However, > what I found is that the "minimal" milax archive is over 700mb! > > > > Looking farther, it seems that SUNWcs is huge, and brings in all > kinds of things like Xorg and Python which don't really seem minimal. > > > > So, my question is, what is the best way to approach this? Is there > precedent for creating a small boot archive like this? I was hoping > that I could get console, dhcp client, and ssh in maybe 100-200 mb. > > > > Any pointers would be greatly appreciated. > > > > > -- > Bernd Schemmer, Frankfurt am Main, Germany > http://bnsmb.de/ > > M s temprano que tarde el mundo cambiar . > Fidel Castro > > -- Bernd Schemmer, Frankfurt am Main, Germany http://bnsmb.de/ M s temprano que tarde el mundo cambiar . Fidel Castro
