Kali Linux

Kali Linux

[Igor Gueths]

Hey all,
does anyone have experience with attempting to get this distro installed and
working (http://kalilinux.org)? I got so far as to get it installed given that
the installer is a fork of upstream Debian, however I am now unable to boot into
the new system. I'm hoping to be able to get some eyes to help poke at it soon,
however if anyone has any ideas offhand they'd be much appreciated!
-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Kali Linux

[Glenn / Lenny]

what is it about this flavor that compels you to attempt to make it 
accessible?
Thanks.
Glenn
----- Original Message ----- 
From: "Igor Gueths" <igueths@lava-net.com>
To: <speakup@linux-speakup.org>
Sent: Tuesday, April 28, 2015 8:23 PM
Subject: Kali Linux


Hey all,
does anyone have experience with attempting to get this distro installed and
working (http://kalilinux.org)? I got so far as to get it installed given 
that
the installer is a fork of upstream Debian, however I am now unable to boot 
into
the new system. I'm hoping to be able to get some eyes to help poke at it 
soon,
however if anyone has any ideas offhand they'd be much appreciated!
-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

RE: Kali Linux

[Don Raikes]

Kali has a lot of very nice security tools built in and since it is a derivative of debian it should be accessible without too much problem.
-----Original Message-----
From: Glenn / Lenny [mailto:glennervin@cableone.net] 
Sent: Tuesday, April 28, 2015 6:32 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Kali Linux

what is it about this flavor that compels you to attempt to make it accessible?
Thanks.
Glenn
----- Original Message -----
From: "Igor Gueths" <igueths@lava-net.com>
To: <speakup@linux-speakup.org>
Sent: Tuesday, April 28, 2015 8:23 PM
Subject: Kali Linux


Hey all,
does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
--
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

RE: Kali Linux

[Don Raikes]

Igor,

I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.

If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.

The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.

It has been a while since I used kali (maybe 4 or 5 months and I have been working on my own customized version. If I can ever get my custom iso to work, it will be accessible either installed or as a live boot image, but life has gotten in the way recently :-)

If you have any other questions about kali, I am happy to help.

Sincerely,
Donald
-----Original Message-----
From: Igor Gueths [mailto:igueths@lava-net.com] 
Sent: Tuesday, April 28, 2015 6:24 PM
To: speakup@linux-speakup.org
Subject: Kali Linux

Hey all,
does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
--
Igor

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Kali Linux

[Igor Gueths]

On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> Igor,
> 
> I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> 

So they would build Speakup into the installer but not into the actual
post-installed system? That doesn't make any sense.
>
> If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
>

Thanks for the tip, I'll give it a try on the version I have here and see if it
works.
>
> The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> 

Yeah, unfortunately I lack a braille display so that's not a viable option.
>
> It has been a while since I used kali (maybe 4 or 5 months and I have been working on my own customized version. If I can ever get my custom iso to work, it will be accessible either installed or as a live boot image, but life has gotten in the way recently :-)
> 
> If you have any other questions about kali, I am happy to help.
> 

Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you
directly regarding Kali but perhaps that message got lost somewhere.
>
> Sincerely,
> Donald
> -----Original Message-----
> From: Igor Gueths [mailto:igueths@lava-net.com] 
> Sent: Tuesday, April 28, 2015 6:24 PM
> To: speakup@linux-speakup.org
> Subject: Kali Linux
> 
> Hey all,
> does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> --
> Igor
> 
> --
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

RE: Kali Linux

[Don Raikes]

Igor,

I just downloaded kali 1.1.0a and installed it onto a virtual machine. The installation went fine with speech.
After the install finished and the system rebooted, orca started talking at the login screen. I pressed space on the "other..." button entered root as the user tabbed to the next control arrowed up once to select gnome classic as my desktop manager, and tabbed to the login button. I pressed that with the spacebar, and was prompted for the password. After entering the password and pressing enter, the gnome desktop came up with orca talking.

I switched to a console window by pressing ctrl+alt+f1 and logged in as root (no speech was available at this point).  
It has been a long time since I tried to start Speakup, but I tried running espeakup but it said that it couldn't fine the softsynth driver. I don't remember how to load that driver so I stopped at that point.  Speakup is installed, it is just a matter of loading the proper driver and starting espeakup.

Once you get that started, or you could do it from a gnome terminal which would give you speech feedback while you work, you can modify the necessary files to have Speakup start automatically on boot and voila there you go.
-----Original Message-----
From: Igor Gueths [mailto:igueths@lava-net.com] 
Sent: Tuesday, April 28, 2015 7:03 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Kali Linux

On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> Igor,
> 
> I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> 

So they would build Speakup into the installer but not into the actual post-installed system? That doesn't make any sense.
>
> If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
>

Thanks for the tip, I'll give it a try on the version I have here and see if it works.
>
> The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> 

Yeah, unfortunately I lack a braille display so that's not a viable option.
>
> It has been a while since I used kali (maybe 4 or 5 months and I have 
> been working on my own customized version. If I can ever get my custom 
> iso to work, it will be accessible either installed or as a live boot 
> image, but life has gotten in the way recently :-)
> 
> If you have any other questions about kali, I am happy to help.
> 

Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you directly regarding Kali but perhaps that message got lost somewhere.
>
> Sincerely,
> Donald
> -----Original Message-----
> From: Igor Gueths [mailto:igueths@lava-net.com]
> Sent: Tuesday, April 28, 2015 6:24 PM
> To: speakup@linux-speakup.org
> Subject: Kali Linux
> 
> Hey all,
> does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> --
> Igor
> 
> --
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> --
> This message has been scanned for viruses and dangerous content by 
> MailScanner, and is believed to be clean.
> 

--
Igor

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Kali Linux

[Doug Smith]

It is really simple to get speech up and running when the system is 
installed.  You are right.  There is no speech in the console by 
default, but you can fix it by doing this:

1. In the graphical environment, press alt f2 and when you are prompted 
for a command, enter leafpad /etc/modules

2. At the very bottom of the list, which I believe only contains two or 
three entries, write: speakup_soft and press return.

3.  This is with an underline between speakup and soft.  Then reboot.

4. You will hear speakup coming up with some kind of fail fail message 
and then it will start reading the bootup messages.  You will have to 
stop it with the speakup stop key or the orca on there will not come up 
talking.

5. When you have all this done, open a terminal and do this:

chmod a=rw- /etc/init.d/gdm  This will keep the graphical environment 
from coming up unless you want it to.  You have to be connected before 
you do this because you have to install a package or two afterward.

6. Now, with the system talking in the console, you need to do an

apt-get install speakup-tools

so that you will have the speakupconf program available to save your 
speakup settings.  Then apt-get install xorg-xinit, I think it is and 
then make a .xinitrc file with only one line in it and that is:

exec gnome-session

and then you can use startx to go into gnome on your kali linux.

I hope I have all those files right.  I hope I have all those package 
names right.  If not, and you have problems, feel free to contact me off 
list and I will help you.



Hope this helps.




-- 
Doug Smith: Special Agent
S.W.A.T  Spiritual Warfare and Advanced Technology
Forever serving our LORD and SAVIOUR, JESUS CHRIST.

RE: Kali Linux

[Don Raikes]

Doug,

Thanks for the simple steps to get kali console speech enabled. 
-----Original Message-----
From: Doug Smith [mailto:savant-technopath@cyber-wizard.com] 
Sent: Wednesday, April 29, 2015 4:46 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Kali Linux

It is really simple to get speech up and running when the system is installed.  You are right.  There is no speech in the console by default, but you can fix it by doing this:

1. In the graphical environment, press alt f2 and when you are prompted for a command, enter leafpad /etc/modules

2. At the very bottom of the list, which I believe only contains two or three entries, write: speakup_soft and press return.

3.  This is with an underline between speakup and soft.  Then reboot.

4. You will hear speakup coming up with some kind of fail fail message and then it will start reading the bootup messages.  You will have to stop it with the speakup stop key or the orca on there will not come up talking.

5. When you have all this done, open a terminal and do this:

chmod a=rw- /etc/init.d/gdm  This will keep the graphical environment from coming up unless you want it to.  You have to be connected before you do this because you have to install a package or two afterward.

6. Now, with the system talking in the console, you need to do an

apt-get install speakup-tools

so that you will have the speakupconf program available to save your speakup settings.  Then apt-get install xorg-xinit, I think it is and then make a .xinitrc file with only one line in it and that is:

exec gnome-session

and then you can use startx to go into gnome on your kali linux.

I hope I have all those files right.  I hope I have all those package names right.  If not, and you have problems, feel free to contact me off list and I will help you.



Hope this helps.




--
Doug Smith: Special Agent
S.W.A.T  Spiritual Warfare and Advanced Technology Forever serving our LORD and SAVIOUR, JESUS CHRIST.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Kali Linux

[Igor Gueths]

Hey all,
thanks for the replies! I test booted my installation while I was at work
earlier today, and got what seemed to be a GDM login screen; alt+f2 appeared to
have no effect, but this could be due to my having installed it within
Virtualbox. Speaking of virtual machines, presuming the installation (s) were
done within Virtualbox, how did you fully capture the keyboard so that you could
do ctrl+alt+f1 and the like? I ask because I have never gotten this to work
reliably. Also is there a kernel difference between the kernel that is used
during installation and that which is used in the installed system? Just trying
to rule out the possibility of unsupported virtual audio chipsets and the like.
Thanks!
On Wed, Apr 29, 2015 at 07:46:27AM -0400, Doug Smith wrote:
> It is really simple to get speech up and running when the system is
> installed.  You are right.  There is no speech in the console by
> default, but you can fix it by doing this:
> 
> 1. In the graphical environment, press alt f2 and when you are
> prompted for a command, enter leafpad /etc/modules
> 
> 2. At the very bottom of the list, which I believe only contains two
> or three entries, write: speakup_soft and press return.
> 
> 3.  This is with an underline between speakup and soft.  Then reboot.
> 
> 4. You will hear speakup coming up with some kind of fail fail
> message and then it will start reading the bootup messages.  You
> will have to stop it with the speakup stop key or the orca on there
> will not come up talking.
> 
> 5. When you have all this done, open a terminal and do this:
> 
> chmod a=rw- /etc/init.d/gdm  This will keep the graphical
> environment from coming up unless you want it to.  You have to be
> connected before you do this because you have to install a package
> or two afterward.
> 
> 6. Now, with the system talking in the console, you need to do an
> 
> apt-get install speakup-tools
> 
> so that you will have the speakupconf program available to save your
> speakup settings.  Then apt-get install xorg-xinit, I think it is
> and then make a .xinitrc file with only one line in it and that is:
> 
> exec gnome-session
> 
> and then you can use startx to go into gnome on your kali linux.
> 
> I hope I have all those files right.  I hope I have all those
> package names right.  If not, and you have problems, feel free to
> contact me off list and I will help you.
> 
> 
> 
> Hope this helps.
> 
> 
> 
> 
> -- 
> Doug Smith: Special Agent
> S.W.A.T  Spiritual Warfare and Advanced Technology
> Forever serving our LORD and SAVIOUR, JESUS CHRIST.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

virtualbox, was: Re: Kali Linux

[Gregory Nowak]

Capturing/releasing the keyboard is described in I believe section
1.8.2 of the virtualbox manual. To capture/release the keyboard, you
need to use the host key, which is your right control key by
default. If you're in the guest, press your right control key to
release the keyboard, and you should then be able to alt+tab to other
windows. When you focus the virtualbox guest window again, it will
capture your keyboard automatically, unless you disabled this. If you
want to use the control key in your guest, use the left control
key. So, ctrl+alt+f1 in the guest would be done using your left
control and alt keys. If you're running on a gnu/linux host, then
things get different as described in section 1.8.3 of the virtualbox
manual. If you're running on a gnu/linux host, then pressing
hostkey+f1 would enter ctrl+alt+f1 into the guest and so on. 

If this bothers you and you can't get used to it, you can remap the
host key to something as I mentioned earlier. Alternatively, if you
have a usb keyboard, and a place to put it, you can pass that keyboard
through to the guest, and not have to deal with the whole host key
thing. HTH.

Greg


On Wed, Apr 29, 2015 at 09:02:56PM -0400, Igor Gueths wrote:
> Hey all,
> thanks for the replies! I test booted my installation while I was at work
> earlier today, and got what seemed to be a GDM login screen; alt+f2 appeared to
> have no effect, but this could be due to my having installed it within
> Virtualbox. Speaking of virtual machines, presuming the installation (s) were
> done within Virtualbox, how did you fully capture the keyboard so that you could
> do ctrl+alt+f1 and the like? I ask because I have never gotten this to work
> reliably. Also is there a kernel difference between the kernel that is used
> during installation and that which is used in the installed system? Just trying
> to rule out the possibility of unsupported virtual audio chipsets and the like.
> Thanks!


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

Re: virtualbox, was: Re: Kali Linux

[Igor Gueths]

Hey Greg, thanks for the tip! I obviously have been neglecting the RTFM time
that Virtualbox requires as of late...Will definitely give that a try though.
On Wed, Apr 29, 2015 at 08:52:07PM -0700, Gregory Nowak wrote:
> Capturing/releasing the keyboard is described in I believe section
> 1.8.2 of the virtualbox manual. To capture/release the keyboard, you
> need to use the host key, which is your right control key by
> default. If you're in the guest, press your right control key to
> release the keyboard, and you should then be able to alt+tab to other
> windows. When you focus the virtualbox guest window again, it will
> capture your keyboard automatically, unless you disabled this. If you
> want to use the control key in your guest, use the left control
> key. So, ctrl+alt+f1 in the guest would be done using your left
> control and alt keys. If you're running on a gnu/linux host, then
> things get different as described in section 1.8.3 of the virtualbox
> manual. If you're running on a gnu/linux host, then pressing
> hostkey+f1 would enter ctrl+alt+f1 into the guest and so on. 
> 
> If this bothers you and you can't get used to it, you can remap the
> host key to something as I mentioned earlier. Alternatively, if you
> have a usb keyboard, and a place to put it, you can pass that keyboard
> through to the guest, and not have to deal with the whole host key
> thing. HTH.
> 
> Greg
> 
> 
> On Wed, Apr 29, 2015 at 09:02:56PM -0400, Igor Gueths wrote:
> > Hey all,
> > thanks for the replies! I test booted my installation while I was at work
> > earlier today, and got what seemed to be a GDM login screen; alt+f2 appeared to
> > have no effect, but this could be due to my having installed it within
> > Virtualbox. Speaking of virtual machines, presuming the installation (s) were
> > done within Virtualbox, how did you fully capture the keyboard so that you could
> > do ctrl+alt+f1 and the like? I ask because I have never gotten this to work
> > reliably. Also is there a kernel difference between the kernel that is used
> > during installation and that which is used in the installed system? Just trying
> > to rule out the possibility of unsupported virtual audio chipsets and the like.
> > Thanks!
> 
> 
> -- 
> web site: http://www.gregn.net
> gpg public key: http://www.gregn.net/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> If we haven't been in touch before, e-mail me before adding me to your contacts.
> 
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

RE: virtualbox, was: Re: Kali Linux

[Don Raikes]

Igor et al,

How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
-----Original Message-----
From: Igor Gueths [mailto:igueths@lava-net.com] 
Sent: Thursday, April 30, 2015 9:31 AM
To: Speakup is a screen review system for Linux.
Subject: Re: virtualbox, was: Re: Kali Linux

Hey Greg, thanks for the tip! I obviously have been neglecting the RTFM time that Virtualbox requires as of late...Will definitely give that a try though.
On Wed, Apr 29, 2015 at 08:52:07PM -0700, Gregory Nowak wrote:
> Capturing/releasing the keyboard is described in I believe section
> 1.8.2 of the virtualbox manual. To capture/release the keyboard, you 
> need to use the host key, which is your right control key by default. 
> If you're in the guest, press your right control key to release the 
> keyboard, and you should then be able to alt+tab to other windows. 
> When you focus the virtualbox guest window again, it will capture your 
> keyboard automatically, unless you disabled this. If you want to use 
> the control key in your guest, use the left control key. So, 
> ctrl+alt+f1 in the guest would be done using your left control and alt 
> keys. If you're running on a gnu/linux host, then things get different 
> as described in section 1.8.3 of the virtualbox manual. If you're 
> running on a gnu/linux host, then pressing
> hostkey+f1 would enter ctrl+alt+f1 into the guest and so on. 
> 
> If this bothers you and you can't get used to it, you can remap the 
> host key to something as I mentioned earlier. Alternatively, if you 
> have a usb keyboard, and a place to put it, you can pass that keyboard 
> through to the guest, and not have to deal with the whole host key 
> thing. HTH.
> 
> Greg
> 
> 
> On Wed, Apr 29, 2015 at 09:02:56PM -0400, Igor Gueths wrote:
> > Hey all,
> > thanks for the replies! I test booted my installation while I was at 
> > work earlier today, and got what seemed to be a GDM login screen; 
> > alt+f2 appeared to have no effect, but this could be due to my 
> > having installed it within Virtualbox. Speaking of virtual machines, 
> > presuming the installation (s) were done within Virtualbox, how did 
> > you fully capture the keyboard so that you could do ctrl+alt+f1 and 
> > the like? I ask because I have never gotten this to work reliably. 
> > Also is there a kernel difference between the kernel that is used 
> > during installation and that which is used in the installed system? Just trying to rule out the possibility of unsupported virtual audio chipsets and the like.
> > Thanks!
> 
> 
> --
> web site: http://www.gregn.net
> gpg public key: http://www.gregn.net/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first) If we 
> haven't been in touch before, e-mail me before adding me to your contacts.
> 
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> --
> This message has been scanned for viruses and dangerous content by 
> MailScanner, and is believed to be clean.
> 

--
Igor

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: virtualbox, was: Re: Kali Linux

[Gregory Nowak]

Early on, virtualbox was using qt3 under which the GUI was indeed not
accessible. This has changed since they started using qt4, and that
was at least two years ago if not more. When I used to use the builds
of virtualbox using qt4 under windows xp, and wineyes 6.1, it was
quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7
home premium with the latest nvda, and that is quiet accessible also.

Greg


On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
> Igor et al,
> 
> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

RE: virtualbox, was: Re: Kali Linux

[Don Raikes]

So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
-----Original Message-----
From: Gregory Nowak [mailto:greg@gregn.net] 
Sent: Friday, May 01, 2015 3:42 PM
To: Speakup is a screen review system for Linux.
Subject: Re: virtualbox, was: Re: Kali Linux

Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.

Greg


On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
> Igor et al,
> 
> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.


--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org _______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: virtualbox, was: Re: Kali Linux

[Igor Gueths]

I'm actually running VirtualBox on a Debian host: 
igueths@holly:~$ uname -a
Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
GNU/Linux
On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes wrote:
> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
> -----Original Message-----
> From: Gregory Nowak [mailto:greg@gregn.net] 
> Sent: Friday, May 01, 2015 3:42 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: virtualbox, was: Re: Kali Linux
> 
> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
> 
> Greg
> 
> 
> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
> > Igor et al,
> > 
> > How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
> 
> 
> --
> web site: http://www.gregn.net
> gpg public key: http://www.gregn.net/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
> 
> --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: virtualbox, was: Re: Kali Linux

[Jason White]

Igor Gueths <igueths@lava-net.com> wrote:
> I'm actually running VirtualBox on a Debian host: 

I haven't used VirtualBox, but my understanding is that it has extensive
command line options. You should be able to do almost everything from a shell
prompt.

I have used Kvm, which likewise can be controlled from the command line and
from the Qemu command interface.

Re: virtualbox, was: Re: Kali Linux

[Gregory Nowak]

Yes, this is correct. the VBoxManage command can manage all aspects of
virtualbox's configuration, even those that cannot be managed through
the GUI at this time. I haven't run vbox inside a GUI like gnome, but
I have run it on a gnu/linux host, and have used VRDP to interact
with the guest from a windows box on my LAN, which worked out rather
well.

Speaking of KVM, how do you interact with the guest? Through the GUI
under gnome, from the text console somehow, through ssh, in some other
way?

Greg


On Sun, May 03, 2015 at 06:33:05PM -0400, Jason White wrote:
> Igor Gueths <igueths@lava-net.com> wrote:
> > I'm actually running VirtualBox on a Debian host: 
> 
> I haven't used VirtualBox, but my understanding is that it has extensive
> command line options. You should be able to do almost everything from a shell
> prompt.
> 
> I have used Kvm, which likewise can be controlled from the command line and
> from the Qemu command interface.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

Re: virtualbox, was: Re: Kali Linux

[Jason White]

Gregory Nowak <greg@gregn.net> wrote:
 
> Speaking of KVM, how do you interact with the guest? Through the GUI
> under gnome, from the text console somehow, through ssh, in some other
> way?

There's an ncurses option to qemu that starts the KVM guest with its console
directed to the terminal in which you're running kvm. Note that this also
provides access to the Grub prompt of the guest system.

You can also configure networking on the guest to enable ssh access from the
host (or from elsewhere). If you have an IPv6 network it's especially
convenient.

Re: virtualbox, was: Re: Kali Linux

[Gregory Nowak]

Does the ncurses option also work if the guest is running x/gnome or
M$ windows?

Greg


On Sun, May 03, 2015 at 07:17:47PM -0400, Jason White wrote:
> Gregory Nowak <greg@gregn.net> wrote:
>  
> > Speaking of KVM, how do you interact with the guest? Through the GUI
> > under gnome, from the text console somehow, through ssh, in some other
> > way?
> 
> There's an ncurses option to qemu that starts the KVM guest with its console
> directed to the terminal in which you're running kvm. Note that this also
> provides access to the Grub prompt of the guest system.
> 
> You can also configure networking on the guest to enable ssh access from the
> host (or from elsewhere). If you have an IPv6 network it's especially
> convenient.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

Re: virtualbox, was: Re: Kali Linux

[Jason White]

Gregory Nowak <greg@gregn.net> wrote:
> Does the ncurses option also work if the guest is running x/gnome or
> M$ windows?

I expect it would work up to the point at which the screen is changed to
graphics mode during the boot process. After that, you would need to run an X
client, which I haven't tried.

Re: virtualbox, was: Re: Kali Linux

[John G Heim]

I am using virtualbox to try to create a version of grml that comes up 
I've been using virtualbox to try to create a version of grml that comes 
up talking. I have virtual machines for straight debian, grml32, and 
grml64. It's pretty nice. I'm not sure if I  prefer virtualbox or vmware 
player. Virtualbox has a really powerful and well docummented command 
line interface. So I was able to script the process of creating virtual 
machines.  Virtualbox stores it's config files in an xml file and it has 
a warning at the top of each file not to edit it. VMware stores it 
config files in plain text that is easily edited in any text editor. 
I've many times changed the boot order of a virtual machine by just 
going in and editing it in the config file. But if you're not 
intimidated by xml, you could probably edit the config files for 
virtualbox too.

One other thing that I really liked about virtualbox was that you can 
get a screen capture. At first, when I have having trouble getting 
virtual machines to start, I'd take a screen cap and run it through 
tesseract to see why it was stuck. I was even able to check the network 
configuration on a Windwos virtual machine this way. I was pretty sure 
the Windows virtual machine was running so I pressed the keys to open a 
command window, windows+r, cmd. Then in the command window, I type 
"ipconfig /all". Then I got the screen cap and was able to check the 
network config. Pretty cool.

But it turns out vmware can do that too.
http://stackoverflow.com/questions/2255477/how-to-make-screenshots-using-vmware-tool-vmrun


On 05/03/2015 05:27 PM, Igor Gueths wrote:
> I'm actually running VirtualBox on a Debian host:
> igueths@holly:~$ uname -a
> Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
> GNU/Linux
> On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes wrote:
>> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
>> -----Original Message-----
>> From: Gregory Nowak [mailto:greg@gregn.net]
>> Sent: Friday, May 01, 2015 3:42 PM
>> To: Speakup is a screen review system for Linux.
>> Subject: Re: virtualbox, was: Re: Kali Linux
>>
>> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
>>
>> Greg
>>
>>
>> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
>>> Igor et al,
>>>
>>> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
>>
>>
>> --
>> web site: http://www.gregn.net
>> gpg public key: http://www.gregn.net/pubkey.asc
>> skype: gregn1
>> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
>>
>> --
>> Free domains: http://www.eu.org/ or mail dns-manager@EU.org _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>

-- 
John Heim, jheim@math.wisc.edu, skype:john.g.heim

RE: virtualbox, was: Re: Kali Linux

[Don Raikes]

If anyone has some command-line scripts for virtualbox they would be willing to share, I would greatly appreciate the assistance.  I was working on a set of scripts a couple of years ago, but can't find them now, and need to get vbox up and running pretty quickly.
-----Original Message-----
From: John G Heim [mailto:jheim@math.wisc.edu] 
Sent: Tuesday, May 05, 2015 8:20 AM
To: Speakup is a screen review system for Linux.
Subject: Re: virtualbox, was: Re: Kali Linux

I am using virtualbox to try to create a version of grml that comes up I've been using virtualbox to try to create a version of grml that comes up talking. I have virtual machines for straight debian, grml32, and grml64. It's pretty nice. I'm not sure if I  prefer virtualbox or vmware player. Virtualbox has a really powerful and well docummented command line interface. So I was able to script the process of creating virtual machines.  Virtualbox stores it's config files in an xml file and it has a warning at the top of each file not to edit it. VMware stores it config files in plain text that is easily edited in any text editor. 
I've many times changed the boot order of a virtual machine by just going in and editing it in the config file. But if you're not intimidated by xml, you could probably edit the config files for virtualbox too.

One other thing that I really liked about virtualbox was that you can get a screen capture. At first, when I have having trouble getting virtual machines to start, I'd take a screen cap and run it through tesseract to see why it was stuck. I was even able to check the network configuration on a Windwos virtual machine this way. I was pretty sure the Windows virtual machine was running so I pressed the keys to open a command window, windows+r, cmd. Then in the command window, I type "ipconfig /all". Then I got the screen cap and was able to check the network config. Pretty cool.

But it turns out vmware can do that too.
http://stackoverflow.com/questions/2255477/how-to-make-screenshots-using-vmware-tool-vmrun


On 05/03/2015 05:27 PM, Igor Gueths wrote:
> I'm actually running VirtualBox on a Debian host:
> igueths@holly:~$ uname -a
> Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) 
> x86_64 GNU/Linux On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes 
> wrote:
>> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
>> -----Original Message-----
>> From: Gregory Nowak [mailto:greg@gregn.net]
>> Sent: Friday, May 01, 2015 3:42 PM
>> To: Speakup is a screen review system for Linux.
>> Subject: Re: virtualbox, was: Re: Kali Linux
>>
>> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
>>
>> Greg
>>
>>
>> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
>>> Igor et al,
>>>
>>> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
>>
>>
>> --
>> web site: http://www.gregn.net
>> gpg public key: http://www.gregn.net/pubkey.asc
>> skype: gregn1
>> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
>>
>> --
>> Free domains: http://www.eu.org/ or mail dns-manager@EU.org 
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>> --
>> This message has been scanned for viruses and dangerous content by 
>> MailScanner, and is believed to be clean.
>>
>

-- 
John Heim, jheim@math.wisc.edu, skype:john.g.heim
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: virtualbox, was: Re: Kali Linux

[John G Heim]

My script is pretty muchjust the vboxmanage commands from a blog entry I 
found by googling. Here is alink to the blog:
http://www.perkin.org.uk/posts/create-virtualbox-vm-from-the-command-line.html

The only thing I did differently was to swap the order of the command to 
create the virtual machine (createvm) and the command to create the 
virtual hard disk (createhd). This allowed me to create the virtual hard 
disk inside the same folder as the virtual machine. That's not necessary 
and depending on your setup, might be counter-productive. I prefer it so 
I can keep everything tidy.

On 05/05/2015 11:08 AM, Don Raikes wrote:
> If anyone has some command-line scripts for virtualbox they would be willing to share, I would greatly appreciate the assistance.  I was working on a set of scripts a couple of years ago, but can't find them now, and need to get vbox up and running pretty quickly.
> -----Original Message-----
> From: John G Heim [mailto:jheim@math.wisc.edu]
> Sent: Tuesday, May 05, 2015 8:20 AM
> To: Speakup is a screen review system for Linux.
> Subject: Re: virtualbox, was: Re: Kali Linux
>
> I am using virtualbox to try to create a version of grml that comes up I've been using virtualbox to try to create a version of grml that comes up talking. I have virtual machines for straight debian, grml32, and grml64. It's pretty nice. I'm not sure if I  prefer virtualbox or vmware player. Virtualbox has a really powerful and well docummented command line interface. So I was able to script the process of creating virtual machines.  Virtualbox stores it's config files in an xml file and it has a warning at the top of each file not to edit it. VMware stores it config files in plain text that is easily edited in any text editor.
> I've many times changed the boot order of a virtual machine by just going in and editing it in the config file. But if you're not intimidated by xml, you could probably edit the config files for virtualbox too.
>
> One other thing that I really liked about virtualbox was that you can get a screen capture. At first, when I have having trouble getting virtual machines to start, I'd take a screen cap and run it through tesseract to see why it was stuck. I was even able to check the network configuration on a Windwos virtual machine this way. I was pretty sure the Windows virtual machine was running so I pressed the keys to open a command window, windows+r, cmd. Then in the command window, I type "ipconfig /all". Then I got the screen cap and was able to check the network config. Pretty cool.
>
> But it turns out vmware can do that too.
> http://stackoverflow.com/questions/2255477/how-to-make-screenshots-using-vmware-tool-vmrun
>
>
> On 05/03/2015 05:27 PM, Igor Gueths wrote:
>> I'm actually running VirtualBox on a Debian host:
>> igueths@holly:~$ uname -a
>> Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)
>> x86_64 GNU/Linux On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes
>> wrote:
>>> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
>>> -----Original Message-----
>>> From: Gregory Nowak [mailto:greg@gregn.net]
>>> Sent: Friday, May 01, 2015 3:42 PM
>>> To: Speakup is a screen review system for Linux.
>>> Subject: Re: virtualbox, was: Re: Kali Linux
>>>
>>> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
>>>
>>> Greg
>>>
>>>
>>> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
>>>> Igor et al,
>>>>
>>>> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
>>>
>>>
>>> --
>>> web site: http://www.gregn.net
>>> gpg public key: http://www.gregn.net/pubkey.asc
>>> skype: gregn1
>>> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
>>>
>>> --
>>> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>
>

