Grab a crappy old athlon tbird box with a gig of ram and set it up as a router/firewall running *LVS (Linux Virtual Server) to forward web requests to your back end web server. You can start out with one web server and gauge the load. If you want to scale the system, add more backend web servers and configure LVS with the new backend ip addresses.
For redundancy on the athlon router, trunk a couple nics for network, and boot from cdrom (knoppix) if you are worried about system disk failure. You could also buy a 3ware 2 lane raid card for a couple bills and sata raid a couple hard disks if cdrom boot doesn't work for you. It's cheaper to keep a couple cdrom drives on hand, and spare knoppix cds, than setup a bootable hard drive raid system.
Figure out if you want a shared filesystem for the web servers, or just rsync the important stuff between them for starters. Software raid on another crappy athlon box will work well for backend storage in the beginning. If you have high disk load, you may need to upgrade the fileserver if transfer rates exceed bus bandwidth. The point is, you are non-profit and running on a shoestring budget. start out cheap and dirty. Spend money on hardware later when you find out where your bottlenecks develop.
If you loose a backend webserver, LVS can be configured to handle it in different ways.
Also, a plug for dotproject. Works very well for project managing. Your phb will love the gantt charts too. It's browser based, so you don't need to get roped into special client-side software (Korganizer, Gnome, etc).
The way of things around us is systemic and indicative of something much greater than ourselves. It's laughable to think we have enough competence to understand how it all works or where it came from. We haven't enough awareness of the depths of the oceans or even enough wisdom to prevent our own demise. Who are we to say we have a rich enough grasp on the rest of it to make more than only mere whimsical observations? We can't even figure out, as a species, how to stop killing ourselves off over money, drugs and oil.
I don't like macs, and especially dislike the mactard syndrome but it seems to me that any computer would be suspect of toxic fumes - ever replace a power supply and notice odor it gives off on powerup? A computer is basically an air pump when it comes right down to it. All the solder, wiring and electronic components certainly must give off some toxicity when they are 'baking-in' and the fans exhaust all that stuff right out into the room.
> decide that the open source licensing of current and previous versions > of jabber (which for most people works perfectly well as it is) are > unforkable and/or non-distributable.
You can't do that (under the GPL anyway). Once a pile of code is released under GPL, the licensing status for that version cannot be changed.
Worst case, as far as I can see, is Cisco says that jabber is assimilated and no longer GPL'd. That doesn't stop anyone from taking code from last week (already released) and forking.
OLPC started the whole sub-mini notebook craze. It was Wintel that did the raining*. It's bad enough the American monopolies had to get their greedy paws in the OLPC pie; let's at least keep the facts straight.
His teacher had told the class to search the Internet for information
on the environment, but the boy was stumped. "I was trying, but I couldn't
find anything,"
What the boy didn't know, was the rest of his classmates *did* find something and the classroom immediately erupted in a resounding "RTFM!" in response, showing proof that children in developing nations can at least find Slashdot.
The Financial Post (Lawrence Solomon is executive director of Energy Probe and author of The Deniers)*.
So some author has a "Growing number of scientists" (to whom do we owe the credits?) who thinks things are roses, huh? And this is on a financial website? Hell, I'm going to go by some Freon and use it to power my H2!
"According to a growing number of scientists", the period of global
warming that we have experienced over the past few centuries as Earth
climbed out of the Little Ice Age is about to end."
Having users manage their workstations is a fine idea in theory, but when it comes to "How did these files get deleted" or "who installed that piece of software" all too often there is just a big shrug or deliberate finger pointing. If users want to follow installation procedures that's a different story, but most users will take as many shortcuts as they can around paperwork.
One problem with documentation is the upkeep because things change frequently. If the process of updating the dox were simple and easy, more people would do it. We use dokuwiki because it is pretty simple and easy to use. When I show a junior admin how to do something on the terminal, I can past the terminal session into a dokuwiki[0] page and it's there for reference next time. I know it's working because now when the juniors call me it's because they don't understand something in the dox, not where to find the dox. If you have a gui app you need to demo, hook up vnc2swf[1] and post the flash file as a link in dokuwiki.
Slashdot Mirror
Grab a crappy old athlon tbird box with a gig of ram and set it up as a router/firewall running *LVS (Linux Virtual Server) to forward web requests to your back end web server. You can start out with one web server and gauge the load. If you want to scale the system, add more backend web servers and configure LVS with the new backend ip addresses.
For redundancy on the athlon router, trunk a couple nics for network, and boot from cdrom (knoppix) if you are worried about system disk failure. You could also buy a 3ware 2 lane raid card for a couple bills and sata raid a couple
hard disks if cdrom boot doesn't work for you. It's cheaper to keep a couple cdrom drives on hand, and spare knoppix
cds, than setup a bootable hard drive raid system.
Figure out if you want a shared filesystem for the web servers, or just rsync the important stuff between them for
starters. Software raid on another crappy athlon box will work well for backend storage in the beginning. If you
have high disk load, you may need to upgrade the fileserver if transfer rates exceed bus bandwidth. The point is,
you are non-profit and running on a shoestring budget. start out cheap and dirty. Spend money on hardware later when
you find out where your bottlenecks develop.
If you loose a backend webserver, LVS can be configured to handle it in different ways.
[*] - http://www.linuxvirtualserver.org/
and this: http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html
There's enough info out there to the contrary of the article that leads me to belive otherwise.
http://yro.slashdot.org/comments.pl?sid=03/01/15/2345217
Perhaps the drive manufacturers could start a recycle program if you ship the disassembled drive back without the platters.
could be a market for ssh proxies in countries where filtering is not implemented.
Also, a plug for dotproject. Works very well for project managing. Your phb will love the gantt charts too. It's browser based, so you don't need to get roped into special client-side software (Korganizer, Gnome, etc).
ftfa: "Due to the presence of commercial malware.."
So.. this was malware someone purchased?
NSA E.A. Testing Criteria
---
EAL0 $1,000,000
EAL1 $1,000,000
EAL2 $2,000,000
EAL3 $3,000,000
EAL4 $4,000,000
EAL5 $5,000,000
EAL6 $6,000,000
EAL7+ Call for quote.
Maybe if you donate a laptop, the kids getting the XOs will figure out how to cluster them and model more than just a malaria cure.
The way of things around us is systemic and indicative of something much greater than ourselves. It's laughable to think we have enough competence to understand how it all works or where it came from. We haven't enough awareness of the depths of the oceans or even enough wisdom to prevent our own demise. Who are we to say we have a rich enough grasp on the rest of it to make more than only mere whimsical observations? We can't even figure out, as a species, how to stop killing ourselves off over money, drugs and oil.
ftfa: "The gambit ultimately failed, and Axel "Ago" Gembe remained safely in Germany."
> Some men just want to watch the world burn.
Others just want to bring marshmallows.
- angry over confusion
- angry over video card
- angry over southpark
- angry over upgrades
- angry over waiting in line
I don't like macs, and especially dislike the mactard syndrome but it seems to me that any computer would be suspect of toxic fumes - ever replace a power supply and notice odor it gives off on powerup? A computer is basically an air pump when it comes right down to it. All the solder, wiring and electronic components certainly must give off some toxicity when they are 'baking-in' and the fans exhaust all that stuff right out into the room.
> decide that the open source licensing of current and previous versions
> of jabber (which for most people works perfectly well as it is) are
> unforkable and/or non-distributable.
You can't do that (under the GPL anyway). Once a pile of code is
released under GPL, the licensing status for that version cannot be changed.
Worst case, as far as I can see, is Cisco says that jabber is assimilated
and no longer GPL'd. That doesn't stop anyone from taking code from last
week (already released) and forking.
OLPC started the whole sub-mini notebook craze. It was Wintel that did the raining*. It's bad enough the American monopolies had to get their greedy paws in the OLPC pie; let's at least keep the facts straight.
[*] - http://technology.timesonline.co.uk/tol/news/tech_and_web/article4472654.ece
http://boycottnovell.com/2008/01/07/mistake-bruce-byfield/
His teacher had told the class to search the Internet for information
on the environment, but the boy was stumped. "I was trying, but I couldn't
find anything,"
What the boy didn't know, was the rest of his classmates *did* find something and
the classroom immediately erupted in a resounding "RTFM!" in response, showing
proof that children in developing nations can at least find Slashdot.
The Financial Post (Lawrence Solomon is executive director of Energy Probe and author of The Deniers)*.
So some author has a "Growing number of scientists" (to whom do we owe the credits?) who thinks things are roses, huh? And this is on a financial website? Hell, I'm going to go by some Freon and use it to power my H2!
"According to a growing number of scientists", the period of global
warming that we have experienced over the past few centuries as Earth
climbed out of the Little Ice Age is about to end."
[*] The Deniers: The World Renowned Scientists Who Stood Up Against Global Warming
Hysteria, Political Persecution, and Fraud**And those who are too fearful to do so (Hardcover)
http://www.amazon.com/Deniers-Renowned-Scientists-Political-Persecution/dp/0980076315
"So many laptops, so little time"
- Kunga the Botmaster
Having users manage their workstations is a fine idea in theory, but when it comes to "How did these files get deleted" or "who installed that piece of software" all too often there is just a big shrug or deliberate finger pointing. If users want to follow installation procedures that's a different story, but most users will take as many shortcuts as they can around paperwork.
"Overall, women categorized more images correctly than men did." What gender determined the 'correct' interpretation of the images?
http://www.google.com/search?q=vista+driver+problems
supercooled magnets, linked like sausages.
Run Firefox/thunderbird as a different user.
/usr/local/firefox/firefox
Not perfect, but gives you the ability to protect your home directory.
- xhost +localhost
- kdesu -u webuser -c
One problem with documentation is the upkeep because things change
frequently. If the process of updating the dox were simple and easy,
more people would do it. We use dokuwiki because it is pretty simple
and easy to use. When I show a junior admin how to do something on
the terminal, I can past the terminal session into a dokuwiki[0] page
and it's there for reference next time. I know it's working because
now when the juniors call me it's because they don't understand something
in the dox, not where to find the dox. If you have a gui app you need
to demo, hook up vnc2swf[1] and post the flash file as a link in dokuwiki.
[0] - http://wiki.splitbrain.org/wiki:dokuwiki
[1] - http://www.unixuser.org/~euske/vnc2swf/