The x.sh script turns off espeak to prevent any possible conflict with
orca and screen output startx generates is also silenced.
On Fri, 13 Oct
2017, Linux for blind general discussion wrote:
Date: Thu, 12 Oct 2017 18:13:05
From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
To: blinux-list@xxxxxxxxxx
Subject: Re: slint-testing site inaccessible
Hello,
thanks for your remarks,
Le 11/10/2017 ? 23:10, Linux for blind general discussion a ?crit :
All of those chmod 755 filename commands can be rewritten as chmod +x filename.
Yes but this works only if the file had previously perms 644 or 755.
This should the case here but generally speaking if a user inadvertently
changed it to, say 666 he will end up with 777. That's why I prefer to
indicate the octal value.
An additional section in the accessibility document on testing your
iso probably will be helpful since this isn't yet a torrent iso
integrity problems can happen using either wget or curl. When I used
wget to get the iso, I used:
wget -bc filename.iso
a wget-log file got created against which I ran two commands.
first was wc -l wget-log and the number that returned as it increased
told me the file size was increasing.
When the wc -l wget-log command stopped returning increasing numbers,
I then used:
tail -3 wget-log|grep -i "saved"
and got the saved file name and its size returned.
You are right the user should check the integrity of the downloaded file.
The usal way to do it is to use one of the checksums available in the
same directory as the ISO.
For instance:
wget http://slackware.uk/slint/x86_64/slint-testing/iso/slint64-14.2.1RC.iso
wget http://slackware.uk/slint/x86_64/slint-testing/iso/slint64-14.2.1RC.iso.sha256
sha256sum -c slint64-14.2.1RC.iso.sha256
The output should be "OK"
The startup procedure for startx I automated earlier.
Cut here.
#!/usr/bin/env bash
# file: x.sh - xorg run script.
clear
sudo -H systemctl stop espeakup
startx 2>&1 >startx.log
sudo -H systemctl start espeakup
For me this provides a much cleaner start for x and also creates a log
file of any error that might appear on the way up into x.
That's interesting but would need to be adapted as we do not use systemd
hence the systemctl command is not available in Slint.
Maybe we could instead use the daemon manager like this:
sudo /etc/rc.d/rc.espeakup stop
sudo /etc/rc.d/rc.espeakup start
Although we generally don't use sudo by default in Slint so that would
need a little more configuration for the user in concern.
Also, I am not sure to understand the need to stop the espeakup daemon
when running startx. Is that to avoid hearing the display on the console
when in a graphical environment? I must admit that so far I have just
used the Print Screen key to stop it before typing startx.
Last, in Slint and other Slackware derivatives the output of the X
server is generally logged in /var/log/Xorg.0.log.
Didier
On Wed, 11 Oct 2017, Linux for blind general discussion wrote:
Date: Wed, 11 Oct 2017 14:00:04
From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
To: blinux-list@xxxxxxxxxx
Cc: Aiyumi <aiyumi.br@xxxxxxxxx>
Subject: Re: slint-testing site inaccessible
Le 11/10/2017 ? 16:28, Linux for blind general discussion a ?crit?:
You're correct that was a typo on my part.
Let's see if the directions for this can be made simpler. If a person
can use an editor edit /etc/slapt-get/slapt-getrc and locate the
SOURCE= line with slint in it. On that line, change 14.2 to testing
then save the file and exit.
That is what I did after a re-install and had only firefox as an
update and I went into lxde and ran firefox after the upgrade and the
accessibility problems I had with firefox yesterday disappeared.
So for now, I think we're all golden.
I have just edited the directions in: http://slackware.uk/slint/x86_64/slint-testing/iso/README
Please let me know if any changes are still needed, as well as in
http://slackware.uk/slint/x86_64/slint-testing/iso/ACCESSIBILITY
More general feedback if of course still welcome.
Cheers,
Didier
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
--
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list