Le mer. 12 août 2020 à 17:04, Christian Nilsson a écrit :
>
> On Wed, 12 Aug 2020, 14:55 Etienne Champetier,
> wrote:
>>
>> Hi Christian,
>>
>> Le mer. 12 août 2020 à 14:42, Christian Nilsson a écrit :
>> >
>> > On Wed, 12 Aug 2020, 13:30 Michael Brown, wrote:
>> >>
>> >> On 12/08/2020 08:50,
On Wed, 12 Aug 2020, 14:55 Etienne Champetier,
wrote:
> Hi Christian,
>
> Le mer. 12 août 2020 à 14:42, Christian Nilsson a
> écrit :
> >
> > On Wed, 12 Aug 2020, 13:30 Michael Brown, wrote:
> >>
> >> On 12/08/2020 08:50, Etienne Champetier wrote:
> >> >>> The automagical construction of CPIO a
Hi Christian,
Le mer. 12 août 2020 à 14:42, Christian Nilsson a écrit :
>
> On Wed, 12 Aug 2020, 13:30 Michael Brown, wrote:
>>
>> On 12/08/2020 08:50, Etienne Champetier wrote:
>> >>> The automagical construction of CPIO archives is indeed for legacy BIOS
>> >>> only. On UEFI, we provide the k
On Wed, 12 Aug 2020, 13:30 Michael Brown, wrote:
> On 12/08/2020 08:50, Etienne Champetier wrote:
> >>> The automagical construction of CPIO archives is indeed for legacy BIOS
> >>> only. On UEFI, we provide the kernel with a virtual filesystem from
> >>> which it can load arbitrary files withou
On 12/08/2020 08:50, Etienne Champetier wrote:
The automagical construction of CPIO archives is indeed for legacy BIOS
only. On UEFI, we provide the kernel with a virtual filesystem from
which it can load arbitrary files without needing a CPIO wrapper.
Do you have a working exemple (maybe I ne
Hi Michael,
Le lun. 3 août 2020 à 15:00, Etienne Champetier
a écrit :
>
> Hi Michael
>
> Le lun. 3 août 2020 à 14:30, Michael Brown a écrit :
> >
> > On 03/08/2020 12:03, Robin Smidsrød wrote:
> > > I seem to recall that this initrd/cpio magic described in the document
> > > only works on legacy
6 matches
Mail list logo
