 |
| Menu |
more |
| to |
| come |
 |
 |
|
 |
Here are some addons that I've made to keep my Freesco box enjoy the cycles while blocking unbidden packets.
Jan 2004 With experience from some packages, I've taken the time to revise my code in the published packages. I did smash some bugs and added some new ones ;-) I also added some new features. All packages has got a help and a status command. The help, -h, lists available commands and status, -s, shows if the service is activated or not.
Note 1: Due to limits on my ISP's system and my knowledge about it, I am not able to keep track of downloaded files. After downloading you are kindly requested to send an email to confirm download. It would assist in giving a picture, if these pages are of any use or not.
Note 2: All your comments, questions and support of any kind are welcome.
atdaemon 0 d/l ?
Guessing you, like me, have things you want to happen at a certain time. Often this is at times when you don't actually are sitting at the box. There is a package, cron, for Freesco. I think it is to big and powerful for my needs, so I started looking at the included at daemon. Did find out that there is an update. Starting from that and included ability to recognize difference between weekdays and weekend and some other things. Here is a description of the modified at daemon. Suitable for running of a floppy.
dnetclient 0 d/l ?
I got interested in having something to count the idle cycles on my Freesco. Since I earlier found the distributed.net client to keep my w311 box busy while it ruminates, I did have a new look to see if/what was available. Here is how to install a dnetc client. A hard drive is required.
pingers 0 d/l ?
In my effort to get a network up and keep it connected I needed some tools in support. Maybe #2 can be tweaked to work from a floppy, but if all are used a hard drive is required. Here are some pingers for different tasks:
* at regular interval for a single host, reports anomalies to log and mail
* from a file, showing hosts on or off
* from a file, showing host and status
seticlient 0 d/l ?
Since the start of the SETI project I've been a member with at least one box crunching WU's. When the Freesco box came into my communication tower I thought it be time to get SETIathome doing some work in the box running 24/7. There was a package made already for Freesco, which I tried. But due to some shortcomings in the construction it would not run properly. It misdirects the workfiles to
/. This makes the client unable to track it's progress. All workfiles should be placed where the client is. I struggled some time with my design of how to manage the SETIathome client and finally got something running SETI@home
. A hard drive is required. BTW, if you load your Freesco box with many packages, it's not advisable to also have the seti client running. You have been warned.
timezone 0 d/l ?
To have a working timezone on your Freesco box has been a wish since it's inception in 1999. Now there's a solution, also on a floppy, space permitting.
keyboard 2 d/l
Many have wished for a swedish keyboard driver working as they are used to. It's available now. Suitable for a floppy, space permitting.
autostart 0 d/l ?
A router shall always be available and not need any manual handling, unless you want to. A power outage at the wrong moment might make your Freesco file system read-only and complaining about it. Maybe you even set up your box to be running without keyboard and monitor connected. With a little work you can configure your Freesco to do its duty as long as there is power in the cord. Configurable on a floppy also, space permitting.
uptime
To be of any use the Freesco router should be available without interruption. A common term is uptime and it's presented as days of zero failure. After installing the patched kernel my router behaves quite good. If I remember right someone reported having a Freesco router up for more than 600 days. He even moved during this period. An UPS and careful handling of the hardware made it possible.
 |