You don't store the packet, you store the layer-4 flow information (address, protocol, port). It adds up to a lot in the end, but still not that much compared to what a mail and/or news-server pulls.
Well - I live in Denmark, just outside Copenhagen. I'd look to the following if I considered moving: Fast, clean, 24hour/day public transport. Clubs, bars, cinemas. Fast, cheap Internet (DSL), though that isn't much of an issue right now since I work at a large ISP. Cheap rent, possibly in a green area just outside the city.
But then again......isn't this what we're all looking for?
There's a long road from "point and click" and thinking you've setup a system to "point and click" to setup a system. And most NT admins I know/have heard of don't know how to do the latter.
You're right, anybody can make an NT boot, but only a few understand the security model thoroughly. Even most MCSE's don't, so your choice here is: 1. Buy NT, get somebody who understands it, and can see through it's obscure "happy, happy" colors GUI, pay a truckload for this. 2. Download a linux dist, get a geek who lives for it, and understands it.
Fact is: NT's GUI only serves as a way of making you believe you can administer it properly, while you can't.
> Isn't that, what the GPL was ment for? To take an existing program (driver, script...), add your own extensions and changes and then give the results back to the community? I think so.
Yes, I don't blame them, it was just to answer if they've been hacking at Becker's or writing their own from scratch.
> My question is "how did they come up with the drivers for Linux?" Did they just tweak Becker's drivers (pardon me if it was someone else), or write them from scratch, or port them from Unices, or what?
If you read the.c file it says they have used Becker's skeleton for ethernet drivers, but everything else seems to be theirs (correct me if I'm wrong)
I think it should work on any dist (haven't tested, since my Debian is at home). But they have only tested the drivers on RH, that's what they state in the README.
Honestly: We all choose, what we read and don't read on the internet. There's bound to be some articles on/. you aren't interested in, so skip them and shut up.
This is complete and utter bull...we have several European backbone(provider)s, which we route through, and most countries have established a national IP traffic exchange (DIX in Denmark, LINX in London, AMS-IX in The Netherlands, and so forth) My statistics for the last 24 hours show that of the top 10 Autonomous systems we have exchanged traffic with, only one is US based, so please get your facts straight, we have, a telephone/IP infrastructure, which is at least as good as in US, if not better.
I still use the classfulnaming, specifically because there's no good way to say/24 in Danish For those interested the's a complete guide to subnets at http://www.ripe.net/lir/services/subnet s.html
Re:Address classes have been gone for a while...
on
IP Address Shortage
·
· Score: 1
We might not use classes, but it's haelluva lot easier to say a C or B class than a/24 or a/16
Again, this shows how the big companies screw up
on
IP Address Shortage
·
· Score: 1
I work at a reasonably sized ISP in.dk, and I'm in charge of allocating IP's for our customers Every now and then people whine about, how they could get more than the 4 or 8 IP's I'm willing to assign for them, and they explain, how they, if they went to a larger ISP could get an entire C-class, even though they'll only be using IP's for a router and a firewall. People don't know, and don't want to know the possibilities of NAT. How sad!
Slashdot Mirror
Try taking a look a CAIDA
Can't help but laughing a bit about the "10 years of Linux training those computer specialists have received"
Well - I live in Denmark, just outside Copenhagen.
I'd look to the following if I considered moving:
Fast, clean, 24hour/day public transport.
Clubs, bars, cinemas.
Fast, cheap Internet (DSL), though that isn't much of an issue right now since I work at a large ISP.
Cheap rent, possibly in a green area just outside
the city.
But then again......isn't this what we're all looking for?
There's a long road from "point and click" and thinking you've setup a system to "point and click" to setup a system. And most NT admins I know/have heard of don't know how to do the latter.
You're right, anybody can make an NT boot, but only a few understand the security model thoroughly. Even most MCSE's don't, so your choice here is:
1. Buy NT, get somebody who understands it, and can see through it's obscure "happy, happy" colors GUI, pay a truckload for this.
2. Download a linux dist, get a geek who lives for it, and understands it.
Fact is: NT's GUI only serves as a way of making you believe you can administer it properly, while you can't.
I know there are a lot, that's why it would hurt so much. (hurt them, not us)
Anybody got a list of DMA members, then we'll just make a list of their domains and disallow them.
I'd be glad to see an article espousing the benfits of BSDs over Linux too, if it wasn't for the FUDish style, and cheap blows, he used in this.
We can all use 10 minutes to completely stomp another OS, but please people, let's be resonable, and base it on facts.
> Isn't that, what the GPL was ment for? To take an existing program (driver, script...), add your own extensions and changes and then give the results back to the community? I think so.
Yes, I don't blame them, it was just to answer if they've been hacking at Becker's or writing their own from scratch.
> My question is "how did they come up with the drivers for Linux?" Did they just tweak Becker's drivers (pardon me if it was someone else), or write them from scratch, or port them from Unices, or what?
.c file it says they have used Becker's skeleton for ethernet drivers, but everything else seems to be theirs (correct me if I'm wrong)
If you read the
What I mean by this is: Other network companies have helped in providing the loads of NIC drivers for Linux
The part about dbecker's driver says:
Note: The 3C59x, 3C900 and 3C905 series NICs are supported by Donald Becker's driver.
This indicates to me, that Donald's supports a supergroup of the 3Com driver, and that they are different.
Realtek haven't written their driver themselves, but afaik they've been helpful in the development process?
Of course most of us need more high-end cards than the RTL8xxx's.
I think it should work on any dist (haven't tested, since my Debian is at home).
But they have only tested the drivers on RH, that's what they state in the README.
> Cisco allegedly has router OS upgrades that will allow their boxes to be used on an
> ipv6 network.
Strike allegedly. They have IPv6 code, but not in production code, only in experimental code.
If you don't like the smell...
/. you aren't interested in, so skip them and shut up.
Honestly: We all choose, what we read and don't read on the internet. There's bound to be some articles on
"It must be true, I read it on the internet"
This is complete and utter bull...we have several European backbone(provider)s, which we route through, and most countries have established a national IP traffic exchange (DIX in Denmark, LINX in London, AMS-IX in The Netherlands, and so forth)
My statistics for the last 24 hours show that of the top 10 Autonomous systems we have exchanged traffic with, only one is US based, so please get your facts straight, we have, a telephone/IP infrastructure, which is at least as good as in US, if not better.
I still use the classfulnaming, specifically because there's no good way to say /24 in Danish For those interested the's a complete guide to subnets at http://www.ripe.net/lir/services/subnet s.html
We might not use classes, but it's haelluva lot easier to say a C or B class than a /24 or a /16
I work at a reasonably sized ISP in .dk, and I'm in charge of allocating IP's for our customers
Every now and then people whine about, how they could get more than the 4 or 8 IP's I'm willing to assign for them, and they explain, how they, if they went to a larger ISP could get an entire C-class, even though they'll only be using IP's for a router and a firewall.
People don't know, and don't want to know the possibilities of NAT.
How sad!