-- 
John Heim, jheim@math.wisc.edu, skype:john.g.heim

RE: virtualbox, was: Re: Kali Linux

[Don Raikes]

I created a github repository to share scripts.

https://github.com/dr1861/vbox-scripts.git

It is a public repository so please feel free to contribute to it.
-----Original Message-----
From: John G Heim [mailto:jheim@math.wisc.edu] 
Sent: Tuesday, May 05, 2015 8:20 AM
To: Speakup is a screen review system for Linux.
Subject: Re: virtualbox, was: Re: Kali Linux

I am using virtualbox to try to create a version of grml that comes up I've been using virtualbox to try to create a version of grml that comes up talking. I have virtual machines for straight debian, grml32, and grml64. It's pretty nice. I'm not sure if I  prefer virtualbox or vmware player. Virtualbox has a really powerful and well docummented command line interface. So I was able to script the process of creating virtual machines.  Virtualbox stores it's config files in an xml file and it has a warning at the top of each file not to edit it. VMware stores it config files in plain text that is easily edited in any text editor. 
I've many times changed the boot order of a virtual machine by just going in and editing it in the config file. But if you're not intimidated by xml, you could probably edit the config files for virtualbox too.

One other thing that I really liked about virtualbox was that you can get a screen capture. At first, when I have having trouble getting virtual machines to start, I'd take a screen cap and run it through tesseract to see why it was stuck. I was even able to check the network configuration on a Windwos virtual machine this way. I was pretty sure the Windows virtual machine was running so I pressed the keys to open a command window, windows+r, cmd. Then in the command window, I type "ipconfig /all". Then I got the screen cap and was able to check the network config. Pretty cool.

