>
> I've discovered the /etc/network/interfaces file -- I think I should
> fix things there.
>
>
yes, that is the correct location now
> Side Note:
>
> If /etc/init.d/network has been discontinued and the functionality
> moved to /etc/network/interface
cipher the setup of a box with stable r 6
installed. I need to add a correct route command. I assume I'd add it
to an init.d script.
grep route /etc/init.d/*
turns up nothing. I have a /etc/init.d/networking file (se list of all
init.d files below) but no /etc/init.d/network. The debian-g
Quoth kmself@ix.netcom.com,
> So -- should I configure /etc/network/interfaces, delete
> /etc/init.d/network, and pray everything works from
> /etc/init.d/networking?
I had a machine which somehow managed to get assigned a wrong default
gateway, which was causing me all sorts of
On Thu, Sep 21, 2000 at 03:01:05PM -0500, will trillich ([EMAIL PROTECTED])
wrote:
> On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote:
> > Could someone set me straight on the distinction between
> > /etc/init.d/network and the definition files und
On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote:
> Could someone set me straight on the distinction between
> /etc/init.d/network and the definition files under /etc/network:
> interfaces, options, and spoof-protect.
>
> We've got a balky server which do
Could someone set me straight on the distinction between
/etc/init.d/network and the definition files under /etc/network:
interfaces, options, and spoof-protect.
We've got a balky server which doesn't like coming on-line (and
occasionally likes going off) when it boots. I suspec
On Wed, Aug 09, 2000 at 11:18:06AM -0700, Bob Nielsen wrote:
> In potato's netbase, the network script has been replaced by
> networking. In an upgrade from slink the old script and its symlinks
> in /etc/rc*.d are retained, however. While this still works, is it
> likely to cause compatibility p
In potato's netbase, the network script has been replaced by
networking. In an upgrade from slink the old script and its symlinks
in /etc/rc*.d are retained, however. While this still works, is it
likely to cause compatibility problems in the future (woody and
beyond)?
Bob
--
Bob Nielsen, N7XY
Friday, May 19, 2000, 9:04:17 AM, A. wrote:
> Thanks to all for the MUA advice. I can see that I'm going to have to learn
> some new things (again), like MTAs. Linux has an amazing ability to laugh at
> your years as a computer professional make you feel like an idiot.
Actually I'd not do that
Thanks to all for the MUA advice. I can see that I'm going to have to learn
some new things (again), like MTAs. Linux has an amazing ability to laugh at
your years as a computer professional make you feel like an idiot.
But that's what's so [EMAIL PROTECTED] great about it.
==
[EMAIL PROTECTED] (Ethan Benson) writes:
[...]
>
> the only MUA for *nix that includes an MTA is bloatscape
> communicator.
Or you can look at xfmail. I've used it a long time (but now I'm using
gnus), and it's easy to setup. Inlucdes code for POP3 and IMAP, can
talk SMTP.
Burkhard
Actually it's not hard in netscape to perform filtering.
If whateverbitofmsg (eg to, sender etc) contains blah then move to
folder (or whatever action you want.)
Word wrap is in Edit/Preferences/Mail and Newsgroups/Messages/Message
Wrapping
Peter.
Mike Werner wrote:
> ... this is not true. Net
On Thu, May 18, 2000 at 08:04:26PM -0700, Karl M. Hegbloom wrote:
> I didn't like Netscrape for mail -
Nor do I, however ...
> it word wraps in the wrong places
> and to put mail in separate folders you've either got to monkey
> around with `procmail' or endlessly drag and drop from Inbox to
> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
Ethan> the only MUA for *nix that includes an MTA is bloatscape
Ethan> communicator.
It's better to install a MTA, like `exim', `postfix', or `sendmail'.
You can set it up so it doesn't accept connections from the net if
you li
> "A" == A Scott White <[EMAIL PROTECTED]> writes:
A> Ethan Benson wrote:
>> that is because outlook is broken and does not understand
>> RFC2015.
A> What Linux MUA should I use. I'd like one that has a complete feature set
A> and doesn't rely on X (I don't like X).
Gnus
On Thu, May 18, 2000 at 11:28:15AM -0500, A. Scott White wrote:
> Ethan Benson wrote:
> > that is because outlook is broken and does not understand
> > RFC2015.
>
> What Linux MUA should I use. I'd like one that has a complete feature set
> and doesn't rely on X (I don't like X).
if you don't lik
Ethan Benson wrote:
> that is because outlook is broken and does not understand
> RFC2015.
What Linux MUA should I use. I'd like one that has a complete feature set
and doesn't rely on X (I don't like X).
Also, most of the MUA's I've looked at don't clearly define a way to specify
checking a corp
On Wed, May 17, 2000 at 10:13:51PM -0700, Karl M. Hegbloom wrote:
> > "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>
> >> Pardon my ignorance. I had no idea that any mechanism for tracking
> threads
> >> existed other than the subject line. I'll keep that in mind.
> >> =20
> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>> Pardon my ignorance. I had no idea that any mechanism for tracking
threads
>> existed other than the subject line. I'll keep that in mind.
>> =20
>> Incidentally, how exactly does thread tracking work? I assume there is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
"A. Scott White" <[EMAIL PROTECTED]> writes:
> Incidentally, how exactly does thread tracking work? I assume there is a
> header of some kind. Maybe I'll hack it out. Interesting.
The In-Reply-To: header field has the message-id of the article y
On Wed, May 17, 2000 at 09:14:17AM -0500, A. Scott White wrote:
> Ethan:
> > to the original poster, reply & change subject != new message
> > ...
> > the former screws up threading in mailing list archives and in
> > MUAs such as mutt. please always create a new message and paste
> > the list add
Ethan:
> to the original poster, reply & change subject != new message
> ...
> the former screws up threading in mailing list archives and in
> MUAs such as mutt. please always create a new message and paste
> the list address in instead of using reply as a shortcut, or if
> you post often create
On Wed, May 17, 2000 at 01:38:19PM +1000, Matthew Dalton wrote:
>
>
> "A. Scott White" wrote:
> >
> > Can anyone tell me exactly what this line accomplishes:
> >
> > [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
>
> if the $GATEWAY variable has been set, run the command 'route a
, i.e., GATEWAY is set.
For details, see the manual pages for `[' (or `test'), `bash' (or your
particular shell) and `route'.
Andreas
> -Original Message-
> From: A. Scott White [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 17, 2000 11:05
> To: debian-user@l
"A. Scott White" wrote:
>
> Can anyone tell me exactly what this line accomplishes:
>
> [ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
if the $GATEWAY variable has been set, run the command 'route add
default gw ${GATEWAY} metric 1.
The [ and ] are synonyms for the 'test' progra
Can anyone tell me exactly what this line accomplishes:
[ "${GATEWAY}" ] && route add default gw ${GATEWAY} metric 1
I'm pretty sure it adds the default gateway setting for TCP/IP, but I don't
understand what it means, exactly. Could you explain:
1. The script syntax
2. the commands involved
I'd
I just installed a Debian 2.1 stable machine.
Since it has a Token Ring adapter I skipped the "configure the network"
step during installation.
I have recompiled a kernel 2.2.13 and have tr0.
My /etc/init.d is missing the network script ... is there a source from
which I could get it/create it ???
recently
updated IP Masq HOWTO found at the link below. It explains most
everything you need to know including what's needed for 2.2.X vs 2.0.X
kernels.
http://www.tor.shaw.wave.ca/~ambrose/ipmasq-HOWTO.html#toc3
As a simple example, here's my /etc/init.d/network for the gateway
machine
So that my computer will apply the ipchains commands, the ipforward
command in echo, the ifconfig, etc... at boot?
NatePuri
Certified Law Student
& Debian GNU/Linux Monk
McGeorge School of Law
[EMAIL PROTECTED]
http://ompages.com
In article <[EMAIL PROTECTED]>,
Peter S Galbraith <[EMAIL PROTECTED]> wrote:
>
>What package sets up /etc/init.d/network ?
Only a new installation configures it in the setup.
>After a new install on a laptop (for which I might have replied that there
>was no networ
What package sets up /etc/init.d/network ?
After a new install on a laptop (for which I might have replied that there
was no network for some configuration question), I'm left without even a
loopback configured. I could hack it in myself, but...
--
Peter Galbraith, research scie
On 13-Nov-97 [EMAIL PROTECTED] wrote:
>When the system boots /etc/init.d/network is run (I know this is true
>because I added some echo statements & watched the screen while it booted.)
>Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/
>network by
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Date: Thursday, November 13, 1997 7:19 AM
Subject: /etc/init.d/network
>Howdy all.
>
>I've got one machine that's really got me stumped. I've been with
On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote:
> When the system boots /etc/init.d/network is run (I know this is true
> because I added some echo statements & watched the screen while it booted.)
> Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/
>
>
> Well...
>
> in the /etc/init.d/network file is the following lines inserted?
>
> /sbin/ifconfig eth0 up
> /sbin/ifconfig eth0 host_name netmask 255.255.255.0
>
> Add the kernel routing table
>
> /sbin/route add -net 198.168.1.0 dev eth0
> /sbin/route ad
TEWAY and so on.
>
I did that. All of the variables are getting assigned properly.
> If you still need help I would be happy to take a look at your files.
>
I've found a kludge - added a sym-link from /etc/rc?.d/S99network to
/etc/init.d/network.
I'm going to try one of the other su
[EMAIL PROTECTED] wrote:
>
> Howdy all.
>
> I've had two network cards in this machine: first, an HP 100VG PCI and
> then an Eagle NE2000 ISA. Both exhibit the same problem. Which is...
>
> When the system boots /etc/init.d/network is run (I know this is true
&
>
> On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote:
>
> > I've had two network cards in this machine: first, an HP 100VG PCI and
> > then an Eagle NE2000 ISA. Both exhibit the same problem. Which is...
>
> Are you using them as modules or did you compile the drivers in?
> Just a random guess..
>
Did you try sticking an "ifconfig" in at the end of /etc/init.d/network to
see if the interface is up at that particular moment?
Maybe something else is shutting it down somewhere else ???
Later,
Kevin
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
..
When the system boots /etc/init.d/network is run (I know this is true
because I added some echo statements & watched the screen while it booted.)
Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/
network by hand afterwards, everything is fine. I've checked, doubl
40 matches
Mail list logo
