Hi,
If this can't be fixed quickly, would it make sense to push an update
which disables os-prober on jessie in cases which are known to (even
possibly) lead to data loss?
I hate to post a "me too" message, but it's a little disheartening to
know that a bug that causes pretty bad data loss in
Hi again,
On Sun, Feb 15, 2015 at 03:21:49PM +0100, Cyril Brulebois wrote:
It would be helpful if either of you could try and figure out what's
going on/why Ron's patch is insufficient/what needs to be changed to
get your usecase to work. At least Chris Kuehl (cc'd) was happy with
the change
Hi all,
Andrew's patch looks very reasonable to me, as it would allow sysadmins
to fully automate installs without further complicating the issues
raised in #712907 (which mostly affect interactive installs).
I've spent a few hours attempting to test the patch, but can't seem to
properly
Hi all,
Petter and Michael, thanks for your work on this!
I'm able to reproduce this bug consistently (100% of the time, having
run ~40 installations in the past week that exhibit it) with the
following steps:
1. PXE boot a jessie netboot image (latest daily build, for example)
2. Add auto=true
On Sun, Sep 21, 2014 at 01:57:55PM +0200, Cyril Brulebois wrote:
Looks like I could just blindly apply both patches, squashing them and
crediting both of you then?
Yup, I think that would do it.
I can do additional sanity testing of the daily build after the patches
are applied, but already
89f74fdc2893a68d2baba8d13cff4846d92840e8 Mon Sep 17 00:00:00 2001
From: Chris Kuehl cku...@ocf.berkeley.edu
Date: Sat, 20 Sep 2014 21:00:11 +
Subject: [PATCH] Fix ldlinux.c32 symlink path
The existing symlink creates a target path like:
debian-installer/amd64/debian-installer/amd64/boot-screens//ldlinux.c32
(note the duplicate
6 matches
Mail list logo
