mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michiel de Boer <x@rebelhomicide.demon.nl>
To: Milton Mobley <miltmobley@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: need source for lspci, lsusb, etc.
Date: Wed, 16 Aug 2006 21:17:47 +0200	[thread overview]
Message-ID: <44E36F5B.905@rebelhomicide.demon.nl> (raw)
In-Reply-To: <af203d350608161137l7b0b1e74i94c4480aecbd4f3d@mail.gmail.com>

Milton Mobley wrote:
> Thanks for your suggestions. My Linux computers are not connected to 
> the net,
> so I am focussing on getting tarballs which I can then move from
> Windows to Linux
>
> On 8/15/06, x@rebelhomicide.demon.nl <x@rebelhomicide.demon.nl> wrote:
>> Milton Mobley wrote:
>> > Hi, I am building kernels from kernel.org sources, and am having 
>> problems
>> > detecting certain pci and usb devices (I didn't change the kernel code
>> > much yet).
>> > Where can I find the sources for programs that live in /sbin,
>> > /usr/sbin, etc.,
>> > especially lspci, lsusb, lsmod?
>> > -
>> > To unsubscribe from this list: send the line "unsubscribe
>> > linux-kernel" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> > Please read the FAQ at  http://www.tux.org/lkml/
>> >
>> Milton, your distribution of Linux should provide those.
>> For Debian Linux for example, you'd do:
>>
>> $ dpkg -S lspci
>> pciutils: /usr/bin/lspci
>>
>> ..and you note that lspci is in the 'pciutils' package.
>> You could then do as follows:
>>
>> $ apt-get update
>> ....
>> $ apt-get source pciutils
>>
>> The source would be downloaded and unpacked in the current working
>> directory.
>>
>> Regards, Michiel de Boer
>>
>
In that case, google for:
source pciutils
source usbutils
source module-init-tools

You should get your hands on a tarball quickly.

Regards, Michiel de Boer

PS:
two tips:
- use "reply to all" when you reply to a message in the lkml
- when you quote previous discussion, place your answer below the quote, 
instead of above ;)
These things are common courtesy & practice on the lkml.
(see: http://kernel.org/pub/linux/docs/lkml/ for reference)

      parent reply	other threads:[~2006-08-16 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  3:14 Milton Mobley
2006-08-16  3:47 ` x
     [not found]   ` <af203d350608161137l7b0b1e74i94c4480aecbd4f3d@mail.gmail.com>
2006-08-16 19:17     ` Michiel de Boer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E36F5B.905@rebelhomicide.demon.nl \
    --to=x@rebelhomicide.demon.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltmobley@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®