Re: Jumpstart with different version of Solaris and Hardware

From: Sarah Tanembaum (sarah.tanembaum_at_yahoo.com)
Date: 05/21/04


Date: Fri, 21 May 2004 14:37:37 -0400


"Bruce D Porter" <bdp@ytc1.co.uk> wrote in message
news:pan.2004.05.21.18.27.22.37722@ytc1.co.uk...
> On Fri, 21 May 2004 11:36:23 -0400, Sarah Tanembaum wrote:
>
> >
> > "Bruce D Porter" <bdp@ytc1.co.uk> wrote in message
> > news:pan.2004.05.21.14.42.45.965105@ytc1.co.uk...
> >> On Fri, 21 May 2004 00:38:54 -0400, Sarah Tanembaum wrote:
> >>
> >>
> >> > "Rich Teer" <rich.teer@rite-group.com> wrote in message
> >> > news:Pine.SOL.4.58.0405202030360.1264@rite-group.com...
> >> >> On Thu, 20 May 2004, Sarah Tanembaum wrote:
> >> >>
> >> >> > Thanks Rich.
> >> >>
> >> >> My pleasure.
> >> >>
> >> >> > But what command should I use to create a Jumpstart Server for
> >> >> > SPARC
> >> > sun4m
> >> >>
> >> >> Jumpstart Servers are not platform dependent (except for CPU). So
you
> >> >> don't create a sun4m Jumpstart server, but a SPARC one (unless you
> >> >> already have one). It's only when you set up each client that you
> >> >> specify the architecture (sum4m, sun4u, etc.).
> >> >>
> >> >> > Solaris 9? Should I use the Solaris 9 SPARC cd or I have to use
the
> >> >> > x86 Solaris 10 cd since the client architecture would be different
> >> >> > than that
> >> > of
> >> >> > the server?
> >> >>
> >> >> You use the CD that you want to create an image of. In you case,
you
> >> >> want to set up a Solaris 9 Jumpstart server, so you insert the S(
> >> >> Software 1 of 2 CD, and go to /cdrom/cdrom0/Solaris_9/Tools (or
> >> >> something similar; I'm going from memory). From there, you run the
> >> >> script setup_install_server. You'll need to perform a similar task
> > with
> >> >> the 2nd SW CD.
> >> >>
> >> >> You add clients using the aptly named add_install_client. See their
> >> >> respective man pages for more info, and docs.sun.com. (Although you
> >> >> run add_install_client from your newly created installation tree,
not
> >> >> the CD.)
> >> >>
> >> >> Very quick summary (not a replacement for using the docs!), from
> >> >> memory (so caveat emptor):
> >> >>
> >> >> Insert CD 1 of 2
> >> >> cd /cdrom/cdrom0/Solaris_9/Tools
> >> >> ./setup_install_server /export/install/solaris-9_0404_SPARC [Time
> >> >> passes]
> >> >> Insert CD 2 of 2
> >> >> cd /cdrom/cdrom0/Solaris_9/Tools
> >> >> ./add_to_install_server /export/install/solaris-9_0404_SPARC [More
> >> >> time passes]
> >> >> cd /export/install/solaris-9_0404_SPARC/Tools ./setup_install_client
> >> >> hostname sun4m
> >> >>
> >> >> That last step assumes that /etc/ethers and /etc/hosts is set up
> >> >> correctly.
> >> >>
> >> >> HTH,
> >> >>
> >> >> --
> >> >> Rich Teer, SCNA, SCSA
> >> >>
> >> >> President,
> >> >> Rite Online Inc.
> >> >>
> >> >> Voice: +1 (250) 979-1638
> >> >> URL: http://www.rite-online.net
> >> >
> >> > Thanks again Rich. I did follow the instruction by running the
> >> > 'setup_install_server -b /export/install' it gives me the following
> > error:
> >> >
> >> > ERROR: Install boot image /cdrom/cdrom0/Solaris_9/Tools/Boot does not
> >> > exist Check that boot image exist, or use [-t] to specify a valid
boot
> >> > image elsewhere.
> >> >
> >> > It turns out, the Boot file(/cdrom/cdrom0/Solaris_9/Tools/Boot is a
> >> > link to ../../../s1 which does not exist!
> >> >
> >> > What boot image is it talking about? Can I copy that boot image
> > somewhere
> >> > else? Thanks
> >>
> >> Looks like you have hit that small glitch... sparc cannot read x86 boot
> >> CDs.
> >>
> >> One solution is to use an already setup x86 machine to run the
> >> setup_install_server/add_install_server, then share the directory,mount
> >> it up on the sparc box and run the setup_install_server from there.
> >>
> >> JET can help and make JumpStarting much easier.
> >>
> >> http://www.sun.com/bigadmin/content/jet/
> >>
> >>
> >> --
> >> Bruce
> >>
> >> "The internet is a huge and diverse community and not every one is
> >> friendly"
> >> http://www.ytc1.co.uk
> >>
> >>
> > Hi Bruce, I'm confuse.
> >
> > Here's my setup:
> >
> > I have 2 machines, one is x86 machines running Solaris 10 server, and
the
> > other is unconfigured SUN SPARCStation 5(I think its sun4m
architecture).
> > I don't have CD on the SPARC but I have one on the x86.
> >
> > Since SS5 can't run Solaris 10, so I have to install Solaris 9 for
SPARC.
> > Here where I found the problem.
> >
> > I'm trying to make my x86 Solaris 10 as a JumpStart server(or perhaps
use
> > it as my SS5 diskless boot server).
> >
> > What I did is putting SPARC Solaris 9 Software CD1 on my x86 and try to
> > run
> > :
> > :
> > # ./setup_install_server -b /JumpStart/sol9.
> >
> > It complaint that it can't find the Boot images. When I check the
> > CD(/cdrom/cdrom0/Solaris_9/Tools/Boot -> ../../../s1) - the file is a
link
> > to non-existant file.
> >
> > I'm stuck.
> >
> > Perhaps if we can do it manually. Instead of using script, can anyone
tell
> > me what file(s) should I put in the /JumpStart/sol9 directory so I can
> > build my SS5?
>
>
> This isn't looking good is it ?
>
> Have you any other Sparc boxes available that you can work with (ie have
> an OS and are networked). If so , you can try this.
>
> Using NFS, gets around the architecture issue with ufs. You can mount a
> NFS share on a client and the client doesn't care what the underlying
> filesystem is on the server.
>
> The downside here is that its a bit more complex and that it may take a
> bit longer to setup because you have to install the image over the
> network. Also, you'll need 2 systems, a SPARC based one and a x86 one.
>
> Add the following line to your /etc/rmmount.conf on the system of the
> same architecture that you want to create a jumpstart image of. (If you
> want to put a copy of Solaris 9 SPARC on your x86 laptop, add this line
> to the SPARC system. If you want to do put a Solaris 9 x86 image on your
> SPARC system, the line goes in your x86 system's rmmount.conf)
>
>
> # share out the CD-ROM
> share cdrom* -o ro,anon=0
>
> This line causes vold automatically share out the CD-ROM and all
> partitions on that CD. This is needed because NFS sharing doesn't span
> filesystems automatically. "anon=0" causes reads by UID=0, which is
> normally mapped to user "nobody" by NFS for security reasons to remain
> mapped to UID=0. This isn't a security issue here because the CD is a
> Read-Only medium anyways.
>
> You will need to re-start vold. Runnning "/etc/init.d/volmgt stop" and
> "/etc/init.d/volmgt start" will do this.
>
> You'll likely need to start up the NFS server processes as well. You can
> either manually start them each time you boot your system or put the
> following into /etc/dfs/dfstab
>
>
> share -F nfs -o ro,anon=0 /cdrom
>
> If you don't have NFS already sharing out filesystems, you'll need to
> start it byt running "/etc/init.d/nfs.server start" as root.
>
> At this point, drop in your CD into the appropriate system. It should
> mount and share things automatically.
>
> # mount
> /cdrom/sol_9_x86/s2 on /vol/dev/dsk/c1t0d0/sol_9_x86/s2 read
> only/nosuid/maplcase/noglobal/rr/traildot/dev=1740003 on Tue Dec 3
> 15:09:39 2002
> /cdrom/sol_9_x86/s0 on /vol/dev/dsk/c1t0d0/sol_9_x86/s0 read
> only/nosuid/intr/largefiles/onerror=panic/dev=1740001 on Tue Dec 3
> 15:09:39 2002
>
> # share
> - /cdrom ro,anon=0 ""
> - /cdrom/sol_9_x86/s2 ro,anon=0 ""
> - /cdrom/sol_9_x86/s0 ro,anon=0 ""
>
> At this point you should be able to CD down
> to the appropriate location to run your setup_install_server.
>
> # pwd
> /
> # cd /cdrom/sol_9_x86/s2/Solaris_9/Tools
> # pwd
> /cdrom/sol_9_x86/s2/Solaris_9/Tools
> # ls
> Boot dial setup_install_server
> add_install_client rm_install_client
>
> Alternately, you can mount up the directories manually. For example:
>
> # mount -F nfs -o ro dhcp-ublm02-228-227:/cdrom /mnt
> # mount -F nfs -o ro dhcp-ublm02-228-227:/cdrom/sol_9_x86/s0
> /mnt/sol_9_x86/s0
> # mount -F nfs -o ro dhcp-ublm02-228-227:/cdrom/sol_9_x86/s2
> /mnt/sol_9_x86/s2
>
> All 3 mounts are needed as we have 3 separate filesystems and NFS
> doesn't span filesystems.
>
> Now run your "setup_install_server" script.
>
> # ./setup_install_server /export/install/sol_9_x86
> Verifying target directory...
> Calculating the required disk space for the Solaris_9 product
> Calculating space required for the installation boot image
> Copying the CD image to disk...
> Copying Install Boot Image hierarchy...
> Install Server setup complete
>
> You can either install the CDROM 2 of 2 through this method or drop it
> in locally as it is in the hsfs format.
>
> There are lots of ways that this can be done outside of this particular
> method. Your mileage may vary.
> --
> Bruce
>
> "The internet is a huge and diverse community and
> not every one is friendly"
> http://www.ytc1.co.uk
>

Well, I do have 2 systems:
- One unconfigured SPARC box and
- One x86 box running Solaris 10

I can't figure out why this is such an ordeal for a UNIX OS that has been
around the longest as compare to the rest? Even Linux has the answer?

Does Sun does not really care about this issues? Is Solaris a dying breed
cause Linux will surpass its capabilities?

Please advise. Thanks



Relevant Pages

  • Re: Jumpstart with different version of Solaris and Hardware
    ... >> It complaint that it can't find the Boot images. ... > Using NFS, gets around the architecture issue with ufs. ... > Copying Install Boot Image hierarchy... ...
    (comp.unix.solaris)
  • Re: Jumpstart with different version of Solaris and Hardware
    ... >> It complaint that it can't find the Boot images. ... > Using NFS, gets around the architecture issue with ufs. ... > Copying Install Boot Image hierarchy... ...
    (comp.sys.sun.admin)
  • Re: PXE boot
    ... The DHCP server ... The NFS server ... The DHCP servers task is to tell any asking clients that a boot image is ... The next step is to tell it about where to get a kernel and ...
    (Ubuntu)
  • Re: [PATCH] Late Re Initialization Of Strong RNG (random.c)
    ... NFS: server 10.150.41.21 error: fileid changed ... Turned out that during every boot, ... random32() returns pseudo random numbers instead of strong random. ... initialization occurs after any of board specific RTC driver ...
    (Linux-Kernel)
  • Re: USB key requirement.
    ... I figured that after the root partition is mounted (nfs), ... wondering what good means the usb key in this case. ... continue the boot sequence. ... the key would be checked right after the block device is ...
    (Debian-User)