Drew Tomlinson said the following on 10/14/2005 3:13 PM:
> OK, duh. I get it now. Thanks for pointing me in the right direction!
Quite welcome! Enjoy!!
Best,
--Glenn
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Drew Tomlinson
> Sent: 10/14/2005 12:54 PM
> To: FreeBSD Questions
> Subject: Help With Find Syntax
>
> I want to recursively search a directory and return files that end in
".
On 10/14/2005 12:05 PM Glenn Sieb wrote:
Drew Tomlinson said the following on 10/14/2005 2:53 PM:
I want to recursively search a directory and return files that end in
".jpg" or ".gif" but I can't seem to get the find syntax right. My
basic command lines are:
find /multimedia/Pictures -in
On Oct 14, 2005, at 2:53 PM, Drew Tomlinson wrote:
$ find /multimedia/Pictures -iname "*.gif" -or "*.jpg" -print
find: paths must precede expression
Usage: find [path...] [expression]
I've tried various placement of quotes, parenthesis, etc. but can't
seem to find the right way to do th
Drew Tomlinson said the following on 10/14/2005 2:53 PM:
> I want to recursively search a directory and return files that end in
> ".jpg" or ".gif" but I can't seem to get the find syntax right. My
> basic command lines are:
>
> find /multimedia/Pictures -iname "*.gif" -print
>
> OR
>
> find /mul
I want to recursively search a directory and return files that end in
".jpg" or ".gif" but I can't seem to get the find syntax right. My
basic command lines are:
find /multimedia/Pictures -iname "*.gif" -print
OR
find /multimedia/Pictures -iname "*.jpg" -print
Both of these work perfectly.
Thank you to everyone for all your help! Something must have 'puked' during
my nightly cvsup of the ports tree. Every directory under /usr/ports had a
sysctl.core file. By deleting these files, I recovered my disk space.
Thanks again!
Drew
___
[EMAI
> - Original Message -
> From: "Malcolm Kay" <[EMAIL PROTECTED]>
> To: "David Carter-Hitchin" <[EMAIL PROTECTED]>; "Drew
> Tomlinson" <[EMAIL PROTECTED]>
> Sent: Friday, October 31, 2003 4:44 PM
>
> On Sat, 1 Nov 2003 11:34, David Carter-Hitchin wrote:
> > Hi Drew,
> [snip]
> > You may find
- Original Message -
From: "David Carter-Hitchin" <[EMAIL PROTECTED]>
To: "Drew Tomlinson" <[EMAIL PROTECTED]>
Sent: Friday, October 31, 2003 5:04 PM
> Hi Drew,
>
> Find is one of those classic commands for confusing people. One just gets
> used to it over time. The behaviour of find va
On Sat, 1 Nov 2003 11:34, David Carter-Hitchin wrote:
> Hi Drew,
[snip]
> You may find the following note from man find helpful:
>
> # All primaries which take a numeric argument allow the number to be pre-
> # ceded by a plus sign (``+'') or a minus sign (``-''). A preceding plus
> # sign means `
'2' before the permissions).
HTH,
David
On Fri, 31 Oct 2003, Drew Tomlinson wrote:
> - Original Message -
> From: "David Carter-Hitchin" <[EMAIL PROTECTED]>
> To: "Drew Tomlinson" <[EMAIL PROTECTED]>
> Cc: "FreeBSD Questions&quo
- Original Message -
From: "David Carter-Hitchin" <[EMAIL PROTECTED]>
To: "Drew Tomlinson" <[EMAIL PROTECTED]>
Cc: "FreeBSD Questions" <[EMAIL PROTECTED]>
Sent: Thursday, October 30, 2003 5:55 PM
Subject: Re: Help With 'find' Syn
Hi Drew,
This should find all files created or modified on 25th October:
find / -mtime 6 -ls -o -ctime 6 -ls
(As today is 31st October which is 6 days after 25th. You may need to
widen your search a little with a seperate search with 7 as the paramter
as 6 may not catch files that were created
On October 25, my /usr partition lost nearly 50% of it's available space.
This disk hasn't had any significant size changes since I built the system
as it basically serves as a gateway.
I'm trying to use the find command to determine what may have been written
to the disk but am not having any luc
14 matches
Mail list logo