From: Renat Golubchyk <ragermany@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] curious thing with net.eth0
Date: Mon, 24 Oct 2005 21:20:05 +0200 [thread overview]
Message-ID: <20051024212005.463d5d0d@mating-tux.renatik.de> (raw)
In-Reply-To: <435D30B2.4020906@harvee.org>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Mon, 24 Oct 2005 15:06:26 -0400 "Eric S. Johansson" <esj@harvee.org>
wrote:
> The problem was /etc/init.d/net.eth0 and /etc/init.d/net.lo were the
> same. The net.eth0 code was overwritten with the lo code.
>
> This happened on two machines and I'm wondering how it happened? Did
> something go wrong in the emerge process? There's no sign of any
> attackers.
They are always the same since net.eth0 (and all other net.<interface>)
is a symlink to net.lo.
Cheers,
Renat
--
Probleme kann man niemals mit derselben Denkweise loesen,
durch die sie entstanden sind.
(Einstein)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-24 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 19:06 [gentoo-user] curious thing with net.eth0 Eric S. Johansson
2005-10-24 19:20 ` Renat Golubchyk [this message]
2005-10-24 19:34 ` Eric S. Johansson
2005-10-24 20:29 ` Willie Wong
2005-10-24 20:47 ` Eric S. Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051024212005.463d5d0d@mating-tux.renatik.de \
--to=ragermany@gmx.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox