Hammer Storage N1200 (HN1200) support
According to some research I have done, this NAS runs a Marvel SoC that's Arm9 based. It's already running Linux. According to some other sources, this vendor is under litigation over busybox gplv2 violations. It's not the only unit running on this chipset out there. There appears to be two serial port headers, but I haven't had a chance to look into it deeply yet. http://www.hammer-storage.com/downloads/myshare/myshare_HardwareGuide.pdf http://www.embeddedarm.com/documentation/third-party/MV88F5182-opensource-manual.pdf In a little while I will pull the harddrives and replace it with a test drive that I can experiment with. So far I haven't found anyone able to install anything but what the OEM provided on this. Any suggestions, thoughts or ideas? Thanks, Scott Edwards -- Daxal Communications - http://daxal.com/?from=debian-boot -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [patch] generalize loopback network interface name
On 23/07/2009, Otavio Salvador ota...@ossystems.com.br wrote: Hello, On Wed, Jul 22, 2009 at 7:58 PM, Luca Favatellaslacky...@gmail.com wrote: Loopback network interface name is lo on GNU/Linux and lo0 on GNU/kFreeBSD. This patch generalizes it with a macro. [...] Please go ahead and commit it. Committed to trunk. Thanks, Luca Favatella -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hammer Storage N1200 (HN1200) support
On Thu, Jul 23, 2009 at 12:10:02AM -0600, Scott Edwards wrote: According to some research I have done, this NAS runs a Marvel SoC that's Arm9 based. It's already running Linux. According to some other sources, this vendor is under litigation over busybox gplv2 violations. It's not the only unit running on this chipset out there. There appears to be two serial port headers, but I haven't had a chance to look into it deeply yet. I've got no specific knowledge of this hardware, but the MV88F5182 is what's in my D-Link DNS-323, so there shouldn't be much trouble getting Debian running on this thing (to at least a basic degree). I've pimped this a bunch of times before, so apologies if you've already seen it, but if you're interested in doing a Debian port (specifically d-i) to this hardware, take a look at the guide I wrote about my experiences porting d-i to the DNS-323: http://www.hezmatt.org/~mpalmer/blog/general/porting_d-i_to_the_dns_323.html That might ease the learning curve a bit if you decide to dig into it. All things considered, it wasn't as hard as I was expecting, and it was a great experience. I'd do it again if I needed another NAS. - Matt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Switch to udhcpc in netcfg
Quoting Otavio Salvador (ota...@ossystems.com.br): Hello all, On Sat, Jul 18, 2009 at 6:00 PM, Otavio Salvadorota...@ossystems.com.br wrote: To test the udhcpc usage you can build an installer image with the modified udebs and do, at console: #: rm -rf /var/lib/dhcp3 /sbin/dhclient* To make it easier to test I've pushed the netcfg changes and also uploaded netcfg. Now the only thing you need to do, besides the removal of the above files, is to copy the udhcpc script from SVN repository[1]. 1. http://svn.debian.org/wsvn/d-i/people/waldi/packages/busybox/debian/bin/default.script Did someone rebuild busybox with that script? I tried but failed miserably. Therefore I can't easily test udhcpc. Would someone have an i386 udeb of busybox with that script included. signature.asc Description: Digital signature
zlib 1:1.2.3.3.dfsg-14
Could you pleas unblock zlib 1:1.2.3.3.dfsg-14? It's been in unstable for getting on for a month without incident, the changelog is: zlib (1:1.2.3.3.dfsg-14) unstable; urgency=low * amd64 has finally abandoned /emul/ia32-linux so install the 32 bit binaries in lib32 as for other architectures (closes: #533015). -- Mark Brown broo...@debian.org Thu, 25 Jun 2009 12:49:05 +0100 -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hinting console-setup for testing?
Yesterday, we discussed about requesting a hint to the release team for console-setup 1.44 to enter testing. Anton, would there be objections to this? -- signature.asc Description: Digital signature
Reorganization od D-I localization levels
After a short discussion on -i18n[1], later crossposted to -boot, I finally achieved a reorganization of the Debian Installer localization levels (that appear in statistics pages[2] and spellchecking pages[3]) Please refer to the abovementioned discussion for details, so in short: Levels 1 and 2 remain unchanged Level 4 and 5 disappear Level 3 is only left with debconf (debconf translations), newt and win32-loader It means that all translation statistics for packages that were previously in levels 3 to 5 will not be followed anymore by the D-I framework. It of course *doesn't* mean that localization is abandoned for those packages. There might be a few remaining glitches, which I intend to fix in the next days... The D-I i18n documentation[4] has been adapted accordingly. References: [1] https://lists.debian.org/debian-i18n/2009/05/msg00047.html [2] http://d-i.debian.org/l10n-stats/ [3] http://d-i.debian.org/l10n-spellcheck/ [4] http://d-i.alioth.debian.org/doc/i18n/ -- signature.asc Description: Digital signature
Automatic partition setup in partman-{lvm,md,crypto}
I was showing this to a few people at DebConf and people seemed
generally in favour of the UI changes, so I thought I'd post it for
wider comment here.
The process of setting up complex block devices (LVM, RAID, crypto) in
partman is currently rather tedious. You have to separately edit each
partition you want to use as a physical volume, change its Use as:
field, and then a Configure foo menu item appears that lets you
assemble the physical volumes. This is very cumbersome, and it also has
discoverability problems - if your goal is to set up LVM, you can't even
see the menu item that lets you do that until you're part-way through
the process.
I'd like to introduce an alternative way to do this that's more
goal-oriented: in other words, I'd like people to be able to select
Configure the Logical Volume Manager, select from a menu of all the
partitions that *could* be used as LVM PVs, and have partman-lvm
automatically set them up for them.
The attached set of three patches implements this for each of
partman-lvm, partman-md, and partman-crypto. In the case of
partman-crypto, I had to add a menu, which both brings it into line with
LVM and RAID and will allow adding a way to deconfigure encrypted
volumes in the future (#381892). The partman-md patch is rather
complicated because I had to cope with the way it trims partitions
already selected as active devices when prompting for spare devices; the
code in this patch is the result of several attempts, and most of my
previous attempts had much twistier uses of IFS that I eventually
rejected.
Talking through this with Max Vozeler identified several problems that
I'd still like to fix:
* There are several common chunks of code that should be moved into
partman-base.
* It'd be nice to show more detail in the partition menus, especially
including a status field and the mountpoint. We can't quite reuse the
standard partition tree as this relies on a separate line to identify
the disk device, which doesn't really work here, but we could do
something similar.
* There's some weird bug in handling of locked devices; the LVM menu,
at least, offers the underlying devices of configured encrypted
volumes when it shouldn't.
* Max suggests that we might exclude partitions with mountpoints to
reduce the probability of mistakes. This seems to make sense - d-i
doesn't automatically set up mountpoints, so if a partition has a
mountpoint then it's because the user deliberately gave it one.
If you'd like to try this out, then I guess a reasonable way to do so
would be to play with a current Ubuntu installation image:
http://cdimage.ubuntu.com/releases/karmic/alpha-3/
(alpha release produced today, CD-sized; use the server option)
http://cdimage.ubuntu.com/ubuntu-server/daily/current/
(server daily build, may be arbitrarily broken)
http://cdimage.ubuntu.com/netboot/karmic/
(netboot images, may be arbitrarily broken though usually not too
bad)
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
=== modified file 'choose_method/lvm/choices'
--- choose_method/lvm/choices 2007-12-05 20:18:24 +
+++ choose_method/lvm/choices 2009-07-13 21:40:14 +
@@ -1,45 +1,11 @@
#!/bin/sh
-. /lib/partman/lib/base.sh
+. /lib/partman/lib/lvm-base.sh
dev=$1
id=$2
-cd $dev
-
-lvm=no
-if grep -q /dev/md $dev/device; then
- # LVM on software RAID
- lvm=yes
-elif grep -q /dev/mapper/ $dev/device; then
- # LVM on device-mapper crypto
- if type dmsetup /dev/null 21; then
- device=$(cat $dev/device)
- if [ $(dmsetup status $device | cut -d' ' -f3) = crypt ]; then
- lvm=yes
- fi
- fi
-fi
-
-# sparc can not have LVM starting at 0 or it will destroy the partition table
-if [ $(udpkg --print-architecture) = sparc ] \
- [ ${id%%-*} = 0 ] [ $lvm = no ]; then
-exit 0
-fi
-
-if [ $lvm = no ]; then
- open_dialog VALID_FLAGS $id
- while { read_line flag; [ $flag ]; }; do
- if [ $flag = lvm ]; then
- lvm=yes
- fi
- done
- close_dialog
-fi
-
-if [ $lvm = no ]; then
- exit 0
-fi
+pv_allowed $dev $id || exit 0
db_metaget partman/method_long/lvm description
=== modified file 'choose_partition/lvm/choices'
--- choose_partition/lvm/choices 2007-12-05 20:18:57 +
+++ choose_partition/lvm/choices 2009-07-09 09:42:49 +
@@ -3,8 +3,9 @@
. /usr/share/debconf/confmodule
. /lib/partman/lib/lvm-base.sh
-# Only show menu option if there is at least one LVM PV
-[ $(pv_list | wc -l) -gt 0 ] || exit 0
+# Only show menu option if there is at least one partition that can be used
+# as an LVM PV
+[ $(pv_list_allowed | wc -l) -gt 0 ] || exit 0
db_metaget partman-lvm/text/configure_lvm description
=== modified file 'choose_partition/lvm/do_option'
--- choose_partition/lvm/do_option 2008-07-31 11:29:20 +
+++ choose_partition/lvm/do_option 2009-07-22 13:12:33 +
@@ -43,15 +43,32 @@ do_display() {
}
do_vg_create() {
- local pvs pv output vg
+ local pvs line pv output vg pathmap
pvs=
+
Processing of hw-detect_1.73_i386.changes
hw-detect_1.73_i386.changes uploaded successfully to localhost along with the files: hw-detect_1.73.dsc hw-detect_1.73.tar.gz ethdetect_1.73_all.udeb disk-detect_1.73_all.udeb hw-detect_1.73_i386.udeb archdetect_1.73_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of debootstrap_1.0.15_i386.changes
debootstrap_1.0.15_i386.changes uploaded successfully to localhost along with the files: debootstrap_1.0.15.dsc debootstrap_1.0.15.tar.gz debootstrap_1.0.15_all.deb debootstrap-udeb_1.0.15_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of localechooser_2.13_amd64.changes
localechooser_2.13_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: localechooser_2.13.dsc localechooser_2.13.tar.gz localechooser_2.13_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of localechooser_2.13_amd64.changes
localechooser_2.13_amd64.changes uploaded successfully to localhost along with the files: localechooser_2.13.dsc localechooser_2.13.tar.gz localechooser_2.13_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
hw-detect_1.73_i386.changes ACCEPTED
Accepted: archdetect_1.73_i386.udeb to pool/main/h/hw-detect/archdetect_1.73_i386.udeb disk-detect_1.73_all.udeb to pool/main/h/hw-detect/disk-detect_1.73_all.udeb ethdetect_1.73_all.udeb to pool/main/h/hw-detect/ethdetect_1.73_all.udeb hw-detect_1.73.dsc to pool/main/h/hw-detect/hw-detect_1.73.dsc hw-detect_1.73.tar.gz to pool/main/h/hw-detect/hw-detect_1.73.tar.gz hw-detect_1.73_i386.udeb to pool/main/h/hw-detect/hw-detect_1.73_i386.udeb Override entries for your package: archdetect_1.73_i386.udeb - standard debian-installer disk-detect_1.73_all.udeb - optional debian-installer ethdetect_1.73_all.udeb - optional debian-installer hw-detect_1.73.dsc - source debian-installer hw-detect_1.73_i386.udeb - standard debian-installer Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
debootstrap_1.0.15_i386.changes ACCEPTED
Accepted: debootstrap-udeb_1.0.15_all.udeb to pool/main/d/debootstrap/debootstrap-udeb_1.0.15_all.udeb debootstrap_1.0.15.dsc to pool/main/d/debootstrap/debootstrap_1.0.15.dsc debootstrap_1.0.15.tar.gz to pool/main/d/debootstrap/debootstrap_1.0.15.tar.gz debootstrap_1.0.15_all.deb to pool/main/d/debootstrap/debootstrap_1.0.15_all.deb Override entries for your package: debootstrap-udeb_1.0.15_all.udeb - extra debian-installer debootstrap_1.0.15.dsc - source admin debootstrap_1.0.15_all.deb - extra admin Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
localechooser_2.13_amd64.changes ACCEPTED
Accepted: localechooser_2.13.dsc to pool/main/l/localechooser/localechooser_2.13.dsc localechooser_2.13.tar.gz to pool/main/l/localechooser/localechooser_2.13.tar.gz localechooser_2.13_all.udeb to pool/main/l/localechooser/localechooser_2.13_all.udeb Override entries for your package: localechooser_2.13.dsc - source debian-installer localechooser_2.13_all.udeb - optional debian-installer Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538171: ITP: makefs -- create a file system image from a directory tree
Package: wnpp Severity: wishlist Owner: Thorsten Glaser t...@mirbsd.de * Package name: makefs Version : 20090724 Upstream Author : The MirOS Project miros-disc...@mirbsd.org * URL : http://www.mirbsd.org/cvs.cgi/src/usr.sbin/makefs/ * License : 4-clause BSD Programming Lang: C Description : create a file system image from a directory tree NetBSD® makefs(8) creates a file system image from a directory tree without the need for superuser privileges. The MirBSD version fixes ECMA 119, SUSP and RRIP (Rock Ridge) compliance. Supported target filesystem types are: cd9660 ISO 9660 (ECMA 119) compatible filesystem images, with Rock Ridge, El Torito, and other features ffs 4.2FFS, the BSD Fast Filesystem, also known as UFS1; support for UFS2 is currently untested The images created can be of a fixed (predefined) size, given on the command line, or sized automatically. Permission bits are taken from the source directory tree but may be overridden using an mtree file. This package is created to aid Luca Favatella in porting d-i to Debian GNU/kFreeBSD. It also serves purpose as a genisoimage re- placement, if people should then so wish. (Which is why the MirBSD version was ported, as it conforms to ECMA 119, RRIP, SUSP and the El Torito standard, which the NetBSD® version doesn’t.) I fully intend to maintain this package in MirBSD (“upstream”) as well as Debian (in my capacity as DM); I also try to coordinate pushing all patches to the “up-upstream” (NetBSD®). -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please build Debian uploads from a Debian system
At least I assume that's where the cause of the problem is here... debian-installer-utils (1.71) unstable; urgency=low [ Luca Favatella ] * Add 'cons25' terminfo file (used by kfreebsd-i386). * Make di-utils-terminfo Architecture: any to avoid size increase. -- Colin Watson cjwat...@debian.org Sat, 18 Jul 2009 20:58:07 +0200 http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log: The following packages have unmet dependencies: di-utils: Depends: libc6-udeb (= 2.10) but 2.9-21 is to be installed $ rmadison libc6 -s unstable libc6 | 2.9-19 | unstable | armel libc6 | 2.9-20 | unstable | hppa, sparc libc6 | 2.9-21 | unstable | amd64, i386, mips, mipsel, powerpc, s390 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Hinting console-setup for testing?
On Thu, Jul 23, 2009 at 12:18:16PM +0200, Christian Perrier wrote: Yesterday, we discussed about requesting a hint to the release team for console-setup 1.44 to enter testing. Anton, would there be objections to this? None from me. But no matter how we feel about it, #532842 means that 1.44 is breaking the law and this is realy not good. One solution I am thinking is to put some information in debian/copyright. Also one needs to check whether the following line # This file is distributed under the same license as debian-installer is compatible with what it was before (what does license of d-i mean?): # This file is distributed under the same license as the console-setup package. Also the lines # Copyright (C) 2003 Software in the Public Interest, Inc. are completely wrong - not only for the translations coming from console-setup, but also for the translations from d-i, unless the translators have sent to SPI a copyright transfer document. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Daily builds status
Here's an overview of how well/badly our various arches have been building. It is based on the same data as used in the daily builds overview. The table starts March this year and shows only _changes_ in build status; an arch with an X did not build at all from the date on that line until the date on the next line. It does not show partial build failures, nor outdated builds. Conclusions: - s390 has not been built at all since March - ia64 was failing for over 2 months but is now OK - alpha has been failing for over a month now - other arches have had occasional failures, but are mostly OK - (mips and mipsel are currently both several weeks outdated) For s390 it looks like a new host for daily builds needs to be found. Could someone (Luk?) please do that? Cheers, FJP datealpha amd64 armel hppa i386 ia64 mips mpsel ppc s390 sparc 03/01/2009 X X X 03/04/2009 X X X 04/07/2009X X 04/14/2009 X X X 04/15/2009X X 04/16/2009X X X 04/17/2009X X X X X X 04/18/2009X X X 04/20/2009 X 04/21/2009 X X 04/23/2009 X X 04/24/2009X X 04/25/2009 X 04/28/2009 X X 04/30/2009 05/01/2009 X 05/08/2009 X X 05/10/2009 X 05/18/2009X X 05/19/2009 X X X X 05/20/2009X X X X X X 05/22/2009X X X X 05/26/2009 X X X 05/31/2009 X X 06/04/2009 X X X 06/09/2009 X X 06/11/2009 X 06/12/2009 X X 06/13/2009 X X X X 06/15/2009 X X X 06/16/2009 X X X X 06/17/2009X X X X X X 06/19/2009X X X X X 06/25/2009X X X X X X 06/26/2009X X X X X 06/28/2009X X X X 07/02/2009X X X 07/03/2009X X X X 07/04/2009X X X 07/20/2009X X X X 07/21/2009X X X X 07/22/2009X X X 07/23/2009X X X -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
D-I build stats
Hi Joey, I've been playing with the build stats a bit and realized that the graphs with the stats are no longer correct for the full history. Cause is that there have been changes in the arches listed which have been made without noting the warning about that in the script, which means arches have shifted columns. I'm to blame for that myself as early this year I first disabled m68k (11 Jan; commented out) and later dropped arm (15 Feb). Early last year (11/12 Jan) you yourself added armel, but possibly you fixed the stats file for that? Anyway, I'd suggest archiving the current stats file and keeping only the stats starting from March this year. The following commands should do that (the tmp file is in case your cron runs in the middle): cp build-logs.stats build-logs.stats.sv sed -nr /^0[3-9]\/[0-9]+\/2009/ p build-logs.stats.sv bl.stats.tmp mv bl.stats.tmp build-logs.stats Another option would be of course to repair the stats file, but I doubt that's worth the effort. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[PATCH] Basic Openmoko GTA02 support
Hi there!
DebCamp9 hacking produced these patches which add a basic support for
building netboot images for the Openmoko GTA02 Neo FreeRunner.
General notes
=
- You need the Debian unofficial kernel from the pkg-fso repository at
deb http://pkg-fso.alioth.debian.org/debian sid main
Some drivers the official Debian kernels compile as modules are
compiled in in the Openmoko kernel instead, thus I am working on
syncing the latter with the former.
- The d-i files generated in build/dest/openmoko-gta02/netboot/gta02 are
the following:
* rootfs.tar -- root archive for Openmoko GTA02 Neo FreeRunner
This must be decompressed on the microSD. Since there are too many
way to partition the microSD and/or booting, ATM you need to
manually prepare it.
I have not checked the latest GTA02, but in the old ones U-Boot
supported booting from an ext2 microSD card with partition 1 as vfat
for /boot. In this case, partition the microSD (8MB vfat + ext2),
decompress root.tar into the ext2 and then copy /boot/uImage$ETC in
/boot/. Since U-Boot usually expects an image named uImage.bin,
creates the symlink.
* rootfs.jffs2 -- root jffs2 image for Openmoko GTA02 Neo FreeRunner
This must be flashed to mtd6, but it does not work as expected ATM:
$ dfu-util -d 0x1d50:0x5119 -a rootfs -R -D uImage.bin
* uImage.bin -- U-Boot image for Openmoko GTA02 Neo FreeRunner
Nothing more than the U-Boot image shipped by the Debian Openmoko
kernel, again to be flashed to mtd3:
$ dfu-util -d 0x1d50:0x5119 -a kernel -R -D uImage.bin
* flash-debian -- Script to flash debian-installer
This does not work ATM, but the idea is quite simple: the basic
command should prepare the microSD card (partition and everything
needed to decompress rootfs.tar on it) and then have an option to
flash the mtds.
Comments
[PATCH 1/3] kernel-wedge: add support for U-Boot uImage.bin
The Debian Linux kernel for the Openmoko GTA02 Neo FreeRunner does not
provide a vmlinuz image, but instead it ships a U-Boot one, thus
kernel-wedge/commands/install-files needs to look for uImage.bin also.
[PATCH 2/3] linux-kernel-di-armel-2.6: add openmoko-gta02 kernel
The Debian Linux kernel for the Openmoko GTA02 Neo FreeRunner is not
yet official and thus it does not follow the Debian official kernel
naming (I know this is ugly, sorry).
NB, there are still some problems with the various modules, which will
be soon corrected. Moreover, hunting down which module are useful and
which not is another thing to do.
[PATCH 3/3] installer: add openmoko-gta02 netboot image
This adds add the basic infrastructure to produce a netboot image.
While cleaning the patch I seems to be unable to produce a correct
netboot image (package ai-choosers not found). I am quite sure that
just after dinner Gaudenz succeded with the same patch (or a very
similar one, just minor modifications). Thus I think it is worth
submitting it now.
I do not think these stuff are at a point for inclusion, but maybe it
would be better for other (hint: Gaudenz) that works on them.
Thx, bye,
Gismo / Luca
diff -Naur debian-installer-trunk.ORG/packages/kernel/kernel-wedge/commands/install-files debian-installer-trunk/packages/kernel/kernel-wedge/commands/install-files
--- debian-installer-trunk.ORG/packages/kernel/kernel-wedge/commands/install-files 2009-07-23 23:11:37.0 +0200
+++ debian-installer-trunk/packages/kernel/kernel-wedge/commands/install-files 2009-07-23 22:48:19.0 +0200
@@ -63,6 +63,11 @@
$sourcedir/boot/vmlinuz-$installedname,
debian/kernel-image-$kernelversion-$flavour-di/boot/vmlinuz$extraname);
}
+ elsif (-e $sourcedir/boot/uImage.bin-$installedname) {
+ doit(install, -D, -m, 644,
+ $sourcedir/boot/uImage.bin-$installedname,
+ debian/kernel-image-$kernelversion-$flavour-di/boot/uImage.bin$extraname);
+ }
elsif (-e $sourcedir/boot/kfreebsd-$installedname.gz) {
doit(install, -D, -m, 644,
$sourcedir/boot/kfreebsd-$installedname.gz,
diff -Naur debian-installer-trunk.ORG/packages/kernel/kernel-wedge/debian/changelog debian-installer-trunk/packages/kernel/kernel-wedge/debian/changelog
--- debian-installer-trunk.ORG/packages/kernel/kernel-wedge/debian/changelog 2009-07-23 18:53:08.0 +0200
+++ debian-installer-trunk/packages/kernel/kernel-wedge/debian/changelog 2009-07-24 04:45:54.0 +0200
@@ -1,3 +1,9 @@
+kernel-wedge (2.59~openmoko.gta02.1) UNRELEASED; urgency=low
+
+ * Add support for U-Boot uImage.bin.
+
+ --
+
kernel-wedge (2.59) unstable; urgency=low
[ Samuel Thibault ]
diff -Naur debian-installer-trunk.ORG/packages/kernel/linux-kernel-di-armel-2.6/debian/changelog debian-installer-trunk/packages/kernel/linux-kernel-di-armel-2.6/debian/changelog
--- debian-installer-trunk.ORG/packages/kernel/linux-kernel-di-armel-2.6/debian/changelog 2009-07-23 18:53:07.0 +0200
+++
