See comments below, interspersed.
At 06:08 PM 2/1/99 +0700, Shaggy Im-erbtham wrote [with deletions]:
>What would be the next step to get this client-server network functional?
Not to quibble or anything, but it really depends on what you wan the LAN to
*do* -- at some level, it sounds like the network is "functional" now. I
(and others) can help with more focused questions, as I have below, but
something this general is hard to respond to. Things you *might* want to do
include: run samba, run apache, configure and run X11, configure and run
Netscape, run IP masquerading, run NFS, run a print server, runa a proxy
server, run a backup system, do some security checking ... I've omitted a
lot of more specialized additions that are possible.
>/etc/host.conf
>order hosts, bind
Add the line "multi on" if you will be (eventually) using BIND.
>/etc/resolv.conf
>domain domain.name
>search domain.name
You don't have any nameservers listed here. You need some, if you are really
using BIND (it appears that you aren't yet, since every host is listed in
hosts.conf and, I infer from your use of 192.168 addresses, this is an
isolated LAN, not conected to the Internet.)
>I have some clues but don't understand them as follows:
>1. "add the following lines to /etc/rc.d/rc.sysinit"
> /sbin/ifconfig eth0 192.168.1.2 netmask 255.255.255.0
> /sbin/route add -net 192.168.1.0 eth0
>I don't have a rc.sysinit file, not with the installation. Should I build
>one with the above two lines?
rc.sysinit is a file used on Red Hat and other distributions. The equivalent
file in Slackware is /etc/rc.d/rc.inet1 . You probably have the needed lines
there since you are successfully telneting to the server .... a normal
Slackware setup will do this configuration for you.
>2. "restart Samba by using there two commands"
> /etc/init.d/smb stop
>/etc/init.d/smb start
>I don't have neither the init.d sub-directory nor the smb file, not from
>the installation. It could mkdir init.d but what about the smb file?
This is, again, a difference between Slackware and other distributions such
as Red Hat. Unfortunately, since I don't use Samba here, I don't know the
Slackware equivalent for this one ... but I do know you need information
specific to Slackware, not generic to Linux (that is, there is no
distribution-independent answer to this one).
>Another question is, once a Linux box is server, could it still perform as
>a workstation? That is, be able to print and play sounds by itself. I am
>aware that it could be print server, fax server and Internet server (latter
>by IP Masquerading) for its clients.
Yes, subject to memory, CPU speed, and disk constraints (for example,
performance may suffer if you are doing CPU-intensive tasks or causing the
system to page to the swap drive a lot). While these constraints apply in a
server-only situation as well, workstation uses -- e.g., running X11 and
Netscape -- can make it happen fast, especially on such a minimal system as
the one you are experimenting with.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