But it turns out vmware can do that too.
http://stackoverflow.com/questions/2255477/how-to-make-screenshots-using-vmware-tool-vmrun


On 05/03/2015 05:27 PM, Igor Gueths wrote:
> I'm actually running VirtualBox on a Debian host:
> igueths@holly:~$ uname -a
> Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) 
> x86_64 GNU/Linux On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes 
> wrote:
>> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
>> -----Original Message-----
>> From: Gregory Nowak [mailto:greg@gregn.net]
>> Sent: Friday, May 01, 2015 3:42 PM
>> To: Speakup is a screen review system for Linux.
>> Subject: Re: virtualbox, was: Re: Kali Linux
>>
>> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
>>
>> Greg
>>
>>
>> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
>>> Igor et al,
>>>
>>> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
>>
>>
>> --
>> web site: http://www.gregn.net
>> gpg public key: http://www.gregn.net/pubkey.asc
>> skype: gregn1
>> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
>>
>> --
>> Free domains: http://www.eu.org/ or mail dns-manager@EU.org 
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>> --
>> This message has been scanned for viruses and dangerous content by 
>> MailScanner, and is believed to be clean.
>>
>

-- 
John Heim, jheim@math.wisc.edu, skype:john.g.heim
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

RE: Kali Linux

[Don Raikes]

A couple minor corrections to the process and they may be because of a newer version of kali:

1. the package to install is not xorg-xinit it is simply xinit.
2. the chmod a=rw- /etc/init.d/gdm3 not /etc/init.d/gdm

One small addition as well,
If you boot into console mode with Speakup if you want to go to gnome, you need to turn speech off for Speakup before running startx otherwise orca cannot access the sound system.

Other than those little tidbits these instructiosn worked perfectly well.
-----Original Message-----
From: Doug Smith [mailto:savant-technopath@cyber-wizard.com] 
Sent: Wednesday, April 29, 2015 4:46 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Kali Linux

It is really simple to get speech up and running when the system is installed.  You are right.  There is no speech in the console by default, but you can fix it by doing this:

1. In the graphical environment, press alt f2 and when you are prompted for a command, enter leafpad /etc/modules

2. At the very bottom of the list, which I believe only contains two or three entries, write: speakup_soft and press return.

3.  This is with an underline between speakup and soft.  Then reboot.

4. You will hear speakup coming up with some kind of fail fail message and then it will start reading the bootup messages.  You will have to stop it with the speakup stop key or the orca on there will not come up talking.

5. When you have all this done, open a terminal and do this:

chmod a=rw- /etc/init.d/gdm  This will keep the graphical environment from coming up unless you want it to.  You have to be connected before you do this because you have to install a package or two afterward.

