Sponsored Content
Operating Systems Solaris jumpstart Solaris 10 on Solaris 9 server Post 302158257 by System Shock on Monday 14th of January 2008 07:49:33 PM
Old 01-14-2008
You can have Solaris 8,9,10 images on a jumpstart server with Sol8, 9, 10 and be able to jump boxes.
It looks like the jumpstart can't find your sysidcfg file, or sysidcfg is not complete. Check the contents of the file and make sure that all variables are defined, and check the location of the file and see if it matches /etc/bootparams
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 Jumpstart Problem

Hi Everyone, Thanks in advance for reading my thread. I am not very familiar with Unix so please bear with me if I say anything stupid. I have a SunFire V100 server with Solaris 8, which I made into a Boot/Install/Profile server. Recently, I re-install the V100 box with Solaris 10. The... (5 Replies)
Discussion started by: cityshrimp
5 Replies

2. UNIX for Advanced & Expert Users

solaris 9 using jumpstart to restore

Hello All, I use flar to install servers. I am not sure why it does not restore my hostname.bge0, hostname.bge1, ... from the same server with quad NIC card. Right now, I use a shell script to copy my networking information. Am I doing anything wrong or is flar behaving the way it is suppose... (1 Reply)
Discussion started by: afadaghi
1 Replies

3. Solaris

Jumpstart solaris

Hi all , I am trying to jumpstart ( webstart) solaris 9 on E2900 ( client) using the DVD of a V440 server ( jumstart server). I did the setup for the V440 as follows : cleaning up preexisting install client "XXXXXXX" removing XXXXXXXfrom bootparams removing /etc/bootparams, since it is... (14 Replies)
Discussion started by: ppass
14 Replies

4. Solaris

Jumpstart Solaris 10 x86

I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install. I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part. So, what... (2 Replies)
Discussion started by: alias.256
2 Replies

5. Solaris

Jumpstart Solaris 10

Hello everyone, I tried to install solaris 10 using the command # boot net - install. I take the image correctly but when you start installing the Operating system installation takes a long (4 hours I have left and not advancing but not send me any errors), it can be seen from the following: ... (7 Replies)
Discussion started by: yflores
7 Replies

6. Solaris

Jumpstart Solaris 10

I have a laptop and need to build an Oracle Linux kickstart server and a Solaris Jumpstart server that can build sparc and x86 systems. Is the best way to create a dual boot from grub for Oracle Linux and Solaris x86? Can the Oracle Kickstart be used as a Jumpstart to build both Solaris 10... (2 Replies)
Discussion started by: Gian
2 Replies

7. Solaris

Solaris 10 JumpStart Server

Hello, Can anyone share a good online article/tutorial on how to properly set up JumpStart server for Solaris 10? Thanks, Regards. (3 Replies)
Discussion started by: NewSolarisSquad
3 Replies

8. Solaris

Solaris jumpstart install server

I am attempting to install Solaris 10, on a SPARC platform, from a Solaris install server running under Oracle Virtual Box (x86 platform) solarisbox1 is server with IP 10.1.1.21 solarisbox2 is client with IP 10.1.1.60 Snoop gives me the following .. solarisbox1 -> (broadcast) ARP C who is... (0 Replies)
Discussion started by: robs2015
0 Replies

9. Solaris

How to install an JumpStart Server on Solaris 11.3?

Hey Guys, i'm trying to install and configure a jumpstart server on a solaris 11.3 x86 based system. I've already created the folders to install the server. I've tried to use the installation script as follow (i'm root on the system): ./setup_install_server /export/jumpstart Everything works... (2 Replies)
Discussion started by: Marcusg562
2 Replies
kdmconfig(1M)						  System Administration Commands					     kdmconfig(1M)

