Install solaris via hyper terminal

Hi,
I just got my new ultra 5 box and I was wondering what type of cable and hyper terminal settings I need in order to get this thing rolling.
The type of cable I used before was a null modem cable db9F --> db9F. Then I read I needed db9 --> db25. So I went out and look for db9 --> db25 only to find that there wasn't any male to male cables ... any suggestions would be great!
Thanks,
IPv6

Dear friends,
I have the same problem...
I have a VGA adapter in my sparc 5, but my 14" monitor doesn't show nothing (only a new MAG 17" but it's not mine).
So, I switched to HyperTerminal.
I made more than 10 Null modem cables, with all the options, but I could not see nothing and I cannot install my mchine.
The explanation of the cable here, I didn't understand so good, albeit that, I make the cable but it didn't work.
Does anybody knows what to do, step by step, or where can I read it?
Thank you very much!
Ilan.

Similar Messages

How to install Solaris 9 connected via Hyper Terminal

Hi All ,
We have planned to Install Solaris 9 in E250. We have connected the console throgh Hyper Terminal.
We are not able to see the options clearly in the console. The options are not in clear way. It is very difficult to install.
Please advice how to install Solaris 9 in Text mode and terminal type for installing the solaris 9 via Hyper Terminal.
I am awaiting for your reply.
Regards,
R. Rajesh Kannan.

When the install starts, select a terminal type of VT100
The screens should display correctly then.

Installing Solaris via network

A few days ago I have got an old Sun server (Netra 1125).
I am fairly new to Sun hardware and I wonder if there is a way to install Solaris via serial cable and a TCP/IP network (I don't have a cdrom and I don't have vga or floppies).
I have a Linux machine nearby. Can I use BOOTP or something like that?
Can anybody point me to some documentation?

solaris' network install is called "jumpstart"
searching for "solaris jumpstart linux" on google provides some pages, in particular is this one that is pretty old (references sunos4) but should work... http://www.unixpeople.com/HOWTO/jumpstart_on_linux.html

Install solaris via jumpstart with 2 network interfaces

Hi guys,
I'm trying to deploy Solaris 10 on a LDOM , using Jumpstart server. The LDOM must have 2 network interfaces and 2 default routes. Here's the relevant part of sysidcfg file:
network_interface=vnet0 {primary
                hostname=aaaaaaaaa
                ip_address=aaa.aaa.aaa.aaa
                netmask=255.255.240.0
                protocol_ipv6=no
                default_route=bbb.bbb.bbb.bbb
network_interface=vnet1 {
                hostname=bbbbbbbbbbb
                ip_address=ccc.ccc.ccc.ccc
                netmask=255.255.248.0
                protocol_ipv6=no
                default_route=ddd.ddd.ddd.ddd
}After {ok} boot net - install, I get these messages:
Using RPC Bootparams for network configuration information.
Attempting to configure interface vnet1...
Skipped interface vnet1
Attempting to configure interface vnet0...
Configured interface vnet0
USB keyboard
Reading ZFS config: done.
Setting up Java. Please wait...
Serial console, reverting to text install
Beginning system identification...
Searching for configuration file(s)...
Using sysid configuration file xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/sysidcfg
Search complete.
Discovering additional network configuration...
Completing system identification...and then unattended install stops and goes into interactive menu:
Default Route     Error for vnet1     ────────────────────────────────────────────────
The route ddd.ddd.ddd.ddd could not be added at this time. If you     wish to     accept
the route provided, the route     will be     added to the /etc/defaultrouter     file
to be     used at     reboot.     If you choose not to accept your choice, you will be
asked     to enter network information again for this interface.
      Accept Route
      ────────────
      [X] Yes
      [     ] NoAfter I choose "yes" , the installation goes back to unattended (automated) state.
Any ideas why installation breaks when adding second default route?
If I delete the line default_route=ddd.ddd.ddd.ddd, the installation is not interrupted.
Many thanks,
kido
Edited by: kido on Dec 29, 2010 6:10 PM

Hello again,
First of all, if I delete the second default route from sysidcfg, the installation performs uninterrupted, but vnet1 is not brought up after reboot. I get a message like: vnet1 is not a valid interface name...or something similar...
Regarding multiple default routes now... As long as "man defaultrouter" and "man sysidcfg" state that multiple routes are supported, I would expect this to work...or at least I need a way of installing 2 NICs without human intervention...
I will try to use some post install script instead ( will create /etc/hostname.vnet1 and add second route to /etc/defaultrouter) and will let you know the results.

Problems installing Solaris 10 on Dell PowerEdge 800

Hi,
I am experiencing some trouble when I attempt to install Solaris 10 on a Dell PowerEdge 800. It is equipped with two RAID disks controlled by a Dell CERC SATA 1.5/6ch (according to the BIOS).
The installation program reports that it cannot write to the disk. This happens when it is about to start installing files. Tried setting it to a single volume and disable RAID. Same thing. Read another article saying something about disabling IDE, well it doesn't seem to help ...
Any hints?

I have the same problem on a dell 750 with the SERC controller. I can add some more information but if you get a solution I would appreciate the detail.
1) If I install Solaris via the SERC in RAID 1 mode then the alarm on the SERC goes off as soon as I start to write to the disk.
2) I bypassed the SERC and installed on a single disk straight off the motherboard. Time the install crashed at the same point but this time the error message told me that the first available cylinder was number 3! Ah
3) I reconnected the disk via the SERC, rebuilt the RAID array and made a mistake. I created a RAID 0 (striped) array and installed the software starting from cylinder 3. I got a complete solaris install that rebooted fine and is fully working.
BUT I NEED A MIRRORED SYSTEM SO
4) I rebuild the machine again this time RAID 1 and again the crash occured at exactly the same point i.e. as soo as I start to write to the disk.
Whether or not DELL / Adaptec support Solaris should not be an issue. This is a BIOS configurable RAID controller that can be fully serviced (e.g. disks replaced) from the BIOS. The system sees the array as a disk via the controller and indeed it is seeing it.
The SERCs own data configuration data should be on sectors which are not visible to solaris VIA the SERC so we shouldnt be able to damage them but I suspect that this may not be the case.
I suspect that the answer is in the partition layout and who or what creates them (I dont mean the Solaris slices but the FDISK partitions)
To make matters worse, since I need the machine working I went back to disks straight of the motherboard and configured again and used metadevices to set up a fully mirrored systemas I have done many times before on sparc (but never on Solaris x86)
This worked fine but I thought that I would test bootability in the event of disk failure. There isnt any!
if disk 1 fails then the motherboard wont accept disk 2 unless you swap the cables and move it do disk 1 and by then the boot sectors are wrong for the address of the device. I can probably solve this by building both disks in slot one but who wants a mirrored server that you have to open up and move a cable when the disk fails. I think I may have to ditch SATA and go back to SCSI !

