Bug#398302: klibc-utils: uswsusp image not recognized
On Thu, Dec 14, 2006 at 09:37:39AM +0100, David H?rdeman wrote: Vagrant Cascadian wrote: i'm not sure this bug is really fixed, or fixed completely... ... APT policy: (500, 'testing') The fixed version is not in testing yet. and i am not using the version of klibc-utils from testing, as noted in my follow-up report. again, the versions of software i am using: ii initramfs-tools 0.85ctools for generating an initramfs ii klibc-utils 1.4.30-2 small statically-linked utilities built with klibc ii libklibc 1.4.30-2 minimal libc subset for use with initramfs ii uswsusp 0.3~cvs20060928-4tools to use userspace software suspend provided by Linux i installed the klibc-utils version 1.4.30-2 from unstable and rebuilt my initramfs images before following up to this bug report. in the changelog entries for klibc-utils 1.4.30-2, it mentioned that this bug is fixed. i do not believe it is fixed for uswsusp images with version 1.4.30-2 of klibc-utils, because when i hacked the initramfs-tools scripts to ignore the output of the fstype command from klibc-utils (version 1.4.30-2), it sucessfully resumes without trouble. if you need more information, please ask, and i will do my best to accomodate (particularly pertaining to what version of klibc-utils i was using), please don't hesitate to ask. :) live well, vagrant p.s. maybe i got a little carried away with reporting which version, in my attempts to be clear, it started being humourous to me. hopefully it does not come across wrongly. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398302: klibc-utils: uswsusp image not recognized
On Thu, Dec 14, 2006 at 11:06:03PM +0100, David H?rdeman wrote: On Thu, Dec 14, 2006 at 12:13:05PM -0800, [EMAIL PROTECTED] wrote: i do not believe it is fixed for uswsusp images with version 1.4.30-2 of klibc-utils, because when i hacked the initramfs-tools scripts to ignore the output of the fstype command from klibc-utils (version 1.4.30-2), it sucessfully resumes without trouble. Ok, that's a bug then :) What output do you get from fstype in the initramfs image? That is, what output does fstype /dev/resume_partition give? the output is: unknown live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402091: [Pbuilder-maint] Bug#402091: pbuilder-uml: create fails when installing linux-kernel-headers
On Fri, Dec 08, 2006 at 10:25:35AM +0100, Mattia Dongili wrote: On Thu, Dec 07, 2006 at 03:30:49PM -0800, Vagrant Cascadian wrote: i can't, for the life of me, get pbuilder-user-mode-linux create to work. it gets as far as installing the bae system with rootstrap, but then when it goes to apt-get packages, it always fails on linux-kernel-headers: One thing to try immediatly anyway would be to increase the mem= parameter in /etc/rootstrap/rootstrap.conf ok, will try that. Otherwise can you get rootstrap alone to create a useable filesystem image? yes, calling rootstrap manually works fine- though i haven't booted to that image and then tried to install additional packages. i'll experiment a little more... live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400506: podebconf-report-po: option to use mail client instead of smtp server
On Mon, Nov 27, 2006 at 12:14:43AM +0100, Nicolas Fran?ois wrote: On Sun, Nov 26, 2006 at 11:48:06AM -0800, [EMAIL PROTECTED] wrote: it would be nice if there were a way to configure podebconf-report-po to use a mail client (such as mutt) instead of sending directly to an smtp server, much like reportbug's --mua and --mutt options. I agree with you. That would be a useful feature. It is not implemented yet because I could not make my mind on how podebconf-report-po should behave in that case. yes, it's a little tricky. podebconf-report-po sends a lot of mails (one to each translator). Do you think --mutt should start mutt once per translator? that would probably be fine when there are not many translations. but would certainly be painful with lots of translations. though, arguably still simpler than manually writing all those emails... Do you think podebconf-report-po should propose a common message for every translators (? la --call) and BCC the mail to all the translators? and this would probably be a good option with lots of translators. would it be feasible to support both methods? maybe with a --mutt/--mua and --mutt-bulk/--mua-bulk option? thanks for giving this some thought. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395004: lsb-release: please review for release exception
i am wondering if this bug should be considered RC, as it makes lsb_release unable to report that is is running etch: lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 4.0 (n/a) Release:4.0 Codename: n/a this bug is present in the version of lsb-release in etch (3.1-15) and though it is fixed in unstable, lsb is frozen, and may require a release exception to propegate to etch. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387808: initramfs-tools: scripts/nfs doesn't properly handle when server-ip is included in root-path
Package: initramfs-tools Followup-For: Bug #387808 found 387808 0.84 thanks seems like this bug is still present in more recent versions of initramfs-tools. :( an ltsp user recently encountered it in bug #395145 i've also confirmed that it's still broken in 0.84 of initramfs-tools. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385226: initramfs-tools: no need to set SERVER_IP in scripts/nfs
On Wed, Aug 30, 2006 at 08:36:58AM +0200, maximilian attems wrote:
On Tue, Aug 29, 2006 at 03:32:50PM -0700, Vagrant Cascadian wrote:
i believe ipconfig defines ROOTSERVER when it is passed via the ip=
parameter, and thus it's not necessary to re-implement this code with
SERVER_IP in initramfs-tools/scripts/nfs
thanks for your check!
need to see why it doesn't do it for NEW_DEVICE?
well, the NEW_DEVICE code i wrote was merely a way so that when it hits:
. /tmp/net-${DEVICE}.conf
it's actually sourcing the right file... though maybe we could just do
something like:
. /tmp/net-*.conf
some risk of getting some other device that way, even though *usually*
there will only be one...
alternately, maybe we could get ipconfig to write to a different
filename that doesn't include the device in it?
attached is a patch which removes this extra code.
i'll double check and will merge - reduces complexity.
not only complexity, but using shell parameter expansion instead of cut
is definitely prone to error, too. so we should avoid it when possible
:)
also available from:
http://llama.freegeek.org/~vagrant/bzr-archives/initramfs-tools/vagrant-initramfs-tools
live well,
vagrant
very appreciated.
i assume that the current retry thing is working for you?
yes, it works quite well, although i still think it needs a call to
sleep to slow down the retry attempts(especially when not using dhcp
to configure).
overall, the nfsroot support is looking pretty good now.
live well,
vagrant
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383730: initramfs-tools: incompatible with udev 0.097-1
On Sat, Aug 19, 2006 at 10:11:10AM +0200, maximilian attems wrote: hello vagrant, thanks for feedback. of course :) On Fri, Aug 18, 2006 at 05:33:05PM -0700, Vagrant Cascadian wrote: well, happy to try out the shiny new ltsp packages, it seems like there may be an incompatibility with initramfs-tools and the new udev: Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/fan.ko): No such device FATAL: Error inserting thermal (/lib/modules/2.6.17-2-486/kernel/drivers/acpi/thermal.ko): No such device this is usual in qemu as it has no acpi support. oh, i've been ignoring that one for so long i didn't even see it :) udevd[769]: lookup_group: error resolving group 'disk': No such file or directory udevd[769]: lookup_group: error resolving group 'floppy': Illegal seek udevd[769]: lookup_group: error resolving group 'cdrom': Illegal seek udevd[769]: lookup_group: error resolving group 'tape': Illegal seek those are harmless. ok... with many more similar lines. i tested it with udev 0.093-1 from etch, and that seemed to work just fine. thanks for all your work on initramfs-tools! :) you may want to look at 383555, fixed klibc is on mentors. i didn't find the klibc packages(just sources), but switching the nuke command with rm -rf seemed to work for me, as suggested in the bug report. oh, you might want to know i booted using: qemu -hda /dev/zero -m 100 -kernel /opt/ltsp/i386/boot/vmlinuz -initrd \ /opt/ltsp/i386/boot/initrd.img \ -nographic \ -append 'nfsroot=10.0.2.2:/opt/ltsp/i386 root=/dev/nfs ip=dhcp console=ttyS0,38400' hehe, that looks like a patched initramfs-tools? :) no, it selects BOOT=nfs using a conf.d snippet for ltsp, but the extra root/ip options don't seem to break anything. the console option works fine, too. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380649: initramfs-tools: new new patch for nfsroot= handling
sorry, i failed to test one of the cases, this patch should fix it.
really.
still need to implement the ip= options... will work on that another
day.
live well,
vagrant
--- scripts/nfs 2006-08-19 12:36:07.0 -0400
+++ ../vagrant-initramfs-tools/scripts/nfs 2006-08-19 12:33:53.0
-0400
@@ -17,6 +17,17 @@
. /tmp/net-${DEVICE}.conf
if [ x${NFSROOT} = xauto ]; then
NFSROOT=${ROOTSERVER}:${ROOTPATH}
+ elif [ x${NFSROOT} != x ]; then
+ # support nfsroot option from linux sources
Documentation/nfsroot.txt:
+ # nfsroot=[server-ip:]root-dir[,nfs-options]
+ if [ x${NFSOPTS} = x ] [ ${NFSROOT#*,} != ${NFSROOT}
] ; then
+ NFSOPTS=-o ${NFSROOT#*,}
+ fi
+ NFSROOT=${NFSROOT%%,*}
+ if [ ${NFSROOT#*:} = $NFSROOT ]; then
+ # get rootserver from dhcp
+ NFSROOT=${ROOTSERVER}:${NFSROOT}
+ fi
fi
if [ x${NFSOPTS} = x ]; then
Bug#380686: initramfs-tools: busybox mount doesn't support nfs
On Tue, Aug 01, 2006 at 07:35:25PM +0200, maximilian attems wrote: On Tue, Aug 01, 2006 at 09:57:02AM -0700, [EMAIL PROTECTED] wrote: well, my ugly workaround was to add a hook that installs /bin/mount to /mount, and hack /usr/share/ltsp/scripts/nfs to use /mount directly. not at all ideal, but it seems to work. sure initramfs-tools is flexible. indeed. i really like it, overall. i'm in exam time atm so quite busy, i thought this busybox mount would make you happy for now. very unhappy that the opposite is true. oh well... so current direction is - improve nfsmount in klibc # find out what is missing or buggy i just tried initramfs-tools 0.69b from etch, and nfsmount appears to work fine for ltsp. we had enabled a workaround to use mount instead for the ltsp packages, but that appears to be unnecessary with recent klibc nfsmount. and, from my breif and initial tests, it seems the nfsmount in sid is also working, so maybe switching scripts/nfs to use nfsmount, as long as you're planning on keeping nfsmount around... (and making it a variable, so easier to enable a workaround... there's a patch for this in my bzr branch mentioned below) maybe also/alternately getting NFS support for busybox mount is also an option, if we can nudge the busybox maintainers? (#348664: busybox: consider CONFIG_NFSMOUNT). all that said, i must say, i'm partial to regular old mount :) hoped to do it today but studies hold me up. patches in aboves directions will be merged, my initramfs-tools bzr branch: http://llama.freegeek.org/~vagrant/bzr-archives/initramfs-tools/vagrant-initramfs-tools currently should contain a patch to make the NFS mount command a variable, and defaulting to nfsmount, as well as (incomplete but useable) patches for #380649. soon to be more :) also you can help me if you publish your qemu args, which usually contains the bootargs. the full qemu (0.8.1-1) commandline i use is this: qemu -hda /dev/zero -m 80 -kernel /opt/ltsp/i386/boot/vmlinuz \ -initrd /opt/ltsp/i386/boot/initrd.img \ -append nfsroot=10.0.2.2:/opt/ltsp/i386 root=/dev/nfs ip=dhcp console=ttyS0,38400 \ -nographic i've also tried without the console=ttyS0,38400 and -nographic parts. /opt/ltsp/i386 is populated using ltsp-server from current development branches. so that i can better take care of nfsrootstuff. thanks! this is definitely holding up initramfs-tools to testing, as there we use nfsmount from klibc solution, which works for some setups. right... well, nfsmount seems to be working now, and making it configurable will greatly simplify workarounds in the future(hopefully not needed)... live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380686: initramfs-tools: busybox mount doesn't support nfs
On Mon, Jul 31, 2006 at 02:03:09PM -0700, Vagrant Cascadian wrote: when setting BOOT=nfs and trying to boot, the nfs mount fails, because busybox mount does not support nfs mounting (debian bug #348664: busybox: consider CONFIG_NFSMOUNT) ...snip... is there any way around this (to get regular mount installed in the initramfs)? well, my ugly workaround was to add a hook that installs /bin/mount to /mount, and hack /usr/share/ltsp/scripts/nfs to use /mount directly. not at all ideal, but it seems to work. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380238: installation-reports: IBM Thinkpad 240
Package: installation-reports Version: daily build 20060721 Severity: normal -- Package-specific info: Boot method: hd-media Image version: 20060721 http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso http://people.debian.org/~fjp/d-i/images/daily/hd-media/2.6/vmlinuz http://people.debian.org/~fjp/d-i/images/daily/hd-media/2.6/initrd.gz Date: 20060722 Machine: IBM thinkpad 240 Partitions: Disk /dev/hda: 30.0 GB, 30005821440 bytes 255 heads, 63 sectors/track, 3648 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 24 192748+ 83 Linux /dev/hda2 25 85 489982+ 83 Linux /dev/hda3 86 207 979965 83 Linux /dev/hda4 208364827639832+ 8e Linux LVM FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/crypt0 ext3 1918363 1398725417290 78% / tmpfstmpfs 96088 0 96088 0% /dev/shm /dev/hda2 ext3 459174 15373419302 4% /boot tmpfstmpfs 1024084 10156 1% /dev (/dev/mapper/crypt0 is on an lvm volume) lvs vg0/oscuro vg0/swap LV VG Attr LSize Origin Snap% Move Log Copy% oscuro vg0 -wi-ao 1.95G swap vg0 -wi-a- 500.00M Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [E] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: i first tried to use the alternate encryption method (loop-aes?), which failed for some reason, so instead i used the dmsetup version (which i think was the default), which worked fine. i used the hd-media kernel + initrd image, and it had a little trouble selecting the appropriate .iso image. i had 3 different ones on 2 different partitions, but it automatically selected the first one it found, which was never the right one. i eventually renamed the other .iso images until it worked. otherwise, the install went fine. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=3.1 (installer build 20060721) == Installer hardware-summary: == umame -a: Linux ghig 2.6.16-2-486 #1 Sat Jul 15 21:23:01 UTC 2006 i686 unknown lspci -v -t: -[:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) lspci -v -t:+-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA lspci -v -t:+-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE lspci -v -t:+-07.2 Intel Corporation 82371AB/EB/MB PIIX4 USB lspci -v -t:+-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI lspci -v -t:+-09.0 Neomagic Corporation NM2160 [MagicGraph 128XD] lspci -v -t:+-0a.0 Texas Instruments PCI1211 lspci -v -t:+-0b.0 ESS Technology ES1969 Solo-1 Audiodrive lspci -v -t:\-0c.0 Agere Systems WinModem 56k lspci -n: 00:00.0 0600: 8086:7192 (rev 03) lspci -n: 00:07.0 0680: 8086:7110 (rev 02) lspci -n: 00:07.1 0101: 8086:7111 (rev 01) lspci -n: 00:07.2 0c03: 8086:7112 (rev 01) lspci -n: 00:07.3 0680: 8086:7113 (rev 02) lspci -n: 00:09.0 0300: 10c8:0004 (rev 01) lspci -n: 00:0a.0 0607: 104c:ac1e lspci -n: 00:0b.0 0401: 125d:1969 (rev 02) lspci -n: 00:0c.0 0780: 11c1:0449 (rev 01) lspci -v: 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) lspci -v: Flags: bus master, medium devsel, latency 64 lspci -v: Memory at f800 (32-bit, prefetchable) [size=64M] lspci -v: lspci -v: 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) lspci -v: Flags: bus master, medium devsel, latency 0 lspci -v: lspci -v: 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) lspci -v: Flags: bus master, medium devsel, latency 64 lspci -v: I/O ports at fc90 [size=16] lspci -v: lspci -v: 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) lspci -v: Flags: bus master, medium devsel, latency 64, IRQ 11 lspci -v: I/O ports at fca0 [size=32] lspci -v: lspci -v: 00:07.3
Bug#302801: lessdisks: package fails to install
the error message went a little something like this: Selecting previously deselected package lessdisks. (Reading database ... 149346 files and directories currently installed.) Preparing to replace lessdisks 0.5.3cvs.20040906-14 (using .../lessdisks_0.5.3cvs.20040906-15_all.deb) ... Unpacking replacement lessdisks ... Setting up lessdisks (0.5.3cvs.20040906-15) ... dpkg: error processing lessdisks (--configure): subprocess post-installation script returned error exit status 10 Errors were encountered while processing: lessdisks E: Sub-process /usr/bin/dpkg returned an error code (1) i just noticed that /var/lib/dpkg/info/lessdisks.config is missing... that would make it hard to run the configure script! live well, vagrant pgphSVVWmosFU.pgp Description: PGP signature
Bug#302801: lessdisks: package fails to install
also, /var/lib/dpkg/info/lessdisks.templates is missing. this is probably causing a problem when lessdisks.postinst tries to do a db_get on numerous lessdisks values (in addItems function) and fails because there is no such value in debconf. these sorts of things would readily show themselves by simply installing the package before uploading it to debian... :P live well, vagrant pgp33T0Ba2orf.pgp Description: PGP signature
