Type and Media students report
Labels: type education
Labels: type education
It is sad to see that the last of the old ticket vending machines at Reading are being removed. Although even I can avoid being emotional over the loss of a ticket machine the truth is that the replacements are in some respects considerably inferior. From the software point of view, there is the decision to use an alphabetic rather than querty keyboard layout. Whatever its faults, to anybody who uses a keyboard the querty layout is far more familiar; I would guess the alphabetic layout is there because it means the ‘keys’ can be really big. I will accept that those who are fleet of vision should learn another skill if it means that those less able to see can use the keys, but I do wonder whether there was any user testing done, or if the mantra was simply ‘as big as will fit all 26 letters on the screen’.
The second thing that is bad – and much harder to fix – is the position of the card reader screen. It’s about four foot up and points directly forward. The rather dim liquid crystal display is behind reflective glass. If your eyes are four foot above ground, it is perfect. For the rest of us, it's very difficult to use. This is seemingly in direct contradiction of the spirit of that giant virtual keyboard on the main screen. And why can’t the messages from the card reader be shown there instead – why is a second screen needed?
If you read the SVN Book chapter on serving SVN via Apache 2 you will see very simple Apache 2.0 virtual host examples that are implicitly correct. They’re in a book, after all. Apache gives good error messages but the one I got when I set everything up following the second example, like so:
DAV svn
# any "/svn/foo" URL will map to a repository /usr/local/svn/foo
SVNParentPath /usr/local/svn
read like this:
client denied by server configuration: /usr/htdocs
referring to a path that is nowhere in any of the .conf files for my Apache instance – it must be hardwired in somewhere, but I didn’t find out where.
I played about with permissions, to no avail*.
What I needed to do was add the conventional access controls, which of course might form part of the main Apache config on a given server (and therefore be inherited by the virtual host). In my case, and reflecting what’s happening gradually across all distributions and indeed the Apache source, there is much tighter security in the default configuration. Explicitly adding
Order allow,deny
Allow from all
(plus authorisation directives) got me back on track.
ServerName my.example.com
DAV svn
SVNParentPath /path/to/repositories
Order allow,deny
Allow from all
AuthType Basic
AuthName "Subversion repository"
AuthUserFile /path/to/htpasswdfile
Require valid-user
* this is Linux therefore whichever user will run the Apache process that serves the files needs to have read and write access to the repository and also read access to the parent directory, so check your group and world permissions on that directory.