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
FSDB(8) 						    BSD System Manager's Manual 						   FSDB(8)

NAME
fsdb -- FFS debugging/editing tool SYNOPSIS
fsdb [-dFn] -f fsname DESCRIPTION
fsdb opens fsname (usually a raw disk partition) and runs a command loop allowing manipulation of the file system's inode data. You are prompted to enter a command with ``fsdb (inum X)>'' where X is the currently selected i-number. The initial selected inode is the root of the filesystem (i-number 2). The command processor uses the editline(3) library, so you can use command line editing to reduce typing if desired. When you exit the command loop, the file system superblock is marked dirty and any buffered blocks are written to the file system. The -d option enables additional debugging output (which comes primarily from fsck(8)-derived code). The -F option indicates that filesystem is a file system image, rather than a raw character device. It will be accessed 'as-is', and no attempts will be made to read a disklabel. The -n option disables writing to the device, preventing any changes from being made to the filesystem. COMMANDS
Besides the built-in editline(3) commands, fsdb supports these commands: help Print out the list of accepted commands. inode i-number Select inode i-number as the new current inode. back Revert to the previously current inode. clri Clear the current inode. lookup name cd name Find name in the current directory and make its inode the current inode. Name may be a multi-component name or may begin with slash to indicate that the root inode should be used to start the lookup. If some component along the pathname is not found, the last valid directory encountered is left as the active inode. This command is valid only if the starting inode is a directory. active print Print out the active inode. uplink Increment the active inode's link count. downlink Decrement the active inode's link count. linkcount number Set the active inode's link count to number. ls List the current inode's directory entries. This command is valid only if the current inode is a directory. blks List the current inode's blocks numbers. findblk disk block number ... Find the inode(s) owning the specified disk block(s) number(s). Note that these are not absolute disk blocks numbers, but offsets from the start of the partition. rm name del name Remove the entry name from the current directory inode. This command is valid only if the current inode is a directory. ln ino name Create a link to inode ino under the name name in the current directory inode. This command is valid only if the current inode is a directory. chinum dirslot inum Change the i-number in directory entry dirslot to inum. chname dirslot name Change the name in directory entry dirslot to name. This command cannot expand a directory entry. You can only rename an entry if the name will fit into the existing directory slot. chtype type Change the type of the current inode to type. type may be one of: file, dir, socket, or fifo. chmod mode Change the mode bits of the current inode to mode. You cannot change the file type with this subcommand; use chtype to do that. chflags flags Change the file flags of the current inode to flags. chown uid Change the owner of the current inode to uid. chgrp gid Change the group of the current inode to gid. chgen gen Change the generation number of the current inode to gen. mtime time ctime time atime time Change the modification, change, or access time (respectively) on the current inode to time. Time should be in the format YYYYMMDDHHMMSS[.nsec] where nsec is an optional nanosecond specification. If no nanoseconds are specified, the mtimensec, ctimensec, or atimensec field will be set to zero. quit, q, exit, <EOF> Exit the program. SEE ALSO
editline(3), fs(5), clri(8), fsck(8) HISTORY
fsdb uses the source code for fsck(8) to implement most of the file system manipulation code. The remainder of fsdb first appeared in NetBSD 1.1. WARNING
Use this tool with extreme caution -- you can damage an FFS file system beyond what fsck(8) can repair. BUGS
Manipulation of ``short'' symlinks doesn't work (in particular, don't try changing a symlink's type). You must specify modes as numbers rather than symbolic names. There are a bunch of other things that you might want to do which fsdb doesn't implement. BSD
January 3, 2004 BSD
All times are GMT -4. The time now is 06:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy