Yes, you need to escape the spaces when using sed; not sure about other regex implementations, although I expect them to be similar.
Why on earth would you need to do that? Space is not a special character in Unix regular expressions. Your second example doesn't even work! (Quotes are not special characters either)
Digital phone was something like 64kbps, one line in an ISDN. 56k never worked at that speed because of power regulations. I think the max is about 50k. The best I've seen is 33k.
Is that meant to contradict what I said? None of the numbers you give are in baud, they are all in bps.
A 56 kbaud modem is 56 * 10^3 baud/s (power of 10)
AFAIK such a thing does not exist, and if it does exist, it doesn't work on regular phone lines. The most you can get from regular phone lines is 8000baud, since that is the sample rate the digital phone central uses. I don't know how many baud a 56k modem runs at.
People have only mentioned hardware solutions so far (apart from a few useless ones like chattr). You can do this with SELinux, in a way so that it requires a reboot with console access to do anything about it. It may not be enough for you, but it's enough for some people.
Sure, you're doing 30mph, car coming towards you is doing 30mph, closing speed of 60?
If both cars are equal weight and the collision is straight-on, they will both experience a deceleration from 30mph to 0mph. Exactly the same as if they each hit a wall at 30mph.
So euhm... The world is damaged beyond control, humankind is doomed to relive the dark ages, but we're still able to serve webpages (if somebody would want them).
A dirty bomb would cause very very few casualties. Definitely not anything involving humankind reliving the dark ages -- well apart from the dark age justice system that the government of various countries would implement afterwards.
This problem isn't restricted to Suns. In the last hosting environment I managed, all of the Cisco gear had to be hard-coded to full duplex/100Mb in the IOS, as auto-detect was busted. All of the Dell networking gear worked like a champ though. Cisco gear is overrated.
I just don't get this. Auto-detect has never failed me, except when I messed up myself. When one end is hard-coded to full duplex and the other end is autonegotiating, the other end picks half duplex. That's what the standard says must happen, brain-dead though it is. The fix is to set both ends to autonegotiate, or if you like debugging weird problems, hard code both ends to full duplex. Anyway, the problem is gone with gigabit ethernet, because autonegotiation is enforced.
But here's the kicker: The basement computer would be a multi-user system, where all the users of the household (including, for example, the living room display) would be using the same system simultaneously. Their rooms would contain displays and input devices only, wired in by fiber.
Postscript is a proprietary protocol/format owned lock stock and barrel by Adobe.
Nope, Postscript is a standard available under Royalty Free terms. Adobe used to be very fussed about the Postscript trademark, which was somewhat annoying, but AFAIK those days are gone too. The same holds for PDF.
Speaking of reducing necessary bandwidth, when are these ISPs all going to push multicast for media delivery?
Multicast is not going to happen. Every router needs to be aware of every multicast group (e.g. every video and radio station) that someone downstream from it wants. There is no way that can be done.
As always with the Internet, the answer is to make the end points smart and the core dumb. In this case that means the end points should pass the traffic on to other end points close by. AKA peer-to-peer.
I believe they mean doubling *existing* bandwidth, in which case it would indeed cost a lot... that would mean doubling the entire infrastructure of our internet backbone.
In most cases it would just mean using more expensive line cards or perhaps replacing routers. It's very rare that fibers are used to capacity.
I mean, make sure the cars are able to supply power to the grid as well as get power from it. Almost all cars spend most of their time standing still, and their vast battery capacity could be a great help for grid stability and take some load off of dirty peak power plants.
It uses much less power and might be able to talk to handsets as well.
I doubt power consumption really matters. My Nokia E70 sucks juice like crazy when bluetooth is in active use, whereas I haven't really been annoyed by its power consumption when accessing stuff through Wi-fi. The difference in power consumption can't be hugely in bluetooths favour in practice, or it would have been noticeable. 3Mbps is barely enough for UMTS anyway, so it's basically obsolete before it gets off the ground.
Bluetooth is so slow it's useless. Headsets need more bandwidth, so you can't get decent bluetooth headsets. File transfer, forget it. Internet access -- even 3G is faster than bluetooth, so forget that too.
(Except for people who configure their DNS proxies to ignore/override TTL values, but that's their problem.)
Their problem, and a problem for all their customers. Some of the largest ISP's do it.
Re:Here's the Cliffs' Notes version
on
DNS Complexity
·
· Score: 1
I've made the point before (not here though), that The Game of Life is a good example of simple rules creating a (potentially, very) complex situation.
Game of Life is Turing Complete. (Proved the boring way, by simply implementing logic gates.)
Article wrong about Unicode?
on
DNS Complexity
·
· Score: 2, Insightful
From the article: "To express multilingual symbol sets usually means Unicode, whose binary representation is not directly compatible with the upper/lowercase "folding" required for DNS labels."
UTF-8 should be perfectly compatible with the case folding. The character which get folded are in the US-ASCII subset of UTF-8 and therefore have their high bit unset. All multibyte-characters in UTF-8 have the high bit set in each byte, so they aren't subject to that case folding. The DNS standard is, as far as I know, completely UTF-8-compatible except in the places where it explicitly says that "only these particular characters are allowed here".
I know people who can reach into boiling water with their bare hands, if they do it quickly, because they've learned to overcome the reaction to pull their hand back; still, I doubt they'd be able to do the same thing with molten lead or glass)
I've had one of my fingers in molten lead. I wouldn't put my bare hands in boiling water, though.
The advent of multicore CPUs HAS hurt single-threaded app performance. You must compare today's multicore CPUs with what would otherwise exist if development efforts were invested, instead, on accelerating single core performance like had always been done in the past. In that light it's clear that today's single threaded apps would be running faster had technology not changed direction.
I think you're wrong. Multicore didn't require any particular development -- basically it's a cut-and-paste job. Intel even went for the real cut-and-paste job with their quad-core; just producing two dual-core processors and putting them in one package. Increasing single-thread performance on the other hand requires serious research at this point. All the cheap stuff has been done. IPC increases a few percent here and there, with lots of effort, and frequency increases a bit faster than that. Look at the Itanium for a serious attempt at single-thread performance. Not doing well.
I can only say that I agree with you entirely. The CSS box model is completely broken. It can only be made to "work" by generous sprinkling of clear=left etc.
Frankly I would prefer something like LaTeX. XML'ify it if you must. Not that TeX isn't broken itself, with all the fixed limits it has. Those would be easy to fix though, if TeX was unfrozen.
Slashdot Mirror
Yes, you need to escape the spaces when using sed; not sure about other regex implementations, although I expect them to be similar.
Why on earth would you need to do that? Space is not a special character in Unix regular expressions. Your second example doesn't even work! (Quotes are not special characters either)
$ echo foo bar | sed -e 's/o b/!!!/'
fo!!!ar
Digital phone was something like 64kbps, one line in an ISDN. 56k never worked at that speed because of power regulations. I think the max is about 50k. The best I've seen is 33k.
Is that meant to contradict what I said? None of the numbers you give are in baud, they are all in bps.
A 56 kbaud modem is 56 * 10^3 baud/s (power of 10)
AFAIK such a thing does not exist, and if it does exist, it doesn't work on regular phone lines. The most you can get from regular phone lines is 8000baud, since that is the sample rate the digital phone central uses. I don't know how many baud a 56k modem runs at.
If we're talking bits and bytes, then we use the base 2 values. Simple.
Except when we don't. Network speeds are almost always base 10. RAM is basically the only thing where base 2 rules. Even flash is base 10.
People have only mentioned hardware solutions so far (apart from a few useless ones like chattr). You can do this with SELinux, in a way so that it requires a reboot with console access to do anything about it. It may not be enough for you, but it's enough for some people.
Sure, you're doing 30mph, car coming towards you is doing 30mph, closing speed of 60?
If both cars are equal weight and the collision is straight-on, they will both experience a deceleration from 30mph to 0mph. Exactly the same as if they each hit a wall at 30mph.
So euhm... The world is damaged beyond control, humankind is doomed to relive the dark ages, but we're still able to serve webpages (if somebody would want them).
A dirty bomb would cause very very few casualties. Definitely not anything involving humankind reliving the dark ages -- well apart from the dark age justice system that the government of various countries would implement afterwards.
There is a lot of speculation currently about whether this is fraud. They may be intending to run away with the money and not send out any laptops.
This problem isn't restricted to Suns. In the last hosting environment I managed, all of the Cisco gear had to be hard-coded to full duplex/100Mb in the IOS, as auto-detect was busted. All of the Dell networking gear worked like a champ though. Cisco gear is overrated.
I just don't get this. Auto-detect has never failed me, except when I messed up myself. When one end is hard-coded to full duplex and the other end is autonegotiating, the other end picks half duplex. That's what the standard says must happen, brain-dead though it is. The fix is to set both ends to autonegotiate, or if you like debugging weird problems, hard code both ends to full duplex. Anyway, the problem is gone with gigabit ethernet, because autonegotiation is enforced.
But here's the kicker: The basement computer would be a multi-user system, where all the users of the household (including, for example, the living room display) would be using the same system simultaneously. Their rooms would contain displays and input devices only, wired in by fiber.
Yay for the return of the mainframe!
Postscript is a proprietary protocol/format owned lock stock and barrel by Adobe.
Nope, Postscript is a standard available under Royalty Free terms. Adobe used to be very fussed about the Postscript trademark, which was somewhat annoying, but AFAIK those days are gone too. The same holds for PDF.
Speaking of reducing necessary bandwidth, when are these ISPs all going to push multicast for media delivery?
Multicast is not going to happen. Every router needs to be aware of every multicast group (e.g. every video and radio station) that someone downstream from it wants. There is no way that can be done.
As always with the Internet, the answer is to make the end points smart and the core dumb. In this case that means the end points should pass the traffic on to other end points close by. AKA peer-to-peer.
I believe they mean doubling *existing* bandwidth, in which case it would indeed cost a lot... that would mean doubling the entire infrastructure of our internet backbone.
In most cases it would just mean using more expensive line cards or perhaps replacing routers. It's very rare that fibers are used to capacity.
I mean, make sure the cars are able to supply power to the grid as well as get power from it. Almost all cars spend most of their time standing still, and their vast battery capacity could be a great help for grid stability and take some load off of dirty peak power plants.
It uses much less power and might be able to talk to handsets as well.
I doubt power consumption really matters. My Nokia E70 sucks juice like crazy when bluetooth is in active use, whereas I haven't really been annoyed by its power consumption when accessing stuff through Wi-fi. The difference in power consumption can't be hugely in bluetooths favour in practice, or it would have been noticeable. 3Mbps is barely enough for UMTS anyway, so it's basically obsolete before it gets off the ground.
Bluetooth is so slow it's useless. Headsets need more bandwidth, so you can't get decent bluetooth headsets. File transfer, forget it. Internet access -- even 3G is faster than bluetooth, so forget that too.
(Except for people who configure their DNS proxies to ignore/override TTL values, but that's their problem.)
Their problem, and a problem for all their customers. Some of the largest ISP's do it.
I've made the point before (not here though), that The Game of Life is a good example of simple rules creating a (potentially, very) complex situation.
Game of Life is Turing Complete. (Proved the boring way, by simply implementing logic gates.)
From the article: "To express multilingual symbol sets usually means Unicode, whose binary representation is not directly compatible with the upper/lowercase "folding" required for DNS labels."
UTF-8 should be perfectly compatible with the case folding. The character which get folded are in the US-ASCII subset of UTF-8 and therefore have their high bit unset. All multibyte-characters in UTF-8 have the high bit set in each byte, so they aren't subject to that case folding. The DNS standard is, as far as I know, completely UTF-8-compatible except in the places where it explicitly says that "only these particular characters are allowed here".
I know people who can reach into boiling water with their bare hands, if they do it quickly, because they've learned to overcome the reaction to pull their hand back; still, I doubt they'd be able to do the same thing with molten lead or glass)
I've had one of my fingers in molten lead. I wouldn't put my bare hands in boiling water, though.
All my electricity comes from renewable energy (hydro), so his reasoning is pure, distilled bullshit, but he's gonna ban 'em!
The electricity could be exported to displace non-renewable fuels.
One of the most effective ways of observing cancer is to notice that someone dies from it.
The advent of multicore CPUs HAS hurt single-threaded app performance. You must compare today's multicore CPUs with what would otherwise exist if development efforts were invested, instead, on accelerating single core performance like had always been done in the past. In that light it's clear that today's single threaded apps would be running faster had technology not changed direction.
I think you're wrong. Multicore didn't require any particular development -- basically it's a cut-and-paste job. Intel even went for the real cut-and-paste job with their quad-core; just producing two dual-core processors and putting them in one package. Increasing single-thread performance on the other hand requires serious research at this point. All the cheap stuff has been done. IPC increases a few percent here and there, with lots of effort, and frequency increases a bit faster than that. Look at the Itanium for a serious attempt at single-thread performance. Not doing well.
There are only two frequency bands for cellular technology: analog & digital
That is wrong. What gave you that idea?
I can only say that I agree with you entirely. The CSS box model is completely broken. It can only be made to "work" by generous sprinkling of clear=left etc.
Frankly I would prefer something like LaTeX. XML'ify it if you must. Not that TeX isn't broken itself, with all the fixed limits it has. Those would be easy to fix though, if TeX was unfrozen.