No. I wasn't around that early, and actually didn't make use of the TCP/IP stack when I started using Linux. Network connectivity around here was way to expensive back then (especially considering I was still in school)
The very first paragraph of his page says that the Windows CE source code was released under a Shared Source license.
And points to a new page that deals with the specifics of the WinCE license, which happens to be somewhat different (and closer to acceptable) than their original "shared source" announcement.
The sentence you're referring to clearly states
The first "Shared Source" code, Windows CE, has been released, and the license is slightly different from what the initial announcement made it look like. You can find a more detailed comment on the Windows CE Source License here..
I've left the comments on the original announcement of "shared source" unchanged because I presume that any "shared source" code that does not belong to an End-of-lifed product like CE will be released under the original terms.
It's what the initial announcement of "shared source" was like.
The WinCE license happens to be a bit different and more open - precisely because of this, I've added a comment about it on the top of the page, leaving the rest of it intact because I assume further "shared source" code will fall under the terms from the original announcement (this is actually explained on shared-source.com/wince.html).
WinCE is an end-of-lifed product, so it makes sense for them to release it under a slightly more sane license.
I'm quite sure that if their cashcows (Windows, Office) become "Shared Source" at all, they'll be released under the original terms, that's why I didn't change the comment on the original announcement.
Well, I was thinking more along the lines of people implying that if you use a GPLed editor to write your code, you have to place the code under the GPL. I've heard some people actually making that claim, so I thought it was important to mention that it's not the case.
Exactly - KDE has set up usability.kde.org and the kde-usability@kde.org mailing list (subscribe by sending a message to kde-usability-request@kde.org with "subscribe" in the subject) just for that purpose.
7.2 includes KDE 2.2 and GNOME 1.4 - both of them make life easier for new users.
7.2 includes more packages than any of the previous releases, so chances you'll actually have to compile something on your own are lower.
File permissions etc. are still there (and will stay) - but they're not really complicated once you've understood them. Basically, a file can be read, written and executed (think of the third as renaming a file from test to test.exe on that other operating system - it's done differently, but the effect is pretty much the same) - each of the operations can be allowed or denied. The file managers in KDE and GNOME give you a GUI frontend to changing permissions, so you don't need to remember commands like "chmod o+rw test" or "chmod 4777/bin/sh".
Try it, and let me know if you're seeing any usability problems - I'd like to fix them, but noticing them after you've used Linux for 10 years is quite tricky.;)
Argh, you caught us! Of course, 7.2 is actually still 1.0, just with a higher version number so people with fat net connections can brag about having more current stuff.
Why RedHat continues to support "gcc-2.96x" is beyond me
We don't want to break binary compatibility between to minor releases, and we need a stable compiler. 3.0 isn't one yet. Try compiling KDE (from CVS) with it, and you'll see.
Almost all of the improvements you listed are already in 2.96, by the way - in fact, they're the reasons we've decided to go with 2.96 rather than 2.95.x in 7.0.
There are 2 reasons why we're still using 2.96 even though 3.0 has been released.
The first is binary compatibility - gcc 3.0 is not binary compatible with anything else, and we don't break binary compatibility between minor releases.
The second is that 2.96 is way more stable than the 3.0 release (though the current 3.0 branch in CVS works somewhat better). If you've ever tried compiling KDE with gcc 3.0, you'll know what I mean.
I don't think you can come up with any program that uses correct code and doesn't work with gcc 2.96 - if you can, report it so we can fix it. If you can't, don't complain.
The final will include KDE 2.2 and a proper compiler (namely 2.96;) ).
Re:For those that actually care about this stuff..
on
RedHat 7.2 Beta: Roswell
·
· Score: 3, Informative
Actually, any news about a new Redhat for Alpha?
7.1 was released, 7.2 will be. I could tell you the release date, but I'd have to kill you afterwards.;)
This happens to be my fault.
Or rather, it's because I didn't have the time to build the packages when the beta was current (if you've ever worked for a linux distributor, you know there are more important things to do a couple of days before a feature freeze...), and I don't think it makes much sense to build them now (now that the beta is pretty much obsolete).
That's precisely why I chose to put a recent CVS snapshot that should be pretty close to the 2.2 release in Roswell.
If you don't like it, send some of your spare time to bero@redhat.com.;) We haven't come up with a way to work more than 24 hours a day, but I'll keep trying.;)
echo Server: Microsoft IIS/5.0
echo Content-Type: text/html
echo
echo <html><title>Server overloaded</title>
echo <body bgcolor="#0000FF">
echo <font face="Courier, Courier New, Fixed">
echo IIS.EXE caused a general protection fault in
echo module BLUESCREEN.DLL at 0123:45F00F00
# Yes, I know it's not exactly clean HTML
# It'll work in almost all browsers though, and
# they DID say compressed...
Call me pessimist, but I think it's yet another
"Microsoft attempts to buy out Linux" story. They'll
help Mono until.NET is widely adapted, at that time,
they drop any support for non-Microsoft OSes and add
proprietary undocumented functions, just like they
always did -- and if you intend to continue using
.net stuff, you have to "upgrade" to Windows.
I wonder where Ximian fits in though - IMO they either don't realize what Microsoft is up to, or they're trying to be bought out by Microsoft to salvage their company financially.
In any case, I'd recommend to avoid.net and Mono wherever possible, using it just where there's no alternative (just like we're using wine for some applications now).
Actually, I don't think Microsoft is coming around.
Quite the opposite: They're faking that they're playing well
until.NET is widely adapted. At that point, they'll
drop any support for.NET on non-Windows platforms,
add proprietary undocumented extensions, and force
everyone to go Windows.
If anyone at Ximian reads this, please don't fall for it,
unless you intend to be bought out by Microsoft and
do Windows from then on.
Am I the only one to think that an Open Source project is not the best way to learn programming?
Probably.;)
An Open Source project is the ideal place to start because you can look at what others have done.
You're writing KHelloWorld and don't know how to open a window? Just look at a simple other KDE application to see how they did it.
And, of course, you'll get help from the people on the mailing lists.
Of course, nobody is suggesting you start by joining kde-core-devel and rewriting the IPC subsystem in kdelibs.;)
Start your own project - something simple (maybe displaying your user ID in a window or such) that can be extended as you learn more features.
Slashdot Mirror
If software is to be free, then who can we expect to write it.
Someone who needs it - most free software projects have started out by someone deciding he needs something for himself and just coding it up.
No. I wasn't around that early, and actually didn't make use of the TCP/IP stack when I started using Linux. Network connectivity around here was way to expensive back then (especially considering I was still in school)
The very first paragraph of his page says that the Windows CE source code was released under a Shared Source license.
And points to a new page that deals with the specifics of the WinCE license, which happens to be somewhat different (and closer to acceptable) than their original "shared source" announcement.
The sentence you're referring to clearly states
The first "Shared Source" code, Windows CE, has been released, and the license is slightly different from what the initial announcement made it look like. You can find a more detailed comment on the Windows CE Source License here..
I've left the comments on the original announcement of "shared source" unchanged because I presume that any "shared source" code that does not belong to an End-of-lifed product like CE will be released under the original terms.
This describes what Microsoft USED to do.
It's what the initial announcement of "shared source" was like.
The WinCE license happens to be a bit different and more open - precisely because of this, I've added a comment about it on the top of the page, leaving the rest of it intact because I assume further "shared source" code will fall under the terms from the original announcement (this is actually explained on shared-source.com/wince.html).
WinCE is an end-of-lifed product, so it makes sense for them to release it under a slightly more sane license.
I'm quite sure that if their cashcows (Windows, Office) become "Shared Source" at all, they'll be released under the original terms, that's why I didn't change the comment on the original announcement.
Well, I was thinking more along the lines of people implying that if you use a GPLed editor to write your code, you have to place the code under the GPL. I've heard some people actually making that claim, so I thought it was important to mention that it's not the case.
In KDE, it's Konqueror - it's installed by default. (It's the file manager - simply right-click on a file)
Exactly - KDE has set up usability.kde.org and the kde-usability@kde.org mailing list (subscribe by sending a message to kde-usability-request@kde.org with "subscribe" in the subject) just for that purpose.
You're all very welcome to join.
7.2 includes KDE 2.2 and GNOME 1.4 - both of them make life easier for new users.
/bin/sh".
;)
7.2 includes more packages than any of the previous releases, so chances you'll actually have to compile something on your own are lower.
File permissions etc. are still there (and will stay) - but they're not really complicated once you've understood them. Basically, a file can be read, written and executed (think of the third as renaming a file from test to test.exe on that other operating system - it's done differently, but the effect is pretty much the same) - each of the operations can be allowed or denied. The file managers in KDE and GNOME give you a GUI frontend to changing permissions, so you don't need to remember commands like "chmod o+rw test" or "chmod 4777
Try it, and let me know if you're seeing any usability problems - I'd like to fix them, but noticing them after you've used Linux for 10 years is quite tricky.
Argh, you caught us! Of course, 7.2 is actually still 1.0, just with a higher version number so people with fat net connections can brag about having more current stuff.
Roswell doesn't exist either...
l
;)
It's ftp://ftp.redhat.com/pub/redhat/linux/beta/roswel
See? It's roswell!
If you're using KDE or GNOME, simply click on the floppy icon.
/mnt/floppy
If you're in text mode,
mount
Why RedHat continues to support "gcc-2.96x" is beyond me
We don't want to break binary compatibility between to minor releases, and we need a stable compiler. 3.0 isn't one yet. Try compiling KDE (from CVS) with it, and you'll see.
Almost all of the improvements you listed are already in 2.96, by the way - in fact, they're the reasons we've decided to go with 2.96 rather than 2.95.x in 7.0.
If you don't like the compiler, take a look at http://www.bero.org/gcc296.html and then fix your applications.
;) ).
There are 2 reasons why we're still using 2.96 even though 3.0 has been released.
The first is binary compatibility - gcc 3.0 is not binary compatible with anything else, and we don't break binary compatibility between minor releases.
The second is that 2.96 is way more stable than the 3.0 release (though the current 3.0 branch in CVS works somewhat better). If you've ever tried compiling KDE with gcc 3.0, you'll know what I mean.
I don't think you can come up with any program that uses correct code and doesn't work with gcc 2.96 - if you can, report it so we can fix it. If you can't, don't complain.
The final will include KDE 2.2 and a proper compiler (namely 2.96
Actually, any news about a new Redhat for Alpha?
;)
7.1 was released, 7.2 will be. I could tell you the release date, but I'd have to kill you afterwards.
This happens to be my fault.
;) We haven't come up with a way to work more than 24 hours a day, but I'll keep trying. ;)
Or rather, it's because I didn't have the time to build the packages when the beta was current (if you've ever worked for a linux distributor, you know there are more important things to do a couple of days before a feature freeze...), and I don't think it makes much sense to build them now (now that the beta is pretty much obsolete).
That's precisely why I chose to put a recent CVS snapshot that should be pretty close to the 2.2 release in Roswell.
If you don't like it, send some of your spare time to bero@redhat.com.
Seems to be another new feature of the new /. - it uses a journal filing system rather than a journaling file system. ;)
Because there's a stock trading window. If they don't sell now, they can't sell for quite a while.
IANAL, so I don't know the specifics on why.
echo Server: Microsoft IIS/5.0
echo Content-Type: text/html
echo
echo <html><title>Server overloaded</title>
echo <body bgcolor="#0000FF">
echo <font face="Courier, Courier New, Fixed">
echo IIS.EXE caused a general protection fault in
echo module BLUESCREEN.DLL at 0123:45F00F00
# Yes, I know it's not exactly clean HTML
# It'll work in almost all browsers though, and
# they DID say compressed...
Since most can handle it, you may even want to "compress" head and body statements... And, of course, leave out closing tags.
print "404 Not FoundThe requested URL was not found on this server.";
Call me pessimist, but I think it's yet another .NET is widely adapted, at that time,
.net and Mono wherever possible, using it just where there's no alternative (just like we're using wine for some applications now).
"Microsoft attempts to buy out Linux" story. They'll
help Mono until
they drop any support for non-Microsoft OSes and add
proprietary undocumented functions, just like they
always did -- and if you intend to continue using
.net stuff, you have to "upgrade" to Windows.
I wonder where Ximian fits in though - IMO they either don't realize what Microsoft is up to, or they're trying to be bought out by Microsoft to salvage their company financially.
In any case, I'd recommend to avoid
Actually, I don't think Microsoft is coming around. Quite the opposite: They're faking that they're playing well until .NET is widely adapted. At that point, they'll
drop any support for .NET on non-Windows platforms,
add proprietary undocumented extensions, and force
everyone to go Windows.
If anyone at Ximian reads this, please don't fall for it,
unless you intend to be bought out by Microsoft and
do Windows from then on.
Check out:
You'll want to start at the documentation supplied with the desktops.
For KDE/Qt, check out http://doc.trolltech.com/ and http://developer.kde.org/documentation.
If you can do C already, try taking a look at http://www.icce.rug.nl/docs/cplusplus/
It's a pretty good introduction to C++ for people who are already familiar with basic C.
Am I the only one to think that an Open Source project is not the best way to learn programming?
;)
;)
Probably.
An Open Source project is the ideal place to start because you can look at what others have done.
You're writing KHelloWorld and don't know how to open a window? Just look at a simple other KDE application to see how they did it.
And, of course, you'll get help from the people on the mailing lists.
Of course, nobody is suggesting you start by joining kde-core-devel and rewriting the IPC subsystem in kdelibs.
Start your own project - something simple (maybe displaying your user ID in a window or such) that can be extended as you learn more features.