Chuck Zmudzinski writes:
> If it doesn't work, I am also willing to try approach a by patching
> the Linux kernel xen-kbdfront driver by removing the for loops that
> advertise those 654 keys. I tend to agree with Philip that this is
> totally unnecessary, but I suppose I could be wrong about th
Ben Hutchings writes:
> I think a proper fix would be one of:
>
> a. If the Xen virtual keyboard driver is advertising capabilities it
>doesn't have, stop it doing that.
> b. Change the implementation of modalias attributes to allow longer
>values.
>
> It's not clear to me whether the X
Michael Biebl writes:
> So this is a change in behaviour in the kernel?
Yes, this commit fixed the kernel to report the error instead of
silently failing:
commit df44b479654f62b478c18ee4d8bc4e9f897a9844
Author: Peter Rajnoha
Date: Wed Dec 5 12:27:44 2018 +0100
kobject: return error cod
Package: debian-installer
Version: 20210415
I just tried using the hd-media build to boot from an existing hard disk
and install without using removable media and was not able to do so
because I used btrfs on the hard disk, and most filesystems are packaged
as separate udebs rather than being buil
reassign 983357 linux
severity grave
thanks
I rebuilt the iso using the version of isolinux from stable and it still
crashed the domU. When I rebuilt it using the vmlinux and initrd.gz
from the stable iso, it successfully boots, so it appears to be caused
by the kernel.
Interestingly, there appe
Package: debian-installer
Version: 20201202
Every bullseye netinst image I have tried to boot in a xen domU has
crashed and rebooted the domU after choosing any entry from the boot
menu. I thought there might have been something wrong with my xen
server, which was running Ubuntu 18.04, but I rebu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: partman-partitioning
Version: 111
When installing to a GPT partitioned disk in bios mode, a bios_grub
partition is required to install grub. Partman should warn the user
of this if they do not have one.
-BEGIN PGP SIGNATURE-
Versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/17/2015 5:51 PM, Steve McIntyre wrote:
> On Tue, Feb 17, 2015 at 09:32:56AM -0500, Phillip Susi wrote:
>> Package: grub-installer Version: 1.110
>>
>> I'm forwarding this patch from Ubuntu:
>>
>> https://la
On 2/17/2015 1:37 AM, Steve McIntyre wrote:
> Any futher clues on this at all? I have next to no knowledge about how
> the Ubuntu installer code uses the d-i packages, which makes it
> difficult for me to comment much more.
I emailed a log with my attempt at analyzing it to Colin Watson the
other
itter: Phillip Susi
branch nick: grub-installer
timestamp: Tue 2015-02-17 09:15:44 -0500
message:
Don't try to mark a partition as active, except on grub-pc.
This was causing failures for grub-efi (LP: #1303790).
diff:
=== modified file 'debian/changelog'
--- debian/changelog2014-
On 02/11/2015 11:47 AM, Steve McIntyre wrote:
> Quite, that's exactly how it's meant to work and it's what I've seen
> in my development and testing. Silly question - is ubiquity trying to
> run some of the d-i bits in parallel, or something?
That's what I was wondering. I'm looking at /var/log/p
On 2/11/2015 4:38 AM, Steve McIntyre wrote:
> Hmmm, and just testing with the latest Debian amd64 daily netinst all
> works flawlessly here still, using the same empty disk in a KVM setup
> as your bug reporter.
Strange.. I'll have to poke around with that.
> This suggests the problem is Ubuntu-s
title 777647 partman-efi complains about boot problem whenever the
target disk does not have an efi system partition
thanks
Sorry, I mentioned that it involved installing from a usb stick, but it
also happens when installing from cdrom; using a usb stick has nothing
to do with it.
--
To UNSUBSC
Package: partman-efi
Version: 59
partman-efi uses flawed logic that trips up when installing from usb.
init.d/efi scans the system and counts the number of efi system
partitions, and the number of non efi system partitions. If it does not
find an EFI system partition, but does find at least one n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: partman-efi
Version: 59
Recently a new message was added to d-i:
This machine's firmware has started the installer in UEFI mode but
it looks like there may be existing operating systems already
installed using "BIOS compatibility mode". I
5268..edf0382 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+partman-efi (40) UNRELEASED; urgency=low
+
+ * Switch to using mkdosfs instead of libparted
+
+ -- Phillip Susi Fri, 14 Feb 2014 15:44:22 -0500
+
partman-efi (39) unstable; urgency=low
[ Updated translations ]
dif
ian/changelog
index 8a8fc5b..16790bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,7 @@ partman-basicfilesystems (91) UNRELEASED; urgency=low
* Remove check_swap, as there is no such thing as fscking swap
* Use dosfstools to format and check fat filesystems rather than
libpar
is no
+longer supported in parted3.
+ * Remove check_swap, as there is no such thing as fscking swap
+
+ -- Phillip Susi Wed, 12 Feb 2014 15:56:24 -0500
+
partman-basicfilesystems (90) unstable; urgency=low
[ Updated translations ]
--
1.8.3.2
--
To UNSUBSCRIBE, email to debian-boot-requ
* Remove check_swap, as there is no such thing as fscking swap
+ * Use dosfstools to format and check fat filesystems rather than
+libparted.
-- Phillip Susi Wed, 12 Feb 2014 15:56:24 -0500
diff --git a/debian/control b/debian/control
index f326b28..82f7288 100644
--- a/debian/control
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/12/2014 9:34 AM, Colin Watson wrote:
> I think it would be very helpful to split up the logical chunks of
> this.
>
> Moving ext2 support means that we need to make sure that
> partman-basicfilesystems and partman-ext3 land in unstable and
> tes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/19/2014 10:14 AM, Steve McIntyre wrote:
> This *looks* sane enough to me, but I've not had a chance to test
> it directly yet. What testing have you done, please?
None yet. I guess I could figure out how to get qemu to emulate an
efi system. On
5:45:19.0 -0500
@@ -1,3 +1,9 @@
+partman-efi (40) unstable; urgency=low
+
+ * Switch to using mkdosfs instead of libparted
+
+ -- Phillip Susi Fri, 14 Feb 2014 15:44:22 -0500
+
partman-efi (39) unstable; urgency=low
[ Updated translations ]
diff -Nru partman-efi-39/debian/control partma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For what it's worth, I agree with Rui that this is a bug in
live-build, not partman. I'm not sure how it gets that way since
Ubuntu's live-build still has that touch command, but the live
squashfs image on Ubuntu's install cds does not have the fstab.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I made one small mistake with this patch. It turns out there aren't
symlinks for mkfs.fat{16,32}, so the mkfs line needs changed from
mkfs.$filesystem to mkfs.vfat -F ${filesystem#fat}.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/14/2014 12:09 AM, Cyril Brulebois wrote:
> The parted3 transition is about transitioning from libparted0 to
> libparted2? Anyway, why is the -dev package versioned at all?
> Unless you keep several source packages in the archive for a while,
> th
@@
+partman-base (173) unstable; urgency=low
+
+ * parted_server: remove support for filesystem create/check/copy
+and link to libparted2 instead of libparted0.
+
+ -- Phillip Susi Wed, 12 Feb 2014 11:57:20 -0500
+
partman-base (172) unstable; urgency=low
[ Updated translations ]
diff -Nru
fi
+ db_progress STOP
if [ "$status" != OK ]; then
db_subst
partman-basicfilesystems/create_swap_failed TYPE linux-swap
diff -Nru partman-basicfilesystems-90/debian/changelog
partman-basi
bian/changelog 2014-02-13 14:16:19.0 -0500
@@ -1,3 +1,9 @@
+partman-ext3 (82) unstable; urgency=low
+
+ * Pick up support for ext2
+
+ -- Phillip Susi Thu, 13 Feb 2014 14:15:28 -0500
+
partman-ext3 (81) unstable; urgency=low
[ Updated translations ]
diff -Nru partman-ext3-81/d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/13/2014 12:08 PM, Michael Tokarev wrote:
> Out of curiocity, why libparted is needed to copy a partition into
> some other place? How about
>
> dd if=/dev/source-partition of=/dev/dest-partition
>
> ?
>
> (Well, with proper options, maybe with
tman-partitioning-100/debian/changelog 2014-02-13 10:04:13.0
-0500
@@ -1,3 +1,9 @@
+partman-partitioning (100) unstable; urgency=low
+
+ * Remove partition copy operation for libparted 3 transition
+
+ -- Phillip Susi Thu, 13 Feb 2014 10:03:14 -0500
+
partman-partitioning (99)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It also depends on ufsutils-udeb, which is only built on kfreebsd. It
seems to me that this package needs changed from all to kfreebsd only.
This prevents building d-i monolithic images.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/10/2014 4:36 PM, Colin Watson wrote:
> Phillip, you've asked me about this a number of times. I think the
> work involved is fairly clear, although I don't seem to have
> managed to make time for it personally. Perhaps, rather than
> continuing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Say Colin, it has been over a year so I thought I would ping on this.
Is this really the only issue that is still preventing the parted3
transition? If so I think it may be time go go ahead and make the
move rather than continue to block on this, whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Do you mean that removing logical volume on ISW and creating an MD
> mirror (i.e., software mirror via normal kernel modules) I would
> get a software mirror accelerated with ISW hardware?
There is no hardware acceleration as this is a fake raid co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/2013 4:17 PM, Marc Haber wrote:
> The following patch introduces an --include-early option which
> allows to introduce eatmydata early enough:
Is this intended to be applied instead of, or on top of my initial
patch? If the former ( which I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2013 06:54 PM, Bob Proulx wrote:
> # time debootstrap wheezy testinstall
> http://localmirror/ftp.us.debian.org/debian ... real2m58.577s
> user0m49.639s sys 0m8.749s
Wow, that's pretty fast. I was testing on a server with a raid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/15/2013 09:09 PM, Cyril Brulebois wrote:
- --force-unsafe-io only eliminates *some* of the syncs, and seems to
only be applied in the latter part of the installation that takes
place after debootstrap.
I started working on a patch to dpkg to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been working on making debootstrap and installing go faster, as
they currently take about 5x longer than they should ( on ext4, it's
even worse on btrfs ). I have patched debootstrap to add the
eatmydata package to the required list and enable it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/15/2013 12:18 PM, Didier 'OdyX' Raboud wrote:
> Reversed patch?
Woops, yes...
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRHoNYAAoJEJrBOlT6nu75
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This simple two line patch does the trick:
- --- sid 2013-02-15 11:03:15.384977238 -0500
+++ sid.orig2013-02-15 10:50:23.381293976 -0500
@@ -16,7 +16,7 @@
esac
work_out_debs () {
- - required="$(get_debs Priority: required) eatmydata"
+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debootstrap
Version: 1.0.46
Debootstrap is very, very slow. I watched a server install crawl by
for something like an hour at a rate of about 1 package per second. A
simple debootstrap chroot takes 10 minutes to setup, with a
predownloaded ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have trouble believing that this is going to be easier than
> patching the most common utilities to add an option for a
> machine-readable progress indicator.
Not too long ago I was looking at patching gparted to support this and
while it did not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm confused. My understanding is that partman was already using
external utilities for everything besides fat, hfs, and ext2 resize,
and that there were already bug reports covering the lack of progress
indication with those. Parted3 appears to have
I posted this reply several weeks ago and have not seen any further
messages on the subject, but I am not subscribed to debian-boot, so was
there follow up discussion there that I missed?
Phillip Susi wrote:
I posted to utnubu-discuss a few weeks ago that I was working on this
myself. I
44 matches
Mail list logo
