Specifically, it is not a hole in Windows 98SE+IE5.0.
Actually, once Microsoft succeeds in burrying normal access to security information, that combination may well be much safer than the latest software, patches, virus updates, etc.
Watch out for trouble when you eventually "upgrade".
>>"chilling effect" upon speech
It's Alan's call, and I can't say that I blame him.
One effect of this is that it puts the USA at a considerable disadvantage in that these matters are publicly available outside the USA. In other words, "foreign hackers" have free access to information withheld from US sysadmins who would otherwise be in a better position to protect their systems.
The logical conclusion is:
For High security, you must not download any Microsoft updates or visit any Microsoft sites.
In any event you do not want the computer being updated to have to be the one connected to the internet. Imagine downloading current errata from RedHat (from NT and IE naturally), and only afterwards registering RedHat 7.1 Professional Server.
There are a couple of ways of extending the 2GB limit in MySQL.
RAID_TYPE=STRIPED where the data is stored in several files.
UNION of several identically structured tables. Good for reading from long monster but only writing to one of them. UNION also works if some of the tables are compressed.
From the MySQL documentation:
The RAID_TYPE option will help you to break the 2G/4G limit for the MyISAM data file (not the index file) on operating systems that don't support big files. You can get also more speed from the I/O bottleneck by putting RAID directories on different physical disks. RAID_TYPE will work on any OS, as long as you have configured MySQL with --with-raid. For now the only allowed RAID_TYPE is STRIPED (1 and RAID0 are aliases for this).
If you specify RAID_TYPE=STRIPED for a MyISAM table, MyISAM will create RAID_CHUNKS subdirectories named 00, 01, 02 in the database directory. In each of these directories MyISAM will create a table_name.MYD. When writing data to the data file, the RAID handler will map the first RAID_CHUNKSIZE *1024 bytes to the first file, the next RAID_CHUNKSIZE *1024 bytes to the next file and so on.
UNION is used when you want to use a collection of identical tables as one. This only works with MERGE tables. See section 7.2 MERGE Tables.
Have you looked at also running a MySQL slave and running the large summarizing queries on that slave?
A heavy combination of fast writers and slow readers is not nice on MySQL.
DB2 on Sun hardware I think IBM supports that.
Multiple vendors is feasible if management is technologically cognizant. With a PHB or two easily intimidated by buzz-words, better to stick with one vendor.
You are thinking cardinals, where an infinite set has exactly as many elements if you add any finite number of elements to it. I.e. there are exactly as many primes as there are fractions.
Problem is, the is no last element added that made it infinity.
If you are counting (ordinals), +1 makes a different number, so if you have infinity, infinity+1 is a different number.
The line looks like this:
1,2,3,4,5,...
...an infinite number of them here...
infinity,infinity+1,infinity+2,...
...another infinite number of 'em...
2infinity,2infinity+1,...
...and so on....
Yellowstone Volcano When the volcano in Yellowstone National Park blew 6,400 centuries ago, it obliterated a mountain range, felled herds of prehistoric camels hundreds of miles away and left a smoking hole in the ground the size of the Los Angeles Basin. Volcanos come in all different sizes too, some of 'em pretty big.
Running production in the field for 5+ years with nobody having a stability problem.
The problem is such as Microsoft get something new and because it managed to stay up all day they think it's (finally) stable.
Security is enhanced by redundancy, by having several distinct systems in place, preferably as dissimilar as possible. AND is not the same as OR
ALL is not the same as ANY
I would much rather have the bits and pieces of my identity stored at multiple sites on a variety of systems. To put them all together, an attacker has to crack ALL of them, not just one.
My mailing address is in the Phone Book, which is pretty widely accessible, but that isn't going to give anyone much access to my/. account.
change one config file in Windows to uninstall something.... One config file: c:\windows\inf\sysoc.inf
remove "hide" from msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7
Now that the "Windows Messenger" has his "Cloak of Invisibility" removed, the normal click&drool will function to kill the messenger.
Actually, Linux is a whole lot easier than Windows. With apache running, rpm -e mod_perl; service httpd restart. Gotta love a system that doesn't go into histerics if you delete a running program.
The first stage is to prove that it can be stable, doing all sorts of misconfigurations and reconfigurations without rebooting. The second stage is to use a reboot to verify that the init scripts function as intended while you still have a vague memory of what you changed. After a long power outage is not the time to find out you left something out of an init script:(
OK, how much of IBM's growth is due to adaption to the OSS Model? Directly, not a lot; indirectly, rather substantial, I'd imagine. The main effect is that by lowering the bar to competition, IBM becomes, long term, a much safer choice of vendor to supply solutions, particularly when that solution has to interface with and must interact with other peoples solutions.
With known open standards being enforced by the industry on the industry Anything else is ultimately suicidal, like the old-west towns that didn't want to allow access by the railroads. The best guarantee of keeping access to your data is that there is an independant source. Good things are like the ability to run KDE apps on a Gnome desktop (and vice-versa), downloading Sun's Trademarked Java from IBM, using Adobe's acrobat to read Ghostscript produced PDFs.
>>isn't there somthing to be said about being able to read a PL?
Sure is. It's called COBOL, which can be read and understood by someone with a rather limited vocabulary.
Think about a database with lots of single character data, but with long column names. The optimal transfer is a COBOL Logical Record, but you have a major problem if the reader does not have the same exact version as the sender.
The trailing tag is just as important as the opening tag. Stuff inside the tags belongs to the tag. Stuff outside the tags does not belong to the tag. If you want to save a few characters, use LISP. It's terse to the point of being cryptic. Thirty close-parens in a row, none of them optional.
Slashdot Mirror
Specifically, it is not a hole in Windows 98SE+IE5.0.
Actually, once Microsoft succeeds in burrying normal access to security information, that combination may well be much safer than the latest software, patches, virus updates, etc.
Watch out for trouble when you eventually "upgrade".
>>"chilling effect" upon speech
It's Alan's call, and I can't say that I blame him.
One effect of this is that it puts the USA at a considerable disadvantage in that these matters are publicly available outside the USA. In other words, "foreign hackers" have free access to information withheld from US sysadmins who would otherwise be in a better position to protect their systems.
Yep, RedHat is fixing more vulnerabilities than Microsoft.
The logical conclusion is:
For High security, you must not download any Microsoft updates or visit any Microsoft sites.
In any event you do not want the computer being updated to have to be the one connected to the internet. Imagine downloading current errata from RedHat (from NT and IE naturally), and only afterwards registering RedHat 7.1 Professional Server.
Scripting disabled.
Do you want to run Scripts. No. Many times no.
A runtime Error has occurred. Do you wish to Debug?
Line 1: Error Object expected.
Methinks it will be a long, long time before Microsoft has anything remotely resembling security.
There are a couple of ways of extending the 2GB limit in MySQL.
RAID_TYPE=STRIPED where the data is stored in several files.
UNION of several identically structured tables. Good for reading from long monster but only writing to one of them. UNION also works if some of the tables are compressed.
From the MySQL documentation:
The RAID_TYPE option will help you to break the 2G/4G limit for the MyISAM data file (not the index file) on operating systems that don't support big files. You can get also more speed from the I/O bottleneck by putting RAID directories on different physical disks. RAID_TYPE will work on any OS, as long as you have configured MySQL with --with-raid. For now the only allowed RAID_TYPE is STRIPED (1 and RAID0 are aliases for this).
If you specify RAID_TYPE=STRIPED for a MyISAM table, MyISAM will create RAID_CHUNKS subdirectories named 00, 01, 02 in the database directory. In each of these directories MyISAM will create a table_name.MYD. When writing data to the data file, the RAID handler will map the first RAID_CHUNKSIZE *1024 bytes to the first file, the next RAID_CHUNKSIZE *1024 bytes to the next file and so on.
UNION is used when you want to use a collection of identical tables as one. This only works with MERGE tables. See section 7.2 MERGE Tables.
Have you looked at also running a MySQL slave and running the large summarizing queries on that slave?
A heavy combination of fast writers and slow readers is not nice on MySQL.
DB2 on Sun hardware
I think IBM supports that.
Multiple vendors is feasible if management is technologically cognizant. With a PHB or two easily intimidated by buzz-words, better to stick with one vendor.
You are thinking cardinals, where an infinite set has exactly as many elements if you add any finite number of elements to it. I.e. there are exactly as many primes as there are fractions.
Problem is, the is no last element added that made it infinity.
If you are counting (ordinals), +1 makes a different number, so if you have infinity, infinity+1 is a different number.
The line looks like this:
1,2,3,4,5,...
...an infinite number of them here...
infinity,infinity+1,infinity+2,...
...another infinite number of 'em...
2infinity,2infinity+1,...
...and so on....
2.4.infinity+1 (we're talking ordinals here)
2.4.infinity+2
...
2.4.inifinity+infinity+1
...
2.5.0
3.0.0
Yellowstone Volcano
When the volcano in Yellowstone National Park blew 6,400 centuries ago, it obliterated a mountain range, felled herds of prehistoric camels hundreds of miles away and left a smoking hole in the ground the size of the Los Angeles Basin.
Volcanos come in all different sizes too, some of 'em pretty big.
Since I don't see a better answer her.
Someone in upper management.
Was very insistent about it.
In fact UNIX is a pun on MULTICS.
UNIX is much smaller and simpler.
Running production in the field for 5+ years with nobody having a stability problem.
The problem is such as Microsoft get something new and because it managed to stay up all day they think it's (finally) stable.
Security is enhanced by redundancy, by having several distinct systems in place, preferably as dissimilar as possible. /. account.
AND is not the same as OR
ALL is not the same as ANY
I would much rather have the bits and pieces of my identity stored at multiple sites on a variety of systems. To put them all together, an attacker has to crack ALL of them, not just one.
My mailing address is in the Phone Book, which is pretty widely accessible, but that isn't going to give anyone much access to my
change one config file in Windows to uninstall something....
One config file: c:\windows\inf\sysoc.inf
remove "hide" from msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7
Now that the "Windows Messenger" has his "Cloak of Invisibility" removed, the normal click&drool will function to kill the messenger.
Actually, Linux is a whole lot easier than Windows. With apache running, rpm -e mod_perl; service httpd restart. Gotta love a system that doesn't go into histerics if you delete a running program.
No, radix sort is O(N log N).
The thing with a card sorter is that you've got to sort on all the relevant columns.
With NT4 it's "Find". W2k is "Search".
*nix is locate for the easy stuff, find for the hard stuff.
Rock solid? 99% of the time?
The first stage is to prove that it can be stable, doing all sorts of misconfigurations and reconfigurations without rebooting. The second stage is to use a reboot to verify that the init scripts function as intended while you still have a vague memory of what you changed. After a long power outage is not the time to find out you left something out of an init script :(
OK, how much of IBM's growth is due to adaption to the OSS Model?
Directly, not a lot; indirectly, rather substantial, I'd imagine. The main effect is that by lowering the bar to competition, IBM becomes, long term, a much safer choice of vendor to supply solutions, particularly when that solution has to interface with and must interact with other peoples solutions.
With known open standards being enforced by the industry on the industry
Anything else is ultimately suicidal, like the old-west towns that didn't want to allow access by the railroads. The best guarantee of keeping access to your data is that there is an independant source. Good things are like the ability to run KDE apps on a Gnome desktop (and vice-versa), downloading Sun's Trademarked Java from IBM, using Adobe's acrobat to read Ghostscript produced PDFs.
>>isn't there somthing to be said about being able to read a PL?
Sure is. It's called COBOL, which can be read and understood by someone with a rather limited vocabulary.
LOL. I know it's a typo, but somehow reched seems rather more descriptive than reached.
Think about a database with lots of single character data, but with long column names.
The optimal transfer is a COBOL Logical Record, but you have a major problem if the reader does not have the same exact version as the sender.
The trailing tag is just as important as the opening tag. Stuff inside the tags belongs to the tag. Stuff outside the tags does not belong to the tag. If you want to save a few characters, use LISP. It's terse to the point of being cryptic. Thirty close-parens in a row, none of them optional.