setup eth0 in TurboLinux

I have a old old old old copy of Turbo Linux 6.0 Server. It does not have a
graphical interface its just comand line driven. How can I setup eth0 ?




Tony

On Mon, 05 Mar 2007 06:44:51 +0000, Tony rearranged some electrons to
form:

> I have a old old old old copy of Turbo Linux 6.0 Server. It does not have a
> graphical interface its just comand line driven. How can I setup eth0 ?

man ifconfig

--
David M (dmacchiarolo)
http://home.triad.rr.com/redsled
T/S 53
sled351 Linux 2.4.18-14 has been up 7 days 11:15

On 03/05/2007 12:14 PM, Tony wrote:
> I have a old old old old copy of Turbo Linux 6.0 Server. It does not have a
> graphical interface its just comand line driven. How can I setup eth0 ?

ifconfig eth0 <ip.add.re.ss> netmask <net.ma.s.k> up
route add default gw <ip.address.of.gw>

--
Dr Balwinder S "bsd" Dheeman Registered Linux User: #229709
Anu'z Linux@HOME Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India Gentoo, Fedora, Knoppix/FreeBSD/XP
Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/

On Mon, 05 Mar 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <D%OGh.846$9g5.240@trnddc08>, Tony wrote:

>I have a old old old old copy of Turbo Linux 6.0 Server.

That's about seven years old. Unless you have a really really good reason
to be using something that ancient, get rid of it and get something modern
that is at least supported. TurboLinux was extremely slow with errata anyway.

>It does not have a graphical interface its just comand line driven.

Servers aren't meant to have lusers logging in and playing on the keyboard,
and thus don't need to be wasting CPU cycles drawing pictures. Most of
our servers don't even have video cards, never mind displays.

>How can I setup eth0 ?

TurboLinux was a Red Hat clone, so networking is set up in
/etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0. The
two files should look something like:

[keyhole ~]$ cat /etc/sysconfig/network
NETWORKING=yes
FORWARD_IPV4=false
HOSTNAME=keyhole.example.com <---- FULL hostname
GATEWAY= <--- gateway to the world - empty otherwise
GATEWAYDEV=
[keyhole ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.1.117
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
BOOTPROTO=none
[keyhole ~]$

The nameserver address goes in /etc/resolv.conf. The file /etc/hosts should
have full hostname and IP address in the form

[keyhole ~]$ cat /etc/hosts
192.168.1.117 keyhole.example.com keyhole
127.0.0.1 localhost
[keyhole ~]$

Old guy

Well me and mom goof around with a Cisco 2500 router when we have time.

I wanted a Linux box to stay connected to it so anyone can get to the router
through the LAN without having to actually plug directlly into it.

I someone gave me a GateWay g6-366c which came with Windows 98 has a 366mhz
processor (PII) and a 2GB HD so thought Turbo was the only thing that would
run on it but I got Fedora Core 1 to run on it so.

No more Turbo

On Tue, 06 Mar 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <wf2Hh.897$9g5.55@trnddc08>, Tony wrote:

>Well me and mom goof around with a Cisco 2500 router when we have time.
>
>I wanted a Linux box to stay connected to it so anyone can get to the
>router through the LAN without having to actually plug directlly into it.

OK - so any simple distribution that gives you a remote terminal session
will work. NORMALLY, I prefer to use the serial link for that, but an
IP connection would work as well assuming you configure for it.

>I someone gave me a GateWay g6-366c which came with Windows 98 has a
>366mhz processor (PII) and a 2GB HD so thought Turbo was the only thing
>that would run on it but I got Fedora Core 1 to run on it so.

Fedora Core 1 is certainly newer (came out November 2003, end of official
support was September 2004, and end of unofficial support was last July),
but it's not all that great. Fedora is a rapid turn-over type of general
distribution. The other "popular" distributions have a support life of
up to three years. See http://www.distrowatch.com for a considerable
number of choices.

Generally, what controls if a specific distribution can be used is the
amount of RAM installed. The modern distributions tend to have all the
bells and whistles and eat RAM like it's going out of style. As an
example, the "requirements" for some recent Red Hat distributions are
as follows:

Red Hat 5.2 Nov 1998 16 Megs _recommended_
Red Hat 7.3 May 2002 32 Mb for text, 128 Mb for GUI
Red Hat 9 Apr 2003 64 Mb for text, 128 Mb for GUI, 192 Mb
recommended
Fedora Core 2 May 2004 64 Mb for text, 192 Mb for GUI, 256 Mb
recommended
Fedora Core 6 Oct 2006 128 Mb for text, 192 Mb for GUI, 256 Mb
recommended

On the other hand, there _are_ distributions that need a hell of a lot
less RAM than that.

Old guy

Thank you that is very good info that i didnt kno.

Question:
Where is a good site in which I could copy scripts learn
them then play with them to make may own

On Thu, 08 Mar 2007, in the Usenet newsgroup comp.os.linux.networking, in
article <QQLHh.1972$3i.1001@trnddc01>, Tony wrote:

>Where is a good site in which I could copy scripts learn
>them then play with them to make may own

-rw-rw-r-- 1 gferg ldp 31540 Jul 27 2000 Bash-Prog-Intro-HOWTO

If you have a Linux box, that document should have been installed,
perhaps in /usr/doc/HOWTO/ or /usr/share/HOWTO/ or similar. There is
a much more extensive document on the Linux Documentation Project called
the 'Advanced Bash Scripting Guide'. http://tldp.org/guides.html

* Advanced Bash-Scripting Guide
version: 4.2
author: Mendel Cooper, <thegrendel(at)theriver.com>
last update: Dec 2006
available formats:
1. HTML (read online)
2. HTML (read online, single file, 1.7M)
3. HTML (tarred and gzipped package, 508K)
4. PDF (1.9M)
5. PostScript (1.1M)
6. text (482k)
7. PluckerDB (535k)

This document is both a tutorial and a reference on shell scripting
with Bash. It assumes no previous knowledge of scripting or
programming, but progresses rapidly toward an intermediate/advanced
level of instruction. The exercises and heavily-commented examples
invite active reader participation. Still, it is a work in progress.
The intention is to add much supplementary material in future updates
to this document, as it evolves into a comprehensive book that
matches or surpasses any of the shell scripting manuals in print.

Another place to learn is your own system. The boot scripts are written
by people who _really_ know shell scripts, and are _flaunting_ their
skills. It's probably not the place to _start_ to learn, but once you
have some fundamentals, it becomes an excellent tutorial.

Old guy