Re: info about debian DVD update
[ Note CC: and Reply-To: to debian-cd, the best place for this type of question. ] On Thu, Jun 04, 2009 at 03:00:52PM +0200, F. Carpico wrote: > Hello, > > Some times ago I've downloaded the 3 DVDs of Debian 4.0r0. > > Now that Debian 5 is here, I've seen that there is a DVD called update > "debian-update-5.0.1-i386-DVD-1.iso" here : > ftp://ftp.proxad.net/mirrors/cdimage.debian.org/debian-cd/5.0.1/i386/iso-dvd/ > > I'd like to know if this DVD can update Debian 4.0r0 to Debian 5.0.1 > instead of downloading the 5 DVDs of Debian 5.0.1. Nope, the update CDs only cover ugrades within one stable release. The 5.0.1 updates just contain the differences between 5.0.0 and 5.0.1. If you want to update from 4.0rX to 5.0.X then you'll need much more than that. See http://www.debian.org/CD/faq/#update-cd for more details. -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Which kernels to include on ISOs? (Was: Re: Netboot Xen images for amd64)
On Thu, 2009-06-04 at 10:42 +0200, Frans Pop wrote: > On Thursday 04 June 2009, Frans Pop wrote: > > There are three things you need to accomplish: > > 1) include the kernel udebs for 686-bigmem on the image > > 2) include the 686-bigmem kernel-image deb (+ maybe headers packages?) > > 3) support it in build scripts on farbror (d-cd buildd) and possibly > >the easybuild script (recommended for testing!) > > Ah, and you need to actually include the correct D-I initrd and kernel on > the CD of course. Thank you for the pointers and advice, I think I've got enough info to make a start. > And you'll need to modify the syslinux boot menu so > that an "install Xen" option gets added. Xen doesn't boot via syslinux so I don't think that will be necessary. I was thinking I would expand the existing xm-debian.cfg (currently included in the netboot-xen d-i output) to include the configurability to boot from a CD device too. Thanks again! Ian -- Ian Campbell Current Noise: My Dying Bride - A Doomed Lover Your love life will be... interesting. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
i386 and amd64 iso images missing
Hi, The iso and jigdo images for debian testing weekly i386 and amd64 are missing since the 1 June. All the other images seem to be in place. Thanks, Robert Key robert...@mighty.co.za -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Which kernels to include on ISOs? (Was: Re: Netboot Xen images for amd64)
On Thursday 04 June 2009, Frans Pop wrote: > There are three things you need to accomplish: > 1) include the kernel udebs for 686-bigmem on the image > 2) include the 686-bigmem kernel-image deb (+ maybe headers packages?) > 3) support it in build scripts on farbror (d-cd buildd) and possibly >the easybuild script (recommended for testing!) Ah, and you need to actually include the correct D-I initrd and kernel on the CD of course. And you'll need to modify the syslinux boot menu so that an "install Xen" option gets added. Both of those mean changes in the boot-x86 and x86-desktop.sh scripts in tools/boot/sqeeze/ [1]. A regular install should remain the default of course. Cheers, FJP [1] I committed some fairly heavy changes in both D-I and d-cd early this week for that. You may want to look at both the old and new version as the old version shows how you could manipulate the syslinux config to add the options in d-cd. I don't think the base syslinux config in d-i should need to be changed for this. -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Which kernels to include on ISOs? (Was: Re: Netboot Xen images for amd64)
On Thursday 04 June 2009, Ian Campbell wrote: > On Thu, 2009-06-04 at 01:10 +0200, Frans Pop wrote: > > [...snipped a bunch of good points which I won't contest...] :-) > > But there is one image that might exactly fit the bill: the > > i386/amd64/ppc multi-arch netinst CD. Current size (Lenny): 488MB. > > For that it does not matter if it would grow a bit, and it's targeted > > exactly at your users: (semi-)professional sysadmins. > > That sounds ideal, thanks for the suggestion. Am I right in thinking > that a netinst CD includes the base system but not any of the other > stuff? (as opposed to just including the installer itself) Correct. But if you implement it correctly, building a "Xen businesscard image" (multi-arch or not) should automatically be supported too. > > Only problem is that implementing adding Xen to just that image will > > require a fair few changes in debian-cd. In configuration, but I > > think also in code (you'll need to introduce a concept of variants > > within arches for D-I tasks). It'll not be trivial to implement that > > cleanly, though it should certainly be possible. > Do you have any specific guidance regarding the direction you'd like to > see me take with this or shall I just dive in and see what I come up > with? Initially from the debian-cd end I'm thinking along the lines of > adding "-DMULTIARCH=1" (where appropriate) to the preprocessor when > generating the package lists. That sounds wrong. The condition is not "am I building multiarch?". It should be "please build a multi-arch image, but add Xen variations". I.e, building a "normal" m-a image should still be possible and should be default. The challenge is to find a way to specify that _optionally_ the bits needed for Xen should be added on top of the normal image. There are three things you need to accomplish: 1) include the kernel udebs for 686-bigmem on the image 2) include the 686-bigmem kernel-image deb (+ maybe headers packages?) 3) support it in build scripts on farbror (d-cd buildd) and possibly the easybuild script (recommended for testing!) For 1) you need to somehow ensure the 686-bigmem udebs do *not get excluded* for only (!) the m-a netinst CD (see tools/generate_di_list and data/squeeze/exclude-udebs-i386), but not for other images. Similar challenge for 2). Kernel packages get included through the script ools/generate_di+k_list, which currently does not allow for variations within an architecture. Ignore the tasks directory: that is only used for full CD and DVD images, not for netinst and businesscard. For 3) you can find the current build scripts used on farbror at [1]. The "please add Xen support" option should be set in the cronjob.daily script in the bit starting with: for arch in $ARCHES; do echo "Building $arch:" if [ "$arch" = "multi-arch" ] ; then echo " i386/amd64/ppc sid netinst" [...] echo " i386/amd64/ppc squeeze netinst" IMO it should be something like adding 'VARIANT=xen', which should automatically only result in changes for arches that support the variant (the m-a CD also includes powerpc, which does not support Xen, and thus should build without any differences with or without the VARIANT option passed). Bonus points if it can be implemented in such a way that 'VARIANT=foo,bar,baz' would be supported too (but that might be tricky with the exclude-udeb files; maybe those need a different implementation anyway?). Such a variant option could be included in the default CONF.sh (commented out by default) and could also be added in the easybuild.sh script (either commented out by default or activated with a new parameter). All the above is subject to comments from Steve McIntyre. Please check your planned solution with him (by mailing d-cd list). Cheers, FJP [1] http://svn.debian.org/wsvn/debian-cd/setup/#_setup_ -- To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Which kernels to include on ISOs? (Was: Re: Netboot Xen images for amd64)
On Thu, 2009-06-04 at 01:10 +0200, Frans Pop wrote: [...snipped a bunch of good points which I won't contest...] > Personally I would say that full CD and DVD are not even very interesting > for Xen installs: their content is desktop oriented, so why download a > lot of shite you're not going to be using anyway? > Netinst and businesscard are much more relevant, but as explained earlier > those have space restrictions. > > But there is one image that might exactly fit the bill: the i386/amd64/ppc > multi-arch netinst CD. Current size (Lenny): 488MB. For that it does not > matter if it would grow a bit, and it's targeted exactly at your users: > (semi-)professional sysadmins. That sounds ideal, thanks for the suggestion. Am I right in thinking that a netinst CD includes the base system but not any of the other stuff? (as opposed to just including the installer itself) > Only problem is that implementing adding Xen to just that image will > require a fair few changes in debian-cd. In configuration, but I think > also in code (you'll need to introduce a concept of variants within > arches for D-I tasks). It'll not be trivial to implement that cleanly, > though it should certainly be possible. > I'm afraid that I have no real affinity with Xen (the current discussion > on lkml rather amuses me TBH), so I don't think I'd work on that [2]. That's fine I'm willing to have a stab at it, I've been exploring the debian-cd code already since I thought I might have to go a-hacking and I've done some (small) d-i stuff in the past. Do you have any specific guidance regarding the direction you'd like to see me take with this or shall I just dive in and see what I come up with? Initially from the debian-cd end I'm thinking along the lines of adding "-DMULTIARCH=1" (where appropriate) to the preprocessor when generating the package lists. Thanks, Ian. -- Ian Campbell Remember, in 2039, MOUSSE & PASTA will be available ONLY by prescription!! signature.asc Description: This is a digitally signed message part
