Vagrant Cascadian (2019-03-07):
> If that's indeed the case, then that does seem like the best approach.
> Happy to test images to confirm.
Rebuilding the stretch debian-installer source package within stretch
should give you everything you need to test. Beware if you go for a
manual build instea
Ben Hutchings (2019-03-07):
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
> > > * Rebuild the debian-installer images, pulling in updates from
> > > stretch-updates, leaving only armhf netboot targets broken.
> >
> > Expanding a bit: rebuilding src:debian-installer from t
On 2019-03-07, Ben Hutchings wrote:
> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
> [...]
>> > * Rebuild the debian-installer images, pulling in updates from
>> > stretch-updates, leaving only armhf netboot targets broken.
>>
>> Expanding a bit: rebuilding src:debian-installer fro
On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
[...]
> > * Rebuild the debian-installer images, pulling in updates from
> > stretch-updates, leaving only armhf netboot targets broken.
>
> Expanding a bit: rebuilding src:debian-installer from the stretch
> branch, which has s-p-u enab
> On Mar 6, 2019, at 7:46 PM, Vagrant Cascadian wrote:
>
> On 2019-03-06, Rick Thomas wrote:
>> Anybody know how can I determine where u-boot is storing it’s environment?
>> Is there an environment variable where that info is stored?
>> (-: Any ironic self-reference in the previous question is
On Thursday 07 March 2019 08:39:19 Cyril Brulebois wrote:
> Hi,
>
> Vagrant Cascadian (2019-03-06):
> > Even rebuilding the debian-installer images, while pulling in a
> > working kernel that would boot, debian-installer would load .udeb
> > modules from stretch, not stretch-updates. This might b
Hi,
Vagrant Cascadian (2019-03-06):
> Even rebuilding the debian-installer images, while pulling in a
> working kernel that would boot, debian-installer would load .udeb
> modules from stretch, not stretch-updates. This might be ok for
> hd-media targets or targets that do not load module .udeb f
On Thu, Mar 7, 2019 at 11:11 AM Rick Thomas wrote:
> Anybody know how can I determine where u-boot is storing it’s environment?
That depends on which build of u-boot you are using, what hardware you
are using etc, but all of them should be able to print it with the
printenv command.
--
bye,
pab
Hi,
W dniu 07.03.2019 o 06:40, Paul Wise pisze:
Hi all,
Is anyone interested in helping out with these and related tools?
https://github.com/libusbgx/libusbgx: C library & example commands
https://github.com/kopasiak/gt: command-line tools
Actually I would be interested in helping with
9 matches
Mail list logo
