Sponsored Content
Operating Systems SCO Virtualization a bare metal SCO Open Server 6? Post 303011312 by jgt on Tuesday 16th of January 2018 12:54:02 PM
Old 01-16-2018
The software is locked using a technique called inode locking.
When activation occurs, the inode number of one of the files is made data in a file. It is difficult (but not impossible) to change the inode number of a file,
As long as you do sector mode copying, you can replace the disk.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sco open server 5.0.6

I'm new to the whole Unix thing and have inherited a network running Macs, Windows 2000 and Unix. The Unix side is very suspect at this point and I want to change out the server. I'd love to use one of the new Apple servers but can't find any info on what "flavors" of Unix it will run. Specificly... (3 Replies)
Discussion started by: matthewd
3 Replies

2. UNIX for Advanced & Expert Users

SCO Open Server 5.05 Installaltuion

I'm in the process of installing SCO Open Server 5.05 on the following platform: Hardware: IBM 300PL 64 MB RAM Yamaha 16/4/16 CDRW (Internal defined on SCSI ID 3 LUN 0) I'm able to boot from the CD and advance to the Installation screen but when it asks for where the media source will... (3 Replies)
Discussion started by: budrito
3 Replies

3. SCO

SCO Open Server.

Dear All, I am considering installing SCO Open Server as an alternative to MS Exchange. Has anybody had any real world experience of using Open Office? Thanks, TC. (1 Reply)
Discussion started by: TCuk
1 Replies

4. SCO

Sco Open Server 5.05

How can I to know procesor type. (1 Reply)
Discussion started by: Batya
1 Replies

5. SCO

Purchase of SCO Open Server 6.0

I have to purchase SCO Open Server 6.0, so I want to know from where I can get SCO Open Server 6.0 and what is the min. cost in which I can avail this. Thanks and Regards Himanshu Software Engineer R&D Department (4 Replies)
Discussion started by: ghimanshu
4 Replies

6. UNIX for Dummies Questions & Answers

what is PXE boot bare-metal

hi members i am reading RHEL and i am unable to under stand about PXE boot and bare metal (1 Reply)
Discussion started by: wagmare
1 Replies

7. HP-UX

bare metal backup for HP-UX 11i v3?

How can i make a dvd image ( bare metal backup ) for HP-UX 11i v3 installation on integrity servers , for quick recovery for the os and installed software in case of disaster (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

8. SCO

SCO Open Server

Hi, Completely new to UNIX - so be gentle Cut a long story short, we have a micros 8700 system (eclipse) that needs the Micros 8700 software installed. The system needs UNIX and I have downloaded and successfully installed SCO open Server 6 and can log into root e.t.c. Now I have... (13 Replies)
Discussion started by: kennyruss
13 Replies

9. Red Hat

Is here anyone hands on in Linux Bare Metal Restore..??

Hi all, I am working on Linux Bare Metal Restore in which i have few things to be discussed with a person who has his/her hands on in that process. If anyone kindly give a reply post in this thread.. :) :) Thanks Selva (3 Replies)
Discussion started by: selvarajvs
3 Replies
clri(1M)																  clri(1M)

NAME
clri - clear inode SYNOPSIS
special i-number ... DESCRIPTION
The command clears the inode i-number by filling it with zeros. special must be a special file name referring to a device containing a file system. For proper results, special should not be mounted (see WARNINGS below). After is executed, all blocks in the affected file show up as "missing" in an of special (see fsck(1M)). This command should only be used in emergencies. Read and write permission is required on the specified special device. The inode becomes allocatable. WARNINGS
The primary purpose of this command is to remove a file that for some reason does not appear in any directory. If it is used to clear an inode that does appear in a directory, care should be taken to locate the entry and remove it. Otherwise, when the inode is reallocated to some new file, the old entry in the directory will still point to that file. At that point, removing the old entry destroys the new file, causing the new entry to point to an unallocated inode, so the whole cycle is likely to be repeated again. If the file system is mounted, is likely to be ineffective. DEPENDENCIES
operates only on file systems of type SEE ALSO
fsck(1M), fsdb(1M), ncheck(1M). STANDARDS CONFORMANCE
clri: SVID2, SVID3 clri(1M)
All times are GMT -4. The time now is 06:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy