The publishers can hire a few college students in each locality. Their job is to pump Freenet full of so much mislabeled shit that nobody can make sense out of anything in the pipe. Unless the anonymnity is done away with it'll be impossible to tell who's doing it.
The consensus model doesn't scale well to the entire world. You'd better get used to the fact that you'll be sharing with the people you know, and not the whole world. It's really not that horrible a fate. And local communities are good.
I seem to recall vaguely that something was written on a page somewhere in a book that I read somewhere in a building. I'm pretty sure the outside of the building was painted brown. Anyhow, the fact that it was written down and I read it proves my point that whatever you just said was wrong.
Actually, there is hypocrisy to the degree that the two groups overlap. And there does appear to be a large body of people who fit into that area of the venn diagram.
And the cool thing about laying in lots of big conduit is that if you really burn out and go luddite, you can use it to make a pneumatic tube message system.
When you run a server on a computer connected to a network, we can only assume that it is because you wish to make some services or data available to users of other computers.
So when you open the door to your house we can only assume you want random homeless people to wander in?
There was a small library headache with Slack when they finally adopted Glibc, but nothing like the every-version-of-everything library headaches that some of the other distros suffer from.
When I drive down the street with the window rolled down, it is not because I want people to spit in the window at me and my passengers.
When a woman wears a hot outfit out in public, it isn't because she wants to be sexually assaulted by any random person who happens along.
There are still communities where people don't need to lock the door to their house, because they know everybody else, and because everybody has the decency to not break in.
There is a rule in a document called the Iroquois Constitution, an 'American Indian' pact (it's available in the Gutenberg Project, I believe): The rule is that if you are going to be away from your lodge for a time, you should put a big signal up in front of it indicating such. Then other people are not supposed to stay away from the dwelling. It was assumed in this society that this was sufficient to keep intruders out.
We don't live in a perfect world, we don't live in a world that's even close to perfection. But people don't have to assume that because they don't lock down their posessions that they become free gimmies for anybody else who happens along.
If the room had nothing of immediate value in it, but the door wasn't locked because the key was out being duplicated and a number of people needed access to the contents of the room, probably that person was doing something very wrong.
And that isn't too far-fetched a hypothetical situation.
Obviously, you don't break into other people's computers and telephone switches in your free time. So you have no need to fog up the definition of various terms.
That isn't true of some of the firebrands participating in the forum, though.
Finally, it is very easy to learn about securing your system without breaking into one that doesn't belong to you.
This point needs to be amplified and made a more prominent part of the anti-cr/hacker message.
Ten years ago most Unix systems in existence were multi-user time sharing machines. To learn anything about Unix you had to get access to someone else's hardware, or spend a ton of money yourself.
These days anybody with an old '386 box laying around can install a free Unix clone on it and hack away. There's no longer the old justification of 'curiosity' and 'just to learn more' to fall back on. If you want to learn more about networking, put a free Unix clone on four old '386 boxes and hack away.
Nobody has any business poking around where they weren't invited and/or where the maintainer of a site doesn't want them.
You poision the truth in your arguement. The 'open source' community should be thankful that Microsoft plowed their field for them, encouraging the hardware industry to produce a large amount of fairly open hardware, years after IBM, who pioneered in that area (producing an open-buss machine based on off-the shelf LSI chips, etc.), had slammed the door shut (OS/2, the PS/2 and Microchannel was IBM's failed effort to recapture the market they'd lost control over.)
Ultimately, of course, it's Microsoft's loss that is 'open sources' benefit. Every machine that the latest version of Windows NT/2000 won't run on is fertle ground for a Freenix (although Xfree itself is starting to 'roll forward' in the same way with their abandonment of, for instance, support for S3/Trio64 graphics cards).
They funded MkLinux because they wanted to take away the motivation for hackers to reverse engineer their hardware.
The last thing Apple Computer wanted was the details of their proprietary hardware to reside in an arch directory of the Linux kernel source. So they released a half-assed psuedo-Linux version.
This dumped water on anybody's motivation to figure out how to implement Linux on Apple hardware.
Because of it, nobody ever ripped into the proprietary boot code in the older Macs and revealed the secrets. Thus to run NetBSD on an older Mac, you've got to have a runty little MacOS partition and a bootloader that's a MacOS binary.
It's obvious to anybody who thinks about it for more than a few moments that Apple was anything but benevolent in releasing MkLinux.
Unless you know what you are doing, all you end up accomplishing is messing up the air-flow that the case designer intended. This can have the end result of reduced cooling. Using a fan to blow in and another fan to suck out of the case can have this effect, particularly if the two fans don't have the same volume, and those are the only two openings in the case.
But all bets are off with most cheap 'clone' cases anyway.
The more fans the noisier the machine will be, though, which should also be a consideration before over-fanning your box.
Slashdot Mirror
Back in the year 89 it was probably good enough.
That was a long time ago, though, so I might be wrong.
It'll be easy to shut down Freenet.
The publishers can hire a few college students in each locality. Their job is to pump Freenet full of so much mislabeled shit that nobody can make sense out of anything in the pipe. Unless the anonymnity is done away with it'll be impossible to tell who's doing it.
The consensus model doesn't scale well to the entire world. You'd better get used to the fact that you'll be sharing with the people you know, and not the whole world. It's really not that horrible a fate. And local communities are good.
I seem to recall vaguely that something was written on a page somewhere in a book that I read somewhere in a building. I'm pretty sure the outside of the building was painted brown. Anyhow, the fact that it was written down and I read it proves my point that whatever you just said was wrong.
Actually, there is hypocrisy to the degree that the two groups overlap. And there does appear to be a large body of people who fit into that area of the venn diagram.
For gameplay, an interface that works without fail for me, and only sporatically for you sounds just plain excellent .
Eventually you'll figure it out and not be such a boring person to play the game against. Or we'll all just quit wanting you in the game.
And the cool thing about laying in lots of big conduit is that if you really burn out and go luddite, you can use it to make a pneumatic tube message system.
Well, if it kills or maims the thief at least there's redeeming social value.
When you run a server on a computer connected to a network, we can only assume that it is because you wish to make some services or data available to users of other computers.
So when you open the door to your house we can only assume you want random homeless people to wander in?
SLS has been dead for years. Oh wait! It evolved into Slackware, it didn't die.
The only installation option was via ftp
And NFS, which I prefer.
There was a small library headache with Slack when they finally adopted Glibc, but nothing like the every-version-of-everything library headaches that some of the other distros suffer from.
He forgot to log out of his troll account before posting his comment??
Sounds like you're ready to be running the hurd.
Better download it fast, before it becomes uncool.
There are some pretty good newspaper ads that are being banned from campuses, too.
Nope. Not going to buy your arguement.
When I drive down the street with the window rolled down, it is not because I want people to spit in the window at me and my passengers.
When a woman wears a hot outfit out in public, it isn't because she wants to be sexually assaulted by any random person who happens along.
There are still communities where people don't need to lock the door to their house, because they know everybody else, and because everybody has the decency to not break in.
There is a rule in a document called the Iroquois Constitution, an 'American Indian' pact (it's available in the Gutenberg Project, I believe): The rule is that if you are going to be away from your lodge for a time, you should put a big signal up in front of it indicating such. Then other people are not supposed to stay away from the dwelling. It was assumed in this society that this was sufficient to keep intruders out.
We don't live in a perfect world, we don't live in a world that's even close to perfection. But people don't have to assume that because they don't lock down their posessions that they become free gimmies for anybody else who happens along.
Maybe that's the world you live in. How pitiful.
If the room had nothing of immediate value in it, but the door wasn't locked because the key was out being duplicated and a number of people needed access to the contents of the room, probably that person was doing something very wrong.
And that isn't too far-fetched a hypothetical situation.
Obviously, you don't break into other people's computers and telephone switches in your free time. So you have no need to fog up the definition of various terms.
That isn't true of some of the firebrands participating in the forum, though.
I don't think there's a place on earth that could sustain a 'million Hackers march.'
First off, the supply of chips and Mountain Dew would run out almost immediately.
Second, the weight load of the mass of paunchy monitor-tanned fatboys would break up the pavement, preventing them from marching.
Third, Eric Raymond returned the Darth Vader costume to the rental place, and with the price of VA Linux stock being what it is.....
Finally, it is very easy to learn about securing your system without breaking into one that doesn't belong to you.
This point needs to be amplified and made a more prominent part of the anti-cr/hacker message.
Ten years ago most Unix systems in existence were multi-user time sharing machines. To learn anything about Unix you had to get access to someone else's hardware, or spend a ton of money yourself.
These days anybody with an old '386 box laying around can install a free Unix clone on it and hack away. There's no longer the old justification of 'curiosity' and 'just to learn more' to fall back on. If you want to learn more about networking, put a free Unix clone on four old '386 boxes and hack away.
Nobody has any business poking around where they weren't invited and/or where the maintainer of a site doesn't want them.
You poision the truth in your arguement. The 'open source' community should be thankful that Microsoft plowed their field for them, encouraging the hardware industry to produce a large amount of fairly open hardware, years after IBM, who pioneered in that area (producing an open-buss machine based on off-the shelf LSI chips, etc.), had slammed the door shut (OS/2, the PS/2 and Microchannel was IBM's failed effort to recapture the market they'd lost control over.)
Ultimately, of course, it's Microsoft's loss that is 'open sources' benefit. Every machine that the latest version of Windows NT/2000 won't run on is fertle ground for a Freenix (although Xfree itself is starting to 'roll forward' in the same way with their abandonment of, for instance, support for S3/Trio64 graphics cards).
They funded MkLinux because they wanted to take away the motivation for hackers to reverse engineer their hardware.
The last thing Apple Computer wanted was the details of their proprietary hardware to reside in an arch directory of the Linux kernel source. So they released a half-assed psuedo-Linux version.
This dumped water on anybody's motivation to figure out how to implement Linux on Apple hardware.
Because of it, nobody ever ripped into the proprietary boot code in the older Macs and revealed the secrets. Thus to run NetBSD on an older Mac, you've got to have a runty little MacOS partition and a bootloader that's a MacOS binary.
It's obvious to anybody who thinks about it for more than a few moments that Apple was anything but benevolent in releasing MkLinux.
Wozniak has spent the last twenty years not doing tech.
Do you seriously think he could cobble together the new G4 machine with a handful of TTL gates?
The computer business has evolved far past anything that Woz could handle.
No.
Extra fans are to keep it cool enough that the 'throttle' doesn't kick in.
If the throttle didn't kick in the chip would burn up. That's what happens with AMD chips.
In a properly designed system the processor should never get that hot.
Motorola makes the StrongARM processor???
Unless you know what you are doing, all you end up accomplishing is messing up the air-flow that the case designer intended. This can have the end result of reduced cooling. Using a fan to blow in and another fan to suck out of the case can have this effect, particularly if the two fans don't have the same volume, and those are the only two openings in the case.
But all bets are off with most cheap 'clone' cases anyway.
The more fans the noisier the machine will be, though, which should also be a consideration before over-fanning your box.