Sponsored Content
Full Discussion: Issue during boot
Operating Systems SCO Issue during boot Post 303005167 by jgt on Saturday 14th of October 2017 12:53:37 PM
Old 10-14-2017
Dev 1/42 is the root file system. It is almost always a HTFS file system and there are no other operating systems that support this type.
Even if you do not have 5.0.7 installed, you may be able to run fsck by booting from a 5.0.7 cd that you can download from here Xinuos Inc. | Support | Update | Download | Support
You must copy the .iso to a CD, a DVD will not work.
Boot from the CD and type "tools" at the Boot: prompt.
This User Gave Thanks to jgt For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot up issue

Could somone please tell me what happened when I reboot my computer, it take too long to pass the part it said "starting sendmail" I only changed the server name and when I reboot the server, all of the services are running except when it got to : starting sendmail it take toooo long to... (1 Reply)
Discussion started by: lapnguyen
1 Replies

2. UNIX for Advanced & Expert Users

Dual boot issue

Hi All, 1st HDD is loaded with Windows 2000 Professional and I have installed Red Hat ES 3.0 on second HDD(80GB). After linux installation failed to load windows and boot stucks with displaying only L How to fix this issue Thanks in advance for your valuable answer. Regards, Bachegowda (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies

4. HP-UX

hp-ux 10.20 boot issue

Hello, have HP Visualize C3600 workstation. Issue is as follows: When I attempt to boot, unit will not boot successfully and will halt at a menu, the same menu as when during a boot one hits any key within 10 seconds to discontinue. When I attempt to boot with Boot primary, both with IPL... (17 Replies)
Discussion started by: davel1000
17 Replies

5. Solaris

boot-archive issue

I had logged into Server via ALOM and was placed into runlevel 5 other than 3 which is default. I did a svcadm delete boot-archive, and was promptly placed in runlevel 3. Now, I am unable to do a telnet or login into the server through any other service. bash-3.00# svcs -a svcs -a STATE ... (3 Replies)
Discussion started by: praveenr
3 Replies

6. Solaris

Solaris-RHEL5 Dual boot issue

Machine: x86 OS : Dualboot Solaris and RHEL5 -Solaris 10 in first fdisk partition. RHEL5 - /boot in partition2 / in partition3 swap in 1st... (1 Reply)
Discussion started by: saagar
1 Replies

7. Red Hat

Dual boot issue .....

Hi, I have a laptop with two os running in it, Windows XP & RHEL5. Accidentally, we have deleted the windows entry in grub.conf file. Later we connected the hard disk of laptop to another system & deleted the linux partitions from the disk management tool of windows. Now the issue is, the... (7 Replies)
Discussion started by: Amol21
7 Replies

8. Solaris

Boot parameter issue

Hi all i have an issue when i change auto-boot?=false and reboot it again it is going to auto-boot?=true can any one tell that what should i do for auto-boot?=false for permanently thank you in advance (11 Replies)
Discussion started by: wkbn86
11 Replies

9. Solaris

Persistent boot disks issue

Hi all, please i need your help urgently I am faced to a serious boot disks issue on an Sun Fire E2900. The system run with two disque in zpool . The operating system is Solaris 10 (ZFS) The first time the issue occured, i got the error below on the two disks: Apr 7 08:04:33... (0 Replies)
Discussion started by: saki_jumeau
0 Replies

10. Solaris

V100 boot issue

In the server room at my new job, there is a V100 with a problem. When power is turned on, the machine goes to the lom prompt. Entering poweron yields an endless supply of this message with no way to break out of it. ********************************************** PSTATE=0000000000000015... (3 Replies)
Discussion started by: chilinski
3 Replies
patchsvr(1M)						  System Administration Commands					      patchsvr(1M)

NAME
patchsvr - set up a Sun Update Connection Proxy SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l] [-p update-source-url] [-s pw-file-location] [-u user-name] [-x web-proxy- host:port] /usr/sbin/patchsvr start /usr/sbin/patchsvr stop /usr/sbin/patchsvr enable /usr/sbin/patchsvr disable DESCRIPTION
The patchsvr command enables you to set up a Sun Update Connection Proxy on your intranet. The setup subcommand configures the Sun Update Connection Proxy. The start and stop subcommands start and stop the Sun Update Connection Proxy. Finally, the enable and disable subcom- mands permit you to start up and prevent startup of the Sun Update Connection Proxy at boot time. The Sun Update Connection Proxy was previously called local patch server. Note - The Sun Update Connection Proxy supports client systems that use the Sun Update Connection, System Edition software and the Sun Patch Manager 2.0 software. A Sun Update Connection client system is not compatible with the older local patch server feature asso- ciated with the Sun Patch Manager 2.0 software. Configuring Your Sun Update Connection Proxy By default, Update Manager expects that your local systems are connected, via the Internet, to the Sun update server to be analyzed and to receive updates. By using a Sun Update Connection Proxy instead, you can minimize the Internet traffic and serve your local systems from a update server on your intranet. The system you choose to act as the Sun Update Connection Proxy must be running at least the Developer Solaris Software Group of the Solaris 10 Operating System. You must also install the Sun Update Manager 1.0 software and the Sun Update Connection Proxy software. The use of a Sun Update Connection Proxy addresses security concerns and reduces the amount Internet traffic between the Sun update server and your client systems. For instance, instead of having to download updates and metadata from the Sun update server to each of your systems, the data is downloaded to the Sun Update Connection Proxy the first time that a client system requests an update. After the update data is stored on your Sun Update Connection Proxy, the transfer of update data to your system for analysis is done over your intranet instead of over the Internet. You can configure a chain of update servers on your intranet. The last link in the chain of local servers can point to the Sun update server or to a local collection of updates. By using this chain of servers, an update download request from your system to its primary update server can be forwarded to other servers in the chain in an attempt to fulfill the request. So, if your system's primary server can- not locate an update, the server makes the same request of the next server in the chain to see if the update is stored there. If the update is found, it is downloaded to the system. If the update is not found, the request continues along the chain until the update is found or the terminal point in the chain is reached. Each server in the chain stores the updates found on another server in the chain based on the download request. So, an update that is not initially found on your local server will be downloaded to your local server and stored before being downloaded to the client system. Your Sun Update Connection Proxy must specify the source of updates to use. By default, the server obtains updates from the Sun update server, but it can also obtain updates from another update server in the chain or from a collection of updates on your system. You must specify the URL that points to the collection of updates. By default, the Sun update server is the source of updates. The URL is: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. This URL must point to another server in the chain or to a collection of updates on the local system. This URL cannot be null. Starting and Stopping Your Sun Update Connection Proxy The patchsvr start command starts the Sun Update Connection Proxy. You can also enable the boot-time startup of the Sun Update Connection Proxy by running patchsvr enable. The patchsvr stop command stops the Sun Update Connection Proxy. You can also disable the boot-time startup of the Sun Update Connection Proxy by running patchsvr disable. Before you use your Sun Update Connection Proxy for the first time, you must run the patchsvr start command. Use these commands when you want to change the configuration of your Sun Update Connection Proxy. Before you use the patchsvr setup command to change the configuration parameter values, you must stop your Sun Update Connection Proxy. Then, you can update the configuration val- ues. Finally, you must restart the Sun Update Connection Proxy. OPTIONS
The following options are supported for the patchsvr setup command: -c cache-location Specifies the location of the server's cache, also known as the update repository. This is the directory in which downloaded updates are stored on the Sun Update Connection Proxy. You must specify a full path to the cache loca- tion. By default, the cache location is file:/var/sadm/spool/patchsvr. Ensure that this update repository has 2 Gbytes of free disk space available to store downloaded updates. -d Resets the Sun Update Connection Proxy configuration settings to the default values. -h Displays information about the command-line options. -l Lists the configuration settings for the update server. -p update-source-url Specifies the URL that points to the collection of updates. By default, the URL points to the Sun update server: https://getupdates.sun.com/solaris/ Note that this URL must appear as a single line. -s pw-file-location Specifies the path of the proxy password file in which you have stored your proxy password. You must put the password in a file rather than specifying it on the command line because command-line information is visible via the ps command. -u user-name Specifies the user name required for web proxy authentication. -x web-proxy-host:port Specifies the local web proxy. If the Sun Update Connection Proxy is behind a firewall, use this option to specify the web proxy that accesses the Internet. Get the name of the web proxy, web-proxy-host, and its port, port, from your system administrator or network administrator. The default port value is 8080. Do not use this option if you are accessing update data from a collection of updates on the Sun Update Connection Proxy. EXAMPLES
Example 1: Changing the Cache Location # patchsvr setup -c /var/update/cache Example 2: Specifying the Sun Update Server as the Source of Updates # patchsvr setup -p https://getupdates.sun.com/solaris/ The Sun update server is the default source of updates. Example 3: Specifying a Sun Update Connection Proxy as the Source of Updates # patchsvr setup -p http://updatesvr1:3816/solaris/ Specifies the system called updatesvr1, a Sun Update Connection Proxy, as the source of updates. Example 4: Specifying a CD as the Source of Updates # patchsvr setup -p file:/cdrom/cdrom0 Specifies the CD mounted from the first CD-ROM drive of the local system as the update source. Example 5: Specifying a Web Proxy # patchsvr setup -x webproxy:8080 Specifies the host name, webproxy, and port, 8080, of the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Example 6: Specifying a User Name and Password for Web Proxy Authentication # (umask 77 ; vi /tmp/password) # patchsvr setup -u terry -s /tmp/password # rm /tmp/password While in a subshell, you create a temporary file that is not readable by others and put the password in that file. Next, you specify the user name, terry, and location of the password file, /tmp/password, used to authenticate the web proxy that your Sun Update Connection Proxy uses to connect to the Internet. Then, you delete the temporary file now that the web proxy authentication is specified. Example 7: Resetting the Configuration Settings to the Default Values # patchsvr setup -d Example 8: Listing the Configuration Settings for Your Sun Update Connection Proxy # patchsvr setup -l Patch source URL: https://getupdates.sun.com/solaris/ Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080 Shows the configuration settings, which include information about the source of updates, the location of the cache directory, and, if needed, a web proxy and port. Example 9: Starting the Sun Update Connection Proxy # patchsvr start Example 10: Stopping the Sun Update Connection Proxy # patchsvr stop Stops your Sun Update Connection Proxy. While the update server is stopped, you can change the configuration settings for your Sun Update Connection Proxy, then restart it. Example 11: Enabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr enable Example 12: Disabling the Boot-Time Startup of the Sun Update Connection Proxy # patchsvr disable ATTRIBUTES
See the attributes(5) man page for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWpsvru | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
smpatch(1M), attributes(5) Sun Update Manager 1.0 Administration Guide SunOS 5.10 12 May 2005 patchsvr(1M)
All times are GMT -4. The time now is 04:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy