Sponsored Content
Operating Systems Solaris Using JumpStart to Install LDoms1.1 Post 302281992 by StarSol on Friday 30th of January 2009 01:53:52 AM
Old 01-30-2009
The error I am getting is

checkdir error: cannot create LDoms_Manager-1_1
unable to process LDoms_Manager-1_1/X/X/X/X/X/X/

Where X/X/X/X/X/X/ is every directory underneath it. So the number of errors I am getting equal the number of directories it tries to create.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Sparc 20 Jumpstart install :(

Hello, I'm having all kinds of trouble jumpstarting some SS20's. After hunting around the newsgroups I find that this seems to be a fairly common problem with no real answer. Here's a brief: SS20, 50mhz, 256mb blah blah. - Client E250 blah blah - J/start server. 10/100bt Network.... (4 Replies)
Discussion started by: itsupplies
4 Replies

2. HP-UX

Oracle 9i install: Error in invoking target install of makefile

I receive an error while installing Oracle 9i: Error in invoking target install of makefile /opt/oracle/product/9.2.0/sqlplus/lib/ins_sqlplus.mk Furthermore: $ whoami oracle $ echo $ORACLE_HOME /opt/oracle/product/9.2.0 $ pwd /opt/oracle/product/9.2.0/sqlplus/lib $ ll total... (5 Replies)
Discussion started by: chris2005
5 Replies

3. Linux

install macbook pro fedora10 ???((<<if can install, how to install? >> ))

If may install can Tells everybody ??? (0 Replies)
Discussion started by: kzBSD
0 Replies

4. Solaris

jumpstart install clusters

Hello, I'm trying to jumpstart a machine with Solaris 10, however the disks in my machine are only 18GB, but I want to have all the developer packages but none of the X windows stuff that can be quite large. Wondered if it was possible to somehow get a list of all packages and remove the ones... (4 Replies)
Discussion started by: Actuator
4 Replies

5. Solaris

Jumpstart with ZFS root install

Has anyone tried Jumpstart with installing a ZFS root pool? I have read the docs (Custom Jumpstart and Advanced Install Guide(doc:821-1911);Network-Based Installations(doc:821-1909)). My issue is that I get prompted for information each time I boot the client system. My goal is to get the... (8 Replies)
Discussion started by: bluescreen
8 Replies

6. Solaris

Solaris 10 install dvd drive boots, but not recoginized by install process

I am trying to build a Sun Ultra 10 with solaris 10. This computer is one of a collection that was donated to the non-profic company I work for. All media was wiped before I recieved them, so I am starting from stratch. I downloaded the Solaris 10 ISO and burned a DVD. The computer came with a... (4 Replies)
Discussion started by: gwillhight
4 Replies

7. 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

8. 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

9. Solaris

Issue with jumpstart install

I've followed a few guides and have what appears to be a working jumpstart server. I can PXE boot a bare system, it gets an IP and launches the installer. However, it takes me to the screen: SunOS Release 5.10 Version generic-147148-26 64 bit Copyright (c) 1983, 2013, Oracle and/or its... (1 Reply)
Discussion started by: jnojr
1 Replies
vntsd(1M)						  System Administration Commands						 vntsd(1M)

NAME
vntsd - virtual network terminal server daemon for Logical Domains SYNOPSIS
/usr/lib/ldoms/vntsd DESCRIPTION
The vntsd daemon is a server that supports connections to the Logical Domains (LDoms) console by using telnet(1). When a telnet session starts, vntsd sends telnet options to the client indicating a willingness to remotely echo characters and to suppress go ahead. Consoles are organized into groups by the LDoms Manager. Each console group is assigned a unique group name and TCP port number. vntsd uses the group's port number to export access to the consoles within that group. To establish a connection with a console or console group, a user starts a telnet(1) session with the corresponding group's port number. Depending on the number of consoles within that group, vntsd does one of two things: o If there is only one console in the group, vntsd connects a session to that LDoms console. o If there are multiple consoles in the group, vntsd prompts the user to select the console to which they would like to connect, as shown in "Multiple-Console Options," below. For each console, vntsd provides write access only to the first user connecting to the console. Subsequent users connecting to the console are allowed only to read from the console and wait for write access. When the first user disconnects, write privileges are transferred to the next user waiting in the queue. If a user who does not have write privileges attempts to write to a console, the vntsd displays the following message: You do not have write access A user who has no write access can acquire write access forcibly by using the ~w special console command, described in "Special Console Commands," below. vntsd can be invoked only with superuser privileges or by someone in the Primary Administrator role. OPTIONS
The options for vntsd are divided into multiple-console options and console commands. Multiple-Console Options The options listed below are supported when there are multiple LDoms consoles in a group. The syntax for the use of these options is: <hostname>-vnts-<group-name>: <option> For example: myhost-vnts-salesgroup: h The h option invokes help, as described below. h Display the following help text: h -- this help l -- list of consoles q -- quit c{id}, n{name} -- connect to console of domain {id} or domain name l List all consoles in the group. For example: DOMAIN ID DOMAIN NAME DOMAIN STATE 0 ldg1 online 1 ldg2 connected ... ... ... The two domain states and their meanings are: online No one is connected to the console. connected At least one user is already connected to the console. q Disconnect from vntsd. c{id}, n{name} Connect to specified console. Upon connection, the following message is displayed: Connecting to console <domain-name> in group <group-name> Press ~? for control options .... Special Console Commands A tilde (~) appearing as the first character of a line is an escape signal that directs vntsd to perform a special console command. The tilde-tilde (~~) sequence outputs a tilde. In conjunction with the initial tilde, vntsd accepts the following special console commands: ~. Disconnect from the console or console group. ~w Force write access to the console. ~p Disconnect from this console, and connect to the console that precedes this console in the list of consoles. ~n Disconnect from this console, and connect to the console that follows this console in the list of consoles. ~# Send break. ~? Display vntsd help, as follows: ~# - Send break ~. - Exit from this console ~w - Force write access ~n - Console next ~p - Console previous ~? - Help FILES
/usr/lib/ldoms/vntsd Binary executable vntsd file. /usr/lib/ldoms/vntsd.xml Service management facility (smf(5)) manifest file for vntsd. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWldoms | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
telnet(1), svccfg(1M), usermod(1M), auth_attr(4), attributes(5), smf(5) NOTES
The vntsd is managed by the service management facility, smf(5), under the service identifier: svc:/ldoms/vntsd You can change the following properties using the svccfg(1M) command: vntsd/vcc_device Set an instance of the virtual console concentrator (vcc) driver to which vntsd is connected. vntsd/listen_addr Set the IP address to which vntsd listens, using the following syntax: vntsd/listen_addr:"xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is a valid IP address. The default value of this property is to listen on IP address 127.0.0.1. Users can con- nect to a guest console over a network if the value is set to the IP address of the control domain. Note - Enabling network access to a console has security implications. Any user can connect to a console and for this reason it is disabled by default. vntsd/timeout_minutes Set timeout in minutes. vntsd will timeout (close) telnet connection if there is no activity (input or output) on the console. The default value is 0, which disables timeout. vntsd/authorization Enable the authorization checking of users and roles for the domain console or consoles that are being accessed. The default value of this property is false to maintain backward compatibility. To enable authorization checking, use the svccfg(1M) command to set the property value to true. While this option is enabled, vntsd listens and accepts connections on localhost. If the listen_addr property specifies an alternate IP address when this option is enabled, vntsd ignores the alternate IP address and continues to listen on local- host. Connections that are initiated from other hosts will also fail. Authorizations are available to access all consoles or console groups, or to access specific consoles or console groups. When the vntsd service is enabled, the following authorization is added to the authorization description database, auth_attr(4): solaris.vntsd.consoles:::Access All LDoms Guest Consoles:: Add any fine-grained authorizations based on the name of the console group. For example, if the name of the console group to be autho- rized is ldg1, add the following entry to the auth_attr(4) file: solaris.vntsd.console-ldg1:::Access Specific LDoms Guest Console:: By default, the authorization to access all consoles is assigned to the root user or role. The Primary Administrator (superuser) can use the usermod(1M) command to assign the required authorization or authorizations to other users or roles. The following example gives user user1 the authorization to access all domain consoles: # usermod -A "solaris.vntsd.consoles" user1 The following example gives user user1 the authorization to access the console group named ldg1: # usermod -A "solaris.vntsd.console-ldg1" user1 SunOS 5.11 13 Feb 2009 vntsd(1M)
All times are GMT -4. The time now is 03:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy