Firewire is a physical transport layer for SCSI[*] which has been around for a very long time. The rub is simply the lack of drives with a native firewire interface. Everything I've ever seen contains a IDE/1394 bridge.
Firewire is a more generalized interface -- storage, video, communications, etc. Where Serial ATA is (at the moment) 100% focused on storage. This is where the current bloody ATA mess comes from (IDE was engineered for hard drives and then people started plugging other crap on the chain.)
* Technically, ATA is a physical transport for SCSI too. It's just in a red-headed, bastard, step-child fashion.
AMEN! If the head of the UNIX ship doesn't know the difference between COPYRIGHT and ROOT, then it's time to take 'em on a boat trip into international waters...
But maybe [top management] are not educable
While I would tend to agree with that, I've seen exceptions. (I was actually very surprised.)
The address of "s" doesn't really amount to much in a sane world. (There are rare, strange situtations where knowing the memory locations of storage is important, but that's not important here.) You don't want gets() changing the storage location of "s"; you want it to change the value of the pointer itself which is the value at the address of "s". In actuality, the function places data at the memory location pointed to by the value of "s".
And so they continue on the road of lameness. There's very (*very*) little reason to run fiber to a desktop. There's not that much of a reason to run fiber to a server.
In my book, the only reason to use fiber is distance. (And the fact that Cisco doesn't support copper GBICs on hardly anything.)
While, yes, they are the same technology, IDSL and ISDN are different creatures. IDSL is ISDN with all of the telco stuff removed... it's just the raw bit stream, no switches, no channels, just bits.
That extra 16k doesn't make that much of a difference. Add to the equation the lack of compression available to most IDSL setups and the ISDN line can actually be faster for most things. Noncompressable stuff moves at about 7.5KBps per channel; compressable stuff (like web pages) can move in excess of 80KBps per channel. I've used ISDN for a long time. It's sufficent for most tasks. (Yes, it's too slow for the modern punks to steal everything they can find.)
And if I wanted to pay BellSouth a fraction of a penny per D channel packet, I could have 144k too. Oh, and ISDN has one major advantage: it's not attached to an specific ISP. When your DSL ISP goes up in smoke, how long will it take to get a new connection? With ISDN, I can connect through whomever I want. If your DSL ISP is having connectivity/routing troubles, you're stuck. With ISDN, I can call a different ISP and get on with business.
Stop being so stupid. Their restrictions are of economic value not because they will be sued for what you do. The ISP sells you an ADSL connection for 50$/month with the stipulation that it will be for your personal use (read: residential service.)
If you pay 50$/month and then connect your entire neighborhood, you've cheated the ISP out of selling those people the same $50 service. You're acting as a commercial entity... from a house in a residential zone... without reporting the income from your little venture to the IRS.
does the landlord get punished for trying to provide a service
That's different. In that context, the landlord is a service provider and is accountable in the same manner as the ISP.
your teenagers... Shall we prosecute you?
As said teen's legal guardian, you are responsible for their actions Furthermore, the name on the account is most likely going to be the parents as "teens" (read: minors) cannot execute a legal contract. (And yes, they will. I've seen it done before my very eyes -- I was there when the "teen" was hauled away in 'cufts.)
VH1 showed "Ren's Evil Half" (or whatever) but they won't show "Man's Best Friend"?
VH1 was showing episodes for a few months but then just stopped. NIK was showing them, but they never aired a single episode when they said they were going to.
Re:Its decent, but I would scarecely call it a PVR
on
DishPVR 721 Review
·
· Score: 2
Historically, all of the dishplayers have sucked in very major ways -- so much so that EchoStar has sued Microsoft repeatedly (gee, I wonder why they suck.) I'm surprised they didn't simply walk down the street and ask Tivo, Inc. to recode the existing DTivo software to deal with the EchoStar signal (DVB vs. DSS) which the hardware can do.
Looking at the screen shots, this thing looks like only a commetic difference from the UTV. Give them some time. If they are developing the system themselves instead of letting M$ screw it up, it'll get better over time. Even the tivo was pretty crappy in the early days.
The stats are very easy to explain... It actually takes time to perform a detailed investigation in the cases of violent theft. The insidious, "white collar" crimes take almost no time to investigate -- once the crime is detected, they pretty much already know who did it and where the money went.
Which is easier to track down: a) a bunch of guys wearing ski masks storming into a bank with guns, or b) the bank manager stuffing a stack of 20's in his pocket when he leaves for lunch everyday?
The police investigate "a". It's very obvious the money is gone. The hard part is now in tracking down who took it. The bank investigates "b". It's rather difficult to see money is missing -- no one opens the vault one morning and half the money is gone. Once someone notices there's money missing, it's a very short trip to find out where it's going. And then the police are called in.
In one case, it's obvious a crime has been commited. In the other, it isn't.
The solution involving the loop cable seems slightly antiquated, since conventional TV cards use a Conexant chip, which writes the data directly via the PCI bus into the graphics card's memory. The solution from Sigma Designs does offer one advantage, however - the PCI bus is not overloaded, thus avoiding problems, particularly with older computers. The manufacturer also cuts costs with this solution.
It's not "antiquated", it's "stupid". There has never been a technological reason for this. You don't have to use the PCI bus to write directly to the frame buffer. The "vga feature connector" has existed much longer than any local bus (even predating EISA.) The BS about bus saturation is laughable -- exactly what would be competing with the PCI transfer? As for costs, that is very much a proven lie! (They may claim that it's cheaper only because the technology is already developed and they won't have to devote developer time for a new driver interface. But don't let Sigma's marketing people fool you, the silicon for that hardware overlay is not cheap and certainly not free.)
Anyone who has ever dealt with Sigma Designs, Real Magic, et. al. knows very well why the external, analog overlay is there. It's there for one almighty reason: DVD CCA licensing rules. There is zero chance the decoded content can be "stolen" in digital format. Rumor has it, even the external SDRAM on the card doesn't hold the decoded data during playback. Where I live, that's called "paranoid."
Thing is, he's not first to do it. Hundreds of people have done what he's done. Only none of them are wasting sourceforge space for their pre-school tinkering. I'm sorry, but that's all this is: a five year old discovering the door switch on the cloths dryer.
If you want to see real CIDS, go talk to people who make and use military encryption devices. (shake some of them too hard and they electrically self-destruct -- they erase their tiny little brain.)
BGP router identifier XXX, local AS number XXX BGP table version is 15846057, main routing table version 15846057 114307 network entries and 335645 paths using 23170999 bytes of memory 58200 BGP path attribute entries using 3260264 bytes of memory 50933 BGP AS-PATH entries using 1314460 bytes of memory 1 BGP community entries using 24 bytes of memory 15 BGP route-map cache entries using 240 bytes of memory 80699 BGP filter-list cache entries using 968388 bytes of memory Dampening enabled. 271 history paths, 458 dampened paths 3 received paths for inbound soft reconfiguration BGP activity 396089/9002885 prefixes, 4768424/4432779 paths, scan interval 15 secs
BGP router identifier XXX, local AS number XXX BGP table version is 15847879, main routing table version 15847879 114302 network entries and 335626 paths using 23169830 bytes of memory 58207 BGP path attribute entries using 3266312 bytes of memory 51007 BGP AS-PATH entries using 1317248 bytes of memory 1 BGP community entries using 24 bytes of memory 15 BGP route-map cache entries using 240 bytes of memory 80841 BGP filter-list cache entries using 970092 bytes of memory Dampening enabled. 759 history paths, 578 dampened paths 3 received paths for inbound soft reconfiguration BGP activity 396098/9003023 prefixes, 4768452/4432826 paths, scan interval 15 secs
Ahh, "chello.nl"... USENET whore capital of the internet [no offense]. When I had a full news feed from UUNET, alt.chello alone was 25% of the traffic (~30G per day) -- I haven't decided which is scarier... UUNET being able to move that much stuff around the planet or the fact that one provider is generating that much stuff (mostly warez, a little porn, and ~2k of discussions.)
All good points except they are all wrong. AT&T doesn't send out paper bills; that's handled electronically by the local telco. The receiving and processing of payments are, again, handled electronically through the same telco. There's almost zero human interaction in the whole system. Aside from auditing and associated fraud investigations, about the only thing that requires human time is billing errors and disputes.
In the months that I make no long distance calls, I present no overhead in any processing. There are no CDRs to be processed on my behalf. The only "overhead" is some space in a database saying I'm a customer and even that is suspect based on the number of times AT&T tries to sell me a service I'm already buying.
At any rate, why would AT&T be sending a bill if there's nothing for me to pay?
Trust me, the billing processes are no where near as complex and time consuming as you think. (I work for a (business) telco. There aren't hundreds of people handling billing. Nor do we charge a minimum or any of those stupid fees.)
That's because of those billing padding service provisions of the FCC -- universal service fees, etc. They are normally charged by the LD carrier. If there is no LD carrier, then the local telco is responsible for collecting them. None of them actually o to the FCC, btw.
Around here, Bell South doesn't allow multiple lines to the same location to be configured differently. If you have three analog lines, they will all have the same service.
Excuse me? This is the same company that imposes a floor on long distance usage -- 3$ per month minimum. They claim this is for "billing overhead" which is 150% complete bullshit; it pads their bottom line by hundred of millions per month.
Read your contract. Your 50$ does not buy you continuous 1.5/384 service. If you sling your full rate "24 hours a day / 7 days a week", I'd give it two weeks before AT&T terminates your service (with a good chance of it being perminant termination.)
do massive networks really have random outages for no reason at all?
Yes, yes they do. I'm afraid say it, but things break and often you never figure out why. Sure, it's very likely someone did something or some sequence of things that ultimately causes a problem, but getting someone to stand up and say "yeah, I fscked it up. Sorry." is rare.
Oddly enough, I've spent most of today (along with a half dozen others) trying to restore connectivity on an SDMS ring. It's working now, but nobody knows why. Nothing at all changed on anything, anywhere to break it. And there were no errors visable on any device. Packets go in, but don't come out; yet other data flows across the loop unfettered the whole time!
(if I didn't know better, I'd say Microsoft must be involved.)
And let's not forget how much money they make every year and yet still increase the price of stamps almost yearly. My personal favorite was the bullshit remark of increasing to 25 cents so people can "buy a stamp with a single coin."
It's a lot like the "touch tone" service fee charged by Bell South for almost 30 years. I remember when they started that to "pay for upgrades to the phone system" to support touch tone. They continued to charge that fee until a few years ago.
Slashdot Mirror
Firewire is a physical transport layer for SCSI[*] which has been around for a very long time. The rub is simply the lack of drives with a native firewire interface. Everything I've ever seen contains a IDE/1394 bridge.
Firewire is a more generalized interface -- storage, video, communications, etc. Where Serial ATA is (at the moment) 100% focused on storage. This is where the current bloody ATA mess comes from (IDE was engineered for hard drives and then people started plugging other crap on the chain.)
* Technically, ATA is a physical transport for SCSI too. It's just in a red-headed, bastard, step-child fashion.
- But maybe [top management] are not educable
While I would tend to agree with that, I've seen exceptions. (I was actually very surprised.)Okidata!
"char *s" means s is a "pointer to char"
"( &s )" means the "address of s"
The address of "s" doesn't really amount to much in a sane world. (There are rare, strange situtations where knowing the memory locations of storage is important, but that's not important here.) You don't want gets() changing the storage location of "s"; you want it to change the value of the pointer itself which is the value at the address of "s". In actuality, the function places data at the memory location pointed to by the value of "s".
And so they continue on the road of lameness. There's very (*very*) little reason to run fiber to a desktop. There's not that much of a reason to run fiber to a server.
In my book, the only reason to use fiber is distance. (And the fact that Cisco doesn't support copper GBICs on hardly anything.)
You can netboot windows. An "nfsroot" windows is a different story.
While, yes, they are the same technology, IDSL and ISDN are different creatures. IDSL is ISDN with all of the telco stuff removed... it's just the raw bit stream, no switches, no channels, just bits.
IDSL = 144kbps
ISDN = 16k(D) + 64k(B) + 64k(B) = 16kbps + 128kbps
That extra 16k doesn't make that much of a difference. Add to the equation the lack of compression available to most IDSL setups and the ISDN line can actually be faster for most things. Noncompressable stuff moves at about 7.5KBps per channel; compressable stuff (like web pages) can move in excess of 80KBps per channel. I've used ISDN for a long time. It's sufficent for most tasks. (Yes, it's too slow for the modern punks to steal everything they can find.)
And if I wanted to pay BellSouth a fraction of a penny per D channel packet, I could have 144k too. Oh, and ISDN has one major advantage: it's not attached to an specific ISP. When your DSL ISP goes up in smoke, how long will it take to get a new connection? With ISDN, I can connect through whomever I want. If your DSL ISP is having connectivity/routing troubles, you're stuck. With ISDN, I can call a different ISP and get on with business.
Stop being so stupid. Their restrictions are of economic value not because they will be sued for what you do. The ISP sells you an ADSL connection for 50$/month with the stipulation that it will be for your personal use (read: residential service.)
If you pay 50$/month and then connect your entire neighborhood, you've cheated the ISP out of selling those people the same $50 service. You're acting as a commercial entity... from a house in a residential zone... without reporting the income from your little venture to the IRS.
TW makes the content being "trashed" by the ads. They probably still wouldn't care.
- does the landlord get punished for trying to provide a service
That's different. In that context, the landlord is a service provider and is accountable in the same manner as the ISP.- your teenagers
... Shall we prosecute you?
As said teen's legal guardian, you are responsible for their actions Furthermore, the name on the account is most likely going to be the parents as "teens" (read: minors) cannot execute a legal contract. (And yes, they will. I've seen it done before my very eyes -- I was there when the "teen" was hauled away in 'cufts.)The person who "owns" the internet connection/computer. Barring that, the property owner.
VH1 showed "Ren's Evil Half" (or whatever) but they won't show "Man's Best Friend"?
VH1 was showing episodes for a few months but then just stopped. NIK was showing them, but they never aired a single episode when they said they were going to.
Historically, all of the dishplayers have sucked in very major ways -- so much so that EchoStar has sued Microsoft repeatedly (gee, I wonder why they suck.) I'm surprised they didn't simply walk down the street and ask Tivo, Inc. to recode the existing DTivo software to deal with the EchoStar signal (DVB vs. DSS) which the hardware can do.
Looking at the screen shots, this thing looks like only a commetic difference from the UTV. Give them some time. If they are developing the system themselves instead of letting M$ screw it up, it'll get better over time. Even the tivo was pretty crappy in the early days.
Unfortunately, blocking everything originating from AS701 would mean about 90% of the internet would simply disappear. Maybe that's what you'd like?
The stats are very easy to explain... It actually takes time to perform a detailed investigation in the cases of violent theft. The insidious, "white collar" crimes take almost no time to investigate -- once the crime is detected, they pretty much already know who did it and where the money went.
Which is easier to track down:
a) a bunch of guys wearing ski masks storming into a bank with guns, or
b) the bank manager stuffing a stack of 20's in his pocket when he leaves for lunch everyday?
The police investigate "a". It's very obvious the money is gone. The hard part is now in tracking down who took it. The bank investigates "b". It's rather difficult to see money is missing -- no one opens the vault one morning and half the money is gone. Once someone notices there's money missing, it's a very short trip to find out where it's going. And then the police are called in.
In one case, it's obvious a crime has been commited. In the other, it isn't.
- The solution involving the loop cable seems slightly antiquated, since conventional TV cards use a Conexant chip, which writes the data directly via the PCI bus into the graphics card's memory. The solution from Sigma Designs does offer one advantage, however - the PCI bus is not overloaded, thus avoiding problems, particularly with older computers. The manufacturer also cuts costs with this solution.
It's not "antiquated", it's "stupid". There has never been a technological reason for this. You don't have to use the PCI bus to write directly to the frame buffer. The "vga feature connector" has existed much longer than any local bus (even predating EISA.) The BS about bus saturation is laughable -- exactly what would be competing with the PCI transfer? As for costs, that is very much a proven lie! (They may claim that it's cheaper only because the technology is already developed and they won't have to devote developer time for a new driver interface. But don't let Sigma's marketing people fool you, the silicon for that hardware overlay is not cheap and certainly not free.)Anyone who has ever dealt with Sigma Designs, Real Magic, et. al. knows very well why the external, analog overlay is there. It's there for one almighty reason: DVD CCA licensing rules. There is zero chance the decoded content can be "stolen" in digital format. Rumor has it, even the external SDRAM on the card doesn't hold the decoded data during playback. Where I live, that's called "paranoid."
So that's what happens to the Earth at the end of Babylon 5!
Thing is, he's not first to do it. Hundreds of people have done what he's done. Only none of them are wasting sourceforge space for their pre-school tinkering. I'm sorry, but that's all this is: a five year old discovering the door switch on the cloths dryer.
If you want to see real CIDS, go talk to people who make and use military encryption devices. (shake some of them too hard and they electrically self-destruct -- they erase their tiny little brain.)
- BGP router identifier XXX, local AS number XXX
After 11am (US/Eastern):BGP table version is 15846057, main routing table version 15846057
114307 network entries and 335645 paths using 23170999 bytes of memory
58200 BGP path attribute entries using 3260264 bytes of memory
50933 BGP AS-PATH entries using 1314460 bytes of memory
1 BGP community entries using 24 bytes of memory
15 BGP route-map cache entries using 240 bytes of memory
80699 BGP filter-list cache entries using 968388 bytes of memory
Dampening enabled. 271 history paths, 458 dampened paths
3 received paths for inbound soft reconfiguration
BGP activity 396089/9002885 prefixes, 4768424/4432779 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
xxx.xxx.xxx.xxx 4 1239 6691013 160774 15845983 0 0 2d07h 113727
xxx.xxx.xxx.xxx 4 701 5769835 160662 15846057 0 0 7w0d 110579
xxx.xxx.xxx.xxx 4 2548 5018626 160732 15846051 0 0 04:34:35 110994
- BGP router identifier XXX, local AS number XXX
That's about 170 routes lost. That doesn't look too bad. However, that could be 170BGP table version is 15847879, main routing table version 15847879
114302 network entries and 335626 paths using 23169830 bytes of memory
58207 BGP path attribute entries using 3266312 bytes of memory
51007 BGP AS-PATH entries using 1317248 bytes of memory
1 BGP community entries using 24 bytes of memory
15 BGP route-map cache entries using 240 bytes of memory
80841 BGP filter-list cache entries using 970092 bytes of memory
Dampening enabled. 759 history paths, 578 dampened paths
3 received paths for inbound soft reconfiguration
BGP activity 396098/9003023 prefixes, 4768452/4432826 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
xxx.xxx.xxx.xxx 4 1239 6691412 160782 15847825 0 0 2d07h 113560
xxx.xxx.xxx.xxx 4 701 5770381 160670 15847879 0 0 7w0d 110410
xxx.xxx.xxx.xxx 4 2548 5019004 160740 15847859 0 0 04:42:31 110823
Ahh, "chello.nl"... USENET whore capital of the internet [no offense]. When I had a full news feed from UUNET, alt.chello alone was 25% of the traffic (~30G per day) -- I haven't decided which is scarier... UUNET being able to move that much stuff around the planet or the fact that one provider is generating that much stuff (mostly warez, a little porn, and ~2k of discussions.)
All good points except they are all wrong. AT&T doesn't send out paper bills; that's handled electronically by the local telco. The receiving and processing of payments are, again, handled electronically through the same telco. There's almost zero human interaction in the whole system. Aside from auditing and associated fraud investigations, about the only thing that requires human time is billing errors and disputes.
In the months that I make no long distance calls, I present no overhead in any processing. There are no CDRs to be processed on my behalf. The only "overhead" is some space in a database saying I'm a customer and even that is suspect based on the number of times AT&T tries to sell me a service I'm already buying.
At any rate, why would AT&T be sending a bill if there's nothing for me to pay?
Trust me, the billing processes are no where near as complex and time consuming as you think. (I work for a (business) telco. There aren't hundreds of people handling billing. Nor do we charge a minimum or any of those stupid fees.)
That's because of those billing padding service provisions of the FCC -- universal service fees, etc. They are normally charged by the LD carrier. If there is no LD carrier, then the local telco is responsible for collecting them. None of them actually o to the FCC, btw.
Around here, Bell South doesn't allow multiple lines to the same location to be configured differently. If you have three analog lines, they will all have the same service.
- I don't think AT&T has gotten greedy yet.
Excuse me? This is the same company that imposes a floor on long distance usage -- 3$ per month minimum. They claim this is for "billing overhead" which is 150% complete bullshit; it pads their bottom line by hundred of millions per month.Read your contract. Your 50$ does not buy you continuous 1.5/384 service. If you sling your full rate "24 hours a day / 7 days a week", I'd give it two weeks before AT&T terminates your service (with a good chance of it being perminant termination.)
- do massive networks really have random outages for no reason at all?
Yes, yes they do. I'm afraid say it, but things break and often you never figure out why. Sure, it's very likely someone did something or some sequence of things that ultimately causes a problem, but getting someone to stand up and say "yeah, I fscked it up. Sorry." is rare.Oddly enough, I've spent most of today (along with a half dozen others) trying to restore connectivity on an SDMS ring. It's working now, but nobody knows why. Nothing at all changed on anything, anywhere to break it. And there were no errors visable on any device. Packets go in, but don't come out; yet other data flows across the loop unfettered the whole time!
(if I didn't know better, I'd say Microsoft must be involved.)
And let's not forget how much money they make every year and yet still increase the price of stamps almost yearly. My personal favorite was the bullshit remark of increasing to 25 cents so people can "buy a stamp with a single coin."
It's a lot like the "touch tone" service fee charged by Bell South for almost 30 years. I remember when they started that to "pay for upgrades to the phone system" to support touch tone. They continued to charge that fee until a few years ago.