eve that
user's expectations have changed through the passage of time and thus a fresh
look at the topic may be warranted.
http://bugs.debian.org/397649
Best,
Thiemo Nagel
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
Dear Christian,
thank you for uploading my patches!
> Changes:
> partman-crypto (66) unstable; urgency=low
> .
> [ Thiemo Nagel ]
>* Use the same security setting for wiping existing volumes
> than previous settings, when the volume was already encrypted.
>
> I suppose that could be mitigated if we created a file something like:
>
> /target/Instalation-In-Progress
>
> [...]
>
> I'm not sure that's a good idea though -- it seems somewhat fragile.
Actually, I rather like your idea. There could be a notice that the
system is partially installed, toget
>>The only reason I can think of is that it helps prevent accidentially
>>rebooting the computer half way through the install and encountering a
>>strange half-installed system.
>
> Definitely, yes. If for some reason the installation is aborted, there
> is a good chance that the system will at lea
> I just committed and uploaded everything.
Thank you very much.
> Sorry for the delay.
Not to worry!
I think that it would be very nice to include the speed improvements
into one of the next point releases (after they have received some
coverage in testing). To minimize the risk for breakage w
Package: debian-installer
Severity: wishlist
Tags: d-i
Hello,
I haven't got replies to my post on debian-boot, so I'm archiving this topic
as a whishlist bug:
I've been wondering why the bootloader is installed only at the very end of
the installation. This means that an aborted installation (eg
Dear Thomas,
a blind guess: gold is known to have some issues. Maybe it helps to
use ld from binutils?
Cheers,
Thiemo
On Wed, Oct 30, 2013 at 11:46 AM, Thomas Martin wrote:
> Hi everyone.
>
> I'm trying to build debian-installer on Debian Wheezy 64 but I'm
> getting this error (full log at the
block 726448 by 722898
thanks
I've rebased the patches so that they apply cleanly on top of those from
http://bugs.debian.org/722898
Cheers,
Thiemo
From b83b939093b22544c3b8d9898662ef66515d039f Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
Date: Mon, 14 Oct 2013 10:38:09 +0200
Subject: [PA
xtended descriptions (at least
not in newt), therefore the message is squeezed into the short description
slightly awkwardly.
From 76ac03df4fcd48bfcbb842f8fe83f4c0f409cec9 Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
Date: Mon, 16 Sep 2013 18:00:19 +0200
Subject: [PATCH 1/8] blockdev-w
Oh well, sorry for missing that!
It seems that the 3.10 packages haven't stayed long: daily builds for
amd64, i386 and sparc are failing since Sunday. When do you plan to
switch to 3.11?
Cheers,
Thiemo
On Tue, Oct 22, 2013 at 8:37 PM, Cyril Brulebois wrote:
> Thiemo Nagel (20
Package: partman-auto-crypto
Severity: normal
Tags: d-i
Hello,
it seems that the daily installer build doesn't contain the menu item "Guided
- use entire disk and set up encrypted LVM" anymore, whereas in the wheezy 7.2
installer it is still present. This looks like a regression to me. (I can't
>From fb1d9122cf228a9f083b34b8fb50e9a45e4bf529 Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
Date: Tue, 15 Oct 2013 01:39:01 +0200
Subject: [PATCH] Bump up kernel version to 3.11 to fix daily build
---
build/config/amd64.cfg | 2 +-
build/config/i386.cfg | 2 +-
build/config/sparc.cfg | 2 +-
3 files ch
Hello,
this has already been reported and is being discussed at:
http://bugs.debian.org/718855
Cheers,
Thiemo
On Wed, Oct 16, 2013 at 7:55 PM, wrote:
> Dear Debian Boot Team,
>
> there is a wrong dependencies in the meta package from testing in
> task-xfce-desktop.
> Rec: network-manager-gno
Hello,
I've been wondering why the bootloader is installed only at the very
end of the installation. This means that an aborted installation (eg.
due to power failure or system crash) leaves the system in an
unbootable state. Would it be possible to install the bootloader
before tasksel is being r
of --use-urandom by
> default is a very good catch and fully agree with changing that.
>
> On 15/10/13 20:46, Thiemo Nagel wrote:
>> urandom also is used in crypto-volume wiping.
>
> The wipe is already done with a potentially lower level of security,
> because it forces AES-128 i
)
Cheers,
Thiemo
On Mon, Oct 14, 2013 at 7:36 PM, Thiemo Nagel wrote:
> Hello debian-boot,
>
> may I ask for your help with building a custom installer? After making
> some modifications to partman-crypto, I'd like to build a mini.iso
> image to test them. I&#x
reassign 726434 tzdata
thanks
Thank you for correcting me!
Cheers,
Thiemo
On Tue, Oct 15, 2013 at 10:08 PM, Cyril Brulebois wrote:
> Debian Bug Tracking System (2013-10-15):
>> Processing commands for cont...@bugs.debian.org:
>>
>> > reassign 726434 tzsetup
>> Bug #726434 [debian-installer] d
Package: tzsetup
Severity: minor
Tags: d-i
Hello,
the latest jessie installer selects Madeira as default for Portugal, which I
don't consider appropriate. Could you please make Lisbon the default?
Thank you and best regards,
Thiemo
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian
urandom also is used in crypto-volume wiping. This should be changed,
too. (And a grep for further occurrences might be sensible.)
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists
device() to read the encryption settings of
the to-be-wiped volume and to use them for wiping, too.
Cheers,
Thiemo
P.S.: The second patch adds a bit of logging. Please only apply it if you
consider that useful.
>From c50fb8869e6ff5686c25b53afedd71cba524f255 Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
I'm looking into it currently and will report back
Cheers,
Thiemo
On Tue, Oct 15, 2013 at 8:10 PM, Cyril Brulebois wrote:
> Thiemo Nagel (2013-10-15):
>> running the jessie installer and selecting location Germany, I'm
>> prompted to choose time zone between "
Package: debian-installer
Severity: minor
Tags: d-i
Hello,
running the jessie installer and selecting location Germany, I'm prompted to
choose time zone between "Europe/Berlin" and "Europe/Busingen". The correct
spelling would be "Büsingen".
Cheers,
Thiemo
--
To UNSUBSCRIBE, email to debian-
Hello debian-boot,
may I ask for your help with building a custom installer? After making
some modifications to partman-crypto, I'd like to build a mini.iso
image to test them. I've tried to follow instructions in
http://d-i.alioth.debian.org/doc/internals/ch04.html#id31
but the desired udeb
severity 726298 wishlist
retitle 726298 Give guidance to console-switching installer users
reassign 726298 busybox
tags 726298 + patch
thanks
It's all my fault. I just realized that X is fine, I just didn't
expect it to live on console #5. Maybe the attached patch could help
prevent others falling
Package: debian-installer
Version: daily
Severity: normal
Tags: d-i
Hello,
when booting the graphical install (daily build) as KVM guest and switching to
the text console via Ctrl-Alt-F2 at any time during installation, the graphics
is crashing.
The following error message is displayed on the fi
Since this bug is already about cleanup, here's another patch, this
time to remove trailing whitespace.
Cheers,
Thiemo
0001-Remove-trailing-whitespace.patch
Description: Binary data
s,
Thiemo
>From 6111f8f6b01beefe517a28f144127beddfa32f64 Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
Date: Mon, 14 Oct 2013 09:36:24 +0200
Subject: [PATCH] Remove unused parameter of crypto_wipe_device()
---
active_partition/erasepart/do_option |2 +-
lib/crypto-base.sh |9 -
> On Wed, Oct 02, 2013 at 05:05:10PM +0200, Thiemo Nagel wrote:
> > This bug has some fixes to blockdev-wipe which should bring it up to speed
> > with dd:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718896
>
> Guess you mean [...] http://bugs.debian.org/7228
This bug has some fixes to blockdev-wipe which should bring it up to speed
with dd:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718896
Cheers,
Thiemo
>
> For what it's worth, the patches look good to me but I didn't test them.
>
Thanks for looking! Is there anything still required for the patches to be
committed?
Cheers,
Thiemo
Hello,
I've benchmarked two different resync speed settings in several
configurations by test-installing a base system with debootstrap and
determining the running time of the package installation phase from
dpkg.log. All tests were run on an Athlon II X4 640 with 4 GB RAM.
The first test setup c
t; Quoting Regis Boudin (re...@boudin.name):
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 19/09/13 18:57, Christian PERRIER wrote:
>> > Quoting Thiemo Nagel (thiemo.na...@gmail.com):
>> >
>> >> 2. In case the job doesn't return
I think that level of detail is just right for the installer, we don't
want to scare people off by getting too technical. The Installation
Guide would be the right place for a more detailed explanation, I'd
say.
Cheers,
Thiemo
On Fri, Sep 20, 2013 at 12:13 PM, Holger Levsen wrote:
> Hi,
>
> On D
Thank you for the explanations! Your final proposal looks good to me.
On Thu, Sep 19, 2013 at 6:55 PM, Christian PERRIER wrote:
> Quoting Thiemo Nagel (thiemo.na...@gmail.com):
>
>> "Overwriting ${DEVICE} with random data to prevent meta-information
>> leaks from the encr
On Thu, Sep 19, 2013 at 6:57 PM, Christian PERRIER wrote:
> Quoting Thiemo Nagel (thiemo.na...@gmail.com):
>
>> 2. In case the job doesn't return within a couple of seconds, instruct
>>the user to a) either press keys until enough entropy has been
>>gathe
Package: partman-crypto
Severity: important
Tags: d-i
Hello,
it seems that upon initialization of encrypted volumes, the LUKS master
key is created by reading "entropy" from /dev/urandom which means that
in case the kernel is low on entropy at the time of volume creation,
the volume will be vulne
Hello Christian,
> > Maybe "Skip" would be more precise than "Cancel"?
>
> You probably can't change this as the 'Cancel' button comes from the
> cdebconf interface.
I see. In this case, I agree with Gaudenz that we should explain what
"Cancel" means. I've given it a try:
"Overwriting ${DEVICE}
> If we are changing this anyway, maybe it's a good time to also make the
> template partman-crypto/progress/erase a bit more explicit about
> canceling.
I fully agree!
> It currently reads: "Erasing data on ${DEVICE}". Maybe something like
> "Erasing data on ${DEVICE}. To continue without ereasi
The issue of the raid speed limit is now tracked in bug #723566.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAOGcq_58haAa82Lpp+AEYH=pwhtx81mlh65gpmjjxunyufr...@ma
4)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
>From 086c51a14dbbc8868461c41820d712b9158994ae Mon Sep 17 00:00:00 2001
From: Thiemo Nagel
Date: Tue, 17 Sep 2013 14:51
Hello Gaudenz,
thank you for your email!
Any reason why you choose 512k? If I understand your benchmarks right,
> doubling this to 1M yelds about another 27% gain.
I'm sorry, I forgot to mention that I've re-run the benchmarks. After
removing O_SYNC, the performance was identical for block size
ep 15, 2013 at 12:31 AM, Ben Hutchings wrote:
> On Sat, 2013-09-14 at 23:33 +0200, Thiemo Nagel wrote:
> [...]
> > What I take away from this: For optimal performance, the frequency of
> > syncs should be kept low, probably well below 50 Hz, ideally as low as
> > possible.
Updated patch to include a commit message.
On Sat, Sep 14, 2013 at 9:03 AM, Christian PERRIER wrote:
> Quoting Thiemo Nagel (thiemo.na...@gmail.com):
> > Package: partman-crypto
> > Severity: normal
> > Tags: d-i patch
> >
> > Hello!
> >
> > blockdev
I've done another series of benchmarks, measuring time in seconds to write
915 MB. (That is equivalent to 20 stars of output by blockdev-wipe. "n/a"
values simply haven't been measured.) I've tried two different settings
for speed_limit_min:
time0: speed_limit_min=0
time1: speed_limit_min=1000 k
Package: partman-crypto
Severity: normal
Tags: d-i, patch
Hello,
I'm currently in the process of installing wheezy and after 15 hours of
blockdev-wipe, the progress indicator is at 11%. This means that the expected
time for the wipe to complete would be 5.5 days when extrapolating linearly
(whic
e could confirm this line of
argument.)
Regards,
Thiemo Nagel
-- System Information:
Debian Release: 6.0.7
APT prefers oldstable-updates
APT policy: (990, 'oldstable-updates'), (990, 'oldstable-proposed-updates'),
(990, 'oldstable'), (450, 'proposed-updates
46 matches
Mail list logo
