Well, not only that, but -RELEASE can refer to -CURRENT snapshots as well (such as the early 5.x releases when 5.x was still -CURRENT). Also, after a certain amount of time, -STABLE branches become errata branches. 4.x has become this. You basically come out with: "Production Release" (STABLE), "Technology Preview" (CURRENT), and "Production (Legacy) Release" (errata, a type of STABLE).
Also, there is only "one" -CURRENT, at least in terms of CVS at least. This is HEAD and the main cvs trunk, and that is where -CURRENT lives. There are no separate -CURRENT branches; when -CURRENT gets branched the branches become -STABLE or -RELEASEs. -CURRENT only gets a version number as the next upcoming "branch". The only way you can find other "CURRENTs" is by going up and down the trunk.
I had a nice "ascii" tree laid out which explained it better, but slashdot shot it down with its lame lameness filter.
Also, this is the way things are laid out today as I can see it. Releases/branches may have been done differently in the past.
The biggest reason why they changed from rh7 as default in ports to rh8 was that rh7 had an unpatched vulnerability. Redhat seems to have no interest in maintaining and updating these outdated versions, so the default had to change.
It probably wouldn't be terribly hard to get FC3 working as a base since it, like the other redhat-related releases that we have already, use rpms, which we already know how to handle. Although, I haven't tried it, so I can't tell you for definite.
Re:You better hope Google's motto is "Do No Evil"
on
Defining Google
·
· Score: 1
As a result, 90% of the world's userbase has Direct3D libs immediately-available as part of Win9x/ME/NT/2k/XP, ready-to-run.
Ah, that doesn't mean OpenGL isn't immediately available either. Games -do- use it, so there a reason for it to end up on the computer before the consumer buys it.
In fact you don't want to rely on the directx (direct3D is part of this) provided with windows anyway! Most games provided a copy of directx on their cd. This is because they probably need the latest and greatest version of directx. Most new games require directx 9.0 (or newer), but WinXP only shipped with 8.1.
Thus, the fact that directx (with direct3d) is provided with windows doesn't do you much good.
It's better than that. Sometimes the binary portion can be made to work with completely different kernels. That's how nvidia started providing drivers for FreeBSD: some people got the Linux driver working under FreeBSD, submitted the patches back and whatnot, and nvidia noticed and decided to extend to providing FreeBSD drivers as well. People have also managed to get the FreeBSD driver working with NetBSD with some limited success.
Actually, the network interface on some nforce boards works this way too. The linux binary nic driver (nvidia provides an.o file) can be compiled into a FreeBSD kernel module.
It wasn't up to me to think of that.;P For the most part, I was only around when he first got the problem, and midway through him trying to fix it with a second copy of XP.
After a few hours of him trying to pound on it, and my non-windows using self not having any idea either, I got my knoppix disk and that solved that, even if it wasn't the "right" way.
I...hope one of the things he tried was to take ownership. (I seem to remember that existing in WinNT at least, but I don't think I thought of it). Might he have been so frustrated and pissed off at Windows' sudden erratic non-booting behavior that it might have slipped his mind? I don't know.
Re:RTFM? Who does that.
on
Grokking Knoppix
·
· Score: 2, Interesting
Something similar happened to a friend of mine.
The copy WinXP on his machine decided to lose the ability to boot up properly. It would show the XP screen....and right before it would go to the login screen, it would reset itself.
Okaayyy. Well, he stuck XP on another drive to try to recover his data. XP on the second drive could see the first drive, read any of the data, except for -his- data, because his data was in "My Documents", which apparently windows will only read if it is the copy of windows it was created with. So, can't get to his data, now what?
I pulled out my trusty knoppix cd, popped it in, and we were able to recover his data.
Unfortunately, it wasn't enough to get him completely away from windows. He still uses it for games, and linux for everything else. He also acts pissed when windows is mentioned. It's a start.
...
Come to think of it, this sort of thing is what got me into FreeBSD. The machine I was using was running WinNT back in the day. It died one night to a virus or it ate itself or something.
My dad was pissed, and the computer went to his work to get fixed and I didn't have a computer for 6 months.
Needless to say, that burned me pretty bad, and a switch away from windows was an easy thing to do.
If two companies can't agree before going to court, why should the courts be used to pressure one side or the other to give in?
Change of ownership can get one of the sides to be more agreeable. IIRC, this is exactly what happened with the USL vs BSD suit. USL was bought by Novell, who decided they wanted to settle. I believe a Novell executive was quoted saying something like "Better to compete in the marketplace than the courts"
Easy there, it might not be that solid. They haven't done much testing outside of x86 and even that is flaky and/or slow for a lot of hardware (including hardware every machine has).
As I understand it a pretty large amount of testing has gone into amd64 too. A decent number of developers have amd64 boxes, and that helps a lot.
Alpha support was in 4.x, but has been going down for a while now, especially in 5.x. Port build testing on pointyhat isn't even done for Alpha anymore (according to Kris the Alphas won't even boot). Fortunately , this isn't as bad as it could be, since the Alphas are going away anyway. (and you know NetBSD will always have support for them;P )
I tried Vice City for PC, and I didn't like it. It may be because I've always been playing it on the PS2, but it just feels more natural there.
On the other hand, I feel just the opposite about Halo. When playing first person shooters a mouse just feels more natural to me. I'm pretty bad at aiming with just my thumb (tying back to GTA...this is probably why I don't like shooting as much in Vice City...fortunately Vice City was more into the whole driving thing)
Slashdot Mirror
Nevermind, phk clarified. :)
So (trying to get this straight), has the FreeBSD Foundation gotten a hold on the Sun licensing people yet (since the newsletter was posted)?
Well, not only that, but -RELEASE can refer to -CURRENT snapshots as well (such as the early 5.x releases when 5.x was still -CURRENT). Also, after a certain amount of time, -STABLE branches become errata branches. 4.x has become this. You basically come out with: "Production Release" (STABLE), "Technology Preview" (CURRENT), and "Production (Legacy) Release" (errata, a type of STABLE).
Also, there is only "one" -CURRENT, at least in terms of CVS at least. This is HEAD and the main cvs trunk, and that is where -CURRENT lives. There are no separate -CURRENT branches; when -CURRENT gets branched the branches become -STABLE or -RELEASEs. -CURRENT only gets a version number as the next upcoming "branch". The only way you can find other "CURRENTs" is by going up and down the trunk.
I had a nice "ascii" tree laid out which explained it better, but slashdot shot it down with its lame lameness filter.
Also, this is the way things are laid out today as I can see it. Releases/branches may have been done differently in the past.
The biggest reason why they changed from rh7 as default in ports to rh8 was that rh7 had an unpatched vulnerability. Redhat seems to have no interest in maintaining and updating these outdated versions, so the default had to change.
It probably wouldn't be terribly hard to get FC3 working as a base since it, like the other redhat-related releases that we have already, use rpms, which we already know how to handle. Although, I haven't tried it, so I can't tell you for definite.
I googled it (http://www.google.com/search?q=site%3Agoogle.com+ %22don't+be+evil%22) The first link says it @
http://www.google.com/governance/conduct.html
There is also http://www.google.com/corporate/tenthings.html (second link), which fits as well.
Doom3 does not use openal, and DOES use alsa, and I get 6 speaker positional sound out of it without any problems. Sounds great too :) (thanks TTimo)
ut2004 uses openal (under linux at least).
As a result, 90% of the world's userbase has Direct3D libs immediately-available as part of Win9x/ME/NT/2k/XP, ready-to-run.
Ah, that doesn't mean OpenGL isn't immediately available either. Games -do- use it, so there a reason for it to end up on the computer before the consumer buys it.
In fact you don't want to rely on the directx (direct3D is part of this) provided with windows anyway! Most games provided a copy of directx on their cd. This is because they probably need the latest and greatest version of directx. Most new games require directx 9.0 (or newer), but WinXP only shipped with 8.1.
Thus, the fact that directx (with direct3d) is provided with windows doesn't do you much good.
It's better than that. Sometimes the binary portion can be made to work with completely different kernels. That's how nvidia started providing drivers for FreeBSD: some people got the Linux driver working under FreeBSD, submitted the patches back and whatnot, and nvidia noticed and decided to extend to providing FreeBSD drivers as well. People have also managed to get the FreeBSD driver working with NetBSD with some limited success.
.o file) can be compiled into a FreeBSD kernel module.
Actually, the network interface on some nforce boards works this way too. The linux binary nic driver (nvidia provides an
It wasn't up to me to think of that. ;P For the most part, I was only around when he first got the problem, and midway through him trying to fix it with a second copy of XP.
After a few hours of him trying to pound on it, and my non-windows using self not having any idea either, I got my knoppix disk and that solved that, even if it wasn't the "right" way.
I...hope one of the things he tried was to take ownership. (I seem to remember that existing in WinNT at least, but I don't think I thought of it). Might he have been so frustrated and pissed off at Windows' sudden erratic non-booting behavior that it might have slipped his mind? I don't know.
You obviously weren't there.
Something similar happened to a friend of mine.
The copy WinXP on his machine decided to lose the ability to boot up properly. It would show the XP screen....and right before it would go to the login screen, it would reset itself.
Okaayyy. Well, he stuck XP on another drive to try to recover his data. XP on the second drive could see the first drive, read any of the data, except for -his- data, because his data was in "My Documents", which apparently windows will only read if it is the copy of windows it was created with.
So, can't get to his data, now what?
I pulled out my trusty knoppix cd, popped it in, and we were able to recover his data.
Unfortunately, it wasn't enough to get him completely away from windows. He still uses it for games, and linux for everything else. He also acts pissed when windows is mentioned. It's a start.
...
Come to think of it, this sort of thing is what got me into FreeBSD. The machine I was using was running WinNT back in the day. It died one night to a virus or it ate itself or something.
My dad was pissed, and the computer went to his work to get fixed and I didn't have a computer for 6 months.
Needless to say, that burned me pretty bad, and a switch away from windows was an easy thing to do.
Perhaps they can come with a chip fast enough to run emacs. :)
;P
Is it a chip that is somehow optimized for swapping memory?
If it is, you might have something there.
And best of all, SMART works with not just ATA, but SATA too, which is what asker seems to be asking for.
Wow, FreeSBIE must be trying for lightweight if they consider xfce4 to be heavy.
:P
I mean, if you are going to talk about heavy you have to talk about gnome or kde
There's been talk of replacing sysinstall with the dfinstaller (aka bsdinstaller).
Of course, there's been talk of replacing sysinstall for years...
Finally, the "old" interface is still very much available. It's at http://groups.google.com
Incorrect. Try to go anywhere from there and you just end up with the new interface anyway.
That's because it's the halo game series console, not xbox. ;P
If two companies can't agree before going to court, why should the courts be used to pressure one side or the other to give in?
Change of ownership can get one of the sides to be more agreeable. IIRC, this is exactly what happened with the USL vs BSD suit. USL was bought by Novell, who decided they wanted to settle. I believe a Novell executive was quoted saying something like "Better to compete in the marketplace than the courts"
It sounds like one of the problems is that there is no fix for win2k users because the patch is bundled with SP2.
and that guy who never says anything is a CIA bot.
Crap, me and too many others must be CIA bots.
I mean, really, what else is IRC for if not idling?
You're going to be using/have the same computer in 10 years?
Are you even sure you won't have to do something really stupid, like reinstall the game to get it working again?
Easy there, it might not be that solid. They haven't done much testing outside of x86 and even that is flaky and/or slow for a lot of hardware (including hardware every machine has).
As I understand it a pretty large amount of testing has gone into amd64 too. A decent number of developers have amd64 boxes, and that helps a lot.
Alpha support was in 4.x, but has been going down for a while now, especially in 5.x. Port build testing on pointyhat isn't even done for Alpha anymore (according to Kris the Alphas won't even boot). Fortunately , this isn't as bad as it could be, since the Alphas are going away anyway. (and you know NetBSD will always have support for them ;P )
...now you have a dual processor system!
I tried Vice City for PC, and I didn't like it. It may be because I've always been playing it on the PS2, but it just feels more natural there.
On the other hand, I feel just the opposite about Halo. When playing first person shooters a mouse just feels more natural to me. I'm pretty bad at aiming with just my thumb (tying back to GTA...this is probably why I don't like shooting as much in Vice City...fortunately Vice City was more into the whole driving thing)
if it was difficult to write, it should be difficult to undestand.
:P
(I wish I could remember where I read that!)
fortune?
as in...fortune the program that spits out silly quotes.