Sponsored Content
Operating Systems SCO Overwritten /dev/root -recovery of SCO OpenServer 5.0.4 Post 302183113 by jgt on Tuesday 8th of April 2008 09:51:09 AM
Old 04-08-2008
How does it go.... he who play in root eventually kill tree.

Re-install the operating system, add the tape drive, make new boot floppies, then restore the root file system from the backup.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help For SCO OpenServer

I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies

2. UNIX for Dummies Questions & Answers

sco openserver 5.5

hello! when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ? kindly help me thanks (1 Reply)
Discussion started by: buntty
1 Replies

3. UNIX for Advanced & Expert Users

SCO 5.0.2 openserver

I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
Discussion started by: SCOoT
3 Replies

4. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi there guys. I just got this new SCO version and i'm having some problem printing from shell, This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error. /dev/fd/7: /usr/lib/lp/sysv/7: not found. ... (1 Reply)
Discussion started by: josramon
1 Replies

5. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi guys, I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies

6. SCO

sco openserver 5.0.7

Dear members when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config. i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies

7. SCO

sco openserver 5.0.0 boot / root disk

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

8. SCO

I need SCO Openserver 4.2!!!!

I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 Replies

9. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

10. SCO

SCO Openserver 5 root password and disk full

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
BACKUP_STATUS(8)					       AFS Command Reference						  BACKUP_STATUS(8)

NAME
       backup_status - Reports a Tape Coordinator's status

SYNOPSIS
       backup status [-portoffset <TC port offset>]
	   [-localauth] [-cell <cell name>] [-help]

       backup st [-p <TC port offset>]
	   [-l] [-c <cell name>] [-h]

DESCRIPTION
       The backup status command displays which operation, if any, the indicated Tape Coordinator is currently executing.

OPTIONS
       -portoffset <TC port offset>
	   Specifies the port offset number of the Tape Coordinator for which to report the status.

       -localauth
	   Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to
	   the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more
	   details, see backup(8).

       -cell <cell name>
	   Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).

       -help
	   Prints the online help for this command. All other valid options are ignored.

OUTPUT
       The following message indicates that the Tape Coordinator is not currently performing an operation:

	  Tape coordinator is idle

       Otherwise, the output includes a message of the following format for each running or pending operation:

	  Task <task_ID>:  <operation>:   <status>

       where

       <task_ID>
	   Is a task identification number assigned by the Tape Coordinator.  It begins with the Tape Coordinator's port offset number.

       <operation>
	   Identifies the operation the Tape Coordinator is performing, which is initiated by the indicated command:

	   Dump
	       The backup dump command.

	   Restore
	       The backup diskrestore, backup volrestore, or backup volsetrestore commands.

	   Labeltape
	       The backup labeltape command.

	   Scantape
	       The backup scantape command.

	   SaveDb
	       The backup savedb command.

	   RestoreDb
	       The backup restoredb command.

       <status>
	   Indicates the job's current status in one of the following messages.

	   number Kbytes transferred, volume volume_name
	       For a running dump operation, indicates the number of kilobytes copied to tape or a backup data file so far, and the volume
	       currently being dumped.

	   number Kbytes, restore.volume
	       For a running restore operation, indicates the number of kilobytes copied into AFS from a tape or a backup data file so far.

	   [abort requested]
	       The backup kill command was issued, but the termination signal has yet to reach the Tape Coordinator.

	   [abort sent]
	       The operation is canceled by the backup kill command.  Once the Backup System removes an operation from the queue or stops it from
	       running, it no longer appears at all in the output from the command.

	   [butc contact lost]
	       The backup command interpreter cannot reach the Tape Coordinator. The message can mean either that the Tape Coordinator handling
	       the operation was terminated or failed while the operation was running, or that the connection to the Tape Coordinator timed out.

	   [done]
	       The Tape Coordinator has finished the operation.

	   [drive wait]
	       The operation is waiting for the specified tape drive to become free.

	   [operator wait]
	       The Tape Coordinator is waiting for the backup operator to insert a tape in the drive.

       If the Tape Coordinator is communicating with an XBSA server (a third-party backup utility that implements the Open Group's Backup Service
       API [XBSA]), the following message appears last in the output:

	  <XBSA_program> Tape coordinator

       where <XBSA_program> is the name of the XBSA-compliant program.

EXAMPLES
       The following example shows that the Tape Coordinator with port offset 4 has so far dumped about 1.5 MB of data for the current dump
       operation, and is currently dumping the volume named "user.pat.backup":

	  % backup status -portoffset 4
	  Task 4001:  Dump:   1520 Kbytes transferred,	volume user.pat.backup

PRIVILEGE REQUIRED
       The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged
       onto a server machine as the local superuser "root" if the -localauth flag is included.

SEE ALSO
       backup(8), butc(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26							  BACKUP_STATUS(8)
All times are GMT -4. The time now is 12:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy