The File utility performs a series of tests on each of the specified files in an attempt to classify it.With text files, the utility tries to determine the programming language by reading the first 512 bytes.
For executable files, the utility displays information about the platform, version and structure of the files libraries.
EX:-
user@ubuntu:~$ file /bin/cat
/bin/cat: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped
user@ubuntu:~$ file ./hello.rb
./hello.rb: a /usr/bin/ruby1.8 script text executable
Sunday, January 11, 2009
system admin vs network admin
sulekha
what exactly is the difference b/w sys admin and a n/w admin ? in my experience they both are the same, isn't it ? , but i keep hearing from some people that they are different ? what exactly is the true story ?
norbert74
My understanding is that they have a different focus. A sysadmin works mainly on servers like installing software, configuration etc.
A network admin works mainly on routers, switches and so on.
If you have package loss you go to the network admin, if you need an upgrade on a web server you ask the sysadmin.
acid kewpie
Well generally the network admin looks after the network and the systems admin looks after the systems. Sorry if that sounds crude / rude, but the clue is in the title. Of course many many many businesses combine the roles formally or informally, but past a certain size of infrastructure the work on the servers, server operating systems and applications is seperated from the work on the routers, switches and firewalls. Maybe you'd be suprised how many sysadmins have no idea about TCP/IP past an ip address and default gateway.
acid kewpie
personally I go to Fedex when I have a package loss. Packet loss i might talk to the network guys. ;-)
sulekha
Originally Posted by acid_kewpie
Maybe you'd be suprised how many sysadmins have no idea about TCP/IP past an ip address and default gateway.
well I haven't seen a system admin like that , what i have seen is the combination sort of thing, the guys who do both stuff
acid kewpie
Well that's down to the way a company works. If you can afford people who can cover an entire infrastructure at a suitable level then that's the better option usually - until sheer vast scale makes it unworkable. I used to be a strictly assigned network admin in a team of about 5 people at the higher technical level. Currently I'm right across the board with Linux and Network as specialities in a flexible pool of about 40... horses for courses really.
what exactly is the difference b/w sys admin and a n/w admin ? in my experience they both are the same, isn't it ? , but i keep hearing from some people that they are different ? what exactly is the true story ?
norbert74
My understanding is that they have a different focus. A sysadmin works mainly on servers like installing software, configuration etc.
A network admin works mainly on routers, switches and so on.
If you have package loss you go to the network admin, if you need an upgrade on a web server you ask the sysadmin.
acid kewpie
Well generally the network admin looks after the network and the systems admin looks after the systems. Sorry if that sounds crude / rude, but the clue is in the title. Of course many many many businesses combine the roles formally or informally, but past a certain size of infrastructure the work on the servers, server operating systems and applications is seperated from the work on the routers, switches and firewalls. Maybe you'd be suprised how many sysadmins have no idea about TCP/IP past an ip address and default gateway.
acid kewpie
personally I go to Fedex when I have a package loss. Packet loss i might talk to the network guys. ;-)
sulekha
Originally Posted by acid_kewpie
Maybe you'd be suprised how many sysadmins have no idea about TCP/IP past an ip address and default gateway.
well I haven't seen a system admin like that , what i have seen is the combination sort of thing, the guys who do both stuff
acid kewpie
Well that's down to the way a company works. If you can afford people who can cover an entire infrastructure at a suitable level then that's the better option usually - until sheer vast scale makes it unworkable. I used to be a strictly assigned network admin in a team of about 5 people at the higher technical level. Currently I'm right across the board with Linux and Network as specialities in a flexible pool of about 40... horses for courses really.
Mark Shuttleworth on ubuntu linux
ABSTRACT An overview of Ubuntu Linux given by Mark Shuttleworth at the Ubuntu Linux Developers Summit. Credits: Speaker:Mark Shuttleworth, November 9, 2006
Wednesday, January 7, 2009
Saturday, January 3, 2009
In the Linux file system what does the name usr , sbin stands for ?
sulekha
In the Linux file system what does the name usr , sbin stands for ?
some say that
sbin means secure binary or system binary ?
usr means user or unix system resources ?
can any one give the correct explanation ?
NB: i know the purpose of usr and sbin directories, i just want to know the naming thing
BBI Nexus BBI
As i understand it:
USR = Unix System Resource
SBIN = Superuser Binaries
RealPSL
Re: unix system resources
Interesting question with an answer here http://www.itworld.com/nlsunix071101
sulekha
in the same lines what about mnt,opt,srv and sys ?
mcduck
/mnt is for mounting devices, either for temporary mounting of a single device directly to /mnt, or for mounting non-removable drives into their own directories under /mnt.
(/media is for removable drives)
/opt is for optional programs, typically you'd install things that are from outside of your distributions package sources into /opt.
/sys includes kernel, firmware and system related files.
I'm not sure about /srv, I believe it has something to do with running servers/services.
/usr is for all user-related files & programs. Everything normal (non-admin) users need goes here. For example you'll find binary files for most of your desktop programs, like browsers, music players etc. in /usr/bin and all system-wide installed themes in /usr/share/themes. Most of the documentation and help files for your programs are in /usr/share/doc.
You can read pretty good explanations of the directory structure here: http://www.pathname.com/fhs/pub/fhs-2.3.html
albinootje
http://www.linux.org/docs/ldp/howto/HighQuality-Apps-HOWTO/fhs.html
Richard petersen
The sysfs file system is a virtual file system that provides a hierarchical map of your kernel-
supported devices such as PCI devices, buses, and block devices, as well as supporting kernel
modules. The classes subdirectory will list all your supported devices by category, such as
network and sound devices. With sysfs your system can easily determine the device file with
which a particular device is associated. This is very helpful for managing removable devices
In the Linux file system what does the name usr , sbin stands for ?
some say that
sbin means secure binary or system binary ?
usr means user or unix system resources ?
can any one give the correct explanation ?
NB: i know the purpose of usr and sbin directories, i just want to know the naming thing
BBI Nexus BBI
As i understand it:
USR = Unix System Resource
SBIN = Superuser Binaries
RealPSL
Re: unix system resources
Interesting question with an answer here http://www.itworld.com/nlsunix071101
sulekha
in the same lines what about mnt,opt,srv and sys ?
mcduck
/mnt is for mounting devices, either for temporary mounting of a single device directly to /mnt, or for mounting non-removable drives into their own directories under /mnt.
(/media is for removable drives)
/opt is for optional programs, typically you'd install things that are from outside of your distributions package sources into /opt.
/sys includes kernel, firmware and system related files.
I'm not sure about /srv, I believe it has something to do with running servers/services.
/usr is for all user-related files & programs. Everything normal (non-admin) users need goes here. For example you'll find binary files for most of your desktop programs, like browsers, music players etc. in /usr/bin and all system-wide installed themes in /usr/share/themes. Most of the documentation and help files for your programs are in /usr/share/doc.
You can read pretty good explanations of the directory structure here: http://www.pathname.com/fhs/pub/fhs-2.3.html
albinootje
http://www.linux.org/docs/ldp/howto/HighQuality-Apps-HOWTO/fhs.html
Richard petersen
The sysfs file system is a virtual file system that provides a hierarchical map of your kernel-
supported devices such as PCI devices, buses, and block devices, as well as supporting kernel
modules. The classes subdirectory will list all your supported devices by category, such as
network and sound devices. With sysfs your system can easily determine the device file with
which a particular device is associated. This is very helpful for managing removable devices
Subscribe to:
Posts (Atom)