Wednesday, 23 November 2011

Guess who's back?


My name is Mobeen Iqbal or Mo for short, and I have recently taken on the roll of Vinux project manager. As many of you may already know, on the 8th of October 2011 Tony Sales, the founder of Vinux announced that he would no longer be able to continue his involvement and work on the Vinux project. Any voluntary project can take up a lot of someone's personal time. Though we are all extremely saddened by Tony's departure, we'd like to take this opportunity to thank Tony for all his hard work both in starting Vinux and developing and maintaining Vinux releases. The amount of work and dedication he has poured in to Vinux is admirable. We wish him all the best for the future and welcome him if he wants to continue work on the project at a later time.

I would also like to thank everyone for the over whelming amount of support and encouragement on and off the Vinux lists which I have received to take on the roll of project manager over the last 5 weeks.

Though at times our mailing lists have been some what quiet, I can assure you I have been making my way around the Vinux teams, users and familiarizing
Myself. Rob Whyte is currently working on Vinux development and taking on the roll Tony was filling in producing updated Vinux releases. However, we are looking to have our build process automated very soon; this should make life a lot easier for people working on the project. I'd like to say a big thanks to Rob for his time in producing updates to our current stable release of Vinux, liaising with developers to iron out bugs and helping out all teams in general. I'd also like to say a huge thanks to Luke Yelavich, our Lead Tech who is currently spending hours of his time working on getting our new build process up and running.

Vinux is continuing to improve and we have not lost any drive or determination. We still have a small core of dedicated contributors who work on Vinux in their own time.
We have been conducting team meetings and they have produced a lot of good ideas and we have started to implement them. Some of the changes we hope to make over the coming months include:

We intend to start a blueprint Vinux project on Launchpad.
This will be a place where people can start an idea and others can follow the progress or provide feedback/suggestions for improvement.

We now have a Vinux Ventrilo server which is push to talk voice chat.
We are implementing an open door policy on our Ventrilo server where Rob and I plan to be available two nights a week for people to drop in and chat with us.

We are taking another look at Vinux media, such as CD's and USB pen drives as well as the possibility of T-Shirts, caps, mugs even stickers and are hoping to setup some kind of distribution network across the world so people can purchase media in their country of residents. We are also in the process of implementing a global contact scheme for users who need on the ground Vinux support.

We are setting up a Vinux YouTube channel so look out for videos being uploaded soon.
If you have a topic that you feel has not been covered or needs revisiting we welcome your input. Also if you would like us to cover a specific topic or provide a walkthrough for a specific app in a video, please don't hesitate to get in touch and we will see what we can do.

We still need more people to be a part of our various Vinux teams, if you have some time let us know what area you would like to contribute in and please
join up.
Although there is no pay, there are many rewards and all contributions how ever large or small are welcome and much appreciated. So far our teams consist of web development, testing, documentation, public relations and the development team.

We are looking in to implementing a donations system on the website.

We are also in the process of updating our user manual and switching to a new wiki platform which should be more intuitive and easier to navigate.

Hopefully over the coming months, we will be demonstrating Vinux at various exhibitions’ across the world, please keep an eye on our news page or on the email lists just in case we're in your area.

You can also buy Vinux computers or laptops, or have Vinux installed on your machine or pen drive for you. Although these services are only available in the UK at present, we are looking in to providing them internationally.

So, where is Vinux going, glad you asked!

Vinux 4.0 is our next long term support release, or referred to as LTS. This will be based on Ubuntu 12.04, and will use the Unity desktop instead of the gnome desktop. Our very talented lead tech Luke Yelavich has been working tirelessly to build a Vinux build process such as the one used by Ubuntu. This offers us many new features that our previous manual build process did not allow, such as extra language support and WUBI support so you can install Vinux to your computer and boot from it without partitioning your hard drive.

For those who are really not sure of Unity we will be having a Vinux 3.3 development build in preparation for Vinux 4.0, this will be for testing
and staging for the next LTS.

We will also be releasing an update to Vinux 3.0.1 shortly, V3.0.2 which is still based on Ubuntu Lucid.

