Pulled the plug on a live banking AS/400. To make matter worse I then had to sit there during the veeery long IPL - what is it with AS/400s and long IPL times?
I doubt that you will find a single car at a dragstrip, either production based, "doorslammer" or a full rail which isn't controlled and tuned with a laptop in the pits nowadays.
BSD is not dying. I remember reading a survey not a month ago that surveyed some top ISPs. FreeBSD running Apache was, according to the article, the most popular and widely used ISP platform there is. Period.
Linux is trying to "do a Windows" and be all things to all men as quickly as possible.
FreeBSD is more like a working pick-up truck. They don't have a wide range of paint colors and picking up chicks with them can be hard - but they do what they are built for, and they do it very well.
Thats fine, Linux dies. Then there'll be a truck-load of developers ready to work on porting all of the remaining user-land bits of a typical GNU/Linux distro to one of the BSD kernels (OpenBSD, NetBSD, FreeBSD for example)
BSD kernels are unencumbered by System V legacy code, copyright and control - which is basically why Apple's OS X isn't a licensee of SCO's UNIX copyright.
I love the fact that when mentioning free UNIX only Linux gets a mention. This is despite the fact that a huge swathe of ISPs run some sort of *BSD for hosting, security, firewalls, etc.
Not only are they free in both senses of the word but there is no viral GNU license which obliges derivative works from adhering to the license.
If GNU is challenge and Linux destroyed then it will only delay the pervasiveness of "free" Unicies - IBM et al will simply adopt a BSD kernel. BSD kernels were created for the specific tasks of removing the old AT&T/System V licensed code!
It really bugs me when a whole lot of SlashDotters turn around and say: "we need to dump this and switch to this" or some other stupid notion. There is no way we can suplant SMTP - it's too pervasive. We can help cut down a large proportion of spam but actually using what we already have properly:
[1] Configure your reverse mappings for your Internet-facing machines properly. That way we can start checking on reverse lookups which would stop Joe Lusers Windows box on DSL being turned into an SMTP engine.
I know that people can trivially configure their own DNS servers and spoof the forward and reverse mappings, but at least there needs to be an administrative contact on the SOA record and on the WHOIS information; which is something
[2] Get rid of the un-needed use of HTML emails. There is no need for half of the formatting and dross in emails. ASCII does just fine, and provide a link to a website if you need to woo people with eye candy.
[3] Undo some of the supposed "intelligent" behviour of email clients. They should display text first, and do everything else (play sounds, render HTML) as a user-invoked extra
[4] Make it a "must manually do" option to allow SMTP servers to allow relaying from anything other than their internal interface and IP range. Too many products come too open out of the box
[5] Use the TXT record or something similar for SMTP servers to list which domains they serve. That way receiving servers performing a forward/reverse lookup for verification will also be able to see if the domain in the email has been spoofed.
This reminds me of a (possible untrue) dialog I heard somewhere between NASA scientists and their Russia counterparts
NASA: We spent $1million developing a pen to write is space, in zero gravity, upsidedown and on a variety of surfaces. What do you guys use and who much did it cost?
I used to work for Natest in this area. They have been taken over by RBoS so God only knows what they are running now.
Whatever it was, when they migrated to the RBoS backend they took steps about 15 years backwards.
In a personal capacity and in no way reflecting my employers - I would like to voice my utter disgust with both the moral and technical ignorance you have shown by placing wildcards in the.com and.net TLD domain space.
Despite toying with and potentially breaking (MTAs, NXDOMAIN no longer work, port 25 open on your "sitefinder" box, direct to A record mail delivery not working properly, breaking negative caching on.com and.net domains, etc, etc) *the* most important service on the internet, you have also abused your power.
What you have done is akin to putting advertisements on road signs that mislead people who don't know/exactly/ where they want to go to get lost.
The Internet is NOT the World Wide Web; what you have done is NOT merely provide a search facility for people - you have fundamentally broken aspects of the DNS system which were working quite well and there for a good reason.
I would suggest to your Board that having abused your trust, you no longer deem yourself worthy of trust in the SSL certificate arena. I would wager that that business is worth more than a few mispelt URL stats.
And I have sent this to the email address on their SOA record:
In a personal capacity and in no way reflecting my employers - I would like to voice my utter disgust with both the moral and technical ignorance you have shown by placing wildcards in the.com and.net TLD domain space.
Despite toying with and potentially breaking (MTAs, NXDOMAIN no longer work, port 25 open on your "sitefinder" box, direct to A record mail delivery not working properly, breaking negative caching on.com and.net domains, etc, etc) *the* most important service on the internet, you have also abused your power.
What you have done is akin to putting advertisements on road signs that mislead people who don't know/exactly/ where they want to go to get lost.
The Internet is NOT the World Wide Web; what you have done is NOT merely provide a search facility for people - you have fundamentally broken aspects of the DNS system which were working quite well and there for a good reason.
I would suggest to your Board that having abused your trust, you no longer deem yourself worthy of trust in the SSL certificate arena. I would wager that that business is worth more than a few mispelt URL stats.
It's just occured to me what a wonderful Virus infection vector Windows Update would make. All-out access to install stuff on the most prevailent OS in the world today.
Now, where did I put that copy of VCL..?
Re:Wait a minute...
on
OSI vs SCO
·
· Score: -1, Flamebait
Once again postings like this prove that Slashdot is full of CS graduates and home "experts" who wouldn't know true corporate computing environments if they slapped them in the face.
Of course people use AIX.
I wonder what the implications would be if I owned, say, whitewatershafting.com and was forced to move that to whitewatershafting.prn; but I then bought sweetnessandlight.com and provided an instant redirect the the.prn site? The site "lives" in the.prn TLD.....
Slashdot Mirror
See the pictures here.
Amen.
Pulled the plug on a live banking AS/400. To make matter worse I then had to sit there during the veeery long IPL - what is it with AS/400s and long IPL times?
If you look at the pics the design similarities are quite obvious.
Take Andy Robinson's doorslammer Stude for example.
Symbolic links (or shortcuts for Windows users) allow you to put pointers to a single file in other directories.
Linux is trying to "do a Windows" and be all things to all men as quickly as possible.
FreeBSD is more like a working pick-up truck. They don't have a wide range of paint colors and picking up chicks with them can be hard - but they do what they are built for, and they do it very well.
BSD kernels are unencumbered by System V legacy code, copyright and control - which is basically why Apple's OS X isn't a licensee of SCO's UNIX copyright.
I love the fact that when mentioning free UNIX only Linux gets a mention. This is despite the fact that a huge swathe of ISPs run some sort of *BSD for hosting, security, firewalls, etc.
Not only are they free in both senses of the word but there is no viral GNU license which obliges derivative works from adhering to the license.
If GNU is challenge and Linux destroyed then it will only delay the pervasiveness of "free" Unicies - IBM et al will simply adopt a BSD kernel. BSD kernels were created for the specific tasks of removing the old AT&T/System V licensed code!
[1] Configure your reverse mappings for your Internet-facing machines properly. That way we can start checking on reverse lookups which would stop Joe Lusers Windows box on DSL being turned into an SMTP engine.
I know that people can trivially configure their own DNS servers and spoof the forward and reverse mappings, but at least there needs to be an administrative contact on the SOA record and on the WHOIS information; which is something
[2] Get rid of the un-needed use of HTML emails. There is no need for half of the formatting and dross in emails. ASCII does just fine, and provide a link to a website if you need to woo people with eye candy.
[3] Undo some of the supposed "intelligent" behviour of email clients. They should display text first, and do everything else (play sounds, render HTML) as a user-invoked extra
[4] Make it a "must manually do" option to allow SMTP servers to allow relaying from anything other than their internal interface and IP range. Too many products come too open out of the box
[5] Use the TXT record or something similar for SMTP servers to list which domains they serve. That way receiving servers performing a forward/reverse lookup for verification will also be able to see if the domain in the email has been spoofed.
NASA: We spent $1million developing a pen to write is space, in zero gravity, upsidedown and on a variety of surfaces. What do you guys use and who much did it cost?
Russia: A pencil.
I used to work for Natest in this area. They have been taken over by RBoS so God only knows what they are running now. Whatever it was, when they migrated to the RBoS backend they took steps about 15 years backwards.
In a personal capacity and in no way reflecting my employers - I would like to voice my utter disgust with both the moral and technical ignorance you have shown by placing wildcards in the .com and .net TLD domain space.
Despite toying with and potentially breaking (MTAs, NXDOMAIN no longer work, port 25 open on your "sitefinder" box, direct to A record mail delivery not working properly, breaking negative caching on .com and .net domains, etc, etc) *the* most important service on the internet, you have also abused your power.
What you have done is akin to putting advertisements on road signs that mislead people who don't know /exactly/ where they want to go to get lost.
The Internet is NOT the World Wide Web; what you have done is NOT merely provide a search facility for people - you have fundamentally broken aspects of the DNS system which were working quite well and there for a good reason.
I would suggest to your Board that having abused your trust, you no longer deem yourself worthy of trust in the SSL certificate arena. I would wager that that business is worth more than a few mispelt URL stats.
In a personal capacity and in no way reflecting my employers - I would like to voice my utter disgust with both the moral and technical ignorance you have shown by placing wildcards in the .com and .net TLD domain space.
Despite toying with and potentially breaking (MTAs, NXDOMAIN no longer work, port 25 open on your "sitefinder" box, direct to A record mail delivery not working properly, breaking negative caching on .com and .net domains, etc, etc) *the* most important service on the internet, you have also abused your power.
What you have done is akin to putting advertisements on road signs that mislead people who don't know /exactly/ where they want to go to get lost.
The Internet is NOT the World Wide Web; what you have done is NOT merely provide a search facility for people - you have fundamentally broken aspects of the DNS system which were working quite well and there for a good reason.
I would suggest to your Board that having abused your trust, you no longer deem yourself worthy of trust in the SSL certificate arena. I would wager that that business is worth more than a few mispelt URL stats.
Confirmed here. I get a 104 error from my squid proxies. hehehehehe ;)
15mins. I think they also say that in their documents/whitepapers
"Sex.com case finally reaches climax" would have been a much better title for this story.
I second that motion - this was the first and best hacking/computer book (and one of the best books along with Neuromancer) that I have ever read.
It's just occured to me what a wonderful Virus infection vector Windows Update would make. All-out access to install stuff on the most prevailent OS in the world today. Now, where did I put that copy of VCL..?
I rest my case ;)
Once again postings like this prove that Slashdot is full of CS graduates and home "experts" who wouldn't know true corporate computing environments if they slapped them in the face. Of course people use AIX.
So how long until I they start moving onto the other untainted languages? perl.NET? assembler.NET? english.NET? This is really going too far, really.
I wonder what the implications would be if I owned, say, whitewatershafting.com and was forced to move that to whitewatershafting.prn; but I then bought sweetnessandlight.com and provided an instant redirect the the .prn site? The site "lives" in the .prn TLD.....