n

Loading and Linking in OS
Linking
The linking is done in the operating system. We can have static linking or dynamic linking. The dynamic linking was performed in 1965 to the multi system. There is commercial operating system like the Microsoft Windows and Unix which support growth linking types. It has shared libraries and windows has dynamic link libraries.
Packages and Modules
Java package concept has relation with the second module of modules. The package can be defined as a collection of types which can be interfaces or the classes and modular two modules is known for storing the record types. In Java text importing can be defined as providing the definition of the field or class in the public format. For all the default values it has only the visible feature in their own package.
We can import and it will be treated as the operation, and it will stab lish the inter class relationship. All the inter class relationships needs to be resolved with the help of linker or the binder. The linking task has recursive nature because if we want to link a class then it will need the linking of all the imported classes. The inter class relationships cannot be performed with the help of Java import statement as it will only extend the name space which is used for the name qualification when we are compiling the code.
They can be established implicitly with the help of class names which can be used for the static method calls or the access of static variables. We can use PJC, but it will use the import table for every runtime class descriptor to the administer like interclass relationships. The separate compilation of the classes can be done but it will ask him the linker to observe consistency in the version of all the inter class relationships. The questions trickle down re compilations as it will invalidate the clients if we are invalidating some plastic then it be invalidated glasses which are importing that particular class.
Traditional linking strategies
If we talk about the traditional operating system than the linker and compiler are used as the separate programs. The compiler is used to translate source text into the object files which has export and import tables. The inter module calls can we realise with the help of in direction which is performed on the import table. The linker is used to check the consistency and fills the import table.
We can define the address is at the loading time and modules are available for relocation. There are few linkers which can be used to eliminate the end direction for inter module calls as it can easily modify the object code as insert direct calls. If we are following this approach, then it needs that linker is able to find every inter module called. This information will need considerable amount of memory and time add it will have one entry for every call, but this can be realised if we are chaining the place holders which are present in the code itself.
The static linking can be defined as a method in which we will copy all the required libraries into the executable file. All the target address is which are required for the inter module references can be determined when we are linking the code and it can be directly inserted into the executable file with the help of the linker.
The procedure calls will show maximum efficiency as it will not have any in directions and the linking errors can be easily detected at the linking time. But on the other side it will waste a lot of memory which means that we will link the Microsoft foundation classes statically which will consume memory for each application which is equivalent to 1.9 megabytes. Any library modifications can be done but it will need the client re compilation.
The dynamic linking can be realised when we are inserting any symbolic reference in the object files for the library...