On Fri, Dec 5, 2008 at 10:24 AM, Dieter Plaetinck wrote:

Gerhard Brauer wrote:

...

Hi,

i would like to offer my help to the ISO build and test procedure. I'm sure i have the time and skill to help on archiso and installer skripts.

Currently i will look deeper to get the isolinux thing get running as a maybe alternative to grub-legacy. Also to get the keyboard/font selection and the time zone setting better integrated in the installer.

Also if there are concrete things to do feel free to contact me.

Regards Gerhard "gerbra"

I'm currently working on a totally refactored installation framework/installer. It's not an official project yet, but the arch devs agree that it looks good and Aaron wants to put it on the installcd. See http://www.nabble.com/Fifa:-Flexible-Installer-Framework-for-Arch-linux-td20...

Any help is welcome (testing, code review (lots of open TODOS), conceptual review, ...) See the AIF packages http://aur.archlinux.org/packages.php?K=aif - aif-alpha_0.5 is the least bleeding edge but most stable. - aif-git should also be stable and more uptodate - aif-blockdevicerefactor-git is atm very unstable, i'm in the middle of a big refactor there.

PS: I think the keyboard layout selection should be outside the installer, because the shorter the command the better. I prefer to type 'km' in a foreign layout then /arch/setup (yes, even with tab completion)

I'm going to do a complete re-write of the ISO scripts. I'm not happy with the route I took them, so want to redo them. What is there works though, even if it is a tad crappy. If you contact me over jabber sometime tomorrow, I will probably be working on the ISO stuff. As for the installer vs Dieter's installer: the next ISO will have the stock installer on it, but I am thinking about adding the AIF stuff as "experimental" so we can test it out.

Angel Velásquez schrieb:

...

If you contact me over jabber sometime tomorrow, I will probably be working on the ISO stuff. As for the installer vs Dieter's installer: the next ISO will have the stock installer on it, but I am thinking about adding the AIF stuff as "experimental" so we can test it out.

What about support for accesibility people?, a friend (FlaPer87) and i can help with some thoughts for accesibility stuff.

There was a thread about that a while ago, and I think it's interesting. Might be worth a look.

"Aaron Griffin" writes:

On Fri, Dec 5, 2008 at 12:00 PM, Angel Velásquez wrote:

...

What about support for accesibility people?, a friend (FlaPer87) and i can help with some thoughts for accesibility stuff.

Just tell me what needs to be done. Is it a simple matter of adding some packages to the ISO, or do certain things need to be run on startup as well?

The following applies to spoken output for the blind. Not sure about other sorts of accessibility. Certain things need to be run on startup. Sound should be unmuted, and volume should be set to something reasonable. Perhaps: amixer set Master 80% unmute amixer set PCM 80% unmute We need a daemon and a couple of kernel modules. The modules are speakup and speakup_soft, and the daemon is called espeakup. I have PKGBUILDs for these in unsupported: http://aur.archlinux.org/packages/speakup/speakup.tar.gz http://aur.archlinux.org/packages/espeakup/espeakup.tar.gz The binary packages espeak and alsa-utils are used, and they bring in several dependencies. Most folks won't want speech at boot, so it should be optional. Perhaps a script could examine /proc/cmdline and start speech if the user supplied a certain argument to the bootloader? -- Chris

"Aaron Griffin" writes:

But how does a blind person reliably edit the grub prompt?

When the CD-ROM drive spins down, I start typing. It works most of the time. Long timeouts from grub help. Perhaps the best solution is a separate, customized disk that starts speech automatically, without human intervention. I'm working on one of those, using the archiso scripts. -- Chris