On Mon, Nov 13, 2017 at 1:17 PM, Nicholas D Steeves
wrote:
> On Mon, Nov 13, 2017 at 10:35:19AM -0700, Ben Hildred wrote:
> >On Fri, Nov 10, 2017 at 12:50 PM, Cyril Brulebois <[1]k...@debian.org
> >
> >wrote:
> >
> > Nicholas D Steeves <[2]nstee...@gmail.com> (2017-11-10):
> > >
On Mon, Nov 13, 2017 at 10:35:19AM -0700, Ben Hildred wrote:
>On Fri, Nov 10, 2017 at 12:50 PM, Cyril Brulebois <[1]k...@debian.org>
>wrote:
>
> Nicholas D Steeves <[2]nstee...@gmail.com> (2017-11-10):
> > 1) get a list of disks
> > 2) identify the disk used by the installer
Hi Kibi,
I see Ben Hildred send a reply before I finished this draft :-) I'll
reply to it separately.
On 10 November 2017 at 14:50, Cyril Brulebois wrote:
> Nicholas D Steeves (2017-11-10):
>> 1) get a list of disks
>> 2) identify the disk used by the installer
>> 3) exclude the disk found at
On Fri, Nov 10, 2017 at 12:50 PM, Cyril Brulebois wrote:
> Nicholas D Steeves (2017-11-10):
> > 1) get a list of disks
> > 2) identify the disk used by the installer
> > 3) exclude the disk found at #2
>
> How do you do 2?
>
> Last I touched this, nothing obvious appeared in d-i to know what the
Nicholas D Steeves (2017-11-10):
> 1) get a list of disks
> 2) identify the disk used by the installer
> 3) exclude the disk found at #2
How do you do 2?
Last I touched this, nothing obvious appeared in d-i to know what the
installer was booted from. ISTR having suggested at the time that
bootlo
On Fri, 2017-11-10 at 12:32 -0500, Lennart Sorensen wrote:
> On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> > This is true, but I don't think it's a good reason not to implement a
> > mostly-reliable heuristic.
> >
> > If there are multiple disks, there are usually going to be ju
On Fri, Nov 10, 2017 at 12:32:59PM -0500, Lennart Sorensen wrote:
> On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> > This is true, but I don't think it's a good reason not to implement a
> > mostly-reliable heuristic.
> >
> > If there are multiple disks, there are usually going t
On Fri, Nov 10, 2017 at 04:19:14PM +, Ben Hutchings wrote:
> This is true, but I don't think it's a good reason not to implement a
> mostly-reliable heuristic.
>
> If there are multiple disks, there are usually going to be just 2 of
> them, one of which contains the installer. In any installe
On Fri, 2017-11-10 at 10:10 -0500, Lennart Sorensen wrote:
> On Tue, Nov 07, 2017 at 09:56:31PM +0100, Michael Kesper wrote:
> > Yes sure but why can't I correct it after the fact?
> > Even "rescanning disks" does not let you chose any other disks.
> >
> > Is there a way of chosing "first internal
On Tue, Nov 07, 2017 at 09:56:31PM +0100, Michael Kesper wrote:
> Yes sure but why can't I correct it after the fact?
> Even "rescanning disks" does not let you chose any other disks.
>
> Is there a way of chosing "first internal disk" then?
> Imagine I want to create one installation medium for l
Dear Cyril,
On 07.11.2017 08:12, Cyril Brulebois wrote:
> Michael Kesper (2017-11-06):
>> I think this bug is specific to partman-auto.
>> Partman should allow rescanning devices and recognize NVMe devices when
>> preconfigured with /dev/sda.
>> Alternatively, there should be an installation tar
Hi Michael,
Michael Kesper (2017-11-06):
> I think this bug is specific to partman-auto.
> Partman should allow rescanning devices and recognize NVMe devices when
> preconfigured with /dev/sda.
> Alternatively, there should be an installation target "largest disk" or
> something similar.
I'm not
control: reassign -1 partman-auto
Dear maintainers,
I think this bug is specific to partman-auto.
Partman should allow rescanning devices and recognize NVMe devices when
preconfigured with /dev/sda.
Alternatively, there should be an installation target "largest disk" or
something similar.
Best
13 matches
Mail list logo