07-11-2001
Yes, you need a boot disk.
As a minimal, you should read the documentation for suggestions on how to partition your disks. I would suggest that you need to find the documentation for your SCO distribution.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How, where from and which UNIX or LINUX can I download so that I can use it normally working on 386 SX 4MB RAM.
I want to use only its basic functions and C and C++ compiler on it.
I need it for my studies.
P.S I need a stable UNIX or LINUX including a full set of
functions of C... (4 Replies)
Discussion started by: Traiancho
4 Replies
2. UNIX for Dummies Questions & Answers
where can i get a boot diskette for my old SCO UNIX V/386 (3 Replies)
Discussion started by: LEO P. CAPARAS
3 Replies
3. UNIX for Dummies Questions & Answers
I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies
4. Programming
hello!i have a 8 year old computer.it's 386dx, 40mhz,4mb edo ram,and it has 400mb hd.i'm looking for unix or linux which can work on my computer.if you know where can i find it please help me.if you have one please send it to ilovebasic@yahoo.com. (4 Replies)
Discussion started by: kfjfgkþo
4 Replies
5. UNIX Desktop Questions & Answers
Hey, can anyone recommend a URL (or website) where I can download a basic (or old) UNIX OS that will run on an ancient laptop that has a 386 processor, 4MB of RAM and a 40MB harddrive? Your help and suggestions are much appreciated! :confused: (4 Replies)
Discussion started by: methudrez
4 Replies
6. SCO
anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Discussion started by: format
5 Replies
7. UNIX for Advanced & Expert Users
We have a C program which does the encryption and decryption. It is running fine in UNIX 386. But the same C program is giving different results in HP UX server.
We found that the Ascii codes (output) are different. I don;t know why it is giving different results. How can we get the same output... (4 Replies)
Discussion started by: Rajeshsu
4 Replies
8. UNIX for Dummies Questions & Answers
I have already learned everything possible from windows or all that I at least care to learn and am now looking to move onto unix. My problem is that I have never used unix nor do I know anyone who has. If anyone could give any clues to what version/make of unix would be best on an old 386 box then... (7 Replies)
Discussion started by: tabodi
7 Replies
9. SCO
Hi i have a problem after boot with N1 disk and putting N2 disk and pressing the enter in this message:Insert N2(filesystem) floppy and press after by this(pressing enter) the system is reboot!! why??? :confused:
my old pc is a Pentium II 333mhz 3gb hd 64mb ram
please help!! :( (3 Replies)
Discussion started by: panos_pit
3 Replies
10. SCO
Hi to all! I'm new here.
Recently I bought an Olivetti M400/10 with SCO System V/386 R3.2 V4.0 installed, complete with all disks and manuals.
Checking the distribution disks however I found that disk labeled B2 was unreadable. Does anyone have an image of this disk?
I wish to do a clean... (7 Replies)
Discussion started by: wisechip
7 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)