Installing Solaris 10 on Sunfire V120 via network boot from Linux

I have been given a free SunFire V120 server loaded with and old copy of Solaris 9. The problem is that this server no longer has the internal DVD/CDRom drive any more. Google'd for finding a replacement CD-Rom drive show cost more than the SunFire V120 unit itself.
The plan: Install Solaris 10 for SPARC on Sunfire V120 Server
Available:
-- Sun Microsystems SunFire V120 Server (1GB of Ram and 2x 36GB 10K RPM SCSI3 drives)
-- CentOS 5.1 Linux Server
-- Solaris 10 SPARC DVD ISO Image
-- DB25 to RJ45 Serial Cable accessing V120 LOM via Minicom application on CentOS 5 server
Via the http://www.docbert.org/Solaris/Jumpstart/linux.html site, I have configured the following:
* NFS Server (nfs-utils under RedHat)
* bootparams server (bootparamd under RedHat)
* rarpd server (rarpd under RedHat)
* tftp server (tftp-server)
CentOS Server Settings:
[root@jsserv ~]# cat /etc/ethers
0:3:ba:36:34:48 jsclient
[root@jsserv ~]# cat /etc/bootparams
jsclient root=jsserv:/jumpstart/sol10/Solaris_10/Tools/Boot install=jsserv:/jumpstart/sol10 boottype=:in
[root@jsserv ~]# cat /etc/exports
/jumpstart *(ro,no_root_squash)
[root@jsserv ~]# cat /etc/hosts
192.168.0.20 jsserv
192.168.0.22 jsclient
[root@jsserv ~]# ls -l /tftpboot
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016 -> inetboot.sol10.sun4u
lrwxrwxrwx 1 root root 20 Mar 7 13:35 C0A80016.SUN4U -> inetboot.sol10.sun4u
-rw-r--r-- 1 root root 217016 Mar 7 13:34 inetboot.sol10.sun4u
On CentOS Linux server -- under /var/log/messages, the rarpd shows this message:
Mar 7 14:24:41 jsserv rarpd[3516]: RARP request from 0 on eth0
Mar 7 14:24:41 jsserv rarpd[3516]: RARP response to 0 192.168.0.22 on eth0
On the SunFire V120 server, the console displays:
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #53883976.
Ethernet address 0:3:ba:36:34:48, Host ID: 83363448.
Executing last command: boot net -v - install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -v - install
38e00 Using RARP/BOOTPARAMS...
Internet address is: 192.168.0.22
hostname: jsclient
domainname: (none)
Found 192.168.0.20 @ 0:13:d3:9a:9e:98
root server: jsserv (192.168.0.20)
root directory: /jumpstart/sol10/Solaris_10/Tools/Boot
boot: cannot open kernel/sparcv9/unix
Enter filename [kernel/sparcv9/unix]: /platform/sun4u/kernel/sparcv9/unix
boot: failed to allocate 8192 bytes from scratch memory
panic - boot: boot: scratch memory overflow.
Program terminated
So now what do I do?
-- Michael

