Search Results

I try to understand the meaning of an inode. I wonder whether


an inode is unique (I'm pretty sure it is) and
whether it remains the same inode regardless of whatever happens to the file, dir...

This is like tutoring, thanks a lot. Working on it, playing around with the code and testing as we speak. Thanks!

Thanks a lot, will read through it and post back if there are things I don't understand.

Thanks a lot, really, for helping me out here. Much appreciated!

@ctsgnb

Ok, this works perfect.

Now it's up to me to understand the code, for I want to learn what the code in fact does. Any guidance would be cool, but do not feel obliged to do so.

@ctsgnb

I thought I made clear what I needed, yet apparently was not clear enough. So here goes.

Output must be something like:
Hence output consists of 4 elements, separated by a semicolon:...

I thought that would create a tmp dir, and in it a foo file. That did not happen. That's all.

But...
find . -ls |awk '{match($0,$9 FS FS "*"...

Does not generate a foo file. In fact it does not do a lot.

But I can give the result (leaving out the print to file):

Mac OS X.

If I use only find . -ls, the result is fine. Fine here means is shown in the result below:
So I have to use your other sample code, for I needed a different output (as explained in previous posts)....

@vgersh99: sorry to say, but still returns the same errors. Print below:



@ctsgnb: similar issue (I guess) as I have using the code of vgersh99

Ok, I went to a one of the dirs where I ran into the issue. I did not list all files (far too long list). Yet, should be sufficient I guess...

Just to be sure, it concerns the following code:...

@vgersh99

Do you want a full find . -ls you mean?

@ctsgnb
Will do. :)

@vgersh99

You did, untill I noticed that the output was not as desired for some files (posted in previous reply). Your output with your code

was:

the issue here is that (last line):...

In case you refer to a 'find . -ls' works
'find . -ls' works fine, but that does not return what I need. It does not allow me to find the name of the file and the folder it belongs to.

When I...

@vgrsh99:

Example return:

I don't think I understand this. Should I add this to previous or...?

Hmm, using blank spaces indeed is not. Yet it's used to pull dir lists from users, and then to 'process' them in excel (a mock-up) to show how the dirs should be organized and what metadata should be...

Wow, this is so way beyond my skills. Thanks. The problem with this is that it ends when there is a file with a blank space in it.

Example:

is printed as


But I need:

Thanks both!

I ended up using the last,
find . -ls | awk 'BEGIN { OFS = ";";} {match($11,"[^/]*$");print $1,$2,$11,substr($11,RSTART,RLENGTH)}'I guess there is no way of adding a filetype to it...

Ok, thanks.

Did not find that in the man find though. Not sure where to look for to be honest.

Hi all,

I tried to find the reply using google, yet did not find a conclusive answer.

When I use 'find . -ls', I get something like:
3423297 8 -rw-r--r-- 1 useradmin staff ...

Brilliant!

Thanks, that is indeed what I need. Yet, the path is included in the last bid. If there are files in a subfolder, the path of those subfolders is printed as well. Will try myself to modify the code....

Error:
-bash: nawk: command not found

The following came rather close:
find . -type d $a ! -name \. | while read a; do echo ${a} \(--${a##*/}--\) \(--DIRECTORY--\); find -type f -prune; done
...

I understand that the $x will return the x-column. Yet, whether a string is a new column or not is defined whether there is a space. This is a problem for:
a column containing the following:
File...

I might have misunderstood you but...

Using
find . -ls |awk -F'.' 'NR>1{print $NF}'
Gives the dirs and extensions of files.

Second
find . -ls |
awk -F'.' 'NR>1{print...