To get hardware details (Linux commands)

To know about the hardware our system has
lspci
lspci -v (more details)
lspci -vv (whatever system know about)

2) USB
----------
lsusb
lsusb -v (more details)

3) to know disk connected
----------------------
fdisk
fdisk -l

hardware check at run time
---------------------------
kudzu - runs at boot time, to detect and configure new h/w
ddcprobe - if above fails, user must be root(only available on x86 or x86_64)

BIOS data gadhering
----------------------
most BIOSes are SMBIOS (system management BIOS) or DMI (desktop management interface)

- biosdecode
- dmidecode (o/p these are not 100% accurate)
- ownership
- vpddecode


Listing and configuring Kernel modules
--------------------------------------------

- modinfo
- modprobe (used for loading module manually)

HAL(hardware abstraction layer)
---------------------------------
HAL daemon run when the system is running to detect new hardware
The HAL daemon
collects information about the device from the kernel as well as other resources

Comments

Post a Comment

Popular posts from this blog

Kind of malware and Names for malicious code

We commonly come across the security issues while using PC/Smart phones, we commonly call it as virus attack. here is gist of few terms(very few) what are the terms used to explain kind of threats malicious code(malware) is mainly classified based on the ability to self replicate i.e. 1) Self replicating malware          example: Virus, Worms       2) Non-self replicating malware          example: Trojan horse Non-replicating malware typically hide their presence on computer or its malicious function We call as Virus if it attaches to itself to running program and start creating damage to victim, it depends on the execution of the  host program,  at some point of execution Virus hijacks execution of running program and executes the malicious code, which could create panic or cause damage to victim we call as Worm  is program , it will look for victim(computer which is not protected) through network ...
Read more

Know tracers mostly available at Linux

following are the tracers can be used for performance tuning and debugging in Linux 1) strace -- system call tracer 2) ltrace -- library tracer 3) ptrace -- Process tracer 4) ktrace -- kernel tracer originally developed for BSD, it has better performance than strace 5) dtrace -- dynamic tracer (hopefully ) can be used to tune both kernel and user application originally developed for Solaris 6) ftrace -- some times called as function tracer 7) btrace -- it is dynamic tracing tool for the Java programs and it is used for debugging java programs 8) xtrace -- is used for X server, it is for displaying the communication between the clients and the server in an human readable form 9) rtrace -- is a program for image synthesis by the ray tracing method; rtrace traces rays from the standard input through the RADIANCE scene given by octree and sends the results to the standard output 10) mtrace -- in Linux, The mtrace interprets the output from when the MALLOC_TRACE environ...
Read more

cases of context switch

system calls and library functions differs in terms of invoking. in Unix based operating system, system calls generate the exception(trap), and invoking system calls will lead to context switch, in case the current process running is not most eligible process to run. where as in case of library function no context switch will be made so executing library function is faster than the system calls. what are all the reasons for context switch of the process following are the cases when context switch can occur 1. if process wants go for sleep 2. process do exit 3. while returning from the system call and it is not most eligible process to run 4. when it returns from the interrupt and it is not most eligible process to continue
Read more