Le Sun, 28 Jan 2007 00:51:57 -0500,
James Lockie [EMAIL PROTECTED] a écrit :
Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I
found that net.eth0 was grabbing my firewire port (ieee1394) and I needed
to create net.eth2 for my NIC as net.eth1
Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found that net.eth0 was
grabbing my firewire port (ieee1394) and I needed to create net.eth2 for my NIC as net.eth1 was
being assigned to my wireless. My problem is that although rc-update show
On Wed, 2007-01-10 at 20:39 +, Mick wrote:
On Tuesday 09 January 2007 23:12, Iain Buchanan wrote:
On Tue, 2007-01-09 at 19:56 +, Mick wrote:
On Tuesday 09 January 2007 01:13, Iain Buchanan wrote:
hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet
the bluetooth
On Tuesday 09 January 2007 23:12, Iain Buchanan wrote:
On Tue, 2007-01-09 at 19:56 +, Mick wrote:
On Tuesday 09 January 2007 01:13, Iain Buchanan wrote:
hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet
the bluetooth service is still started automatically (not in any
On Tuesday 09 January 2007 01:13, Iain Buchanan wrote:
hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the
bluetooth service is still started automatically (not in any runlevel).
thoughts? thanks,
Could it be that bluetooth is the wrong name for it? Is it identified as
On Tue, 2007-01-09 at 19:56 +, Mick wrote:
On Tuesday 09 January 2007 01:13, Iain Buchanan wrote:
hmm, now I look at it, I have RC_PLUG_SERVICES=!bluetooth, and yet the
bluetooth service is still started automatically (not in any runlevel).
thoughts? thanks,
Could it be that
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I found
that net.eth0 was grabbing my firewire port (ieee1394) and I needed to create
net.eth2 for my NIC as net.eth1 was being assigned to my wireless. My problem
is that although rc-update show indicates all my interfaces
On Tue, 9 Jan 2007 10:42:37 +1000, Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I
found that net.eth0 was grabbing my firewire port (ieee1394) and I
needed to create net.eth2 for my NIC as net.eth1 was being assigned to
my wireless. My problem is
On Tue, 2007-01-09 at 10:42 +1000, Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I
found that net.eth0 was grabbing my firewire port (ieee1394) and I
needed to create net.eth2 for my NIC as net.eth1 was being assigned to
my wireless. My problem is
On Tue, 2007-01-09 at 01:04 +, Neil Bothwick wrote:
On Tue, 9 Jan 2007 10:42:37 +1000, Richard Watson wrote:
Hi, I recently upgraded my system with emerge -uDN world. Afterwards I
found that net.eth0 was grabbing my firewire port (ieee1394) and I
needed to create net.eth2 for my NIC
10 matches
Mail list logo
