(a) static configuration: no arp, no dhcp. (b) declare an ipsec tunnel from your laptop to your gateway. (c) set ipsec policy to require it for all traffic. (d) rtfm
ip link set dev wireless arp off up ip address add dev wireless local 192.168.1.2 peer 192.168.1.3 ip neighbor add dev wireless to 192.168.1.3 lladdr 00:11:24:2c:38:c6 nud permanent
Personal-computer software today is broadly the same as it was twenty years ago. There has been little real progress, because no one has a vision for the future.
When I encounter a television, I make haste to shift my place. And I carry a can of insect repellant for in case I meet an American. It's a challenging world out there, and to survive one must be well prepared.
my whole life long. richard stallman even gave me a medal for it & invited me into his secret chambers of gnu-love. moo like the gentoo cow, naked like the ubuntu orgy, we did.
Web technologies are the stuff of nightmares and firefox is a noxious nest of code.
Simple alternative: Write a graphics/video/sound/network/keyboard-mouse-events library; web pages would then be programs linked against this library. Your browser simply downloads and runs such programs in a sandbox; they render to the browser window in response to keyboard, mouse, and network events. Let page authors link in shared libraries, which the browser caches, dynamically retrieving a necessary library if it is not already cached.
All that's about five thousand lines of code, no kidding. Straightforward elaboration: consder the above as implementing the "screen interface" for a given site; sites could then implement other interfaces with other conceptual structures like RSS feeds, printed pages, audio-based interfaces, whatever. (CSS2 makes a half-hearted attempt at this.) So, one logical site (say, google.com) might implement many of these interfaces, and you could use that subset of them which your platform supports. From the author's point of view, a site becomes a sort of class that implements N interfaces, the mechanism for this always being to produce a program for each interface, to be ultimately downloaded and run by the browser. (There would be many frameworks to do this, in various ways.)
But they explain different things, as your examples well illustrate. No one asks astronomy to make suffering and death bearable.
(Medieval Catholicism's flirtation with natural science is, by the way, another exception that proves the rule: it would not be noteworthy were it normal.)
Science manages your irrational expectations about how the world will behave in the future, whereas religion proposes irrational moral precepts like "don't feed your children to the moloch." They cannot be compared as if they were two ways of doing the same thing.
Slashdot Mirror
Here, we call it Occupied Normandy.
(a) static configuration: no arp, no dhcp.
2 0d13277558056a4c
2 0d13277558056a4c
(b) declare an ipsec tunnel from your laptop to your gateway.
(c) set ipsec policy to require it for all traffic.
(d) rtfm
ip link set dev wireless arp off up
ip address add dev wireless local 192.168.1.2 peer 192.168.1.3
ip neighbor add dev wireless to 192.168.1.3 lladdr 00:11:24:2c:38:c6 nud permanent
setkey -c >/dev/null <<-END
flush;
spdflush;
add 192.168.1.2 192.168.1.3 esp 256 -m tunnel
-E aes-cbc 0x25d8d1bbcf9b7b416ebd7ce514627539f12dc64e3e75c5a
-A hmac-sha1 0x17f98a8f668324191ee406855e81130fb17f7726;
add 192.168.1.3 192.168.1.2 esp 512 -m tunnel
-E aes-cbc 0x25d8d1bbcf9b7b416ebd7ce514627539f12dc64e3e75c5a
-A hmac-sha1 0x17f98a8f668324191ee406855e81130fb17f7726;
spdadd 192.168.1.3 0.0.0.0/0 any -P in ipsec
esp/tunnel/192.168.1.3-192.168.1.2/require;
spdadd 0.0.0.0/0 192.168.1.3 any -P out ipsec
esp/tunnel/192.168.1.2-192.168.1.3/require;
END
And I had thought proprietary software was all kittens and ice-cream cones. They should have downloaded GNOME.
That must be one smart plant.
But you're definitely not going to get a very good slave at that price.
(The exchange rate is more like six iPods to one slave.)
You can just dd if=winimage of=/dev/winpartition every so often. (keep your documents on another partition or server)
If a computer malfunctions, simply inspect its source code to diagnose and correct the problem.
You're sitting on your couch, playing video games. Shooting a gun would put you several steps higher up the evolutionary ladder.
Personal-computer software today is broadly the same as it was twenty years ago. There has been little real progress, because no one has a vision for the future.
When I encounter a television, I make haste to shift my place. And I carry a can of insect repellant for in case I meet an American. It's a challenging world out there, and to survive one must be well prepared.
He can finance his investments at the risk-free rate in the derivatives markets. Student loans are more expensive.
moo, said hte cow
my whole life long. richard stallman even gave me a medal for it & invited me into his secret chambers of gnu-love. moo like the gentoo cow, naked like the ubuntu orgy, we did.
pay a thousand bucks a year to have some stupid wire come to your house. yeah, that's progress/// life sure is getting better.
Ubuntu is easy, Gentoo is flexible. Debian manages to give you the opposite.
I clicked one and it installed Windows XP on my computer.
Web technologies are the stuff of nightmares and firefox is a noxious nest of code.
Simple alternative: Write a graphics/video/sound/network/keyboard-mouse-events library; web pages would then be programs linked against this library. Your browser simply downloads and runs such programs in a sandbox; they render to the browser window in response to keyboard, mouse, and network events. Let page authors link in shared libraries, which the browser caches, dynamically retrieving a necessary library if it is not already cached.
All that's about five thousand lines of code, no kidding. Straightforward elaboration: consder the above as implementing the "screen interface" for a given site; sites could then implement other interfaces with other conceptual structures like RSS feeds, printed pages, audio-based interfaces, whatever. (CSS2 makes a half-hearted attempt at this.) So, one logical site (say, google.com) might implement many of these interfaces, and you could use that subset of them which your platform supports. From the author's point of view, a site becomes a sort of class that implements N interfaces, the mechanism for this always being to produce a program for each interface, to be ultimately downloaded and run by the browser. (There would be many frameworks to do this, in various ways.)
But they explain different things, as your examples well illustrate. No one asks astronomy to make suffering and death bearable.
(Medieval Catholicism's flirtation with natural science is, by the way, another exception that proves the rule: it would not be noteworthy were it normal.)
The creationists and their ilk are the exceptions that prove the rule—religion today is not much concerned with world-explanation.
Science manages your irrational expectations about how the world will behave in the future, whereas religion proposes irrational moral precepts like "don't feed your children to the moloch." They cannot be compared as if they were two ways of doing the same thing.
But an attitude of caveat emptor and a basic understanding of capital markets sure would have helped.
It's so easy, everyone does it sooner or later.
I believe that I am a tree.
I'm going to laugh at you when you die.
Persuade me that common sense is better justified than the wildest mystical lunacy.
"Common sense is sensible," by the way, is no better a justification than "mysticism is mystical" might be.