Eggs and Cheese in MRE's? Been there, done that
on
The Future of MREs
·
· Score: 1
I was in Uncle Sam's Marine Corps for five years ending in 1998. We had egg MRE's (omelet... my least favorite), and every MRE had either peanut butter or _cheese_ to spread on the brick-like crackers.
Given my experience with MRE's, I'd have to say it doesn't matter which process they use to prepare the food. It will still taste like crap.
The trick to being able to stomach the MRE's is to make sure you get one w/ a Tabasco in the accessories pack. Better to taste the Tabasco then an artist's rendition of whatever it says on the label.
For those of you looking for a fun Online RPG, check out Wyvern. It's written in Python and Jython. I'm not sure if the engine code is open source, but the author funds the server himself and only asks for contributions if you can spare them. If you know Jython, you can become a wizard and write your own additions to the game (new maps, towns, monsters, items, etc.).
If I recall correctly, the last flurry of/. articles on this subject included some information about an old movie or video of someone demonstrating hyperlinks. I think it was dated in the late sixties. What ever happened to that?
GNU sought to develop a desktop environment they could release under the GPL. They came up with GNOME. At the time, they had no choice due to the fact that the Qt widget set was not compatible with the GPL. Now that it is, they are happier about companies like RedHat including it in their distributions, but they are still dedicated to seeing their baby (GNOME) succeed. Check out RMS' recent comments on the subject if you can find them.
Granted, it's been a while since I was a sp00k for Uncle Sam, but when I worked with the DISA systems, they all ran Solaris on Sparc hardware.
The next giant leap for DoD will be to standardize on Linux for their other desktop systems and implement StarOffice or OpenOffice for compatibility across the board. When I worked on the non-secret squirrel projects, they couldn't decide on a standard office software package. Some shops used AmiPro, some used Wordperfect, etc. It varied across the board.
I think this linux.com news article says it a little better. Sorry if you took my reply as whining, but I believe the article explains in a little more detail the point I was trying to get across about duplication of effort. For example, Mr. Egelman's closing remarks:
I think that soon people will start realizing what's going on. The only way for this revolution to continue is by contributing to it rather than creating separate paths.
I agree to a certain extent. One thing that pisses me off is watching all of the duplication of effort in the Open Source Community. For example, if all of the groups out there working on accounting projects would combine forces and agree on technologies (Perl, Apache, PostgreSQL, RPM, etc.), we could soon have an Open Source, modular, scalable accounting package comparable to something like Great Plains Dynamics. If you don't agree with me, browse around sourceforge.net sometime and look at all of the groups working on similar projects. Imagine what would happen if you combined some of those projects and focused that productivity into one kickass line of Open Source applications!! Don't re-invent the wheel!!
Now... I'm not saying that RedHat should have full reign of Linux standards. However, those of you who have read the book Net Ready know that there are four pillars to success in the modern E-conomy: Leadership, Governance, Competencies, and Technologies. RedHat is providing leadership for much of the community. We should be using the Open Source model not only to support them with the other three, but also to help them with a good system of checks and balances.
Bob's got some good points, and I think we should stop beating RedHat down and instead stick out a hand to pull him back up. Face it, we're all in this together. We might as well stop pointing fingers and try some "I'll scratch your back if you scratch mine" instead. Then, and only then, will we truly be on our way to world domination.
Personally, I'll be installing RHL7.0 as soon as I can purchase a copy. Why purchase you may ask? Because RedHat, for all they've done for the community, deserves $29.95 of my money.
One of the problems I see with your theory of blocking out all private addresses (for those of you keeping score at home, that's 10.x.x.x, 172.16.x.x through 172.31.x.x, and 192.168.x.x) is that you won't see these addresses trying to come in through your firewall (if you've built it right) as often as you'd think. With Network Address Translation (NAT) and Port Address Translation (PAT), you'll see the public IP addresses of these hosts being attacked more often than not. The ability of any given script kiddie to modify the TCP header will complicate this, but without prior knowledge of your network it's a hit and miss attack. For all they know, you could be running any combination of subnetted private and/or public IP addressing schemes behind your firewall.
The best defense against these attacks is a good ACL on a solid firewall platform. Block incoming traffic from private addresses, but be sensible and put internet accessible hosts on a DMZ. For general internet use, select one public IP address from your pool of public IP addresses and use PAT.
The info above was typed out haphazardly and may not make sense, but after working with Internet security in a myriad of environments, the best advice I can give you is that if even if you THINK you understand it, you should still seek consult (the more eyes the better). I would go into more detail, but unfortunately I have to go set up a firewall for a client:)
Slashdot Mirror
I was in Uncle Sam's Marine Corps for five years ending in 1998. We had egg MRE's (omelet... my least favorite), and every MRE had either peanut butter or _cheese_ to spread on the brick-like crackers. Given my experience with MRE's, I'd have to say it doesn't matter which process they use to prepare the food. It will still taste like crap. The trick to being able to stomach the MRE's is to make sure you get one w/ a Tabasco in the accessories pack. Better to taste the Tabasco then an artist's rendition of whatever it says on the label.
For those of you looking for a fun Online RPG, check out Wyvern. It's written in Python and Jython. I'm not sure if the engine code is open source, but the author funds the server himself and only asks for contributions if you can spare them. If you know Jython, you can become a wizard and write your own additions to the game (new maps, towns, monsters, items, etc.).
If I recall correctly, the last flurry of /. articles on this subject included some information about an old movie or video of someone demonstrating hyperlinks. I think it was dated in the late sixties. What ever happened to that?
-- Gun
GNU sought to develop a desktop environment they could release under the GPL. They came up with GNOME. At the time, they had no choice due to the fact that the Qt widget set was not compatible with the GPL. Now that it is, they are happier about companies like RedHat including it in their distributions, but they are still dedicated to seeing their baby (GNOME) succeed. Check out RMS' recent comments on the subject if you can find them.
Granted, it's been a while since I was a sp00k for Uncle Sam, but when I worked with the DISA systems, they all ran Solaris on Sparc hardware. The next giant leap for DoD will be to standardize on Linux for their other desktop systems and implement StarOffice or OpenOffice for compatibility across the board. When I worked on the non-secret squirrel projects, they couldn't decide on a standard office software package. Some shops used AmiPro, some used Wordperfect, etc. It varied across the board.
Best regards,
-- Gunfighter
I agree to a certain extent. One thing that pisses me off is watching all of the duplication of effort in the Open Source Community. For example, if all of the groups out there working on accounting projects would combine forces and agree on technologies (Perl, Apache, PostgreSQL, RPM, etc.), we could soon have an Open Source, modular, scalable accounting package comparable to something like Great Plains Dynamics. If you don't agree with me, browse around sourceforge.net sometime and look at all of the groups working on similar projects. Imagine what would happen if you combined some of those projects and focused that productivity into one kickass line of Open Source applications!! Don't re-invent the wheel!!
Now... I'm not saying that RedHat should have full reign of Linux standards. However, those of you who have read the book Net Ready know that there are four pillars to success in the modern E-conomy: Leadership, Governance, Competencies, and Technologies. RedHat is providing leadership for much of the community. We should be using the Open Source model not only to support them with the other three, but also to help them with a good system of checks and balances.
Bob's got some good points, and I think we should stop beating RedHat down and instead stick out a hand to pull him back up. Face it, we're all in this together. We might as well stop pointing fingers and try some "I'll scratch your back if you scratch mine" instead. Then, and only then, will we truly be on our way to world domination.
Personally, I'll be installing RHL7.0 as soon as I can purchase a copy. Why purchase you may ask? Because RedHat, for all they've done for the community, deserves $29.95 of my money.
--Gunfighter
One of the problems I see with your theory of blocking out all private addresses (for those of you keeping score at home, that's 10.x.x.x, 172.16.x.x through 172.31.x.x, and 192.168.x.x) is that you won't see these addresses trying to come in through your firewall (if you've built it right) as often as you'd think. With Network Address Translation (NAT) and Port Address Translation (PAT), you'll see the public IP addresses of these hosts being attacked more often than not. The ability of any given script kiddie to modify the TCP header will complicate this, but without prior knowledge of your network it's a hit and miss attack. For all they know, you could be running any combination of subnetted private and/or public IP addressing schemes behind your firewall.
The best defense against these attacks is a good ACL on a solid firewall platform. Block incoming traffic from private addresses, but be sensible and put internet accessible hosts on a DMZ. For general internet use, select one public IP address from your pool of public IP addresses and use PAT.
The info above was typed out haphazardly and may not make sense, but after working with Internet security in a myriad of environments, the best advice I can give you is that if even if you THINK you understand it, you should still seek consult (the more eyes the better). I would go into more detail, but unfortunately I have to go set up a firewall for a client :)