Homer: [scoffs] I know. And this perpetual motion machine she made
today is a joke! It just keeps going faster and faster. Marge: And Bart isn't doing very well either. He needs boundaries and
structure. There's something about flying a kite at night that's
so unwholesome. [looks out window]
Bart: [creepy voice] Hello, Mother dear. Marge: [closing the curtains] That's it: we have to get them back to
school. Homer: I'm with you, Marge. Lisa! Get in here.
[Lisa walks in, chuckling nervously]
In this house, we obey the laws of thermodynamics!
With proper setup, even NFS can be 'transparent and secure'. It's not the technology, it's the admins.
To a point, Billy boy is right. The users (and/or admins) need to know how to set things up in a secure manner. But this is only half the problem. The other half is having a platform that is designed with security in mind, and having tools that are properly designed as well.
I have personally setup remote file system access securely under unix. But I'm sure you don't care about that, I'm not an 'average' user.
Allowing root across networked file systems is not a great security practice. That's not the OS's fault, that's the fault of whoever setup the systems.
"Windows's security problems are related to application coding, not OS design."
Ok, where does the OS end and the application begin? We all know how Microsoft likes to incorporate things into their OS, so where is the line drawn?
That's really very interesting, considering that Charter Communications just sent us a letter saying that they were upping our bandwidth from 1.5Mbps down to 2Mbps down. Not a big leap, by any means, but they increased the cap.
Now, if only their network was operational long enough to use that bandwidth...that would be impressive...
I have at least 7 access points within detection distance of my room, which now makes me wonder how many waves pass through me from those alone...not to mention the rest of the world.
I would think that anyone who didn't want to restart an entire project like this would save state. You can never tell when there are going to be power problems, virus/worm problems, or even a stupid user that decided they needed that machine and crashed it.
I'm glad someone spent the time to study this. Next they'll tell us that those same people were concerned with copyrights when it was their own works being copied and distributed.
It takes next to no time at all to build the new kernel modules from nVidia (I don't know how many other manufacturers distribute modules this). Certainly it takes longer to build the kernel...
Also, (again, specific to nVidia) when loading the module it should warn about tainting the kernel. Last I checked, non-kernel code in the kernel doesn't help find bugs/increase stability.
I admit it's a minor irritation to have to rebuild the driver module whenever I build a kernel, but let's face it. The hardware in my desktop doesn't change. So I only rebuild a kernel when a new version is released.
I can understand it if you're using test kernels, however, in that case, your video driver is probably the least of your worries.
One of the nicest things about having a cell is that only the people I give my number to have my number. They say telemarketers wouldn't get their hands on the numbers, but how long would it take before they paid someone off or obtained the list by some other not quite proper way?
I'll just have to stop answering this phone, too...
Our cable guy asked us if we had a PC or a router...when he found out it was a Linux box playing NAT he said 'ok, I'll just use my laptop to test it then' and never installed or even gave us any CD's.
All the better for us.
Too bad half the world is less intelligent than the 'average person'.
Slashdot Mirror
Homer: [scoffs] I know. And this perpetual motion machine she made
today is a joke! It just keeps going faster and faster.
Marge: And Bart isn't doing very well either. He needs boundaries and
structure. There's something about flying a kite at night that's
so unwholesome. [looks out window]
Bart: [creepy voice] Hello, Mother dear.
Marge: [closing the curtains] That's it: we have to get them back to
school.
Homer: I'm with you, Marge. Lisa! Get in here.
[Lisa walks in, chuckling nervously]
In this house, we obey the laws of thermodynamics!
Ok, I'll just patent 1337 5p34k.
I guess it's time for me to patent 'alphanumeric symbols combined to create grammatical constructs'.
I'd better hurry, before someone else grabs it up from under my nose.
For those who want a patch...
http://minion.de/nvidia.html was updated a matter of moments ago.
Go grab the latest patch now!
True, but the x is no longer there. It was replaced with the 1. It isn't an x anymore.
...the symbology...
I believe the word you were looking for was symbolism. What is the symbolism of having only female connectors.
</movie title="Boondock Saints">
This is a repost from a while ago.
And besides, is anyone really suprised by this? It makes perfect sense, when you stop to think about it.
The kernel doesn't include stdlib.h. That would imply that it gets linked with libc somehow. Last time I checked, that doesn't happen.
With proper setup, even NFS can be 'transparent and secure'. It's not the technology, it's the admins.
To a point, Billy boy is right. The users (and/or admins) need to know how to set things up in a secure manner. But this is only half the problem. The other half is having a platform that is designed with security in mind, and having tools that are properly designed as well.
I have personally setup remote file system access securely under unix. But I'm sure you don't care about that, I'm not an 'average' user.
Allowing root across networked file systems is not a great security practice. That's not the OS's fault, that's the fault of whoever setup the systems.
"Windows's security problems are related to application coding, not OS design."
Ok, where does the OS end and the application begin? We all know how Microsoft likes to incorporate things into their OS, so where is the line drawn?
...And there is no cap on how much we can bring down, assuming that 2Mbps was saturated the entire month...
That's really very interesting, considering that Charter Communications just sent us a letter saying that they were upping our bandwidth from 1.5Mbps down to 2Mbps down. Not a big leap, by any means, but they increased the cap.
Now, if only their network was operational long enough to use that bandwidth...that would be impressive...
Sad that I never thought about that...
I have at least 7 access points within detection distance of my room, which now makes me wonder how many waves pass through me from those alone...not to mention the rest of the world.
I would think that anyone who didn't want to restart an entire project like this would save state. You can never tell when there are going to be power problems, virus/worm problems, or even a stupid user that decided they needed that machine and crashed it.
Checkpointing is your friend.
Duh.
I'm glad someone spent the time to study this. Next they'll tell us that those same people were concerned with copyrights when it was their own works being copied and distributed.
It's great that so many people have so many ideas on how to avoid recieving unwanted calls. The sit tones, caller id, etc.
Here's the real question: is there any way (besides the do-not-call lists) that can stop the barrage of annoying phone calls?
I'll agree with that.
But...
It takes next to no time at all to build the new kernel modules from nVidia (I don't know how many other manufacturers distribute modules this). Certainly it takes longer to build the kernel...
Also, (again, specific to nVidia) when loading the module it should warn about tainting the kernel. Last I checked, non-kernel code in the kernel doesn't help find bugs/increase stability.
How often do you build a kernel?
I admit it's a minor irritation to have to rebuild the driver module whenever I build a kernel, but let's face it. The hardware in my desktop doesn't change. So I only rebuild a kernel when a new version is released.
I can understand it if you're using test kernels, however, in that case, your video driver is probably the least of your worries.
One of the nicest things about having a cell is that only the people I give my number to have my number. They say telemarketers wouldn't get their hands on the numbers, but how long would it take before they paid someone off or obtained the list by some other not quite proper way?
I'll just have to stop answering this phone, too...
I must have gotten really messed up last night, cuz I'm still seeing double!
Am I the only one who felt his answers were extremely short and not entirely informative?
Usually people would put some effort into their answers, but this just seems like it was a minor thing that got blown off...
Yes, I believe it is.
And if it isn't the messaging stuff, I would think it would have to be an exploit of some other service that's running.
Does that messaging exploit go past firewalls? I highly doubt it...that sounds a bit fishy to me.
Our cable guy asked us if we had a PC or a router...when he found out it was a Linux box playing NAT he said 'ok, I'll just use my laptop to test it then' and never installed or even gave us any CD's.
All the better for us.
Too bad half the world is less intelligent than the 'average person'.
--
JB - CAE UNIX Systems Staff
A quoted string is a char *. It's replaced during compilation.
Please correct me if I'm wrong...but I'm fairly sure on this.
I dislike M$ and Windows as much as the next guy, but this story is rediculous.
Mainly, he didn't use a Windows 2000 install CD. When I used 2k on my machine, I used 1 CD, the Win2k CD, and I had 1 driver CD to switch to.
I can go from no OS to Win2k in an hour. Updated and all.
I can also go from no OS to Debian 3.0r0 in 20 minutes.
All anti-M$ bias aside, I'd still be on (almost) any linux distribution to install faster than Win2k.