Anyone know where I can get the firmware (OBP) update / upgrade version 4.22 for the SunFire V120 server?
There is an old thread (http://forum.java.sun.com/thread.jspa?threadID=5137796) that talks of having to update your firmware 4.22.x, but I have looked through the SunSolve site and I cannot find a reference to this firmware any place for the SunFire V120 servers.

Unable to install solaris 9 on via pt800 mainboard with Celeron 2.13 Ghz pr

Hi everybody
This is sharavan .I have a desktop with VIA PT800 Mainboard ,512 MB DDR SDRAM,Celeron 2.13 Ghz processor ,80 GB ATA HDD installed with Windows 2000 on one partition occupieng 20 GB and Red hat linux ES3 on another partition of 30 GB. I want to install SOLARIS 9 (X86 Version) on remaining unpartitioned free space 30GB. The installation is being sruckedup at the stage "Boot Solaris kernel from any of the identified devices 1)CDROM 2)HARD DISK ,I have choosen CDROM But the System is being hanging up there,no further action" I have restarted the system manually and tried many times without success. How to complete the installation ,Please suuggest me ,help me.........
Thanking u
[email protected]

Hello!
There is one simple method also..
Instead of Installation disk of Solaris, insert the Software 1/2 Disk, and try to follow the actuall Suninstall method of installing Solaris. Here you will get the option that how to utilize the free space.
I myself have installed more 5 OS on a single Hard disk :) this way. Try this method

Attempting to install Solaris 10 on Netra t1 via external DVD-Rom

Hello Experts,
I am trying to install Solaris 10 on my Netra t1 via external DVD. I connected the DVD-ROM to the scsi port on the back. System recognized the DVD but does not allow me to boot from it. I have done many things without any success. Following are the details:
System info:
Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard
OpenBoot 3.10.25 ME, 1024 MB memory installed,
Ran the scsi test and it doesn't report any issues:
ok test scsi
Probe-scsi-all shows the drive:
ok probe-scsi-all
/pci@1f,0/pci@1,1/scsi@2
Target 0
Unit 0 Disk SEAGATE ST318404LSUN18G 4207
Target 1
Unit 0 Disk SEAGATE ST318404LSUN18G 4207
Target 4
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
devalias also shows as cdrom1:
ok devalias
cdrom1 /pci@1f,0/pci@1,1/scsi@2/disk@6,0:f
cdrom /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f
ide-disk /pci@1f,0/pci@1/pci@1/ide@e/disk@0:f
ide-cdrom /pci@1f,0/pci@1/pci@1/ide@e/cdrom@2:f
ide /pci@1f,0/pci@1/pci@1/ide@e
I created devalias manually also with no help. Following is what I get when I try to boot from it:
ok boot cdrom1
Resetting ...
Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard
OpenBoot 3.10.25 ME, 1024 MB memory installed,
Executing last command: boot cdrom1
Boot device: /pci@1f,0/pci@1,1/scsi@2/disk@6,0:f File and args:
Drive not ready
Evaluating: boot cdrom1
Can't open boot device
I verified the DVD and it works just fine. I install the OS with the same DVD on Netra-440 system without any issues.
Please tell me what am I missing here or doing wrong. Please help.

Sun-worshiper,
Thank you so much for pointing that out. I was loosing it.
Just in case someone else runs into this type of issue:
When you run probe-scsi-all please pay attention to the target. In order to boot from the DVD, I executed the following commands from the ok prompt:
ok nvalias dvd /pci@1f,0/pci@1,1/scsi@2/disk@4,0:f
ok boot dvd

Installing Solaris 10 on VIA EPIA PE10000G mobo + VIA C3 Nehemiah processor

Hello,
I was wondering if anyone could help me out. I recently purchased a VIA EPIA PE10000G motherboard with a VIA C3 Nehemiah 1.0GHz EBGA processor (http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_id=451).
I am trying to install Solaris 10 08/07 and running into problems with the processor being recognized. In my research, I've found some posts, but alas, I seem to have come to a dead end. Here's what I've done:
Downloaded Solaris, fired up the installation. When the kernel starts booting I get:
"486 processor detected this processor not supported by solaris"
After searching on this error, I conculded that by doing the following, I should be able to get around this problem:
perl -pi -e 's#GenuineIntel#CentaurHauls#g' solaris_cd_1.iso
in order to swap out the vendor string for the processor.
Next, I booted with b -kv to see what would happen. While it seems that I got further along, I now get the following:
"processor does not support cmpxchg8b instruction"
and I get dropped into the kernel debugger which I am not familiar with.
I looked for an exact match for this error in Google and came up with this page as the only hit:
http://fxr.watson.org/fxr/source/i86pc/vm/hat_i86.c?v=OPENSOLARIS
Even though it says OPENSOLARIS in the URL, I bet it's the same piece of code that I'm hitting when I try to install Solaris 10:
if ((x86_feature & X86_CX8) == 0)
panic("Processor does not support cmpxchg8b instruction");
So my guess is that either x86_feature or X86_CX8 is false, I'm figuring it's the latter since the error message has looks similar to that variable.
Furthermore, I see that the error message exists in several places on the original installation CD:
strings solaris_cd_1.iso |grep cmpxchg8b
Processor does not support cmpxchg8b instruction
Processor does not support cmpxchg8b instruction
Processor does not support cmpxchg8b instruction
Processor does not support cmpxchg8b instruction
cmpxchg8b
cmpxchg8b
cmpxchg8b
cmpxchg8b
I'd really like to get Solaris 10 on this motherboard because I'd like to use it as a small firewall where space is at a premium.
Might anyone have some further suggestions as to what I can do to get this to work? From what I've seen, I think it is possible, it's just a matter of changing something more to the disk image.
thanks,
Geoprge

