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 start from scratch - > > (1) How can I check which packages are and which are not installed on my > system?
Can we just check that you have run dselect the first (automatic) time, and haven't just installed the base system (roughly five floppies-worth). For hamm, dpkg -l will list about 59 packages if you've just installed the base system. It will list about 145 packages if you skip the "Package Selection" step just after typing the root password and creating the first user, and just take what dselect "forces" on you. One of these packages is make, for example. I assume there are people who prune that list the first time they see it, because a FAQ on this list is "Where is as86?" and the answer is "In package bin86" which is one of the 145 packages Debian installs by default. > (2) In case a particular command is not recognized, how can I find out > what package is needed to make it work? > > Additional question: What does "mktimes" mean? Could we have more context please? Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
