01-22-2010
giving it a go now, thanks for the link.
10 More Discussions You Might Find Interesting
1. SCO
Hi,
I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone.
I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies
2. SCO
New IBM x3400 machine with a raid 5 configuration. Go through the early setup routine to the point where I answer the questions for time zone, machine name. Enter continue and get a message stating :
"Incorrect disk partitioning cannot continue" This is a sco message, refers to the installation... (1 Reply)
Discussion started by: wjbtms
1 Replies
3. Solaris
Hi,
I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below:
/pci@8,600000/SUNW,qlc@2
LiD HA LUN --- Port WWN --- ----- Disk description -----
0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies
4. SCO
hi all
i use sco open server reliseas 5 on my system i get an image from system hard disk to another hard disk with acronis software and start system with new(backup)hard disk, but during the boot process some errors generate as follow
warning:hd:noroot disk controler was found
hd:a boot-time... (2 Replies)
Discussion started by: mehran_malek
2 Replies
5. SCO
hi...
i hav a problem to install sco unix
while installing sco unix 5.0.5 in acer altos with hardware raid
am getting error
"Warning HD: no root disk controller was found
system error 5: while getting fs type
flushing controller: DAC960PRL cache done."
i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies
6. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
7. SCO
Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies
8. SCO
Hi,
We have an old SCO Openserver 5.0.7 server that I have inherited that currently has two issues that we are trying to resolve.
1. We do not know the root password. I have contacted the old admin, looked for rescue disk and documentation but there appears to be nothing.
I have tried... (1 Reply)
Discussion started by: acerimmer10
1 Replies
9. Solaris
Hi
The scenario in the oracle t4-1 hardware with solaris 10 is as follows:
1. The initial install on the server was performed with an incorrect disk layout.
2. New disks were ordered and slot into the server.
3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies
10. SCO
I am working on a system that uses SCO Unix 5. I started later in this troubleshooting process so I have had to play catch up on some of the earlier mistakes that were made.
The HD was formatted using the SCSI controller cards bios.
I have 2 recovery floppies the boot and the root.
After... (19 Replies)
Discussion started by: graysona
19 Replies
LEARN ABOUT OPENSOLARIS
link
link(1M) System Administration Commands link(1M)
NAME
link, unlink - link and unlink files and directories
SYNOPSIS
/usr/sbin/link existing-file new-file
/usr/xpg4/bin/link existing-file new-file
/usr/sbin/unlink file
DESCRIPTION
The link and unlink commands link and unlink files and directories. Only super-users can use these commands on directories.
Use link to create a new file that points to an existing file. The existing-file and new-file operands specify the existing file and
newly-created files. See OPERANDS.
link and unlink directly invoke the link(2) and unlink(2) system calls, performing exactly what they are told to do and abandoning all
error checking. This differs from the ln(1) command. See ln(1).
While linked files and directories can be removed using unlink, it is safer to use rm(1) and rmdir(1) instead. See rm(1) and rmdir(1).
/usr/xpg4/bin/link
If the existing file being hard linked is itself a symbolic link, then the newly created file (new-file) will be a hard link to the file
referenced by the symbolic link, not to the symbolic link object itself (existing-file).
OPERANDS
The following operands are supported:
existing-file Specifies the name of the existing file to be linked.
file Specifies the name of the file to be unlinked.
new-file Specifies the name of newly created (linked) file.
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of link: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
/usr/xpg4/bin/link
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWxcu4 |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO
ln(1), rm(1), link(2), unlink(2), attributes(5), environ(5), standards(5)
SunOS 5.11 9 Oct 2002 link(1M)