I have read quite a few threads here about the unix file creation date. I was interested in finding how to display it using a unix command ...
You can see if command stat is available in SCO as it is in Linux, but as you see and have seen, there is no creation date. If it is important, the date can be made to be part of the filename, e.g. my_important_stuff_2007.05.26.txt. Here is a stat example:
cheers, drl
Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
the superblock has the offset for inode table.
My question is
1) whether it starts relative to the start of the first cylinder group
or is it relative to the start of filesystem???
2)and also which entry corresponds to the root(/) inode?? is it second or third entry???
My questions are... (4 Replies)
What are some benefits of the UNIX hierarchical file structure?
I am new to UNIX and researching some information about it for a class so please help if you can.
Thanks. (1 Reply)
I'm not sure where to post this but I'm having some trouble with the directories in CP/M... I'm sorry about the length but I'm totally confused... I've seen that the directory entry in CP/M contains the following:
1 byte User Code
8 bytes Filename
3 bytes File extension
1 byte Extension
2... (3 Replies)
Hi
I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7.
I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Hi everyone,
I am new here in www.unix.com, i found this site because I am looking for an answer to this problem of mine.
I need to know a UNIX command to display an inode's thread id and process id.
Hope someone can help me on this.
Thanks :D (8 Replies)
Hi
I am creating a utility which needs to create a log file under the path represented by an environment variable. The condition is that this path must be a valid DIRECTORY PATH. So i need to determine that the path is indeed a VALID DIRECTORY PATH.
I have written a function which will return... (2 Replies)
How can I get only FileName associated with a INODE on Unix in seconds instead of minutes, as it is the case for me as shown below.
# Say I have FileDescriptor: 43, INODE: 2590784, File: abc.rdb. I want to get only filename associated with inode:2590784 and FD:43.
$> time find / -inum... (7 Replies)
Hi All,
I have a compute box and I want to tar directory structure under a directory and then Deploy/untar it in a new compute box so that the directory structure will be exactly the same.
I do not want any of the file to be extracted and deployed but instead only the directory structure.
... (2 Replies)
Discussion started by: filter
2 Replies
LEARN ABOUT DEBIAN
ffind
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)