Granted, it's a third person shooter, but the new "Return to Castle wolfenstein" game requires some amount of strategy, for the allies at least. Rather than they typical CTF game, you (as the allies) are required to have different types of players (Engineers, Lieutenants, Medics, Soldiers) in order to actually accomplish your objective. Also, you have to coordinate with the rest of your team, both who will be each of the characters, and getting multiple people to attack the objective at the same time. Justa though.
So did they decided to continue including FreeBSD as a supported platform for Gnome . . . or did they get us yet another gnome release where all the parts wont build/run on all the supported systems . . (eg. Nautilus, Evolution, etc.)
I haven't had much chance to play with OS X (disappointing), but all the previous Mac's I've played with have had it set that "Stuffit" (like winzip) is launched automatically for the.hqx file so they're auto unzipped onto your desktop. didn't matter what browser you were using, that's just the way it was done. Probably just something that got overlooked in the MacOS to FreeBSD core transition . . .
"Firewire" is also a term coined by apple for stuff they started and pushed . . . seems to me the mouse would be yet another thing, and the GUI (you could argue xerox), they've all now spread rather widely.
Apple may not be a mega-giant . . but it seems they've got it where it counts . . .
Right now the ports tree is not akin to any of the Linux distrobution models.
FreeBSD (as w/ other BSD) has the advantage of having a single distribution, so packages listed in ports can contain distro specific patches. Hence, all the work going into FreeBSD weather it be the Base system or the apps is compounded togeter in a central repository.
Linux is not so lucky. The different linux distibutions all have different file heirarchys (yah, there are "standards" . . but that doesnt mean they're followed). Each distribution also has it's own package distribution method. This is a problem for ports.
On my FreeBSD system, ports allows me to grap the source, add my own optomization and other compile/configure time flags, and have the perfect package. It doesn't just randmly install the stuff, it packages it up first (see pkg-plist file), and then installs it. This is great, because weather you choose to use the binary package, or the port, there's no dependency problems.
If you install the Linux-Ports on your Debian/Redhat/Mandrake system, and install something, and later try to install an official package, your going to have dependency problems. You'll be forced to install the "official" version of the program, and you lose the advantage of ports.
Even if the Linux-Ports stuff was able to detect your distro, build the appropriate type of package, and then install it, you've strayed from the central distro chain. Debian (apt), RedHat (up2date), and Mandrake (I dunno what it's called) have their own centralized package systems, and will detect that your package differs from the latest one on the server. Your ports package gets overwritten, and your screwed again.
Ports would be great for Linux, but I dont think it will happen unless some distro decides to add it to their standard distro . . . Long live FreeBSD.
Slashdot Mirror
Granted, it's a third person shooter, but the new "Return to Castle wolfenstein" game requires some amount of strategy, for the allies at least. Rather than they typical CTF game, you (as the allies) are required to have different types of players (Engineers, Lieutenants, Medics, Soldiers) in order to actually accomplish your objective. Also, you have to coordinate with the rest of your team, both who will be each of the characters, and getting multiple people to attack the objective at the same time. Justa though.
Dano
Question . .
So did they decided to continue including FreeBSD as a supported platform for Gnome . . . or did they get us yet another gnome release where all the parts wont build/run on all the supported systems . . (eg. Nautilus, Evolution, etc.)
I haven't had much chance to play with OS X (disappointing), but all the previous Mac's I've played with have had it set that "Stuffit" (like winzip) is launched automatically for the .hqx file so they're auto unzipped onto your desktop. didn't matter what browser you were using, that's just the way it was done. Probably just something that got overlooked in the MacOS to FreeBSD core transition . . .
Dan
Great price for an apparently awesome board, but I dont really wanna pay the extra for the Registered Ram . . .
:)
Looks like I've now got something to save my paychecks for
"Firewire" is also a term coined by apple for stuff they started and pushed . . . seems to me the mouse would be yet another thing, and the GUI (you could argue xerox), they've all now spread rather widely. Apple may not be a mega-giant . . but it seems they've got it where it counts . . .
Right now the ports tree is not akin to any of the Linux distrobution models.
FreeBSD (as w/ other BSD) has the advantage of having a single distribution, so packages listed in ports can contain distro specific patches. Hence, all the work going into FreeBSD weather it be the Base system or the apps is compounded togeter in a central repository.
Linux is not so lucky. The different linux distibutions all have different file heirarchys (yah, there are "standards" . . but that doesnt mean they're followed). Each distribution also has it's own package distribution method. This is a problem for ports.
On my FreeBSD system, ports allows me to grap the source, add my own optomization and other compile/configure time flags, and have the perfect package. It doesn't just randmly install the stuff, it packages it up first (see pkg-plist file), and then installs it. This is great, because weather you choose to use the binary package, or the port, there's no dependency problems.
If you install the Linux-Ports on your Debian/Redhat/Mandrake system, and install something, and later try to install an official package, your going to have dependency problems. You'll be forced to install the "official" version of the program, and you lose the advantage of ports.
Even if the Linux-Ports stuff was able to detect your distro, build the appropriate type of package, and then install it, you've strayed from the central distro chain. Debian (apt), RedHat (up2date), and Mandrake (I dunno what it's called) have their own centralized package systems, and will detect that your package differs from the latest one on the server. Your ports package gets overwritten, and your screwed again.
Ports would be great for Linux, but I dont think it will happen unless some distro decides to add it to their standard distro . . . Long live FreeBSD.