I just created a file called /etc/modprobe.d/zte-mf633.conf

and added the following to it:
options usbserial vendor=0x19d2 product=0x0031

and then reboot with the modem in to test it works on a fresh boot. If you insert the modem *after* you have booted, you may have to unmount/eject the cdrom that it is detect as prior to it being detect in connection manager. The above may also interrupt with other usb devices, though my storage key still works and it’s all I need for now.

Then it will display as a 3G card and you can use the network wizard to configure it.

Two things to note.
1. You have to “register/signup” using a Windows computer – which I had a lot of problems with and had to end up doing it in store
2. I forget now, but it seemed noteworthy.

TonidoPlug is a tiny, low power, low cost home server based on the 1.2 GHz Sheeva processor that allows you to access your applications, files, photos, music and media from anywhere (Powered by Tonido).

TonidoPlug comes pre-installed with powerful Tonido Applications – Photos, Jukebox, Webshare, Workspace, Thots, Explorer, Torrent and Search – all running on top of embedded Ubuntu Jaunty Linux OS. Additionally, TonidoPlug can be extended by installing new applications from Tonido App store.

Not sure if we are going to see them in Australia anytime soon, and if any adapters will be needed

Here’s a Youtube review of the TonidoPlug:

Technorati Tags: sheeva, tonidoplug, p2p, Torrent, Jaunty, Ubuntu, Embedded

So I decided to find out what it would be like to do some web programming in it. I learned a bit about asp.Net in the process and mono also.

So first thing I did was:

$ cd /usr/share/doc/boo/examples/asp.net
$ xsp2

and then from your browser you can run any of the “inline” samples

http://localhost:8080/InlineBooButtonClick.aspx
http://localhost:8080/InlineBooExpression.aspx
http://localhost:8080/InlineBooHelloAspNet.aspx

but if you try and run one of the code behind samples, you get something like this:

Description: Error parsing a resource required to service this request. Review your source file and modify it to fix this error.

Parser Error Message: Cannot find type Boo.Examples.Web.YourName

Source Error:

Line 1: <%@Page Inherits=”Boo.Examples.Web.YourName” %>
Line 2:
Line 3:

The problem is the the boo source code needs to be compiled and the dll’s must be placed in a bin directory in the folder you are running xsp2 from. There is a nant build script there but after trying to hack it to get it to build, we worked out it was easier to just compile manually.ie:

$ sudo mkdir bin
$ sudo booc -t:library -o:ScriptRunner.dll ScriptRunner.aspx.boo
$ sudo cp ScriptRunner.dll bin

from your browser:

http://localhost:8080/ScriptRunner.aspx

You can then use this to play around with some boo as if it were the booshell (booish)

Thanks to Cedric for helping me out in IRC on this.Technorati Tags: mono, python, boo, language, xsp, ubuntu, linux

We are going to use three command line tools for this: aumix, which and cron. We are also only going to set things up so the commands are run under the user account, rather than as root as cron used incorrectly can open up some security issues.

so, to get started try and run:

:~$ aumix

and if it’s not there, try

:~$ sudo apt-get install aumix

for Debian / Ubuntu or

:~$ yum install aumix

for Redhat / Centos / Fedora

Now that we have aumix installed, we want to find out the path to the executable as Cron doesn’t always use our environmental variables to find executables on our path. So type:

:~$ which aumix
/usr/bin/aumix

We can see it’s in /usr/bin/aumix

So, kick-off your music player and try playing some music or other audio then run the following commands:

:~$ aumix -v 0

then

:~$ aumix -v 100

The first command should have dropped your volume down to 0% and the second command should have taken it back to 100%. Now that we have that working, let’s add it to cron. For myself, I don’t want to be disturbed between 11pm and 7am, so following cron’s options, we have

minute-hour-day-month-weekday-command – and we use 24 hour format. An asterisk means run at every instance of that time period, so:
* * * * * would mean every minute of every day, every month and
0 0 * * * would mean at midnight every day.

For myself, I want the 23rd hour of every day, every month for the volume to be set down and I want the 7th hour of every day for the volume to be returned to 90%. So we add this to our crontab:

0 23 * * * /usr/bin/aumix -v 0
00 07 * * * /usr/bin/aumix -v 90

To do so as a user, we use:

:~$ crontab -e

Now if your default editor is vim / vi and you have never used it before, you will need to learn a little vi before we get started. When the editor opens, type to enter insert mode allowing you to copy and paste the above code and modify for your needs, when you are finished editing, press esc then VV to save the file and exit.

:~$ EDITOR=/usr/bin/nano

and then run

:~$ crontab -e

:~$ sudo apt-get install gnome-schedule

for raising and lowering the volume.

Technorati Tags: volume, linux, crontab, automation