NAME
kdmconfig - configure or unconfigure keyboard, display, and mouse options for OpenWindows and internationalization SYNOPSIS
kdmconfig kdmconfig [-fv] [-s hostname] -c | -t | -u | -d filename DESCRIPTION
The kdmconfig program configures or unconfigures the /etc/openwin/server/etc/OWconfig file with the keyboard, display, and mouse informa- tion relevant to a client's machine on x86 based systems for Solaris software. kdmconfig can also be used to set up the display, pointer, and keyboard entries in the bootparams(4) database on a server machine or the monitor, keyboard, display, and pointer keywords in a sysid- cfg(4) file. kdmconfig can only be run by the super-user. Upon completion of device selection, kdmconfig prompts the user to test the con- figuration, which is done by running the window system. The kdmconfig program is normally run during installation and upon reboot, but it can also be run from the command line after the system has been installed. When configuring a client during an initial installation or a reconfigure reboot, the sysidconfig(1M) program will invoke kdmconfig with the -c option, and when the user executes the sys-unconfig(1M) program, kdmconfig will be executed with the -u option. Similarly, when you run kdmconfig from the command line, use the -u option to unconfigure the existing OpenWindows configuration. You can then rerun kdmconfig with the -cf options to create a new OpenWindows configuration. To edit the existing configuration, run kdm- config from the command line without options. After each reboot, kdmconfig will be invoked by the system with the -t (test mode) option to ensure autoconfiguration capability and identify possible conflicts between the current configuration and the one recorded in the OWconfig file. OPTIONS
The valid options are: -c Run the program in the configuration mode. This mode is used to create or update the OWconfig file. When invoked in this way, kdmconfig first looks for the relevant configuration information in the bootparams(4) databases. It also takes into account the information returned from device probes, unless the -s option is also used. The bootparams(4) databases avail- able to the client are all of the /etc/bootparams files on servers on the same subnet as the client, provided the server machine is running the bootparamd(1M) daemon. kdmconfig is invoked with the -c option when called by sysidconfig(1M) -d filename Set up a sysidcfg(4) file. This option displays the same screens as the -c option, but the information you specify is saved as sysidcfg(4) keywords (monitor, keyboard, display, and pointer). This enables you to use a sysidcfg(4) file to precon- figure a system's device information and bypass kdmconfig during an installation. filename is the sysidcfg(4) file that is created, and it is created in the directory where kdmconfig is being run unless a path is specified. If filename already exists in the specified directory, the keywords are appended to the existing file. -f Force screens mode. When this option is invoked, no network probing will be performed. This is helpful when debugging the client's configuration environment. Note that the -s option implies the use of -f, bypassing network probing when setting up a server. -s hostname Set up the bootparams(4) database on this machine for the specified client. This option presents the same screens as it does when run on a client, but instead writes the resulting information to the /etc/bootparams file. Also, -s implies the use of the -f option. That is, the program will always present the screens to the user when invoked this way. This option will reconfigure the nsswitch.conf( 4) file to look for a bootparams(4) database on a local server. This option is only available to the super-user. -t Run the program in test mode. In this mode, kdmconfig will use device probe information to determine whether the OWconfig file contains complete and up-to-date information about the keyboard, display, and mouse. If the information is accurate, kdmconfig will exit silently. Otherwise, kdmconfig will prompt for the super-user password and proceed to a normal editing session (as though it had been run without options). -u Unconfigure the system, returning it to an "out-of-the-box" state. In this state, the factory default keyboard, mouse, and display are selected as a result of removing the device configuration entries from the /etc/openwin/server/etc/OWconfig file. This may result in an unusable configuration for the display server. -v Enable verbose mode. Normally, kdmconfig will not produce any output. This option is helpful for debugging, as it records the different actions taken by kdmconfig on stderr. No Options Run without options, kdmconfig is used to edit the current configuration. kdmconfig uses the information from the OWconfig file in addi- tion to information obtained from the bootparams(4) file and from device probes. In other respects, it is similar to using the -c option of kdmconfig. FILES
/etc/openwin/server/etc/OWconfig OpenWindows configuration file /etc/bootparams contains list of clients that diskless clients use for booting /etc/nsswitch.conf name service configuration file x86 Only /dev/openprom installed devices and properties ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWos86r | +-----------------------------+-----------------------------+ SEE ALSO
bootparamd(1M), sys-unconfig(1M), sysidconfig(1M), bootparams(4), nsswitch.conf(4), sysidcfg(4), attributes(5) SunOS 5.10 12 Feb 1997 kdmconfig(1M)
All times are GMT -4. The time now is 02:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy