Craig Sanders wrote: > > libc5/libc6 > > what's the problem with libc5 and libc6? they both work in debian.
no problem, only a question mark for a newbie at installation > the usual cycle with dselect is: > > 1. Update > 2. Select > 3. Install > 4. Configure > 5. repeat steps 3 & 4 until there are no problems reported Here i got stuck on my first attempts to install a running system (ok, but only after selecting tons of packages and having no idea, what i'm actually doing) > no, not with the standard "mounted" method. they should be logged. but > they aren't. > > there is another install method called "mountable" which logs everything > to /var/log/dpkg-mountable. good, this is what i wanted > some packages also have easy to use configure scripts. sendmail, apache, > and bind are the most obvious examples. there has been a lot of hard > work put into the config scripts for those packages... and it shows, > they really are excellent. Yes, they are very good. > > At least the package-descriptions should contain some info about all > > the installed files (their names and their destination-paths). Ok, but to be more precise. The path/file descriptions should be integrated in the dselect-screen and in the logfile. Almost like in other installers (copy file x.y to /destination/path/x.y - successfull, and so on). With those points changed, dselect would be the perfect tool for big installations (in my opinion). dpkg is already best. Mac -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .