Re: Missing AMD64 3.1_r5 images (Was: Re: 404 errors for install image links)
On Fri, Mar 23, 2007 at 09:59:17PM +0100, Mattias Wadenstein wrote: >On Fri, 23 Mar 2007, Jens Seidel wrote: > >>Hi, >> >>there were recently a few reports about missing 3.1_r5 images for >>amd64. I think it would be a good idea to build these before Etch is >>released. > >Sarge was not released with amd64, and will not be. Etch is the first >official amd64 release. > >There is an inofficial release maintained by the amd64 port team, but >AFAIK, they have not gotten r5 out yet. These are available here: > >http://cdimage.debian.org/cdimage/unofficial/ > >Note that the newest amd64-3.1_* is r4. Hmmm. It seems from the Release file[1] in the amd64 unofficial archive that there *has* been an r5 release of a sort, but the Version: tag in the file still says 3.1r *2*. That'd explain why my own checks have not shown the change. If somebody with appropriate permissions can fix that, I'll try and get some amd64 r5 images built. [1] ftp://amd64.debian.net/debian-amd64/dists/sarge/Release -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Is there anybody out there? signature.asc Description: Digital signature
Re: ping on CD would not take up any additional space
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/24/2007 08:40 AM, Richard Atterer wrote: > On Fri, Mar 23, 2007 at 10:46:14PM -0300, Felipe Augusto van de Wiel (faw) > wrote: >> ping is not exactly the smallest of the programs (~30K), and I >> really trust d-i team judgement, I was just imagining that if it is >> possible to have ping (which means that space and other things are not a >> problem), we should add it for our users. > > There is _no_ reason to exclude ping because of concerns about its size!! > > I have just compiled the udebs both without and with ping. Adding ping > makes the busybox binary larger by 1568 BYTES or 800 BYTES depending on the > udeb: > busybox binary size:with ping: > busybox-floppy-udeb/bin/busybox74404 75972 > busybox-udeb/bin/busybox 201228 202028 > > In the packed udeb, the difference is a whopping 678 bytes or 472 bytes: > > .udeb size: with ping: > busybox-floppy-udeb_1.1.3-4_i386.udeb 45920 46598 > busybox-udeb_1.1.3-4_i386.udeb118896 119368 > > BTW, when the .udeb is put on a CD, the ISO9660 filesystem will always > round up the required space to the next multiple of 2 kBytes. As it > happens, the addition of ping makes no difference at all when this is > considered: > .udeb 2k CD blocks: with ping: > busybox-floppy-udeb_1.1.3-4_i386.udeb 23 23 > busybox-udeb_1.1.3-4_i386.udeb59 59 > > Cheers, > > Richard That's great. Thanks for the nice report. :-) Now, the question would be if it is enough to convince Frans and d-i team to add ping back and if there is anything that we can do to help on this. Kind regards, - -- Felipe Augusto van de Wiel (faw) "Debian. Freedom to code. Code to freedom!" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGByCCCjAO0JDlykYRAuknAJ9iu/wYtoN73BM1LR72a/4MRnpmUACgkY2S LN059AI00K1wIvq7kLKaGR0= =jAlv -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416230: debian-cd: support KERNEL_PARAMS for powerpc, alpha and sparc
Package: debian-cd
Version: 3.0.1
Severity: wishlist
Tags: patch
i make use of the KERNEL_PARAMS variable when creating custom
debian-installer CDs, but after trying to build a powerpc image, noticed
that it is only supported on i386 and amd64... why should other
architectures miss out on the fun?
please consider the attached patch (untested) to add support for
KERNEL_PARAMS to powerpc, alpha and sparc.
not sure how the other arches work to even try...
live well,
vagrant
Index: tools/boot/etch/boot-powerpc
===
--- tools/boot/etch/boot-powerpc (revision 1386)
+++ tools/boot/etch/boot-powerpc (working copy)
@@ -75,6 +75,9 @@
> boot.msg
cat $BASEDIR/data/$DI_CODENAME/yaboot/yaboot.conf \
| sed "s/CODENAME/${CODENAME}/g" > yaboot.conf
+if [ -n "$KERNEL_PARAMS" ]; then
+sed -ie "s|append=\"|append=\"$KERNEL_PARAMS |g" yaboot.conf
+fi
cp $BASEDIR/data/$DI_CODENAME/yaboot/ofboot.b ofboot.b
for subarch in powerpc powerpc64 prep
@@ -123,5 +126,8 @@
cp $BASEDIR/data/$DI_CODENAME/chrp/bootinfo.txt ppc
mkdir etc
cp $INSTALLDIR/yaboot.conf etc
+if [ -n "$KERNEL_PARAMS" ]; then
+sed -ie "s|append=\"|append=\"$KERNEL_PARAMS |g" etc/yaboot.conf
+fi
exit 0
Index: tools/boot/etch/boot-alpha
===
--- tools/boot/etch/boot-alpha (revision 1386)
+++ tools/boot/etch/boot-alpha (working copy)
@@ -80,9 +80,9 @@
RSIZE=$(expr $(zcat boot$N/boot/initrd.gz | wc --bytes) / 1024)
OPTS="ramdisk_size=$RSIZE initrd=/boot/initrd.gz root=/dev/ram devfs=mount,dall"
-echo "0:boot/vmlinuz $OPTS" > boot$N/etc/aboot.conf
-echo "1:boot/vmlinuz $OPTS console=ttyS0" >> boot$N/etc/aboot.conf
-echo "2:boot/vmlinuz $OPTS console=ttyS1" >> boot$N/etc/aboot.conf
+echo "0:boot/vmlinuz $OPTS $KERNEL_PARAMS" > boot$N/etc/aboot.conf
+echo "1:boot/vmlinuz $OPTS console=ttyS0 $KERNEL_PARAMS" >> boot$N/etc/aboot.conf
+echo "2:boot/vmlinuz $OPTS console=ttyS1 $KERNEL_PARAMS" >> boot$N/etc/aboot.conf
mkdir -p boot$N/milo
Index: tools/boot/etch/boot-sparc
===
--- tools/boot/etch/boot-sparc (revision 1386)
+++ tools/boot/etch/boot-sparc (working copy)
@@ -46,6 +46,9 @@
# Some custom etc files
cp -f -p $BASEDIR/data/etch/sparc/silo.conf $inst/boot/
+if [ -n "$KERNEL_PARAMS" ]; then
+sed -ie "s|append=\"|append=\"$KERNEL_PARAMS |g" $inst/boot/silo.conf
+fi
cat $BASEDIR/data/etch/sparc/debian.txt \
| sed "s/\${MEDIA_TYPE}/CDROM/" \
| sed "s/\${DEBIAN_VERSION}/${CODENAME}/g" \