I did some more research and found a pdf on my processor and here's what I came up with:
0 = The CPUID instruction does not report the presence of the CMPXCHG8B instruction
(CX8 = 0). The instruction actually exists and operates correctly, however.
1 = The CPUID instruction reports that the CMPXCHG8B instruction is supported
(CX8 = 1).
From what I read here http://www.via.com.tw/download/mainboards/6/13/VIA_C3_EBGA%20datasheet110.pdf it would seem that the default is CX8=0 and I'm guessing that if it were 1, then I'd at least get past this error message.
Maybe there's a way to trick the installation image by changing the code that checks for this value similar to what I did for the vendor processor ID string? Seems to me that if I find where it checks for the CX8 value and reverse the logic, the installation would continue...

Installing Solaris 10 via external CD drive on Dell Latitude D800 Laptop

Hello all, I am trying to install Solaris 10 via external CD drive on Dell Latitude D800 Laptop. After the GRUB menu it begins to load, displaying the " . . . . . ." and hangs about 1/4 way accross the screen. When attempting the install from a DVD instead of a CD the installation hangs on the same screen even sooner. Has anyone encoutered this problem?

Hello Alex,
no, you can't use USB devices on SPARC as boot device.
The OBP (even updated ones) contains only support for the USB keyboard, but none for USB mass storage (which requires a device driver). The integrated USB ports are for slow devices like keyboard and mouse.
Using an external SCSI DVD-ROM works. Another choice is an installation via network.
Michael

Installing Plugins via Terminal (Mac)

I would like to be able to install plugins in Extension Manager via terminal and enable the installed plugins for a specific set of extensions (InCopy). I have downloaded the Adobe Extension Manager Help and Tutorials document and it explains the process of installing plugins via terminal. But when I run the install command, it actually launches Extension Manager in the console.
I want to be able to install extensions and plugins silently and even when the user is not logged in. Is this possible and can someone point me to a document which explains the process?
Bob Reed
AARP

For your issue, please follow http://forums.adobe.com/thread/977043?tstart=0 to generate log files and send them to [email protected]
For your coworker's issue, besides database file and plugin files, you also have to include files in EM Store folder and Mxi Flag folder.
If your extension is per-machine extension (all files in extension will be installed to per-machine location), you have to include "/Library/Application Support/Adobe/Extension Manager CS6/Configuration/DB/ExMan.db", "/Library/Application Support/Adobe/Extension Manager CS6/EM Store/InCopy CS6/*.*" and "/Library/Application Support/Adobe/Extension Manager CS6/Mxi Flag/InCopy CS6/*.*"
If your extension is per-user extension (all files in extension will be installed to folder under user home), you have to include "/Users/<UserName>/Library/Application Support/Adobe/Extension Manager CS6/Configuration/DB/ExManUser.db", "/Users/<UserName>/Library/Application Support/Adobe/Extension Manager CS6/EM Store/InCopy CS6/*.*" and "/Users/<UserName>/Library/Application Support/Adobe/Extension Manager CS6/Mxi Flag/InCopy CS6/*.*".
You also have to ensure all the machines have the same user name.

Linux guy wants to install solaris 10 via nfs using centos as nfs server

well in linux when installing this way I simply copy the dvd install image to an nfs share (or do mount -o loop "isoimage" /nfsmountdir), copy the boot.iso so a cdrom and do a "linux askmethod" during install and then specify the nfs server and dir.
I want to learn sun and want to start by really understanding the install and how to set up slices etc. I would really like to do this using nfs using my centos box as the server as this method at least when installing linux is much mush faster.
so can I do this and if so what are the commands. I did see some documentation but it was for installing from a sun nfs server. but I need to install from the centos as the server. I already have the iso's for the 5 cdroms as well as the dvd image. if possible I would obviously like to use the dvd image.
thanks and remember I am a sun newbie (just bought my first solaris book this week so the more dummied down answer would be the best one for me). if it can be done could you give me the exact process.
thanks a million (and one).

The Sun network installer scripts only work on Solaris. So there's no instructions from Sun for configuring the daemons on Linux necessary to do the configuration.
There are some guides on the net, but I don't know of one that tells the whole story.
You might consider installing Solaris in a VM on the linux box, then configuring jumpstart on that. You could then see how the daemons on it are configured and replicate that configuration on the Linux machine.
Darren

Installing Solaris 7 - timeout waiting for ARP/RARP packet

I'm attempting to install Solaris 7 on and E250. I'm using HyperTerminal connection via a null modem cable. I boot up the server and I see various harware init processes echoed to the terminal and then I receive this error: Timeout waiting for ARP/RARP packet
I have connected the nic card to a network connection.
any help would be appreciated.
Steve

This is because you HAVE a network connection. You can resolve this with 1 of the following 2 methods:
A:
disconnect the network cable and reconnect when the installation process gets to the prompt for hostname.
B:
1. Get to the OK prompt
2. setenv diag-device disk
3. reset

Trying to install solaris 10 on sun file v210

Rebooting with command: boot net - install nowin
Boot device: /pci@1f,700000/network@2 File and args: - install nowin
1000 Mbps FDX Link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 1000 Mbps FDX Link up
Requesting Internet address for 0:3:ba:60:36:d
I am trying to install solaris 10 (sparc) on a sun fire v210 and I get kernel dump and
the following crash messages:
Any suggestion would be very welcome indeed as this the first of 250 systems...
Lydia
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Cannot find /system/contract
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Cannot mount /proc
WARNING: file system 'mntfs' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: Cannot find /etc/svc/volatile
WARNING: Cannot find /system/object
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Failed to process interrupt for ali1535d+-power0 due to down-rev nexus driver isa0
WARNING: power_attach: failed to add high-level interrupt handler.
WARNING: power button driver failed to install
WARNING: Failed to process interrupt for rmc_comm0 due to down-rev nexus driver isa0
WARNING: rmc_comm failed to install
WARNING: Could not install rmclomv driver
WARNING: Failed to process interrupt for pcf85840 due to down-rev nexus driver isa0
WARNING: i2c_0 failed to retrieve iblock cookie. Operating in POLL MODE only
fs/sockfs:sock_getfasync() not defined properly
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetpeername'
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetsockname'
WARNING: mod_load: cannot load module 'c2audit'
WARNING: c2audit: unable to resolve dependency, module 'fs/sockfs' not found
misc/consconfig:consconfig_get_usb_kb_path() not defined properly
panic[cpu1]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/consconfig
000000000180b890 genunix:mod_hold_stub+1f0 (0, 185f800, 18ac878, 60000c44fb0, 1817328, 0)
%l0-3: 0000000001843ac8 000006000136e000 0000000001811cf8 0000000000000000
%l4-7: 0000000000000000 0000000000000064 0000000000000064 0000000000000001
000000000180b940 unix:stubs_common_code+30 (21dead78c0, 960010, 53555554, 0, 31f400, 0)
%l0-3: 000000000180b209 000000000180b2e1 000000123e000000 0000000000000001
%l4-7: 0000000000000000 0000000001817338 0000000000000000 0000060000c1abc0
000000000180ba10 genunix:main+134 (18accd0, 18a8800, 18364c0, 1861400, 183b400, 1814000)
%l0-3: 0000000070002000 0000000000000001 0000000000000000 0000000000000002
%l4-7: 00000000018afef8 00000000018afc00 00000000018acce0 00000000018acc00

