dselect (Re: Using dpkg for a custom installation from cdrom media)
On Mon, 2 Mar 1998, Henry Hollenberg wrote: I have a particular list of packages I would like to install saved in a file and am using a 3 CD-ROM Debian 1.3.1 set I got with Dale Scheetz's book as my media. I imagine I need to mount the cdrom and use dpkg --get-selections and dpkg --set-selections and maybe cd to the cdrom stable directory then do some sort of dpkg -R command No, you just need to use the dselect program. but I have no idea how to hang all these steps together. Dselect takes care of most of the detail work. Anybody know how to do this?type/talk slowly so I can see your lips move. First become superuser (root) to be able to make system-level changes; you do this with the command su - and typing in root's password at the prompt. Next, type the dselect command. Now, read slowly what messages dselect shows on screen, or you might get confused at a later stage about the purpose of the questions dselect asks you and what keypresses are at your disposition to instruct dselect. Generally, every time dselect comes up with a screen of informative text, read it thoroughly before hitting the space key. Another valuable piece of knowledge is that pressing the ? key brings you to a help screen, where you can find out about the general purpose and setup of dselect (more or less what I'm typing here) and about specific keybindings. The first time you are going to use your cd, you'll have to set the Access method. If you have installed the system from cd, then it probably isn't necessary set the access method again and you can skip this step. Every time you insert a new cd, you have to Update the available list, so that the dselect engine (called dpkg) knows what packages are available for installation. If you just want to add a package from a cd that you have previously used, then you can safely assume that dpkg still knows what's available and skip this step. Next comes the Select part. This is often the most difficult and confusing part because it requires the most user interaction. You're first shown an informative text. Read it. When you're finished, you arrive at the list of available packages. The list shows a lot of information at once, so don't be confused. If you are not sure about the meaning of symbols, just press ? and read the on-line documentation. Because there are so many available packages (more then you would ever want - or even could - install on your system,) it is the easiest to find a package by its name if you know a part of that. Press / and type a part of the package's name and hit enter. If that gives a result that is not quite right, press \ (yes, I know, this isn't the most intuitive key for the job) to search for the next match until you find what you're looking for. To mark a package for installation, you move the selection bar to the line that lists the package. You can also mark a group of packages by putting the selection bar on the group's header in the list, but I don't advise you to do this until you understand all about the dependency mechanism as explained below. Selecting a lot of packages at once is very likely to cause a bunch of dependency conflicts between packages at once and this is very confusing, even to the initiated. There are a couple of keybindings to mark a package for installation, I always use insert, but that doesn't always work when I login remotely over the net, so you might want to check all the possibilities. Just press the ? key and lookup the keybindings. Assuming you have found the package you want to add to your system, mark it for installation. This will not install it yet, it just tells dselect that you want dpkg to install it in a later phase. One reason to do things this way is to allow the dselect program to check your wishes against package dependencies. Some packages conflict, you can't have them installed at the same time. Others depend, you must have one to install the other. The dpkg engine won't install packages until these dependencies are resolved. This is what dselect is good at, it tries to help you along in resolving the dependencies. When you change a package's status, by marking or unmarking it, dselect will look for dependency issues and if it detects cinflicts, it steps in and presents the (in)famous dependency screen. This is one of the things that has so many people confused, while it is in fact one of the best things since sliced bread. It is (apart from the high standards and strong consistency of the distribution) the big difference between Debian's packaging tools and The Others. What happens when dselect finds a dependency unresolved is that it first shows you an informative message. Read it. Next, you see a sublist of the entire packages list with only those packages that are in some way or another involved in the dependency. Dselect has already suggested a marking for each package involved, but you can still change the suggested markings before you acknowledge the
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
Hello Joost and thanks for the reply. I've been tinkering with dselect and I think I've figured out enough to get it to do what it can for me..as far as that goes. But I'm trying to do a custom install with alots of selected packages for a bastion host/firewall. This would be cumbersome to do by hand on the three machines that would make up the firewall. Also, we are trying to come up with a somewhat automated and well worked out procedure for building a Debian based firewall, see: http://www.weikert.de/debwall/ and debian-firewall@lists.debian.org therefore I believe dselect just will not have the functionality required for this project and that is why I'm looking into dpkg. It looks as if dpkg can probably pull it off.I'm just not sure how to use it in this complex scenario.I've used it for simpler stuff and it works great.installing a kernel dselect couldn't find for instance (2.0.33). so my question remains, what are the steps? ? base install su mount cdrom cd /mnt/stable dpkg --set-selections /tmp/custom_package_list -R ? I've got some new machines coming in this morning so I'll try this out blindly soon, but would appreciate any guidance from the gurus. Thanks Henry Hollenberg [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
On Tue, 3 Mar 1998, Henry Hollenberg wrote: Hello Joost and thanks for the reply. I've been tinkering with dselect and I think I've figured out enough to get it to do what it can for me..as far as that goes. Oh, sorry, I didn't quite get that. But I'm trying to do a custom install with alots of selected packages for a bastion host/firewall. This would be cumbersome to do by hand on the three machines that would make up the firewall. therefore I believe dselect just will not have the functionality required for this project and that is why I'm looking into dpkg. You're probably wrong about that: - theoretically because: dselect builds on dpkg; it provides extra functionality that dpkg doesn't have and calls upon dpkg to do what dpkg can. - practically because: see suggestions below; It looks as if dpkg can probably pull it off.I'm just not sure how to use it in this complex scenario.I've used it for simpler stuff and it works great.installing a kernel dselect couldn't find for instance (2.0.33). Was that a kernel you brewed yourself with kernel-package? Then it probably wasn't mentioned in a Packages file. How would dselect know about your package then? Dselect's standard way of getting to know what packages are available in an archive is to run dpkg --update-avail on the Packages file that comes with the archive. You could have made a Packages file yourself, with dpkg-scanpackages and put that in a DIY archive and use it with dselect (making a custom archive). You'll have to make an override file too, to get dpkg-scanpackages to add sections to the packages entries in the Packages file. You can find examples in the ftp.debian.org /debian/indices/ directory. Or (not using an archive at all) you could have used dpkg --avail custom-kernel.deb. I'm afraid you'd have to put the .deb on a floppy to use it with dselect, because that's the only way it knows how to deal with a non-archive. In this simple case, dpkg -i by hand is more convinient of course. so my question remains, what are the steps? Another solution is to build a package with dependencies on all the packages you want to install. Create an archive that contains that package, the packages it depends on and packages that those depend on. Since you want to build a firewall, you'll probably want to put in a _lot_ of conflicts as well ;-). Use dpkg-scanpackages to generate a Packages file. Burn it on a cd or put it on your ftp site and it should work fine with dselect and deity. If you're really serious about creating your own cd, then dselect is definately the way to go. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
Henry Hollenberg [EMAIL PROTECTED] On Tue, 3 Mar 1998, Joost Kooij wrote: On Tue, 3 Mar 1998, Henry Hollenberg wrote: Hello Joost and thanks for the reply. I've been tinkering with dselect and I think I've figured out enough to get it to do what it can for me..as far as that goes. Oh, sorry, I didn't quite get that. But I'm trying to do a custom install with alots of selected packages for a bastion host/firewall. This would be cumbersome to do by hand on the three machines that would make up the firewall. therefore I believe dselect just will not have the functionality required for this project and that is why I'm looking into dpkg. You're probably wrong about that: - theoretically because: dselect builds on dpkg; it provides extra functionality that dpkg doesn't have and calls upon dpkg to do what dpkg can. - practically because: see suggestions below; It looks as if dpkg can probably pull it off.I'm just not sure how to use it in this complex scenario.I've used it for simpler stuff and it works great.installing a kernel dselect couldn't find for instance (2.0.33). Was that a kernel you brewed yourself with kernel-package? Then it probably wasn't mentioned in a Packages file. How would dselect know about your package then? It's one from Herbert Xu that's not showing up in stable or bo-update: http://cgi.debian.org/www-master/debian.org/Packages/unstable/devel/kernel-source-2.0.33.html not sure why it's in unstable/devel since it looks like a stable (even number) release. once I had the .deb file downloaded I cd'ed to that directory as su and ran dpkg -i ./*.deb and I had my stable sources installed. then I did make menuconfig in the new sources directory tree then I did, make-kpkg kernel-image then edited lilo.conf then cd'ed to /usr/src where the new compiled kernel package .deb file was and ran dpkg -i *.deb and bingo I had a lean mean tuned kernel (also downloaded the latest 3com driver source from Donald Becker and put that in the source tree before compilation, 3c59x.c). Dselect's standard way of getting to know what packages are available in an archive is to run dpkg --update-avail on the Packages file that comes with the archive. You could have made a Packages file yourself, with dpkg-scanpackages and put that in a DIY archive and use it with dselect (making a custom archive). You'll have to make an override file too, to get dpkg-scanpackages to add sections to the packages entries in the Packages file. You can find examples in the ftp.debian.org /debian/indices/ directory. Now we're getting somewhere! I'm going to have to print this one and read and think awhile! Thanks hgh Or (not using an archive at all) you could have used dpkg --avail custom-kernel.deb. I'm afraid you'd have to put the .deb on a floppy to use it with dselect, because that's the only way it knows how to deal with a non-archive. In this simple case, dpkg -i by hand is more convinient of course. so my question remains, what are the steps? Another solution is to build a package with dependencies on all the packages you want to install. Create an archive that contains that package, the packages it depends on and packages that those depend on. Since you want to build a firewall, you'll probably want to put in a _lot_ of conflicts as well ;-). Use dpkg-scanpackages to generate a Packages file. Burn it on a cd or put it on your ftp site and it should work fine with dselect and deity. If you're really serious about creating your own cd, then dselect is definately the way to go. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
On Tue, 3 Mar 1998, Henry Hollenberg wrote: Was that a kernel you brewed yourself with kernel-package? Then it probably wasn't mentioned in a Packages file. How would dselect know about your package then? It's one from Herbert Xu that's not showing up in stable or bo-update: http://cgi.debian.org/www-master/debian.org/Packages/unstable/devel/kernel-source-2.0.33.html not sure why it's in unstable/devel since it looks like a stable (even number) release. Stable and unstable kernel releases have nothing to do with stable and unstable debian distribution trees. The Debian unstable tree always has stable kernels for instance. The stable and unstable debian distribution tree have different Packages files though. Since the kernel included with stable has no major bugs that needed to be fixed, it hasn't been changed in the bo tree and neither in bo's Packages file. Maybe that explains why you didn't see it; you're looking at the Packages file from bo. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
Henry Hollenberg [EMAIL PROTECTED] On Tue, 3 Mar 1998, Joost Kooij wrote: On Tue, 3 Mar 1998, Henry Hollenberg wrote: Was that a kernel you brewed yourself with kernel-package? Then it probably wasn't mentioned in a Packages file. How would dselect know about your package then? It's one from Herbert Xu that's not showing up in stable or bo-update: http://cgi.debian.org/www-master/debian.org/Packages/unstable/devel/kernel-source-2.0.33.html not sure why it's in unstable/devel since it looks like a stable (even number) release. Stable and unstable kernel releases have nothing to do with stable and unstable debian distribution trees. The Debian unstable tree always has stable kernels for instance. The stable and unstable debian distribution tree have different Packages files though. Since the kernel included with stable has no major bugs that needed to be fixed, it hasn't been changed in the bo tree and neither in bo's Packages file. Maybe that explains why you didn't see it; you're looking at the Packages file from bo. What would point dselect at this particular kernel then? (2.0.33) unstable? Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
Henry Hollenberg [EMAIL PROTECTED] On Tue, 3 Mar 1998, Joost Kooij wrote: On Tue, 3 Mar 1998, Henry Hollenberg wrote: Hello Joost and thanks for the reply. I've been tinkering with dselect and I think I've figured out enough to get it to do what it can for me..as far as that goes. Oh, sorry, I didn't quite get that. You could have made a Packages file yourself, with dpkg-scanpackages and put that in a DIY archive and use it with dselect (making a custom archive). You'll have to make an override file too, to get dpkg-scanpackages to add sections to the packages entries in the Packages file. You can find examples in the ftp.debian.org /debian/indices/ directory. Is override.bo.gz the example you refer to? I just downloaded it and will have a look a little later...have to run an errand. thanks hgh -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect (Re: Using dpkg for a custom installation from cdrom media)
On Tue, 3 Mar 1998, Henry Hollenberg wrote: Henry Hollenberg [EMAIL PROTECTED] On Tue, 3 Mar 1998, Joost Kooij wrote: On Tue, 3 Mar 1998, Henry Hollenberg wrote: Was that a kernel you brewed yourself with kernel-package? Then it probably wasn't mentioned in a Packages file. How would dselect know about your package then? It's one from Herbert Xu that's not showing up in stable or bo-update: http://cgi.debian.org/www-master/debian.org/Packages/unstable/devel/kernel-source-2.0.33.html not sure why it's in unstable/devel since it looks like a stable (even number) release. Stable and unstable kernel releases have nothing to do with stable and unstable debian distribution trees. The Debian unstable tree always has stable kernels for instance. The stable and unstable debian distribution tree have different Packages files though. Since the kernel included with stable has no major bugs that needed to be fixed, it hasn't been changed in the bo tree and neither in bo's Packages file. Maybe that explains why you didn't see it; you're looking at the Packages file from bo. What would point dselect at this particular kernel then? (2.0.33) unstable? Yes, but since there's a big difference between current stable and unstable (libc5 vs. libc6) there's slightly more to it than pointing dselect at the unstable tree. Testing is currently being done to make the transition as smooth as possible (another great thing of Debian; other distributions require you to scrap your existing setup and reinstall completely.) You can move to unstable too, but you'll have to read the HOWTO on the subject and follow the advice pretty closely, because it's a big thing to go from one libc major version to another. You'll be better off with a fast net connection too, because almost all packages have newer versions (linked against different libs and a lot of newer versions.) If you're on a 14k4 modem link, better wait a wild guess month or two until the debian 2.0 cd's are in the shops /wild guess. You can find the upgrade-HOWTO at http://taz.net.au/autoup/libc5-libc6-Mini-HOWTO.html Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
