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 manual entries which I could access > before ...
My not-so-very-well-grounded quess is that when you used floppies to install your debian, you missed too many packages, which were depending on each other... In my case I had first some problems because of defect multicd-installation-program. It didn't install at all a basic packet (dpkg-perl) and I made a mistake to install with dpkg -i method quite many packages separately and my dselect was some time totally out of order. It showed uninstalled packets installed and vice versa. Finally I had to reinstall the whole thing. Now it works quite perfectly. Could it be possible for you to connect your computer with another one possesing a cd-rom driver? Is it possible to use somehow for example laplink cable to connect computers to use the other computer's cd-rom-drive to install the other? [EMAIL PROTECTED] > 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". I was thinking that this might be the case because > something was not installed properly, or because something which needs > to be installed is not installed at all. Would this be a likely > explanation (and if so, how can I find out what package is needed to > make the COMMAND work - I suppose this is not the same as asking what > package contains a certain FILE), or is there an alternative scenario > that might explain the present state of affairs? Are there simply > certain parameters specifically to run "make config" that I am > blissfully unaware of? > > -- > birgit kellner > department for indian philosophy > hiroshima university > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
