Am Dienstag, 21. Mai 2019, 16:55:02 CEST schrieb Petr Štetiar:
Hi Petr,
> Etienne Champetier [2019-05-21 14:55:42]:
>
> Hi,
>
> > > First, simply writing to /dev/urandom does not increase the kernel's
> > > entropy count, this casuses processes obtaining randomness to block.
> > > Particularly
Petr Štetiar writes:
> Jeff Kletsky [2019-05-20 20:42:16]:
>
>> Having spent quite a bit of time today thinking about the impact of
>> board-name changes, I can see use cases where the running system doesn't
>> know a priori what the range of acceptable tar-dir values are.
>
> Well it makes me w
On 21/05/2019 17:44, Nick wrote:
If I extend iwinfo to allow setting interfaces into monitor mode, will
it be excepted?
Or is iwinfo just for getting information for an interface?
I use libiwinfo for abstraction for my own daemons.
Bests,
Nick
iwinfo is designed for introspection of the int
If I extend iwinfo to allow setting interfaces into monitor mode, will
it be excepted?
Or is iwinfo just for getting information for an interface?
I use libiwinfo for abstraction for my own daemons.
Bests,
Nick
___
openwrt-devel mailing list
openwrt-de
Etienne Champetier [2019-05-21 14:55:42]:
Hi,
> > First, simply writing to /dev/urandom does not increase the kernel's
> > entropy count, this casuses processes obtaining randomness to block.
> > Particularly processes using OpenSSL's RAND_bytes() will block until the
> > kernel emits 'random: c
> > On Sun, May 19, 2019 at 12:44:18PM -0700, Jeff Kletsky wrote:
> > I'm in the process of porting the AR750S to the ath79 target with
> > SPI-NAND support now available on Linux 4.19[1].
> >
> > From what I can tell, the AR300M (NAND) target, while it builds,
> > does not provide a function
Hi Petr,
Le lun. 20 mai 2019 à 18:14, Petr Štetiar a écrit :
>
> Hi,
>
> this patch series is an RFC which attempts to fix some of the current
> urandom-seed based flaws.
>
> First, simply writing to /dev/urandom does not increase the kernel's
> entropy count, this casuses processes obtaining ran
On 21/05/19 13:10, Petr Štetiar wrote:
Alberto Bursi [2019-05-21 11:44:37]:
On 20/05/19 23:48, Linus Walleij wrote:
On Mon, May 20, 2019 at 10:56 PM Petr Štetiar wrote:
I can start while I still have it in fresh memory and you can chime
in on how you want people to do generic checksum etc.
Jeff Kletsky [2019-05-20 20:42:16]:
> Having spent quite a bit of time today thinking about the impact of
> board-name changes, I can see use cases where the running system doesn't
> know a priori what the range of acceptable tar-dir values are.
Well it makes me wonder, why you just don't do fol
Alberto Bursi [2019-05-21 11:44:37]:
> On 20/05/19 23:48, Linus Walleij wrote:
> > On Mon, May 20, 2019 at 10:56 PM Petr Štetiar wrote:
> >
> > I can start while I still have it in fresh memory and you can chime
> > in on how you want people to do generic checksum etc.
>
> You don't need to wor
On 21/05/19 12:11, Petr Štetiar wrote:
Alberto Bursi [2019-05-21 11:37:31]:
The only clear thing is that documentation does not write itself and that
you can't rely on users to write developer documentation.
You actually can enforce it somehow, as you either include/update
documentation to r
Alberto Bursi [2019-05-21 11:37:31]:
> The only clear thing is that documentation does not write itself and that
> you can't rely on users to write developer documentation.
You actually can enforce it somehow, as you either include/update
documentation to reflect your changes or your contributio
Petr Štetiar wrote:
> From: Liangbin Lian
>
> Lua's LNUM patch currently doesn't parse properly certain
> numbers as it's visible from the following simple tests.
>
Tested-by: Karl Palsson
This makes some busted unit tests of ours pass for the first time
on the openwrt target itself :) It
On 20/05/19 23:48, Linus Walleij wrote:
On Mon, May 20, 2019 at 10:56 PM Petr Štetiar wrote:
And merged[1] it into my staging tree, so please check it and let me know if
it's ok with you or if you prefer to go with v4, thanks.
Thanks man, sorry if I'm a bit confused around how you want the
s
On 21/05/19 11:13, Petr Štetiar wrote:
Linus Walleij [2019-05-20 23:48:41]:
[adding Alberto, Thomas and Javier to the Cc: loop]
how you want the sysupgrade to work.
it's just preferred to share as much common code as possible.
Maybe we could open a documentation page for new devices, like
Linus Walleij [2019-05-20 23:48:41]:
[adding Alberto, Thomas and Javier to the Cc: loop]
> how you want the sysupgrade to work.
it's just preferred to share as much common code as possible.
> Maybe we could open a documentation page for new devices, like here is how
> we want you to implement
16 matches
Mail list logo
