I'm assuming your kids use windows. Can't help you there - but if you can setup a unix-like router you might be able to implement some of these....
If you can restrict access to a unix machine acting as a router that's running PF, you could use AuthPF to enable or disable a NAT connection to your child's box. Just have them ssh in when they want to use the machine and they either get logged out automatically somehow or logout when they're done. (It's not hard. Putty with private keys makes this a two click operation or it could be scripted to run at startup on a unix box.) This could be setup to allow or restrict access to individual computers on your in-house LAN.
Note: OpenBSD does not have the sessiontime clause in login.conf
You could use login.conf and times.allow, times.deny to restrict when logins are allowed (on FreeBSD):
The times.allow and times.deny entries consist of a comma-separated list
of time periods during which the users in a class are allowed to be
logged in. These are expressed as one or more day codes followed by a
start and end times expressed in 24 hour format, separated by a hyphen or
dash. For example, MoThSa0200-1300 translates to Monday, Thursday and
Saturday between the hours of 2 am and 1 p.m.. If both of these time
lists are empty, users in the class are allowed access at any time. If
times.allow is specified, then logins are only allowed during the periods
given. If times.deny is specified, then logins are denied during the
periods given, regardless of whether one of the periods specified in
times.allow applies.
You could also use AuthPF and a cron script to write and remove/etc/nologin. from the system at given times.
## ADJUST TO TASTE - they're your kids! ##
0 14 * * * rm/etc/nologin # go ahead and use computer till 4p. Then we have dinner # and you kids do homework not needing online time 0 16 * * * touch/etc/nologin # alright, chat with your friends for a bit or finish up your homeword 0 20 * * * rm/etc/nologin # no more. Say goodnight to your friends and hit the sack! 30 21 * * * touch/etc/nologin
Remember root can login anytime (can also be overridden on individual accounts through login.conf with ignorenologin. You'll need to periodically check and force logouts (after a winpopup warning) based on the existence of this file.
You could modify the firewall/NAT rules directly via cron or some other method to your choosing (report cards online? Screenscrape the results and allow an extra hour for each grade point above a B-...)
You could block services on an individual basis. Web allowed all the time but chatting only from 2000-2100?? No filesharing untill after dinner?
There may be a PAM module that will restrict login based on time of day, week, etc.
You could use user accounting to record how much time they spend online. A weekly review with them.... You could restrict usage to hours/day, hours/week or whatever. When the time is all used up, access get's locked.
I LOVE FreeBSD!!! I really can't wait for this release. Actually I can (perhaps unlike others), but it does excite me quite a bit. Just wish I had a MP machine on which to play....
Developers. Developers. Developers. You're all beautiful. Your work is wonderful. You code so we don't have to. Kudos, thanks, and appreciation to the Nth!
Same goes for the testers. FreeBSD wouldn't be where it is today if it weren't for you installing untested code on your machines and diligently reporting problems and fixes. Cheers to you brave, brave souls.
Shoutouts to the documentation crew! THE HANDBOOK ROCKS and has since I started reading it. What a value. It comes free! Free OS, Free docs. What's not to love???
Port maintainers. Put up your hands for these guys. A wide range of code setup for flawless builds with a single command.
Get the CD and install on a spare machine. BEAT THE HELL OUT OF IT.
If you find a bug you will be a GOD in the eyes of those that want to run 5.3 production-style.
I vote wait untill that release is FULLY READY TO GO OUT THE DOOR. 5.3 is critical to further acceptance of FreeBSD, further commercial funding support, further legitimacy of the platform, and confidence in the developers/Release Engineering team.
If you need it now, run the RC. Unless a TON of people need 5.3 NOW, the developers should feel no pressure to get it out the door. They should feel pressure to get testers to find problems. They should feel pressure to find people that like inflicting damage on a running OS. Find those twisted individuals and give them a RC CD and a keyboard. Hear their stories.
Make it good as the worlds's eyes will be upon this relase and any further potential problems. RC2 should be fixing a much smaller list of bugs.
WE'RE STILL PLAYING AROUND WITH SCHEDULER CHOICES!! ???? I'd suggest more RCs. Blank CD-R media is CHEAP. Corporate downtime when bugs are discovered 1.5 weeks out from a release IS NOT!
Test Test Test Test Test. Beat the hell out of it - portinstall all ports. Rock the box and see how she holds. Try and crash it. Pound it from the network. Pull a live disk. JMP to a block of random bytes. Run 200 instances of your JVM. Start up as many desktop applications as possible. Try and kill your install and see how Beastie holds.....
5.3 is going to ROCK but SHOULD NOT BE RUSHED!!! If it needs time, by all means give RE-team time!
I hope we don't have to see a 5.3.1 release.
Perhaps the developers should require a certain variation in hardware platforms tested on or a given number of people to run it with no problems before final release.
(I don't run FreeBSD in a corporate environment or profess to know much about RE's testing process. Just trying to get in people's heads that extreme testing WILL make this release a HUGE success.)
[from the page.... apologies for formatting - lameness filter...]
FreeMail is a peer-to-peer Mail Server program (aka 'Mail Transfer Agent' or 'MTA') that makes it possible for you to send and receive email messages with unprecedented levels of privacy and anonymity.
Normal mailservers (such as Exim, Sendmail, qMail etc) communicate directly over the normal Internet, and send/receive all of your emails in plaintext for Big Brother and goodness knows how many companies to see. Even if your ISP uses encryption for transfer of mail, a simple court order (or bribe) is all it takes for your emails to end up in front of prying eyes, even many years after you sent or received them..
On the other hand, FreeMail encrypts your messages and hides them within the privacy-protecting Freenet network, where they are picked up and decrypted only by the people you're sending your messages to.
Features A lot of thought has gone into FreeMail's design, to arrive at a secure, robust yet user-friendly system to satisfy your email communication needs.
So far, FreeMail includes the following features:
100% compatible with normal email client programs (eg Mozilla, Evolution, Outlook Express)
Protects every aspect of your privacy, by concealing:
What you are sending and receiving
Who you are sending to or receiving from
Whether you are sending or receiving messages at all
Whether you even have Freemail installed
Convenient Web interface for installation, administration and viewing of mail statistics
Fully peer to peer (does not depend on any in-Freenet service)
Unlimited personal email accounts (called 'identities'), that cannot be linked together or traced to you
Censors out 'X-Mailer' header, to protect your privacy
Unlimited message sizes
Full support for message attachments
Interacts with your favourite email client via the standard SMTP/POP3 protocols, with user-selectable host-based access restrictions
Difficult and time-consuming for spammers
People familiar with Freenet will also understand and appreciate the following features:
Works fine with transient nodes, as long as the node (and the Freemail software) runs once every couple of days or so
Convenient to associate mail accounts with Freenet freesites, or use separately
All data inserted into and retrieved from Freenet is encrypted to the recipient and cryptographically signed by the sender; recipient verifies signatures by accessing the sender's freemail mailsite (a special kind of freesite whose URI is isomorphic to the sender's purported freemail address)
Receipted delivery of messages
Tenacious retry/confirmation protocol to overcome Freenet performance fluctuations
Every mail account is self-certifying. Certificates are validated via special 'freesites' created by FreeMail
Good use of Freenet keys:
KSK queues are protected from spamming/spoofing by the mandatory signature mechanisms
Ability to relocate the mess queues in the event of DoS attacks
Ability to balance performance against use of system resources
At this time, there are no third-party certification. The author is open to suggestions from users about how this should happen. For example, a web of trust amongst linked freesites, assigning 'karma' to mail addresses.
Changing Options Running the Node Monitoring the Node Restarting the Node Network Participation Network Integration Finer Points Stable or Unstable? Datastore Size Bandwidth Allotment Connection Limiting When Things Go Wrong Clock Skew
Quite helpful for tuning and optimizing your node once you get it up and running.
3 Most important ingredients:
Permanent connection
Bandwidth
Disk space
Without these you'll be complaining like the rest. Go ahead and set up a node, but optimum performance is a dream without all 3 above elements. Also, count on 2 days of letting it just run before you'll be able to get much done. After you're integrated things run much more smoothly!
If you're behind a firewall you'll need to know how to setup port forwarding. Windows install is the easiest, GNU systems should be trivial and there's a port for FreeBSD. I believe MacOSX can run it as well. If you can run a modern JavaVM, Freenet should be no trouble for you.
(About firewalls - if your $50 router/NAT/switch thingy cannot handle the hundreds of TCP connections Freenet can generate, you might want to either invest in a dedicated box (OpenBSD works well for me and allows me to prioritize traffic behind my interactive_ssh and vonage queues - Linux floppy distros should be fine too) or specify in freenet.conf to limit the number of open connections. Just be aware as connection tables can overload and distrupt the connection for all behind the NAT. Then again your $50 box may have no trouble at all. Port numbers are all random high port numbers making Freenet difficult to detect and firewall. Connections out will be made but the portforward is necessary for other nodes to connect to you. If nodes can't connect to you, performance will most likely be horrendous.)
If you just install Freenet and immediately try and download large files, you will be frusturated and give up. DON'T! Many freesites will not appear at all. NEVER FEAR! Let your node run in the background for a few days and get itself integrated into the mesh. Nodes that are more useful to the network (fast connection, large data store) will end up the most successful when downloading or uploading content. If you can't leave your machine running all the time or want to use freenet over dialup, fine, but your performance will not match those of others that can provide more to the network. Leeching is fine, it allows others to leech off of you - but leave your machine connected and Freenet's performance may end up suprising you.
Towards the beginning you may just want to start a number of downloads and count on many of them not completing - JUST WALK AWAY or do something else. Don't waste your time. By grabbing whatever bits you can, you'll increase the data in your own datastore and your connections within the network. If others find those bits from your node, your status will increase, more will connect to you and they will then be potential sources for more desired bits of your own. The better connectivity you've got, the more you will find. Leaving your node up at all times and keeping your datastore intact are the best ways to increase Freenet's performance (not just for you but for all).
THOSE PARANOID: I've been running my Freenet node wide open (no throttle) on my Earthlink cable connection in the heart of Raleigh, NC for some time. No threatening letters or trouble, my Vonage works fine (I do use pf's ALTQ) and those in my house have no trouble with connections, download or upload speeds)
For those that are already on Freenet and trying to download large files, one tool is critical. FUQUD (Freenet Utility for Queued Uploads and Downloads). Find it. Use it. Fred (the built in web interface) isn't going to cut it.
Regarding disk space. Unless you've got around say 2Gigs to dedicate to a node, your node may not perform as well as it could (200M is practical minimum). Consider the value you choose to be relatively permanant. You can't trade it with other uses - you build a datastore and that's the size, unusable for your MP3's or ogg's for example. They don't grow or shrink. You s
If the voice recorder has "VOX" record capabilities then you could design a mute circuit that gates open at random times for either a random or fixed interval. This would save you the record time (get a week's worth rather than uploading every day) and you wouldn't need to mess around with splitting files or worry as much about privacy concerns.
I realize onboard soldered electrets may be a problem but if you've got recorders that are using external mics this could work. This is unlikely but I thought I'd mention it anyway. (I wish more "voice recorders" would provice external microphone inputs....) This method would throw away much chance of gathering data on when the recorded snippits were made however- not sure it that would matter.
Here's my suggestion. Feel free to ask for details by emailing [cyrus at 80d dot org].
I have a very rough idea here. Buy or make some sea anchors. Sea anchors are very high drag in the water and are used to limit boat drifting in windy conditions. They are basically a large tapered piece of cloth (like a bucket) with a hole in the bottom. They collect water in a big hole and make it flow through a small hole at the other end. This is just drag in the water. The trick is to make one so that it can be converted between a high-drag and a low-drag state. Pull on one line (at the big opening, via a few connection points) and it's high drag. If you pull the small opening through the middle and release tension on the big opening connection, the material can be forced inside out and will then hopefully offer little resistance. You could also somehow have it move sideways through the water, offering little resistance.
What you then need to do is have one on each side of a pully type gear mechanism. As the water pulls on the high-drag anchor, you get a chance to make some electricity (ratio gear drive to a generator) while you reel the other one in. Switch modes, put your gear drive in "reverse" and have the other pulled out. This will reel in the opposite anchor as you drive your generator. Rinse and repeat.
Another option would be to attach a number of these "underwater sails" to a loop. Configure so they pull on one side and are collapsed on the other. This would give you continuous power.
The anchors should be positioned to be in the highest flow possible. If they float to the top or sink too much you could attach a float or weight (or both) to properly position them under the water.
All that's left is implementation. I'd be glad to help further with design. This could even work in the winter underneath an icy cover.
If not to power a generator, you could perhaps power a water pump that would raise the water to a high enough head that you could power a paddle wheel at high velocity. This could be attached to an alternator. You can find plans for these with home power people. Be sure to raise your voltage as high as possible before transmitting it any distance and use the largest diameter cable you can afford. Vdrop at 12 or 24 volts can be very large (relatively), wasting much of your effort.
Exercise. "Street level" social/cultural interactions. It's all there. Just get up and go. You'll find people with interests that will keep you busy. Coffee shops. Book stores. The street corner. Make random friends. Exchange numbers. Get together next Tuesday here or there. Talk more. Get introduced to friends, friends of friends, etc.
You may want to consider your use of midnight as a good time to run scripts.
Many people are still awake at this time, perhaps working from home, trying to beat a deadline, etc. Cron jobs using resources at this time could be frusturating, making a long night even longer.
You may want to consider moving jobs to 2 or 3 AM instead.
When in this country might I expect to see a digital public notary? 5 years?
Present a document, and the notary wraps the contents with a digital signature and timestamp, similar to the way GPG clearsigning works. That would be pretty neat.
I'd pay by the megabyte for somebody to timestamp stuff for me.
How would you like a glass of water?? ANSWER=NO!
on
Twist on DNA Privacy
·
· Score: 1
If you are suspected of a crime in which officers of the law have some DNA evidence, you may be offered a glass of water or a piece of gum in the interviewing room. There is a good chance this is an easy way to get a DNA sample from you if they do not already have one.
Take the gum, but think twice before spitting it in the trash.
I'm curious when we may have access to a government approved digital time-stamping service?
Ever like to prove to somebody that a document existed at a certain date? "Mail it to yourself. It's got the postmark."
Well, besides the fact that this ploy would never stand up in court (it's too easy to steam the flap open), it's a good idea.
How about the USPS providing a digital document time-stamping service? What good time-stamps are availible out there that would stand a test at the patent office, for example???
You got me! Most common means I've seen is to take a naked toilet paper or paper towel roll and stuff it with some dryer sheets, new or used; just stuff them in there so they fill the entire air passage. The spun fiber material they are made of is pretty neat because it will catch particulate matter (like smoke, dust), yet still allows air to pass by with a very low pressure drop. (new dryer sheets will keep the odor down much better, but be harder to 'draw' through)
If you're smoking in your dorm room, a 'oney', or 'one hitter', is probably the least conspicuous means of getting certain psychoactive chemicals into your blood, but the use of the tube as described above need not be limited to such low quantity imbibing. Water pipe, steamroller, Jay or Joint, vaporizer, chillum, blunt, or iBong smoke could also be blown through one of these things and work equally well:)
Make a SMB share somewhere containing all your dotfiles and things you want to get to from elsewhere. This may or may not work very well for other types of files/documents/etc.
In each homedirectory on each real machine: $ mkdir ~/dotfiles $ cp (or mv) dotfiles to ~/dotfiles $ ln -s all the.* files in ~/ to the copies in ~/dotfiles
(omit any files that are specific to the machine and which you don't want to use the master for)
In a shell-login script (.profile or.login) DON'T MOVE THESE AS DESCRIBED ABOVE
Put a master copy of your.bashrc,.vimrc,.muttrc, etc. onto the master SMB share.
$smbmount [master homedir] on top of ~/dotfiles
all the symlinks will then point to the mounted homedir.
On logout, unmount the remote SMB directory (or directories, if you'd like to adapt the idea for other types of files) and rsync (or unionify, or codafy, cvs, etc.) any changes from the master back to ~/dotfiles. This way, if the next time you login to that machine, the master isn't availible, you've got at least a semi-current version of your files (via the symlinks). If you want to keep a file local, don't symlink it.
Works under windows or uni*. Isn't nearly as complex as some other ideas mentioned. Isn't perfect, so lay off. Just popped into my head..... Adapt as needed, you're smart.
The free Netpbm toolkit includes a pnmstitch program which can do what you describe (lest the fact that right now it can only join two photos, left and right). It's a relatively new addition to the suite. These operations can be easily strung together to join multiple images (via pipes, most operations with these tools employ the use of stdin/stdout, though other options are availible).
These tools are the default utilities for mainipulating images serverside with the Gallery web based photo album.
But for all of us who need not install from a floppy, can cvsup the RELENG_4_8_0_RELEASE tag, and buildworld without waiting for the floppy issue to be resolved, am I correct?
Would you demand a full refund for the dental work?
I'd ask 'em for a mouth full of gold crowns if your tongue doesn't regain sensitivity in another month. If palladium, or a base-metal alloy (nickel or chromium) are more your style, those are availible too!
Slashdot Mirror
There's this page.
I'm assuming your kids use windows. Can't help you there - but if you can setup a unix-like router you might be able to implement some of these....
If you can restrict access to a unix machine acting as a router that's running PF, you could use AuthPF to enable or disable a NAT connection to your child's box. Just have them ssh in when they want to use the machine and they either get logged out automatically somehow or logout when they're done. (It's not hard. Putty with private keys makes this a two click operation or it could be scripted to run at startup on a unix box.) This could be setup to allow or restrict access to individual computers on your in-house LAN.
Note: OpenBSD does not have the sessiontime clause in login.conf
You could use login.conf and times.allow, times.deny to restrict when logins are allowed (on FreeBSD):
You could also use AuthPF and a cron script to write and remove /etc/nologin. from the system at given times.
Remember root can login anytime (can also be overridden on individual accounts through login.conf with ignorenologin. You'll need to periodically check and force logouts (after a winpopup warning) based on the existence of this file.
You could modify the firewall/NAT rules directly via cron or some other method to your choosing (report cards online? Screenscrape the results and allow an extra hour for each grade point above a B-...)
You could block services on an individual basis. Web allowed all the time but chatting only from 2000-2100?? No filesharing untill after dinner?
There may be a PAM module that will restrict login based on time of day, week, etc.
You could use user accounting to record how much time they spend online. A weekly review with them.... You could restrict usage to hours/day, hours/week or whatever. When the time is all used up, access get's locked.
Yo. Link with this instead.
[CORAL-LINK]/serpents-wall/
Perfect time for CORAL
Sorry about the yelling people.
I LOVE FreeBSD!!! I really can't wait for this release. Actually I can (perhaps unlike others), but it does excite me quite a bit. Just wish I had a MP machine on which to play....
Developers. Developers. Developers. You're all beautiful. Your work is wonderful. You code so we don't have to. Kudos, thanks, and appreciation to the Nth!
Same goes for the testers. FreeBSD wouldn't be where it is today if it weren't for you installing untested code on your machines and diligently reporting problems and fixes. Cheers to you brave, brave souls.
Shoutouts to the documentation crew! THE HANDBOOK ROCKS and has since I started reading it. What a value. It comes free! Free OS, Free docs. What's not to love???
Port maintainers. Put up your hands for these guys. A wide range of code setup for flawless builds with a single command.
Wizardry. Pure wizardry.
Get the CD and install on a spare machine. BEAT THE HELL OUT OF IT.
If you find a bug you will be a GOD in the eyes of those that want to run 5.3 production-style.
I vote wait untill that release is FULLY READY TO GO OUT THE DOOR. 5.3 is critical to further acceptance of FreeBSD, further commercial funding support, further legitimacy of the platform, and confidence in the developers/Release Engineering team.
If you need it now, run the RC. Unless a TON of people need 5.3 NOW, the developers should feel no pressure to get it out the door. They should feel pressure to get testers to find problems. They should feel pressure to find people that like inflicting damage on a running OS. Find those twisted individuals and give them a RC CD and a keyboard. Hear their stories.
Make it good as the worlds's eyes will be upon this relase and any further potential problems. RC2 should be fixing a much smaller list of bugs.
WE'RE STILL PLAYING AROUND WITH SCHEDULER CHOICES!! ???? I'd suggest more RCs. Blank CD-R media is CHEAP. Corporate downtime when bugs are discovered 1.5 weeks out from a release IS NOT!
Test Test Test Test Test. Beat the hell out of it - portinstall all ports. Rock the box and see how she holds. Try and crash it. Pound it from the network. Pull a live disk. JMP to a block of random bytes. Run 200 instances of your JVM. Start up as many desktop applications as possible. Try and kill your install and see how Beastie holds.....
5.3 is going to ROCK but SHOULD NOT BE RUSHED!!! If it needs time, by all means give RE-team time!
I hope we don't have to see a 5.3.1 release.
Perhaps the developers should require a certain variation in hardware platforms tested on or a given number of people to run it with no problems before final release.
(I don't run FreeBSD in a corporate environment or profess to know much about RE's testing process. Just trying to get in people's heads that extreme testing WILL make this release a HUGE success.)
On the Care and feeding of Permanent Nodes
and Information on FreeMail, totally private and anonymous email.
The 2nd and 3rd links are comments tagged onto the first.
Regular internet link to the page is http://freenet.org.nz/freemail/
Freemail runs on Freenet or Entropy networks.
[from the page.... apologies for formatting - lameness filter...]
FreeMail is a peer-to-peer Mail Server program (aka 'Mail Transfer Agent' or 'MTA') that makes it possible for you to send and receive email messages with unprecedented levels of privacy and anonymity.
Normal mailservers (such as Exim, Sendmail, qMail etc) communicate directly over the normal Internet, and send/receive all of your emails in plaintext for Big Brother and goodness knows how many companies to see. Even if your ISP uses encryption for transfer of mail, a simple court order (or bribe) is all it takes for your emails to end up in front of prying eyes, even many years after you sent or received them..
On the other hand, FreeMail encrypts your messages and hides them within the privacy-protecting Freenet network, where they are picked up and decrypted only by the people you're sending your messages to.
Features
A lot of thought has gone into FreeMail's design, to arrive at a secure, robust yet user-friendly system to satisfy your email communication needs.
So far, FreeMail includes the following features:
Evolution, Outlook Express)
People familiar with Freenet will also understand and appreciate the following features:
At this time, there are no third-party certification. The author is open to suggestions from users about how this should happen. For example, a web of trust amongst linked freesites, assigning 'karma' to mail addresses.
A
Here's a Freenet-only link On the Proper Care and Feeding of Permanent Nodes.
Contents include:
Changing Options
Running the Node
Monitoring the Node
Restarting the Node
Network Participation
Network Integration
Finer Points
Stable or Unstable?
Datastore Size
Bandwidth Allotment
Connection Limiting
When Things Go Wrong
Clock Skew
Quite helpful for tuning and optimizing your node once you get it up and running.
[Tips for running a successful Freenet node]
3 Most important ingredients:
Permanent connection
Bandwidth
Disk space
Without these you'll be complaining like the rest. Go ahead and set up a node, but optimum performance is a dream without all 3 above elements. Also, count on 2 days of letting it just run before you'll be able to get much done. After you're integrated things run much more smoothly!
If you're behind a firewall you'll need to know how to setup port forwarding. Windows install is the easiest, GNU systems should be trivial and there's a port for FreeBSD. I believe MacOSX can run it as well. If you can run a modern JavaVM, Freenet should be no trouble for you.
(About firewalls - if your $50 router/NAT/switch thingy cannot handle the hundreds of TCP connections Freenet can generate, you might want to either invest in a dedicated box (OpenBSD works well for me and allows me to prioritize traffic behind my interactive_ssh and vonage queues - Linux floppy distros should be fine too) or specify in freenet.conf to limit the number of open connections. Just be aware as connection tables can overload and distrupt the connection for all behind the NAT. Then again your $50 box may have no trouble at all. Port numbers are all random high port numbers making Freenet difficult to detect and firewall. Connections out will be made but the portforward is necessary for other nodes to connect to you. If nodes can't connect to you, performance will most likely be horrendous.)
If you just install Freenet and immediately try and download large files, you will be frusturated and give up. DON'T! Many freesites will not appear at all. NEVER FEAR! Let your node run in the background for a few days and get itself integrated into the mesh. Nodes that are more useful to the network (fast connection, large data store) will end up the most successful when downloading or uploading content. If you can't leave your machine running all the time or want to use freenet over dialup, fine, but your performance will not match those of others that can provide more to the network. Leeching is fine, it allows others to leech off of you - but leave your machine connected and Freenet's performance may end up suprising you.
Towards the beginning you may just want to start a number of downloads and count on many of them not completing - JUST WALK AWAY or do something else. Don't waste your time. By grabbing whatever bits you can, you'll increase the data in your own datastore and your connections within the network. If others find those bits from your node, your status will increase, more will connect to you and they will then be potential sources for more desired bits of your own. The better connectivity you've got, the more you will find. Leaving your node up at all times and keeping your datastore intact are the best ways to increase Freenet's performance (not just for you but for all).
THOSE PARANOID: I've been running my Freenet node wide open (no throttle) on my Earthlink cable connection in the heart of Raleigh, NC for some time. No threatening letters or trouble, my Vonage works fine (I do use pf's ALTQ) and those in my house have no trouble with connections, download or upload speeds)
For those that are already on Freenet and trying to download large files, one tool is critical. FUQUD (Freenet Utility for Queued Uploads and Downloads). Find it. Use it. Fred (the built in web interface) isn't going to cut it.
Regarding disk space. Unless you've got around say 2Gigs to dedicate to a node, your node may not perform as well as it could (200M is practical minimum). Consider the value you choose to be relatively permanant. You can't trade it with other uses - you build a datastore and that's the size, unusable for your MP3's or ogg's for example. They don't grow or shrink. You s
I realize onboard soldered electrets may be a problem but if you've got recorders that are using external mics this could work. This is unlikely but I thought I'd mention it anyway. (I wish more "voice recorders" would provice external microphone inputs....) This method would throw away much chance of gathering data on when the recorded snippits were made however- not sure it that would matter.
Here's my suggestion. Feel free to ask for details by emailing [cyrus at 80d dot org].
I have a very rough idea here. Buy or make some sea anchors. Sea anchors are very high drag in the water and are used to limit boat drifting in windy conditions. They are basically a large tapered piece of cloth (like a bucket) with a hole in the bottom. They collect water in a big hole and make it flow through a small hole at the other end. This is just drag in the water. The trick is to make one so that it can be converted between a high-drag and a low-drag state. Pull on one line (at the big opening, via a few connection points) and it's high drag. If you pull the small opening through the middle and release tension on the big opening connection, the material can be forced inside out and will then hopefully offer little resistance. You could also somehow have it move sideways through the water, offering little resistance.
What you then need to do is have one on each side of a pully type gear mechanism. As the water pulls on the high-drag anchor, you get a chance to make some electricity (ratio gear drive to a generator) while you reel the other one in. Switch modes, put your gear drive in "reverse" and have the other pulled out. This will reel in the opposite anchor as you drive your generator. Rinse and repeat.
Another option would be to attach a number of these "underwater sails" to a loop. Configure so they pull on one side and are collapsed on the other. This would give you continuous power.
The anchors should be positioned to be in the highest flow possible. If they float to the top or sink too much you could attach a float or weight (or both) to properly position them under the water.
All that's left is implementation. I'd be glad to help further with design. This could even work in the winter underneath an icy cover.
If not to power a generator, you could perhaps power a water pump that would raise the water to a high enough head that you could power a paddle wheel at high velocity. This could be attached to an alternator. You can find plans for these with home power people. Be sure to raise your voltage as high as possible before transmitting it any distance and use the largest diameter cable you can afford. Vdrop at 12 or 24 volts can be very large (relatively), wasting much of your effort.
Best of luck! Cool project!
Walking. This is a wonderful activity.
Walk around. Talk to people. Ask them questions.
Exercise. "Street level" social/cultural interactions. It's all there. Just get up and go. You'll find people with interests that will keep you busy. Coffee shops. Book stores. The street corner. Make random friends. Exchange numbers. Get together next Tuesday here or there. Talk more. Get introduced to friends, friends of friends, etc.
Ask. Ask. Ask. And you shall learn.
Offtopic:
You may want to consider your use of midnight as a good time to run scripts.
Many people are still awake at this time, perhaps working from home, trying to beat a deadline, etc. Cron jobs using resources at this time could be frusturating, making a long night even longer.
You may want to consider moving jobs to 2 or 3 AM instead.
Thank you.
When in this country might I expect to see a digital public notary? 5 years?
Present a document, and the notary wraps the contents with a digital signature and timestamp, similar to the way GPG clearsigning works. That would be pretty neat.
I'd pay by the megabyte for somebody to timestamp stuff for me.
If you are suspected of a crime in which officers of the law have some DNA evidence, you may be offered a glass of water or a piece of gum in the interviewing room. There is a good chance this is an easy way to get a DNA sample from you if they do not already have one.
Take the gum, but think twice before spitting it in the trash.
I'm curious when we may have access to a government approved digital time-stamping service?
Ever like to prove to somebody that a document existed at a certain date? "Mail it to yourself. It's got the postmark."
Well, besides the fact that this ploy would never stand up in court (it's too easy to steam the flap open), it's a good idea.
How about the USPS providing a digital document time-stamping service? What good time-stamps are availible out there that would stand a test at the patent office, for example???
If you're smoking in your dorm room, a 'oney', or 'one hitter', is probably the least conspicuous means of getting certain psychoactive chemicals into your blood, but the use of the tube as described above need not be limited to such low quantity imbibing. Water pipe, steamroller, Jay or Joint, vaporizer, chillum, blunt, or iBong smoke could also be blown through one of these things and work equally well:)
Used dryer sheets. Tape them over your inlet vents in your case/power supply/whatever. Watch the temperature.
Make a SMB share somewhere containing all your dotfiles and things you want to get to from elsewhere. This may or may not work very well for other types of files/documents/etc.
.* files in ~/ to the copies in ~/dotfiles
.login) DON'T MOVE THESE AS DESCRIBED ABOVE
.bashrc, .vimrc, .muttrc, etc. onto the master SMB share.
In each homedirectory on each real machine:
$ mkdir ~/dotfiles
$ cp (or mv) dotfiles to ~/dotfiles
$ ln -s all the
(omit any files that are specific to the machine and which you don't want to use the master for)
In a shell-login script (.profile or
Put a master copy of your
$smbmount [master homedir] on top of ~/dotfiles
all the symlinks will then point to the mounted homedir.
On logout, unmount the remote SMB directory (or directories, if you'd like to adapt the idea for other types of files) and rsync (or unionify, or codafy, cvs, etc.) any changes from the master back to ~/dotfiles. This way, if the next time you login to that machine, the master isn't availible, you've got at least a semi-current version of your files (via the symlinks). If you want to keep a file local, don't symlink it.
Works under windows or uni*. Isn't nearly as complex as some other ideas mentioned. Isn't perfect, so lay off. Just popped into my head..... Adapt as needed, you're smart.
The free Netpbm toolkit includes a pnmstitch program which can do what you describe (lest the fact that right now it can only join two photos, left and right). It's a relatively new addition to the suite. These operations can be easily strung together to join multiple images (via pipes, most operations with these tools employ the use of stdin/stdout, though other options are availible).
These tools are the default utilities for mainipulating images serverside with the Gallery web based photo album.
But for all of us who need not install from a floppy, can cvsup the RELENG_4_8_0_RELEASE tag, and buildworld without waiting for the floppy issue to be resolved, am I correct?
Lest you be refering to tri-state logic...
Would you demand a full refund for the dental work?
I'd ask 'em for a mouth full of gold crowns if your tongue doesn't regain sensitivity in another month. If palladium, or a base-metal alloy (nickel or chromium) are more your style, those are availible too!
This can be easily done in the configuration file. Upload and download rates can be throttled. Firewall's your own problem.
Anybody know if this could be done in a LKM (loadable kernel module)?
I know I'm off topic - just looking for an answer here in a low scoring reply.
BTW - FreeBSD is Unix.