I've been musing about a comment Samuel Thibault made a while back:
> On Mar 2, 2020, at 07:57, Samuel Thibault wrote:
>
> Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit:
>> ... More generally, is there a better way to provide accessibility at boot
>> time
The idea of detecting the presence (or absence) of a blind-related device seems
worth pursuing, even if there are some issues to be resolved.
For example, following Jude's notion of checking for a monitor, maybe Avahi and
SSH could be enabled whenever a monitor isn't found. For that matter, ena
Jude DaShiell said:
> If dummy was used for monitor type, the screen reader could come up talking
> without any monitor attached. ...
I can think of a couple of issues with this approach. First, there are various
reasons for leaving a monitor off a system. For example, if a RasPi is being
us
> On Mar 5, 2020, at 03:30, Samuel Thibault wrote:
>
> One thing I am missing in your description is: how is the system getting
> installed in your use case? Is it installed by the blind user himself,
> or by somebody else?
Ideally, the system hardware and software could be installed and config
Thanks to everyone for considering these questions, offering suggestions, etc.
Here are some comments and clarifications.
I don't know all the ins and outs of preseeding, etc. So, I'll talk about use
cases. I'm mostly looking for a way to make freshly installed systems (e.g.,
PC, RasPi) acce
In another forum, I've been told that Orca is a rather heavyweight solution for
providing boot-time speech generation. It was recommended that I consider
Fenrir, instead. So, recasting my question, what would it take to make these
changes to the default Debian installation?
- include Fenrir,
velopment teams, but
it seems logical to start at the headwaters (Debian), then move downstream.
> On Feb 24, 2020, at 14:41, Samuel Thibault wrote:
>
> Rich Morin, le lun. 24 févr. 2020 08:22:06 -0800, a ecrit:
>> The first notion has to do with the initial accessibility of the sy
Package: installation-reports
Boot method:
ok, I had a little bit time to play around,
perhaps this is helpful for the Debian Installer:
I changed in the original (non working) xorg.conf
>>Modes"1440x900"<< to >>Modes"1024x768"<<
... and after reboot X-Server was working, no other changes.
Cheers Richard
--
To UNSUBSCRI
Package: installation-reports
Boot method:
Image version: <2007-12-28; 162,4 MB (170291200 Bytes)>
Date: <2007-12-28>
Machine:
Processor:AMD X2 64
Memory:2GB
Partitions:
NumeroUno:/home/richrat# lspci -nn
00:00.0 Host bridge [0600]: ATI Technologies Inc Unknown device [1002:7910]
00:02.0 PCI
With our pills, she'll be speechless... and defiantly coming back for more...
http://emagx.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: installation-reports
Boot method: X floppy? network?>
Image version:
Date: 3-23-06 11 AM
Machine: default
Output of lspci and lspci -n:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[o]
Configure n
Hi,
I'm trying to install Sarge and everything is fine
until I'm asked for the second CD.
The CD isn't recognised, and the prompt to insert
second disk simply reappears.
The CD was Jigdo-d and burned on my Windoes box as
a bootable image and appears to be OK and indeed disk one worked just
filesystem.
cheers, Rich.
-- System Information
Debian Release: 3.0r0
Architecture: ARM
Kernel: bootfloppy kernel
Locale: LANG=C, LC_CTYPE=C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
system _before_ being able to rebuild
the kernel?
I am currently up and limping. I used debootstrap to load the base system and
then debootstrap's shell to obtain a benh kernel. The process was rough and
the machine is not yet sure-footed enough to attempt kernel building.
--rich
--
To U
summary of thread:
> On Thu, Jan 31, 2002 at 10:09:13AM -0500, Rich Johnson wrote:
> > package: boot-floppies
> > version: 3.0.18
> > architecture: powerpc
> > model: Mac 8500 /132 ("old world" firmware)
> > memory: 32M
> > scsi: on-board
> >
package: boot-floppies
version: 3.0.18
architecture: powerpc
model: Mac 8500 /132 ("old world" firmware)
memory: 32M
scsi: on-board
cd-rom:apple, scsi interface
Manually invoking root.bin's "/usr/sbin/chroot /target " from the
installer's shell always segfaults.
Perhaps this explains the
package: boot-floppies
version: 2.2.26
architecture: powerpc
model: Mac 8500 /132 ("old world" firmware)
memory: 32M
scsi: on-board
cd-rom:apple, scsi interface
dbootstrap doesn't recognize either ext2 or swap partitions on an
existing disk.
Partitioning was done from MacOS, and these par
ile is put in the queue.
For those of us who do not have a Linux system but
are trying to convert, access to a complete ISO image
would be just as fast, cause no more network
traffic and be a lot more convenient.
Rich Skrydlak
19 matches
Mail list logo
