Actually, Google would be well placed to do this -- at least from a test standpoint. They (working with Earthlink) are looking to provide wireless to all of San Francisco. Once that infrastructure is in place, they have a full network that can do geospatially based maps, ads, etc. Imagine walking around San Francisco wearing the Google Googgles (TM) - information pops up based on which building you look at (they've already done the street level mapping) - including businesses that are located there. Or if you are walking (or driving) and pre-program in a map to display with arrows and the like.. I'm certain others will add to this...
I did a quick whois lookup to see when yellowpages.com and citysearch.com were registered.
I think citysearch.com will qualify as prior art... as the whole concept was to provide geographically specific searches.
Domain Name: citysearch.com
Created on..............: Wed, Nov 22, 1995
Expires on..............: Wed, Nov 20, 2013
Record last updated on..: Fri, Jun 02, 2006
Yellowpages.com's whois says:
Record expires on 10-Oct-2016.
Record created on 05-Apr-1996.
Database last updated on 12-Jun-2007 20:39:45 EDT.
A little later but they were on the web at that point too.. and did area code based lookups and zip code based lookups if memory serves. I wonder what the WayBack machine would have to say about each site...
Ah.. mentioned this to a friend of mine and was commenting about being able to drive to the tip of South America all the way to London after they completed this. He said that he had four words for me. "Are we there yet?" Then said something about "Hmm.. I guess this justifies the larger hard drive on the iPod or going ahead and signing up for satellite radio"
The problem with just adding yourself temporarily to the permissions when the support request comes in is that you seem to also have to either wait a couple of hours for the mailbox to allow the access, or restart the Information Store on the server (which disconnects all the clients from the server).
Exchange tip: If you find you need to add yourself and permissions are not updating quickly enough, you can do the following:
1) Check to see which server the mailbox resides on and which DC that Exchange server thinks is it's primary, then connect to that domain controller and add your account there.
2) Run the Recipient Update Service - tell it to update changes made.
That should get you in without having to wait for replication or dropping the information store service (eeek.) Works in 2000 and 2003. Haven't tried it with 2007 but then I haven't played with 2007 yet.
The former Grateful Dead lyricist that the EFF is using isn't just a spokesperson, he's also a founding member. You know - one of the people looking far enough ahead to see that it was going to be an issue before it became an issue. As far as locations are concerned, they didn't move to the West Coast - they were founded on the West Coast - San Francisco being only a short drive away from the headquarters of Yahoo, Google, Intel, Sun, Apple, eBay, Cisco, HP, Seagate, Western Digital - those companies who's technologies are the reason that the EFF needs to exist?
If that happened, that sounds pretty stupid. When I go on vacation to Miami, should I be allowed to refuse sales taxes on the souvenir crap I buy, because I didn't live there to vote on the tax rate?
Actually, yes. Well, the process is you keep all of your receipts, fill out the proper paperwork[PDF Warning] and send it in to get your refund. Then you fill out the appropriate forms in your state of residence and write a check to your state tax board based on what the sales tax would be had you made your purchase in your home state.
Hmm. Salmon Rushdie might disagree with you about the whole "bury it" bit. And I'm certain there are a few embassy staffers in a few countries around the world that also might have a comment or three based on some published cartoon drawings?
Two small websites and Exchange and pretending to be a file server. The mail traffic is from a few lists plus the household stuff - but then it's Exchange so go figure.
System information for \\: Uptime: 380 days, 3 hours, 43 minutes, 28 seconds Kernel version: Microsoft Windows 2000, Uniprocessor Free Product type: Advanced Server Product version: 5.0 Service pack: 4
And it isn't even that decent a box. A skilled IT staff can keep any operating system running for long uptimes -- it isn't the uptime of the box that you should look at -- it is the uptime of the application - if you've had to restart it (for whatever reason - died/patched/etc.) then zero out the clock and start counting again.
Oh come on now... data hostage because you can't hook up a hard drive directly to transfer? Have to go through a second machine, upload and download? I take it you have never had to transfer data from a machine that had a live network connection that you couldn't bring down -- for instance - fear that the drive wouldn't come back up.
scp works. So does ftp for that matter (which has a native Windows client so you could do it from there). Or heck, if your Linux box speaks samba, you can just mount the share from the Windows box and use cp. (Or copy/paste). Sorry - this particular diatribe just goes over the top. Geez.
hmm.. call bull malarkey on this one. System ROM is a 64K block and starts at F000 - which means the top of memory would be at 960K and the max you could get if you didn't have to load in DOS. (assuming of course you were able to get the system to ignore the video ROMs in the B000 range - which isn't exactly the easiest thing in the world to do)
4. Will they even cover Peter Wiggin? It will be hard to do that as well, especially his rise to power on the nets...
I never really liked that subplot. Taking over the world by blogging? Just didn't seem plausible, even for a couple of supergenius prodigies.
What's really going to bake your noodle later is when you think about when the book was written. "Blogging" didn't exist. Neither did the world-wide networks and usage of them as we do today. Copyrights are 1977, 1985 and 1991.
It isn't that hard to set this up properly. You just have to fix the accounts of the individuals who aren't hosted on Exchange to be mail-enabled users instead of mailboxes. And for the delivery you should be able to send to user1@host.domain.com (with alternate addressing being user1@domain.com)... It's also easy to configure to say that you aren't the master of the domain and forward all non-local delivery mail to a mailhub system that handles final delivery. Your problem here sounds more configuration issue than exchange won't allow you.
Almost all call boxes exist where cell phones work perfectly. In fact, the kind I'm talking about use the cellular phone system to make their calls. Your juvenile slander is uncalled for.
Maybe they had more of a point 15 years ago when most of them were being installed (at great expense I'm sure due to the newness of the technology), but they are hardly a necessary service, and now they're practically useless. All I'm asking is, were they really worth the money?
Actually, a long time ago - these were all wired to land lines. It was actually cheaper to install the cellular/solar ones as they really could be placed anywhere that the sun could shine and a cell tower reached vs. having to run miles of telephone wire out to each location. And although it seems like everyone and their brother have cell phones, everyone really doesn't. Or their battery may die (especially going up I-5 when there were large stretches of analog service only zones at one time...) In general, everyone is going to call in accidents, but a flat tire or car stalling - how often have you whizzed by at 85+ 30 miles outside Kettleman City and seen a car on the side of the road with someone standing next to it? That call box is available for those who aren't as lucky to own a cell phone - or for some reason their phone isn't working.
Yep again. Except Exchange (2000/2003) doesn't install without IIS being already installed - it is a pre-requisite.
Hence, IIS does smtp email, not exchange.
Kinda. The smtp engine in IIS is extended when Exchange 200x is installed to support assorted Exchange specific functions.
Exchange runs happily without that useless public standard, smtp.
Exchange 5.5 does indeed. However 200x doesn't - it supports smtp natively as the primary protocol for exchanging traffic between Exchange servers. If smtp isn't running, Exchange doesn't communicate. (yes, there are a few caveats to this, but that discussion can be saved for the next "OSS Exchange Killer" news story).
Buncha useless whining fscking idiots.
Er.. pot. kettle. hmm.
Bleh. Quick, where's that URL for that study about how useless people always think they know more than other people?
In your case, assuming you're running httpd on your local system, try http://127.0.0.1/clue/
Or at least make it a possibility that it is illegal for the following to exist if it passes:
1) Upload/Download ratios of any kind no matter what the purpose.
The act states that anything that gives incentives or better performance by requiring the end user to participate more in a possibly infringing act... wait a minute - does this mean that slashdot's moderation system would have to be reworked -- you get moderation rights by reading more... hmm. The possibilities and permutations of twisting this bugger.
2) FTP, SCP, SFTP combined with directory listing of files.
Well -- it's definitely peer-to-peer. Just twist...
3) E-mail
Okay - not quite peer-to-peer however definitely has infringing abilities.. er.. okay.. this would tkae a lot of bending.
If you stretch it a bit further, it could also make VPN networks illegal.
Wouldn't it be kind of fun to have the Congressional Network shut down due to infringing activity?:)
Very good question. It's highly pathetic IMHO. I keep hearing about organization after organization switching to Exchange, despite the fact that it's by far the most expensive available (my organization did a cost study on several different groupware/mail products, and we found that Exchange cost TEN TIMES what Bynari Insight would cost, and significantly more than the second most expensive) and a standards-non-compliance nightmare.
Have you really gone through and looked at what you get when you go the whole Exchange route vs. what else is out there? Microsoft pricing and security aside for the moment (yes, it sucks. That's a given. No arguments.) the equivalent you get in the Open Source world for Exchange is...
SMTP server NNTP server LDAP server IMAP server POP server HTTP server Database Server MS-Specific (MAPI) server
This is all the back-end stuff that has nothing to do with Outlook. In addition, all of the various servers act well distributed and use the ldap server for central authentication for all users. The database server currently doesn't do replication for individual mailboxes but does for the NNTP portion. The SMTP server uses the LDAP server to reference valid mailbox addresses and the specific database server users's mailboxes reside on. The MAPI, POP and IMAP servers all use LDAP to reference where the specific database server user's mailboxes reside on. They also use LDAP for authentication.
(This is why you can use IMAP [which is still supported half-assed in Exchange 2003] or POP with any client - and the http stuff with any modern web client)
Then let's add the Outlook client. This builds the calendaring into the picture. Server-side everyone's scheduling information is stored in a newsgroup and an entry in the database. When building a new meeting, the client queries the newsgroup to see if time is clear or not (to allow checking to see if everyone is free) and then sends the meeting info out to the various invites. Oh - and the client also allows setting up for viewing other's calendars and administrative assistants can handle their bosses' mail and calendaring functions through the client without having to lose their own stuff or log in as their boss. And I haven't touched a lot of the other server-side stuff and how 3rd parties have built tools around it.
Consider the complexity of mail and groupware. It can't be squat compared to, say, the Linux Kernel. So why is it so evasive?
Ease of use. Ease to support. Interoperability. Support of just about any mail client. Ties to make the functions that are not mail-specific work even with non-MS mail clients. (link on meeting invite to the web based item for completion)
These are just a few of the reasons why organizations go this route and it has nothing to do with being in Microsoft's pocket to begin with. And it doesn't include things like tying your voice mail into your inbox so that it is available via your wireless device, your phone or your e-mail client.. or being able to schedule multi-user conference calls that update calendars and send out notifications or....:)
The open source packages that are available today do not have the level of integration or functionality that is offered via Exchange to an organization. Once the above si working fairly seamlessly as an integrated package that could be deployed - then a true challenge to Exchange would exist - for now it isn't there.
Apache has a much larger base than IIS, yet most of the exploits are for IIS.
Would that be Apache on Linux, Apache on Solaris, Apache on NetBSD, Apache on FreeBSD, Apache on OSX, Apache on Windows, Apache on DOS, Apache on your Toaster, Apache on [etc], or IIS on Windows?
It's much easier to exploit a webserver when the underlying OS is the same...
Slashdot Mirror
Um, you're incorrect about this. RU-486 has been accepted in the U.S. since 2000.
Actually, Google would be well placed to do this -- at least from a test standpoint. They (working with Earthlink) are looking to provide wireless to all of San Francisco. Once that infrastructure is in place, they have a full network that can do geospatially based maps, ads, etc. Imagine walking around San Francisco wearing the Google Googgles (TM) - information pops up based on which building you look at (they've already done the street level mapping) - including businesses that are located there. Or if you are walking (or driving) and pre-program in a map to display with arrows and the like.. I'm certain others will add to this...
I did a quick whois lookup to see when yellowpages.com and citysearch.com were registered.
I think citysearch.com will qualify as prior art... as the whole concept was to provide geographically specific searches.
Domain Name: citysearch.com
Created on..............: Wed, Nov 22, 1995
Expires on..............: Wed, Nov 20, 2013
Record last updated on..: Fri, Jun 02, 2006
Yellowpages.com's whois says:
Record expires on 10-Oct-2016.
Record created on 05-Apr-1996.
Database last updated on 12-Jun-2007 20:39:45 EDT.
A little later but they were on the web at that point too.. and did area code based lookups and zip code based lookups if memory serves. I wonder what the WayBack machine would have to say about each site...
Ah.. mentioned this to a friend of mine and was commenting about being able to drive to the tip of South America all the way to London after they completed this. He said that he had four words for me. "Are we there yet?" Then said something about "Hmm.. I guess this justifies the larger hard drive on the iPod or going ahead and signing up for satellite radio"
Exchange tip: If you find you need to add yourself and permissions are not updating quickly enough, you can do the following:
1) Check to see which server the mailbox resides on and which DC that Exchange server thinks is it's primary, then connect to that domain controller and add your account there.
2) Run the Recipient Update Service - tell it to update changes made.
That should get you in without having to wait for replication or dropping the information store service (eeek.) Works in 2000 and 2003. Haven't tried it with 2007 but then I haven't played with 2007 yet.
The former Grateful Dead lyricist that the EFF is using isn't just a spokesperson, he's also a founding member. You know - one of the people looking far enough ahead to see that it was going to be an issue before it became an issue. As far as locations are concerned, they didn't move to the West Coast - they were founded on the West Coast - San Francisco being only a short drive away from the headquarters of Yahoo, Google, Intel, Sun, Apple, eBay, Cisco, HP, Seagate, Western Digital - those companies who's technologies are the reason that the EFF needs to exist?
I had to've been trolled here.
If that happened, that sounds pretty stupid. When I go on vacation to Miami, should I be allowed to refuse sales taxes on the souvenir crap I buy, because I didn't live there to vote on the tax rate?
Actually, yes. Well, the process is you keep all of your receipts, fill out the proper paperwork[PDF Warning] and send it in to get your refund. Then you fill out the appropriate forms in your state of residence and write a check to your state tax board based on what the sales tax would be had you made your purchase in your home state.
Hmm. Salmon Rushdie might disagree with you about the whole "bury it" bit. And I'm certain there are a few embassy staffers in a few countries around the world that also might have a comment or three based on some published cartoon drawings?
Two small websites and Exchange and pretending to be a file server. The mail traffic is from a few lists plus the household stuff - but then it's Exchange so go figure.
I don't think he'd be allowed in the U.S. being a convicted criminal and all... those pesky immigration rules. (Hi Gary!)
Oh come on now... data hostage because you can't hook up a hard drive directly to transfer? Have to go through a second machine, upload and download? I take it you have never had to transfer data from a machine that had a live network connection that you couldn't bring down -- for instance - fear that the drive wouldn't come back up.
scp works. So does ftp for that matter (which has a native Windows client so you could do it from there). Or heck, if your Linux box speaks samba, you can just mount the share from the Windows box and use cp. (Or copy/paste). Sorry - this particular diatribe just goes over the top. Geez.
hmm.. call bull malarkey on this one. System ROM is a 64K block and starts at F000 - which means the top of memory would be at 960K and the max you could get if you didn't have to load in DOS. (assuming of course you were able to get the system to ignore the video ROMs in the B000 range - which isn't exactly the easiest thing in the world to do)
4. Will they even cover Peter Wiggin? It will be hard to do that as well, especially his rise to power on the nets...
I never really liked that subplot. Taking over the world by blogging? Just didn't seem plausible, even for a couple of supergenius prodigies.
What's really going to bake your noodle later is when you think about when the book was written. "Blogging" didn't exist. Neither did the world-wide networks and usage of them as we do today. Copyrights are 1977, 1985 and 1991.
It isn't that hard to set this up properly. You just have to fix the accounts of the individuals who aren't hosted on Exchange to be mail-enabled users instead of mailboxes. And for the delivery you should be able to send to user1@host.domain.com (with alternate addressing being user1@domain.com)... It's also easy to configure to say that you aren't the master of the domain and forward all non-local delivery mail to a mailhub system that handles final delivery. Your problem here sounds more configuration issue than exchange won't allow you.
The government has a job that pays you to jerk off to porn - it's called the FCC...
(okay okay... back to work for me)
F*cking
Ball-busting
Imbeciles
(now for 20 extra points, what movie is that line from?)
Only in Soviet Russia...
Not all SUVs are big/bad and evil. Sometimes you just have to look for them. You might be surprised.
Almost all call boxes exist where cell phones work perfectly. In fact, the kind I'm talking about use the cellular phone system to make their calls. Your juvenile slander is uncalled for.
Maybe they had more of a point 15 years ago when most of them were being installed (at great expense I'm sure due to the newness of the technology), but they are hardly a necessary service, and now they're practically useless. All I'm asking is, were they really worth the money?
Actually, a long time ago - these were all wired to land lines. It was actually cheaper to install the cellular/solar ones as they really could be placed anywhere that the sun could shine and a cell tower reached vs. having to run miles of telephone wire out to each location. And although it seems like everyone and their brother have cell phones, everyone really doesn't. Or their battery may die (especially going up I-5 when there were large stretches of analog service only zones at one time...) In general, everyone is going to call in accidents, but a flat tire or car stalling - how often have you whizzed by at 85+ 30 miles outside Kettleman City and seen a car on the side of the road with someone standing next to it? That call box is available for those who aren't as lucky to own a cell phone - or for some reason their phone isn't working.
fscking newbies
IIS installs SMTPD
Yep.
Exchange does NOT install SMTPD.
Yep again. Except Exchange (2000/2003) doesn't install without IIS being already installed - it is a pre-requisite.
Hence, IIS does smtp email, not exchange.
Kinda. The smtp engine in IIS is extended when Exchange 200x is installed to support assorted Exchange specific functions.
Exchange runs happily without that useless public standard, smtp.
Exchange 5.5 does indeed. However 200x doesn't - it supports smtp natively as the primary protocol for exchanging traffic between Exchange servers. If smtp isn't running, Exchange doesn't communicate. (yes, there are a few caveats to this, but that discussion can be saved for the next "OSS Exchange Killer" news story).
Buncha useless whining fscking idiots.
Er.. pot. kettle. hmm.
Bleh. Quick, where's that URL for that study about how useless people always think they know more than other people?
In your case, assuming you're running httpd on your local system, try http://127.0.0.1/clue/
Or at least make it a possibility that it is illegal for the following to exist if it passes:
:)
1) Upload/Download ratios of any kind no matter what the purpose.
The act states that anything that gives incentives or better performance by requiring the end user to participate more in a possibly infringing act... wait a minute - does this mean that slashdot's moderation system would have to be reworked -- you get moderation rights by reading more... hmm. The possibilities and permutations of twisting this bugger.
2) FTP, SCP, SFTP combined with directory listing of files.
Well -- it's definitely peer-to-peer. Just twist...
3) E-mail
Okay - not quite peer-to-peer however definitely has infringing abilities.. er.. okay.. this would tkae a lot of bending.
If you stretch it a bit further, it could also make VPN networks illegal.
Wouldn't it be kind of fun to have the Congressional Network shut down due to infringing activity?
Very good question. It's highly pathetic IMHO. I keep hearing about organization after organization switching to Exchange, despite the fact that it's by far the most expensive available (my organization did a cost study on several different groupware/mail products, and we found that Exchange cost TEN TIMES what Bynari Insight would cost, and significantly more than the second most expensive) and a standards-non-compliance nightmare.
.. :)
Have you really gone through and looked at what you get when you go the whole Exchange route vs. what else is out there? Microsoft pricing and security aside for the moment (yes, it sucks. That's a given. No arguments.) the equivalent you get in the Open Source world for Exchange is...
SMTP server
NNTP server
LDAP server
IMAP server
POP server
HTTP server
Database Server
MS-Specific (MAPI) server
This is all the back-end stuff that has nothing to do with Outlook. In addition, all of the various servers act well distributed and use the ldap server for central authentication for all users. The database server currently doesn't do replication for individual mailboxes but does for the NNTP portion. The SMTP server uses the LDAP server to reference valid mailbox addresses and
the specific database server users's mailboxes reside on. The MAPI, POP and IMAP servers all use LDAP to reference where the specific database server user's mailboxes reside on. They also use LDAP for authentication.
(This is why you can use IMAP [which is still supported half-assed in Exchange 2003] or POP with any client - and the http stuff with any modern web client)
Then let's add the Outlook client. This builds the calendaring into the picture. Server-side everyone's scheduling information is stored in a newsgroup and an entry in the database. When building a new meeting, the client queries the newsgroup to see if time is clear or not (to allow checking to see if everyone is free) and then sends the meeting info out to the various invites.
Oh - and the client also allows setting up for viewing other's calendars and administrative assistants can handle their bosses' mail and calendaring functions through the client without having to lose their own stuff or log in as their boss. And I haven't touched a lot of the other server-side stuff and how 3rd parties have built tools around it.
Consider the complexity of mail and groupware. It can't be squat compared to, say, the Linux Kernel. So why is it so evasive?
Ease of use. Ease to support. Interoperability. Support of just about any mail client. Ties to make the functions that are not mail-specific work even with non-MS mail clients. (link on meeting invite to the web based item for completion)
These are just a few of the reasons why organizations go this route and it has nothing to do with being in Microsoft's pocket to begin with. And it doesn't include things like tying your voice mail into your inbox so that it is available via your wireless device, your phone or your e-mail client.. or being able to schedule multi-user conference calls that update calendars and send out notifications or..
The open source packages that are available today do not have the level of integration or functionality that is offered via Exchange to an organization. Once the above si working fairly seamlessly as an integrated package that could be deployed - then a true challenge to Exchange would exist - for now it isn't there.
3 is a crowd...
Huh? I thought 3 is a magic number.
(off topic yeah I know.. back to work for me)
Apache has a much larger base than IIS, yet most of the exploits are for IIS.
Would that be Apache on Linux, Apache on Solaris, Apache on NetBSD, Apache on FreeBSD, Apache on OSX, Apache on Windows, Apache on DOS, Apache on your Toaster, Apache on [etc], or IIS on Windows?
It's much easier to exploit a webserver when the underlying OS is the same...