The next 12 months should be an exciting time for us all. I'd like to thank everyone for their help and support. Both the various teams and developers working behind the scenes to keep the project alive and producing releases, and of course you, the users. Its you that make Vinux what it is today. With your input, Vinux will hopefully continue for years to come. Let’s make Vinux the number one distribution for anyone with a disability and have a great time while we're at it!

Saturday, 8 October 2011

So Long and Thanks for all the Fish...

I regret to inform you that due to serious personal/family issues that I would rather not discuss publicly I will be unable to continue working on the Vinux Project (or any other development project) for the foreseeable future, if ever. I am very sorry for all of the problems and difficulties this might cause but I am sure there is now enough of a community of developers to continue with the project without my personal help or advice. I think there are already other members of the development team who already have admin status for most of the lists, repos and websites etc. If there are any other resources and/or passwords etc developers need from me please contact me personally and I will help with any hand-over to the best of my ability. I will be disabling the server in a few weeks time when the current contract runs out. Once again I am very sorry to be making this announcement and would like to thank all of the people who have contributed to the Vinux Project over the years without whom it would just not of been possible. I believe the Vinux project will continue for a long time and will go from strength to strength, until hopefully all mainstream distributions are fully accessible...

drbongo (signing off)

Saturday, 9 July 2011

A Tale of Two CD's:

I haven't posted anything on the blog for months! Not because of a lack of interest, but because I have been so busy preparing for the release of Vinux 3.2 and rather surprisingly the release of Vinux 3.2.1 just a week or so afterwards. It has taken a lot of effort to adapt the Vinux Build Scripts to work with Ubuntu 11.04 'Natty Narwhal' and we have introduced a number of new packages and scripts. Vinux 3.2  was a cutting edge release featuring the latest versions of Orca and Speech-Dispatcher from the daily build repositories  available as CD and DVD in both 32 and 64 bit editions. The DVD version provided the same software as the CD but with the addition of libreoffice and some non-free multimedia codecs etc. The default desktop was Classic Gnome 2.x but Unity was also available from the GDM login screen if your video card supports 3D. This release included the Pico TTS voices for the first time in addition to Espeak, the Epiphany Internet Browser and new built-in keybindings to quickly organise multiple windows with x-tile. It also featured some new packages including Orca-Teacher and  Talking Clock. This version also played a system bell when the isolinux boot screen appeared allowing you to select different boot options including an experimental 'toram' mode. There was also a Vinux 3.2 PLUS edition which features lots of extra packages for partially sighted users. I  also managed to fit more text tools on the CD edition including: sox gpm screen, splitvt, figlet, cmatrix, txt2html, html2text, pdf2svg, pstotext, units mc, trash-cli, vrms, dict, sc, htop, linuxinfo, w3m, elinks-lite, urlview, finch, axel, calcurse and tdl. However, Vinux 3.2 had a few bugs including: Selecting the Cicero speech synth would crash Orca and you would have to run: orca -t to reset everything back to the way it was. The x-tile keybinding to 'quad tile' open windows was set to 'win+alt+v' by accident - to correct the user had  open the keyboard shortcuts manager and re-assign it to 'win+alt+q' - then the 'vertical tile' option would work as well (win+alt+v). The most serious issue was that Pulseaudio still crashed after boot on a small number of soundcards.
So because of these issues we have now released Vinux 3.2.1 - the main difference between this and the recently released Vinux 3.2 is that by default it boots with Pulseaudio running in 'user' mode rather than 'system' mode. This prevents pulseaudio from crashing at boot on a small number of sound cards, but it means that speakup is not available from the live CD or immediately after installation. However, there are now two simple commands for switching Pulseaudio from user to system mode in conjunction with a reboot of the machine. To switch to system mode and enable speakup, simply run: sudo pulsesystem - in a terminal and to switch back to user mode, simply run: sudo pulseuser - in a terminal. This new release also includes an accessible Zenity front end for Unetbootin which allows users to install Vinux to a USB pendrive with persistent storage. Users who have already installed Vinux 3.2 can upgrade to this version by simply running the following three commands in a terminal:

tar -zxvf upgrade_script.tar.gz

sudo ./

