hardly. First of all, the IP your access provider gives you isn't yours forever, it's the provider's who lets you use it while you connect via them. switch provider and you switch IP.
It is customary in autoconfiguration to set the lower 64 bits to a function of your NIC's MAC address, but this is entirely optional. You can set it to a random number, or just number sequentially or whatever you want (as long as you manage to avoid collisions with other machines on the same network). And this is entirely up to you.
A lot of access providers here in europe already do, and I expect it's much the same in asia. Send a request to your access provider for them to offer IPv6 tunnels, if they get enough requests (and they're not a monopoly that doesn't care about user satisfaction) they should be offering them pretty quickly, it's still a nice marketing ploy to be able to claim you're offering "the internet of the future" even though only a very small promillage of their users is going to be using it.
Purely a misconfiguration or software issue then (and don't discont the placebo effect based on one or a few faster ftp downloads), once the initial protocol chatter is done, ftp and http are exactly equal.
Hmm? It's already been implemented, and I'm already using it for a lot of things. There isn't going to be a switchover day, whatever those spring clean emails might have claimed:-).
you grow the plant on the soil, extract the salt, put the remains back on the soil. Repeat, preferrably rotating crop. End result: A bag of salt and some fertile ground.
LEDs are diodes, which means they only conduct electricity (and in doing so give of light) in one direction. Usually on LEDs the shorter of the two leads is the cathode, which means the side that's to be connected to the negative side of the battery. The other side (the anode) connects to the positive side of the battery.
Depends on where the endpoints are. If you're generating the packets and stuffing them into a tcp tunnel on the same host you're fine. If your packets get out of order/dropped/whatever before they enter the tunnel you're still screwed though.
- find . -name test.txt (why not just allow 'find test.txt')
Because that'd be ambigious. That could mean both find all files in test.txt, or as you wanted find files with name test.txt. Making behaviour like that depend on what's on disk is generally a very bad idea. If you use it a lot, put "alias fi='find . -name'" in your shells rc-file.
This is where linux bind mounts come in handy, you can bind mount your/lib and/usr/lib into all your chroots (just make sure they don't contain suids or anything:) ), that way all libraries will only go into memory once, even when used from multiple chroots. (of course you can olso have all your fake roots on the same filesystem and hardlink, but this is a lot nicer)
Nonsense. Think of a number that's looks like the binary expansion of Pi (ie just 1's and 0's), but in base 10.This'd be non repeating, irrational, not representable as a finite function (for suitable definitions of 'a finite function), and yet I can assure you you won't find the sequence 123456 in it.
The linux kernel isn't written to be cross-compiler, it's written to work with GCC. And any other compilers it works with are either modifications of GCC or have put a lot of work into acting like GCC.
Slashdot Mirror
hardly. First of all, the IP your access provider gives you isn't yours forever, it's the provider's who lets you use it while you connect via them. switch provider and you switch IP.
It is customary in autoconfiguration to set the lower 64 bits to a function of your NIC's MAC address, but this is entirely optional. You can set it to a random number, or just number sequentially or whatever you want (as long as you manage to avoid collisions with other machines on the same network). And this is entirely up to you.
A lot of access providers here in europe already do, and I expect it's much the same in asia. Send a request to your access provider for them to offer IPv6 tunnels, if they get enough requests (and they're not a monopoly that doesn't care about user satisfaction) they should be offering them pretty quickly, it's still a nice marketing ploy to be able to claim you're offering "the internet of the future" even though only a very small promillage of their users is going to be using it.
Purely a misconfiguration or software issue then (and don't discont the placebo effect based on one or a few faster ftp downloads), once the initial protocol chatter is done, ftp and http are exactly equal.
That's really convincing, especially considering the fact that Rusty has recently rewritten the module handling code.
Hmm? It's already been implemented, and I'm already using it for a lot of things. There isn't going to be a switchover day, whatever those spring clean emails might have claimed :-).
you grow the plant on the soil, extract the salt, put the remains back on the soil. Repeat, preferrably rotating crop. End result: A bag of salt and some fertile ground.
LEDs are diodes, which means they only conduct electricity (and in doing so give of light) in one direction. Usually on LEDs the shorter of the two leads is the cathode, which means the side that's to be connected to the negative side of the battery. The other side (the anode) connects to the positive side of the battery.
Depends on where the endpoints are. If you're generating the packets and stuffing them into a tcp tunnel on the same host you're fine. If your packets get out of order/dropped/whatever before they enter the tunnel you're still screwed though.
- find . -name test.txt (why not just allow 'find test.txt')
Because that'd be ambigious. That could mean both find all files in test.txt, or as you wanted find files with name test.txt. Making behaviour like that depend on what's on disk is generally a very bad idea. If you use it a lot, put "alias fi='find . -name'" in your shells rc-file.
the entire book is there
It's already done, but it's put in a LOC record, not in the free-form TXT record. (google for it)
If the attacker has root you're dead anyway, ..
mkdir foo; chroot foo; cd
This is where linux bind mounts come in handy, you can bind mount your /lib and /usr/lib into all your chroots (just make sure they don't contain suids or anything :) ), that way all libraries will only go into memory once, even when used from multiple chroots. (of course you can olso have all your fake roots on the same filesystem and hardlink, but this is a lot nicer)
Should have used rsync witch can run over ssh and does --bwlimit. Still plenty of reason to use it though.
Actually it's third level, and it doesn't matter. Hostnames nor domain names are allowed to contain underscores.
And rightly so, hostnames/domainnames aren't allowed to have underscores in them.
Four even. I seem to have misplaced the 1st one, but the others were called "Build disk", "utility disk" and "application disk".
I doubt you have the full thing then, win 1.0 came on 3 360k floppies, and I doubt it'd compress to 22%.
SYN's either get responded to with SYN|ACK if the port is open, or RST|ACK if it's closed.
google.us
Nonsense. Think of a number that's looks like the binary expansion of Pi (ie just 1's and 0's), but in base 10.This'd be non repeating, irrational, not representable as a finite function (for suitable definitions of 'a finite function), and yet I can assure you you won't find the sequence 123456 in it.
Just because the n-ary representation of pi is infinite does not mean that all sequences will occur in it, and this has in fact not yet been proven.
And, lest we forget, the linux kernel is brimming with //-style comments.