Actully I do my hard thumping at 3:15am.. I think your clock is slow...
He lives 600 miles west of you, in the next time zone. I think you're both in sync.
Mark
Re:For those unfortunate times...
on
42-Volt Autos
·
· Score: 1
No, you just need to jump start your car with 4 friends in parallel.
Slashdot readers will be delighted to hear that the number-of-friends bar has been lowered: you only need 3 of 'em.
(And they have to be in series.)
12V (nominal) automotive systems usually run at 14V with a hot alternator. The 42V (nominal) system is 36V at the batteries with no generation. For some reason*, "they" chose to use the higher number as the nominal figure this time around.
* probably marketing, 'cuz Bigger Is Better, right?
The reality is that there's plenty of IPv4 space available and there will be for years to come. APNIC may be nearing the exhaustion of the address space currently assigned to that region of the world, but that doesn't mean that more space won't be assigned.
The Asia-Pacific region got additional IP address space in April 2003. And February 2003. And July 2002. And December 2001, September 2001, and December 2000. And so on.
And there's more space where that came from. Plenty of it. In fact, nearly half of IPv4's 32-bit address space is still up for grabs.
For more, see this and various other pages reachable by cutting-edge clickable links!
Have you actually tried it and listened to the results? It actually works fairly well. If you have $10,000 speakers at home then what are you doing listening to any form of compressed music? But for most of us it sounds just fine.
For "most of us," it may, but I'm not going to pay for the privilege.
Right now, part of the problem is that ISPs and users are bearing the cost of spam. In the end, any of the costs to the ISPs are passed on to their customers. Making us pay to send, is going to cut down on the usefulness of e-mail to legitimate users. If I have to pay by the message, I'm going to think twice about a quick note to a friend asking if he wants to meet for lunch. I'll pass along fewer cool URLs.
You're taking sender-pays much too literally.
A proper sender-pays system does not imply micropayments or line-item e-mail fees from your provider. The costs of sender-pays systems can be covered in the same ways as the receiver-pays services you use now. Micropayments could, and in some cases do, cover the cost of service under the current architecture too, but most operators offer e-mail as a package, a bundled service, or display advertisements to cover their costs. The only difference with a sender-pays system is that the bulk of the underlying costs cover the expenses involved in sending messages rather than receiving them.
Until then I don't see the big deal. You can burn your downloads to a CD right? Just burn them to a CD and then rip the CD as oggs or mp3s if you really need to share.
You're already purchasing lossily-compressed music. Now you propose running it through a lossy compressor again?
It may be quick, it may be dirty, and it may work*, but I'll pass.
By law, you can always obtain a copy of any publicly-regulated utility's tariff. Contact the utility or your state's PSC, PUC, or other regulator. If not available online, you should be able to receive information through the mail. Since when has "online" become the yardstick of availability?
Verizon will be extremely pissed about this. They will throw everything they have to prevent it. Maybe even sue as well as continue the usual heavy lobbing the baby bells are known for.
If everything they've got includes competitive bids, let them bring it on.
Verizon's actually in a position to win, anyway. Empire City Subway, a wholly-owned subsidiary of Verizon, has held a long-term contract with the city for over a century to build, maintain, and lease space in the underground conduit network in Manhattan and much of the Bronx. This is not an annual contract, and it's not in any danger of being opened for competitive bids. With few responsibilities and a steady revenue stream, ECS is a moneymaker.
Rememeber they paid for laying the fibers so they can service the financial industry based in lower manhattan.
This is about the municipal telecom contracts. Let the financial industry negotiate their own.
In their opinion its their god given right to protect their assets at all costs.
They will, regardless. Whom do you suppose the smaller guys will lease facilities from in the event that the city awards some contracts to other parties?
There is even a building with the old bell labs logo still on that is visual from the brooklynn bridge. I believe that one is owned by AT&T today and yes they also laid hundreds of miles of fiber there as well.
That's Verizon's Pearl Street CO (NYCMNYPS), and the Bell logo was replaced with a Verizon one over a year ago.
Of course it will expire once you stop paying the sub fee, but which do you think is the better deal: $7500 to fill a 30GB player (7500 songs at $1 each) with iTunes Music Store, or $120 a year with the ability to swap in new music whenever you want?
Where in the article does it say anything about $120/year?
Are we supposed to be so gullible as to believe that a subscription service would allow unlimited "rentals" for a flat fee of $10/month? What kind of an asinine business model would that be? Does anyone really think that the recording industry would ever make such an offering?
I've had . in my path for many years, and wouldn't do without it. It's at the end of my path, so there's no way you're going to spoof my "cat". It's only those who have . at the beginning of their path that get screwed.
Oh, you've never accidentally run a chomd, or maybe l s-l?
SEATTLE, March 20, 2004 -- Amazon, Inc. (Pink Sheets: AMZNQ) announced today that the U.S. Patent Office has granted it a patent for "a method to systematically patent all things obvious and previously discovered by others." Jeff Bezos, CEO of Amazon, indicated that this patent places the company firmly on the path to reorganization as an intellectual property and rights management firm. "I fully expect this strategy to enable us to emerge from Chapter 11 bankruptcy protection later this year," Bezos said at a press conference this morning, where he outlined his plan to an enthusiastic crowd of such totalitarian dictators as Fidel Castro and Bill Gates. The remaining points of his strategy include patenting patent infringement as well as a method to litigate patent infringement cases.
Supposedly the Sprint PCS Vision Merlin card looks like a generic LAN card to the OS and requires no special drivers, but still has a Sprint app for establishing the connection. I'd love to hear if someone knows more about that or the others under Linux.
Phones are visible to the computer as plain old AT-compatible modems. From what I remember, so are the "Merlin" PCMCIA cards. You don't need a special applicaton to make the connection, all you need is the PPP client built into the operating system, and possibly a tweaked modem script to feed it the right initialization string. Linux? OS X? No problem. This has been working on our side of the river for a few years now.
Barring any good info on that, the Sony 608 is being announced by SprintPCS Tuesday, and it's got Bluetooth GPRS modem support like the T68i. No word from Sprint on whether you're allowed to use that, or if the Sprint PCS Vision service is restricted to the phone browser for that as it is with the other Sprint phones. Here's hoping.
GPRS is packet data for GSM. The T608, being a CDMA handset, uses data over CDMA. 1xRTT cdma2000, where available.
Last I checked, you could plug into a Sprint phone and surf. Or a phone from any of a number of other carriers. Nothing new there, and all stateside.
Why not share the code that parses and assemble the packets?
There's nothing wrong with that. Many projects, of which BIND is one, aim to produce a monolithic DNS server capable of performing both authoritative and recursive service. On the other hand, a project which aims to focus on a more specific aspect of DNS should not be discounted for the reason that it ignores all the other aspects. On the contrary, the focused nature of such a project is indeed a benefit for those that do not require the flexibility of something like BIND, but instead seek (for example) performance, scalability, and security.
That's not to say that BIND and other monolithic DNS servers are terrible. In fact, I run BIND and find it quite agreeable. The code (versions >=9) is clean and easy to digest and modify, and the developers have been receptive to bona fide bug reports.
Now I am going to dig an even bigger hole for myself, but aren't most DNS servers authoratitive for one or several domains and caching data for all the others?
Not in this day and age. Real DNS servers managed by competent administrators are dedicated to one task or the other.
Why shouldn't they benefit from the optimized authoratitive code?
It's optimized for the wrong purpose. In general, a recursive server would be better off with its own optimizations. This is the general KISS principle. It's a guideline, not a hard-and-fast rule. One of the goals of the NSD project, and other similar projects, is to produce an authoritative-only nameserver. Recursive operations being outside of this scope, they're omitted. If that makes the software unattractive to you, then so be it. But have no fear, there are plenty of recursive-only nameservers out there that have been optimized for their tasks.
The market for DNS server software that is able to perform both authoritative and recursive service from within a single process has shrunk to an incredibly small size. There are just too many problems when the DNS universe is shared by the two data sources, and we've realized that this sharing is not necessary. So, while the world may see future development of new do-it-all DNS servers, we shouldn't be bound to developing future DNS servers to meet the needs of yesterday's network. If there's a better way to do it, we shouldn't let prior practice discourage us.
I guess you wouldn't like embedded Linux then, because desktop Linux has all that bloated mainframe scalabilty code that is not needed on a PDA.
Hyperbole much? Besides, I don't like Linux or PDAs for other reasons.:)
I don't see how refusing to reuse code without a specific reason is superior.
Y'know, I bet that some of the NSD code would be reusable in a recursive server. Much of that code would come from the top end, where data is moved between the network and the nameserver process. That code is largely trivial. It's the equivalent of int main(int argc,char **argv). You can optimize that as much as you want, but the end result won't be much different than what you started with.
If BIND sucks or is not modular enough, then write a nicer, more modular DNS server that covers the needs of most users.
I think you've mistaken my viewpoint for a complaint.
Finally, why shouldn't dialup users run a caching-only DNS server to reduce the number of lookups going over the modem?
There's no reason they shouldn't. It's an excellent idea. Just use a tool designed for the job. Recursive-only? Great. Big monolithic DNS, SMTP, and HTTP server with integral seat warmer? Great. But something designed for an entirely different target audience? It's not happening.
One bad thing is that NSD is only for authoratitive name servers, so the efforts spent developing, debugging, porting and optimizing its code will be wasted for most of us.
Ooh, is that flamebait I smell?
It's long since been agreed upon that combining authoritative and recursive name services is a terrible idea. With that in mind, is there any reason for your authoritative DNS server to contain recursive code? Do recursive servers (for most of us?) benefit at all from the authoritative code?
Most of us in the scope that you use it may never realize incredible benefits from software targeted at most of us network operators. Just because the effort spent developing this software will not directly benefit you doesn't mean it was wasted.
Except for the original iBook, which is universally identified as the Toilet Seat, I refer to them by year. I wish Apple would officially do the same. It seems to work for the automotive industry.
(It seems to work for Microsoft, too - never mind.)
People seem to be interpreting this to mean that Mac OS X applications will never use file locking unless the programmer explicitly requests it. This may have been true prior to 10.2 (Jaguar), but is no longer the case. The tech note is a little bit sketchy on this point, but it was written before the release of Jaguar.
Applications that open files with calls to the standard Mac frameworks will use locking. A Carbon app that locks in OS 9 will still lock when running under a recent version of OS X.
Until this [major] oversight was fixed, workarounds were required in application code. This is no longer the case.
Only applications that use open() directly need to take extra steps to lock files. This is the way it's done in the Unix world, and Apple has chosen the correct implementation by not forcing the standard open() call to lock.
Flat files in/etc are cumbersome and inefficient, and don't scale beyond a single computer with a handful of entries. For that reason, alternatives have been available for many years. YP, NIS+, and now LDAP are other mechanisms that address these shortcomings - perhaps you've seen an nsswitch.conf file? The functionality is present in any recent Unix[-like] system, the only difference is that Apple has enabled it by default.
Traditionally, these "alternative" directory sources have been a major nuisance to configure. Kudos to Apple for providing a system that relies on proper databases for directory information out of the box. Bonus points for not forcing it down the throats of hobbyists with a single machine and a small handful of users.
Slashdot Mirror
Actully I do my hard thumping at 3:15am.. I think your clock is slow...
He lives 600 miles west of you, in the next time zone. I think you're both in sync.
Mark
No, you just need to jump start your car with 4 friends in parallel.
Slashdot readers will be delighted to hear that the number-of-friends bar has been lowered: you only need 3 of 'em.
(And they have to be in series.)
12V (nominal) automotive systems usually run at 14V with a hot alternator. The 42V (nominal) system is 36V at the batteries with no generation. For some reason*, "they" chose to use the higher number as the nominal figure this time around.
* probably marketing, 'cuz Bigger Is Better, right?
Mark
Fear.
Uncertainty.
Doubt.
The reality is that there's plenty of IPv4 space available and there will be for years to come. APNIC may be nearing the exhaustion of the address space currently assigned to that region of the world, but that doesn't mean that more space won't be assigned.
The Asia-Pacific region got additional IP address space in April 2003.
And February 2003.
And July 2002.
And December 2001, September 2001, and December 2000.
And so on.
And there's more space where that came from. Plenty of it. In fact, nearly half of IPv4's 32-bit address space is still up for grabs.
For more, see this and various other pages reachable by cutting-edge clickable links!
Mark
Have you actually tried it and listened to the results? It actually works fairly well. If you have $10,000 speakers at home then what are you doing listening to any form of compressed music? But for most of us it sounds just fine.
For "most of us," it may, but I'm not going to pay for the privilege.
Mark
Right now, part of the problem is that ISPs and users are bearing the cost of spam. In the end, any of the costs to the ISPs are passed on to their customers. Making us pay to send, is going to cut down on the usefulness of e-mail to legitimate users. If I have to pay by the message, I'm going to think twice about a quick note to a friend asking if he wants to meet for lunch. I'll pass along fewer cool URLs.
You're taking sender-pays much too literally.
A proper sender-pays system does not imply micropayments or line-item e-mail fees from your provider. The costs of sender-pays systems can be covered in the same ways as the receiver-pays services you use now. Micropayments could, and in some cases do, cover the cost of service under the current architecture too, but most operators offer e-mail as a package, a bundled service, or display advertisements to cover their costs. The only difference with a sender-pays system is that the bulk of the underlying costs cover the expenses involved in sending messages rather than receiving them.
Mark
Until then I don't see the big deal. You can burn your downloads to a CD right? Just burn them to a CD and then rip the CD as oggs or mp3s if you really need to share.
You're already purchasing lossily-compressed music. Now you propose running it through a lossy compressor again?
It may be quick, it may be dirty, and it may work*, but I'll pass.
* for some values of "work"
Mark
In the US, this obligation applies to every telco anyway, under FCC regs, but the filed tariffs aren't online, only displayed in the FCC library IIRC.
Verizon publishes their tariffs online.
The NYS Public Service Commission also publishes tariffs of some of the utilities they regulate online, although Verizon's are not currently among those available.
By law, you can always obtain a copy of any publicly-regulated utility's tariff. Contact the utility or your state's PSC, PUC, or other regulator. If not available online, you should be able to receive information through the mail. Since when has "online" become the yardstick of availability?
Mark
Verizon will be extremely pissed about this. They will throw everything they have to prevent it. Maybe even sue as well as continue the usual heavy lobbing the baby bells are known for.
If everything they've got includes competitive bids, let them bring it on.
Verizon's actually in a position to win, anyway. Empire City Subway, a wholly-owned subsidiary of Verizon, has held a long-term contract with the city for over a century to build, maintain, and lease space in the underground conduit network in Manhattan and much of the Bronx. This is not an annual contract, and it's not in any danger of being opened for competitive bids. With few responsibilities and a steady revenue stream, ECS is a moneymaker.
Rememeber they paid for laying the fibers so they can service the financial industry based in lower manhattan.
This is about the municipal telecom contracts. Let the financial industry negotiate their own.
In their opinion its their god given right to protect their assets at all costs.
They will, regardless. Whom do you suppose the smaller guys will lease facilities from in the event that the city awards some contracts to other parties?
There is even a building with the old bell labs logo still on that is visual from the brooklynn bridge. I believe that one is owned by AT&T today and yes they also laid hundreds of miles of fiber there as well.
That's Verizon's Pearl Street CO (NYCMNYPS), and the Bell logo was replaced with a Verizon one over a year ago.
And so what?
Mark
Of course it will expire once you stop paying the sub fee, but which do you think is the better deal: $7500 to fill a 30GB player (7500 songs at $1 each) with iTunes Music Store, or $120 a year with the ability to swap in new music whenever you want?
Where in the article does it say anything about $120/year?
Are we supposed to be so gullible as to believe that a subscription service would allow unlimited "rentals" for a flat fee of $10/month? What kind of an asinine business model would that be? Does anyone really think that the recording industry would ever make such an offering?
Mark
I've had . in my path for many years, and wouldn't do without it. It's at the end of my path, so there's no way you're going to spoof my "cat". It's only those who have . at the beginning of their path that get screwed.
Oh, you've never accidentally run a chomd, or maybe l s-l?
(Ouch, those hurt to type.)
Mark
Option-e agieu (sp?)
aigu, but in English, we say acute. é
Option-i carat (?)
circumflex (circonflexe in French). î
Regards,
The Cunning Linguist
I love "metric time" as much as the next guy, but I wouldn't trust any review that equates 47 seconds with 0.47 minutes [from the review].
Mark
Superflous Patenting Patented
SEATTLE, March 20, 2004 -- Amazon, Inc. (Pink Sheets: AMZNQ) announced today that the U.S. Patent Office has granted it a patent for "a method to systematically patent all things obvious and previously discovered by others." Jeff Bezos, CEO of Amazon, indicated that this patent places the company firmly on the path to reorganization as an intellectual property and rights management firm. "I fully expect this strategy to enable us to emerge from Chapter 11 bankruptcy protection later this year," Bezos said at a press conference this morning, where he outlined his plan to an enthusiastic crowd of such totalitarian dictators as Fidel Castro and Bill Gates. The remaining points of his strategy include patenting patent infringement as well as a method to litigate patent infringement cases.
Mark
Phones are visible to the computer as plain old AT-compatible modems. From what I remember, so are the "Merlin" PCMCIA cards. You don't need a special applicaton to make the connection, all you need is the PPP client built into the operating system, and possibly a tweaked modem script to feed it the right initialization string. Linux? OS X? No problem. This has been working on our side of the river for a few years now.
GPRS is packet data for GSM. The T608, being a CDMA handset, uses data over CDMA. 1xRTT cdma2000, where available.
Last I checked, you could plug into a Sprint phone and surf. Or a phone from any of a number of other carriers. Nothing new there, and all stateside.
Mark
There's nothing wrong with that. Many projects, of which BIND is one, aim to produce a monolithic DNS server capable of performing both authoritative and recursive service. On the other hand, a project which aims to focus on a more specific aspect of DNS should not be discounted for the reason that it ignores all the other aspects. On the contrary, the focused nature of such a project is indeed a benefit for those that do not require the flexibility of something like BIND, but instead seek (for example) performance, scalability, and security.
That's not to say that BIND and other monolithic DNS servers are terrible. In fact, I run BIND and find it quite agreeable. The code (versions >=9) is clean and easy to digest and modify, and the developers have been receptive to bona fide bug reports.
Not in this day and age. Real DNS servers managed by competent administrators are dedicated to one task or the other.
It's optimized for the wrong purpose. In general, a recursive server would be better off with its own optimizations. This is the general KISS principle. It's a guideline, not a hard-and-fast rule. One of the goals of the NSD project, and other similar projects, is to produce an authoritative-only nameserver. Recursive operations being outside of this scope, they're omitted. If that makes the software unattractive to you, then so be it. But have no fear, there are plenty of recursive-only nameservers out there that have been optimized for their tasks.
The market for DNS server software that is able to perform both authoritative and recursive service from within a single process has shrunk to an incredibly small size. There are just too many problems when the DNS universe is shared by the two data sources, and we've realized that this sharing is not necessary. So, while the world may see future development of new do-it-all DNS servers, we shouldn't be bound to developing future DNS servers to meet the needs of yesterday's network. If there's a better way to do it, we shouldn't let prior practice discourage us.
Hyperbole much? Besides, I don't like Linux or PDAs for other reasons.
Y'know, I bet that some of the NSD code would be reusable in a recursive server. Much of that code would come from the top end, where data is moved between the network and the nameserver process. That code is largely trivial. It's the equivalent of int main(int argc,char **argv). You can optimize that as much as you want, but the end result won't be much different than what you started with.
I think you've mistaken my viewpoint for a complaint.
There's no reason they shouldn't. It's an excellent idea. Just use a tool designed for the job. Recursive-only? Great. Big monolithic DNS, SMTP, and HTTP server with integral seat warmer? Great. But something designed for an entirely different target audience? It's not happening.
Mark
init.
Mark
Ooh, is that flamebait I smell?
It's long since been agreed upon that combining authoritative and recursive name services is a terrible idea. With that in mind, is there any reason for your authoritative DNS server to contain recursive code? Do recursive servers (for most of us?) benefit at all from the authoritative code?
Most of us in the scope that you use it may never realize incredible benefits from software targeted at most of us network operators. Just because the effort spent developing this software will not directly benefit you doesn't mean it was wasted.
Oh, I see. It was flamebait, after all.
Mark
...how IE for Windows would fare with these tests.
Based on experience, I'm not holding my breath.
Mark
Except for the original iBook, which is universally identified as the Toilet Seat, I refer to them by year. I wish Apple would officially do the same. It seems to work for the automotive industry.
(It seems to work for Microsoft, too - never mind.)
Mark
1999 PowerBook G3 - or Bronze or Lombard
People seem to be interpreting this to mean that Mac OS X applications will never use file locking unless the programmer explicitly requests it. This may have been true prior to 10.2 (Jaguar), but is no longer the case. The tech note is a little bit sketchy on this point, but it was written before the release of Jaguar.
Applications that open files with calls to the standard Mac frameworks will use locking. A Carbon app that locks in OS 9 will still lock when running under a recent version of OS X.
Until this [major] oversight was fixed, workarounds were required in application code. This is no longer the case.
Only applications that use open() directly need to take extra steps to lock files. This is the way it's done in the Unix world, and Apple has chosen the correct implementation by not forcing the standard open() call to lock.
Mark
Flat files in /etc are cumbersome and inefficient, and don't scale beyond a single computer with a handful of entries. For that reason, alternatives have been available for many years. YP, NIS+, and now LDAP are other mechanisms that address these shortcomings - perhaps you've seen an nsswitch.conf file? The functionality is present in any recent Unix[-like] system, the only difference is that Apple has enabled it by default.
Traditionally, these "alternative" directory sources have been a major nuisance to configure. Kudos to Apple for providing a system that relies on proper databases for directory information out of the box. Bonus points for not forcing it down the throats of hobbyists with a single machine and a small handful of users.
Mark