Task 1. Originally Linux/UNIX systems had one all-powerful user called root that managed systems. Discuss the risks of having a single root user and how more limited management abilities can be given...

Task

1. Originally Linux/UNIX systems had one all-powerful user called
root
that managed systems. Discuss the risks of having a single root user and how more limited management abilities can be given to others users on Linux/UNIX systems. Include a sample generic policy for a limited user from which a configuration could be written. (500 words)

2. Attempt to install the following web applications on Linux. The Moodle Learning Platform link: http://moodle.org, The Etherpad shared document editing system link: http://etherpad.org, and The Community version of the Alfresco Enterprise Content Management System link: http://alfresco.com. You should write a short report documenting each of the installations even if you don't get the applications running. (3 to 5 pages per report)

Rationale

This assessment item is designed to test your ability formulate methods for protecting data and services, to create and manage information services, and produce coherent and knowledgeable writings in these topic areas.

Marking criteria

Question 1 (6 marks)	FL	PS	CR	DI	HD
Quality of discussion	No content	Very brief content	A few sentences on email	A well-developed paragraph on email and an alternative	Several well-developed paragraphs discussing several alternatives

Question 1 (1 mark)	Unsatisfactory	Satisfactory
Quality of sources	No sources cited or uses Wikipedia or similar sources	Several credible sources used that support the discussion

Question 2 (2 marks)	Unsatisfactory	Satisfactory
Evidence of a web server working on Linux/UNIX	None	Screenshots or other evidence

Question 2 (10 marks)	FL	PS	CR	DI	HD
Quality of Report and Method to avoid log file loss	No method or a method doesn't work	A method that could work with major work	A method described that could work with minor work	Good description of an appropriate method that works	Outstanding description of an appropriate method that works

Answered Same DayDec 24, 2021

Answer To: Task 1. Originally Linux/UNIX systems had one all-powerful user called root that managed systems....

David answered on Dec 24 2021

122 Votes

Answer 1
In figuring, the superuser is an unique user account utilized for framework organization.
Contingent upon the working framework (OS), the real name of this account may be: root,
executive, administrator or boss. Now and again the real name is not critical, rather an approval
banner in the user's profile figures out whether regulatory capacities might be performed.
In Oses which have the idea of a superuser, it is by and large suggested that most application
work be carried out utilizing a customary account which does not can make framework wide
changes.
In Unix-like machine Oses, root is the ordinary name of the user who has all rights or consents
(to all documents and projects) in all modes (single- or multi-user). Option names incorporate
nobleman in Beos and symbol on some UNIX variations. BSD regularly gives a toor ("root"
composed regressive) account notwithstanding a root account. Despite the name, the superuser
dependably has user ID 0. The root user can do numerous things a standard user can't, for
example, changing the responsibility for and tying to system ports numbered beneath 1024. The
name "root" may have begun on the grounds that root is the main user account with authorization
to alter the root index of an UNIX framework and this catalog was initially thought to be root's
home registry.
The principal...

SOLUTION.PDF

Task 1. Originally Linux/UNIX systems had one all-powerful user called root that managed systems. Discuss the risks of having a single root user and how more limited management abilities can be given...

Answer To: Task 1. Originally Linux/UNIX systems had one all-powerful user called root that managed systems....

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment