Linux inxtallation Post: 39437

2 More Discussions You Might Find Interesting

1. Fedora

Which is the better platform to learn UNIX/Linux (Kali Linux Vs. Red Hat or other)?

I just started a new semester and I started my UNIX class yesterday. I've already decided to use python along with my learning process but what I really want to use with it is Kali as my UNIX/Linux platform to learn off of since I already wanted to learn Cyber Sec. anyways. I just wanted to know if...

2. UNIX for Beginners Questions & Answers

Simple sed command not working; could be a Mac/Linux vs. PC/Linux issue

Hello, I am on a Mac and trying to clean up some monthly files with a very simple SED: sed '3,10d;/<ACROSS>/,$d' input.txt > output.txt (from the input, delete lines 3 - 10; then delete from the line containing <ACROSS> to the end of the file) then output to output.txt Even when I try...

LEARN ABOUT CENTOS

lsdev

LSDEV(8)                                                        Linux System Manual                                                       LSDEV(8)

NAME

       lsdev - display information about installed hardware

SYNOPSIS

       lsdev

DESCRIPTION

       lsdev  gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
       giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.

OPTIONS

       None.

FILES

       /proc/interrupts
              IRQ channels.

       /proc/ioports
              I/O memory addresses.

       /proc/dma
              DMA channels.

BUGS

       lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files  sometimes  use
       different  names  for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
       `keyboard' in /proc/interrupts.  This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).

       The program does however try to match lines by stripping anything after a space or open  parenthesis  from  the  name,  so  that  e.g.  the
       `serial'  lines  from /proc/interrupts match the `serial(set)' lines from /proc/ioports.  This attempt at DWIM might be considered a bug in
       itself.

       This program only shows the kernel's idea of what hardware is present, not what's actually physically available.

SEE ALSO

       procinfo(8).

AUTHOR

       Sander van Malssen <svm@kozmix.cistron.nl>

3rd Release                                                         1998-05-31                                                            LSDEV(8)