I am using jet to do the jumpstart and the config file for jet is list below.
The install server is solaris 10 sparc
SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500
The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded
the latest recommended patchset which should bring me to 118855-36 plus the latest
minor kernel patches.
nereid-root (482)>cat m1001
# Client template file
# Client: m1001 (derived from quintor.js)
# Created: Wed Mar 8 14:38:51 GMT 2006
# This file was automatically generated using 'make_template'
# Product: base_config
# Synopsys: Basic host information
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# i86pc : Intel X86
# Ethernet can be obtained from the 'banner' command at OBP
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
base_config_ClientArch="sun4u"
base_config_ClientEther=00:03:ba:60:36:0d
base_config_ClientOS="sol10_u3"
# Client allocation
# The mechanism used to build this client; by default, the options listed
# in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
# if this particular client needs to do something different.
base_config_client_allocation="newboot"
# products is the set of products to install after base_config; this
# should be updated automatically by make_template, so you
# will only need to change it, if you wish to omit certain
# modules when testing/debugging.
base_config_products=" custom"
# JumpStart sysidcfg information
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
# terminal: terminal type (vt100/vt220/sun etc)
# security_policy: Kerberos policy (Solaris 8 +)
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
# default_route: Solaris 9 allows a default route to be set
# (ignored on all other versions of Solaris, less than 9)
base_config_sysidcfg_nameservice=NONE
base_config_sysidcfg_network_interface=PRIMARY
base_config_sysidcfg_ip_address=172.17.3.1
base_config_sysidcfg_netmask=255.255.0.0
base_config_sysidcfg_root_password="xxxxxxxxxxxx"
base_config_sysidcfg_system_locale="en_GB.ISO8859-15"
base_config_sysidcfg_timeserver=
base_config_sysidcfg_timezone="GB"
base_config_sysidcfg_terminal=vt100
base_config_sysidcfg_security_policy=NONE
base_config_sysidcfg_protocol_ipv6=no
base_config_sysidcfg_default_route=
# X86, X64 specific settings. If this is an x86 client, then you may need
# to configure these settings. They are ignored for SPARC builds.
# base_config_x86_nowin:
# This stops Solaris from trying to run windows during the install.
# the default value is yes.
# base_config_x86_console:
# Set the console to the correct tty port. This is used for doing installs
# via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
# and v65x use ttyb. NOTE: you only need to set this if you are NOT going
# to connect a keyboard and monitor to the client.
# base_config_disable_acpi:
# Disable ACPI - sometimes disabling ACPI makes the install go
# better due to how the interrupts are handled. Non-Null disables ACPI.
# base_config_x86_safetoreboot:
# The Solaris installer can't control the BIOS, therefore does not
# know if its safe to reboot the client as it may simply jumpstart
# again. If your PXE boot is a one time option, and the next reboot
# will attempt to boot from disk, then you probably want to set this
# option to "yes". Otherwise, leave it as it is so that it won't reboot
# and therefore allow you to manually change your BIOS to boot from disk.
base_config_x86_nowin=""
base_config_x86_console=""
base_config_x86_disable_acpi=""
base_config_x86_safetoreboot=""
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory, otherwise
# fill in the other details below to get toolkit to create one for you.
base_config_profile=""
# JumpStart profile information
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
# partition sizes:
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
# / s0
# swap s1
# /var s5
# /usr s6
# /opt s7
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
base_config_profile_cluster=SUNWCall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=""
base_config_profile_root=8192
base_config_profile_swap=4096
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
# If you are not using VxVM, then you can use s3 and s4 for whatever you wish!
base_config_profile_s3_mtpt=""
base_config_profile_s3_size=""
base_config_profile_s4_mtpt=""
base_config_profile_s4_size=""
base_config_profile_s5_mtpt=""
base_config_profile_s5_size=""
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""
# If you are using DiskSuite, the default behaviour is to use slice 7 as a
# location for metastate databases. If you are using DiskSuites default config,
# please avoid using s7 for data!
base_config_profile_s7_mtpt="/export/disk/1"
base_config_profile_s7_size="free"
# You can specify additional disks to use/configure here
# additional_disks is a space separated list of c?t?d? type disk names
# For each disk listed in additional_disks, a pair of variables of the form
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
# should be defined for each slice required on the disk.
# N.B. DO NOT SET THE BOOT DISK UP HERE !
base_config_profile_additional_disks=""
base_config_profile_disk_c0t3d0s0_mtpt=""
base_config_profile_disk_c0t0d0s0_size=
# Additional locales/geos e.g. N_Europe, C_Europe
base_config_profile_add_locales=""
base_config_profile_del_locales=""
base_config_profile_add_geos=""
base_config_profile_del_geos=""
# UFS Logging
# Solaris 7 and above support UFS+, which allows for a logging filesystem
# under UFS. If you want to use this feature on any of the UFS mount points,
# please specify the mount points here, as a space seperated list, or enter
# the keyword "all" to enable logging on all UFS filesystems.
# Solaris 9 09/04 enables logging by default. You can also specify mountpoints
# preceded by a - sign to say that you DON'T want logging enabled on that
# filesystem, or you can use the keyword "none" to say you don't want any
# ufs logging turned on at all.
# N.B. root (/) can be included in the list, and is included by default if
# using either the "all" or "none" keyword.
# Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
# valid.
# e.g. base_config_ufs_logging_filesys="all" : log all filesystems
# base_config_ufs_logging_filesys="none" : log no filesystems
# base_config_ufs_logging_filesys="-/ /var -/usr" : log /var, but not / and /usr.
base_config_ufs_logging_filesys="all"
# Packages to add to/remove from the selected cluster
# Use this to populate the profile with package <pkg> <add|delete> entries
base_config_profile_add_packages=""
base_config_profile_del_packages="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"
# Clusters to add to/remove
# Use this to populate the profile with cluster <cluster> <add|delete> entries
base_config_profile_add_clusters=""
base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"
# Remote file systems (NFS)
# Specify these as space seperated list of pairs as follows, using ? as
# the seperator (as : has special meanings with nfs!)
# e.g. to mount 1.1.1.1:/fs on /fs you would create the entry
# base_config_nfs_mounts="fs?1.1.1.1:/fs"
base_config_nfs_mounts=""
# Host information
# This section defines most things network related etc.
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
# nodename: the value for /etc/nodename if it's not the default
# hostname
# defaultrouter: the value for /etc/defaultrouter.
# notrouter: if this is set, the file /etc/notrouter will be created
# dns_domain: domain entry for /etc/resolv.conf
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
# dns_searchpath: list of entries to go in the search line
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# of DNS until later on.
base_config_nodename=""
base_config_defaultrouter=""
base_config_notrouter=""
base_config_dns_domain=""
base_config_dns_nameservers=""
base_config_dns_searchpath=""
base_config_dns_disableforbuild="yes"
# NTP configuration
# Specify a list of names or ip addresses for the NTP servers. The first
# one will be given a 'prefer' tag. This section will only place lines
# of the form: server <ipaddress/name> [prefer]
# into the /etc/inet/ntp.conf file. If you require more control of ntp,
# please use the custom module to deploy your own custom ntp.conf file.
# N.B. If you do use names, they must be resolvable in your name service.
base_config_ntp_servers=""
# Network Interface information
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
# Logical interfaces should be defined using _'s rather
# than :'s.
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
# For example:
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
base_config_networkifs="beg1"
base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"
# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""
# IP Multipathing (Solaris 8+)
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
# netgroup: ipmp interface group name
# e.g. database-net
# ipmp mode: s = standby (failover only)
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
# l = load spreading / active-active
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
# test1: ipmp test address1
# test2: ipmp test address2
# N.B. these addresses must not be used or
# placed in the hosts file
# mask: netmask for ipmp pair
# hostname: unique hostname for logical ip
# log-ip: logical ip address for first i/f of pair
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
# hostname2: unique hostname for logical ip
# log-ip2: logical ip address for second i/f
# of pair
# Example:
# base_config_ipmp_networkifs="qfe0_qfe1"
# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""
# Misc options
# this section is a catchall for other options not included above
# update_terminal: if set, put the sysidcfg terminal type into inittab
# enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
# dumpadm_minfree: set a limit so that crash dumps don't fill up the
# dump filesystem. See dumpadm(1M) -m option for
# possible values.
# noautoshutdown: if set to any value, disable power management
# enable_rootlogin: if set to any value, enable network root login
# from both telnet/rsh and ssh
# enable_rootftp: if set to any value, enable root ftp access
# shutup_sendmail: if set, create an alias hostname. to shut up sendmail
# poweroff_afterbuild: if set, shut the machine down once it has been built
# base_config_dedicated_dump_device:
# if set, dumpadm will configure the partition as a
# Dedicated Dump Device. See dumpadm(1M) for supported
# Operating Environments.
# (Device path e.g. /dev/dsk/c?t?d?s?)
# N.B. This partition is for the SOLE use of the crashdump utility !
# enable_altbreak: if set, enable alternate break sequence
# disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
# usually just tries to rarp ip addresses for additional
# interfaces and takes ages on machines with lots
# of unused network adapters.
base_config_update_terminal="yes"
base_config_enable_savecore="yes"
base_config_dumpadm_minfree="20000k"
base_config_noautoshutdown="pm_disabled"
base_config_enable_rootlogin="yes"
base_config_enable_rootftp=""
base_config_shutup_sendmail=""
base_config_poweroff_afterbuild=""
base_config_dedicated_dump_device=""
base_config_enable_altbreak=""
base_config_disable_sysid_probe="yes"
# NFSv4
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
base_config_nfsv4_domain=""
# N.B. Unless you need to point this client at alternate media for patches
# and packages that is not held on this server, please skip this section!
# productdir is where to find the products. This should be an NFS style
# path, i.e. 192.168.1.1:/export/install but if the server
# is the JumpStart server, then it should just be specified
# as a normal path.
# patchdir is where to find the patches. Same format as productdir.
# Leaving the following blank means they will be populated using jumpstart.conf
# and the JumpStart servers ip address. This is the default behaviour
# and should only be changed if your patch/package repository is not held
# on this server.
base_config_productdir=""
base_config_patchdir=""
# Last one - mainly for developing JumpStart scripts!
# If you set this, the rc3.d/S99jumpstart script will be disabled
# (set to rc3.d/s99jumpstart) every time it is processed - this allows you
# to run it by hand and invoke each reboot step
base_config_debug_jumpstart_postinstall=""
# Product: Custom
# Synopsis: The custom product can install packages and patches that
# would not otherwise be included by the standard
# installation products.
# Which additional packages are to be installed
# (by default, these get added during the main Solaris installation phase)
# O.S. Specific versions:
# as a side effect, if a directory exists under the package dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main package directory
# i.e /export/install/pkgs/custom/sparc/5.8 takes preference over
# /export/install/pkgs/custom/sparc for a Solaris 8 box
# Package Response files:
# If a custom package needs a response file, create a directory called
# /opt/jet/Clients/<clientname>/responses
# and put the response file in to it, named the same as the package.
# i.e. for a package called Fred, on client1, use pkgask to create
# pkgask -r /opt/jet/Clients/client1/responses/Fred Fred
# (Space seperated list of packages)
custom_packages=""
# Custom packages at subsequent boots
custom_packages_1=""
custom_packages_n=""
# Which additional patches are to be installed
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of patches)
custom_patches=""
# Custom patches at subsequent boots
custom_patches_1=""
custom_patches_n=""
# Custom patch sets... create a directory in the patch directory named after
# the set, and put a patch_order file in it, along with the patches...
# (Space seperated list of patch set names)
# N.B. as a side effect, if a directory exists under the patch set dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main patchset directory
# i.e /export/install/patches/patchset/5.8 takes preference over
# /export/install/patches/patchset
custom_patchsets=""
# Custom patchsets at subsequent boots
custom_patchsets_1=""
custom_patchsets_n=""
# Search paths
# The files and scripts sections below will look for source files relative
# to the Clients/<clientname> directory. If you wish to look in other places
# for files, please fill out the search path option below. Items in the
# search path are relative to the Clients/<clientname> directory, since the
# client has no knowledge of the filesystem layout of the server
# e.g. for a client 'fred', the default location for all custom files/scripts
# is /opt/jet/Clients/fred
# if the search path was set to "../common" then the installation routines
# would look first in Clients/fred then
# Clients/fred/../common (or Clients/common in this case)
# Search path is a space separated list of places to search
# THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!
custom_search_path="../common.files"
# Files to be copied to the client. The filenames must be of the form
# filename1:a:filename2
# Where filename1 is the name of the source file in the
# /opt/jet/Clients/<clientname> directory
# filename2 is the full path of the file on the installed client
# and the middle option is whether to a - append, or o - overwrite the file
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of tuples)
# N.B. Please see section above regarding where to place the source files
# N.B. (2):
# appending to /etc/hosts is a special case; instead of just appending
# the file, the module will do an 'intelligent merge' of the new hosts
# file with the existing one.
# custom_files="hosts:a:/etc/hosts"
#custom_files="system:a:/etc/system"
custom_files=""
custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"
# Custom files at subsequent boots
custom_files_n=""
# Scripts to be run on the client at the end of the build
# The scripts must be placed in the directory
# /opt/jet/Clients/<clientname>
# and will be copied to the client.
# Note: we don't allow you to run custom scripts during the Jumpstart
# phase because its kinda dangerous.
# If you need to do this, the best way is to create
# your own custom module to do this.
# Custom scripts at subsequent boots
custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"
custom_scripts_n=""
# Special JumpStart 'Begin' phase scripts
# If you need to run scripts in the 'begin' phase of the JumpStart, you
# can supply them here. Please note, that in the 'begin' phase, the
# new OS has not been installed and the majority of the OS running will
# be read-only from the JumpStart server.
custom_scripts_b=""
nereid-root (483)>

