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
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
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
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
How can I to know procesor type. (1 Reply)
Discussion started by: Batya
1 Replies
5. SCO
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
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
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
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
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
FFIND(1) General Commands Manual FFIND(1)
NAME
ffind - Finds the name of the file or directory using a given inode
SYNOPSIS
ffind [-aduvV] [-f fstype] [-i imgtype] [-o imgoffset] [-b dev_sector_size] image inode
DESCRIPTION
ffind finds the names of files or directories that are allocated to inode on disk image image. By default it only will only return the
first name it finds. With some file systems, this will find deleted file names.
ARGUMENTS
image [images]
One (or more if split) disk or partition images whose format is given with '-i'.
inode Integer of inode to find.
The optional arguments are:
-a Find all occurrences of inode.
-d Find deleted entries only.
-f fstype
Identify the file system type of the image. Use '-f list' to list the supported file system types. If not given, autodetection
methods are used.
-u Find undeleted entries only.
-i imgtype
Identify the type of image file, such as raw or split. Use '-i list' to list the supported types. If not given, autodetection
methods are used.
-o imgoffset
The sector offset where the file system starts in the image.
-b dev_sector_size
The size, in bytes, of the underlying device sectors. If not given, the value in the image format is used (if it exists) or
512-bytes is assumed.
-v Verbose output to stderr.
-V Display version.
This program searches all directory entries looking for the given inode. This is useful when an inode has been identified from a disk unit
address using ifind(1).
EXAMPLE
# ffind -a image 212
SEE ALSO
ifind(1)
AUTHOR
Brian Carrier <carrier at sleuthkit dot org>
Send documentation updates to <doc-updates at sleuthkit dot org>
FFIND(1)