Suppose that i have the following function declaration:
struct x_struct my_function( struct x_struct val );
while this is legal, it suffers from an inefficiency. what is the problem?
a.
i have no idea. this is not the
b.
the function will execute slowly because "val", and the return value of the function will both require a lot of data copying. this is because c is call-by-value.
c.
the function can not alter the original value of "val", so passing it is not useful.
d.
the function can alter the original structure "val", making the code hard to follow.
e.
the function will execute slowly because "val", and the return value of the function will both require a lot of data copying. this is because c is call-by-reference.

You have a linux system that has a 1000gb hard disk drive, which has a 90gb partition containing an ext4 filesystem mounted to the / directory and a 4gb swap partition. currently, this linux system is only used by a few users for storing small files; however, the department manager wants to upgrade this system and use it to run a database application that will be used by 100 users. the database application and the associated data will take up over 200gb of hard disk space. in addition, these 100 users will store their personal files on the hard disk of the system. each user must have a maximum of 5gb of storage space. the department manager has made it very clear that this system must not exhibit any downtime as a result of hard disk errors. how much hard disk space will you require, and what partitions would you need to ensure that the system will perform as needed? where would these partitions be mounted? what quotas would you implement? what commands would you need to run and what entries to /etc/fstab would you need to create? justify your answers.