Following the intrusion on kernel.org I reverified my system
with chkrootkit and it moans like this:
Searching for Suckit rootkit... Warning: /sbin/init INFECTED
SuckIT rootkit? Don't think so, because after
yum reinstall systemd, chkrootkit still reports it.
This is on x86_64
I don't know wher
On Sat, 1 Oct 2011 09:58:12 +0200, LW (Linus) wrote:
> Following the intrusion on kernel.org I reverified my system
> with chkrootkit and it moans like this:
>
> Searching for Suckit rootkit... Warning: /sbin/init INFECTED
>
> SuckIT rootkit? Don't think so, because after
> yum reinstall systemd
2011/10/1 Michael Schwendt :
> On Sat, 1 Oct 2011 09:58:12 +0200, LW (Linus) wrote:
>>
>> I don't know where to report this false positive, shall it
>> be sent to chkrootkit?
>
> Has been reported before -> http://bugz.fedoraproject.org/chkrootkit
Thanks Michael, now I can sleep well again :-)
Yo
Hi All,
Please note that I'm not claiming that the critpath process is broken
in general. But it does not work for certain components. To be specific
it does not work for Xorg drivers for non common hardware.
This morning bodhi send me 3 mails with the following subjects:
[Fedora Update] [CRITPAT
On Sat, Oct 1, 2011 at 9:29 AM, Hans de Goede wrote:
> Hi All,
>
> Please note that I'm not claiming that the critpath process is broken
> in general. But it does not work for certain components. To be specific
> it does not work for Xorg drivers for non common hardware.
>
> This morning bodhi sen
Hi All,
The subject more or less says it all. When I startup my desktop machine (which
thus
is always on AC), and leave it at the gdm screen it will suspend after being
left
alone for 30 minutes. This is not good, since I only leave it powered on when I
intend to access it remotely.
I would lik
On Sat, Oct 1, 2011 at 1:02 PM, Hans de Goede wrote:
> And I can honestly say I've never seen a
> desktop machine where suspend worked with Linux, so suspending desktop
> machines by default seems like a bad idea.
I don't get where this is coming from, suspend has pretty much always
worked on my
Peter Robinson wrote:
> There is a ticket open with fesco to improve the critpath process. You
> can see the proposed changes on the link below.
>
> https://fedorahosted.org/fesco/ticket/667
The problem is that you're a priori exluding the only real solution
(discontinue the critpath process and
On Sat, Oct 1, 2011 at 7:02 AM, Hans de Goede wrote:
> The subject more or less says it all. When I startup my desktop machine
> (which thus
> is always on AC), and leave it at the gdm screen it will suspend after being
> left
> alone for 30 minutes. This is not good, since I only leave it power
On Sat, 01 Oct 2011 13:33:13 +0200, drago01 wrote:
> but the "suspend does not work on desktop" argument is simply not true
Not replying to metoo/flames but neither suspend nor hibernate worked reliably
for me through years on notebook (T60). Depending on BIOS and kernel versions
the former or lat
Hans de Goede wrote:
> The subject more or less says it all. When I startup my desktop machine
> (which thus is always on AC), and leave it at the gdm screen it will
> suspend after being left alone for 30 minutes. This is not good, since I
> only leave it powered on when I intend to access it remo
11 matches
Mail list logo
