Agreed. The densely woven physical layer carries timing information in the analog domains, with extensive cross-connections, that are very difficult to simulate in a classical Turing machine or binary network. The switches between complex analog mixing and routing, and the centralization or near digitization of the signals to provide reliable low bandwidth communications to more central or more remote processing, is material all network engineers could learn quite a lot from.
The article left out a rule that is bad for CIO's trying to protect their fiefdoms from competing departments, but great for the staff and makes the company more effective overall. Communicate with your employees about your plans and policies. There are few things as frustrating as spending a month satisfying a technical requirement, documenting it, integrating it into your environment, getting to the release date and finding out that the whole project it was built for was planned to be outsourced and the plan has been in the pipeline for six months. The CIO went to the meeting, argued the case without informing you as the technical expert of the information, and didn't ask for your opinion on the suggested alternatives.
That has happened to me several times in my professional career, and it's predictable when I'll be called in from my primary tasks to clean up the integration mess for something I was not permitted to address earlier.
Oh, my. Replacing _Exchange_, and most especially its calendar functions, to interoperate well with MS Outlook, is like dancing with bears. It's amazingly that they'll dance at all with you, and you have to be very careful not to get stepped on or clawed.
Active Directory's individual functions can generally be better handled in a more consistent, configurable, and manageable way by providing its individual services and not managing them through a GUI that doesn't even know how to configure what its own standards are designed to allow.
I think it's a cluttered mess, as do some others. Those others, me, and everybody else, are going to have to live with it. I think that is enough to justify a 'we' there: do you really disagree?
Part of why it's a mess is that the option bar pulldown function is overly large and tends to go to lengthy, recent URL's instead of site URL's. This debris can clutter a screen quite a lot. The ordering and size of the bar also makes its use awkward when sites have complex URL's identifying specific and potentially hazardous to repeat operations. It's also cluttered by the 'favicon.ico' URL at many sites, which is not helpful at all. Even for simple sites like webcomics, previous day's URL's seem to be frequently listed ahead of the main site URL.
I think you are mistaken about the API necessities. Contemporary versions of Samba, Kerberos, and LDAP work quite nicely with Active Directory integration. Additional API's might be desirable to replace Active Directory _servers_, and the Samba team is having understandable difficulty getting all the details right for Samba 4.0. But keeping Microsoft's alleged but undocumented and unrevealed patents away from your investors could easily be worth signing such an agreement to a company that just wants to sell their products, and is willing to leave the ethical andn legal burdens of protecting Linux to the rest of us.
Crossover Office is handy, but I've never found it to be more than 95% effective. Perhaps this API cooperation with Microsoft is more centered on MS Office? That's a vastly more complex, ill-documented, and difficult to integrate API than network integration itself.
NT was _not_ a ground-up rewrite of DOS or Windows 3.x. The interface was preserved from Windows, but much of the kernel was a wholesale theft of VMS from DEC, when Microsoft hired David Cutler and his crew away from DEC. They had to backport madly to get much of the VMS kernel into 32-bit rather than the 64-bit of DEC's Alpha chips, but the lawsuits were massive and justified. It's also why NT ran so well on Alphas (which few people used, as Intel was stealing pieces of _that_ technology for the Pentium).
Apple did something similar, but legally, by porting FreeBSD tools and structure to their new MacOS. When you've become too big, it's sometimes a lot easier to adopt a technology wholesale from outside the company than try to develop it in-house.
You don't spar in training? I should think sparring counts.
Blocking incoming punches, and even a lot of stance and foot movement, are tactical decisions. They occur very quickly with proper training, and leave your mind free to work on strategic decisions.
My oint is that a lot of decisions are actually very quickly made.
And I, too, make decisions without conscious evaluation. Which hand do I block that incoming punch with? After 30 years of martial arts, I hope you're reacting _long_ before you decide.
Would you rather have a centralized, Soviet Union style setup? It's already bad enough when the NSA can and does instlal taps on AT&T's central backbone without notice or warrant: centralizing companies like Bell into a monopoly is begging to have bad policies and bad decisions cast in bureaucratic stone and resistant to evolutionary forcs.
You may think you're kidding, but I've recently had to explain to some very nice people that no, I cannot force their machine to be 'Firstname.Lastname.example.com' without causing lots of DNS problems, and they'd just have to use a '-'.
I understand how DNS is supposed to work, and this is going to be a major pain to deal with. It's going to force undesired upgrades of software worldwide, especially proxies and dedicated proxy hardware. It's also going to cause significant burdens on legitimate filtering software such as spam blacklists, and even more of a market for the domain squatters who pay a lot of ICANN's bills.
If there were a way to force sites to use '.xxx' for porn sites, or '.pay' for ecommerce sites that handle money, I'd say it was worth it. But this just means more confusion of an already mis-regulated and deliberately abused structure.
It is disgusting. But besides being 10 years ago, some other factors may have been involved. Who is this fellow in Jamaica she was married to? Did he have some other history that didn't come up n her Congressional testimony? I'm not saying the Customs people weren't completely out of line in how they treated a pregnant woman. There are apparently laxatives that are safe for pregnant women, such as Metamucil, but it would seem well worth consulting a competent physician in such a case.
If this woman's testimony is true, I hope she sued these agents into the ground. And I certainly hope her son was unharmed. Human fetuses can endure a lot of abuse, because accidents and illness happen even to the most cautious pregnant women. Most of us seem to have survived our mothers' adventures. Whether we can withstand all the stories they tell about it is another matter.
Oh? What about monitoring of political opponents? Tax fraud? Cell phone records and email of individuals for whom there just isn't enough evidence for a legitimate warrant? Cute college students that the border guard can plan to be at the same bar or party with? Stock tips from business travelers closing international deals?
The potential for abuse is endless. Please don't limit your completely justified paranoia. Since there's no court order, and no clear judicial jurisdiction for this data, it will most certainly be abused, and abused with little recourse to prove who had it.
The feds also know about root kits and stealing site keys to perform a man-in-the-middle attack, or even just using their own keys purchased from Verisign as 'authorized', even though there is no chain of trust between you personally and the key owner.
SSL is helpful against casual or unsophisticated monitoringl. But once someone can steal the server's keys and perform man-in-the-middle monitoring, it's pretty useless.
I'd give quite a lot to see the guard who tries to search Richard Stallman. The man is famous for not bathing, and you could probably hide an OLPC laptop in that beard.
Yes, you can. But rewriting an installer to avoid having to manually accept the EULA is itself a violation of the EULA: including it in a distribution is _definitely_ a violation of the EULA.
There are published RPM's, such as those at livna.org, for RPM system users. And from an earlier comment, I'm looking at the new alternative repository for OpenSuSE at http://en.opensuse.org/NVIDIA. The craziness and foolishness needed to integrate it are related to the inability to include its OpenGL libraries in the basic OS installation, and the RPM simply runs the Nvidia installer automatically. Unless they've gotten very clever, upgrades of the Nvidia or RPM provided OpenGL libraries will completely ruin the setup and disable X windows.
You're using YaST, right? Unless it's changed from SuSE, that one click is dead wrong. It ignores the RPM management, and installs an out-of-date NVidia tarball from NVidia's website, with no way in the YaST system to select a newer version of the NVidia drivers, in order to force you to go though the manual agreement to the EULA. As soon as the Xorg package that includes the OpenGL libraries is installed, it overwrites the NVidia included OpenGL libraries because the RPM system knows nothing about those libraries, because they're only one component of a much larger package which NVidia's installers do _not_ replace.
I ran into this with an Italian professional colleague who likes SuSE last year. It was quite nasty to keep his system alive, partly because YaST is so unable to see or keep the modifications made directly in configurations, modifications that it has no way itself to create. The results are deadly.
And NVidia i a real burden this way. Their driver installers for Linux move aside your existing your OpenGL libraries, without notifying the package manager. This means that your next software update or rebuild will ruin your NVidia drivers, because the package manager does not know about these semi-manually installed files.
It wouldn't be hard to fix by incorporating the NVidia software into a managed software package for automatic installation, but NVidia clearly wants people to click on the end-user license agreement when they install the drivers. This makes automatic deployment of such drivers a real problem for the Linux world. Nvidia has chosen not to cooperate with this much needed feature of Linux operating systems, and the resulting instability is quite predictable.
It's the business pricing model. Rather than merely having one price and one set of features, and accepting the business that this balance will provide, this allows NVidia and companies like them to simply scale back the features to gain customers with less money to spend. And doing it as a driver, rather than as a hardware difference, tremendously eases manufacturing requirements. We've seen this for decades in all sorts of products, such as a lot of DEC computers from decades ago that required only a few minutes with a soldering iron to perform some very serious hardware upgrades.
Multiple, parallel versions splits development efforts. It also splits QA efforts, and makes support for both versions problematic. It's usually much safer to have a primary release and branches to test new features, rather than being forced to rewrite from scratch.
I give good credit to Sun for doing this: it's one of the missing Java support components for the open source world, and should allow inclusion of actual Java in distributions such as Fedora and Mandriva, saving us serious pain maintaining multiple, slightly conflicting versions in different locations for different packages. And it should make OpenOffice installations much smaller and more efficient.
A lot of the spam from China is from US spammers: throwaway domains are very useful, to duck blacklists. It's really an international problem, and tends to fester due to companies like this, which ICANN is typically unable or unwilling to disconnect.
Some of do get touchy when a new programmer says 'I can code that in 20 lines! 18 lines! 6 lines!' And then we look at what they wrote, and there is no error checking or overflow testing or error reporting, and we have to clean up the resulting mess when it shows up in the code review.
The credit for the first paper to explain it, or to give the most feasible explanations cited by the next crop of graduate students, isn't going to be available for long. Discovering genuinely new classes of celestial objects depends very much on timing.
Slashdot Mirror
Agreed. The densely woven physical layer carries timing information in the analog domains, with extensive cross-connections, that are very difficult to simulate in a classical Turing machine or binary network. The switches between complex analog mixing and routing, and the centralization or near digitization of the signals to provide reliable low bandwidth communications to more central or more remote processing, is material all network engineers could learn quite a lot from.
The article left out a rule that is bad for CIO's trying to protect their fiefdoms from competing departments, but great for the staff and makes the company more effective overall. Communicate with your employees about your plans and policies. There are few things as frustrating as spending a month satisfying a technical requirement, documenting it, integrating it into your environment, getting to the release date and finding out that the whole project it was built for was planned to be outsourced and the plan has been in the pipeline for six months. The CIO went to the meeting, argued the case without informing you as the technical expert of the information, and didn't ask for your opinion on the suggested alternatives.
That has happened to me several times in my professional career, and it's predictable when I'll be called in from my primary tasks to clean up the integration mess for something I was not permitted to address earlier.
Oh, my. Replacing _Exchange_, and most especially its calendar functions, to interoperate well with MS Outlook, is like dancing with bears. It's amazingly that they'll dance at all with you, and you have to be very careful not to get stepped on or clawed.
Active Directory's individual functions can generally be better handled in a more consistent, configurable, and manageable way by providing its individual services and not managing them through a GUI that doesn't even know how to configure what its own standards are designed to allow.
I think it's a cluttered mess, as do some others. Those others, me, and everybody else, are going to have to live with it. I think that is enough to justify a 'we' there: do you really disagree?
Part of why it's a mess is that the option bar pulldown function is overly large and tends to go to lengthy, recent URL's instead of site URL's. This debris can clutter a screen quite a lot. The ordering and size of the bar also makes its use awkward when sites have complex URL's identifying specific and potentially hazardous to repeat operations. It's also cluttered by the 'favicon.ico' URL at many sites, which is not helpful at all. Even for simple sites like webcomics, previous day's URL's seem to be frequently listed ahead of the main site URL.
So yes, it's cluttered.
The new option bar is a cluttered mess we're going to have to live with, much like the Vista interface.
I think you are mistaken about the API necessities. Contemporary versions of Samba, Kerberos, and LDAP work quite nicely with Active Directory integration. Additional API's might be desirable to replace Active Directory _servers_, and the Samba team is having understandable difficulty getting all the details right for Samba 4.0. But keeping Microsoft's alleged but undocumented and unrevealed patents away from your investors could easily be worth signing such an agreement to a company that just wants to sell their products, and is willing to leave the ethical andn legal burdens of protecting Linux to the rest of us.
Crossover Office is handy, but I've never found it to be more than 95% effective. Perhaps this API cooperation with Microsoft is more centered on MS Office? That's a vastly more complex, ill-documented, and difficult to integrate API than network integration itself.
NT was _not_ a ground-up rewrite of DOS or Windows 3.x. The interface was preserved from Windows, but much of the kernel was a wholesale theft of VMS from DEC, when Microsoft hired David Cutler and his crew away from DEC. They had to backport madly to get much of the VMS kernel into 32-bit rather than the 64-bit of DEC's Alpha chips, but the lawsuits were massive and justified. It's also why NT ran so well on Alphas (which few people used, as Intel was stealing pieces of _that_ technology for the Pentium).
Apple did something similar, but legally, by porting FreeBSD tools and structure to their new MacOS. When you've become too big, it's sometimes a lot easier to adopt a technology wholesale from outside the company than try to develop it in-house.
You don't spar in training? I should think sparring counts.
Blocking incoming punches, and even a lot of stance and foot movement, are tactical decisions. They occur very quickly with proper training, and leave your mind free to work on strategic decisions.
My oint is that a lot of decisions are actually very quickly made.
And I, too, make decisions without conscious evaluation. Which hand do I block that incoming punch with? After 30 years of martial arts, I hope you're reacting _long_ before you decide.
Would you rather have a centralized, Soviet Union style setup? It's already bad enough when the NSA can and does instlal taps on AT&T's central backbone without notice or warrant: centralizing companies like Bell into a monopoly is begging to have bad policies and bad decisions cast in bureaucratic stone and resistant to evolutionary forcs.
You may think you're kidding, but I've recently had to explain to some very nice people that no, I cannot force their machine to be 'Firstname.Lastname.example.com' without causing lots of DNS problems, and they'd just have to use a '-'.
I understand how DNS is supposed to work, and this is going to be a major pain to deal with. It's going to force undesired upgrades of software worldwide, especially proxies and dedicated proxy hardware. It's also going to cause significant burdens on legitimate filtering software such as spam blacklists, and even more of a market for the domain squatters who pay a lot of ICANN's bills.
If there were a way to force sites to use '.xxx' for porn sites, or '.pay' for ecommerce sites that handle money, I'd say it was worth it. But this just means more confusion of an already mis-regulated and deliberately abused structure.
It is disgusting. But besides being 10 years ago, some other factors may have been involved. Who is this fellow in Jamaica she was married to? Did he have some other history that didn't come up n her Congressional testimony? I'm not saying the Customs people weren't completely out of line in how they treated a pregnant woman. There are apparently laxatives that are safe for pregnant women, such as Metamucil, but it would seem well worth consulting a competent physician in such a case.
If this woman's testimony is true, I hope she sued these agents into the ground. And I certainly hope her son was unharmed. Human fetuses can endure a lot of abuse, because accidents and illness happen even to the most cautious pregnant women. Most of us seem to have survived our mothers' adventures. Whether we can withstand all the stories they tell about it is another matter.
It's summer. They've migrated south.
Oh? What about monitoring of political opponents? Tax fraud? Cell phone records and email of individuals for whom there just isn't enough evidence for a legitimate warrant? Cute college students that the border guard can plan to be at the same bar or party with? Stock tips from business travelers closing international deals?
The potential for abuse is endless. Please don't limit your completely justified paranoia. Since there's no court order, and no clear judicial jurisdiction for this data, it will most certainly be abused, and abused with little recourse to prove who had it.
The feds also know about root kits and stealing site keys to perform a man-in-the-middle attack, or even just using their own keys purchased from Verisign as 'authorized', even though there is no chain of trust between you personally and the key owner. SSL is helpful against casual or unsophisticated monitoringl. But once someone can steal the server's keys and perform man-in-the-middle monitoring, it's pretty useless.
I'd give quite a lot to see the guard who tries to search Richard Stallman. The man is famous for not bathing, and you could probably hide an OLPC laptop in that beard.
Yes, you can. But rewriting an installer to avoid having to manually accept the EULA is itself a violation of the EULA: including it in a distribution is _definitely_ a violation of the EULA.
There are published RPM's, such as those at livna.org, for RPM system users. And from an earlier comment, I'm looking at the new alternative repository for OpenSuSE at http://en.opensuse.org/NVIDIA. The craziness and foolishness needed to integrate it are related to the inability to include its OpenGL libraries in the basic OS installation, and the RPM simply runs the Nvidia installer automatically. Unless they've gotten very clever, upgrades of the Nvidia or RPM provided OpenGL libraries will completely ruin the setup and disable X windows.
You're using YaST, right? Unless it's changed from SuSE, that one click is dead wrong. It ignores the RPM management, and installs an out-of-date NVidia tarball from NVidia's website, with no way in the YaST system to select a newer version of the NVidia drivers, in order to force you to go though the manual agreement to the EULA. As soon as the Xorg package that includes the OpenGL libraries is installed, it overwrites the NVidia included OpenGL libraries because the RPM system knows nothing about those libraries, because they're only one component of a much larger package which NVidia's installers do _not_ replace.
I ran into this with an Italian professional colleague who likes SuSE last year. It was quite nasty to keep his system alive, partly because YaST is so unable to see or keep the modifications made directly in configurations, modifications that it has no way itself to create. The results are deadly.
And NVidia i a real burden this way. Their driver installers for Linux move aside your existing your OpenGL libraries, without notifying the package manager. This means that your next software update or rebuild will ruin your NVidia drivers, because the package manager does not know about these semi-manually installed files.
It wouldn't be hard to fix by incorporating the NVidia software into a managed software package for automatic installation, but NVidia clearly wants people to click on the end-user license agreement when they install the drivers. This makes automatic deployment of such drivers a real problem for the Linux world. Nvidia has chosen not to cooperate with this much needed feature of Linux operating systems, and the resulting instability is quite predictable.
It's the business pricing model. Rather than merely having one price and one set of features, and accepting the business that this balance will provide, this allows NVidia and companies like them to simply scale back the features to gain customers with less money to spend. And doing it as a driver, rather than as a hardware difference, tremendously eases manufacturing requirements. We've seen this for decades in all sorts of products, such as a lot of DEC computers from decades ago that required only a few minutes with a soldering iron to perform some very serious hardware upgrades.
Multiple, parallel versions splits development efforts. It also splits QA efforts, and makes support for both versions problematic. It's usually much safer to have a primary release and branches to test new features, rather than being forced to rewrite from scratch. I give good credit to Sun for doing this: it's one of the missing Java support components for the open source world, and should allow inclusion of actual Java in distributions such as Fedora and Mandriva, saving us serious pain maintaining multiple, slightly conflicting versions in different locations for different packages. And it should make OpenOffice installations much smaller and more efficient.
A lot of the spam from China is from US spammers: throwaway domains are very useful, to duck blacklists. It's really an international problem, and tends to fester due to companies like this, which ICANN is typically unable or unwilling to disconnect.
Some of do get touchy when a new programmer says 'I can code that in 20 lines! 18 lines! 6 lines!' And then we look at what they wrote, and there is no error checking or overflow testing or error reporting, and we have to clean up the resulting mess when it shows up in the code review.
The credit for the first paper to explain it, or to give the most feasible explanations cited by the next crop of graduate students, isn't going to be available for long. Discovering genuinely new classes of celestial objects depends very much on timing.