help3002

It's UWAweek 47

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

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. How do I ask a good question?

Displaying the 4 articles in this topic

Showing 4 of 503 articles.
Currently 33 other people reading this forum.

UWA week 23 (1st semester, 1st exam week) ↓

final exam 2023 4a (all 4)

10:15pm Wed 5th Jun, ANONYMOUS

The Network File System (NFS) employs Remote Procedure Calls (RPCs) over the User Datagram Protocol (UDP). With reference to traditional file-system semantics, what problems does this choice of interprocess communication scheme introduce? What solutions have been implemented to address these issues? For this question, is it referring to potential issues such as the need for authentication across remote machine, potential networking errors like packet loss/duplication, and the need for XDR encoding? I'm a bit unsure on what the right direction is

final exam 2023 4a (all 4)

4:33am Thu 6th Jun, Christopher M.

ANONYMOUS wrote:

> The Network File System (NFS) employs Remote Procedure Calls (RPCs) over the User > Datagram Protocol (UDP). > With reference to traditional file-system semantics, what problems does this choice of > interprocess communication scheme introduce? > What solutions have been implemented to address these issues? > > For this question, is it referring to potential issues such as the need for authentication across remote machine, potential networking errors like packet loss/duplication, and the need for XDR encoding? I'm a bit unsure on what the right direction is

The emphasis is on the word 'semantics' - how things must work as expected. For example, authentication is not *required* for a file-system to work as expected.

final exam 2023 4a (all 4)

5:19pm Thu 6th Jun, ANONYMOUS

What is the traditional file system semantics? is this the same as the "read, write, append" command in the Linux File System? Hence, this will create an issue about the address space that the target's pointing to? Or the problem asks more about the potential issue of seemingly "idempotent" operations that lead to some issues if implemented without "file locking" assuming the UDP protocol the operations are done over UDP, making it unable to see whether the operations are done, crashed, or halted by the client(s), ended in a deadlock? (timeout might solve it)

final exam 2023 4a (all 4)

6:38am Fri 7th Jun, Christopher M.

ANONYMOUS wrote:

> What is the traditional file system semantics? is this the same as the "read, write, append" command in the Linux File System? Hence, this will create an issue about the address space that the target's pointing to? Or the problem asks more about the potential issue of seemingly "idempotent" operations that lead to some issues if implemented without "file locking" assuming the UDP protocol the operations are done over UDP, making it unable to see whether the operations are done, crashed, or halted by the client(s), ended in a deadlock? (timeout might solve it)

The matter of what are traditional file-system semantics should already be quite clear to you. What do we expect a file-system to do for us - to reliably store and transfer/copy data, not losing any data, not replicating any data. How do RPCs support these requirements in an environment where any request or reply can be lost, and any remote host can crash and reboot.