This reading of the message is unlikely to be correct. There are following reasons:
The message about the panzers is useless without knowing the actual direction the panzers drive to. The same is true for Jerry's whereabouts.
It is highly unlikely that the codebook used would use the first letters of the messages. Codes were not always strong, but this would border on pure incompetence.
If the codes are actually consisting of the first letters of message words, one would expect the letter frequencies of the message to be comparable to the English language. But this is not the case. There are too many Xs, Qs and Js.
The actual codebook using the acronyms have not been cited, referenced or a picture provided.
Five-letter groups are standard for the time. There is no reason to believe that there is a single six-letter PABLIZ group in the message. In the picture published by GCHQ the group is clearly PABUZ and not PABLIZ.
AOAKN is repeated at the front and at the end of the message. It is more likely that this is an indicator group and doesn't have any meaning.
At this point in time there is not much one can say for sure about the message: The message encryption requires a substitution because the letter frequency is significantly different form English. It is not a pure transposition. A codebook is possible, but I wouldn't exclude substitution ciphers right now. AOAKN is very likely a indicator group.
This paper has not seen any reasonable peer review. There are indices simply missing. The letter l (ell) is clearly not a good index. He uses n for number of transactions, users and networks. He even uses n for networks and users in the same formula, which must mean that number of users and networks are identical. In the summation of the users he leaves the denominators simply away. Usually scientiest don't name laws after themselves.
This doesn't mean that the basic idea might be wrong, but the work itself doesn't support the argument.
Who is disagreeing with the license change?
on
GCC 4.2.1 Released
·
· Score: 1
I have just looked at the GCC mailing list. There is some discussion how to make the change the best way and what happens to backports. But I have to see now a message, which explicitly states, that he will fork GCC. I think this is overblown.
There have actually been two crew losses by Soyuz: One cosmonaut at Soyuz 1 and three others at Soyuz 11. In the first case the main parachute didn't deploy and in the second case a valve were not closed during the landing. So the failure rate of the Space Shuttle is actually better 2/117 < 2/96. However the Soyuz had no crew loss since 1971, so the early issues have been fixed. It will be quite difficult to make this statement about the Shuttle.
This sounds well in theory, but in practice it will not work. There is a lot of very specific information required to implement firmware, which is not even available from the open-source-friendly vendors. If you think, this shouldn't stop smart people, then try it on your own.
I write together with others the ZD1211 WLAN driver for the Linux kernel and though we have a lot of useful information from the vendor, we have huge trouble to match the performance of the Windows driver. If you think that is our fault, try to do better. Keep in mind that the developers of the Windows driver, have access to the hardware engineers, know all the registers on the chips and have access to test labs and equipment. All the information we have about the hardware registers is the open-source driver of the vendor, but you have to reverse engineer the semantics of the vendor driver.
From my perspective the PC becomes more and more a closed platform, which makes it more and more difficult to compete with Windows. The reverse-engineering effort required becomes larger and larger, which should be spend on performance optimizations or feature requests. I personally believe that closed source drivers should be banned from the Linux kernels, because they support this trend to the closed PC platform.
I'm no astrophysicist. But Alex Mayer claims based on his explaination of the red-shift, that there has never been a big bang. He explains a number of phenomena based on his theory and he doesn't need dark energy and dark matter, which is currently needed to make the theories match observed reality.
I'm in no position to judge his radical theories, but I like the way that he tries to show, that his theories are consistent with observed facts. He will certainly have some opposition and it will be interesting to see, whether somebody could put a hole in his theories.
I don't buy the argument, that pointers are needed for interoperation with existing libraries.
Java can interoperate without supporting the pointer concept and P/Invoke (Platform Invoke) can be used on.net without leaving the managed code. BTW it is possible to create pointer issues with P/Invoke without writing a single line of "unsafe" code. Been there, done this.
However in all VMs calling native code is slow because the VM has to switch to another mode to support it, so the best way is always to implement all algorihtms in the VM environment and switch to native libraries only for device interaction or huge batch jobs.
As far as I understood Mr. Theisinger, the problem is that programms and config data to operate the Rover are stored on the flash file system. The rover has no other mean to store data permanently. The computer is normally shut down at the end of each Sol (Mars day). So without the mounted flash file system, the Rover can't be fully operational. The software reboots after ca. 40 minutes in the failure mode. Now it seems, that they have to send always a command which prevents the reboot after 40 minutes.
Probably they have to reformat the flash RAM, but before that the must transmit they complete flash-ram image to analyze, the cause of the problem. Transferring 256 MByte (2 GBit) over 60 million km is quite a challenge, even if you can compress it. Transmission for a satellite pass are around 20 MBit and the direct to link to earth (estimated 4 hrs a day)is 13 kbit/s maximum, which results in an estimated 182 MBit maximum per day. So we have a maximum capacity of 200 MBit per day, if all goes extremely well.
So if half of that capacity could be indeed used for the flash RAM and the compression rate is 0.25, you need ca. 5 days to get the complete disk image. The real numbers will be of course different, but I think this estimation is in the right range. I think, that Theisinger's 3 week prediction before operational mode is not to pessimistic.
I'm not a legal expert, but I assume that all changes are made while you are working at the
company. This means the copyright of the code belongs to the company. If you want to publish your patches, you need a formal decision by the company management for doing this. Notify that if you modify code under the GPL and distribute that code to a third party, you are required to publish it with the complete source.
Please make sure, that every decision is documented and signed by the legal responsible persons. Keep hard copies of these documents.
Re:IMPORTANT: Please translate. Infringement Doc.
on
SCO To Show Copied Code
·
· Score: 4, Interesting
Nothing dramatic.
Basically they say, that if you use SCO shared libraries with Linux, you have to license them. There is some hyperbole: So they try to create the impression, that there is no UNIX software available without the iBCS2 interface. No need for comment.
They also state, that most users using the iCBS2 kernel interface didn't respect the copyright of SCO shared libraries. Today there is no need for SCO shared libs anyway, because all Linux application vendors sell now native Linux binaries using the GNU libc shared libraries.
Nothing in the above document proves following statement from SCO's letter to Linux customers:
"We have evidence that portions of UNIX System V software code have been copied into Linux and that additional other portions of UNIX System V software code have been modified and copied into Linux, seemingly for the purposes of obfuscating their original source."
As a Linux customer I request from SCO:
(1) Show the evidence! (2) Use clear language: What do you mean with Linux? Whole Distributions or the kernel. (3) Publish the UNIX source code into the Public Domain to become a respected company once again.
(1) Strategic value of proprietary Word format decreases.
Most texts written today are E-Mails not Word-Documents.
Word becomes more and more an editing format. Documents are published as ASCII texts, HTML and PDF.
Word douments can't be combined with Web services, I've never seen a Web application creating Word documents.
(2) Microsoft can't create a new proprietary format, that can't be read by Word 97.
Everybody will accept that Word 97 doesn't read XML. If you want XML, you have to buy the new Office.
(3) Outlook and Internet Explorer are examples how Microsoft can dominate a market starting with standard formats and protocols.
The problem is cause be the EBDIC code. It has special codes for CARRIAGE RETURN (CR), LINE FEED (LF) and NEW LINE (NL). The problem is now how you convert NL into UNICODE, you could map it to LF, but that can't be mapped back. You could als map it to LINE SEPERATOR U+2028, but IBM seems to think that mapping it the NEL (New Line) U+0085 control character is appropriate. This is supported by UNICODE standard annex UAX #13. However in UAX #14 U+0085 has not the line breaking property, so there is still some inconsistence in the UNICODE standard.
But I don't think this is an major issue. It does mean only, that you will have problems to edit XML-documents generated in EBCDIC in some of the worser editors. We have lived all the years with the DOS CRLF/UNIX LF problem, so we will survive this too.
Imagine a CIO of a Fortune 500 company, planning a new web project. For the hardware he has two options:
/1/ Add a dozen or more CPUs and some RAM to the existing mainframe infrastructure, to support a number of Linux images. (His data center probably runs a number of several MVS, OS/390 and maybe z/OS images in parallel.)
/2/ Buy and install two new Sun Starfire 15K.
Obviously his choice would be/1/, if the software guys are saying that it will work. Probably they will have all a Linux partition on their PC:-).
If costs is the strong argument in the situation, Sun will have only a chance with large discounts.
I think Sun's strategy to build the next mainframe with the 15K backfires here, because for web servers the Intel rack hardware running Linux is the better option and IBM's virtual OS images will use CPU and RAM more efficiently than Sun's domain per 4-processor cartridge by definition. The nightly mainframe batches map well with the usage patterns of online services.
So Sun's revenue is now attacked by Linux from below and from above. These guys are forced to love Linux. Remember Linus's joke about world domination?
We have used Linux and Token Ring for years in our company network. Biggest problem has been to find a reliable drivers. We settled for Olicom adapters and their driver. The driver works under kernel version 2.2.19. We used it on our central CVS server with more than 50 users. Olicom has been bought by Madge the other non-IBM-producer of Token-Ring-Adapters.
We switched the whole network to 100 MBit Ethernet, so we will not look into the issue in the future.
The drivers in the kernel have some problems, particular for PCMCIA.
Here some useful links:
Linux Token-Ring page, with updated drivers, but a discouraging news entry from 9/14/2001:
http://www.linuxtr.net/
Linux-Software for Olicom-Drivers(recommended):
http://www.madge.com/connect/downloads/software/ ol icom/
Linux-Software for Madge-Adapters on:
http://www.madge.com/Connect/Downloads/Software/
You may fool all the people some of the time, you can even fool some of the people all of the time; but you can't fool all of the people all of the time.
Somewhere in the book it is stated, that Dirk Hohndel is CEO of Suse AG. He has never been the CEO, he is currently the CTO.
Comment: I found it a shame that celebrities like Bill Gates, Bill Joy or Steve Jobs found their way into the book, but not a single name of his lieutenants: Alan Cox, Theodore Tso, H.J. Lu to name a few.
The book is a perfect gift for geek mothers, girlfriends and wifes:
1) Your geek isn't alone.
2) This Linus Torvalds seems to be more social dysfunctional than your geek.
3) Don't send your geek to the gym or outdoors, he will lose millions there.
First UNICODE gives only advantage to the US and english speaking countries, because UTF-8 is compatible with ASCII (American Standard Code for Information Interchange).
Germany has the problem that UNICODE uses the same code points as ISO 8859 Latin 1, but UTF-8 encodes all characters above code point 127 different.
UNICODE 3.1 differentiates code points and encodings. There a range of encodings UTF-8, UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE and UTF-32LE. This way it is possible to extend the code space to the 170.000 code points characters requested by the author of the article. At least another supplementary plane has to be used. It should be noted, that the policy of UNICODE forbids the assignment of the same character to several code points unless there exists an already a standard defining the characters. So it might be that less than 170.000 code points are necessary.
UNICODE made the mistake to assume that 16 Bit are enough to encode all the characters of the world. But they have corrected that mistake without breaking the current implementations introducing code point and encoding semantics.
I believe that UNICODE ist the best thing we have now and everybody criticising UNICODE should make proposals for improvements or another scheme. As far as I understand, the definition of a world wide unique character code is far from easy.
Top 10 reasons for usung Z-Shell
on
To Z Or Not To Z
·
· Score: 4
10) precmd() calls commands before displaying the prompt
9) user binding of keys for command line editing
8).zlogout
7) ignores duplicates in the history list
6) best prompt: spider:src/linux/include/linux * (cuts longer directory names)
5) compatible with Bourne Shell, works as expected
4) best completion
3) make |& less feeds stdout and and stdin into less, shorter than make 2>&1 | less
2) Z-Shell has the best vi emulation
1) more exclusive than vim;-)
I recommend the stable version 3.0.8, zsh in distributions are often from the 3.1 branch. This version breaks my skeleton files and some things (vi binding) doesn't work as I'm used too.
Writing an OS is such a complex task, that a look into other people code shouldn't be a problem.
Hey, that's what Open Source is about. But you are not allowed to integrate GPL'd code into your product.
What we need is some kind of proof, like function names in debugging versions of the NT/Win2K kernel. Otherwise Petreley has lost the basic of good journalism: No fiction!
The SAP wants to announce tomorrow on the LinuxWorld in Frankfurt [/Main], that it's data base SAP DB will be licensed under GPL or LGPL. Until now the SQL data base has been mainly used together with the flag ship of the Walldorf company, the merchandise planning and control system SAP R/3. However R3 provides interfaces to data bases like Informix, Oracle or DB2. For the first time SAP releases a bigger software project in source code. (ju/c't)
Slashdot Mirror
At this point in time there is not much one can say for sure about the message: The message encryption requires a substitution because the letter frequency is significantly different form English. It is not a pure transposition. A codebook is possible, but I wouldn't exclude substitution ciphers right now. AOAKN is very likely a indicator group.
The number of primes pi(x) not exceeding x is approximately x/ln(x). (Source: Graham, Knuth and Patashnik, "Concrete Mathematics")
This paper has not seen any reasonable peer review. There are indices simply missing. The letter l (ell) is clearly not a good index. He uses n for number of transactions, users and networks. He even uses n for networks and users in the same formula, which must mean that number of users and networks are identical. In the summation of the users he leaves the denominators simply away. Usually scientiest don't name laws after themselves.
This doesn't mean that the basic idea might be wrong, but the work itself doesn't support the argument.
I have just looked at the GCC mailing list. There is some discussion how to make the change the best way and what happens to backports. But I have to see now a message, which explicitly states, that he will fork GCC. I think this is overblown.
There have actually been two crew losses by Soyuz: One cosmonaut at Soyuz 1 and three others at Soyuz 11. In the first case the main parachute didn't deploy and in the second case a valve were not closed during the landing. So the failure rate of the Space Shuttle is actually better 2/117 < 2/96. However the Soyuz had no crew loss since 1971, so the early issues have been fixed. It will be quite difficult to make this statement about the Shuttle.
This sounds well in theory, but in practice it will not work. There is a lot of very specific information required to implement firmware, which is not even available from the open-source-friendly vendors. If you think, this shouldn't stop smart people, then try it on your own.
I write together with others the ZD1211 WLAN driver for the Linux kernel and though we have a lot of useful information from the vendor, we have huge trouble to match the performance of the Windows driver. If you think that is our fault, try to do better. Keep in mind that the developers of the Windows driver, have access to the hardware engineers, know all the registers on the chips and have access to test labs and equipment. All the information we have about the hardware registers is the open-source driver of the vendor, but you have to reverse engineer the semantics of the vendor driver.
From my perspective the PC becomes more and more a closed platform, which makes it more and more difficult to compete with Windows. The reverse-engineering effort required becomes larger and larger, which should be spend on performance optimizations or feature requests. I personally believe that closed source drivers should be banned from the Linux kernels, because they support this trend to the closed PC platform.
I'm no astrophysicist. But Alex Mayer claims based on his explaination of the red-shift, that there has never been a big bang. He explains a number of phenomena based on his theory and he doesn't need dark energy and dark matter, which is currently needed to make the theories match observed reality.
I'm in no position to judge his radical theories, but I like the way that he tries to show, that his theories are consistent with observed facts. He will certainly have some opposition and it will be interesting to see, whether somebody could put a hole in his theories.
I don't buy the argument, that pointers are needed for interoperation with existing libraries.
Java can interoperate without supporting the pointer concept and P/Invoke (Platform Invoke) can be used on .net without leaving the managed code. BTW it is possible to create pointer issues with P/Invoke without writing a single line of "unsafe" code. Been there, done this.
However in all VMs calling native code is slow because the VM has to switch to another mode to support it, so the best way is always to implement all algorihtms in the VM environment and switch to native libraries only for device interaction or huge batch jobs.
As far as I understood Mr. Theisinger, the problem is that programms and config data to operate the Rover are stored on the flash file system. The rover has no other mean to store data permanently. The computer is normally shut down at the end of each Sol (Mars day). So without the mounted flash file system, the Rover can't be fully operational. The software reboots after ca. 40 minutes in the failure mode. Now it seems, that they have to send always a command which prevents the reboot after 40 minutes. Probably they have to reformat the flash RAM, but before that the must transmit they complete flash-ram image to analyze, the cause of the problem. Transferring 256 MByte (2 GBit) over 60 million km is quite a challenge, even if you can compress it. Transmission for a satellite pass are around 20 MBit and the direct to link to earth (estimated 4 hrs a day)is 13 kbit/s maximum, which results in an estimated 182 MBit maximum per day. So we have a maximum capacity of 200 MBit per day, if all goes extremely well. So if half of that capacity could be indeed used for the flash RAM and the compression rate is 0.25, you need ca. 5 days to get the complete disk image. The real numbers will be of course different, but I think this estimation is in the right range. I think, that Theisinger's 3 week prediction before operational mode is not to pessimistic.
I'm not a legal expert, but I assume that all changes are made while you are working at the company. This means the copyright of the code belongs to the company. If you want to publish your patches, you need a formal decision by the company management for doing this. Notify that if you modify code under the GPL and distribute that code to a third party, you are required to publish it with the complete source. Please make sure, that every decision is documented and signed by the legal responsible persons. Keep hard copies of these documents.
Nothing dramatic.
Basically they say, that if you use SCO shared libraries with Linux, you have to license them. There is some hyperbole: So they try to create the impression, that there is no UNIX software available without the iBCS2 interface. No need for comment.
They also state, that most users using the iCBS2 kernel interface didn't respect the copyright of SCO shared libraries. Today there is no need for SCO shared libs anyway, because all Linux application vendors sell now native Linux binaries using the GNU libc shared libraries.
Nothing in the above document proves following statement from SCO's letter to Linux customers:
"We have evidence that portions of UNIX System V software code have been copied into Linux and that additional other portions of UNIX System V software code have been modified and copied into Linux, seemingly for the purposes of obfuscating their original source."
As a Linux customer I request from SCO:
(1) Show the evidence!
(2) Use clear language: What do you mean with Linux? Whole Distributions or the kernel.
(3) Publish the UNIX source code into the Public Domain to become a respected company once again.
So debugging code is easier for simpler, cleaner code. So KISS (Keep it simple and stupid) will be the best debugging tool, we will ever have.
(1) Strategic value of proprietary Word format decreases. Most texts written today are E-Mails not Word-Documents. Word becomes more and more an editing format. Documents are published as ASCII texts, HTML and PDF. Word douments can't be combined with Web services, I've never seen a Web application creating Word documents. (2) Microsoft can't create a new proprietary format, that can't be read by Word 97. Everybody will accept that Word 97 doesn't read XML. If you want XML, you have to buy the new Office. (3) Outlook and Internet Explorer are examples how Microsoft can dominate a market starting with standard formats and protocols.
The problem is cause be the EBDIC code. It has special codes for CARRIAGE RETURN (CR), LINE FEED (LF) and NEW LINE (NL). The problem is now how you convert NL into UNICODE, you could map it to LF, but that can't be mapped back. You could als map it to LINE SEPERATOR U+2028, but IBM seems to think that mapping it the NEL (New Line) U+0085 control character is appropriate. This is supported by UNICODE standard annex UAX #13. However in UAX #14 U+0085 has not the line breaking property, so there is still some inconsistence in the UNICODE standard. But I don't think this is an major issue. It does mean only, that you will have problems to edit XML-documents generated in EBCDIC in some of the worser editors. We have lived all the years with the DOS CRLF/UNIX LF problem, so we will survive this too.
Imagine a CIO of a Fortune 500 company, planning a new web project. For the hardware he has two options:
/1/, if the software guys are saying that it will work. Probably they will have all a Linux partition on their PC :-).
/1/ Add a dozen or more CPUs and some RAM to the existing mainframe infrastructure, to support a number of Linux images. (His data center probably runs a number of several MVS, OS/390 and maybe z/OS images in parallel.)
/2/ Buy and install two new Sun Starfire 15K.
Obviously his choice would be
If costs is the strong argument in the situation, Sun will have only a chance with large discounts.
I think Sun's strategy to build the next mainframe with the 15K backfires here, because for web servers the Intel rack hardware running Linux is the better option and IBM's virtual OS images will use CPU and RAM more efficiently than Sun's domain per 4-processor cartridge by definition. The nightly mainframe batches map well with the usage patterns of online services.
So Sun's revenue is now attacked by Linux from below and from above. These guys are forced to love Linux. Remember Linus's joke about world domination?
From my .zshenv, works in .profile too. Could be used also for other path variables. Works for all Operating Systems with a reasonable Bourne Shell.
/usr/local/gcc-2.95.2/bin
/opt/kde/bin
/usr/lib/java/bin
/usr/X11R6/bin
/usr/local/samba/bin
/usr/local/ssl/bin
/usr/local/bin
/usr/local/bin/gnu
/usr/bin
/bin
/usr/local/sbin
/usr/sbin
/sbin
/usr/ucb
/usr/bin/X11
/usr/ccs/bin
export PATH
reset_path() {
NPATH=''
}
set_path() {
if [ -d "$1" ]; then
if [ -n "$NPATH" ]; then
NPATH="$NPATH:$1"
else
NPATH="$1"
fi
fi
}
reset_path
set_path $HOME/bin
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
set_path
PATH="$NPATH:."
unset reset_path set_path
We have used Linux and Token Ring for years in our company network. Biggest problem has been to find a reliable drivers. We settled for Olicom adapters and their driver. The driver works under kernel version 2.2.19. We used it on our central CVS server with more than 50 users. Olicom has been bought by Madge the other non-IBM-producer of Token-Ring-Adapters.
/ ol icom/
/
We switched the whole network to 100 MBit Ethernet, so we will not look into the issue in the future.
The drivers in the kernel have some problems, particular for PCMCIA.
Here some useful links:
Linux Token-Ring page, with updated drivers, but a discouraging news entry from 9/14/2001:
http://www.linuxtr.net/
Linux-Software for Olicom-Drivers(recommended):
http://www.madge.com/connect/downloads/software
Linux-Software for Madge-Adapters on:
http://www.madge.com/Connect/Downloads/Software
We should concentrate on better code, more user-friendly software and more consistent interfaces.
We should defend the GPL wherever we are, because it protects our rights to use our own work.
You may fool all the people some of the time, you can even fool some of the people all of the time; but you can't fool all of the people all of the time.
Somewhere in the book it is stated, that Dirk Hohndel is CEO of Suse AG. He has never been the CEO, he is currently the CTO.
Comment: I found it a shame that celebrities like Bill Gates, Bill Joy or Steve Jobs found their way into the book, but not a single name of his lieutenants: Alan Cox, Theodore Tso, H.J. Lu to name a few.
The book is a perfect gift for geek mothers, girlfriends and wifes:
1) Your geek isn't alone.
2) This Linus Torvalds seems to be more social dysfunctional than your geek.
3) Don't send your geek to the gym or outdoors, he will lose millions there.
First UNICODE gives only advantage to the US and english speaking countries, because UTF-8 is compatible with ASCII (American Standard Code for Information Interchange).
Germany has the problem that UNICODE uses the same code points as ISO 8859 Latin 1, but UTF-8 encodes all characters above code point 127 different.
UNICODE 3.1 differentiates code points and encodings. There a range of encodings UTF-8, UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE and UTF-32LE. This way it is possible to extend the code space to the 170.000 code points characters requested by the author of the article. At least another supplementary plane has to be used. It should be noted, that the policy of UNICODE forbids the assignment of the same character to several code points unless there exists an already a standard defining the characters. So it might be that less than 170.000 code points are necessary.
UNICODE made the mistake to assume that 16 Bit are enough to encode all the characters of the world. But they have corrected that mistake without breaking the current implementations introducing code point and encoding semantics.
I believe that UNICODE ist the best thing we have now and everybody criticising UNICODE should make proposals for improvements or another scheme. As far as I understand, the definition of a world wide unique character code is far from easy.
10) precmd() calls commands before displaying the prompt .zlogout ;-)
9) user binding of keys for command line editing
8)
7) ignores duplicates in the history list
6) best prompt:
spider:src/linux/include/linux *
(cuts longer directory names)
5) compatible with Bourne Shell, works as expected
4) best completion
3) make |& less feeds stdout and and stdin into less, shorter than make 2>&1 | less
2) Z-Shell has the best vi emulation
1) more exclusive than vim
I recommend the stable version 3.0.8, zsh in distributions are often from the 3.1 branch. This version breaks my skeleton files and some things (vi binding) doesn't work as I'm used too.
Writing an OS is such a complex task, that a look into other people code shouldn't be a problem.
Hey, that's what Open Source is about. But you are not allowed to integrate GPL'd code into your product.
What we need is some kind of proof, like function names in debugging versions of the NT/Win2K kernel. Otherwise Petreley has lost the basic of good journalism: No fiction!
comments in [ ]
Translation from heise news ticker.
Message from 04.10.2000 15:43 [MEST]
SAP goes Open Source
The SAP wants to announce tomorrow on the LinuxWorld in Frankfurt [/Main], that it's data base SAP DB will be licensed under GPL or LGPL. Until now the SQL data base has been mainly used together with the flag ship of the Walldorf company, the merchandise planning and control system SAP R/3. However R3 provides interfaces to data bases like Informix, Oracle or DB2. For the first time SAP releases a bigger software project in source code. (ju/c't)