On Thursday 06 September 2001 11:32, Marco Fioretti spoke wisely: <snip>
> > dselect > > apt-get install <all the packages you need> > > > > i would recommend dselect, because you get the recommendations for > > additional packages, too, not only the absolutely needed depends. But > > that could be against that, what you really want to do. > > Which one of these methods is best for script use right after > installation, i.e.: > > No net access yet > Only the official debian CDs available > Minimum manual intervention (hopefully just > changing the CD when asked?) Then you should use apt-get. If you install a bare debian system apt/dpkg asks you, how many questions it should ask during installation. If you set the priority to critical, you don't get almost any questions during installation. If you want to script, i recommend using apt-get because thats the simpliest way. Simply make a script: apt-get install <the packages you need> there should be a parameter --assume-yes which causes even less questions to be asked. see man apt-move > I am quite expert with red hat, and have started to study debian > recently. > One of the things I found most confusing is the relationship betweeen > apt, > dselect (?dpkg?) and what not. When do you use one or the other? Why? > Are there any online documents explaining this specific issues? > > TIA, > Marco Fioretti in short: dpkg is the backend as rpm is on suse or redhat. apt-get and dselect are frontends. With dselect you normally use apt-get as a middle-part between dselect itself and dpkg. the frontends have in common that the "acquire" the packages automatically from cdrom, ftp, http, ... with dpkg you can only install packages you have as files directly with dpkg -i <packagefile.deb> For further info have a look at: http://www.debian.org/doc/ddp http://www.linuxpress.com/debusered2.html#page107 hope that helps -- Daniel Kleine-Albers [EMAIL PROTECTED]
