I believe that the Samba team is concerned with patent enforcement.
I remember an article in the past regarding some type of password hashing technique where Microsoft discretely reminded a Samba developer that the Samba code was treading on a Microsoft patent.
I own macs, pcs, linux and bsd systems. Just observing:
No PC user is going to shell out $130/year for OS upgrades. Rule of thumb is 3 year minimum. My most recent install is Win2000. A one year duration is wayyyy to much.
No PC user is going to switch when the old OSes aren't supported. Despite their threats, WinUpdate still releases patches for Win98. Where are my 10.[01] patches? Unbelieveably, Microsoft is the best for OS support longevity.
These are huge problems if Apple really wants "switchers." I don't think that they do.
The G4 is finally introducing a memory interface that is significantly faster than PC133. Granted, it is no G5, but there is life in it yet.
Apple should maintain a relationship with the Motorola semiconductor unit. I don't think that Apple managed their dual-supplier relationship very well in the past (altivec), but adopting IBM as a single supplier now should frighten them. We've seen what IBM can do when it's angry.
Transmeta makes wholesale changes to the backend architecture of these chips with each release. The x86 frontend is the only thing that they guarantee to remain stable.
A compiler producing native Transmeta code would need to emit (wildly) different code for each different revision. I read a quote from Linus somewhere that the scheduling and parallelism issues are very, very messy.
So that is why you don't see native Transmeta compilers, although I have heard of large customers tweaking the translation software for higher FPU performance.
As in where you have to declare all your variables at the very beginning and can't declare them anywhere else.
Sure you can.
#include <stdio.h> main() { int i = 2; printf("%d\n", i); { int j = 5;
printf("%d\n", i + j); }
printf("goodbye, world!\n"); }
In some cases, it is more clear to do the above than have useless variables defined over much larger scopes - it may be easier on memory, too, since the automatic variable will exist over a sorter duration.
As a grad student, I worked with a team where the project lead insisted that infinite loops be written at "while(1)" - even though K&R wrote them as "for(;;)" - and the position was not changed even after I produced documentation.
Just because some stupid teacher says that a certain programming style is bad, doesn't mean that it has no application. If your teachers told you that flat-head screwdrivers were stylistically bad and should never be used, would you believe them?
I'm an Oracle man myself, so I don't know beans about SQL Server. However, I would think that these people would.
According to the reports, plant computer engineers hadn't installed the patch for the MS-SQL vulnerability that Slammer exploited. In fact, they didn't know there was a patch, which Microsoft released six months before Slammer struck.
Of course, auto apply/reboot is not acceptable - but Windows Update ought to handle patches for all M$ products. It ought to automatically download patches for any installed products, and prompt to apply. RedHat up2date certainly could handle this.
M$ was roundly criticised for "hiding" the Slammer patch so well. Why install software that a) will not be patched and b) is sure to be abused?
There will be bugs in the M$ nfs server code. Will Windows Update patch them?
The patch against SQL Slammer had been out for six months before Slammer took down South Korea and invaded a nuclear power plant. I don't want to install anything that requires special patching procedures.
...one of my firewalls to a Compaq Contura 50MHz 486. The power supply says that it takes only 26W.
Various OpenBSD people get excited with the Soekris. I think this super-486 board is underpowered for the price. I'd like to see a Transmeta Crusoe or VIA Eden in the same form factor, which should be much faster. Never seen one though.
If you're in it just for the money, I really don't want to hear your music anyway. Art should be created for the love of the art, not for monetary gain.
If what you are saying were true, then we should shut down the entire entertainment industry and replace it with an organization on a subsistence government dole.
Some art produced for profit is good, and some is not. Some art produced as a means to other ends is good, and some is not. Some art produced as an end in itself is good, and some is not.
I've never seen a set of rules that can navigate such matters of personal taste. Your generalization is bad.
In the interaction between Newtonian and Quantum physics, we can infer that any creator might be both deterministic and chaotic. Asserting that this creator "willed" life on Mars is missing the point - perhaps the creator both willed it and allowed it to develop via probability. In the final analysis, just as we lack a full understanding of the universe around us, we cannot have full understanding of the one who created it. It's a Heisenberg thing.
The Bible, like all of the other religious texts, are simple stories written for a simple people. Any of them might be true, and all of them might be true. If they are true, they must be seen as the most basic preperatory readers, on the level of a "Dick and Jane" school text. As you peruse a treatise on metaphysics or physical sciences, the Dick and Jane is still important, but it is less of a focus.
In any case, just as you do not walk into a friends house and start telling them why they furnished it as they did, we should not assert that the creator is this or that. The creator is as it wishes to be, and if it wishes to predate the physical universe, then perhaps it does. If it does not wish to predate the physical universe, then perhaps it does not. In any case, it is certainly not my place to say one way or the other.
...the documentation advises against building your own kernel unless you have a very good reason. They won't support you, either (not that their support will solve all your problems).
Under most circumstances you will NOT need to compile your own kernel. The GENERIC kernel will usually be all that you need. In fact, there are several reasons why you do not want to create your own kernel. The main reason is that it is very easy to make changes to the kernel configuration which look logical, but do not work. This is your danger sign. If something does not appear to work properly, please try the GENERIC kernel before sending in a bug report. Developers will usually ignore bug reports dealing with custom kernels, unless the problem can be reproduced in a GENERIC kernel as well. You have been warned.
I find it hard to believe that anything taken out of context could be worse than what he says in context:
We're sick and tired of talking. Around here we do things. And we do
it how we like it. And I am not going to change my processes for you.
I make release when *I WANT TO*. And I WANT TO make them every 6 months,
and that is that. So stop acting as if this is a democratic process.
I'm the one doing the release work, so get stuffed.
AMD seems to want to outsource compiler development. I've read recently on the Inquirer that Intel compilers produce very fast code on AMD. Some third parties are also releasing optimized AMD64 compilers, also.
They should have completely simulated this mission by putting a rover down in an abandoned field and conducting a full analysis, just as they planned to do on Mars.
How could they have not stress-tested the file system? I'm amazed!
...as the substrate of the chip, rather than a silicon wafer, so the chip was a "sapphire" chip rather than a silicon chip (although doped silicon could then be used to form transistors, as could Gallium Arsenide or Germanium, through the regular lithographic process).
This is the classic "Silicon On Insulator." IBM has a process of embedding a layer of glass beneath the surface of a standard silicon wafer, allowing SOI using silicon substrates. This and their work with copper set them apart from the other large silicon transisitor foundries (TSMC, Intel, etc.).
The processors on the rovers are probably SOI, but I don't know which process is used.
Slashdot Mirror
I believe that the Samba team is concerned with patent enforcement.
I remember an article in the past regarding some type of password hashing technique where Microsoft discretely reminded a Samba developer that the Samba code was treading on a Microsoft patent.
The EU action gets the patent engine rolling.
I own macs, pcs, linux and bsd systems. Just observing:
These are huge problems if Apple really wants "switchers." I don't think that they do.
The G4 is finally introducing a memory interface that is significantly faster than PC133. Granted, it is no G5, but there is life in it yet.
Apple should maintain a relationship with the Motorola semiconductor unit. I don't think that Apple managed their dual-supplier relationship very well in the past (altivec), but adopting IBM as a single supplier now should frighten them. We've seen what IBM can do when it's angry.
Does anybody know if there is a Soekris-like board built with Transmeta?
I'd like to buy a low-power embedded server with something better than a souped-up 486. A micro-micro-ITX system might be cool, too.
Transmeta makes wholesale changes to the backend architecture of these chips with each release. The x86 frontend is the only thing that they guarantee to remain stable.
A compiler producing native Transmeta code would need to emit (wildly) different code for each different revision. I read a quote from Linus somewhere that the scheduling and parallelism issues are very, very messy.
So that is why you don't see native Transmeta compilers, although I have heard of large customers tweaking the translation software for higher FPU performance.
Sure you can.
In some cases, it is more clear to do the above than have useless variables defined over much larger scopes - it may be easier on memory, too, since the automatic variable will exist over a sorter duration.
As a grad student, I worked with a team where the project lead insisted that infinite loops be written at "while(1)" - even though K&R wrote them as "for(;;)" - and the position was not changed even after I produced documentation.
Just because some stupid teacher says that a certain programming style is bad, doesn't mean that it has no application. If your teachers told you that flat-head screwdrivers were stylistically bad and should never be used, would you believe them?
I'm an Oracle man myself, so I don't know beans about SQL Server. However, I would think that these people would.
Of course, auto apply/reboot is not acceptable - but Windows Update ought to handle patches for all M$ products. It ought to automatically download patches for any installed products, and prompt to apply. RedHat up2date certainly could handle this.
M$ was roundly criticised for "hiding" the Slammer patch so well. Why install software that a) will not be patched and b) is sure to be abused?
There will be bugs in the M$ nfs server code. Will Windows Update patch them?
The patch against SQL Slammer had been out for six months before Slammer took down South Korea and invaded a nuclear power plant. I don't want to install anything that requires special patching procedures.
...one of my firewalls to a Compaq Contura 50MHz 486. The power supply says that it takes only 26W.
Various OpenBSD people get excited with the Soekris. I think this super-486 board is underpowered for the price. I'd like to see a Transmeta Crusoe or VIA Eden in the same form factor, which should be much faster. Never seen one though.
Signal processing engineers know that nature abhors the unit impulse.
A gradual reduction in services over a few months might have kept the fellow out of gaol.
If what you are saying were true, then we should shut down the entire entertainment industry and replace it with an organization on a subsistence government dole.
Some art produced for profit is good, and some is not. Some art produced as a means to other ends is good, and some is not. Some art produced as an end in itself is good, and some is not.
I've never seen a set of rules that can navigate such matters of personal taste. Your generalization is bad.
AMD made a bundle by keeping a stable SlotA/SocketA while Intel constantly changed the socket.
I realize that Hypertransport changes things, but why can't AMD settle down into a standard Athlon64 socket? Do they know what this will cost them?
In any case, just as you do not walk into a friends house and start telling them why they furnished it as they did, we should not assert that the creator is this or that. The creator is as it wishes to be, and if it wishes to predate the physical universe, then perhaps it does. If it does not wish to predate the physical universe, then perhaps it does not. In any case, it is certainly not my place to say one way or the other.
...if it were able to use DDR RAM. The chip clocks competetively, but is handicapped by PC133.
Why is it that a G4's memory subsystem can't be retrofitted with DDR?
...until you can get a major commercial vendor to bite and dump their own package system.
I seem to remember that Digital UNIX was converting to RPM, but it doesn't seem to have panned out.
I don't know beans about astronomy, but:
We did with Hubble what we did with the Shuttle: we stuck with a bad design for far too long.
Never develop a sentimental attachment to technology.
...the documentation advises against building your own kernel unless you have a very good reason. They won't support you, either (not that their support will solve all your problems).
Is there any way that we could prod Santana to bring his binary patches up to date for 3.3 i386 when the patch is released?
I've already emailed him that I'd send him $50.
I find it hard to believe that anything taken out of context could be worse than what he says in context:
Granted, OpenBSD is his baby.
The extra registers are all integer registers; the SIMD instructions and register count do not change between 32 and 64 bit modes.
If the tests are truly FP-centric, this shouldn't make any difference.
AMD seems to want to outsource compiler development. I've read recently on the Inquirer that Intel compilers produce very fast code on AMD. Some third parties are also releasing optimized AMD64 compilers, also.
XFS is GPL. Is SGI changing to a BSD license?
Good heavens, that is a ridiculous quantity of acronyms!
They should have completely simulated this mission by putting a rover down in an abandoned field and conducting a full analysis, just as they planned to do on Mars.
How could they have not stress-tested the file system? I'm amazed!
...as the substrate of the chip, rather than a silicon wafer, so the chip was a "sapphire" chip rather than a silicon chip (although doped silicon could then be used to form transistors, as could Gallium Arsenide or Germanium, through the regular lithographic process).
This is the classic "Silicon On Insulator." IBM has a process of embedding a layer of glass beneath the surface of a standard silicon wafer, allowing SOI using silicon substrates. This and their work with copper set them apart from the other large silicon transisitor foundries (TSMC, Intel, etc.).
The processors on the rovers are probably SOI, but I don't know which process is used.