It's called running ~arch. It's the only way to fly. ACCEPT_KEYWORDS="amd64 ~amd64" in make.conf in my case. Lots of goodies available without having to fiddle with package.keywords including xorg 7.0 for a while now.
I use a router but I can see why other users won't. For one, my ISP absolutely refuses to provide support to any user who uses a router. Second they don't tell you directly the information you need to configure the router, they give you a Windows program that sets automatically sets up your computer for their service.
If they don't understand how to set up a firewall properly, they probably don't know how to set up PPPOE on their router without even being given the proper information by their ISP.
Yes, of course. I was just making a comment about the dillution of the term Beta. Most people are just treating it like production software now. Then the parent to my first post suggested calling it Alpha instead of calling it Beta. My post was saying that people shouldn't do that because it just makes the word Beta a meaningless corporate buzzword by stripping it of it's original intended meaning.
Then Alpha would eventually be the new and hip Beta. If we constantly adapt the meaning of the words, they effectively become meaningless. If it is Alpha call it Alpha; if it is Beta call it Beta but if it Beta don't call it Alpha.
I wouldn't say they are fine normally when they advertise features that they know themselves dont work. For me UPNP didn't work on my router so I called them up and they said it wasn't implemented properly yet even though they advertised it as a feature. The next firmware upgrade let UPNP work some of the time but broke port forwarding so, again, I called them up and they said it was a KNOWN problem that port forwarding doesn't work properly in the new firmware. Then on my wireless card, the board itself does not work with motherboards with VIA chipsets and is a KNOWN problem yet they still refuse to provide refunds.
So, in conclusion, no, D-Link is NOT "fine normally". My problems along with this new NTP debacle is enough to show this.
I have never once had a good piece of D-Link hardware. I bought both the DI-624 wireless router and the DWL-G520 PCI wireless card. First up the router didn't do UPNP properly; it simply did not work. A call to tech support told me to upgrade the firmware because they knew that UPNP simply didn't work. After the firmware upgrade, port forwarding didn't work at all either. No solution for the router yet. As for the wireless card. After installing it, my system would completely hardlock after about 5 minutes of use. I called D-Link tech support and had to deal with all the questions for clueless people such as "Do you have the drivers?" and "Is it plugged in right?". After being elevated two or three tiers of tech suport, I was finally able to get an RMA. I sent the card to D-link and waited a week or so for my new card. I plug in the new card and what happens? Same deal! Hardlock in 5 minutes of use! Now I have to wade through tech support all over again and end up getting another RMA. Wait another week; new card makes not one lick of difference. So I decide, I will just return the bugger to the store. The store wouldn't take it back because it has been 30 days since I baught the card! 30 days of tech support and RMAs. I call D-Link once more. This time I get to top level tech support and the guy said "Oh yeah, that card doesn't work with certain VIA chipsets, sorry.". I am quite annoyed because it says nothing of the sort on the box of the card. So I politely ask that since the card doesnt work as advertised if I could have a refund. He said "Oh no, we can't do that it is against our policy.". He then offered me an 802.11b card for a $15 administration fee.
Sounds to me like you just about summed up SDL pretty well...
And the statement about multiple libraries? boo hoo, is it too much of a hassle to type -lGL -lSDL?
The article compared fancy physics effects on the CPU at ~6fps and fancy physics effects on the GPU at ~60fps. This is completely understandable. It does nothing for current games and you most definitely will not see framerates of 600.
Did you RTFA? (this is Slashdot, stupid question) This is what the whole purpose of EncFS is, you don't need to pre-allocate a set amount of disk space.
I use encfs every day on my ~amd64 Gentoo system with absolutely no problems whatsoever. And secondly, how on earth did you corrupt a partition using encfs? Encfs is a layer on top of an existing filesystem. Methinks you may have tried using it a little... strangely.
Extra features? Not likely considering that, in most cases, the feature presentation itself barely fits on the disc. I see extra features gettign the shaft as far as HD-DVD is concerned unless 'every' release is 2-disc.
Apache does not fork a new process for each request in Windows, it actually just creates a new thread. (Source) Not that I would use it in Windows anyways though.
I was refering to the original script that used `ls *.jpg` instead of simply *.jpg. The original script will choke on images with a space in the file name.
Slashdot Mirror
This statement would hold water if MS didn't wait an eternity to release an OS.
When you change the statement to "Try a version of Windows less than one version old please." the argument starts to break down...
Tag this article gentoodiditfirst. I saw this in gentoo long ago.
They just want to make sure you become a properly informed citizen from a reliable and unbiased source!
It's in Gentoo; I have been using it for a few days...
I had the same problem with video not showing in Opera even with version 7 of Flash. So I don't think this breakage is version 9 specific.
My old hardware doesn't have any OpenGL support.
If it tried to use OpenGL it would end up using the software implementation thus hosing the CPU.
Dude, sesame seeds.
It's called running ~arch. It's the only way to fly. ACCEPT_KEYWORDS="amd64 ~amd64" in make.conf in my case. Lots of goodies available without having to fiddle with package.keywords including xorg 7.0 for a while now.
I am Canadian and even I know this isn't ironic. This my friend is called S-A-R-C-A-S-M.
I use a router but I can see why other users won't. For one, my ISP absolutely refuses to provide support to any user who uses a router. Second they don't tell you directly the information you need to configure the router, they give you a Windows program that sets automatically sets up your computer for their service.
If they don't understand how to set up a firewall properly, they probably don't know how to set up PPPOE on their router without even being given the proper information by their ISP.
Yes, of course. I was just making a comment about the dillution of the term Beta. Most people are just treating it like production software now. Then the parent to my first post suggested calling it Alpha instead of calling it Beta. My post was saying that people shouldn't do that because it just makes the word Beta a meaningless corporate buzzword by stripping it of it's original intended meaning.
Then Alpha would eventually be the new and hip Beta. If we constantly adapt the meaning of the words, they effectively become meaningless. If it is Alpha call it Alpha; if it is Beta call it Beta but if it Beta don't call it Alpha.
Thats where GMF comes in.
I wouldn't say they are fine normally when they advertise features that they know themselves dont work. For me UPNP didn't work on my router so I called them up and they said it wasn't implemented properly yet even though they advertised it as a feature. The next firmware upgrade let UPNP work some of the time but broke port forwarding so, again, I called them up and they said it was a KNOWN problem that port forwarding doesn't work properly in the new firmware. Then on my wireless card, the board itself does not work with motherboards with VIA chipsets and is a KNOWN problem yet they still refuse to provide refunds.
So, in conclusion, no, D-Link is NOT "fine normally". My problems along with this new NTP debacle is enough to show this.
I have never once had a good piece of D-Link hardware. I bought both the DI-624 wireless router and the DWL-G520 PCI wireless card. First up the router didn't do UPNP properly; it simply did not work. A call to tech support told me to upgrade the firmware because they knew that UPNP simply didn't work. After the firmware upgrade, port forwarding didn't work at all either. No solution for the router yet. As for the wireless card. After installing it, my system would completely hardlock after about 5 minutes of use. I called D-Link tech support and had to deal with all the questions for clueless people such as "Do you have the drivers?" and "Is it plugged in right?". After being elevated two or three tiers of tech suport, I was finally able to get an RMA. I sent the card to D-link and waited a week or so for my new card. I plug in the new card and what happens? Same deal! Hardlock in 5 minutes of use! Now I have to wade through tech support all over again and end up getting another RMA. Wait another week; new card makes not one lick of difference. So I decide, I will just return the bugger to the store. The store wouldn't take it back because it has been 30 days since I baught the card! 30 days of tech support and RMAs. I call D-Link once more. This time I get to top level tech support and the guy said "Oh yeah, that card doesn't work with certain VIA chipsets, sorry.". I am quite annoyed because it says nothing of the sort on the box of the card. So I politely ask that since the card doesnt work as advertised if I could have a refund. He said "Oh no, we can't do that it is against our policy.". He then offered me an 802.11b card for a $15 administration fee.
Umm... MS _did_ lisence DOS to IBM. The GP was being sarcastic.
Except he mentions XGL and AIGLX as doing the same thing in the article...
Sounds to me like you just about summed up SDL pretty well...
And the statement about multiple libraries? boo hoo, is it too much of a hassle to type -lGL -lSDL?
The article compared fancy physics effects on the CPU at ~6fps and fancy physics effects on the GPU at ~60fps. This is completely understandable. It does nothing for current games and you most definitely will not see framerates of 600.
Did you RTFA? (this is Slashdot, stupid question) This is what the whole purpose of EncFS is, you don't need to pre-allocate a set amount of disk space.
I use encfs every day on my ~amd64 Gentoo system with absolutely no problems whatsoever. And secondly, how on earth did you corrupt a partition using encfs? Encfs is a layer on top of an existing filesystem. Methinks you may have tried using it a little... strangely.
Extra features? Not likely considering that, in most cases, the feature presentation itself barely fits on the disc. I see extra features gettign the shaft as far as HD-DVD is concerned unless 'every' release is 2-disc.
Apache does not fork a new process for each request in Windows, it actually just creates a new thread. (Source) Not that I would use it in Windows anyways though.
MacOS - OphoneX
Windows - Netmeeting
As for solaris, I believe it will run Ekiga/Gnomemeeting itself anyways (guessing but very probable)
I was refering to the original script that used `ls *.jpg` instead of simply *.jpg. The original script will choke on images with a space in the file name.