Some professional experience might change your tune about the approachability of open source.
You'll likely be tasked at some point on a team building a large system that has components that are closed, components that your team is writing, and open source components. Inevitably some interaction between those spheres will lead to a failing test case (or bug report). You'll be able to see inside the open source (and ask informed meaningful questions about it on the Internet), see inside your team's work and discuss it with your team, and have to trust the documentation of the closed stuff.
Your definition of which sphere has a lack of approachability will change rapidly:)
with a "peak" and "sustained" rating (e.g., 512kb peak and 56kb sustained.)
You make a slight confusion here (or make it sound confusing), what do you mean by 56kb sustained? Because if it's 56 kbit, that's dial-up speed, and I don't think anybody would be stupid enough to pay "broadband" price for dial-up speed. I wouldn't, for sure.
You don't understand how the token bucket works. It allows you to run at the peak bandwidth for a certain period of time, (the original poster suggested an extremely generous 1 hour) and if you saturate the link for that entire time only then do you get scaled back.
To do the math on the original poster's comment, your bucket would hold 225MBytes worth of tokens. If you started downloading say a redhat.iso you would go for the first hour at full speed (225MB worth), and even over that hour you would have been earning new tokens at the rate of 56Kbit/s - which is another 24MB (6.5 minutes) worth..
Pretty soon after this you run out of stored tokens and can only spend them at the rate you acquire them (56Kb/s). However, this is exactly the case you're trying to target - someone who has been saturating their link.
For shorter uses (most downloads, browsing, email etc) they complete in less than 1 hour, and you always run at the peak rate and recharge your token bucket during the interspersed idle periods without ever noticing.
The best part of this kind of scheme is that it actually encourages the provider to run with a higher peak rate. And for daily use the peak rate is what you perceive as being fast - but they can raise the peak rate safely without worrying that total bandwidth consumed will go up proportionately.
The one time linux crashed on me was the time I was trying to configure a nVidia card
So you just take your oops to linux-kernel for a little insight and lickety split.. oh, wait. It's a binary only driver - they'll tell you that the only people that can debug your formerly open source system are at nvidia.
The overall situation (If I'm not wrong) is that even though nVidia provides the drivers (and even the source)
nVidia does not provide source - they only provide closed source binary drivers.
Their source distribution contains a binary module (Module-nvkernel) and a little glue code that you can compile. This is so you can run it with your current kernel. The driver itself remains opaque.
At least Yahoo! lets you delete an account you don't want anymore . That's a rarity amongst online services. If your account isn't useful to you anymore - this is the best way to make sure they don't reset the preferences when you're not looking ever again.
http://edit.yahoo.com/config/delete_user (must be logged in)
Even if your preferred support method is a prepaid contract - the availability of open source de-monopolizes the market for providing that support. You're certainly going to get a better deal for your contract when many firms have the ability to bid on it than when just one (the original vendor) does.
Hey Bender, will the futurama references be cancelled
from the next version of slashcode too? (gotta stay current!)
/home/person>telnet slashdot.org 80
Trying 64.28.67.150...
Connected to slashdot.org.
Escape character is '^]'.
HEAD / HTTP/1.1
host: slashdot.org:80
HTTP/1.1 200 OK
Date: Wed, 13 Feb 2002 03:20:08 GMT
Server: Apache/1.3.20 (Unix) mod_perl/1.25 mod_gzip/1.3.19.1a
SLASH_LOG_DATA: shtml
X-Powered-By: Slash 2.003000
X-Fry: I'm gonna be a science fiction hero, just like Uhura, or Captain Janeway, or Xena!
Connection: close
Content-Type: text/html
In a corporate environment, pay for 1 RCE, operate that
RCE through a squid proxy with a large max cachable
object size.
proceed to operate the other N-1 RC-Classic clients through that same proxy.
Instant and seemless mirror - indeed faster than RCE. Any minor differences in installations can still be resolved automatically against the 'slow' classic server as cache misses.
Saves both you and ximian bandwidth - a win win and very use to do with already deployed tools.
DNS doesn't work instantly. Never has, never will. And with the profusion of names, it will just get slower. It's only the local caching which seems to make DNS fast.
We thought that. But it might not to be as true
as you think.
Slashdot Mirror
Some professional experience might change your tune about the approachability of open source.
You'll likely be tasked at some point on a team building a large system that has components that are closed, components that your team is writing, and open source components. Inevitably some interaction between those spheres will lead to a failing test case (or bug report). You'll be able to see inside the open source (and ask informed meaningful questions about it on the Internet), see inside your team's work and discuss it with your team, and have to trust the documentation of the closed stuff.
Your definition of which sphere has a lack of approachability will change rapidly :)
with a "peak" and "sustained" rating (e.g., 512kb peak and 56kb sustained.)
.iso you would go for the first hour at full speed (225MB worth), and even over that hour you would have been earning new tokens at the rate of 56Kbit/s - which is another 24MB (6.5 minutes) worth..
You make a slight confusion here (or make it sound confusing), what do you mean by 56kb sustained? Because if it's 56 kbit, that's dial-up speed, and I don't think anybody would be stupid enough to pay "broadband" price for dial-up speed. I wouldn't, for sure.
You don't understand how the token bucket works. It allows you to run at the peak bandwidth for a certain period of time, (the original poster suggested an extremely generous 1 hour) and if you saturate the link for that entire time only then do you get scaled back.
To do the math on the original poster's comment, your bucket would hold 225MBytes worth of tokens. If you started downloading say a redhat
Pretty soon after this you run out of stored tokens and can only spend them at the rate you acquire them (56Kb/s). However, this is exactly the case you're trying to target - someone who has been saturating their link.
For shorter uses (most downloads, browsing, email etc) they complete in less than 1 hour, and you always run at the peak rate and recharge your token bucket during the interspersed idle periods without ever noticing.
The best part of this kind of scheme is that it actually encourages the provider to run with a higher peak rate. And for daily use the peak rate is what you perceive as being fast - but they can raise the peak rate safely without worrying that total bandwidth consumed will go up proportionately.
[linux-kernel] Re: Kernel hosed or Nvidia modules?
Riddle: What do you do if you're running two closed binary modules from different companies?
nVidia does not provide source - they only provide closed source binary drivers.
Their source distribution contains a binary module (Module-nvkernel) and a little glue code that you can compile. This is so you can run it with your current kernel. The driver itself remains opaque.
At least Yahoo! lets you delete an account you don't want anymore . That's a rarity amongst online services. If your account isn't useful to you anymore - this is the best way to make sure they don't reset the preferences when you're not looking ever again.
http://edit.yahoo.com/config/delete_user (must be logged in)
Even if your preferred support method is a prepaid contract - the availability of open source de-monopolizes the market for providing that support. You're certainly going to get a better deal for your contract when many firms have the ability to bid on it than when just one (the original vendor) does.
Hey Bender, will the futurama references be cancelled
from the next version of slashcode too? (gotta stay current!)
/home/person>telnet slashdot.org 80
Trying 64.28.67.150...
Connected to slashdot.org.
Escape character is '^]'.
HEAD / HTTP/1.1
host: slashdot.org:80
HTTP/1.1 200 OK
Date: Wed, 13 Feb 2002 03:20:08 GMT
Server: Apache/1.3.20 (Unix) mod_perl/1.25 mod_gzip/1.3.19.1a
SLASH_LOG_DATA: shtml
X-Powered-By: Slash 2.003000
X-Fry: I'm gonna be a science fiction hero, just like Uhura, or Captain Janeway, or Xena!
Connection: close
Content-Type: text/html
Connection closed by foreign host.
In a corporate environment, pay for 1 RCE, operate that
RCE through a squid proxy with a large max cachable
object size.
proceed to operate the other N-1 RC-Classic clients through that same proxy.
Instant and seemless mirror - indeed faster than RCE. Any minor differences in installations can still be resolved automatically against the 'slow' classic server as cache misses.
Saves both you and ximian bandwidth - a win win and very use to do with already deployed tools.
http://nms.lcs.mit.edu/papers/dns-imw2001.html
-Patrick
probably 'strucuture and interpretation of
computer programs' by abelson and sussman...
we used it at WPI too..
tremendously good book about getting started in
programming.. it teaches a little scheme along the
way, but definitely isn't about that.
I hear WPI starts with something more traditional
like C these days.. that used to be only true for
non majors.. too bad really.