It's UWAweek 9 (1st semester, week 1)

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying selected article
Showing 1 of 1168 articles.
Currently 1 other person reading this forum.


 UWA week 39 (2nd semester, week 9) ↓
SVG not supported

Login to reply

👍x1
helpful
12:45pm Fri 29th Sep, Christopher M.

ANONYMOUS wrote:
> 2. so is there an answer for my 2nd question? or did I miss something on the project page.
No answer for the 2nd question. I started to write a small clarification for it, but then realised that there is no correct answer. For example, in determining which of two files we should copy (from) - we presume that 2 candidate files have the same relative location, same filenames, (now) same modification-time, (hmmm, OK, same size, ....., but different contents. There's no way to meaningfully state which should be the file to be copied. And even if we someone considered the contents/text, which file should win? So, when testing your projects, we'll ensure that no 2 files have the same modification time (avoiding the potential problem).
> 3. for -n, how do we identify the files to be copied without syncing them then?
Your approach may be wrong. You first identify what should be copied and then (if no -n option) you do the copying.
> what does it mean by "it will report the actions that would be taken in synchronizing them, but no actual copying will be performed"? where do we report it?
Providing the -n option also sets the -v option and so, whether actually copy files or not, you may wish to annotate what your program is doing (or *would be doing* is -n is provided).

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy