Please respond to the ANSWER in regards to the QUESTION that has been answered.

Question

Please respond to the ANSWER in regards to the QUESTION that has been answered.

ANSWER(respond to this):

Thus far, with my limited experience with Linux as an OS, it would seem to me that one of the biggest benefits that a pure-file architecture could provide is that working with solely files makes it so that changes to the file system are much more easily tracked than they would be on a proprietary OS such as Windows, which makes use of a different architecture. Changing any one small file on Linux can effect large-scale change, while doing the same on a relatively locked OS would either do nothing, or end up breaking something on the opposite side of the system, in a seemingly unrelated area.

Downsides, however, come back to what seems to be one of the largest downfalls of a strictly Linux-based system in a consumer market: the organization and manipulation of these files would be much more dependent on someone with a higher threshold of knowledge than the everyday user, seeing as the system appears to be a lot less automated than the offerings that are generally given to the open market. Added to that, if you are again working with a file system that incorporates a single, continuous file tree across multiple disks or partitions even, if even one important file displays any kind of corruption, the implications would be severe and far-reaching, as opposed to a system that uses integrated programs and a master file heirarchy.

Question:

Unix provides a powerfully unified file system. Everything is a file: data, programs, and all physical devices. the entire file system appears as a single large tree of nested directories, regardless of how many different physical devices (disks) are included. What might be a positive, or negative, with this type of file system design?

Explanation / Answer

Pros-  multi-user
multi-tasking, priorities, job control
good scalability, built-in TCP/IP stack

built-in standard shell with open functionality

"client-server" concept came from Unices

Cons:no program development kits

no realtime functionality in major releases

incompatibilities in source code because of different
leading standards (SVID/BSD/IBM).

incompatibilities in source code because of different
leading standards (SVID/BSD/IBM).

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.