On Thu, 2018-06-21 at 12:40 -0700, stan wrote:
> On Thu, 21 Jun 2018 10:50:10 -0700
> Adam Williamson wrote:
>
> > On Thu, 2018-06-21 at 19:27 +0200, Lennart Poettering wrote:
> > > (Also, why is there a userspace component for this stuff in the
> > > first place? I mean streaming data from one c
On Thu, 21 Jun 2018 10:50:10 -0700
Adam Williamson wrote:
> On Thu, 2018-06-21 at 19:27 +0200, Lennart Poettering wrote:
> > (Also, why is there a userspace component for this stuff in the
> > first place? I mean streaming data from one corner of the kernel to
> > another corner of the kernel is
On 06/21/2018 02:00 PM, Gerald B. Cox wrote:
> On Thu, Jun 21, 2018 at 10:27 AM, Lennart Poettering
> wrote:
>
>> Just out of curiosity: when precisely is rngd supposed to be used? As
>> soon as there's a hardware RNG device /dev/hwrng? That should be
>> easy enough: ConditionFileExists=/dev/hwrng
I just installed the cpuid package. Here is a portion of the output for my
processor. As you can see: RDRAND reported "= false" which means
my processor does not suppoprt the hardware random number generator feature.
feature information (1/ecx):
PNI/SSE3: Prescott New Instructions =
On Thu, Jun 21, 2018 at 10:27 AM, Lennart Poettering
wrote:
>
> Just out of curiosity: when precisely is rngd supposed to be used? As
> soon as there's a hardware RNG device /dev/hwrng? That should be
> easy enough: ConditionFileExists=/dev/hwrng... Or are there other
> cases when this is suppose
On Thu, Jun 21, 2018 at 10:48 AM, Adam Williamson <
adamw...@fedoraproject.org> wrote:
> I don't maintain any of these services, so your criticism is neither
> constructive nor accurate.
>
Then why are you inserting yourself into this conversation and looking for
ways to be offended?
It's not abo
On Thu, 2018-06-21 at 19:27 +0200, Lennart Poettering wrote:
> On Do, 21.06.18 10:07, Adam Williamson (adamw...@fedoraproject.org) wrote:
>
> > On Thu, 2018-06-21 at 09:46 -0700, Gerald B. Cox wrote:
> > > Interesting... thanks Adam... but the way I read that is specifically
> > > tailored to "rel
On Thu, 2018-06-21 at 10:18 -0700, Gerald B. Cox wrote:
> On Thu, Jun 21, 2018 at 10:07 AM, Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
> > On Thu, 2018-06-21 at 09:46 -0700, Gerald B. Cox wrote:
> > > Interesting... thanks Adam... but the way I read that is specifically
> > > tailore
On Do, 21.06.18 10:07, Adam Williamson (adamw...@fedoraproject.org) wrote:
> On Thu, 2018-06-21 at 09:46 -0700, Gerald B. Cox wrote:
> > Interesting... thanks Adam... but the way I read that is specifically
> > tailored to "release criteria", not
> > design/implementation guidelines - i.e. to me t
On Thu, Jun 21, 2018 at 10:07 AM, Adam Williamson <
adamw...@fedoraproject.org> wrote:
> On Thu, 2018-06-21 at 09:46 -0700, Gerald B. Cox wrote:
> > Interesting... thanks Adam... but the way I read that is specifically
> > tailored to "release criteria", not
> > design/implementation guidelines -
On Thu, 2018-06-21 at 09:46 -0700, Gerald B. Cox wrote:
> Interesting... thanks Adam... but the way I read that is specifically
> tailored to "release criteria", not
> design/implementation guidelines - i.e. to me this says, don't hold up a
> release because someone
> screwed up and didn't conditio
I opened the ticket, it is here: https://pagure.io/fesco/issue/1918
Thanks again Stephen for the suggestion.
On Thu, Jun 21, 2018 at 9:46 AM, Gerald B. Cox wrote:
> Interesting... thanks Adam... but the way I read that is specifically
> tailored to "release criteria", not
> design/implementati
Interesting... thanks Adam... but the way I read that is specifically
tailored to "release criteria", not
design/implementation guidelines - i.e. to me this says, don't hold up a
release because someone
screwed up and didn't conditionalize the process correctly.
On Thu, Jun 21, 2018 at 9:38 AM, Ad
On Thu, 2018-06-21 at 12:08 -0400, Stephen Gallagher wrote:
> On Thu, Jun 21, 2018 at 12:03 PM Gerald B. Cox wrote:
>
> >
> >
> > On Thu, Jun 21, 2018 at 6:39 AM, Stephen Gallagher
> > wrote:
> >
> > >
> > >
> > >
> > > > I believe we're missing something fundamental here. If a
> > > > pr
Stephen,
Yes, unfortunately, it appears that is needed. I'll create a ticket.
Thanks Stephen.
On Thu, Jun 21, 2018 at 9:08 AM, Stephen Gallagher
wrote:
>
>
> On Thu, Jun 21, 2018 at 12:03 PM Gerald B. Cox wrote:
>
>>
>>
>> On Thu, Jun 21, 2018 at 6:39 AM, Stephen Gallagher
>> wrote:
>>
>>>
On Thu, Jun 21, 2018 at 12:03 PM Gerald B. Cox wrote:
>
>
> On Thu, Jun 21, 2018 at 6:39 AM, Stephen Gallagher
> wrote:
>
>>
>>
>>
>>> I believe we're missing something fundamental here. If a
>>> program/service etc. requires specific hardware to work
>>> and it can't gracefully handle situatio
On Thu, Jun 21, 2018 at 6:39 AM, Stephen Gallagher
wrote:
>
>
>
>> I believe we're missing something fundamental here. If a program/service
>> etc. requires specific hardware to work
>> and it can't gracefully handle situations where that hardware is not
>> present - it shouldn't be a default.
>
On Wed, Jun 20, 2018 at 8:54 PM Gerald B. Cox wrote:
> On Wed, Jun 20, 2018 at 3:26 PM, Adam Williamson <
> adamw...@fedoraproject.org> wrote:
>
>> On Wed, 2018-06-20 at 13:15 -0400, Stephen Gallagher wrote:
>> > On Wed, Jun 20, 2018 at 12:34 PM Gerald B. Cox wrote:
>> >
>> > The proper behavior
On Wed, Jun 20, 2018 at 11:15 PM, Samuel Sieb wrote:
> On 06/20/2018 05:53 PM, Gerald B. Cox wrote:
>
>> I believe we're missing something fundamental here. If a program/service
>> etc. requires specific hardware to work
>> and it can't gracefully handle situations where that hardware is not
>>
On 06/20/2018 05:53 PM, Gerald B. Cox wrote:
I believe we're missing something fundamental here. If a
program/service etc. requires specific hardware to work
and it can't gracefully handle situations where that hardware is not
present - it shouldn't be a default.
The way to handle this (and o
On Wed, Jun 20, 2018 at 3:26 PM, Adam Williamson wrote:
> On Wed, 2018-06-20 at 13:15 -0400, Stephen Gallagher wrote:
> > On Wed, Jun 20, 2018 at 12:34 PM Gerald B. Cox wrote:
> >
> > The proper behavior here would be for these services not to be marked as
> > "failed" when the appropriate hardw
On Wed, 2018-06-20 at 13:15 -0400, Stephen Gallagher wrote:
> On Wed, Jun 20, 2018 at 12:34 PM Gerald B. Cox wrote:
>
> > This isn't related to a service, but is throwing out an spurious error
> > message. There is a patch but it hasn't made it's way
> > yet into the Fedora kernel:
> >
> > rt_c
On Wed, Jun 20, 2018 at 12:35 PM, Lennart Poettering
wrote:
> On Mi, 20.06.18 13:15, Stephen Gallagher (sgall...@redhat.com) wrote:
>
> > The proper behavior here would be for these services not to be marked as
> > "failed" when the appropriate hardware is not present. When possible, we
> > shoul
On Mi, 20.06.18 13:15, Stephen Gallagher (sgall...@redhat.com) wrote:
> The proper behavior here would be for these services not to be marked as
> "failed" when the appropriate hardware is not present. When possible, we
> should be using systemd's Condition* features to skip attempting to start
>
On Wed, Jun 20, 2018 at 10:15 AM, Stephen Gallagher
wrote:
>
>
> On Wed, Jun 20, 2018 at 12:34 PM Gerald B. Cox wrote:
>
>> This isn't related to a service, but is throwing out an spurious error
>> message. There is a patch but it hasn't made it's way
>> yet into the Fedora kernel:
>>
>> rt_cmo
Hi,
On 20-06-18 18:33, Gerald B. Cox wrote:
This isn't related to a service, but is throwing out an spurious error message.
There is a patch but it hasn't made it's way
yet into the Fedora kernel:
rt_cmos registration error: rhbz#1568276
Basically an error is being thrown because your system
On Wed, Jun 20, 2018 at 12:34 PM Gerald B. Cox wrote:
> This isn't related to a service, but is throwing out an spurious error
> message. There is a patch but it hasn't made it's way
> yet into the Fedora kernel:
>
> rt_cmos registration error: rhbz#1568276
> Basically an error is being thrown
27 matches
Mail list logo