There are two new scripts included in Vinux 3.2.1, usbinstall and cdburn. These are accessible scripts for installing Vinux to a USB pendrive, and for burning a CD/DVD then checking the md5sum of the burnt CD/DVD. They are still prototype scripts with no error checking so I have not included them in the menus yet, they must be launched by pressing alt+f2 and then typing usbinstall or cdburn - then pressing enter.

USBinstall - Instructions.

1. After launching the usbinstall script a zenity file selection dialog will appear. Use this to select the ISO you want to install to the pen drive.

2. Next you will be asked to enter the name/path of the USB pen drive. this will usually be something like /dev/sdb or /dev/sdc - the default entry is /dev/sd - so all you have to do is type one letter 'b' or 'c; etc and press enter. However make sure you provide the correct letter as you could potentially wipe a partition or hard drive if you use for example /dev/sda. The easiest way to find the correct letter is to run 'df' in a terminal after inserting the pendrive - it will be the last one in the list.

3. Now you must enter the size of the persistent storage file in MB - the default value is 9999 which will just use all of the available space (up to 10GB) but you can use less if you want to.

4. Next you must decide how many seconds you want to set the notification for - this will pop up an alert when the build has (probably) finished. the default setting is 1200 (20 minutes) which is a safe setting - if you reduce this there is a chance that when the notification goes off the installation will not have finished. There is no way for us to detect when the installation is finished yet - so this is just a guess, most installations take between 10-15 minutes, so set it for longer if you want to be extra safe.

5. You then have to enter your password and then press enter for the process to start. Do not disconnect the pendrive or make any changes to it until the notification appears. When you are told the process has finished press enter to quit the program, and then remove the pendrive.

CDburn - instructions

1. When you launch the application a Zenity file selection dialog will appear, use this to select the ISO you want to burn. The application will then calculate the md5sum of the ISO file.

2. Next you have to enter the path to the cd/dvd burner, if you only have one optical drive/burner this will be /dev/cdrom (which is the default entry) otherwise you will have to add the appropriate number e.g. /dev/cdrom1 or /dev/cdrom2 etc. Make sure the blank disk is in the drive before you do this.

3. The CD/DVD will now be burned. when it is finished the draw will eject (in most cases) and you will be asked to reinsert the CD and click OK. make sure you close the draw and let the CD/DVD spin up before you click OK (although I have built in a 30 second delay).

4. The application will now calculate the md5sum of the burnt CD/DVD and tell you whether the burn was successful or a failure. When you click OK the CD/DVD will be ejected (in most cases). Close the draw and click OK to exit.

Wednesday, 16 March 2011

The Two Towers: Unity and the Gnome Shell!

In the aftermath of the release of 3.0.1 there has now been time for the dust to settle and I have been surveying the way ahead (does this make me Aragon?). We have achieved a great deal over the last three releases and I think we have done pretty much everything it is possible to do given the number of people involved and our dependence on upstream projects we can do little to influence. Vinux 3.0.1 is probably the most stable and accessible release we have made, in spite of the small number of people who have had problems with lack of sound or having a Mandarin voice variant by default. One of the areas where the most work is needed is with the performance of Orca with Firefox. This is a complex issue and will take a lot of work to sort out. The vast majority of this work lies with the Orca team who are also doing a great job given the small number of (volunteer) developers involved. Another area where Vinux/Linux Accessibility could improve would be the availability of a wider variety of voices, although I think much of this is down to what you are used to rather than which is the best voice - a very subjective issue. Unfortunately these are the least of my worries at the moment because we face an assault on accessibility of epic proportions from two sources in the very near future. In April Ubuntu will switch to the Unity desktop and Gnome will switch to the Gnome Shell with the release of Ubuntu 11.04 (The Nasty Narwhal?) and Gnome 3.0 respectively. Both of these desktops rely heavily on 3D technology and at the moment accessibility seems to be almost non-existent. There has been talk about Ubuntu making the system fall back to Gnome if there was no 3D acceleration but it seems that both Ubuntu and Gnome are now creating special 2D versions of Unity (using QT) and the Gnome Shell. Now although accessibility will improve over time this effectively means that the Gnome 2.x desktop is now dead in the water. Most distros will switch to the Gnome Shell and support and development for the existing desktop will wither away. So from April onwards there will be a major obstacle to the continued development of Vinux. Firstly it is likely that most of the existing buildscripts will have to be completely rewritten to work with Unity and the Gnome Shell (if that is actually possible), people without 3D accelleration may have problems running the lower priority 2D backup versions and as usual accessibility will have been put backwards several years and be playing catch up again - because of changes to the graphical system which have no benefits at all for a visually impaired user. On top of this, whilst the appointment of team coordinators has taken a significant amount of responsibility off my shoulders, we still don't have enough core developers working on the build scripts and it is simply too much work for one person to do, in addition to holding down a full-time job and trying to have a 'normal' family life (whatever that means!).