6. Now, with the system talking in the console, you need to do an

apt-get install speakup-tools

so that you will have the speakupconf program available to save your speakup settings.  Then apt-get install xorg-xinit, I think it is and then make a .xinitrc file with only one line in it and that is:

exec gnome-session

and then you can use startx to go into gnome on your kali linux.

I hope I have all those files right.  I hope I have all those package names right.  If not, and you have problems, feel free to contact me off list and I will help you.



Hope this helps.




--
Doug Smith: Special Agent
S.W.A.T  Spiritual Warfare and Advanced Technology Forever serving our LORD and SAVIOUR, JESUS CHRIST.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Kali Linux

[Igor Gueths]

Hi Don,
what virtualization software did you use? Currently, my Kali is running inside
Virtualbox with an audiocontroller of Puse and an emulated chipset of
AC97...While this worked in the installer, it does not seem to work in my new
system i.e., Orca does not come up talking by default as it supposedly should.
Any ideas as to audio parameters I should use instead in order to correct this?
On Tue, Apr 28, 2015 at 11:05:41PM -0700, Don Raikes wrote:
> Igor,
> 
> I just downloaded kali 1.1.0a and installed it onto a virtual machine. The installation went fine with speech.
> After the install finished and the system rebooted, orca started talking at the login screen. I pressed space on the "other..." button entered root as the user tabbed to the next control arrowed up once to select gnome classic as my desktop manager, and tabbed to the login button. I pressed that with the spacebar, and was prompted for the password. After entering the password and pressing enter, the gnome desktop came up with orca talking.
> 
> I switched to a console window by pressing ctrl+alt+f1 and logged in as root (no speech was available at this point).  
> It has been a long time since I tried to start Speakup, but I tried running espeakup but it said that it couldn't fine the softsynth driver. I don't remember how to load that driver so I stopped at that point.  Speakup is installed, it is just a matter of loading the proper driver and starting espeakup.
> 
> Once you get that started, or you could do it from a gnome terminal which would give you speech feedback while you work, you can modify the necessary files to have Speakup start automatically on boot and voila there you go.
> -----Original Message-----
> From: Igor Gueths [mailto:igueths@lava-net.com] 
> Sent: Tuesday, April 28, 2015 7:03 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: Kali Linux
> 
> On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> > Igor,
> > 
> > I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> > In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> > 
> 
> So they would build Speakup into the installer but not into the actual post-installed system? That doesn't make any sense.
> >
> > If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
> >
> 
> Thanks for the tip, I'll give it a try on the version I have here and see if it works.
> >
> > The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> > 
> 
> Yeah, unfortunately I lack a braille display so that's not a viable option.
> >
> > It has been a while since I used kali (maybe 4 or 5 months and I have 
> > been working on my own customized version. If I can ever get my custom 
> > iso to work, it will be accessible either installed or as a live boot 
> > image, but life has gotten in the way recently :-)
> > 
> > If you have any other questions about kali, I am happy to help.
> > 
> 
> Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you directly regarding Kali but perhaps that message got lost somewhere.
> >
> > Sincerely,
> > Donald
> > -----Original Message-----
> > From: Igor Gueths [mailto:igueths@lava-net.com]
> > Sent: Tuesday, April 28, 2015 6:24 PM
> > To: speakup@linux-speakup.org
> > Subject: Kali Linux
> > 
> > Hey all,
> > does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> > --
> > Igor
> > 
> > --
> > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > 
> > --
> > This message has been scanned for viruses and dangerous content by 
> > MailScanner, and is believed to be clean.
> > 
> 
> --
> Igor
> 
> --
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Kali Linux

