That's not right (at least in terms of cut and paste). The X server handles it. Select with the left mouse button, paste with the middle. No messing with the keyboard. Works the same with every app.
The modular approach of X is one of its great strengths, not weaknesses. The same specification (X11R6) has scaled well enough that it hasn't needed reworking in over a decade. The Windows GDI seems to change whenever the wind blows.
Other Perl (non-haiku) poetry that is especially important and/or funny:
Roses are red, Violets are blue, Taint check your scripts, Or 1 w1ll 0wn j00
There was a perl hacker named Ray, Who wanted the time of the day. He pushed and he popped Shifted and chopped Till tomorrow was somehow today.
Re:I despise IPv6 and I think it's horrid...
on
The State of IPv6
·
· Score: 1
Possibly the best thing you can do is set yourself up with a recent Linux system, and find a tunnel broker (such as he.net) and create a tunnel. You can assign IPv6 addresses with 'ifconfig' in exactly the same manner as an IPv4 address (just you need -A inet6 as an option). I know RedHat and Debian both understand IPv6, and you can put it in their standard config files.
Are you really sure you can't just supply the IPv6 address as an argument to Solaris's 'ifconfig' command?
Re:IP6s problem is the numeric addresses r so comp
on
The State of IPv6
·
· Score: 1
Mainly because I've only just set up a permanent IPv6 presence and I need to spend some time playing with it. It's a learning experience.
Re:I despise IPv6 and I think it's horrid...
on
The State of IPv6
·
· Score: 5, Informative
The biggest problem that immediately jumps out at you with IPv6 is the fact that individual addresses in a subnet have absolutely no relation to each other. So John in the cube next to me will have an entirely different address than I do, and it will have no relation to me.
I'm sorry, but that's unadulterated bullshit. There is absolutely nothing stopping you from assigning adjacent addresses, or using the phone number of the cube-owner, or any other addressing scheme you want for your IPv6 addressing scheme.
For simplicity, on my server network, I simply assigned 2001:470:1f01:109::1 for the first machine, 2001:470:1f01:109::2 for the second, all the way onto the sixth, which (predictably) is 2001:470:1f01:109::6. I could have quite easily used the MAC address instead if I wanted to. Or used 2001:470:1f01:109::dead:beef and 2001:470:1f01:109::baad:f00d if I really wanted. Or set part of the last 64 bits to be telephone numbers. Or...and the list goes on.
IPv6 doe NOT put any constraints on the way you assign addresses in a subnet.
How you manage your network is up to you. If you chose lame IPv6 allocations, that's your fault, not the protocol's fault.
Re:IP6s problem is the numeric addresses r so comp
on
The State of IPv6
·
· Score: 2, Insightful
Oh for heaven's sake, that's a pretty lame excuse.
I didn't find it particularly difficult to set my entire server network running with IPv6. DNS wasn't hard to set up (both forward and PTR). Routing was no more difficult than IPv4. My website is available over IPv6 and even the forum is IPv6 aware (including having an IPv6 whois).
Once it's set up in DNS, you seldom have to touch it again - that's what DNS is there for.
I've not had X crash in a very long while (I can't remember offhand when the last time I had X die). I use X every day, I play games on the machine, I do development. I'm not just writing the odd letter in OpenOffice. X11R6 as XFree86 has been very stable on my current system (a P4 with a GeForce4 and the nVidia drivers).
I think X crashing has the same root cause as Win32 crashing (since Win2K) - bad hardware and/or bad drivers. Every time I've had a Windows crash/hang since using Win2K and WinXP has been either hardware or driver issues. The difference with X crashing and the Windows GUI crashing is that X isn't part of the kernel - I don't have to wait for the machine to reboot and all my daemons keep running. Have the Windows GUI crash and all processes are toast.
You don't really need ultra high speed to beat the airlines. A typical airline journey involves up to two hours waiting at the departure terminal, and half an hour in the disembarkation process at the other end.
On the train? Turn up 10 minutes before it leaves to ensure you don't miss it, get on, find a seat, spend under 5 minutes disembarking at the other end. Also, train stations generally are placed more conveniently than airports which by necessity have to be out of town. It's much easier to put a railway station in the middle of a city.
A TGV-style train going 180 mph will beat an airliner door-to-door on some surprisingly long journeys. If China builds a standard high-speed conventional rail link, it'll probably be good enough.
But the cryptic *nix commands are all short (that's why they are thought of as 'cryptic'). No, I wouldn't want to do massive amounts of admin on a mobile phone, but it might be useful if I get 'Oh my god I can't get to X' when I'm otherwise AFK, and want to do some basic troubleshooting.
I was thinking of getting a Sony Ericcson phone, but if the Nokia will have a Perl port available, I might wait a bit longer before getting a replacement for my existing one:-)
I used to work (until about 1.5 years ago) pretty much opposite the Johnson Space Center in Houston. They have a Saturn V outside there - I often took people who came to visit me to JSC, and we'd have a look around the rocket park.
It's an impressive thing up close. From our parking lot at work, it didn't look that impressive. But when you got up close to it, it was another story.
However, the Saturn V at JSC is also in pretty poor shape - it's corroded right through in places if you look closely. The white paintwork on the CM is badly cracked. Apparently, it also became a home for some owls (which is not a bad thing really).
The best artifact inside JSC is an Apollo capsule that went to the moon and back. You can actually (or could when I was last there) touch the heat shield - it's neat touching something that's been to the Moon and back. When you look at it closely, with its primitive electronics and its small size, you wonder how they ever did it.
But BSD has also become simpler and more graphical in nature. KDE and Gnome are available for BSD, too. I use KDE on OpenBSD. I also use KDE on Linux. I don't find the differences between OpenBSD and Linux particularly distracting.
No, street lamps in Britain are street lamps. They vary in size, but the common feature of a street lamp is they generally don't carry telephone wiring. A telephone pole in Britain is...erm...a wooden pole with phone lines on it and no light (although the telcos are generally burying increasing quantities of telephone lines).
A picture of a typical suburban street lamp in Britain is here and one on a bigger, main road is here. Note the complete absence of telephone lines.
Ah, the good 'ol "They Don't Make Cars Like They Used To" thing (or in this case, education etc):
I'm not denying that there ARE people with problems out there. I'm not even saying that this guy's kid may not have problems. But let's step back a bit. Back to the time when kids were allowed to be kids. When they didn't have to "perform" in a certain way by a certain age lest they be considered "freaks".
What age would this be? The one where left handed children were forced to learn to write with their right hand? The one where dyslexics were labelled retards and put in special classes? The one where adolescents who turned out to be gay were forced to take hormone treatments?
Like many large companies, the left hand of Microsoft often has no idea what the right hand is doing. Microsoft are even actively funding GPL code - see http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ - the Xen virtual machine monitor.
The difference is that Linux was never a proprietary OS. SkyOS is a closed source proprietary OS. It's unlikely to get the support or development effort that Linux got.
...but a realistic one, too. Having gone on a 7-year trip to the United States, I can confidently say that the real American people generally look nothing like "the beautiful people" Hollywood stick in films and the networks put on the TV. Most people in the US are plain or ugly or fat too. The fact that Hollywood seems to believe the entire US consists of a small piece of California and maybe New York if they remember doesn't help.
The Office would just not be realistic if they had all these "beautiful made for Hollywood" people in it, instead of real people.
It's all about the question of the right tool for the right job.
On my network, I use Linux for the servers, but OpenBSD for the outer perimeter security. Why OpenBSD? 'pf' makes a very good firewall system, and it has some very useful features. The documentation is excellent - I could get started and understand 'pf' using only the manual pages - I didn't have to search for HOWTOs finding them often out of date. It was easy to set up a bridging firewall (I have a very small IP block allocation, and don't want to lose any to a firewall for the DMZ). The other thing is was the default OpenBSD install was very minimal - the only Linux distro I've used recently where it was practical to start from something very small and add bits where needed was Debian (guess what my servers are running now).
Hopefully, the nightmare possible scenario I outlined as the possible SCO strategy can't and won't happen now this has been done. See the link to my JE below for an explanation.
Unfortunately, most people will probably allocate their IPv6 addresses as follows:
2001:1234:abcd::1 2001:1234:abcd::2
etc. When I set up my servers with IPv6 addresses (they are dual stacked, accessable both by IPv4 and IPv6) without thinking, I did that by default. Now I know better though, but I've just not got around to changing it.
The nice thing about having an IPv6 network is when I set up a test system, I can give it an IPv6 address to get to it, rather than using one of the very few IPv4 addresses I have - so I find IPv6 practically useful already.
Given enough processing power, even/dev/rand can produce terrorist messages.
It would have to be an enormous amount of power. Consider we limit the possibilities merely to the alphabet.
To come up with the word 'the' would be reasonably common place. The odds are 1 in 27*27*27 (26 letters plus space), or 1 in 19683, that any three outputs from a purely alphabetical/dev/urandom would give you that.
But the word 'the' is hardly a meaningful message. Let's consider 'The quick brown fox jumps over the lazy dog', a fairly short message at 43 characters. The odds of that coming from an alpha/space/dev/urandom are 1 in 35370553733215749514562618584237555997034634776827 523327290883 - astronomically unlikely. Even if every single atom in the Solar System was working on generating the string at random, it's still very unlikely to show up!
With a stegged message, where the entire ASCII character set may be used, the message such as what you speculate (some GPS coordinates and suspect verbiage) is even less likely.
The example of Shakespeare with an infinite number of monkeys is cute, but there *isn't* an infinite number of monkeys, or infinite bytes in images for that matter. The odds are so infinitessimally small that it's barely worth worrying about.
SCO will NOT take a large company (or even mid sized one) to court. They might hold 'low level' talks, which are pretty insignificant. What's a low level talk? It's probably SCO's telemarketers calling Google and trying to sell them UnixWare.
The only people that SCO will subponea or sue will be those who can't defend themselves. My JE says it all (link below) so I won't bother repeating it here.
Slashdot Mirror
That's not right (at least in terms of cut and paste). The X server handles it. Select with the left mouse button, paste with the middle. No messing with the keyboard. Works the same with every app.
The modular approach of X is one of its great strengths, not weaknesses. The same specification (X11R6) has scaled well enough that it hasn't needed reworking in over a decade. The Windows GDI seems to change whenever the wind blows.
Other Perl (non-haiku) poetry that is especially important and/or funny:
Roses are red,
Violets are blue,
Taint check your scripts,
Or 1 w1ll 0wn j00
There was a perl hacker named Ray,
Who wanted the time of the day.
He pushed and he popped
Shifted and chopped
Till tomorrow was somehow today.
Possibly the best thing you can do is set yourself up with a recent Linux system, and find a tunnel broker (such as he.net) and create a tunnel. You can assign IPv6 addresses with 'ifconfig' in exactly the same manner as an IPv4 address (just you need -A inet6 as an option). I know RedHat and Debian both understand IPv6, and you can put it in their standard config files.
Are you really sure you can't just supply the IPv6 address as an argument to Solaris's 'ifconfig' command?
Mainly because I've only just set up a permanent IPv6 presence and I need to spend some time playing with it. It's a learning experience.
I'm sorry, but that's unadulterated bullshit. There is absolutely nothing stopping you from assigning adjacent addresses, or using the phone number of the cube-owner, or any other addressing scheme you want for your IPv6 addressing scheme.
For simplicity, on my server network, I simply assigned 2001:470:1f01:109::1 for the first machine, 2001:470:1f01:109::2 for the second, all the way onto the sixth, which (predictably) is 2001:470:1f01:109::6. I could have quite easily used the MAC address instead if I wanted to. Or used 2001:470:1f01:109::dead:beef and 2001:470:1f01:109::baad:f00d if I really wanted. Or set part of the last 64 bits to be telephone numbers. Or...and the list goes on.
IPv6 doe NOT put any constraints on the way you assign addresses in a subnet.
How you manage your network is up to you. If you chose lame IPv6 allocations, that's your fault, not the protocol's fault.
Oh for heaven's sake, that's a pretty lame excuse.
I didn't find it particularly difficult to set my entire server network running with IPv6. DNS wasn't hard to set up (both forward and PTR). Routing was no more difficult than IPv4. My website is available over IPv6 and even the forum is IPv6 aware (including having an IPv6 whois).
Once it's set up in DNS, you seldom have to touch it again - that's what DNS is there for.
Why IPv8? Why not IPv7?
There is after all an IPv5 (the Internet Streaming Protocol).
I've not had X crash in a very long while (I can't remember offhand when the last time I had X die). I use X every day, I play games on the machine, I do development. I'm not just writing the odd letter in OpenOffice. X11R6 as XFree86 has been very stable on my current system (a P4 with a GeForce4 and the nVidia drivers).
I think X crashing has the same root cause as Win32 crashing (since Win2K) - bad hardware and/or bad drivers. Every time I've had a Windows crash/hang since using Win2K and WinXP has been either hardware or driver issues. The difference with X crashing and the Windows GUI crashing is that X isn't part of the kernel - I don't have to wait for the machine to reboot and all my daemons keep running. Have the Windows GUI crash and all processes are toast.
You don't really need ultra high speed to beat the airlines. A typical airline journey involves up to two hours waiting at the departure terminal, and half an hour in the disembarkation process at the other end.
On the train? Turn up 10 minutes before it leaves to ensure you don't miss it, get on, find a seat, spend under 5 minutes disembarking at the other end. Also, train stations generally are placed more conveniently than airports which by necessity have to be out of town. It's much easier to put a railway station in the middle of a city.
A TGV-style train going 180 mph will beat an airliner door-to-door on some surprisingly long journeys. If China builds a standard high-speed conventional rail link, it'll probably be good enough.
The thing is - it's in China. Do you think the maglev IP is actually patented in China? Probably not.
But the cryptic *nix commands are all short (that's why they are thought of as 'cryptic'). No, I wouldn't want to do massive amounts of admin on a mobile phone, but it might be useful if I get 'Oh my god I can't get to X' when I'm otherwise AFK, and want to do some basic troubleshooting.
Big question - does it have an SSH client? That would be a killer app for me, assuming latencies on GPRS are reasonable.
:-)
It goes without saying that it's bound to have an IRC client
I was thinking of getting a Sony Ericcson phone, but if the Nokia will have a Perl port available, I might wait a bit longer before getting a replacement for my existing one :-)
I used to work (until about 1.5 years ago) pretty much opposite the Johnson Space Center in Houston. They have a Saturn V outside there - I often took people who came to visit me to JSC, and we'd have a look around the rocket park.
It's an impressive thing up close. From our parking lot at work, it didn't look that impressive. But when you got up close to it, it was another story.
However, the Saturn V at JSC is also in pretty poor shape - it's corroded right through in places if you look closely. The white paintwork on the CM is badly cracked. Apparently, it also became a home for some owls (which is not a bad thing really).
The best artifact inside JSC is an Apollo capsule that went to the moon and back. You can actually (or could when I was last there) touch the heat shield - it's neat touching something that's been to the Moon and back. When you look at it closely, with its primitive electronics and its small size, you wonder how they ever did it.
But BSD has also become simpler and more graphical in nature. KDE and Gnome are available for BSD, too. I use KDE on OpenBSD. I also use KDE on Linux. I don't find the differences between OpenBSD and Linux particularly distracting.
No, street lamps in Britain are street lamps. They vary in size, but the common feature of a street lamp is they generally don't carry telephone wiring. A telephone pole in Britain is...erm...a wooden pole with phone lines on it and no light (although the telcos are generally burying increasing quantities of telephone lines).
A picture of a typical suburban street lamp in Britain is here and one on a bigger, main road is here. Note the complete absence of telephone lines.
What age would this be? The one where left handed children were forced to learn to write with their right hand? The one where dyslexics were labelled retards and put in special classes? The one where adolescents who turned out to be gay were forced to take hormone treatments?
Like many large companies, the left hand of Microsoft often has no idea what the right hand is doing. Microsoft are even actively funding GPL code - see http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ - the Xen virtual machine monitor.
The difference is that Linux was never a proprietary OS. SkyOS is a closed source proprietary OS. It's unlikely to get the support or development effort that Linux got.
...but a realistic one, too. Having gone on a 7-year trip to the United States, I can confidently say that the real American people generally look nothing like "the beautiful people" Hollywood stick in films and the networks put on the TV. Most people in the US are plain or ugly or fat too. The fact that Hollywood seems to believe the entire US consists of a small piece of California and maybe New York if they remember doesn't help.
The Office would just not be realistic if they had all these "beautiful made for Hollywood" people in it, instead of real people.
It's all about the question of the right tool for the right job.
On my network, I use Linux for the servers, but OpenBSD for the outer perimeter security. Why OpenBSD? 'pf' makes a very good firewall system, and it has some very useful features. The documentation is excellent - I could get started and understand 'pf' using only the manual pages - I didn't have to search for HOWTOs finding them often out of date. It was easy to set up a bridging firewall (I have a very small IP block allocation, and don't want to lose any to a firewall for the DMZ). The other thing is was the default OpenBSD install was very minimal - the only Linux distro I've used recently where it was practical to start from something very small and add bits where needed was Debian (guess what my servers are running now).
Hopefully, the nightmare possible scenario I outlined as the possible SCO strategy can't and won't happen now this has been done. See the link to my JE below for an explanation.
Unfortunately, most people will probably allocate their IPv6 addresses as follows:
2001:1234:abcd::1
2001:1234:abcd::2
etc.
When I set up my servers with IPv6 addresses (they are dual stacked, accessable both by IPv4 and IPv6) without thinking, I did that by default. Now I know better though, but I've just not got around to changing it.
The nice thing about having an IPv6 network is when I set up a test system, I can give it an IPv6 address to get to it, rather than using one of the very few IPv4 addresses I have - so I find IPv6 practically useful already.
It would have to be an enormous amount of power. Consider we limit the possibilities merely to the alphabet.
To come up with the word 'the' would be reasonably common place. The odds are 1 in 27*27*27 (26 letters plus space), or 1 in 19683, that any three outputs from a purely alphabetical
But the word 'the' is hardly a meaningful message. Let's consider 'The quick brown fox jumps over the lazy dog', a fairly short message at 43 characters. The odds of that coming from an alpha/space
With a stegged message, where the entire ASCII character set may be used, the message such as what you speculate (some GPS coordinates and suspect verbiage) is even less likely.
The example of Shakespeare with an infinite number of monkeys is cute, but there *isn't* an infinite number of monkeys, or infinite bytes in images for that matter. The odds are so infinitessimally small that it's barely worth worrying about.
SCO will NOT take a large company (or even mid sized one) to court. They might hold 'low level' talks, which are pretty insignificant. What's a low level talk? It's probably SCO's telemarketers calling Google and trying to sell them UnixWare.
The only people that SCO will subponea or sue will be those who can't defend themselves. My JE says it all (link below) so I won't bother repeating it here.