Birgit Kellner wrote:
>The basic and (perhaps deceptively) simple question is: I cannot use
>certain basic commands such as "make config", where bash keeps returning
>"command not found".
Like this?:
$ bake config
bash: bake: command not found
If you get that for make, you need to install t
On Mon, 14 Dec 1998, Birgit Kellner wrote:
> Thanks a lot to everyone who has replied to this thread so far. I
> managed to sort out some package conflicts with dselect, but they have
> not resolved the basic problem. What's more, dselect has configured man,
> to the effect that I cannot find manu
Quoting Birgit Kellner ([EMAIL PROTECTED]):
> I thought that I had successfully installed Debian, but it so happens
> that bash replies "command not found" to just about every second command
> I type, including such basic things as "make config". Before I lose my
> temper, erase everything and star
Thanks a lot to everyone who has replied to this thread so far. I
managed to sort out some package conflicts with dselect, but they have
not resolved the basic problem. What's more, dselect has configured man,
to the effect that I cannot find manual entries which I could access
before ...
The basi
Birgit Kellner wrote:
>(1) How can I check which packages are and which are not installed on my
>system?
dpkg -l
>(2) In case a particular command is not recognized, how can I find out
>what package is needed to make it work?
1. To look for in the list of all _installed_ files:
I thought that I had successfully installed Debian, but it so happens
that bash replies "command not found" to just about every second command
I type, including such basic things as "make config". Before I lose my
temper, erase everything and start from scratch -
(1) How can I check which package
6 matches
Mail list logo
