Hello,
On Sat, Mar 26, 2022 at 08:48:35AM -0400, Greg Wooledge wrote:
> Maybe I should remove the trinity-3c-app-mailcom block, since it
> no longer seems to be doing anything helpful...?
Looking at my mailbox I've got hundreds of hits matching that, from
many differently apparently-real people a
On Sat, 26 Mar 2022 at 23:48, Greg Wooledge wrote:
> On Fri, Mar 25, 2022 at 11:43:36PM -0500, David Wright wrote:
> > On Fri 25 Mar 2022 at 07:31:14 (+0100), Stella Ashburne wrote:
> If "Stella" is
> a real person who has been blocked as collateral damage, well, that's
> unfortunate.
You can ju
On Fri, Mar 25, 2022 at 11:43:36PM -0500, David Wright wrote:
> In passing, I'm mystified by your quoting mechanism thinking
> it appropriate to display my time header in Chinese time:
> $ TZ='Asia/Shanghai' date --date='Thu, 24 Mar 2022 21:09:41 -0500'
> Fri Mar 25 10:09:41 CST 2022
> $
>
> On F
On 2022-03-26, David Wright wrote:
>>
>> When the /etc/network/interfaces file has the line
>>
>> source-directory /etc/network/interfaces.d/*
>
> An eccentric choice. But no elaboration, opinion, or reasoning.
>
>> Best wishes.
>
> To you too.
-directory /etc/network/interfaces.d
> >
> > Without knowing the reasoning behind your statement, there's
> > not a lot more help I can give.
> >
>
> My distro is Debian 11
>
> Attempt #1
>
> When the /etc/network/interfaces file has the line
>
Mon cheri
> Sent: Friday, March 25, 2022 at 10:09 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> Please elabora
t; And in some situations, it's connected to a smartphone via USB tethering.
> > > And when I'm in the office, I may connect it to a LAN cable.
> > >
> > > Below are the contents of my /etc/network/interfaces file:
> > >
> > > # This file describes t
Mon cheri
> Sent: Sunday, March 20, 2022 at 10:31 PM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> On Sat 19 Mar 2
On Wed 23 Mar 2022 at 13:35:13 (+0100), Stella Ashburne wrote:
> From: "David Wright"
> > >
> > > source /etc/network/interfaces.d/*
> >
> > I would change this line to
> >
> > source-directory /etc/network/interfaces.d
> >
> > (which was the default on new buster installations).
> >
> Am I right
debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
> >
> > source /etc/network/interfaces.d/*
>
> I would change this line to
>
> source-directory /etc/network/interfaces
t; > And in some situations, it's connected to a smartphone via USB tethering.
> > > And when I'm in the office, I may connect it to a LAN cable.
> > >
> > > Below are the contents of my /etc/network/interfaces file:
> > >
> > > # This file desc
ice, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
I would change this line
cable.
>
> Below are the contents of my /etc/network/interfaces file:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
I would change
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten foot
pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at all .. but Linux distros think it
is some sort of
On 2022-03-19 13:19, Eduardo M KALINOWSKI wrote:
On 19/03/2022 09:06, Stella Ashburne wrote:
No thank you. I won't touch NetworkManager or its variants with a ten
foot pole. Why?
Reason #1
[quote] I am sorry but we do not support NetworkManager.
I would go so far as to say do not use it at a
Mon cheri
Thanks for your reply.
> Sent: Saturday, March 19, 2022 at 3:17 PM
> From: "Tim Woodall"
> To: "Stella Ashburne"
> Cc: "debian-user mailing list"
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> wa
Mon cheri
> Sent: Saturday, March 19, 2022 at 7:13 PM
> From: "Eduardo M KALINOWSKI"
> To: debian-user@lists.debian.org
> Subject: Re: Under each of these scenarios, what is the neatest and simplest
> way to manipulate the /etc/network/interfaces file?
>
>
> Th
of my /etc/network/interfaces file:
[...]
1. At the moment, if I wish to change to using a mobile hotspot from USB
tethering, I'll edit the /etc/network/interfaces file, uncomment the applicable
lines under #The primary network interface for wireless connections and place a
# in front of all
. And when
I'm in the office, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interf
Hi
There are instances in which my machine is connected to a mobile hotspot. And
in some situations, it's connected to a smartphone via USB tethering. And when
I'm in the office, I may connect it to a LAN cable.
Below are the contents of my /etc/network/interfaces file:
# This file
On 12/21/06, Joey Hess <[EMAIL PROTECTED]> wrote:
stevendemetrius wrote:
> The issue is that "allow-hotplug eth0" does *not* work while "auto eth0"
> does work! If "allow-hotplug" is used then "dhclient" has to be run
> manually in order for eth0 to get its IP related settings.
I've investigate
stevendemetrius wrote:
> The issue is that "allow-hotplug eth0" does *not* work while "auto eth0"
> does work! If "allow-hotplug" is used then "dhclient" has to be run
> manually in order for eth0 to get its IP related settings.
I've investigated this for a few hours today, and if you have any
s
On Sun, Dec 17, 2006 at 11:51:40AM -0900, Greg Madden wrote:
> On Sun, 17 Dec 2006 10:56:23 +0200
> [EMAIL PROTECTED] (Andrei Popescu) wrote:
>
> > On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> > > For several installs over a period of time for Etch, using a
> > > net-install cd.
* stevendemetrius <[EMAIL PROTECTED]> [2006 Dec 18 03:14 -0600]:
>
> It seems the point is being missed here.
>
> The issue is that "allow-hotplug eth0" does *not* work while "auto eth0"
> does work! If "allow-hotplug" is used then "dhclient" has to be run
> manually in order for eth0 to get it
It seems the point is being missed here.
The issue is that "allow-hotplug eth0" does *not* work while "auto eth0" does work! If
"allow-hotplug" is used then "dhclient" has to be run manually in order for eth0 to get its IP
related settings.
This seems to be a bug. Greg since you started this
On Sat, 16 Dec 2006 17:17:39 -0900
Greg Madden <[EMAIL PROTECTED]> wrote:
> For several installs over a period of time for Etch, using a
> net-install cd. The ~/network/interfaces file uses the line
> "allow-hotplug eth0". This has not worked on my boxes, I have to type
> 'dhclient eth0' to connec
On Sun, 17 Dec 2006 10:56:23 +0200
[EMAIL PROTECTED] (Andrei Popescu) wrote:
> On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> > For several installs over a period of time for Etch, using a
> > net-install cd. The ~/network/interfaces file uses the line
> > "allow-hotplug eth0". Thi
On Sat, Dec 16, 2006 at 05:17:39PM -0900, Greg Madden wrote:
> For several installs over a period of time for Etch, using a net-install
> cd. The ~/network/interfaces file uses the line "allow-hotplug eth0".
> This has not worked on my boxes, I have to type 'dhclient eth0' to
> connect. I use an Ip
2006/12/17, stevendemetrius <[EMAIL PROTECTED]>:
Anyone, any ideas?
PCMCIA optimisation?
I've noticed the same thing and I've done a similar change in the
/etc/network/interfaces file.
change:
"allow-hotplug eth0"
to:
"auto eth0"
I'm not sure what is causing the problem and don't know which package to file a
bug against.
I'm assuming
For several installs over a period of time for Etch, using a net-install
cd. The ~/network/interfaces file uses the line "allow-hotplug eth0".
This has not worked on my boxes, I have to type 'dhclient eth0' to
connect. I use an Ipcop firewall, dhcp, hooked up to a switch. I comment
out the 'hotplug
On Thu, Feb 05, 2004 at 02:39:34AM +, Joseph Jones said
> Could someone just check over this for me please? I'm having no end of
> trouble trying to get my nforce's onboard interface working.
>
> If this isn't the problem, could someone suggest what is? The forcedeth
> patch installed cleanl
On Fri, Feb 06, 2004 at 09:52:36AM -0600, Kent West said
> Joseph Jones wrote:
> >Output follows (hope you don't mind me cc'ing to you and the list):
> >
> >00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet
> >Controller (rev c2)
> >Subsystem: Asustek Computer, Inc.: Unknown devi
Kent West wrote:
Joseph Jones wrote:
Adam Aube wrote:
On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote:
I try to get [the network] working by starting up my PC. I was under
the
impression that that was all was requied after installing the kernel
(it's all my Via Rhine based card needed
Joseph Jones wrote:
I'm using a custom 2.4.22 kernel with the forcedeth (the reverse
engineered driver for my onboard adaptor) patch applied.
I'm unfamiliar with this option, but I do recall seeing something about
this option in the past couple of days (maybe it was even part of this
thread)
Joseph Jones wrote:
Adam Aube wrote:
On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote:
I try to get [the network] working by starting up my PC. I was under
the
impression that that was all was requied after installing the kernel
(it's all my Via Rhine based card needed).
Upon bootup,
Adam Aube wrote:
On Thursday 05 February 2004 12:06 pm, Joseph Jones wrote:
Adam Aube wrote:
Your interfaces file looks fine. Exactly what happens when you try to
get your network interface working, and how do you try to do it?
I try to get it working by starting up my PC. I was under the
impres
Kent West wrote:
Joseph Jones wrote:
On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
Could someone just check over this for me please? I'm having no end of
trouble trying to get my nforce's onboard interface working.
I try to get it working by starting up my PC. I was under the
i
On 2004-02-05, Joseph Jones penned:
> Adam Aube wrote:
>> On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
>>
>>>Could someone just check over this for me please? I'm having no end
>>>of trouble trying to get my nforce's onboard interface working.
>>>
>>>If this isn't the problem, could
Joseph Jones wrote:
On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
Could someone just check over this for me please? I'm having no end of
trouble trying to get my nforce's onboard interface working.
I try to get it working by starting up my PC. I was under the
impression that tha
On Thu, 2004-02-05 at 12:08, Joseph Jones wrote:
> Adam Aube wrote:
> > On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
> >
> >>Could someone just check over this for me please? I'm having no end of
> >>trouble trying to get my nforce's onboard interface working.
> >>
> >>If this isn't
Adam Aube wrote:
On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
Could someone just check over this for me please? I'm having no end of
trouble trying to get my nforce's onboard interface working.
If this isn't the problem, could someone suggest what is? The forcedeth
patch installed c
Joseph Jones wrote:
Could someone just check over this for me please? I'm having no end of
trouble trying to get my nforce's onboard interface working.
If this isn't the problem, could someone suggest what is? The forcedeth
patch installed cleanly, and appears to be trying to work.
To bolster yo
On Wednesday 04 February 2004 09:39 pm, Joseph Jones wrote:
> Could someone just check over this for me please? I'm having no end of
> trouble trying to get my nforce's onboard interface working.
>
> If this isn't the problem, could someone suggest what is? The forcedeth
> patch installed cleanly,
Could someone just check over this for me please? I'm having no end of
trouble trying to get my nforce's onboard interface working.
If this isn't the problem, could someone suggest what is? The forcedeth
patch installed cleanly, and appears to be trying to work.
Many thanks
Joe.
/etc/network/
tart on boot up, the "iface" configures "eth1"
as a "inet" (TCP/IP) "static" address. Then of course the next lines are
what that address should be.
At 12:38 PM 13/03/2001, Bill Fowler wrote:
Hello,
I want to make my network config permanent with the
On Tue, 13 Mar 2001 11:38:43 -0700
Bill Fowler <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I want to make my network config permanent with the /etc/network/interfaces
> file in Debian 2.2. The file is as follows:
>
> # /etc/network/interfaces -- configuration fi
Hello,
I want to make my network config permanent with the /etc/network/interfaces
file in Debian 2.2. The file is as follows:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
#
# Configure loopback interface
ifconfig lo 127.0.0.1
# Configure ethernet interface
IPADDR
48 matches
Mail list logo
