[ale] how do I list big files

[Wolf Halton]

Ron,
/sys/devices are hardware - in this case they are probably pci cards 
(maybe your video memory??)
/dev are devices (mounted storage devices will show up in other folders, 
so you will not miss anything crazy important (I don't think))
/proc are running processes (not files)

I haven't looked, but there may be a simple way to exclude that kind of 
folder

Wolf

On 03/20/2011 09:44 AM, Pete Hardie wrote:
> On Sun, Mar 20, 2011 at 09:26, Ron Frazier
> <atllinuxenthinfo at c3energy.com>  wrote:
>> I tried the command as follows without sending to the text file and it
>> appeared to work.  However, it generated some errors and odd behavior which
>> I've highlighted below.  (Hopefully that comes through in the post.)  I
>> tried it from root as well as my home directory with similar results.  When
>> I send it to the text file, the normal lines appear to go to the file and
>> the errors appear to go to the screen.  So, I'm wondering four things.
>>
>> 1) Am I actually seeing all the files on the system that match the criteria?
>> 2) What are the strange files I've highlighted which are not errors?
>> 3) What are the errors?
>> 4) Are these errors harmful to the system in any way?
>>
>> See printout below.
>>
>> Sincerely,
>>
>> Ron
>>
>> -----------------------------------
>>
>> ron at TAZ1:~$ sudo find / -type f -size +100M
>>
>> /sys/devices/pci0000:00/0000:00:00.0/resource3     ???
>> /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.0/resource0     ???
>> /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.0/resource0_wc     ???
> I don't know for sure, but since these look like devices, they may not
> have a size value (think keyboard, monitor)
>
>
>> find: `/home/ron/.gvfs': Permission denied
> a straight permissions issue - my .gvfs is dr-x------, so nobody but
> me has read permission
>
>
>> /proc/kcore     ???
> Again, perhaps not a regular file, so no size attribute
>> find: `/proc/18372/task/18372/fd/5': No such file or directory
>> find: `/proc/18372/task/18372/fdinfo/5': No such file or directory
>> find: `/proc/18372/fd/5': No such file or directory
>> find: `/proc/18372/fdinfo/5': No such file or directory
>>
> These are unde r/proc, so they refer to processes, and find may have
> gotten their names from the parent directory, but they stopped
> existing by the time it processed them