public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Kohl <citizen428@cargal.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] a suggestion about einfo messages
Date: Wed, 21 Jul 2004 17:51:59 +0200	[thread overview]
Message-ID: <20040721175159.2c35401f@localhost> (raw)
In-Reply-To: <43241.66.99.246.226.1090423772.squirrel@66.99.246.226>

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

On Wed, 21 Jul 2004 10:29:32 -0500 (CDT)
"Joseph Booker" <joe@neoturbine.net> wrote:

> I think what he was saying, is that einfo (and i guess ewarn also)
> would be redirected to a file, what about the same file as the regular
> PORT_LOGDIR, but with *.einfos.log files also? (or instead of?)

Look, that's sample output from portlog-info:
=== 2004-07-08 12:56 === iptables-1.2.11-r2 ===
 = /var/log/emerge/4528-iptables-1.2.11-r2.log =
...
 * This package now includes an initscript which loads and saves
 * rules stored in /var/lib/iptables/rules-save
 * This location can be changed in /etc/conf.d/iptables
 *
 * If you are using the iptables initsscript you should save your
 * rules using the new iptables version before rebooting.
 *
 * If you are uprading to a >=2.4.21 kernel you may need to rebuild
 * iptables.
 *
 * !!! ipforwarding is now not a part of the iptables initscripts.
 * Until a more permanent solution is implemented adding the following
 * to /etc/conf.d/local.start will enable ipforwarding at bootup:
 *   echo "1" > /proc/sys/net/ipv4/conf/all/forwarding


As you can see these *ARE* the einfo lines, so there's no need for other
files like iptables.einfo.log, because the information is already there.
Or maybe I'm just not getting what you're trying to tell me, which is
always a possibility with me... ;-)

Regards,
Michael

-- 
www.cargal.org 
GnuPG-key-ID: 0x90CA09E3
Jabber-ID: citizen428 [at] cargal [dot] org
Registered Linux User #278726

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-21 15:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  8:22 [gentoo-portage-dev] a suggestion about einfo messages YiDa Chiang
2004-07-21  9:04 ` Michael Kohl
2004-07-21 15:29   ` Joseph Booker
2004-07-21 15:51     ` Michael Kohl [this message]
2004-07-21 16:15       ` Thomas de Grenier de Latour
2004-07-21 16:19         ` Michael Kohl
2004-07-21 16:01     ` Thomas de Grenier de Latour
2004-07-21 16:06       ` Joseph Booker
2004-07-21 21:30   ` [gentoo-portage-dev] " Joel Konkle-Parker
2004-07-22 20:48     ` Joseph Booker
2004-07-22 21:31       ` Joel Konkle-Parker
2004-07-23  9:08         ` Kumba
2004-07-23 11:32           ` Joel Konkle-Parker
2004-07-25 15:57           ` [gentoo-portage-dev] SSE2 and MMX2 use flags Roman Gaufman
2004-07-25 16:16             ` Marius Mauch
2004-07-25 18:06               ` Roman Gaufman

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=20040721175159.2c35401f@localhost \
    --to=citizen428@cargal.org \
    --cc=gentoo-portage-dev@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