On 04/07/13 04:06, Stroller wrote:
On 6 April 2013, at 16:57, Alan Mackenzie wrote:
...
Please excuse me, I am running back and forth from the servers and
typing the error message here. Did our configuration get switched to
IP6? These are our DB servers and why me!!! Why ME!
No, it's not
On Sat, Apr 06, 2013 at 09:46:13PM +0700, Pandu Poluan wrote
> Ah, thanks for the clarification! :-)
>
> So, from now on, for safety I'm going to use a custom naming scheme,
> like lan[0-9]+ or wan[0-9]+ or wifi[0-9]+, anything that won't
> collide with kernel names of eth[0-9]+
>
> Now I only h
On 04/06/2013 11:06 PM, Grant Edwards wrote:
> On 2013-04-06, Pandu Poluan wrote:
>
>> Ahhh... I think now I understand...
>>
>> So. Here's my summarization of the situation:
>>
>> * The ethX naming can change, i.e., the interfaces can get out of order
>> * So, to fix this, udev decided to use th
On 04/06/2013 11:19 PM, Nick Khamis wrote:
> Hello Michael,
>
>>> Is it because you disabled udev's renaming entirely via the kernel
>>> command-line parameter? >> Because you've done some magic in
>>> /etc/udev/rules.d/?
>
> I did not change 70-something contents. I deleted it and let udev reg
Hello Michael,
>> Is it because you disabled udev's renaming entirely via the kernel
>> command-line parameter? >> Because you've done some magic in
>> /etc/udev/rules.d/?
I did not change 70-something contents. I deleted it and let udev regenerate it.
The name in rules.d is net=eth0 and net=e
The problem is that the definition of 'correctly' has changed. I don't
know if this is 'correctly' from your perspective of 'this is how I'm
used to seeing it' or 'correctly' from any of the three or more ways one
could use udev. The various defintions of 'correctly' may not overlap.
If they're sh
On 6 April 2013, at 16:57, Alan Mackenzie wrote:
> ...
>> Please excuse me, I am running back and forth from the servers and
>> typing the error message here. Did our configuration get switched to
>> IP6? These are our DB servers and why me!!! Why ME!
>
> No, it's not just you, it's happened
On 2013-04-06, Pandu Poluan wrote:
> Ahhh... I think now I understand...
>
> So. Here's my summarization of the situation:
>
> * The ethX naming can change, i.e., the interfaces can get out of order
> * So, to fix this, udev decided to use the physical attachment points of
> the NIC in driving a
Can't do nothing right now, no network connection... Don't feel like
burning a livecd and chrooting to jail...
N.
On 4/6/13, Randy Barlow wrote:
> On Sat, 6 Apr 2013 22:35:22 -0400
> Nick Khamis wrote:
>> As for /sbin/ip. I have no such command.
>
> I'd recommend installing and becoming familia
On Sat, 6 Apr 2013 22:35:22 -0400
Nick Khamis wrote:
> As for /sbin/ip. I have no such command.
I'd recommend installing and becoming familiar with the iproute2
package. I personally find the tools it delivers to be more intuitive
than the older tools, and I *think* they are considered to obsolot
ifconfig -a and ifconfig eth0 etc.. lists the interfaces correctly.
When trying to start net.eth0 the error that struck me as odd was:
/lib64/rc/net/wpa_supplicant.sh: line 68: _is_wireless: command not found
/etc/init.d/net.eth0: line 548: _exists: command not found
Sorry I can't paste stuff dir
It's probably not a module issue.
Are these interfaces supposed to be DHCP-configured, or are they
supposed to be statically and locally configured?
If they're supposed to be configured via DHCP, try "dhclient
$interface_name". If they're supposed to be statically configured, try
using ifconfig t
Sorry I did mean /sbin/ip... Long day. Regardless, /sbin/ipmaddr does
now show any ipv4 related material. Other than the network card
driver, what module should I ensure is loaded for ipv4 related stuff.
As for /etc/conf.d/net, net.eth0/eth1 these were untouched and still
point to eth0 and eth1.
A
/sbin/ip, not /etc/ip
Those inet6 addresses beginning with ff02 are link-local addresses.
Those are automatically configured on a link simply by the link being up.
Something is failing to configure your interfaces' ipv4 settings.
The culprit is almost certainly somewhere in one of these places,
Read the news entry - add the designated option to your grub kernel
line - reboot. That will be the simplest solution for now.
Long term, avoid udev upgrades like the plague and test them on
non-critical systems first. Strange that the reason I think us server
people were OK with udev being add
I do not have /etc/ip however, I do have /etc/ipmaddr show:
1: lo
inet6 ff02::1
2: sit0
inte6 ff02::1
3: eth0
link 33:33:00:00:00:01
inet6 ff02:1
4: eth1
link 33:33:00:00:00:01
inet6 ff02:1
Too much inte6 for my liking... Did I somehow get rid of ipv4?
N.
On 4/6/13, Michael
On 04/06/2013 08:53 PM, Nick Khamis wrote:
> I took a closer look at /etc/udev/70-something-rules-net and
> /sys/class/net/eth0/ and all the ATTR (i.e., address, type, dev_id)
> line up fine. I did not find a "name" file in /sys/class/net/eth0 however,
> name=eth0 in etc/udev/70-something-rules-net
The problem with eudev is that we are using the hardened profile and not sure
if it is part of our source tree. Right now, I just would like to
pinpoint this stubborn
little issue
I just wanted to mention that name did not change. ifconfig eth0 still pulls up
the interface, and same for ifconf
On 07/04/13 01:10, Alan Mackenzie wrote:
> 'Evening, Alan.
>
> On Sat, Apr 06, 2013 at 06:36:07PM +0200, Alan McKinnon wrote:
>> On 06/04/2013 17:57, Alan Mackenzie wrote:
Please excuse me, I am running back and forth from the servers and
> typing the error message here. Did our configura
I took a closer look at /etc/udev/70-something-rules-net and
/sys/class/net/eth0/ and all the ATTR (i.e., address, type, dev_id)
line up fine. I did not find a "name" file in /sys/class/net/eth0 however,
name=eth0 in etc/udev/70-something-rules-net.
Ifconfig alone returns nothing. Ifconfig eth0/1
On Thu, Apr 04, 2013 at 06:37:22PM +0200, J??rg Schaible wrote:
> Neil Bothwick wrote:
>
> > On Wed, 3 Apr 2013 16:38:28 + (UTC), Grant Edwards wrote:
> >
> >> > Have you read the news item?
> >>
> >> Yes. I found it rather confusing.
> >>
> >> It refers to a "new format" for rules, but th
In attempted to delete 70-something rules from /etc/udev/rules.d/ and
it was recreated on boot with the same content. I don't think the
device got renamed since "ifconfig eth0" shows the correct info.
Your help is greatly appreciated,
N.
On 4/6/13, Nick Khamis wrote:
> Well I looked into "/sys/
Well I looked into "/sys/class/net" as mentioned by Alan. In there I
see eth0/ eth1/ lo/ and sit0/. Not sure what too look for in (e.g.
eth0/). /sys/class/net/eth0/ifindex says 3. Other files look ok, for
example address (contains mac address if that has not changed...).
N.
On 4/6/13, Volker Arm
Am 06.04.2013 23:28, schrieb Volker Armin Hemmann:
> Am 06.04.2013 23:19, schrieb Nick Khamis:
>> Our net card was also build as a module Volker, did you include
>> your net driver for example in /etc/conf.d/modules?
>
> no
> I removed the 70-something rules, and did pretty much nothing else.
Am 06.04.2013 23:19, schrieb Nick Khamis:
> Our net card was also build as a module Volker, did you include
> your net driver for example in /etc/conf.d/modules?
no
I removed the 70-something rules, and did pretty much nothing else.
/etc/udev/rules.d/80-net-name-slot.rules just exists and is f
Our net card was also build as a module Volker, did you include
your net driver for example in /etc/conf.d/modules?
N.
On 4/6/13, Nick Khamis wrote:
> Oh dear what did I start!@!@! I'm sorry, I did not know this was a
> machine brewing. Don't follow the mailing list all that often. I
> updat
On 2013-04-06 1:50 PM, Jarry wrote:
Well, in my case 80-net-names-slot.rules was neither empty,
nor symlink to dev null, but FULL OF COMMENTS AND NOTING ELSE,
Well... even I know enough to reason that 'empty' in this context means
no UNcommented lines. Comments are just that, and if there are
Oh dear what did I start!@!@! I'm sorry, I did not know this was a
machine brewing. Don't follow the mailing list all that often. I
updated 3 x86 machines with no problem but the 64 just took a crap...
I agree! Should have read the notes.
N.
On 4/6/13, Jörg Schaible wrote:
> Volker Armin Hemmann
Volker Armin Hemmann wrote:
> Am 06.04.2013 21:33, schrieb Mick:
>> On Saturday 06 Apr 2013 20:03:15 Volker Armin Hemmann wrote:
>>> Am 06.04.2013 17:57, schrieb Alan Mackenzie:
Hi, Nick.
On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
> After updating our systems w
Am 06.04.2013 21:33, schrieb Mick:
> On Saturday 06 Apr 2013 20:03:15 Volker Armin Hemmann wrote:
>> Am 06.04.2013 17:57, schrieb Alan Mackenzie:
>>> Hi, Nick.
>>>
>>> On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
After updating our systems we lost network connectivity to the
>>
On Saturday 06 Apr 2013 18:49:31 meino.cra...@gmx.de wrote:
> meino.cra...@gmx.de [13-04-06 18:52]:
> > Randy Barlow [13-04-06 17:24]:
> > > On Sat, 2013-04-06 at 08:32 +0200, meino.cra...@gmx.de wrote:
> > > > How can I activate/use the additional functionality as reported by
> > > > the log fil
On Saturday 06 Apr 2013 20:03:15 Volker Armin Hemmann wrote:
> Am 06.04.2013 17:57, schrieb Alan Mackenzie:
> > Hi, Nick.
> >
> > On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
> >> After updating our systems we lost network connectivity to the
> >> servers. When trying to start net.
On Sat, 2013-04-06 at 19:49 +0200, meino.cra...@gmx.de wrote:
> For scrolling one has to move ONE finger on the right edge of the
> pad.
>
> And it scrolls!
>
> BUT unfortunately the scrollevents ALWAYS reach the taskbar and I am
> warped through my desktops regardless of the focus a certain wind
Jarry wrote:
> On 06-Apr-13 19:10, Alan Mackenzie wrote:
>>
>>> STOP SPREADING THIS FUD
>>
>>> It did not happen to pretty much everybody. It happened to people who
>>> blindly updated thignsd and walked away, who did not read the news
>>> announcement, who did not read the CLEARLY WORDED wiki art
On Sat, 2013-04-06 at 18:48 +0200, meino.cra...@gmx.de wrote:
> "One touch scrolling" and "2 fingers tap = scroll" is a
> contradiction, isn't it?
Haha, yeah it is confusing sounding. Perhaps one touch scrolling means
you can scroll by using a single finger on the right side of the pad? A
lot of t
Am 06.04.2013 17:57, schrieb Alan Mackenzie:
> Hi, Nick.
>
> On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
>> After updating our systems we lost network connectivity to the
>> servers. When trying to start net.eth0 we got the following message:
>> /ib64/rc/net/wpa_supplicant.sh: line
On 06-Apr-13 19:10, Alan Mackenzie wrote:
STOP SPREADING THIS FUD
It did not happen to pretty much everybody. It happened to people who
blindly updated thignsd and walked away, who did not read the news
announcement, who did not read the CLEARLY WORDED wiki article at
freedesktop.org or alte
meino.cra...@gmx.de [13-04-06 18:52]:
> Randy Barlow [13-04-06 17:24]:
> > On Sat, 2013-04-06 at 08:32 +0200, meino.cra...@gmx.de wrote:
> > > How can I activate/use the additional functionality as reported by the
> > > log file?
> >
> > I'm not familiar with that device, but I do have a suggest
On Saturday 06 Apr 2013 15:07:45 Peter Humphrey wrote:
> On Friday 05 April 2013 21:58:32 Peter Humphrey wrote:
>
> --->8
>
> > Why does emerge want to emerge chromium?
> >
> > Have I tripped over a line length limit? Have I got a circular
> > dependency? What else might be wrong? I can't see an
'Evening, Alan.
On Sat, Apr 06, 2013 at 06:36:07PM +0200, Alan McKinnon wrote:
> On 06/04/2013 17:57, Alan Mackenzie wrote:
> >> Please excuse me, I am running back and forth from the servers and
> >> > typing the error message here. Did our configuration get switched to
> >> > IP6? These are our
Randy Barlow [13-04-06 17:24]:
> On Sat, 2013-04-06 at 08:32 +0200, meino.cra...@gmx.de wrote:
> > How can I activate/use the additional functionality as reported by the
> > log file?
>
> I'm not familiar with that device, but I do have a suggestion: does it
> respond to multitouch gestures? For
On 06/04/2013 17:57, Alan Mackenzie wrote:
>> Please excuse me, I am running back and forth from the servers and
>> > typing the error message here. Did our configuration get switched to
>> > IP6? These are our DB servers and why me!!! Why ME!
> No, it's not just you, it's happened to pretty mu
Hi, Nick.
On Sat, Apr 06, 2013 at 10:51:42AM -0400, Nick Khamis wrote:
> After updating our systems we lost network connectivity to the
> servers. When trying to start net.eth0 we got the following message:
> /ib64/rc/net/wpa_supplicant.sh: line 68: _is wireless command not found
> /etc/init.d/ne
On Sat, 2013-04-06 at 08:32 +0200, meino.cra...@gmx.de wrote:
> How can I activate/use the additional functionality as reported by the
> log file?
I'm not familiar with that device, but I do have a suggestion: does it
respond to multitouch gestures? For example, with my trackpad on my
T530, I can
On Sat, Apr 06, 2013 at 07:11:46PM +0700, Pandu Poluan wrote:
>
> Ahhh... I think now I understand...
>
> So. Here's my summarization of the situation:
>
> * The ethX naming can change, i.e., the interfaces can get out of order
> * So, to fix this, udev decided to use the physical attachment poi
On 2013-04-06 10:40 AM, Neil Bothwick wrote:
On Sat, 06 Apr 2013 10:22:49 -0400, Tanstaafl wrote:
So, other than userland scripts that I created myself and know where
they live, where do I search for any files/scripts
created/generated/maintained by the system, for references to eth0/1 to
chan
After updating our systems we lost network connectivity to the
servers. When trying to start net.eth0 we got the following message:
/ib64/rc/net/wpa_supplicant.sh: line 68: _is wireless command not found
/etc/init.d/net.eth0: line 548: _exists command not found
Errror: Interface eth0 does not exi
On Apr 6, 2013 7:32 PM, wrote:
>
> On Sat, 6 Apr 2013 19:11:46 +0700
> Pandu Poluan wrote:
>
> > On Apr 6, 2013 3:44 PM, "Neil Bothwick" wrote:
> > >
> > > On Fri, 5 Apr 2013 21:14:39 -0400, Walter Dnes wrote:
> > >
> > > > * on a machine with multiple network cards *ALL USING DIFFERENT
> > > >
On Sat, 06 Apr 2013 10:22:49 -0400, Tanstaafl wrote:
> So, other than userland scripts that I created myself and know where
> they live, where do I search for any files/scripts
> created/generated/maintained by the system, for references to eth0/1 to
> change to net0/1? Is it just /etc/conf.d?
On 2013-04-05 4:11 PM, William Hubbs wrote:
On Fri, Apr 05, 2013 at 02:38:21PM -0500, Bruce Hill wrote:
Just dealing with one server and my Linux router, they've been updated to
sys-fs/udev-200 and are both still using the same
/etc/udev/rules.d/70-persistent-net.rules file they've had for over
On 2013-04-06 8:31 AM, kwk...@hkbn.net wrote:
Almost, except you should not specify a name that is also eth[0-9]+
(what you called 'traditional' name), since it can cause a race
condition where the kernel and udev fight for the name. While it used
to be the case (i.e.
Ok, thanks, I *think* I'
Hello Everyone,
On our test machines we are using and EOL Myrinet fibercahnnel card:
01:05.0 Network controller: MYRICOM Inc. Myrinet 2000 Scalable Cluster
Interconnect (rev 03)
The problem is that their open source driver only supports up to 2.6
kernels. And with us running gentoo 3.x kernel h
On Friday 05 April 2013 21:58:32 Peter Humphrey wrote:
--->8
> Why does emerge want to emerge chromium?
>
> Have I tripped over a line length limit? Have I got a circular
> dependency? What else might be wrong? I can't see anything relevant at
> BGO.
Well, what d'you know? Today it worked just
On Sat, 6 Apr 2013 19:11:46 +0700
Pandu Poluan wrote:
> On Apr 6, 2013 3:44 PM, "Neil Bothwick" wrote:
> >
> > On Fri, 5 Apr 2013 21:14:39 -0400, Walter Dnes wrote:
> >
> > > * on a machine with multiple network cards *ALL USING DIFFERENT
> > > DRIVERS*
> > > * drivers are built as modules, not
On Apr 6, 2013 3:44 PM, "Neil Bothwick" wrote:
>
> On Fri, 5 Apr 2013 21:14:39 -0400, Walter Dnes wrote:
>
> > * on a machine with multiple network cards *ALL USING DIFFERENT DRIVERS*
> > * drivers are built as modules, not built-in into the kernel
> > * is it possible to set things up so that the
On Saturday 06 Apr 2013 09:43:28 Neil Bothwick wrote:
> On Fri, 5 Apr 2013 21:14:39 -0400, Walter Dnes wrote:
> > * on a machine with multiple network cards *ALL USING DIFFERENT DRIVERS*
> > * drivers are built as modules, not built-in into the kernel
> > * is it possible to set things up so that t
On Fri, 5 Apr 2013 21:14:39 -0400, Walter Dnes wrote:
> * on a machine with multiple network cards *ALL USING DIFFERENT DRIVERS*
> * drivers are built as modules, not built-in into the kernel
> * is it possible to set things up so that the network driver modules do
> not load automatically at bo
57 matches
Mail list logo