Installed Solaris, No OS-boot sector is recognized.

Hello,
I just installed Solaris 10 11/06 version on x86 Intel pentium. I followed through every steps, ejected the DVD and upon restart ,nothing happens, it mentions press a key to continue and restarts and comes back to the same point.
My assumption is that the menu.lst is not updated or not sure. There is no operating system boot happening,How do you set the bootloader to pick the Solairs Operating System from disk partition C0D0S0, what are the main entries in the menu.lst, is this what i should be doing. I logged via the DVD boot and get a prompt, i tried bootadm and other utilities, any help.
Basically the Solaris is installed but just need to configure the bootloader or bios to recognize Solaris OS is installed. My bios setting points to HDD.
Any help would be great
Thanks
MJ

A couple things you can I'd look at or do. First I'd make sure that your ribbon connected to your hdd is not loose. A bad ribbon, or intermitten one will cause your hdd not being recognized. If you're sure it good then try booting from the installation DVD and at the prompt type the following command:
installgrub
That should reinstall grub for you.
You can also try booting in safe mode and run the following command:
- bootadm update-archive -f -R /a.
That should update your boot archive.
More good grub info is located at:
http://www.sun.com/bigadmin/features/articles/grub_boot_faq.html#q19
Also, if you want to try editing you're copy of /boot/grub/menu.1st. Here's a copy of what mine looks like:
# default menu entry to boot
default 0
# menu timeout in second before default OS is booted
# set to -1 to wait for user input
timeout 10
# To enable grub serial console to ttya uncomment the following lines
# and comment out the splashimage line below
# WARNING: don't enable grub serial console when BIOS console serial
#     redirection is active!!!
# serial unit=0 speed=9600
# terminal serial
# Uncomment the following line to enable GRUB splashimage on console
splashimage /boot/grub/splash.xpm.gz
# To chainload another OS
# title Another OS
#     root (hd<disk no>,<partition no>)
#     chainloader +1
# To chainload a Solaris release not based on grub
# title Solaris 9
#     root (hd<disk no>,<partition no>)
#     chainloader +1
#     makeactive
# To load a Solaris instance based on grub
# title Solaris <version>
#     root (hd<disk no>,<partition no>,x)     --x = Solaris root slice
#     kernel /platform/i86pc/multiboot
#     module /platform/i86pc/boot_archive
# To override Solaris boot args (see kernel(1M)), console device and
# properties set via eeprom(1M) edit the "kernel" line to:
# kernel /platform/i86pc/multiboot <boot-args> -B prop1=val1,prop2=val2,...
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris 10 11/06 s10x_u3wos_10 X86
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
#---------------------END BOOTADM--------------------
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
Message was edited by:
mrmdls
Added a copy of /boot/grub/menu.1st

Install solaris via hyper terminal

Similar Messages

Maybe you are looking for