Package Manager-B tech final year project

Our purpose is to introduce a Package deal Supervisor for Supply Code Set up in Linux distributions. This Package deal Supervisor would itself care for upkeep of full system, which up to now has been a really cumbersome job for any administrator. This LPM together with a Registry would offer another back-end for numerous textual content configuration information.

Thus, as a substitute of every utility having its personal text-configuration information, our utility supplies a common, hierarchical, quick & constant namespace & infrastructure to entry configuration parameters by a key-value pair mechanism.

This would come with creation of separate entities:-

• native database for native machine administration & upkeep.
• registry for native in addition to distant administration of the machine configuration.

• I386 Structure Machines.
• Crimson Hat Linux 9.Zero Working System.

The project has some {hardware} & software program necessities which can be described as follows:-

• Crimson Hat Linux 9.Zero with kernel(2.4.23)
• Linux GUI builder bundle – QT
• A C/C++ IDE for Linux – Anjuta
• Elektra API’s

• Two PC’s with standard configurations (128/256RAM P4 Processors and many others.)
• LAN connection b/w the machines.

It has been lengthy desired to have some form of Package deal Administration system in current Linux atmosphere. Because of the pre-existing characteristic of being Open Supply, any bundle could be put in & used, nearly wherever in a Linux system (be it Private/Server configuration).

Right this moment’s GNU/Linux techniques are a sum of unbiased elements collected from Open Supply Neighborhood. Every of them already has a working, however egocentric configuration system.

One of many system (maintained by an administrator X) has an Apache bundle (say model 1.4) put in from source (as a substitute of RPM distribution).After a while a brand new administrator (say Y) begins sustaining that system. Suppose he involves know that Apache (model 1.4) has a critical safety flaw and he installs a more moderen model (2.0). Now to scrub the system extra effectively he has to successfully delete all of the information (foremost information in addition to help information) from numerous places which change into a really tedious job itself.

Thus we understand that the general upkeep of full Linux system is a extremely cumbersome course of which any administrator has problem in finishing up, each effectively & successfully.

Now that the issue at hand may be very a lot clear, the following & foremost step is as to how the information about numerous packages, getting put in on the system, must be observe down & saved. One of the essential design points that wants utmost consideration is:-

The present system mustn’t change. It signifies that we can not go about altering the complete set up methodology, only for the sake of acquiring the specified information. The reason being if the prevailing system adjustments, there’s a excessive chance that the newer system is by no means welcomed by the prevailing developer & consumer society.

Thus after contemplating numerous different points, the answer that has been finalized is as follows:-

We have to entice the information when & the place it’s getting created & moved into the prevailing system.

This information then must be saved & afterward retrieved in an environment friendly & efficient approach that may suite our project necessities.

Thus the whole project now will get divided into 4 completely different phases. They’re:-

• Assortment of all the information.
• Extraction of Info.
• Environment friendly storage of the information.
• Efficient retrieval of this information.