From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-51807-garchives=archives.gentoo.org@gentoo.org>)
id 1GRvDX-0006cz-9J
for garchives@archives.gentoo.org; Mon, 25 Sep 2006 18:30:11 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8PIT1fv003864;
Mon, 25 Sep 2006 18:29:01 GMT
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8PINrMW014323
for <gentoo-user@lists.gentoo.org>; Mon, 25 Sep 2006 18:23:53 GMT
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id 9AA7B64141
for <gentoo-user@lists.gentoo.org>; Mon, 25 Sep 2006 18:23:52 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 required=5.5 tests=[AWL=0.318,
BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2, HTML_30_40=0.374,
HTML_MESSAGE=0.001]
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id cEnGzLkA9XS3 for <gentoo-user@lists.gentoo.org>;
Mon, 25 Sep 2006 18:23:50 +0000 (UTC)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169])
by smtp.gentoo.org (Postfix) with ESMTP id 83B7E641CB
for <gentoo-user@gentoo.org>; Mon, 25 Sep 2006 18:23:49 +0000 (UTC)
Received: by ug-out-1314.google.com with SMTP id h2so582398ugf
for <gentoo-user@gentoo.org>; Mon, 25 Sep 2006 11:23:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
b=OXZlW5G2ZVxIQEV2TYYpKeYehKG+NuCjbmB7IPGfmppM7ivpUw6R93iWr7AN1EOBnnly1b+BFIq73ujJz1ggT/TT1mhSeqyEhTKtqA875hZldQQVSMUK9+Gvel+aqeEKrUjgNlQPFb+G8JdMhjCzMb0gbgdgeoT8RuMZgppqsuM=
Received: by 10.66.219.11 with SMTP id r11mr3641286ugg;
Mon, 25 Sep 2006 11:23:48 -0700 (PDT)
Received: by 10.66.245.16 with HTTP; Mon, 25 Sep 2006 11:23:47 -0700 (PDT)
Message-ID: <d18977190609251123p41e5f0d3h62c18eae19a45270@mail.gmail.com>
Date: Mon, 25 Sep 2006 11:23:47 -0700
From: "David Grant" <davidgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [gentoo-dev] baselayout-1.12.5 sucks
In-Reply-To: <7B97065F451A23458ED0C63B4CA5A2EA7C4AE2@SRV-EXCHANGE.AUTOonline.local>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_46720_12576456.1159208627946"
References: <7B97065F451A23458ED0C63B4CA5A2EA7C4AE2@SRV-EXCHANGE.AUTOonline.local>
X-Archives-Salt: af9db90f-8eca-490e-82cb-301d9334daaa
X-Archives-Hash: a87495097e48e30b015d284fa835fd41
------=_Part_46720_12576456.1159208627946
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Try:
RC_HOTPLUG="no"
RC_COLPLUG="no"
RC_NET_STRICT_CHECKING="no"
doing that I think will give you what you want.
Dave
On 9/25/06, Noack, Sebastian <S.Noack@autoonline.de> wrote:
>
> Hi,
>
> at the weekend I upgraded to baselayout-1.12.5. And this is the worse
> version of baselayout since I'm using Gentoo.
>
> The first reason therefore is, that the kernel log is spamming to your
> console all the time, because of the loglevel doesn't become set to 1
> anymore.
>
> The workaround is to hack /etc/init.d/checkroot to call `dmesg -n 1` on
> startup, even though in /etc/conf.d/rc is a variable RC_DMESG_LOGLEVEL
> which is set to "1" by default, but it doesn't affect anything.
>
>
> The other reason is, that independent from which net.*-scripts are
> attached to a runlevel, at least one net.*-script besides net.lo becomes
> started according to RC_NET_STRICT_CHECKING="no" [1] in /etc/conf.d/rc.
> Such behaviour shouldn't be the default. If I want a distro where
> anything happens automatically, I would use Ubunto or Suse. Furthermore
> it isn't even possible to stop this behaviour by setting
> RC_NET_STRICT_CHECKING to "none" or "lo" [1].
>
> The workaround therefore is to set RC_PLUG_SERVICES="!net.*" in
> /etc/conf.d/rc.
>
>
> But however, the best workaround would be the following I guess. :)
>
> echo "~sys-apps/baselayout-1.12.5" >> /etc/portage/package.mask
>
>
> If I just misunderstood the new configurations of baselayout-1.12.5,
> feel free to answer, before other people apply my bad workarounds. ;)
>
>
> [1]
> # RC_NET_STRICT_CHECKING allows some flexibility with the 'net' service.
> # The following values are allowed:
> # none - The 'net' service is always considered up.
> # no - This basically means that at least one net.* service besides
> net.lo
> # must be up. This can be used by notebook users that have a
> wifi and
> # a static nic, and only wants one up at any given time to have
> the
> # 'net' service seen as up.
> # lo - This is the same as the 'no' option, but net.lo is also
> counted.
> # This should be useful to people that do not care about any
> specific
> # interface being up at boot.
> # yes - For this ALL network interfaces MUST be up for the 'net'
> service to
> # be considered up.
>
>
> Regards
> Sebastian Noack
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
David Grant
http://www.davidgrant.ca
------=_Part_46720_12576456.1159208627946
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Try:<br>RC_HOTPLUG="no"<br>RC_COLPLUG="no"<br>RC_NET_STRICT_CHECKING="no"<br><br>doing that I think will give you what you want.<br><br>Dave<br><br><br><div><span class="gmail_quote">On 9/25/06,
<b class="gmail_sendername">Noack, Sebastian</b> <<a href="mailto:S.Noack@autoonline.de">S.Noack@autoonline.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>at the weekend I upgraded to baselayout-1.12.5. And this is the worse<br>version of baselayout since I'm using Gentoo.<br><br>The first reason therefore is, that the kernel log is spamming to your<br>console all the time, because of the loglevel doesn't become set to 1
<br>anymore.<br><br>The workaround is to hack /etc/init.d/checkroot to call `dmesg -n 1` on<br>startup, even though in /etc/conf.d/rc is a variable RC_DMESG_LOGLEVEL<br>which is set to "1" by default, but it doesn't affect anything.
<br><br><br>The other reason is, that independent from which net.*-scripts are<br>attached to a runlevel, at least one net.*-script besides net.lo becomes<br>started according to RC_NET_STRICT_CHECKING="no" [1] in /etc/conf.d/rc.
<br>Such behaviour shouldn't be the default. If I want a distro where<br>anything happens automatically, I would use Ubunto or Suse. Furthermore<br>it isn't even possible to stop this behaviour by setting<br>RC_NET_STRICT_CHECKING to "none" or "lo" [1].
<br><br>The workaround therefore is to set RC_PLUG_SERVICES="!net.*" in<br>/etc/conf.d/rc.<br><br><br>But however, the best workaround would be the following I guess. :)<br><br>echo "~sys-apps/baselayout-1.12.5
" >> /etc/portage/package.mask<br><br><br>If I just misunderstood the new configurations of baselayout-1.12.5,<br>feel free to answer, before other people apply my bad workarounds. ;)<br><br><br>[1]<br># RC_NET_STRICT_CHECKING allows some flexibility with the 'net' service.
<br># The following values are allowed:<br># none - The 'net' service is always considered up.<br># no - This basically means that at least one net.* service besides<br>net.lo<br># must be up. This can be used by notebook users that have a
<br>wifi and<br># a static nic, and only wants one up at any given time to have<br>the<br># 'net' service seen as up.<br># lo - This is the same as the 'no' option, but net.lo is also<br>counted.<br>
# This should be useful to people that do not care about any<br>specific<br># interface being up at boot.<br># yes - For this ALL network interfaces MUST be up for the 'net'<br>service to<br># be considered up.
<br><br><br>Regards<br>Sebastian Noack<br><br>--<br><a href="mailto:gentoo-dev@gentoo.org">gentoo-dev@gentoo.org</a> mailing list<br><br></blockquote></div><br><br clear="all"><br>-- <br>David Grant<br><a href="http://www.davidgrant.ca">
http://www.davidgrant.ca</a>
------=_Part_46720_12576456.1159208627946--
--
gentoo-user@gentoo.org mailing list