10-30-2008
Well, the /etc/default/boot file has the following:
DEFBOOTSTR=hd(40)unix swap=hd(41) dump=hd(41) root=hd(42)
AUTOBOOT=YES
FSCKFIX=YES
MULTIUSER=YES
PANICBOOT=NO
MAPKEY=YES
SERIAL8=NO
SLEEPTIME=0
BOOTMNT=RO
apm.connect=no
I don't know enough about this file and where to make the changes to include the boot levels. Can you explain or tell me anything from seeing what I listed?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am currently running SCO OpenServer.
When the machine is restart it automatically intitiates processes that allow me to use the ARCserv backup software... Recently, these process were killed and I would like to restart them. The problem is I dont know the name or location of the files invoked... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
2. UNIX for Dummies Questions & Answers
Hi guys,
May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro.
Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies
3. UNIX for Advanced & Expert Users
Hello there
I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager".
I thought i could do this simply putting the script in "/sbin/init.d,
and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies
4. UNIX for Dummies Questions & Answers
Hi all
The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated.
Bios 03.0
0130688 KB memory good
01 processor(s) in system
remote console dialing on, please wait
connect fail : modem off
cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies
5. UNIX for Dummies Questions & Answers
Evry time I start up my mavhine ,have to type in unix at
Boot
:
Is there a way unix should bootup automatically?
Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies
6. UNIX for Dummies Questions & Answers
Does anyone know it it is possible to start a program with a timeout, so that it is automatically killed if the timeout expires? If yes, how? (6 Replies)
Discussion started by: soheil.samii
6 Replies
7. Solaris
Does anyone know how I stop nfs/lockd and all of the associated services from starting at bootup? There's nothing in the /etc/rc*.d files to rename. That was my first idea. I also tried renaming /etc/init.d/nfs.server to something else, but that did not work either.
Any ideas would be greatly... (2 Replies)
Discussion started by: amheck
2 Replies
8. AIX
Hello,
I'm having a problem starting the cron daemon automatically from inittab, let me provide the details below:
We are having five equally installed machines. One of them was upgraded in the past, one we upgraded recently, both from 5300-05-06 to 5300-07-01-0748. On the upgraded... (6 Replies)
Discussion started by: hybr1d
6 Replies
9. UNIX and Linux Applications
hi
I have created autosys job but its not auto starting , also tried job control > start job but doesn't start that way only way it starts is force_startjob. why ? :(
thanks (0 Replies)
Discussion started by: user0489
0 Replies
10. UNIX for Dummies Questions & Answers
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)