Re: [ARMini-support] ARMX6 OS update 7 released
- From: A Rawnsley <rcomp@xxxxxxxxxxx>
- To: <armini-support@xxxxxxxxxxxxx>
- Date: Wed, 06 Apr 2016 16:50:45 +0100
In message <a1b69c6c55.boase@xxxxxxxxxxxxxxxxx>
Bernard Boase <b.boase@xxxxxxx> wrote:
On 5 Apr, rcomp@xxxxxxxxxxx typed:
Looking through the relevant file, the only line that I can see that
might trigger this copies files to the "Sound" directory on the main
drive. Perhaps you have deleted this?
Thanks for that, Andrew. Spot on! I restored that directory from
SDFS::System.$.SSD.Sound to SCSI::SSD.$.Sound and update 7 completed
correctly (5.23 18-Mar-2016).
The experience raises an interesting question: Precisely which objects
(directories and files) and where placed does a RISC OS operating
system developer expect/need for fault-free upgrades to systems that
are bound to have been personalised? This would apply across the
board: in my case only R-Comp and ROOL with Iyonix, ARMX6, and RPi.
In this, admittedly trivial, example I had moved the apps in directory
Sound into $.Apps.Audio and the data into $.Data.Music.Maestro because
I want to keep apps organised by topic (like Packman), and separate
apps from data. So $.Sound became redundant.
Given how Apps/ResourceFS works, the "Packman" method of installing into
sub-folders of Apps is fairly bad idea IMHO, as the computer will have no
clue where things are. There's no recursion down the directory tree, so
subfolders are effectively ignored, and create a disparity between Apps on
the iconbar and Apps on the hard drive. I *really* don't like that.
To my mind, it rather defeats the purpose of the "magic" Apps folder.
To be honest, the script probably should have checked to see that the
Sound folder existed, as you're right that it is one that people might
delete. Once we issue a SP with the HDMI audio files in, they won't be
needed in the "OS updater" anyway.
The following folders should be considered sacresanct really (on any RISC
OS system):
!Boot
Apps
Printing (!Printers normally resides here, and may be !Boot-ed)
Utilities (contents are filer_booted by an ordinary !Boot)
The standard ROOL disc image shares much in common with the original Acorn
RiscPC-era image. We basically follow the same standards, so Sound is
present just as it was historically. I often wonder whether we *really*
need an empty "Public" folder on every machine, but...
My feeling is that folks are best advised to stick to the standard
Acorn/ROOL/R-Comp folder layout where possible, and add to, rather than
subtract from.
In our standard disc image, the one folder which I'd say could be fairly
safely removed is the "Develop" one, if you're not interested in
programming etc.
Obviously our RCI disc image is considerably expanded on that of ROOL etc,
but I've gone to some pains to try and do so in a way that is sensitive to
the work that has gone before - Acorn, ROL, Castle, ROOL...
Kind wishes,
Andrew
--
R-Comp
22 Robert Moffat, High Legh, Knutsford, Cheshire WA16 6PS
Tel: 01925 755043 Fax: 01925 757377
http://www.rcomp.co.uk
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
