Sponsored Content
Full Discussion: poewr management problem
Top Forums UNIX for Dummies Questions & Answers poewr management problem Post 29099 by RTM on Monday 30th of September 2002 09:18:50 AM
Old 09-30-2002
If it's at the ok prompt because of a Stop-A key sequence or break, you can type the word 'go' (no quotes). If the system crashed, then type 'boot'.

Look in /etc/rc2.d for the power management startup and disable it by moving it's startup script to begin with a lowercase s instead of uppercase S.
 

8 More Discussions You Might Find Interesting

1. Linux

Resource management

Hi all, we have a big problem, we are running an IA-64 linux system, with 8 CPUs and some GB of RAM, for user usage. The user are compiling and testing programs on this system, and this caused some problems. Sometimes, a user program used the hole memory, blocks the other users, and also... (1 Reply)
Discussion started by: malcom
1 Replies

2. UNIX for Advanced & Expert Users

Query Management

Is there any good query management systems that run on Linux and/or Solaris? I'm looking at KBugBuster and Bugzilla, and was wondering is there any others worth considering that run on these platforms? Txs (2 Replies)
Discussion started by: Breen
2 Replies

3. What is on Your Mind?

Configuration Management

Not sure where to post this so I placed it here. Anyone have any experience with cccHarvest 5.1 or AllFusion Harvest Change Manager 5.1? I have to put together a plan to move from PVCS to Harvest/AllFusion and I dont know much at all about the latter. Any help, information, or links would be... (3 Replies)
Discussion started by: google
3 Replies

4. AIX

AIX software management problem

Hi to all please help ...Acutally i m new in AIX. I dont much know about AIX. I m totally confusing with software management chapter. Actually i m not getting difference between. LPP,,BUNDLE,,,PACKAGE,,FIXES,,,APAR,,,,,FILESET..... i read in the book.......as i know about RPM in linux.....but in... (2 Replies)
Discussion started by: life008
2 Replies

5. UNIX and Linux Applications

Password management / centralized password management

Hello all, I need help for build server call as Password management / centralized password management server. My situation and example: I have 600 server in my server room running on Linux then I need 1 server only can create login/password and then user can login to all 600 server no... (2 Replies)
Discussion started by: sheikh76
2 Replies

6. IP Networking

IP Management

Hello all, I was wondering which way do you use to manage you IPs? For example in our case we have excel sheets and we export them in html first and import it to a server running apache, so to be visible from all. But i was wondering if there are any way (prefer a way running in web server)... (2 Replies)
Discussion started by: @dagio
2 Replies

7. UNIX for Advanced & Expert Users

Password management

You know those lists of "the most common passwords"? I was looking at one of those because I actually want to use a really common password or two on occasion. The thing is I'm skeptical that these are legitimate lists. Most things these days require at least 8 chars with a numeral. But these lists... (1 Reply)
Discussion started by: jutnobs
1 Replies

8. What is on Your Mind?

Individual Risk Management (Personal IT Security) and Browser Cache Management

Original post from this thread on browser caching. To add to this, it is an effective security measure to clear absolutely all cached data (cookies, web content, ....) when closing the browser - i.e. in case of a shutdown. It takes a bit of work to re-login to all the sites but websites will not... (7 Replies)
Discussion started by: bakunin
7 Replies
BOOT(8) 						      System Manager's Manual							   BOOT(8)

NAME
boot - startup procedures DESCRIPTION
A PDP11/45 and PDP11/70 UNIX system is started by a two-stage process. The first is a primary bootstrap which is able to read in rela- tively small stand-alone programs; the second (called boot) is used to read in the system itself. The primary bootstrap must reside in the otherwise unused block zero of the boot device. It can be read in and started by the standard ROM programs, or if necessary by keying in a small startup routine. This program is capable of loading type 407 executable files (not shared, not separate I&D). The user types on the system console the name of the program wished, in this case boot, followed by a carriage return; the named program is retrieved from the file system that starts at block 0 of drive 0 of the boot device. No prompt is given, no diagnos- tic results if the file cannot be found, and no provision is made for correcting typographical errors. The second step, called boot, actually brings in the system. When read into location 0 and executed, boot sets up memory management, relo- cates itself into high memory, and types a `:' on the console. Then it reads from the console a device specification (see below) followed immediately by a pathname. Boot finds the corresponding file on the given device, loads that file into memory location zero, sets up mem- ory management as required, and calls the program by executing a `trap' instruction. Normal line editing characters can be used. Conventionally, the name of the secondary boot program is `/boot' and the name of the current version of the system is `/unix'. Then, the recipe is: 1) Load block 0 of the boot device by fiddling with the console keys as appropriate for your hardware. If you have no appropriate ROM, some programs suitable for manual use are given below. 2) Type boot. 3) When the prompt is given, type hp(0,0)unix or rp(0,0)unix depending on whether you are loading from an RP04/5/6 or an RP03 respectively. The first 0 indicates the physical unit number; the second indicates the block number of the beginning of the logical file system to be searched. (See below). When the system is running, it types a `#' prompt. After doing any file system checks and setting the date (date(8)) a multi-user system is brought up by typing an EOT (control-d) in response to the `#' prompt. Device specifications. A device specification has the following form: device(unit,offset) where device is the type of the device to be searched, unit is the unit number of the device, and offset is the block offset of the file system on the device. Device is one of the following rp RP03 hp RP04/5/6 rk RK05 For example, the specification hp(1,7000) indicates an RP03 disk, unit 1, and the file system found starting at block 7000 (cylinder 35). ROM programs. The following programs to call the primary bootstrap may be installed in read-only memories or manually keyed into main mem- ory. Each program is position-independent but should be placed well above location 0 so it will not be overwritten. Each reads a block from the beginning of a device into core location zero. The octal words constituting the program are listed on the left. RK (drive 0): 012700 mov $rkda,r0 177412 005040 clr -(r0) / rkda cleared by start 010040 mov r0,-(r0) 012740 mov $5,-(r0) 000005 105710 1: tstb (r0) 002376 bge 1b 005007 clr pc RP (drive 0) 012700 mov $rpmr,r0 176726 005040 clr -(r0) 005040 clr -(r0) 005040 clr -(r0) 010040 mov r0,-(r0) 012740 mov $5,-(r0) 000005 105710 1: tstb (r0) 002376 bge 1b 005007 clr pc FILES
/unix - system code /usr/mdec/rpuboot, /usr/mdec/hpuboot - copies of primary bootstrap /boot - second stage bootstrap SEE ALSO
init(8) BOOT(8)
All times are GMT -4. The time now is 03:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy