C Program in Linux Environment - Simple

( Detailed description and files attached ) SUMMARY - (1) complete user code "frg.c" ; (2) write kernel code "lab2.c" to implement sys_lab2_contiguousness(); (3) write user code "contiguousness.c" that uses sys_lab2_contiguousness(). (4) write user code "read_file.c" that file is in’root_fs’ and runs on your UML kernel. This program sequentially reads an entire file from its beginning and print its I/O bandwidth. Details- There are four programs in this section: (1) lfb.c: a program which lists all the LBNs of a file or files in a directory. (LBN stand for logical block number, which represents the block layout on a device). This program has been fully implemented. (2) mfb.c: a program that moves a block in a file to a designated LBN on a device. This program has been fully implemented. (3) frg.c: a program that fragments blocks of a block across the device. Usage: ./frg device pathname The file specified by the ‘pathname’ on the ‘device’ will be fragmented across the device, i.e., the blocks of the file are moved to any random locations on the device. This program has not fully implemented, and you are required to complete it. In the program, function ‘fill_free_block_bitmap()’ is used to collect all the free blocks on the device and place them in an array called ‘free_blk_bit_map[]’ (a global variable). It then uses random function ‘rand()’ to select a free block from the array and a file block into that location (LBN). This is actually the core operation of program ‘mfb.c’ and is repeated for each block in the file. This program may modify the filesystem. So be very cautious and do backup of important data in your ‘root_fs’ before test run of your frg.c. (4) dfg.c: a program that defragments a file, trying to move blocks of a file to a contiguous area on a device. This program has been fully implemented. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Linux C