On Fri, 2015-01-02 at 11:09 +0100, Uwe Kleine-König wrote:
> Hello Ian,
>
> > Uwe, any chance you could try this please:
> >
> > diff --git a/functions b/functions
> > index d45a4e6..a7ff6de 100644
> > --- a/functions
> > +++ b/functions
> > @@ -41,7 +41,11 @@ error() {
> > mtdblock() {
> >
Hello Ian,
Uwe, any chance you could try this please:
diff --git a/functions b/functions
index d45a4e6..a7ff6de 100644
--- a/functions
+++ b/functions
@@ -41,7 +41,11 @@ error() {
mtdblock() {
local mtdname="$1"
- sed -rn "s,^mtd([^:]*).*\"$mtdname\"\$,/dev/mtdblock\\1,p" "$PRO
On Tue, 2014-12-30 at 13:42 -0800, Vagrant Cascadian wrote:
> On 2014-12-30, Ian Campbell wrote:
>
> > 0004-Add-SD-card-image-build-support-for-hd-media-builds-.patch
> ...
> > It seems to be creating a copy of dtbs again, please lets try
> > and keep it to one set of these files
On Wed, 2014-12-31 at 01:59 +0100, Karsten Merker wrote:
> > 0001-Add-boot-arm-u-boot-image-config.patch
> >
> > Seems fine.
> >
> > 0002-Provide-u-boot-binaries-for-armhf-systems-without-u-.patch
>
> > I think this isn't actually publishing the u-boot binaries, but
> > r
Hello,
I can tell example where having raw disk as PV is handy: using hardware
RAID controllers, such as Areca ones.
Raid controllers allows you to add new disks to existing raid array. For
example, if you have Raid 10 using four 1TB disks, you can add two more
disks and increase capacity from 2T
Samuel Thibault (2015-01-01):
> Source: libxml2
> Version: 2.8.0+dfsg1-7+wheezy2
> Severity: serious
> Justification: makes other package FTBFS
>
> Hello,
>
> The cve-2014-3660.patch patch makes installation-guide FTBFS:
>
> Entity: line 2: parser error : Detected an entity reference loop
> u
Karsten Merker (2015-01-02):
> > (Do your patches end up adding the correct Built-Using on u-boot?)
>
> No, they don't, but d-i does not do that for similar components
> on other platforms (syslinux/isolinux/grub) as well. Probably we
> should do that, but then it would have to be done for all
>
On 2015-01-02, Ian Campbell wrote:
> On Tue, 2014-12-30 at 13:42 -0800, Vagrant Cascadian wrote:
>> On 2014-12-30, Ian Campbell wrote:
>> I think the difference is one is a set of netboot images, and the other
>> is a set of hd-media images.
>
> But what is the difference between these two things
When the only disk is "completely LVM",
then boot loaders should also have support for it.
When the computer is "Only LVM" also.
"workaround": use an additional dedicated boot disk[1]
Groeten
Geert Stappers
Note
[1] something that bootROM ( "BIOS" ) supports
signature.asc
Description: Di
Source: choose-mirror
Severity: important
cdn.debian.net is in the process of being deprecated, orphaned and
transitioned to http.debian.net, please remove it from the mirrors list.
This should be fixed in both wheezy and jessie d-i.
https://lists.debian.org/cag2rkxmdbll-vsfw6deu4p0nwt7qqor3pxvqd
2015.01.02 22:13, Geert Stappers wrote:
"workaround": use an additional dedicated boot disk[1]
With HW Raid, it's exactly what we intended to do: create very small volume (for Linux point of view it's just /dev/sda)
to be as "boot disk", containing only boot loader (and maybe /boot), which sh
11 matches
Mail list logo
