handle the System.IO.IOException that will be raised if the If this is not appropriate for your application, you can whether it already exists, and create it if it does not. System.IO.FileInfo fileNames = dirInfo.GetFiles("*.*") įoreach (System.IO.FileInfo fi in fileNames)Ĭonsole.WriteLine("",fi.Name, fi.Directory) Get the files in the directory and print out some information about them. System.IO.DirectoryInfo dirInfo = di.RootDirectory Ĭonsole.WriteLine(()) System.IO.DriveInfo di = new Get the root directory and print out some information about it. obtain names of all logical drives on the computer. The following example shows various ways to access information about files and folders. The System.IO.Directory and System.IO.File classes provide static methods for retrieving information about directories and files. You can create instances of these classes by passing a string that represents the name of the file, folder, or drive in to the constructor: System.IO.DriveInfo di = new can also obtain the names of files, folders, or drives by using calls to DirectoryInfo.GetDirectories, DirectoryInfo.GetFiles, and DriveInfo.RootDirectory. They also contain methods for opening, closing, moving, and deleting files and folders. The FileInfo and DirectoryInfo classes represent a file or directory and contain properties that expose many of the file attributes that are supported by the NTFS file system. NET, you can access file system information by using the following classes: This package provides various utilities that are useful for maintaining a working BIND installation.In. You can use aptitude show pkgname or dpkg -version pkgname aptitude show bind9utilsĭepends: libbind9-80, libc6 (>= 2.14), libdns81, libisc83, libisccc80, libisccfg82 : tools for verifying that the DNS server is operating properly. : (routines for applications to use when interfacing with DNS) and : which resolves host names to IP addresses a resolver library Summary : The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) serverĭescription: BIND (Berkeley Internet Name Domain) is an implementation of the DNS Loading mirror speeds from cached hostfile Loaded plugins: downloadonly, fastestmirror, security You can use yum info packagename or if it installed then use rpm -version packagename ~]# yum info bind97 There is NO WARRANTY, to the extent permitted by law.Īlso you can use yum or aptitude based on distro you are using This is free software: you are free to change and redistribute it. License GPLv3+: GNU GPL version 3 or later. You can use ldconfig -v | grep libraryname ,Īlso command has option command -V or binaryfile -versionĬopyright (C) 2011 Free Software Foundation, Inc. Or you can rely on the program itself or your packaging system, as Rahul Patil wrote. If you simply want to get the library version, you can play with: readelf -d /path/to/library.so |grep SONAMEĪFAIK, there's no such info (at least not by default) in executable files. Where elffile can be either an library of an executable. If you want to verify, what exactly is in which ELF file, you can try to run: readelf -a -W elffile When you link a program against this library, the linked program will store the soname of the library under NEEDED entry in the dynamic section. In the library file libtest.so.1.0.1, there will be an entry called SONAME in dynamic section, that will say this library is called libtest.so.1. libtest.so - Symlink to libtest.so.1 used for linking.libtest.so.1 - Symlink to libtest.so.1.0.1, having the same name as soname.libtest.so.1.0.1 - The library file itself, containing the full version.If you have library, say libtest.so, then you usually have: The full version is usually stored as a part of the library file name. What you have in there is the name of the library, the soname, which includes the major version. The version info in not explicitly stored in an ELF file.
0 Comments
Leave a Reply. |