Re: getting full package name

2004-09-07 Thread Johann Koenig
On Monday September 6 at 11:18pm Craig Jackson <[EMAIL PROTECTED]> wrote: > Hi, > If I would like to know the name of a package, for example dhcp, > installed on the system, I would run > > dpkg -l | grep dhcp > > Most of the time I get the right name and I'm happy. But there are > times when t

Re: getting full package name

2004-09-06 Thread Oliver Elphick
On Tue, 2004-09-07 at 05:18, Craig Jackson wrote: > Hi, > If I would like to know the name of a package, for example dhcp, > installed on the system, I would run > > dpkg -l | grep dhcp > > Most of the time I get the right name and I'm happy. But there are times > when the name of the package is

Re: getting full package name

2004-09-06 Thread Kevin Mark
On Mon, Sep 06, 2004 at 11:18:42PM -0500, Craig Jackson wrote: > Hi, > If I would like to know the name of a package, for example dhcp, > installed on the system, I would run > > dpkg -l | grep dhcp > > Most of the time I get the right name and I'm happy. But there are times > when the name of th

Re: getting full package name

2004-09-06 Thread Jacob S.
On Mon, 6 Sep 2004 23:18:42 -0500 Craig Jackson <[EMAIL PROTECTED]> wrote: > Hi, > If I would like to know the name of a package, for example dhcp, > installed on the system, I would run > > dpkg -l | grep dhcp > > Most of the time I get the right name and I'm happy. But there are > times when t

getting full package name

2004-09-06 Thread Craig Jackson
Hi, If I would like to know the name of a package, for example dhcp, installed on the system, I would run dpkg -l | grep dhcp Most of the time I get the right name and I'm happy. But there are times when the name of the package is so long that I cannot tell what the name is. In that situation if