So we need to come up with a strategy for dealing with these issues. In terms of core developers I can see a solution of sorts. I need to recruit some apprentices so I can teach them the ways of the force, I mean bash scripting and how the whole process works. That way in time the workload of the core development can be shared; either by taking turns to make a release, working on different sections of the build process or even making completely separate versions or flavours of Vinux. So with this in mind I intend to work on a set of tutorials to explain how the buildscripts work and how all the contents of the Vinuxscripts repository fit together to create the final version. Having read this people can then decide whether they are willing and able to become a Padawan and learn the ways of Bash. That is the easy bit. More difficult is which way to go in the future. Do we stick with Ubuntu and see what Unity has to offer? Do we try out the Gnome Shell and see if that is any more accessible than Unity is? Do we try to keep Gnome 2.x on a life support machine for as long as possible while Unity and the Gnome Shell evolve? Do we try out other desktop environments like LXDE and XFCE and try to make them accessible? Do we stick with Ubuntu or switch to Mint, Debian Mint or just pure Debian? Do we switch to a rolling release model or stick with a reinstall every year or two? I have to say, my gut feeling at the moment is to jump to Debian and start investigating XFCE and the possibility of a Debian based rolling release. So I would ask you to have a good think about all of these issues and we will have another Vinux Conference on IRC at the end of the month to try and make some decisions about the direction we go in.

Sunday, 13 March 2011

Vinux 3.0.1 Released!

The Vinux 3.0.1 release based on Ubuntu 10.04.2 LTS is now available for download. This combines all of the accessibility of Vinux 3.1 with the stability of Vinux 3.0 as well as a few completely new features. In addition to the existing three screen-readers (Orca, Speakup and YASR) this release also includes Emacspeak 'The Complete Audio Desktop' pre-configured and ready to go out of the box. You can now create audio books from text-based files using our exclusive Audiobook Converter package, browse our new HTML based Vinux Manual to help get you started, install the latest version of Libre Office using an EasyInstall script, and customise your desktop experience with Ubuntu Tweak. It is initially available as a 32bit CD, a 64bit CD, a 32bit DVD version and a 64bit DVD version (which both comes with Libre Office and non-free multimedia codecs pre-installed). The VMWare virtual edition, and a 32bit USB version will be available shortly. An upgrade script has also been released that allows people to upgrade from Vinux 3.0 to 3.0.1:

In order to update run the following commands in a terminal:

git clone git://

cd vinuxscripts

sudo make install

sudo buildvinux

This will start the interactive Vinux buildscript which runs in a terminal, it will beep when it expects input from the user. I have tested this script on Vinux 3.0 and it upgraded without any issues, but if you have installed software which I haven't I cannot guarantee that it won't mess that up, so make a backup of everything before you upgrade. I know that the script works, but I am not sure how usable it is at the moment because of the amount of data which will be read out. Most of the questions are straight-forward - when emacspeak is installed you will have to select 'espeak' and then 'none' for hardware synths. When the script has finished running you should restart the computer and try out your shiny new Vinux 3.0.1 - I would like feedback on the usability of the script - I have also uploaded a simplified non-interactive version of the script to the mailing list which just asks for your username and doesn't install emacspeak.

One or two people have found that after the installation of 3.0.1 Orca and Speakup start talking gibberish. In fact it is trying to read English text in Mandarin. We do not know why this has happened, but we suspect that it is to do with a corrupted ISO, CD or a unreliable CD drive. If this happens you can fix Orca by opening the Orca Preferences Manager and selecting another voice. We recommend selecting the English(en) voice if you want the default voice. However, to fix Speakup you will have to run:

sudo rm -f /usr/share/espeak-data/voices/zh

This will delete the Mandarin voice, or try replacing and renaming the 'zh' voice file with your preferred voice from the /usr/share/espeak-data/voices/en/ directory.

As always we do not recommend that users update any packages after installing Vinux unless they have a very good reason to do so. Installing unnecessary updates can break your system and it may be very difficult or impossible to repair if you lose speech without performing a complete re-installation. Although not invulnerable to viruses and hacking, Linux is significantly more secure than Windows and unless you are running a server with open ports and/or installing packages from untrusted third party sources, you are unlikely to have any major security issues (although we obviously can't guarantee this). If you are running a server with open ports then you should install security patches when they are available, and if you really want to try a new version of a specific package then only update that individual package, don't just install all of the available updates. If you do decide to install updates despite this warning then please make a backup of your files and/or installation before doing so.

I will now be having a break from Vinux Development for a few weeks, which will give me time to reflect on how the project is going and in what direction it should take next. Thanks to everyone who has contributed to this release...

Sunday, 23 January 2011

Vinux Conference a Success!

I am pleased to say that the online meeting to discuss the future development of Vinux took place last night and we had about thirty participants on and off, although some people had a few teething problems using IRC for the first time. It was decided that Vinux would continue to be based on Ubuntu for the time being, but that we would look into the possibility of building upon Debian Mint and/or Squeeze in the meantime, just in case Ubuntu 11.04 and/or the new Unity desktop and the Wayland Display Server cause any unexpected accessibility issues. Ten members of the Vinux Support/Development List were also duly elected as Team Coordinators: BuildScripts - Tony Sales, Software Development -
Don Marang, Testing - Nimer Jaber, Website - Mobeen Iqbal, Publicity - Storm Dragon, Fundraising - Arianna Sepulveda, Documentation is shared by Nimer Jaber, Krishnakant and Merrill Woolnough, and we accepted offers for Translated Versions of Vinux from Kris (Dutch), Ferdinand/Joey (German) , Cleverson/Rui (Portuguese) and Burt (Spanish).

Sunday, 16 January 2011

Vinux IRC Meeting Agenda:

Event: Vinux Development Meeting
Date: Saturday 22nd January
Time 21:00 GMT
Location: #vinux


1. Development Roles

As always the main problem faced by the Vinux Project is the relatively small number of people who are willing and able to contribute in some way. I would like to recruit more people to help with development and try to formalise the different roles. As I see it there are six distinct roles, which could assigned to an individual or shared between a small team, and of course there is nothing to stop one person performing more than one role if they wish. The six roles are:

A. Build Script Team - Writing and testing the build scripts then producing the final releases of Vinux.

B. Software Development Team - Writing and testing new packages then adding them to the Vinux repository.

C. Testing Team - Testing individually assigned packages in the alpha,beta and release candidates and passing the feedback to the build script and/or software development team.

D. Translations Team - Creating Vinux isos in new languages once the build script is finalised and uploading them to the website and/or mirrors.

E. Website/Hosting Team - Maintaining the website, wiki, mirrors, mailing lists and publicity etc.

F. Documentation Team - Writing how-to articles for the Quickstart Guide and the Vinux Manual.

Initially we just need people to volunteer to be part of a team, and depending upon the number of responses we get, I would then like to appoint a member of each team as the coordinator of that team.

2. Which distribution should we base Vinux on?

This is another issue which crops up every year - should we stick with Ubuntu, or switch to another distro. Ubuntu offers many advantages such as hardware compatibility, but it has a very fast release cycle and is planning to make some major changes in its next release (Gnome>Unity and Xorg>Wayland) and we have no idea how this will effect accessibility. There are other distributions we could base Vinux on including: Debian, Linux Mint and PCLInuxOS - however the one that holds the most promise at the moment is Debian Mint. This offers the hardware detection of Ubuntu, with a rolling release based on Debian Squeeze, meaning once installed there shouldn't ever be a need to reinstall. So the question is: do we stick with Ubuntu, Switch to Debian Mint or develop both in parallel initially to see what happens. The answer to this will depend largely on whether we have enough people to support two versions or not, and of course whether people think this is a good idea or not.

3. Any Other Business