Re:Windows XP was great, except....
on
New Red Hat Beta
·
· Score: 1, Flamebait
-Lack of EXT3 filesystem support by default: Near-neccessary for Linux dual-booters 1 of 2 valid points.
-That silly "start" menu: you never quite know where software is going to turn up, some make shortcuts on the desktop and in the menu, other programs only in the menu, some don't create any shortcuts MS doesn't pick where most stuff goes. RH does. RH's fault if the menu's don't make sense.
-No MP3 encoding support in WMP 2 of 2 valid points.
-DMA is off by default on CD-ROM drives. This is easily fixed through device manager, but for the average user, this is a hurdle to DVD playing and CD burning. Hrm, both my DVD-ROM and my CD-R/CD-RW drive seem to be the correctly supported DMA mode by default in WinXP.
-No nVidia, ATI, S3, Creative Labs, Turtle Beach, AMD, Intel, 3Com, VIA, or Matrox drivers, except very limited (no openGL, poor directX) drivers for some older devices. Uhh the default nVidia support for cards that existed at the time of release worked, but wern't super fast. ATI, S3, TB, Intel, 3COM and matrox I can't comment on. My VIA and AMD stuff workes just great ('cept for stuff released after XP). CL drivers for my live! were a bit lacking.
-These were all easily fixed if you knew what you were doing, but kept Windows XP out of the realm of being usable for average people. Or not. TROLL!
Alignment, what alignment are you talking about? Pixels don't move, they change color intensities. In this 3D LCD, its really just 2 screens designed to be seen at two different angles to be trick your eyes into believing its "3D"
Moderators, can we get a (-1) Moron?
Besides, LCDs will have 30ms response RSN, and then it won't matter. At 25ms, you have time for 40FPS, which is more than most human eyes can distinguish.
Except one problem. LCD's don't refresh at all. There is no moving dot drawing the pixels like there is on a CRT. That's why an LCD at any 'refresh' looks cleaner than an CRT at any refresh rate, when looking at a static image. Moving images LCDs have trouble with, because of the response times of the displays (the time it takes a pixel to change colors/brightness).
My grandfather may still have a copy of this, for the IBM PCjr, but not the plastic case. I was still playing that game well until the 1990's, until the PCjr failed to POST anymore.
Everyone on this board is a FUCKING ASSHOLE!
on
NWN Linux Client Delayed
·
· Score: -1, Flamebait
Yeah that's right. Bioware is providing this port out of the good of their hearts, because its something they want to do. For everyone who can't understand this, let me make it really really clear: NWN IS A WINDOWS GAME ONLY! NWN IS A WINDOWS GAME ONLY! NWN IS A WINDOWS GAME ONLY!
There will be no linux version on the shelves. Its just like Blizzard games. The Mac version comes in the box. Blizzard doesn't really know which platform you bought it for, they just see sales.
They are providing this port for us because they want to. No one has the right to piss, moan or bitch about it at all. No one also has the right to complain about their choice of sound or video toolkits either, as there were more reasons for choosing what they did then most of you could possibly understand. (Here's a hint.. its called support. My contract pays $100k a year for support contracts that usually only get used 5 times a year. Is it worth it? yes).
Gosh, if I was bioware and I saw all you people talking shit like this about me, I'd stop work on the port and tell you all to fuck-off, permamently. You all ought to be glad they're porting something at all. Would it be nice if they released a beta or something now? Yes. WOuld many people play it? Probably not, I'd rather play the full game in windows.
Place where geeky-wannabes can hang out and pretend to be 'l337'
Domain: http://www.slashdot.org/
Re:alias to 127.0.0.1 and then nothing loads at al
on
Only Thieves Block Pop-Ups
·
· Score: 4, Informative
Aliasing to many things to 127.0.0.1 isn't a very smart idea, it can break your resolver code. Better thing is to place them in your firewall with a REJECT (not block) rule.
Changing the attenna won't change the power output one bit. It will change the distance hte signal travels, due to gain increases, but not measured power. Its most likely, the power would be far less unless you're good at this stuff, due to SWR and the like. Good, directive dishes are easy to come by if you are in the know, but if not, forget. Besdies, since its class B, as long as it doesn't cause any interference, the FCC won't care much.
BTW, microwaves are 1000x more fun than HF. My dad does lots of high-end (10GHz+) micro wwork, and enjoys it far more than any HF stuff he does. Besides, its far easier to care a 20" dish than a 20' dipole any day.
Mainly, if you have window manager running as a client, it takes over from MS Windows being WM. Reall PITA, as our client software does that 'automatically'. Bastards.
Not true. MS Exchange actually implements an open spec, X.400 I believe (I'm fairly sure I'm wrong, but someone can correct). Exchange does use some proprietary hooks and stuff though that defeat the "open" aspect.
MAPI stands for Mail Application Programming Interface, and its intended as a generic interface for any program to use any provider within the 'Mail' applet of the Control Panel.
The OpenSSL holes have nothing to do with OpenBSD, they are built by a seperate team. 3rd party auditing of the source (which is what OpenBSD does for stuff it doesn't directly develop) won't find everything.
The OpenSSH hole was to be expected, and was long past due. No software is perfect, this just proves it. Face the facs, it'll happening sooner or later.
I don't see what you mean what gee-whiz hardware. Hardware support is still pretty far down on the list, and even my new system is about 80%% supported at best. Security is still the critical issues, but the development teams is humans, and humans miss things.
Flashy features? Again the same thing. The reason I use OpenBSD is because it isn't so darn flashy. That and it just runs.
Path to shame? I think the 3.0 series has been the best yet, and the most innovative. I think it will continue to be too.
Bullcrap. We just had to put in a patch to cover a buffer overflow/memory leak issue in UCX For OpenVMS. We know it caused buffer overflow issues becuase we could bomb Sybase sending it large amounts of data. Now there may be no OS-level overflows, but your statment is just ludicris. Our code is one walking buffer-overflow. Kernel != System, and just because the kernel is secure doesn't mean the system is.
Otherwise, I tend to agree, but OpenVMS is bi*ch to configure.
Re:Well, I'm waiting for a downloadable iso
on
OpenBSD 3.2 Available
·
· Score: 5, Informative
Download the sources. Burn on a CD. There you go.
IF oyu want it bootable, that's also fairly easy to pull off as well. Just have it boot to the floppy image.
Other way around. The whole point of any GNU/*anything* port, Debian or not, is to get the entire GNU toolchain running on said kernel.
The debian part would obviously be porting as much stuff as possible to run on said GNU/*anything*.
So GNU/OpenBSD would run pf but not iptables. See?
This is the one point where the GNU/*OS* thing makes sense. Though I think GNU Debian *OS*/*arch* would be better, as in GNU Debian Linux/i386 or GNU Debian OpenBSD/i386.
Slashdot Mirror
-Lack of EXT3 filesystem support by default: Near-neccessary for Linux dual-booters
1 of 2 valid points.
-That silly "start" menu: you never quite know where software is going to turn up, some make shortcuts on the desktop and in the menu, other programs only in the menu, some don't create any shortcuts
MS doesn't pick where most stuff goes. RH does. RH's fault if the menu's don't make sense.
-No MP3 encoding support in WMP
2 of 2 valid points.
-DMA is off by default on CD-ROM drives. This is easily fixed through device manager, but for the average user, this is a hurdle to DVD playing and CD burning.
Hrm, both my DVD-ROM and my CD-R/CD-RW drive seem to be the correctly supported DMA mode by default in WinXP.
-No nVidia, ATI, S3, Creative Labs, Turtle Beach, AMD, Intel, 3Com, VIA, or Matrox drivers, except very limited (no openGL, poor directX) drivers for some older devices.
Uhh the default nVidia support for cards that existed at the time of release worked, but wern't super fast. ATI, S3, TB, Intel, 3COM and matrox I can't comment on. My VIA and AMD stuff workes just great ('cept for stuff released after XP). CL drivers for my live! were a bit lacking.
-These were all easily fixed if you knew what you were doing, but kept Windows XP out of the realm of being usable for average people.
Or not. TROLL!
Alignment, what alignment are you talking about? Pixels don't move, they change color intensities. In this 3D LCD, its really just 2 screens designed to be seen at two different angles to be trick your eyes into believing its "3D"
Moderators, can we get a (-1) Moron?
Besides, LCDs will have 30ms response RSN, and then it won't matter. At 25ms, you have time for 40FPS, which is more than most human eyes can distinguish.
Except one problem. LCD's don't refresh at all. There is no moving dot drawing the pixels like there is on a CRT. That's why an LCD at any 'refresh' looks cleaner than an CRT at any refresh rate, when looking at a static image. Moving images LCDs have trouble with, because of the response times of the displays (the time it takes a pixel to change colors/brightness).
Where's my -1 (Moron)?
MAD FORK BOMB!
My grandfather may still have a copy of this, for the IBM PCjr, but not the plastic case. I was still playing that game well until the 1990's, until the PCjr failed to POST anymore.
Yeah that's right.
Bioware is providing this port out of the good of their hearts, because its something they want to do.
For everyone who can't understand this, let me make it really really clear:
NWN IS A WINDOWS GAME ONLY!
NWN IS A WINDOWS GAME ONLY!
NWN IS A WINDOWS GAME ONLY!
There will be no linux version on the shelves. Its just like Blizzard games. The Mac version comes in the box. Blizzard doesn't really know which platform you bought it for, they just see sales.
They are providing this port for us because they want to. No one has the right to piss, moan or bitch about it at all. No one also has the right to complain about their choice of sound or video toolkits either, as there were more reasons for choosing what they did then most of you could possibly understand. (Here's a hint.. its called support. My contract pays $100k a year for support contracts that usually only get used 5 times a year. Is it worth it? yes).
Gosh, if I was bioware and I saw all you people talking shit like this about me, I'd stop work on the port and tell you all to fuck-off, permamently. You all ought to be glad they're porting something at all. Would it be nice if they released a beta or something now? Yes. WOuld many people play it? Probably not, I'd rather play the full game in windows.
All of you people really need to go piss off
Oh come on... throw me a frickin' phone here!
Place where geeky-wannabes can hang out and pretend to be 'l337'
Domain: http://www.slashdot.org/
Aliasing to many things to 127.0.0.1 isn't a very smart idea, it can break your resolver code.
Better thing is to place them in your firewall with a REJECT (not block) rule.
I'd hit it! (And no, its not a goatse.cx link or anything...)
Changing the attenna won't change the power output one bit. It will change the distance hte signal travels, due to gain increases, but not measured power. Its most likely, the power would be far less unless you're good at this stuff, due to SWR and the like. Good, directive dishes are easy to come by if you are in the know, but if not, forget. Besdies, since its class B, as long as it doesn't cause any interference, the FCC won't care much.
BTW, microwaves are 1000x more fun than HF. My dad does lots of high-end (10GHz+) micro wwork, and enjoys it far more than any HF stuff he does. Besides, its far easier to care a 20" dish than a 20' dipole any day.
If you actually think anything that comes from behind the counter is good for you, you're insane.
In all reality, you're not gonna really get thinner from eating Subway. The only way is to--
WORK YOUR FAT ASS!
I should know, I used to work there.
However, Exceed in rootless mode isn't perfect.
Mainly, if you have window manager running as a client, it takes over from MS Windows being WM. Reall PITA, as our client software does that 'automatically'. Bastards.
I'm assuming the towers are a good-bit up. I of course don't read articles, only TOMA (troll out of my ass).
Earth horizon limitation would be more like 300 miles. I know people who've hit that problem talking at 24GHz.
Beat that!
LIFT! ROCK BIG! FOOD GOOD!
OOG! OOG! OOG!
its to beat the stupid lameness filter. really it is. stupid slashdot
Will I still get porn ads when I search for porn?
But if you control the server as well (I'm assuming its like one at home), then you can go home and tell it to run on port 23.
Just run an SSH server on port 23 instead of port 22. That's what I do. Try the -p option.
Until some idiot accidently embeds the wrong figure within his PowerPoint presentation.
At the board meeting:
"As you can see in this full-page figure..."
"Well, something about that figure is certainly full..."
Not true. MS Exchange actually implements an open spec, X.400 I believe (I'm fairly sure I'm wrong, but someone can correct). Exchange does use some proprietary hooks and stuff though that defeat the "open" aspect.
MAPI stands for Mail Application Programming Interface, and its intended as a generic interface for any program to use any provider within the 'Mail' applet of the Control Panel.
The OpenSSL holes have nothing to do with OpenBSD, they are built by a seperate team. 3rd party auditing of the source (which is what OpenBSD does for stuff it doesn't directly develop) won't find everything.
The OpenSSH hole was to be expected, and was long past due. No software is perfect, this just proves it. Face the facs, it'll happening sooner or later.
I don't see what you mean what gee-whiz hardware. Hardware support is still pretty far down on the list, and even my new system is about 80%% supported at best. Security is still the critical issues, but the development teams is humans, and humans miss things.
Flashy features? Again the same thing. The reason I use OpenBSD is because it isn't so darn flashy. That and it just runs.
Path to shame? I think the 3.0 series has been the best yet, and the most innovative. I think it will continue to be too.
Bullcrap. We just had to put in a patch to cover a buffer overflow/memory leak issue in UCX For OpenVMS. We know it caused buffer overflow issues becuase we could bomb Sybase sending it large amounts of data. Now there may be no OS-level overflows, but your statment is just ludicris. Our code is one walking buffer-overflow. Kernel != System, and just because the kernel is secure doesn't mean the system is.
Otherwise, I tend to agree, but OpenVMS is bi*ch to configure.
Download the sources. Burn on a CD. There you go.
IF oyu want it bootable, that's also fairly easy to pull off as well. Just have it boot to the floppy image.
Otherwise, buy a CD.. we need the money.
Other way around. The whole point of any GNU/*anything* port, Debian or not, is to get the entire GNU toolchain running on said kernel.
The debian part would obviously be porting as much stuff as possible to run on said GNU/*anything*.
So GNU/OpenBSD would run pf but not iptables. See?
This is the one point where the GNU/*OS* thing makes sense. Though I think GNU Debian *OS*/*arch* would be better, as in GNU Debian Linux/i386 or GNU Debian OpenBSD/i386.