Well what if you have a packet that's part of a vi clone with b00bies that will enlarge your penis? Or an internal Microsoft memo that contains pictures of dead babies being eaten by a man covered in feces?
refer to RFC 2471, which established the current address allocation: "These addresses are temporary and will be reclaimed in the future."
And why are they closing the 6bone? "As IPv6 is beginning its production deployment it is appropriate to plan for the phaseout of the 6bone."
They're just cleaning up from the testing phase so they can move into official use. It's only a step backwards if you consider the end of a beta test a step backwards.
I've not met any other blokes insecure enough to whine about it.
Insecurity or not, making any sort of grammar commentary is a high sin. Most people will avoid commenting because they don't want to be harrassed in return.
It's kind of a pity, without constructive, non-derogitory criticism, how is anyone going to improve their poor grammar? Even scathing remarks are helpful, would you rather have someone tell you that you're an idiot once, or would you rather have many people think so forever?
(fwiw, I prefer the gender neutral "he/him/his" or, more commonly, "they/them/their", which is probably technically wrong, but more smooth.)
Plus, the third-world manufacturer can still sell widgets to other countries, whose products will have an advantage over the U.S., since they'll be using half-price widgets!
Nor is anything else that was built with VC++ (or visual studio in general) and thus uses its implementation of malloc.
How do you know that? Link, please.
Even if everything that was compiled under Visual Studio used its malloc (which is not true), that still has to get the memory from the system sometime.
Is it worth an extra $3-$5 to be able to backup the CD
Backup? Try play.
Copy protection often breaks CD-ROM drives' ability to ready them in a sensible way at all. I always rip CDs when I buy them and listen to them as MP3, either on the computer or on my NEXII. I leant my CD player to my sister since I never use it. (CDs are a pain when you have better options)
So is it work $3-$5 extra so I can actually use it? Maybe, but then most CDs aren't worth $3 to begin with.
Yeah I dunno, I got sshd for free when I set up my home server. Do hardware failures happen often enough that you'll need to see POST on some machine every week?
Could you provide an example? Last time I set up a firewall on Linux, I had to use ipchains, which was baffling to no end. I gave up on any manual configuration and went with linuxconf.
pf is practically configured in english, I actually know where the config file is, and I can easily understand it weeks later without digging through the man page again.
I've taken a quick look around www.netfilter.org, but the best I've seen is stuff like: iptables -t filter -A INPUT -d $PUBLIC -m state --state INVALID -j log iptables -t filter -A INPUT -s localhost -d localhost -j ACCEPT iptables -t filter -A INPUT -s $PUBLIC -d $PUBLIC -j ACCEPT iptables -t filter -A INPUT -d $PUBLIC -m state --state RELATED,ESTABLISHED -j ACCEPT
which is still fairly opaque compared to: pass in quick on $xif inet proto udp from 10.150.88.1 to 255.255.255.255 keep state pass in quick on $xif inet proto tcp from any to ($xif) port 22 keep state block in log all
What's more, few if any Gnutella developers will ever support Gnutella2 because of the divisive way that it was introduced, permanently fracturing the Gnutella community, with almost all of the Gnutella community still working on Gnutella because they were never told of the so-called Gnutella2 until it was slashdotted, much as we're seeing today.
No problem, they just need to come out with Gnutella3, thus grabbing back the spotlight by "superceding" this.
Understand this: No corporation has ever made enough money out of something.
At some point it costs the corporation more to dig up and make a copy for distribution than anyone is willing to pay for it. When this happens, it is impossible for them to make any more money off of this product.
Windows 1.0 probably falls into this category.
OTOH, it also costs something to dig it up and release it for free. With books it's a little different, since the book's content is already out there.
I wouldn't be suprized to find that the Window 1.0 source code no longer exists. In that case, the cost to release it for free is enormous.
I'd think dead pixels on a CRT are more likely caused by a the video card, either a bad cell in its RAM, or a glitch somewhere else. (especially if it shows up on more than one monitor)
Refresh rates = 1 / response time
on
LCD Overtaking CRT
·
· Score: 2, Informative
Technically, LCD displays don't have a refresh rate, but they do have a maximum change rate which is effectively the same thing in this case.
On an LCD: 1 / (response time) = maximum frame rate
Whereas on a CRT: refresh rate = maximum frame rate
So you can loosely compare refresh rate to the inverse of the response time.
Most modern LCDs operate at only 24 bit color.
How many video cards can put out more than 8 bits per primary? Only really high-end graphics people are going to care about that anyway, the gamut is probably much more important.
MSDOS.SYS was a text file containing some boot options. It had a large block of comments that had the message you remembered. (some programs required that it be some minimum size)
IO.SYS contains the DOS startup code/kernel and is loaded by the boot sector code. It is definitely not a text file. It's responsible for loading CONFIG.SYS, a few drivers required by windows, then command.com or win.com.
(While you're at it, command.com isn't a.com file, since it outgrew the 64k limit)
Second, most people would argue that you should not be putting 'real' data in attributes, but rather in elements.
Then I would argue that XML is bloated and ugly.
A small amount of bloat is ok, sure, but putting each piece of that in a separate element makes it huge. Even after compression you'll have a significant increase in size.
Also, you'll won't be able to easily read it manually because the 'real' data is lost in the noise of tags. (how often do you surf the web looking at HTML source?)
I was thinking more from the viewpoint of some person who didn't design the file format of named.conf or whatever, but wants to write his own tool to parse it.
Still, most of them are pretty similar. Probably the only reason there isn't a generic parser is that the parsing is so simple that no one thinks it's worthwhile.
Nearly all of them are a keyword followed by some number of whitespace-separated tokens. Lines starting with # are comments (and often;). Meaning for the fields is derived from order rather than named attributes. You've got practically all the parsing you need in std::istream.
It's ad hoc, but it's still pretty standardized. There's more variation than XML, but it's still a lot easier to write a parser for. (granted you don't have to write one for XML, but *someone* did)
Well, honestly I don't know. XML using separate tags for everything is bloated and ugly. XML using attributes is much less so.
I personally would prefer the less descriptive method if there's unambiguous resolution. No one would split a floating point number into a separately labelled integer and fractional part because there's a simple, universal standard for expressing them together.
most other non-xml config files in/etc, like say hosts, DNS zone files, named.conf, passwd/shadow, hosts.allow/deny, sendmail.mc or resolv.conf (etc. etc.)
all these can be parsed but they all require *different* code for each config file.
Nonsense, if you're smart about your parser, you'll need about 3. If you're not smart about your parser, you'd probably design lousy XML anyway.
how do I quote strings, how do I escape newlines, how do I mark nested scopes, what happens when the string delimiter character occurs inside a string, how do I deal with comments, what is the character set, is there a formal grammar for the document, etc etc
afaik, most config files ignore these issues, but you could easily separate these options from the core of the parser. Pass them in as a traits class or something.
Slashdot Mirror
I bet they came from a Unix machine, I hear they have demons.
Well what if you have a packet that's part of a vi clone with b00bies that will enlarge your penis? Or an internal Microsoft memo that contains pictures of dead babies being eaten by a man covered in feces?
Internet protocols have to be flexible, you know.
I'm waiting for the year that every story on the front page is the same.
refer to RFC 2471, which established the current address allocation: "These addresses are temporary and will be reclaimed in the future."
And why are they closing the 6bone? "As IPv6 is beginning its production deployment it is appropriate to plan for the phaseout of the 6bone."
They're just cleaning up from the testing phase so they can move into official use. It's only a step backwards if you consider the end of a beta test a step backwards.
I've not met any other blokes insecure enough to whine about it.
Insecurity or not, making any sort of grammar commentary is a high sin. Most people will avoid commenting because they don't want to be harrassed in return.
It's kind of a pity, without constructive, non-derogitory criticism, how is anyone going to improve their poor grammar? Even scathing remarks are helpful, would you rather have someone tell you that you're an idiot once, or would you rather have many people think so forever?
(fwiw, I prefer the gender neutral "he/him/his" or, more commonly, "they/them/their", which is probably technically wrong, but more smooth.)
Plus, the third-world manufacturer can still sell widgets to other countries, whose products will have an advantage over the U.S., since they'll be using half-price widgets!
"I think we should tax the foreigner abroad."
Nor is anything else that was built with VC++ (or visual studio in general) and thus uses its implementation of malloc.
How do you know that? Link, please.
Even if everything that was compiled under Visual Studio used its malloc (which is not true), that still has to get the memory from the system sometime.
FWIW, I have a thin 8 1/2 x 11" fresnel that can easily melt a lump of regular solder (then turn it into a wierd yellowish powdery-crystally thing)
iirc, you can also use it to peel traces off of circuit boards. (it also melts sand, ashes, chars wood instantly...)
This place claims 25-35%
The compression artifacts in jpeg 2000 are a lot better than standard jpeg as well, for when you make things really small.
Is it worth an extra $3-$5 to be able to backup the CD
Backup? Try play.
Copy protection often breaks CD-ROM drives' ability to ready them in a sensible way at all. I always rip CDs when I buy them and listen to them as MP3, either on the computer or on my NEXII. I leant my CD player to my sister since I never use it. (CDs are a pain when you have better options)
So is it work $3-$5 extra so I can actually use it? Maybe, but then most CDs aren't worth $3 to begin with.
Yeah I dunno, I got sshd for free when I set up my home server. Do hardware failures happen often enough that you'll need to see POST on some machine every week?
Why is it that those who complain about SUVs are always the ones who don't have them?
Why is it that those who complain about spammers are always the ones who don't spam?
Could you provide an example? Last time I set up a firewall on Linux, I had to use ipchains, which was baffling to no end. I gave up on any manual configuration and went with linuxconf.
pf is practically configured in english, I actually know where the config file is, and I can easily understand it weeks later without digging through the man page again.
I've taken a quick look around www.netfilter.org, but the best I've seen is stuff like:
iptables -t filter -A INPUT -d $PUBLIC -m state --state INVALID -j log
iptables -t filter -A INPUT -s localhost -d localhost -j ACCEPT
iptables -t filter -A INPUT -s $PUBLIC -d $PUBLIC -j ACCEPT
iptables -t filter -A INPUT -d $PUBLIC -m state --state RELATED,ESTABLISHED -j ACCEPT
which is still fairly opaque compared to:
pass in quick on $xif inet proto udp from 10.150.88.1 to 255.255.255.255 keep state
pass in quick on $xif inet proto tcp from any to ($xif) port 22 keep state
block in log all
What's more, few if any Gnutella developers will ever support Gnutella2 because of the divisive way that it was introduced, permanently fracturing the Gnutella community, with almost all of the Gnutella community still working on Gnutella because they were never told of the so-called Gnutella2 until it was slashdotted, much as we're seeing today.
No problem, they just need to come out with Gnutella3, thus grabbing back the spotlight by "superceding" this.
This only matters if you're trying to compare processors rather than how well Adobe's software runs on those processors.
And I dunno about them, but I'd try to keep as much code as possible identical between the two systems.
Why would the cops let you know what number they're calling from? You can only block numbers if your phone company tells you what number it is.
There *will* be an increased memory footprint, unless you never take advantage of the larger address space.
All pointers double in size, and the page table will grow.
Understand this: No corporation has ever made enough money out of something.
At some point it costs the corporation more to dig up and make a copy for distribution than anyone is willing to pay for it. When this happens, it is impossible for them to make any more money off of this product.
Windows 1.0 probably falls into this category.
OTOH, it also costs something to dig it up and release it for free. With books it's a little different, since the book's content is already out there.
I wouldn't be suprized to find that the Window 1.0 source code no longer exists. In that case, the cost to release it for free is enormous.
Are you sure it was the monitor?
I'd think dead pixels on a CRT are more likely caused by a the video card, either a bad cell in its RAM, or a glitch somewhere else. (especially if it shows up on more than one monitor)
Technically, LCD displays don't have a refresh rate, but they do have a maximum change rate which is effectively the same thing in this case.
On an LCD:
1 / (response time) = maximum frame rate
Whereas on a CRT:
refresh rate = maximum frame rate
So you can loosely compare refresh rate to the inverse of the response time.
Most modern LCDs operate at only 24 bit color.
How many video cards can put out more than 8 bits per primary? Only really high-end graphics people are going to care about that anyway, the gamut is probably much more important.
MSDOS.SYS was a text file containing some boot options. It had a large block of comments that had the message you remembered. (some programs required that it be some minimum size)
.com file, since it outgrew the 64k limit)
IO.SYS contains the DOS startup code/kernel and is loaded by the boot sector code. It is definitely not a text file. It's responsible for loading CONFIG.SYS, a few drivers required by windows, then command.com or win.com.
(While you're at it, command.com isn't a
Second, most people would argue that you should not be putting 'real' data in attributes, but rather in elements.
Then I would argue that XML is bloated and ugly.
A small amount of bloat is ok, sure, but putting each piece of that in a separate element makes it huge. Even after compression you'll have a significant increase in size.
Also, you'll won't be able to easily read it manually because the 'real' data is lost in the noise of tags. (how often do you surf the web looking at HTML source?)
I was thinking more from the viewpoint of some person who didn't design the file format of named.conf or whatever, but wants to write his own tool to parse it.
;). Meaning for the fields is derived from order rather than named attributes. You've got practically all the parsing you need in std::istream.
Still, most of them are pretty similar. Probably the only reason there isn't a generic parser is that the parsing is so simple that no one thinks it's worthwhile.
Nearly all of them are a keyword followed by some number of whitespace-separated tokens. Lines starting with # are comments (and often
It's ad hoc, but it's still pretty standardized. There's more variation than XML, but it's still a lot easier to write a parser for. (granted you don't have to write one for XML, but *someone* did)
So element attributes are the way to go?
Well, honestly I don't know. XML using separate tags for everything is bloated and ugly. XML using attributes is much less so.
I personally would prefer the less descriptive method if there's unambiguous resolution. No one would split a floating point number into a separately labelled integer and fractional part because there's a simple, universal standard for expressing them together.
most other non-xml config files in /etc, like say hosts, DNS zone files, named.conf, passwd/shadow, hosts.allow/deny, sendmail.mc or resolv.conf (etc. etc.)
all these can be parsed but they all require *different* code for each config file.
Nonsense, if you're smart about your parser, you'll need about 3. If you're not smart about your parser, you'd probably design lousy XML anyway.
how do I quote strings, how do I escape newlines, how do I mark nested scopes, what happens when the string delimiter character occurs inside a string, how do I deal with comments, what is the character set, is there a formal grammar for the document, etc etc
afaik, most config files ignore these issues, but you could easily separate these options from the core of the parser. Pass them in as a traits class or something.