[Igor Gueths]

Interestingly enough, I reinstalled the system, remembering to enable the
virtual NIC and all came up talking as a result. Rather odd that...
On Thu, Apr 30, 2015 at 02:51:07PM -0400, Igor Gueths wrote:
> Hi Don,
> what virtualization software did you use? Currently, my Kali is running inside
> Virtualbox with an audiocontroller of Puse and an emulated chipset of
> AC97...While this worked in the installer, it does not seem to work in my new
> system i.e., Orca does not come up talking by default as it supposedly should.
> Any ideas as to audio parameters I should use instead in order to correct this?
> On Tue, Apr 28, 2015 at 11:05:41PM -0700, Don Raikes wrote:
> > Igor,
> > 
> > I just downloaded kali 1.1.0a and installed it onto a virtual machine. The installation went fine with speech.
> > After the install finished and the system rebooted, orca started talking at the login screen. I pressed space on the "other..." button entered root as the user tabbed to the next control arrowed up once to select gnome classic as my desktop manager, and tabbed to the login button. I pressed that with the spacebar, and was prompted for the password. After entering the password and pressing enter, the gnome desktop came up with orca talking.
> > 
> > I switched to a console window by pressing ctrl+alt+f1 and logged in as root (no speech was available at this point).  
> > It has been a long time since I tried to start Speakup, but I tried running espeakup but it said that it couldn't fine the softsynth driver. I don't remember how to load that driver so I stopped at that point.  Speakup is installed, it is just a matter of loading the proper driver and starting espeakup.
> > 
> > Once you get that started, or you could do it from a gnome terminal which would give you speech feedback while you work, you can modify the necessary files to have Speakup start automatically on boot and voila there you go.
> > -----Original Message-----
> > From: Igor Gueths [mailto:igueths@lava-net.com] 
> > Sent: Tuesday, April 28, 2015 7:03 PM
> > To: Speakup is a screen review system for Linux.
> > Subject: Re: Kali Linux
> > 
> > On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> > > Igor,
> > > 
> > > I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> > > In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> > > 
> > 
> > So they would build Speakup into the installer but not into the actual post-installed system? That doesn't make any sense.
> > >
> > > If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
> > >
> > 
> > Thanks for the tip, I'll give it a try on the version I have here and see if it works.
> > >
> > > The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> > > 
> > 
> > Yeah, unfortunately I lack a braille display so that's not a viable option.
> > >
> > > It has been a while since I used kali (maybe 4 or 5 months and I have 
> > > been working on my own customized version. If I can ever get my custom 
> > > iso to work, it will be accessible either installed or as a live boot 
> > > image, but life has gotten in the way recently :-)
> > > 
> > > If you have any other questions about kali, I am happy to help.
> > > 
> > 
> > Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you directly regarding Kali but perhaps that message got lost somewhere.
> > >
> > > Sincerely,
> > > Donald
> > > -----Original Message-----
> > > From: Igor Gueths [mailto:igueths@lava-net.com]
> > > Sent: Tuesday, April 28, 2015 6:24 PM
> > > To: speakup@linux-speakup.org
> > > Subject: Kali Linux
> > > 
> > > Hey all,
> > > does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> > > --
> > > Igor
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by 
> > > MailScanner, and is believed to be clean.
> > > 
> > 
> > --
> > Igor
> > 
> > --
> > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > 
> > -- 
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > 
> 
> -- 
> Igor
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

RE: Kali Linux

[Don Raikes]

Not so odd, the system probably hung while checking for the network. I have seen this happen before on other virtual systems.
-----Original Message-----
From: Igor Gueths [mailto:igueths@lava-net.com] 
Sent: Thursday, April 30, 2015 7:25 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Kali Linux

Interestingly enough, I reinstalled the system, remembering to enable the virtual NIC and all came up talking as a result. Rather odd that...
On Thu, Apr 30, 2015 at 02:51:07PM -0400, Igor Gueths wrote:
> Hi Don,
> what virtualization software did you use? Currently, my Kali is 
> running inside Virtualbox with an audiocontroller of Puse and an 
> emulated chipset of AC97...While this worked in the installer, it does 
> not seem to work in my new system i.e., Orca does not come up talking by default as it supposedly should.
> Any ideas as to audio parameters I should use instead in order to correct this?
> On Tue, Apr 28, 2015 at 11:05:41PM -0700, Don Raikes wrote:
> > Igor,
> > 
> > I just downloaded kali 1.1.0a and installed it onto a virtual machine. The installation went fine with speech.
> > After the install finished and the system rebooted, orca started talking at the login screen. I pressed space on the "other..." button entered root as the user tabbed to the next control arrowed up once to select gnome classic as my desktop manager, and tabbed to the login button. I pressed that with the spacebar, and was prompted for the password. After entering the password and pressing enter, the gnome desktop came up with orca talking.
> > 
> > I switched to a console window by pressing ctrl+alt+f1 and logged in as root (no speech was available at this point).  
> > It has been a long time since I tried to start Speakup, but I tried running espeakup but it said that it couldn't fine the softsynth driver. I don't remember how to load that driver so I stopped at that point.  Speakup is installed, it is just a matter of loading the proper driver and starting espeakup.
> > 
> > Once you get that started, or you could do it from a gnome terminal which would give you speech feedback while you work, you can modify the necessary files to have Speakup start automatically on boot and voila there you go.
> > -----Original Message-----
> > From: Igor Gueths [mailto:igueths@lava-net.com]
> > Sent: Tuesday, April 28, 2015 7:03 PM
> > To: Speakup is a screen review system for Linux.
> > Subject: Re: Kali Linux
> > 
> > On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> > > Igor,
> > > 
> > > I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> > > In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> > > 
> > 
> > So they would build Speakup into the installer but not into the actual post-installed system? That doesn't make any sense.
> > >
> > > If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
> > >
> > 
> > Thanks for the tip, I'll give it a try on the version I have here and see if it works.
> > >
> > > The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> > > 
> > 
> > Yeah, unfortunately I lack a braille display so that's not a viable option.
> > >
> > > It has been a while since I used kali (maybe 4 or 5 months and I 
> > > have been working on my own customized version. If I can ever get 
> > > my custom iso to work, it will be accessible either installed or 
> > > as a live boot image, but life has gotten in the way recently :-)
> > > 
> > > If you have any other questions about kali, I am happy to help.
> > > 
> > 
> > Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you directly regarding Kali but perhaps that message got lost somewhere.
> > >
> > > Sincerely,
> > > Donald
> > > -----Original Message-----
> > > From: Igor Gueths [mailto:igueths@lava-net.com]
> > > Sent: Tuesday, April 28, 2015 6:24 PM
> > > To: speakup@linux-speakup.org
> > > Subject: Kali Linux
> > > 
> > > Hey all,
> > > does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> > > --
> > > Igor
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by 
> > > MailScanner, and is believed to be clean.
> > > 
> > 
> > --
> > Igor
> > 
> > --
> > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > 
> > --
> > This message has been scanned for viruses and dangerous content by 
> > MailScanner, and is believed to be clean.
> > 
> 
> --
> Igor
> 
> --
> This message has been scanned for viruses and dangerous content by 
> MailScanner, and is believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
Igor

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: Kali Linux

[Igor Gueths]

Hey there,
On Fri, May 01, 2015 at 08:58:18AM -0700, Don Raikes wrote:
> Not so odd, the system probably hung while checking for the network. I have seen this happen before on other virtual systems.
>

