I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.
[...]

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

On Tue, 05 Aug 2008 23:30:23 GMT, P1 wrote:

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

That sounds very much like some sort of homework.

changed the filenames in my description, but the problem is actually a
real-world one. I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the

mailbox as empty. I need to find all directories where these two
files have a different case so that I can fix that problem. In

You're the second person that stated that this sounds like homework.
Maybe it does, I've never taken a Linux class, been a Windows admin
for many years, just starting to scratch the surface of Linux. I
changed the filenames in my description, but the problem is actually a
real-world one. I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the

system can't find the index for the mailbox file and hence shows the
mailbox as empty. I need to find all directories where these two
files have a different case so that I can fix that problem. In
Windows, this didn't matter because there is no case sensitivity, but
obviously in Linux this broke the mailbox. Gordano support is trying
to figure out how to fix this programmatically also, but they're slow
as hell so I was trying a different avenue...

Pete.

On Wed, 6 Aug 2008 16:16:17 +0000 (UTC), "Auric__"
not.my.real at (no spam) email.address> wrote:

On Tue, 05 Aug 2008 23:30:23 GMT, P1 wrote:

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

That sounds very much like some sort of homework.

P1 <p1 at (no spam) eagency.com> writes:

You're the second person that stated that this sounds like homework.
Maybe it does, I've never taken a Linux class, been a Windows admin
for many years, just starting to scratch the surface of Linux. I
changed the filenames in my description, but the problem is actually a
real-world one. I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the

So, why not change them all to the same case for all users, and have
everything be stadard.

for i in `find . -iname inbox.mbx`
do
j=`dirname $i`
mv $i ${j}/inbox.mbx
done

and then the same for inbox.idx

system can't find the index for the mailbox file and hence shows the
mailbox as empty. I need to find all directories where these two
files have a different case so that I can fix that problem. In
Windows, this didn't matter because there is no case sensitivity, but
obviously in Linux this broke the mailbox. Gordano support is trying
to figure out how to fix this programmatically also, but they're slow
as hell so I was trying a different avenue...

Pete.

On Wed, 6 Aug 2008 16:16:17 +0000 (UTC), "Auric__"
not.my.real at (no spam) email.address> wrote:

On Tue, 05 Aug 2008 23:30:23 GMT, P1 wrote:

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

That sounds very much like some sort of homework.

Thought about that too, but unfortunately, there's a config file or
something somewhere that tells the system how the file name is
spelled, and it's not the same for all users, so I can't standardize
it, unless Gordano rewrites their code to ignore case or we can find
the config file and modify the names there. I don't even know if it
is a config file or if it's hard-coded.

Pete

On Wed, 06 Aug 2008 22:03:08 GMT, Unruh <unruh-spam at (no spam) physics.ubc.ca
wrote:

P1 <p1 at (no spam) eagency.com> writes:

You're the second person that stated that this sounds like homework.
Maybe it does, I've never taken a Linux class, been a Windows admin
for many years, just starting to scratch the surface of Linux. I
changed the filenames in my description, but the problem is actually a
real-world one. I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the

So, why not change them all to the same case for all users, and have
everything be stadard.

for i in `find . -iname inbox.mbx`
do
j=`dirname $i`
mv $i ${j}/inbox.mbx
done

and then the same for inbox.idx

system can't find the index for the mailbox file and hence shows the
mailbox as empty. I need to find all directories where these two
files have a different case so that I can fix that problem. In
Windows, this didn't matter because there is no case sensitivity, but
obviously in Linux this broke the mailbox. Gordano support is trying
to figure out how to fix this programmatically also, but they're slow
as hell so I was trying a different avenue...

Pete.

On Wed, 6 Aug 2008 16:16:17 +0000 (UTC), "Auric__"
not.my.real at (no spam) email.address> wrote:

On Tue, 05 Aug 2008 23:30:23 GMT, P1 wrote:

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

That sounds very much like some sort of homework.

P1 <p1 at (no spam) eagency.com> writes:

Thought about that too, but unfortunately, there's a config file or
something somewhere that tells the system how the file name is
spelled, and it's not the same for all users, so I can't standardize
it, unless Gordano rewrites their code to ignore case or we can find
the config file and modify the names there. I don't even know if it
is a config file or if it's hard-coded.

If it is hard coded then it should be the same for all. You say they are
not the same for all.

You are left with the problem that if the two names disagree, then which is
the one that determines what the common name should be?

Pete

On Wed, 06 Aug 2008 22:03:08 GMT, Unruh <unruh-spam at (no spam) physics.ubc.ca
wrote:

.... I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the
system can't find the index for the mailbox file and hence shows the
mailbox as empty.
....

You're the second person that stated that this sounds like homework.
Maybe it does, I've never taken a Linux class, been a Windows admin for
many years, just starting to scratch the surface of Linux. I changed
the filenames in my description, but the problem is actually a
real-world one. I migrated a proprietary email system (Gordano GMS)
from Windows to Linux a couple of weeks ago. Most accounts work fine,
but a few hundred don't and I found that they don't because the
INBOX.MBX file case doesn't match the INBOX.IDX file case, so the system
can't find the index for the mailbox file and hence shows the mailbox as
empty. I need to find all directories where these two files have a
different case so that I can fix that problem. In Windows, this didn't
matter because there is no case sensitivity, but obviously in Linux this
broke the mailbox. Gordano support is trying to figure out how to fix
this programmatically also, but they're slow as hell so I was trying a
different avenue...

Pete.

On Wed, 6 Aug 2008 16:16:17 +0000 (UTC), "Auric__"
not.my.real at (no spam) email.address> wrote:

On Tue, 05 Aug 2008 23:30:23 GMT, P1 wrote:

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

That sounds very much like some sort of homework.

I'm in need of script that would allow me to find the following but
I've never scripted anything. Hoping to get some help as I just don't
have time to learn scripting just for this particular task, although
it's definitely something I want to put on my todo list...

Find all subfolders with a file.ext1 and file.ext2 but only where the
letter case of "file" is different. There are three possible ways the
name can be spelled: file, File and FILE.

So a subfolder containing both file.ext1 and File.ext2 would be found
since the case is different, but a subfolder containing FILE.ext1 and
FILE.ext2 would not, since the case matches.

Hope that makes sense...

Thanks,
Pete.

for i in `find . -iname inbox.MBX`
do
j=`dirname $i`
k=`basename $i .MBX`
l=`find $j -iname inbox.IDX`
if [ "`basename $l .IDX`" != "$k" ]; then
echo $k
fi
done

Unruh wrote:

for i in `find . -iname inbox.MBX`
do
j=`dirname $i`
k=`basename $i .MBX`
l=`find $j -iname inbox.IDX`
if [ "`basename $l .IDX`" != "$k" ]; then
echo $k
fi
done


Being a noob to this, it took me a while to figure out what was wrong
with this script, because it made sense on paper but yet it was
resulting in listing ALL user directories. So I started breaking it
down and put echo $variable statements before the end and found that
basename wasn't stripping the suffix, it's apparently case-sensitive
Here's my modified version of it:

for i in `find . -iname inbox.mbx`
do
dir=`dirname $i`
mbxname=`basename $i .mbx`
idxpath=`find $dir -iname inbox.idx`
idxname=`basename $idxpath .idx`
if [ "$idxname" != "$mbxname" ]; then
echo Case Mismatch in $dir; else
echo Match OK in $dir
fi
done

Thanks for the help and the lesson
Pete.
PS. Btw, how can I pipe that output to "sort" or "count"?