public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openrc 0.9.4 : opaque warnings
Date: Tue, 29 Nov 2011 06:41:57 -0500	[thread overview]
Message-ID: <20111129114157.GA3067@ca.inter.net> (raw)
In-Reply-To: <CAA2qdGWNaVup7VXQBE745UprnaHUeeO5Tjc_u0zZL=xCQ7d3hg@mail.gmail.com>

111128 Pandu Poluan wrote:
> On Mon, Nov 28, 2011 at 17:17, Philip Webb <purslow@ca.inter.net> wrote:
>> Since updating to Openrc 0.9.4 , I'm getting some opaque messages :
>> (1) When starting eth0 : "You are using a bash array for config_eth0.
>> This feature will be removed in the future.  Please see net.example
>> for the correct format for config_eth0".
> Open /etc/conf.d/net ; Compare it with /etc/conf.d/net.example
> For example: The old way of writing multiple addresses for eth0 is:
> config_eth0=("1.2.3.4" "6.7.8.9")
> The new non-bash-array way: config_eth0="1.2.3.4 <newline> 6.7.8.9"
> Make sure you rewrite your conf.d files according to the new way.

Thanks: I've done that & my I/net connection doesn't seem affected.

>> (2) When starting D-BUS system messages: "Use of the opts variable
>> is deprecated & will be removed in the future.  Please see extra_commands
>> or extra_started_commands".
> The relevant initscript in /etc/init.d is still using opts="..." line.
> The newer way is to put the words in opts="..."
> into extra_commands="..." or extra_started_commands="..."
> both parameters described in 'man runscript'
> You *can* edit the offending initscript,
> but it should be the package's maintainers' responsibility
> to revise the initscript and release a new revision.
> Just wait say one or two months & update to the fixed new revision.

So that one looks like an oversight by the maintainer.
I've read & noted the subsequent msgs in the thread: thanks.

A further question: since I had previously updated  /etc/conf.d/net ,
I was given a router by my ISP & therefore started to use DHCP.
The new  net.example  file suggests I might make further changes in 'net'
& simplify my configuration files.  What I have now in 'net' is :

# For a static configuration use eg :
# PP 111129 : drop Bash syntax to avoid start-up warning
#config_eth0=( "192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255" )
config_eth0="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
# You need to create the PPP net script yourself:
# do it via 'cd /etc/init.d ; ln -s net.lo net.ppp0'
# We have to instruct ppp0 to actually use ppp
config_ppp0=( "ppp" )
# Each PPP interface requires an interface to use as a "Link"
link_ppp0="eth0"       		# PPPoE requires an ethernet interface
# Specify what pppd plugins you want to use: available are:
# pppoe, pppoa, capi, dhcpc, minconn, radius, radattr, radrealms, winbind 
plugins_ppp0=( "pppoe" )
# PPP requires at least a username.
# It will use the password specified in /etc/ppp/*-secrets
username_ppp0='****@***'
#pppd_ppp0=( "debug" "updetach" "noauth" "defaultroute" "usepeerdns" "persist" )
pppd_ppp0=( "updetach" "defaultroute" )

Does anyone have further suggestions or comments ?

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca




  parent reply	other threads:[~2011-11-29 11:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 10:17 [gentoo-user] openrc 0.9.4 : opaque warnings Philip Webb
2011-11-28 10:29 ` Pandu Poluan
2011-11-28 10:40   ` Pandu Poluan
2011-11-28 10:50   ` Neil Bothwick
2011-11-28 11:50     ` Pandu Poluan
2011-11-28 20:01       ` Mick
2011-11-29  1:35         ` Dale
2011-11-29  1:48           ` Neil Bothwick
2011-11-29  2:54             ` Pandu Poluan
2011-11-29  3:08               ` Dale
2011-11-29  7:16                 ` Dale
2011-11-29 11:41   ` Philip Webb [this message]
2011-11-30  6:43     ` Mick
2012-01-08  2:15       ` Philip Webb

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=20111129114157.GA3067@ca.inter.net \
    --to=purslow@ca.inter.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