So did the system get to the point at which it would display GDM and then hang?
If so, then this would explain some rather odd behavior that I started initially
seeing in my first install.
> -----Original Message-----
> From: Igor Gueths [mailto:igueths@lava-net.com] 
> Sent: Thursday, April 30, 2015 7:25 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: Kali Linux
> 
> Interestingly enough, I reinstalled the system, remembering to enable the virtual NIC and all came up talking as a result. Rather odd that...
> On Thu, Apr 30, 2015 at 02:51:07PM -0400, Igor Gueths wrote:
> > Hi Don,
> > what virtualization software did you use? Currently, my Kali is 
> > running inside Virtualbox with an audiocontroller of Puse and an 
> > emulated chipset of AC97...While this worked in the installer, it does 
> > not seem to work in my new system i.e., Orca does not come up talking by default as it supposedly should.
> > Any ideas as to audio parameters I should use instead in order to correct this?
> > On Tue, Apr 28, 2015 at 11:05:41PM -0700, Don Raikes wrote:
> > > Igor,
> > > 
> > > I just downloaded kali 1.1.0a and installed it onto a virtual machine. The installation went fine with speech.
> > > After the install finished and the system rebooted, orca started talking at the login screen. I pressed space on the "other..." button entered root as the user tabbed to the next control arrowed up once to select gnome classic as my desktop manager, and tabbed to the login button. I pressed that with the spacebar, and was prompted for the password. After entering the password and pressing enter, the gnome desktop came up with orca talking.
> > > 
> > > I switched to a console window by pressing ctrl+alt+f1 and logged in as root (no speech was available at this point).  
> > > It has been a long time since I tried to start Speakup, but I tried running espeakup but it said that it couldn't fine the softsynth driver. I don't remember how to load that driver so I stopped at that point.  Speakup is installed, it is just a matter of loading the proper driver and starting espeakup.
> > > 
> > > Once you get that started, or you could do it from a gnome terminal which would give you speech feedback while you work, you can modify the necessary files to have Speakup start automatically on boot and voila there you go.
> > > -----Original Message-----
> > > From: Igor Gueths [mailto:igueths@lava-net.com]
> > > Sent: Tuesday, April 28, 2015 7:03 PM
> > > To: Speakup is a screen review system for Linux.
> > > Subject: Re: Kali Linux
> > > 
> > > On Tue, Apr 28, 2015 at 06:37:21PM -0700, Don Raikes wrote:
> > > > Igor,
> > > > 
> > > > I have been successful in getting kali to work on a virtual machine. The problem is that accessibility is not enabled by default.
> > > > In fact, I am not sure that Speakup is built into kali. I tried to get the kali developers to build it in but I think it got dropped somewhere along the way.
> > > > 
> > > 
> > > So they would build Speakup into the installer but not into the actual post-installed system? That doesn't make any sense.
> > > >
> > > > If I remember right, the system brings you to a gnome desktop and if you press alt+f2 to open the run dialog then type orca<enter> orca should start talking.
> > > >
> > > 
> > > Thanks for the tip, I'll give it a try on the version I have here and see if it works.
> > > >
> > > > The only caveat to this is that if you installed it with another user, then you have to login first.  If you have a Braille display, you could press ctrl+alt+f1-6 and open a console window, enter root as the user and whatever the root password is then type brltty to launch brltty. After that you just need to adjust the /etc/default/brltty file so brltty starts automatically.
> > > > 
> > > 
> > > Yeah, unfortunately I lack a braille display so that's not a viable option.
> > > >
> > > > It has been a while since I used kali (maybe 4 or 5 months and I 
> > > > have been working on my own customized version. If I can ever get 
> > > > my custom iso to work, it will be accessible either installed or 
> > > > as a live boot image, but life has gotten in the way recently :-)
> > > > 
> > > > If you have any other questions about kali, I am happy to help.
> > > > 
> > > 
> > > Yeah, pesky lives...Who needs one of those? Anyway, iirc I had mailed you directly regarding Kali but perhaps that message got lost somewhere.
> > > >
> > > > Sincerely,
> > > > Donald
> > > > -----Original Message-----
> > > > From: Igor Gueths [mailto:igueths@lava-net.com]
> > > > Sent: Tuesday, April 28, 2015 6:24 PM
> > > > To: speakup@linux-speakup.org
> > > > Subject: Kali Linux
> > > > 
> > > > Hey all,
> > > > does anyone have experience with attempting to get this distro installed and working (http://kalilinux.org)? I got so far as to get it installed given that the installer is a fork of upstream Debian, however I am now unable to boot into the new system. I'm hoping to be able to get some eyes to help poke at it soon, however if anyone has any ideas offhand they'd be much appreciated!
> > > > --
> > > > Igor
> > > > 
> > > > --
> > > > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@linux-speakup.org
> > > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@linux-speakup.org
> > > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > > 
> > > > --
> > > > This message has been scanned for viruses and dangerous content by 
> > > > MailScanner, and is believed to be clean.
> > > > 
> > > 
> > > --
> > > Igor
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > > 
> > > --
> > > This message has been scanned for viruses and dangerous content by 
> > > MailScanner, and is believed to be clean.
> > > 
> > 
> > --
> > Igor
> > 
> > --
> > This message has been scanned for viruses and dangerous content by 
> > MailScanner, and is believed to be clean.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> --
> Igor
> 
> --
> This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

-- 
Igor

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Kali Linux

[Doug Smith]

I have installed it.  I don't have one going right here right now, but 
it is easy to get installed and up and running.

You're right.  The installer is totally accessible with speakup and the 
install process goes well.  You can't boot in until the installer 
finishes and the system reboots on its own.

With regard to getting into the new system, it is a little tricky. 
They're using gnome 3.4 until the next version releases, any time in the 
next little while.  After this, the distribution will be based on debian 
jessie which will contain gnome 3.14 and there should not be as many 
accessibility issues.

On my sonar install, gnome 3.14 worked fine, but 3.16 is even better.  
We use orca exclusively over here with sonar, but it should not be hard 
to get that up and running.



Hope this helps.




-- 
Doug Smith: Special Agent
S.W.A.T  Spiritual Warfare and Advanced Technology
Forever serving our LORD and SAVIOUR, JESUS CHRIST.

Re: Kali Linux

[Jude DaShiell]

I got a version of that installed once an earlier version so your 
experience may be better.  You start orca up with alt-fb orca and then 
do your install.  You'll need to log in as root on post install boot and 
start up orca again in the same way.  Once that gets done, orca 
sometimes works and sometimes doesn't and I never got to the bottom of 
reason(s) for intermitent performance.  Each user account will also need 
orca started up and configured once installation is complete.

On Tue, 28 Apr 2015, Igor Gueths wrote:

> Date: Tue, 28 Apr 2015 21:23:32
> From: Igor Gueths <igueths@lava-net.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@linux-speakup.org>
> To: speakup@linux-speakup.org
> Subject: Kali Linux
> 
> Hey all,
> does anyone have experience with attempting to get this distro installed and
> working (http://kalilinux.org)? I got so far as to get it installed given that
> the installer is a fork of upstream Debian, however I am now unable to boot into
> the new system. I'm hoping to be able to get some eyes to help poke at it soon,
> however if anyone has any ideas offhand they'd be much appreciated!
> -- 
> Igor
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--