Bluetooth has never been in the MS best interest. It is in the interest of Sony, JVC, and other entertainment and home equipment vendors. They (for example look for the interviews with Sony's boss) will eat MS alive the moment they can and they hate it. They will have most of the profit margin. Microsoft will not earn from it. Even if it could they will not let it.
It is a very popular misconseption that milk is good for you. This is just bulshit and dairy farmers proapaganda. Go and ask a biochemist how hard it is to digest caseine for a human that is older then 16-18 months.
Have you ever ran cdd2wav with a reasonable quantity of -v flags? Even now almost all tracks have the restricted copy flag set. The problem is that allmost all CD drives ignore it and do a digital read anyway. So unless someone goes out there and changes all CDR drives or uses a format that no CDR things will be the same as now.
It is perfectly valid and legal. You are allowed to charge for distribuition. Check the GPL. You must provide the source free of charge and accessible though.
You are close but not as close as you could be. To be more exact there will be no Internet as we know it. All ATM and SONET equipment uses external GPS based synchronization sources. Which means that a considerable fraction of high speed lines (above 45M) will die miserably. ATM dies for sure. Sonet - it depends;-)
The main problem in the DeCSS case is that EFF, 2600 are all daft. Obviously violating the law has never been a wise idea. Especially if there is a way around it.
In detail:
It is very easy for the RIAA and MPAAA to fight now. Reason is that was is actually published is the decryption device. Which is illegal according to the current laws.
It would have been much harder for the MPAA to remove all articles that describe in exruciating detail the encryption scheme (not the decryption). And from there on any clueful indvidual can scribble the decryption in half a day using a standard RSA toolkit or something as daft as the java.security and java.encryption. And at the same time there is no law violated. There is no "circumvention" device described. So legally (IANAL) this should be a much harder target.
Portable platforms have much wider applications than handhelds. The same hardware is quite often used in ATMs, ticket sellers, etc. And there the stability and portability of an enterprise class Unix OS makes sense.
In other words when was the last time you have seen a bluescreened WinCE ATM terminal. I saw one this morning...
And NetBSD on hardware originally designed for WinCE is already giving linux a run for its money more specifically in industrial applications.
Complete and utter bulshit. You have missed the most important point: IP Agreement is approved by the board.
The IP Agreement and actually most of the contractual terms for the fist employees in a startup are determined by the VCs and by the board. They are part of the conditions upon which the copany has recieved funding. Noone in the company has the right to change them. If the company you are applying for is a startup you take what you get or leave. C'est la vie. There is no negotiation whatsoever.
And it is least likely to change until the company has receieved additional investment or even gone public.
The same complaint goes for m68K (which has maybe a handfull of mainstream kernels that even compile) and quite often for (u)sparc. There are lots of conspiracy theories but I think that the answer is very simple: endian-ness. Let's face it most linux development is done on 32 bit little endian. And quite a lot of people do not recheck their stuff for endian issues.
Hopefully now, with IBM's and other "big endian guns" involvment the issues will subside by themselves.
Yes. And this time it is right and proper.
on
Suing Over... Fans?
·
· Score: 3
I understand the luddite primal instincts of some slashdot users but they are not right in this case. Designing a silent and highly efficient fan requires some serious aerodinamics, sound propagation and thermal conduction research. It is IMHO harder than designing a memory bus (no fionger pointing at favourite targerts). And "one click" bogousities should not even be compared to the case.
So IMHO a patent on a good fan design has merit.
If you still do not believe me take a golden orb and compare it some cheepo piece of junk. Just look at the blade shapes...
Re:read more about it at
on
Spidergoats
·
· Score: 2
For once the XXX.cx and FP to be funny. Congrats. The last time it happened it was more than a year ago.
So this is why there are so many variations of Unix and Linux--species splitting!
Infected by which STD?
I would outright disagree with most statements
on
David Korn Tells All
·
· Score: 2
Ksh syntax more readable than perl... Yeah right. I have read enough IBM install scripts or semi-insane scripts from commercial solaris software to object. Well written ksh is more readable than horrible perl, but it does not even get closed to proper perl.
Perl developers not using unix system toolkits. Well... there is a reason for it. Specifically related to temporary files, the system call versus fork/exec and so on. Most ksh programs I have seen (including parts of commercial software) do not take these subtleties into account. As a result they are full with root holes. Perl programmers have learned to take them into account the hard way
Ksh faster than perl. Seeing is believing. Unless we are talking about arithmetics where perl traditionally does not cut the mustard...
Ksh more extensible than perl... Well... Once again seing is believing... So far just looking at CPAN the answer is "bulshit"
They are not laptops. The laptops are only for austronauts personal use and sometimes for control of non-critical experiments
The guydance and control computers are actually almost as simple as apollo 11. They were either 804(X=8,9)or 805(X=0,1). These were the highest ones certified for NASA use at the time the shuttle was designed. There is an overall of 5 of these extremely simple systems operating commands to the valves and the engine ignition system on a voting principle. The majority gets to execute the command. The idea is that there cannot be a simultaneous triple failure. This is actually described in detail in one of the articles on the shuttle ran by Scientific American in the eighties.
No it is not. The dynamic key infrastructure and the stack itself are not 100% stable yet. The reason is that due to various vendor intrigues the highly efficient mechanism for dynamic key management initially implemented in early 2.x OpenBSDs (firefly) was replaced by the current one. The PKI for the current one is horrible and noone besides OpenBSD and a handfull of commercial products implements the entire thing. For example linux does not.
Of course, for a house network you can use static keys. But if you are down to static keys something more simple like cipe or windows PPTP services will do the job anyway. Also in the former (cipe) case you can use blowfish which means much lower overhead.
If the government is sucking up the "loss" in the sales,
where is that money coming from, taxxed people?
You do have a point and this is quite likely. At the same time
Who said that there will be any loss. An IDT winchip or K6-2+ based board with the worst type "fry your brain" 14in CRT with 16M flash, 64M memory and a linmodem will cost exactly there. Bulk prices of course. And even if not picked up by the masses it will still make a good terminal for schools if the linmodem is replaced by LAN.
First, I agree power management in a server makes sense. But not because of california legislations but because the most important server parameter is MTBF. Power management can increase the MTBF and efficiency of the cooling subsystem. This in turn increases MTBF of disks and the entire system. One degree away from the optimum operating temperature can decrease a disk's life by an year or more.
Also, you do not spin down disks on servers for both business and reliability reasons. The business reason is server latency. The reliability reason is that most server HDUs hate to be spun down and their MTBF decreases (which is again business in a sense). Also, the biggest power eaters in most modern servers are the cooling systems and the CPUs. Not the disks. Disks hardly go above 2-10W nowdays while a PIII with the fans can go up to a 100W. Alpha goes even beyond that. Also, spinning up and down disks to 7200-10000 RPM can actually generate more heat and consume more power than keeping them running.
Some bits of info by platform:
x86APM does not work at all or has only limited functionality with SMP systems and any newer boards. Which means that only an ACPI supporting system will have working power management. ACPI is a new addition in linux and BSD. Neither ACPI nor APM exist in solaris. NT is not really using it for power management in servers to the extent of my knowledge. So only a very upto date installation can actually use power management. But it will be only the CPUs. I have yet to see an x86 server where the fan is actively controlled by chassis temperature. Usually servers have them hardwired at MAX. Which means the entire exercise meaningless as you are not actually improving your MTBF that much.
Alpha Only recently someone (forgot who) modified the original DGUX PAL code to do power management on the newer CPUs. This is hardly used and unusable in all AlphaBios installs. Which is a pity as the alphas have always had the fan speed controlled by CPU temperature.
MIPS - never heard of power management. Server lines of PPC derived (u)Sparc - same.
So overall the situation is that for one of the most popular platforms the power magement is hardly used due to the fact that the OS support just came in. For the second most popular platform (Sun) the power management was never there. The others are pretty much there as well.
And to conclude: I do not feel comfortable installing linux 2.4.0 or the ACPI support for BSD on real production machines yet.
The ratio for average server performance is more than 1:2 not 1:12. So you logic is flawed. Transmeta is not that slow. Tried it. It is about as fast as PIII at the same frequency on integer math and this is what matters for a server. Also, for real server operations quite often the bottleneck is the IO, not the CPU anyway.
The reason why people use PIII and not transmeta or AMD (which also has very good power saving under UNIXes) is the fact that there are no server boards available. For example try to find a mainboard for AMD with console redirection and enjoy the nightmare. At the same time all high end Intel and ServerWorks boards support it.
OK, How is it an outlook killer if it isn't competing on the same platform?
The important bit is the server platform. It is very hard to make cretinous Minesweeper Consulatants and Solitaire Experts that dwell around the coridors of large corps and claim to be from the "Incompetent in Technology" department to use anything but MS Exchange. So anything that can deal with their abominative productions is more than welcome.
The sponsors of the specification "may" have various patents
Welcome to the world of telecoms. And that is the exact reason I will buy myself a visorphone. Because it is built from the PDA to the phone so that it is not encumbered by the standard nasonal telecom appreciation like all the GSM phone stuff currently in circulation. And in btw, some patents there are much sillier than the patents in software.
Especially about the gentle giant. 747 is a subject to additional USAF and NATO requirements and all 747s currently in operation are subject to draft in case of military emergency. Which actually happened during the Gulf War. The airlines were extremely pissed off but there was nothing they could do.
It is not a gentle giant. It is a military transport aircraft. It is redundant by the military, not the civil aviation spec (check the engine redundancy and power excess parameters for example). And it was already used in several projects as a carrier for Star Wars weapons (mostly missiles and stuff). So nothing new. Nothing amazing.
Slashdot Mirror
Well... At least this will solve the Middle East Conflict once and for all. No more whose is the holy city question to fight about.
Bluetooth has never been in the MS best interest. It is in the interest of Sony, JVC, and other entertainment and home equipment vendors. They (for example look for the interviews with Sony's boss) will eat MS alive the moment they can and they hate it. They will have most of the profit margin. Microsoft will not earn from it. Even if it could they will not let it.
It is a very popular misconseption that milk is good for you. This is just bulshit and dairy farmers proapaganda. Go and ask a biochemist how hard it is to digest caseine for a human that is older then 16-18 months.
Bollocks.
Have you ever ran cdd2wav with a reasonable quantity of -v flags? Even now almost all tracks have the restricted copy flag set. The problem is that allmost all CD drives ignore it and do a digital read anyway. So unless someone goes out there and changes all CDR drives or uses a format that no CDR things will be the same as now.
It is perfectly valid and legal. You are allowed to charge for distribuition. Check the GPL. You must provide the source free of charge and accessible though.
So I see no problem here.
You are close but not as close as you could be. To be more exact there will be no Internet as we know it. All ATM and SONET equipment uses external GPS based synchronization sources. Which means that a considerable fraction of high speed lines (above 45M) will die miserably. ATM dies for sure. Sonet - it depends ;-)
The main problem in the DeCSS case is that EFF, 2600 are all daft. Obviously violating the law has never been a wise idea. Especially if there is a way around it. In detail: It is very easy for the RIAA and MPAAA to fight now. Reason is that was is actually published is the decryption device. Which is illegal according to the current laws. It would have been much harder for the MPAA to remove all articles that describe in exruciating detail the encryption scheme (not the decryption). And from there on any clueful indvidual can scribble the decryption in half a day using a standard RSA toolkit or something as daft as the java.security and java.encryption. And at the same time there is no law violated. There is no "circumvention" device described. So legally (IANAL) this should be a much harder target.
Portable platforms have much wider applications than handhelds. The same hardware is quite often used in ATMs, ticket sellers, etc. And there the stability and portability of an enterprise class Unix OS makes sense.
In other words when was the last time you have seen a bluescreened WinCE ATM terminal. I saw one this morning...
And NetBSD on hardware originally designed for WinCE is already giving linux a run for its money more specifically in industrial applications.
Complete and utter bulshit. You have missed the most important point: IP Agreement is approved by the board.
The IP Agreement and actually most of the contractual terms for the fist employees in a startup are determined by the VCs and by the board. They are part of the conditions upon which the copany has recieved funding. Noone in the company has the right to change them. If the company you are applying for is a startup you take what you get or leave. C'est la vie. There is no negotiation whatsoever.
And it is least likely to change until the company has receieved additional investment or even gone public.
The same complaint goes for m68K (which has maybe a handfull of mainstream kernels that even compile) and quite often for (u)sparc. There are lots of conspiracy theories but I think that the answer is very simple: endian-ness. Let's face it most linux development is done on 32 bit little endian. And quite a lot of people do not recheck their stuff for endian issues.
Hopefully now, with IBM's and other "big endian guns" involvment the issues will subside by themselves.
I understand the luddite primal instincts of some slashdot users but they are not right in this case. Designing a silent and highly efficient fan requires some serious aerodinamics, sound propagation and thermal conduction research. It is IMHO harder than designing a memory bus (no fionger pointing at favourite targerts). And "one click" bogousities should not even be compared to the case.
So IMHO a patent on a good fan design has merit.
If you still do not believe me take a golden orb and compare it some cheepo piece of junk. Just look at the blade shapes...
For once the XXX.cx and FP to be funny. Congrats. The last time it happened it was more than a year ago.
Infected by which STD?
Ksh syntax more readable than perl... Yeah right. I have read enough IBM install scripts or semi-insane scripts from commercial solaris software to object. Well written ksh is more readable than horrible perl, but it does not even get closed to proper perl.
Perl developers not using unix system toolkits. Well... there is a reason for it. Specifically related to temporary files, the system call versus fork/exec and so on. Most ksh programs I have seen (including parts of commercial software) do not take these subtleties into account. As a result they are full with root holes. Perl programmers have learned to take them into account the hard way
Ksh faster than perl. Seeing is believing. Unless we are talking about arithmetics where perl traditionally does not cut the mustard...
Ksh more extensible than perl... Well... Once again seing is believing... So far just looking at CPAN the answer is "bulshit"
That is called: some stupid moron compiled libreadline statically. Not amazing...
They are not laptops. The laptops are only for austronauts personal use and sometimes for control of non-critical experiments
The guydance and control computers are actually almost as simple as apollo 11. They were either 804(X=8,9)or 805(X=0,1). These were the highest ones certified for NASA use at the time the shuttle was designed. There is an overall of 5 of these extremely simple systems operating commands to the valves and the engine ignition system on a voting principle. The majority gets to execute the command. The idea is that there cannot be a simultaneous triple failure. This is actually described in detail in one of the articles on the shuttle ran by Scientific American in the eighties.
No it is not. The dynamic key infrastructure and the stack itself are not 100% stable yet. The reason is that due to various vendor intrigues the highly efficient mechanism for dynamic key management initially implemented in early 2.x OpenBSDs (firefly) was replaced by the current one. The PKI for the current one is horrible and noone besides OpenBSD and a handfull of commercial products implements the entire thing. For example linux does not.
Of course, for a house network you can use static keys. But if you are down to static keys something more simple like cipe or windows PPTP services will do the job anyway. Also in the former (cipe) case you can use blowfish which means much lower overhead.
You do have a point and this is quite likely. At the same time
Who said that there will be any loss. An IDT winchip or K6-2+ based board with the worst type "fry your brain" 14in CRT with 16M flash, 64M memory and a linmodem will cost exactly there. Bulk prices of course. And even if not picked up by the masses it will still make a good terminal for schools if the linmodem is replaced by LAN.
First, I agree power management in a server makes sense. But not because of california legislations but because the most important server parameter is MTBF. Power management can increase the MTBF and efficiency of the cooling subsystem. This in turn increases MTBF of disks and the entire system. One degree away from the optimum operating temperature can decrease a disk's life by an year or more.
Also, you do not spin down disks on servers for both business and reliability reasons. The business reason is server latency. The reliability reason is that most server HDUs hate to be spun down and their MTBF decreases (which is again business in a sense). Also, the biggest power eaters in most modern servers are the cooling systems and the CPUs. Not the disks. Disks hardly go above 2-10W nowdays while a PIII with the fans can go up to a 100W. Alpha goes even beyond that. Also, spinning up and down disks to 7200-10000 RPM can actually generate more heat and consume more power than keeping them running.
Some bits of info by platform:
So overall the situation is that for one of the most popular platforms the power magement is hardly used due to the fact that the OS support just came in. For the second most popular platform (Sun) the power management was never there. The others are pretty much there as well.
And to conclude: I do not feel comfortable installing linux 2.4.0 or the ACPI support for BSD on real production machines yet.
The ratio for average server performance is more than 1:2 not 1:12. So you logic is flawed. Transmeta is not that slow. Tried it. It is about as fast as PIII at the same frequency on integer math and this is what matters for a server. Also, for real server operations quite often the bottleneck is the IO, not the CPU anyway.
The reason why people use PIII and not transmeta or AMD (which also has very good power saving under UNIXes) is the fact that there are no server boards available. For example try to find a mainboard for AMD with console redirection and enjoy the nightmare. At the same time all high end Intel and ServerWorks boards support it.
One reasonable person amidst the insane zealots. Finally.
The important bit is the server platform. It is very hard to make cretinous Minesweeper Consulatants and Solitaire Experts that dwell around the coridors of large corps and claim to be from the "Incompetent in Technology" department to use anything but MS Exchange. So anything that can deal with their abominative productions is more than welcome.
Welcome to the world of telecoms. And that is the exact reason I will buy myself a visorphone. Because it is built from the PDA to the phone so that it is not encumbered by the standard nasonal telecom appreciation like all the GSM phone stuff currently in circulation. And in btw, some patents there are much sillier than the patents in software.
Especially about the gentle giant. 747 is a subject to additional USAF and NATO requirements and all 747s currently in operation are subject to draft in case of military emergency. Which actually happened during the Gulf War. The airlines were extremely pissed off but there was nothing they could do.
It is not a gentle giant. It is a military transport aircraft. It is redundant by the military, not the civil aviation spec (check the engine redundancy and power excess parameters for example). And it was already used in several projects as a carrier for Star Wars weapons (mostly missiles and stuff). So nothing new. Nothing amazing.
You mean carefull, not cluefull, right? As they have set themselves up for a trademark infringement suit. And a good one...