From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-146681-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 1DC311381F3
for <garchives@archives.gentoo.org>; Mon, 8 Apr 2013 18:37:07 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id B924BE0BAD;
Mon, 8 Apr 2013 18:36:57 +0000 (UTC)
Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 7DE9EE0BA7
for <gentoo-user@lists.gentoo.org>; Mon, 8 Apr 2013 18:36:56 +0000 (UTC)
Received: from mail-ve0-f174.google.com ([209.85.128.174]:63302)
by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128)
(Exim 4.80)
(envelope-from <pandu@poluan.info>)
id 1UPGw6-001GKL-2B
for gentoo-user@lists.gentoo.org; Tue, 09 Apr 2013 01:36:58 +0700
Received: by mail-ve0-f174.google.com with SMTP id jz10so5718238veb.33
for <gentoo-user@lists.gentoo.org>; Mon, 08 Apr 2013 11:36:53 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.221.4.131 with SMTP id oc3mr3350343vcb.46.1365446213319;
Mon, 08 Apr 2013 11:36:53 -0700 (PDT)
Received: by 10.220.67.3 with HTTP; Mon, 8 Apr 2013 11:36:53 -0700 (PDT)
Received: by 10.220.67.3 with HTTP; Mon, 8 Apr 2013 11:36:53 -0700 (PDT)
In-Reply-To: <20130408161657.GP18234@server>
References: <5160607B.6000601@gmail.com>
<kjps0v$l37$1@ger.gmane.org>
<5789717fb32d4039ac67d0fe143ac1b6@127.0.0.1>
<CAGWRaZb7z1DCaJSi2its=6SxqAQNLp39nuQamrjweMBVb1ertg@mail.gmail.com>
<20130407151559.37e3d5b6@hactar.digimed.co.uk>
<CAGWRaZbH3A_+YkfRGu5DsyY-S0TRUxPN6shZAd_QE9AQ0dPVPw@mail.gmail.com>
<CAGWRaZbm9rDf1RDbz5cbx3y0CjdkgKvb1q0-ntpUX8QKVtBGjw@mail.gmail.com>
<516181C2.2060104@gmail.com>
<CAGWRaZZx+Ks2r095fy13Ecp7N8KW2heP6QCkiMmjrJzvqw8wEA@mail.gmail.com>
<5161AFFF.1020102@hadt.biz>
<20130408161657.GP18234@server>
Date: Tue, 9 Apr 2013 01:36:53 +0700
Message-ID: <CAA2qdGXq0iP+=iU6vKDGyFYNTA9gXkC2RrPMP4rz-Vv-kMW2ng@mail.gmail.com>
Subject: Re: [gentoo-user] Re: Eth0 interface not found - udev that little slut!!!!!
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=089e01293fe281449304d9ddb815
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com
X-AntiAbuse: Original Domain - lists.gentoo.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - poluan.info
X-Get-Message-Sender-Via: svr-us4.tirtonadi.com: authenticated_id: rileyer+pandu.poluan.info/only user confirmed/virtual account not confirmed
X-Archives-Salt: a01bec13-3db3-445b-838d-cef23a454b1b
X-Archives-Hash: efa5b6a9e638c7dd48e4a0c9a0d26925
--089e01293fe281449304d9ddb815
Content-Type: text/plain; charset=UTF-8
On Apr 8, 2013 11:17 PM, "Bruce Hill" <daddy@happypenguincomputers.com>
wrote:
>
> On Sun, Apr 07, 2013 at 07:42:23PM +0200, Michael Hampicke wrote:
> >
> > Mike is right, if it's not a dep of another ebuild, you don't need
> > wpa_supplicant. I just upgraded udev to 200 on the last remote box
> > (which is always a bit of a thrill after typing reboot <return> :-) ).
> > As expected, eth0 came up, everything works fine, wpa_supplicant is not
> > installed.
>
> Don't know what you guys do for rebooting a headless server blindly like
this,
> nor if it would work for the udev/NIC situation. But fwiw, what I've
always
> done for new kernels is:
>
> mingdao@server ~ $ egrep -v "(^#|^ *$)" /etc/lilo.conf
> compact
> lba32
> default = Gentoo-def
> boot = /dev/md0
> raid-extra-boot = mbr-only
> map = /boot/.map
> install = /boot/boot-menu.b # Note that for lilo-22.5.5 or later you
> # do not need boot-{text,menu,bmp}.b in
> # /boot, as they are linked into the lilo
> # binary.
> menu-scheme=Wb
> prompt
> timeout=50
> append="panic=10 nomce dolvm domdadm rootfstype=xfs"
> image = /boot/vmlinuz
> root = /dev/md0
> label = Gentoo
> read-only # Partitions should be mounted read-only for checking
> image = /boot/vmlinuz.old
> root = /dev/md0
> label = Gentoo-def
> read-only # Partitions should be mounted read-only for checking
>
> Then issue "lilo -R Gentoo" or whatever the label of your new kernel, and
if
> it boots, you're okay. If not, after 10 seconds of panic, it automatically
> reboots back into the default kernel and you can check logs to see what
you've
> broken. (panic=10 append statement and default = Gentoo-def) After you
know
> the new kernel works, comment the default line. (NB: You can name them
> differently, etc. It just helps to know before you reboot that if you
panic,
> the machine will boot back into the known, good, kernel.)
>
> Granted, this might not help with the udev/NIC situation, but it's saved
me
> from a few PEBKAC situations, as well as new kernel changes I'd not
learned
> until the reboot.
Personally, I always try to install *any* Linux server on top of Xen (in my
case, XenServer). That way, I got a remote "console" always.
Rgds,
--
--089e01293fe281449304d9ddb815
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p><br>
On Apr 8, 2013 11:17 PM, "Bruce Hill" <<a href=3D"mailto:daddy=
@happypenguincomputers.com">daddy@happypenguincomputers.com</a>> wrote:<=
br>
><br>
> On Sun, Apr 07, 2013 at 07:42:23PM +0200, Michael Hampicke wrote:<br>
> ><br>
> > Mike is right, if it's not a dep of another ebuild, you don&#=
39;t need<br>
> > wpa_supplicant. I just upgraded udev to 200 on the last remote bo=
x<br>
> > (which is always a bit of a thrill after typing reboot <return=
> :-) ).<br>
> > As expected, eth0 came up, everything works fine, wpa_supplicant =
is not<br>
> > installed.<br>
><br>
> Don't know what you guys do for rebooting a headless server blindl=
y like this,<br>
> nor if it would work for the udev/NIC situation. But fwiw, what I'=
ve always<br>
> done for new kernels is:<br>
><br>
> mingdao@server ~ $ egrep -v "(^#|^ *$)" /etc/lilo.conf<br>
> compact<br>
> lba32<br>
> default =3D Gentoo-def<br>
> boot =3D /dev/md0<br>
> raid-extra-boot =3D mbr-only<br>
> map =3D /boot/.map<br>
> install =3D /boot/boot-menu.b =C2=A0 # Note that for lilo-22.5.5 or la=
ter you<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # do not need boot-{text,menu,bmp}.b in<=
br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # /boot, as they are linked into the lil=
o<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # binary.<br>
> menu-scheme=3DWb<br>
> prompt<br>
> timeout=3D50<br>
> append=3D"panic=3D10 nomce dolvm domdadm rootfstype=3Dxfs"<b=
r>
> image =3D /boot/vmlinuz<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 root =3D /dev/md0<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 label =3D Gentoo<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 read-only =C2=A0# Partitions should be mou=
nted read-only for checking<br>
> image =3D /boot/vmlinuz.old<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 root =3D /dev/md0<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 label =3D Gentoo-def<br>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 read-only =C2=A0# Partitions should be mou=
nted read-only for checking<br>
><br>
> Then issue "lilo -R Gentoo" or whatever the label of your ne=
w kernel, and if<br>
> it boots, you're okay. If not, after 10 seconds of panic, it autom=
atically<br>
> reboots back into the default kernel and you can check logs to see wha=
t you've<br>
> broken. (panic=3D10 append statement and default =3D Gentoo-def) After=
you know<br>
> the new kernel works, comment the default line. (NB: You can name them=
<br>
> differently, etc. It just helps to know before you reboot that if you =
panic,<br>
> the machine will boot back into the known, good, kernel.)<br>
><br>
> Granted, this might not help with the udev/NIC situation, but it's=
saved me<br>
> from a few PEBKAC situations, as well as new kernel changes I'd no=
t learned<br>
> until the reboot.</p>
<p>Personally, I always try to install *any* Linux server on top of Xen (in=
my case, XenServer). That way, I got a remote "console" always.<=
/p>
<p>Rgds,<br>
--<br>
</p>
--089e01293fe281449304d9ddb815--