...except there are legal ways of buying and downloading music. See iTMS for one often-used example (although it's not available where I live, and uses DRM, but you didn't mention either of these points).
The BSDs all keep the system under revision control; all the free BSDs
use CVS.
Revision control (in extremely brief) is a process by which editing a
program means checking out a file or group of files, making the changes,
then checking in the new versions, along with a message describing the
change.
A full history of all changes is kept in the revision control system, so
you can view a history of the changes, check out an old version, look at
the differences between arbitrary versions, etc.
All the BSDs provide public access to their CVS repositories in one way
or another; generally through anonymous CVS, or CVSup checkout or
mirroring, or often both.
That means that, as a user, you can see exactly what changes happened
when, who did them, and why they did them.
You can also always get your hands on the latest changes (within a few
hours, anyway, depending on mirroring strategies).
All of the free BSDs have mailing lists that you can subscribe to and
see the changes as they're made.
In fact, they all have web frontends as well; you can poke around
FreeBSD's entire source tree online at
http://cvsweb.freebsd.org/src/,
and see all the history of every file.
Linux, historically, hasn't used any version control for the kernel.
I don't have exact data at my fingertips here, but I believe it was
somewhere in mid-2.4 days that the kernel began being kept in a public
BitKeeper repository.
Many of the other utilities use revision control, but since they're all
developed separately, there isn't any central place you can go to to
look through the changes.
So it's sometimes hard to get a historic picture of even any one part;
to so do for a whole distribution is practically impossible.
This leads to a lot of differences.
In a very real sense, BSD systems are constantly developed; I can always
update my system to the absolute latest code, irrespective of
"releases".
In Linux, that doesn't really have as much meaning, because the release
process is very different.
I think the most appropriate verb for a Linux release is "assembled".
A Linux release is assembled from version A.B of this program, plus
version C.D of this program, plus version E.F of this program... all
together with version X.Y.Z of the Linux kernel.
In BSD, however, since the pieces are all developed together, the verb
"cut" makes a lot more sense; a release is "cut" at a certain time.
Linux releases kernels in two parallel lines (well, often more than 2,
but we're simplifying); a version with an odd minor release number, as a
"development" version, and a version with an even minor release number,
as a "production" version.
The BSDs also have "development" and "production" tracks, but they're
handled rather differently.
CVS, like most version control systems, has the concept of "branches".
It's easy to understand, but somewhat difficult to explain.
Basically, when you "branch" a file or a set of files (or a whole
directory tree), you create a new version of the file which exists in
parallel with the primary version.
When you make changes to the primary version, it doesn't affect the
branched version.
And you can make changes to the branched version without affecting the
primary.
In FreeBSD, there's usually 2 active development lines; one called
"-CURRENT", which is the development version, and the other called
"-STABLE", which is the production version.
Both, of course, are under development, and both have some attempt to be
made to keep them usable.
-STABLE, as a rule, gets bug and security fixes, but only gets new
features and such that are well tested, usually by a stint in -CURRENT
first.
-CURRENT gets new features, big architectural changes, and all those
sorts of new development stuff.
It should be noted that the naming of the branches doesn't necessarily
mean what it seems to; while -STABLE usually is "stable" as in
Unlike Russia that has flooded all sources of media with advertisements stating that piracy is persecuted by law and tries very hard to fight with the sellers, the Ukraine is a haven for the illegal media industry. Here you will find stands selling all sorts of programs, music, movies, games at any subway station, along with massive markets devoted only to this industry.
Most people I know. Then again, who the hell calls a tissue a Kleenex? A photocopy a Xerox? Never heard the latter two used, except once in Calvin and Hobbes where it confused me...
Chapest Vagr nline! http://mNIbEvrjE2LUpKe8uHtv6QdhqHIq88nvW8HAB7Tf7.n ewzb.com/d12/index.php?id=d11
Tp 5 Reasons: Csts 5$ less per pll from nline pharmacies Get 1_day shipping. Recieve your rdr next day Bst up your sex life. Vagr wrks! Stay rck hard like yu use to Lst ll night with Vagr **C**L**I**C**K*** HR TO S MR INFRMTIN! http://D7volDT14l5Uzjih2Kma7T6fyFNFy.newzb.com/d12/index.php?id=d11
I'm not a *BSD expert (I use Linux), but anyway...
1) People who want to use it I guess; I've seen quite a few Web servers running it. 2) BSD licence. Basically do what you want with it, sell it in binary form, whatever, as long as you don't try and misrepresent the original author(s). 3) Not sure... 4) There are different BSDs, yes, e.g. FreeBSD, NetBSD, OpenBSD etc. 5) Not sure, again. Although Hotmail used to run on *BSD, FWIW 6) With NetBSD, most platforms. 7) No idea what your circumstances are...
Hey, why not go international and attempt to get licence money out of the Beagle 2 people - their workstation for sending/recieving data to/from Beagle 2 runs Linux... Hey, the workstation even runs Spacecraft Control Operating System (SCOS) - clearly taken from SCO's name!
/me awaits the trolls about how Linux can't cope with getting signals from outer space, so isn't ready for the desktop.
Does Lego actually have a plural? I'd say Lego bricks, or pieces of Lego. A lot like chewing gum, you don't say "can I have a gum", or "can I have some gums"?
You already can, with a number of ports to Windows. See the 3DRealms forum on the Duke 3D source for a load of topics/links about the source release and ports (I don't have Duke3D and don't use Windows so I can't recommend one, and I know it was meant as a joke).
Slashdot Mirror
...except there are legal ways of buying and downloading music. See iTMS for one often-used example (although it's not available where I live, and uses DRM, but you didn't mention either of these points).
I assume you mean the person who wrote the article - I just pasted it...
The BSDs all keep the system under revision control; all the free BSDs use CVS. Revision control (in extremely brief) is a process by which editing a program means checking out a file or group of files, making the changes, then checking in the new versions, along with a message describing the change. A full history of all changes is kept in the revision control system, so you can view a history of the changes, check out an old version, look at the differences between arbitrary versions, etc.
All the BSDs provide public access to their CVS repositories in one way or another; generally through anonymous CVS, or CVSup checkout or mirroring, or often both. That means that, as a user, you can see exactly what changes happened when, who did them, and why they did them. You can also always get your hands on the latest changes (within a few hours, anyway, depending on mirroring strategies). All of the free BSDs have mailing lists that you can subscribe to and see the changes as they're made. In fact, they all have web frontends as well; you can poke around FreeBSD's entire source tree online at http://cvsweb.freebsd.org/src/, and see all the history of every file.
Linux, historically, hasn't used any version control for the kernel. I don't have exact data at my fingertips here, but I believe it was somewhere in mid-2.4 days that the kernel began being kept in a public BitKeeper repository. Many of the other utilities use revision control, but since they're all developed separately, there isn't any central place you can go to to look through the changes. So it's sometimes hard to get a historic picture of even any one part; to so do for a whole distribution is practically impossible.
This leads to a lot of differences. In a very real sense, BSD systems are constantly developed; I can always update my system to the absolute latest code, irrespective of "releases". In Linux, that doesn't really have as much meaning, because the release process is very different. I think the most appropriate verb for a Linux release is "assembled". A Linux release is assembled from version A.B of this program, plus version C.D of this program, plus version E.F of this program... all together with version X.Y.Z of the Linux kernel. In BSD, however, since the pieces are all developed together, the verb "cut" makes a lot more sense; a release is "cut" at a certain time.
Linux releases kernels in two parallel lines (well, often more than 2, but we're simplifying); a version with an odd minor release number, as a "development" version, and a version with an even minor release number, as a "production" version. The BSDs also have "development" and "production" tracks, but they're handled rather differently.
CVS, like most version control systems, has the concept of "branches". It's easy to understand, but somewhat difficult to explain. Basically, when you "branch" a file or a set of files (or a whole directory tree), you create a new version of the file which exists in parallel with the primary version. When you make changes to the primary version, it doesn't affect the branched version. And you can make changes to the branched version without affecting the primary.
In FreeBSD, there's usually 2 active development lines; one called "-CURRENT", which is the development version, and the other called "-STABLE", which is the production version. Both, of course, are under development, and both have some attempt to be made to keep them usable. -STABLE, as a rule, gets bug and security fixes, but only gets new features and such that are well tested, usually by a stint in -CURRENT first. -CURRENT gets new features, big architectural changes, and all those sorts of new development stuff. It should be noted that the naming of the branches doesn't necessarily mean what it seems to; while -STABLE usually is "stable" as in
Most people I know. Then again, who the hell calls a tissue a Kleenex? A photocopy a Xerox? Never heard the latter two used, except once in Calvin and Hobbes where it confused me...
Noooooooooooooooooooooo... :(
I used to go to the cinema in Hatfield, now it's...tainted
How many people here with the bandwidth necessary to download 400MB easily don't have BitTorrent?
I've already heard it as STFU...
Anyway, it's still better than the Critical Update Notification Tool.
Apparently not... (that's a real spam I got)
When I started downloading (before it was posted) it was slowish - 19.7KB/s. It's currently downloading at 17.3KB/s, so not that much difference...
"from the help-me-find-directions-to-p4r1s-h1l70n dept."
I'm not a *BSD expert (I use Linux), but anyway...
1) People who want to use it I guess; I've seen quite a few Web servers running it.
2) BSD licence. Basically do what you want with it, sell it in binary form, whatever, as long as you don't try and misrepresent the original author(s).
3) Not sure...
4) There are different BSDs, yes, e.g. FreeBSD, NetBSD, OpenBSD etc.
5) Not sure, again. Although Hotmail used to run on *BSD, FWIW
6) With NetBSD, most platforms.
7) No idea what your circumstances are...
Not really, they aren't trying to sell an XP 2500+ as an XP 2600+; they just changed their naming scheme.
M-S
IRC!
*cough*
You know SCO is running Apache on Linux, right?
Hey, why not go international and attempt to get licence money out of the Beagle 2 people - their workstation for sending/recieving data to/from Beagle 2 runs Linux... Hey, the workstation even runs Spacecraft Control Operating System (SCOS) - clearly taken from SCO's name!
/me awaits the trolls about how Linux can't cope with getting signals from outer space, so isn't ready for the desktop.
Does Lego actually have a plural? I'd say Lego bricks, or pieces of Lego. A lot like chewing gum, you don't say "can I have a gum", or "can I have some gums"?
You already can, with a number of ports to Windows. See the 3DRealms forum on the Duke 3D source for a load of topics/links about the source release and ports (I don't have Duke3D and don't use Windows so I can't recommend one, and I know it was meant as a joke).
Hey, so you're going to switch to it even though you don't think it'll reduce spam in any way, shape or form... Amazing!
This appears to be a straight copy/paste from this comment in one of the linked articles...
Not really, I already have excellent karma, and even if I didn't, who cares about it?
Ah, typical, it's sourceforge which has decided to slow down, not crawler.archive.org.
*sigh*
The source download is available on sourceforge.
I doubt it'll get slashdotted, but you never know...
Did you reply to the wrong post? Google Toolbar doesn't touch how IE renders pages.
I'd wait for IE to get an improved rendering engine first (note: I don't use Windows, I do have to cater for IE in HTML though...)