"Dad, er. You know all that money you sent me? You know how I promised that it would last me the full term? Well, uh, I'm not broke *exactly*, but I'm currently restructuring. Yeah. And food would help the process, yes. I expect to be cashflow-positive by Q3 2003. "
The release notes for x86 indicate that the thing ships with 2.2.20, with an optional 2.4.x for the bleeding-edgers, with (as explanation) a catty remark about the Debian developers not considering 2.4 a 'stable' branch.
Admittedly, I prefer Debian for the work that I do mainly because of the stability. But really -- 2.4 has been utterly reliable since ~2.4.14. Isn't this just a little paranoid? C'mon, folks, the thing is solid! I mean, the VM subsystem hasn't been completely re-written in *months*!;)
Well, first of all: You should segment your network, with an old Linux box as gateway.
Whether or not you'd consider this a 'separate network' is really up to you. However, it may be that you can't do this, for technical or political (or economical) reasons. Having worked as a network admin for a small library, I understand that there a well-considered hesitance to embrace yet another chunk of technology that only one employee (and, at that,a highly mobile and long-term-unpredictable one) understands. Essentially, you want something that's drop-dead stupid to administer, so that (if, for any reason, you leave) some poor high-school schmuck who just happens to be the kid of one of the librarians stands at least even odds of being able to get it going again.
So instead, you could do something like only assign IPs within a certain 'redlisted' range, such that the important computers on the network can run some cheap-ass firewall freeware to block from those IPs. Such a solution doesn't protect everyone, but it's really fast and easy.
Alternately, you could always buy one of those $60 firewall/routers between the rest of the library's computers and the Internet, and then put the newcomers outside said firewall. Such boxes are easy to administer, and come with nice glossy manuals. Set it up like this:
[T1]
|
| [Hub for Anonymous Users]
| [Firewall/Router]
| {all the other computers}
However, in this scenario, you'll need to make sure that the firewall appliance is (a) able to handle a simple 100BaseTX connection (not just, say, PPPoE) and has sufficiently full NAT support that dhcpd could still be heard from behind it. (Either this last, or ensure that dhcpd is upstream, near (or on) the T1 gateway). This option also has the downside of forcing NAT upon all the rest of the library's computers, which (depending on how things are set up) could be a big pain in the ass, or break your network altogether. Caveat Emptor.
Back on the Secret Ranch, RMS perfects his GPL'ed ultralight, which (for some bizarre reason) has all the features of the bigger planes at none of the cost. However, due to licensing constraints, whenever the plane is brought into battle a copy of all the blueprints and materials must be given to the opponent. Additionally, they occasionally explode due to forgetful pilots leaving out a couple of right parentheses, as the only interface to the flight computer is through M-x and M-;.
I'm such a geek. I read the headline and thought, 'Kick ass! With the new Radeon 8500 drivers, a DRM-enabled helmet could really make XF86 4 a very cool gaming environment!
-Scientists use magnetism to do stuff -Scientists use gravity to linearly accelerate falling objects -Scientists harness laws of physics in a creative fashion
O Female Starship Enterprise Voice! The Silken Strains of your Status Report And error messages, long and short Cannot exist; we have no choice
But to point and click, to touch and stroke Plasma Displays that explode under fire. Or when tempest-tossed by space/time dire Make extra low-rank bridge crew croak --
What cruelty! Oh proud Science, how could you Leave the future so truncated, without Considering an old trekkie's doubt of limits to what we can do?
For if our starships don't even talk to us, Could we ever discover warp-speed, thus?
Slashdot Mirror
Ah, but it's that first ingredient
that can be a little troubling
to undergrads...
Tuna Mac 1 can of tuna 1 can of macaroni and cheese 1 tsp black pepper
:)
What? Tuna Mac? Blueberry and Tangerine weren't enough?
That might be an interesting analysis
if Red Bull contained caffeine.
Sigh.
Man, I love that line. I'm going to try it:
"Dad, er. You know all that money you sent me? You know how I promised that it would last me the full term? Well, uh, I'm not broke *exactly*, but I'm currently restructuring. Yeah. And food would help the process, yes. I expect to be cashflow-positive by Q3 2003. "
The release notes for x86 indicate that the thing
;)
ships with 2.2.20, with an optional 2.4.x for the bleeding-edgers, with (as explanation) a catty remark about the Debian developers not considering 2.4 a 'stable' branch.
Admittedly, I prefer Debian for the work that I do mainly because of the stability. But really -- 2.4 has been utterly reliable since ~2.4.14. Isn't this just a little paranoid? C'mon, folks, the thing is solid! I mean, the VM subsystem hasn't been completely re-written in *months*!
I think the theory behind it is that people will consume anything if it's packaged properly.
I'm supposed to use this computer for *work*?
Dammit, all I do all day is hit 'reload' on
the Slashdot Explorer program.
Is there a page anywhere that summarizes the holes/bugs/exploits in OpenSSH discovered in the last, say, two years? year? six months?
Here we go again.
Someone prepare a bald-headed chick and a transporter beam... 'ocar' is back.
notice how Slashdot didn't link to this Zine, either.
(Let alone deep linkin)
Well, first of all: You should segment your network, with an old Linux box as gateway.
Whether or not you'd consider this a 'separate network' is really up to you. However, it may be that you can't do this, for technical or political (or economical) reasons. Having worked as a network admin for a small library, I understand that there a well-considered hesitance to embrace yet another chunk of technology that only one employee (and, at that,a highly mobile and long-term-unpredictable one) understands. Essentially, you want something that's drop-dead stupid to administer, so that (if, for any reason, you leave) some poor high-school schmuck who just happens to be the kid of one of the librarians stands at least even odds of being able to get it going again.
So instead, you could do something like only assign IPs within a certain 'redlisted' range, such that the important computers on the network can run some cheap-ass firewall freeware to block from those IPs. Such a solution doesn't protect everyone, but it's really fast and easy.
Alternately, you could always buy one of those $60 firewall/routers between the rest of the library's computers and the Internet, and then put the newcomers outside said firewall. Such boxes are easy to administer, and come with nice glossy manuals. Set it up like this:
[T1]
|
|
[Hub for Anonymous Users]
|
[Firewall/Router]
|
{all the other computers}
However, in this scenario, you'll need to make sure that the firewall appliance is (a) able to handle a simple 100BaseTX connection (not just, say, PPPoE) and has sufficiently full NAT support that dhcpd could still be heard from behind it. (Either this last, or ensure that dhcpd is upstream, near (or on) the T1 gateway).
This option also has the downside of forcing NAT upon all the rest of the library's computers, which (depending on how things are set up) could be a big pain in the ass, or break your network altogether. Caveat Emptor.
Oh well, six of one, half a dozen of the other.
:)
Besides. Both countries have the same accent.
Back on the Secret Ranch, RMS perfects his GPL'ed ultralight, which (for some bizarre reason) has all the features of the bigger planes at none of the cost. However, due to licensing constraints, whenever the plane is brought into battle a copy of all the blueprints and materials must be given to the opponent. Additionally, they occasionally explode due to forgetful pilots leaving out a couple of right parentheses, as the only interface to the flight computer is through M-x and M-;.
Reuters - In a stunning example of the dangers of high-frequency communication technology, two garage thinkers were baked crispy gold by microwaves.
Warning: Contents of Garage may be hot!
I'm such a geek. I read the headline and thought, 'Kick ass! With the new Radeon 8500 drivers, a DRM-enabled helmet could really make XF86 4 a very cool gaming environment!
By any chance, is your Mom named 'Lucy'?
Closer than you think. I've worked in both. (/me prints the value of 'emacs-user-scars and 'McGill-university-X$^#-theory-courses)
The Golden Rule for being Proficient at Lisp:
Never iterate, and always follow the Golden Rule.
I imagine that the speed of 'light' is pretty close to the speed of 'heavy', provided that the vacuum is well-made and in good condition.
In Las Vegas, you might wait for an indefinite amount of time, but you will eventually be able to tell if the person you are calling is home or not.
In Monte Carlo, you can make the connection immediately, but you might get a spurrious busy signal a certain percent of the time.
Everyone knows the speed of light is 600mph, which it's day on one side of the world's disc while night on the other.
(With apologies to Terry Pratchett).
it must've been that wench Circuit Breaker.
Even Prowl can be wrong, sometimes.
*Yawn*. Next, after the commercial break:
-Scientists use magnetism to do stuff
-Scientists use gravity to linearly accelerate falling objects
-Scientists harness laws of physics in a creative fashion
... that Microsoft would have a whole new kind of 'product activation' to worry about.
O Female Starship Enterprise Voice!
The Silken Strains of your Status Report
And error messages, long and short
Cannot exist; we have no choice
But to point and click, to touch and stroke
Plasma Displays that explode under fire.
Or when tempest-tossed by space/time dire
Make extra low-rank bridge crew croak --
What cruelty! Oh proud Science, how could you
Leave the future so truncated, without
Considering an old trekkie's doubt
of limits to what we can do?
For if our starships don't even talk to us,
Could we ever discover warp-speed, thus?