Build a code for minix

Project4: A Minix Disk Program (Due at 11:59:59pm on 03/16/2020 (EDT)) Group Arrangment. You are asked to develop a Minix Disk program that allows users to access a Minix disk locally mounted on a computer. You are expected to use C programming language. In your program, all file I/O related operations should use the system calls discussed in our lectures, including open(), read(), write(), lseek(), close(), and you should not use those library functions like fopen() and fread(). Your implementation must work on Linux machine in FH131 lab. Required Modules: [90%] Client Environment (a minix console): the console (interface) allows users to access the minix disk by using the following commands: [5%] help: show the commands supported in the minix console. [5%] minimount argument: mount a local minix disk, where "argument" is a iminix image file, e.g., imagefile.img. [5%] miniumount: umount the mounted minix disk. [10%] showsuper: to list the information of the super block. For example: minix: showsuper number of inodes: 3424 number of zones: 10240 number of imap_blocks: 1 number of zmap_blocks: 2 first data zone: 112 log zone size: 0 max size: 268966912 magic: 5007 state: 0 zones: 0 Note that the above numbers should be extracted from the minix disk rather than being hard coded (you won't received any credit for the hard coding). [30%] traverse [-l]: list the content in the root directory. Note that you don't have to show the entries of "." and "..". For example: minix: traverse [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] dir1 [login to view URL] [login to view URL] [login to view URL] [login to view URL] When switch -l is turned on (long list), all detailed information is shown, including the file type, 9 permission bits, user ID, file size (in bytes), last modified date (with year), and the file/path name. For example: minix: traverse -l -rw-rw-r-- 1000 670 Sep 20 2012 [login to view URL] -rw-r--r-- 1000 763 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 333 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 786 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 404 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 786 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 408 Dec 14 2010 [login to view URL] -rw-rw-r-- 1000 358 Sep 20 2012 [login to view URL] -rw-r--r-- 1000 1067 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 444 Dec 14 2010 [login to view URL] -rw-rw-r-- 1000 508 Sep 20 2012 [login to view URL] -rw-r--r-- 1000 967 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 648 Dec 14 2010 [login to view URL] drwx------ 1000 128 Oct 27 2014 dir1 -rw-rw-r-- 1000 630 Sep 20 2012 [login to view URL] -rw-rw-r-- 1000 1063 Sep 20 2012 [login to view URL] -rw-r--r-- 1000 226 Dec 14 2010 [login to view URL] -rw-r--r-- 1000 278 Dec 14 2010 [login to view URL] Hint: the mode field (a 2-byte unsigned integer) in inode struct uses the following flags: S_IFMT 0170000 bit mask for the file type bit fields S_IFSOCK 0140000 socket S_IFLNK 0120000 symbolic link S_IFREG 0100000 regular file S_IFBLK 0060000 block device S_IFDIR 0040000 directory S_IFCHR 0020000 character device S_IFIFO 0010000 FIFO S_ISUID 0004000 set-user-ID bit S_ISGID 0002000 set-group-ID bit (see below) S_ISVTX 0001000 sticky bit (see below) S_IRWXU 00700 mask for file owner permissions S_IRUSR 00400 owner has read permission S_IWUSR 00200 owner has write permission S_IXUSR 00100 owner has execute permission S_IRWXG 00070 mask for group permissions S_IRGRP 00040 group has read permission S_IWGRP 00020 group has write permission S_IXGRP 00010 group has execute permission S_IRWXO 00007 mask for permissions for others (not in group) S_IROTH 00004 others have read

Project ID: 24305866