Actually, OSX is NOT case-insensitive. It remembers the case, but DOESN'T always *ignore* it. I have some files on a SMB share mounted using the "Connect to Server" command as/Volumes/sharename. When I first login, and attempt to access those files with the application, the OS nicely re-connects the share, but mounts it as/Volumes/SHARENAME, and then the applications fails to find the files. BROKEN.
I think the problem is actually the application, not the OS. If I create a file named "foo" and try to open() "FOO", the call succeeds with a valid file descriptor. However, a badly written application does a directory listing of "/Volumes", looks for "sharename", doesn't see it, and bombs.
Now, I realize this is a programmer problem, but I think that it is a symptom of a design flaw that the onus is on the programmer rather than the operating system to enforce the "case-insensitive, but case-preserving" behavior. I've seen this behavior on Windows with some cygwin-compiled programs as well.
Simply put, Case-Insensitive is ok, but Case-Preserving is BAD, IMHO.
MPLS is also going to help solve this problem. Core routers will have much smaller MPLS routing tables, with only edge routers knowing IP routes.
If all goes according to plan, of course.
>> P.S. : "no real compiler support" - what are you talking about?
> Ideally, you have a compiler that takes care of using all the nodes and distributing the code. > If you have to hand-code all that, it just takes too long and is error-prone (debugging > distributed code is a really ugly task). Something like High Performance Fortran.
Are you aware that there are HPF compilers for Linux being used in Beowulf clusters?
As distributed IDS detection software matures, I think most sites and perhaps their hosting ISPs will work together to implement such systems, thus rendering most script-kiddie DOS attacks powerless or at least short-lived. Comments?
Slashdot Mirror
My favorite sign...seen on the lab door at my college: "WARNING! Do Not Look Into Laser With Remaining Eye."
Don't anthropomorphize Computers. They don't like it.
Actually, OSX is NOT case-insensitive. It remembers the case, but DOESN'T always *ignore* it. I have some files on a SMB share mounted using the "Connect to Server" command as /Volumes/sharename. When I first login, and attempt to access those files with the application, the OS nicely re-connects the share, but mounts it as /Volumes/SHARENAME, and then the applications fails to find the files. BROKEN.
I think the problem is actually the application, not the OS. If I create a file named "foo" and try to open() "FOO", the call succeeds with a valid file descriptor. However, a badly written application does a directory listing of "/Volumes", looks for "sharename", doesn't see it, and bombs.
Now, I realize this is a programmer problem, but I think that it is a symptom of a design flaw that the onus is on the programmer rather than the operating system to enforce the "case-insensitive, but case-preserving" behavior. I've seen this behavior on Windows with some cygwin-compiled programs as well.
Simply put, Case-Insensitive is ok, but Case-Preserving is BAD, IMHO.
Links:
Cisco - IP+ATM Solutions
IETF MPLS Charters
> Ideally, you have a compiler that takes care of using all the nodes and distributing the code.
> If you have to hand-code all that, it just takes too long and is error-prone (debugging
> distributed code is a really ugly task). Something like High Performance Fortran.
Are you aware that there are HPF compilers for Linux being used in Beowulf clusters?
Check out:
VastHPF
PGHPF
There are other commercial products, plus some educational type compilers.
- Darren
--
As distributed IDS detection software matures, I think most sites and perhaps their hosting ISPs will work together to implement such systems, thus rendering most script-kiddie DOS attacks powerless or at least short-lived. Comments?