Linux-Networking Digest #819, Volume #9           Fri, 8 Jan 99 20:13:41 EST

Contents:
  Re: Have a small problem yet an important one (root)
  Re: SEE YA' LATER SUCKERS !!! HAHAHAHA !!! ("DAYPASS")
  Re: Multiple NIC Cards.. HELP!! ("PDG")
  Possible Red Hat pppd routing poblem ("James  Higgins")
  Utterly clueless about PPP ("Juergen Fiedler")
  Re: need paging software for linux (David Barnes)
  Re: Telneting as "root" (Ingo Wichmann)
  Re: Telneting as "root" (Ingo Wichmann)
  Re: Telneting as "root" (Ingo Wichmann)
  Re: Telneting as "root" (Ingo Wichmann)
  Re: sharing a cablemodem (with 1 NIC?) (root)
  Re: i need help networking a win98 to redhat 5.1 using the recomended  (Dale Miracle)
  Re: Utterly clueless about PPP (Sydney Weidman)
  Re: Possible Red Hat pppd routing poblem (Doug Bryant)
  Re: Can't reboot at root from "xdm" (DonJr)
  Help! Ethernet problem!!! ("Kyle J. Lee")
  Modules for Dec 21140 NICs ("endlessknot")
  telnet problem: connects than diconnects before login. PLEASE HELP ! (Luigi Fabbro)
  Re: No FTP Under ipfwadm (Additional Info) (John Beppu)

----------------------------------------------------------------------------

From: root <[EMAIL PROTECTED]>
Subject: Re: Have a small problem yet an important one
Date: 08 Jan 1999 23:24:49 +0100

[EMAIL PROTECTED] writes:

> Hi! and a very happy new year. I'm from Chandigarh,India. 
                
                Greetings from Greece !

> I'm working on
> RedHat 5.0 (kernel 2.0.35) and have got quite busy trying to configure it for
> my LAN. I'm using the default kernel shipped with RedHat and have not
> recompiled it. I'm using a Compex RL2000 10Mbps ethernet card. The card has
> been registered in my /proc/pci as having IRQ=12, I/O 0xe400 

                I have exactly the same card, IRQ=10, IO 0xd400

> and since is the
> only card so is identified as eth0. After it got detected in /proc/pci i used
> "linux ether=12,0xe400, eth0" at the LILO BOOT prompt since it was not
> getting detected at boot. 

                No need to do this. You SHOULD be using the ne2k-pci.o (module) by 
adding
the line to your /etc/conf.modules :
alias eth0 ne2k-pci

HOWEVER :

                As I recall you may (or may not !) have a problem with 2.0.35 and 
especially
the ne2k-pci version that came with it, detecting the RL2000.
                To check it out do the following :
                Without having you NIC recognised during boottime, go to 
/lib/modules/2.0.35
(or /lib/modules/preferred whatever there is) and find the ne2k-pci.o module (it should
be in the ./net).
                Then issue : insmod 8390 ; insmod ne2k-pci

                If it finds the ethercard all ok, just add the line I told you in 
/etc/conf.modules.
                If not, you need to upgrade your kernel and recompile it OR get an 
updated
ne2k-pci.c and compile it. It's in  /usr/src/linux/drivers/net/ne2k-pci.c.

                However if the ne2k-pci doesn't find your ethercard, upgrading your 
kernel
is highly recommended (you will have added benefits from this, apart from your NIC
problem).

If you have more questions don't hesitate to use my email.

========================
p94003@rainbow.**NOSPAM**.cs.unipi.gr
remove **NOSPAM** to answer !



------------------------------

From: "DAYPASS" <[EMAIL PROTECTED]>
Crossposted-To: 
linux.redhat.install,comp.os.linux.questions,comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: SEE YA' LATER SUCKERS !!! HAHAHAHA !!!
Date: Fri, 8 Jan 1999 17:37:09 -0500

My dad taught me how to run programs in DOS..


Mitchell Ullman wrote in message ...
>Well, sounds like to me that this guy wanted to be spoon-fed.  I bet this
>guy had is daddy teach him how to run programs in DOS!
>
>
>On Thu, 7 Jan 1999, Iain wrote:
>> >
>> > FTP INSTALL FINALLY WORKED THANKS TO CROSSBONES !!!
>> > Well, except for me and Crossbones, all of you are none more than
>> > f****** idiots. But it's been fun insulting everyone one of you, who
>> > were against me, in this newsgroup. In fact, when you look at the
>> > thread(s), it probably reminds you of Jerry Springer. Now I did not ask
>> > for this, you all forced me into it, so don't even f****** blame me !!!
>> > Anyway, it was fun fighting like in the Springer shows but I gotta go
>> > now, so
>> > GOOD-BYE TO ALL YOU MENTALLY RETARDED IDIOTS OUT THERE WHO CAN'T BE
HELPFUL THE WAY I WANT IT !!!
>>
>>
>



------------------------------

From: "PDG" <[EMAIL PROTECTED]>
Crossposted-To: 
alt.linux,alt.os.linux,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.misc,linux.redhat.install,linux.redhat.misc
Subject: Re: Multiple NIC Cards.. HELP!!
Date: Thu, 7 Jan 1999 22:09:27 -0500

if you plan on using two nic cards of the same type, you need to re-compile
your kernel to use the driver directly IN the kernel, not as a module

--
PDG--"We bring bad things to life"

For PGP Public key-- http://webcrush.com/pgp.htm




------------------------------

From: "James  Higgins" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.ppp
Subject: Possible Red Hat pppd routing poblem
Date: Thu, 7 Jan 1999 22:43:30 -0500

I just installed Red Hat 5.2 and set up a ppp link using linuxconf.  My ISP,
Prodigy Internet, uses PAP authentication.  I have successfully configured
this before in both Linux and FreeBSD.

The session will connect successfully and I see the following in
/var/log/messages:

<snip from /var/log/messages>
Jan  7 21:47:49 localhost chat[1247]: ATDT9757702^M^M
Jan  7 21:47:49 localhost chat[1247]: CONNECT
Jan  7 21:47:49 localhost chat[1247]:  -- got it
Jan  7 21:47:49 localhost chat[1247]: send (^M)
Jan  7 21:47:49 localhost chat[1247]: timeout set to 5 seconds
Jan  7 21:47:49 localhost chat[1247]: expect (~)
Jan  7 21:47:49 localhost chat[1247]:  49333/ARQ^M
Jan  7 21:47:54 localhost chat[1247]: alarm
Jan  7 21:47:54 localhost chat[1247]: send (^M)
Jan  7 21:47:54 localhost chat[1247]: send (^M)
Jan  7 21:47:54 localhost pppd[1245]: Serial connection established.
Jan  7 21:47:55 localhost kernel: PPP: version 2.2.0 (dynamic channel
allocation)
Jan  7 21:47:55 localhost kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
Jan  7 21:47:55 localhost kernel: PPP line discipline registered.
Jan  7 21:47:55 localhost kernel: registered device ppp0
Jan  7 21:47:55 localhost pppd[1245]: Using interface ppp0
Jan  7 21:47:55 localhost pppd[1245]: Connect: ppp0 <--> /dev/cua0
Jan  7 21:47:56 localhost pppd[1245]: Remote message:
Jan  7 21:47:57 localhost pppd[1245]: local  IP address 166.72.245.138
Jan  7 21:47:57 localhost pppd[1245]: remote IP address 204.146.251.97

That look ok to me.  If I try ifconfig:

[root@vetex network-scripts]# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:75 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0

ppp0      Link encap:Point-to-Point Protocol
          inet addr:166.72.245.138  P-t-P:204.146.251.97  Mask:255.255.0.0
          UP POINTOPOINT RUNNING  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Memory:4f56038-4f56c04


No apparent problems there.  If I try pinging the local ip address I get
times around 0.1 ms.  If I try the remote IP address I get no response.
route -n shows:

[root@vetex network-scripts]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
204.146.251.97  0.0.0.0         255.255.255.255 UH    0      0        1 ppp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        8 lo
0.0.0.0         204.146.251.97  0.0.0.0         UG    0      0       14 ppp0


This has me completely baffled.  I DO specify the defaultroute option to
pppd.  I also get the same results if I establish the connection with
minicom and alt-a q then run pppd manually.

Any help would be greatly appreciated.

James Higgins



------------------------------

From: "Juergen Fiedler" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Utterly clueless about PPP
Date: Thu, 7 Jan 1999 22:38:18 -0500

Hi,

I'm trying to get PPP to work, but I just can't seem to get anywhere. As
recommended in the PPP-HOWTO, I first set up my /etc/resolv.conf and
/etc/ppp/options. My /etc/ppp/options looks like this:

    -detach
    modem
    lock
    crtscts
    defaultroute
    asyncmap 0
    mtu 552
    mru 552
    lcp-max-configure 30

After setting up everything, I use minicom to connect to my ISP and upon
establishing the connection, quit without resetting the modem. Then, I type

     pppd file /etc/ppp/options /dev/modem 57600

This produces some lines in /var/log/messages that look like that:

    Jan  7 22:08:14 CaveMaus kernel: PPP: version 2.2.0 (dynamic channel
allocation)
    Jan  7 22:08:14 CaveMaus kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
    Jan  7 22:08:14 CaveMaus kernel: PPP line discipline registered.
    Jan  7 22:08:14 CaveMaus kernel: registered device ppp0
    Jan  7 22:08:14 CaveMaus pppd[539]: pppd 2.3.3 started by root, uid 0
    Jan  7 22:08:14 CaveMaus pppd[539]: Using interface ppp0
    Jan  7 22:08:14 CaveMaus pppd[539]: Connect: ppp0 <--> /dev/modem
    Jan  7 22:09:27 CaveMaus pppd[539]: Modem hangup
    Jan  7 22:09:27 CaveMaus pppd[539]: Connection terminated.
    Jan  7 22:09:28 CaveMaus pppd[539]: Exit.

Having watched the activity with 'tail -f /var/log/messages', I can say that
it takes a while for the modem to hang up - as you can see from the log
file.
If I leave the 'lcp-max-configure 30' line out of the options file, I get a

    Jan  7 21:58:50 CaveMaus pppd[494]: LCP: timeout sending Config-Requests

instead of the modem hangup.
I am completely stumped. And very frustrated, too. I managed to hook my
Linux machine up to the Net using WinGate - but using a Windows proxy for a
Linux machine is a shame and an abomination.
Could someone please help me get online the Linux way? I'm really desperate.

TIA,
Juergen



------------------------------

From: David Barnes <[EMAIL PROTECTED]>
Subject: Re: need paging software for linux
Date: Fri, 08 Jan 1999 18:17:50 -0500

I did that several years ago.  A Perl script grabbed whatever page needed to
be sent out and emailed it to the paging company.  It worked very well for us.

Barnes
[EMAIL PROTECTED]

Stephen Carville wrote:

> Daddy Rabbit wrote:
> >
> > I have a communications server (windblows machine) that is used for
> > accessing the net, sending message to pagers, etc. I would like to get
> > rid of windblows alltogether. The only thing preventing me from doing
> > this is finding a paging program for linux.
>
> Most major paging services allow for paging by email.  If yours does, then
> create a mail alias like page_username with the correct address format for
> your provider and hand the message off via your mail server.
>
> --
> Stephen Carville
> [EMAIL PROTECTED]
> ----------------------------------------------------
> Management: The art of hiring intelligent, skilled individuals and then
> ignoring their advice.



------------------------------

From: Ingo Wichmann <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Telneting as "root"
Date: Fri, 08 Jan 1999 05:21:28 +0100

A.G. wrote

> I can remotely telnet to any of the machines, but not as root to either.
> Just as a regular user.
> 
> Is this normal or I have misconfigured smth?

This is standart on many computers. To do things as root change to
superuser mode by typing su. 
The login as regular user is made for security reasons: That way you
know who has loged in as root.

ingo

wichmann at uni-wuppertal dot de

------------------------------

From: Ingo Wichmann <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Telneting as "root"
Date: Fri, 08 Jan 1999 05:21:50 +0100

A.G. wrote

> I can remotely telnet to any of the machines, but not as root to either.
> Just as a regular user.
> 
> Is this normal or I have misconfigured smth?

This is standart on many computers. To do things as root change to
superuser mode by typing su. 
The login as regular user is made for security reasons: That way you
know who has loged in as root.

ingo

wichmann at uni-wuppertal dot de

------------------------------

From: Ingo Wichmann <[EMAIL PROTECTED]>
Subject: Re: Telneting as "root"
Date: Fri, 08 Jan 1999 05:26:17 +0100

A.G. wrote

> I can remotely telnet to any of the machines, but not as root to either.
> Just as a regular user.
> 
> Is this normal or I have misconfigured smth?

This is standart on many computers. To do things as root change to
superuser mode by typing su. 
The login as regular user is made for security reasons: That way you
know who has loged in as root.

ingo

wichmann at uni-wuppertal dot de


------------------------------

From: Ingo Wichmann <[EMAIL PROTECTED]>
Subject: Re: Telneting as "root"
Date: Fri, 08 Jan 1999 05:24:07 +0100

A.G. wrote

> I can remotely telnet to any of the machines, but not as root to either.
> Just as a regular user.
> 
> Is this normal or I have misconfigured smth?

This is standart on many computers. To do things as root change to
superuser mode by typing su. 
The login as regular user is made for security reasons: That way you
know who has loged in as root.

ingo

wichmann at uni-wuppertal dot de

------------------------------

From: root <[EMAIL PROTECTED]>
Subject: Re: sharing a cablemodem (with 1 NIC?)
Date: 08 Jan 1999 23:30:35 +0100

"Tom Shealy" <[EMAIL PROTECTED]> writes:

                Not sure, but I think that you might want to check out ip - aliasing 
i.e.
assign more than 1 different ip addresses to the same NIC.
e.g.
ifconfig eth0:0 192.168.0.x
ifconfig eth1:1 192.168.0.y

and so on.

As far as the clients looking for a particular MAC address, how about using dhcpd 
on the server spreading ip's based on the mac address ? 

Anyway I hope I haven't confused you more.

Don't hesitate to ask further !

====================
p94003@rainbow.**NOSPAM**.cs.unipi.gr
remove **NOSPAM** to reply !

> Is there any way to build a network where the server and clients all plug
> into the same hub (and where the cablemodem plugs into the uplink port on
> that hub?)
> 
> I was wondering because I only have one ethernet card in the server
> computer.  (I don't want to buy another because the server is a nubus-based
> ppc macintosh running mklinux and i've found old apple peripherals to be
> overpriced and hard to find...esp for nubus architecture)  Still, I'd rather
> use the mklinux box as a server than i would my pentium because I dual-boot
> the pentium, but don't use the mac for anything.
> 
> I was hoping there might be a way to make the clients look for the
> particular MAC address of the server, and then configure the server normally
> with the cable-modem.  Any ideas?
> 
> 
> Thanks,
> -Tom

------------------------------

From: Dale Miracle <[EMAIL PROTECTED]>
Subject: Re: i need help networking a win98 to redhat 5.1 using the recomended 
Date: Thu, 07 Jan 1999 23:30:45 -0500

InSaNeWAREZ wrote:
> 
> i have used the tulip driver that Linksys recomended from their
> website and i don't even get a link light on the hub...
> but they have an updated driver, but i don't know how to compile could
> someone please help me or

The driver is probably a .c file , copy that file to
/usr/src/linux/drivers/net.  Type 'cp tulip.c
/usr/src/linux/drivers/net'  without the '' signs.  Once you have copied
that file over you can recompile your kernel.  In the /usr/src/linux
directory type in make menuconfig (it is a menu driven config menu,
under network device make sure the tulip driver is checked , it is
located under either EISA/VLB/PCI  submenu (it make be different
depending on your current kernel version). 
When you exit type in make dep ; make clean ; make boot  (I believe that
is correct for RedHat, I haven't used it since last spring..I use all
slackware over here and I use make zlilo .  After that is done type in
make modules ; make modules_install    After that you can reboot.  It
sounds like a lot of work but it is not bad once you do it once.  The ;
stacks the commands sorta like a queue, it will do each command in the
order you type then in one at a time.

-- 
Dale Miracle                    "No matter where you go, there you are",
System Administrator         Oliver's Law of Location
The Edge of Insanity          "Real funny Scotty, now beam down my
[EMAIL PROTECTED]                    clothes"
              "I've gone to look for my self, if I return before I get
                            back keep me here."

------------------------------

From: Sydney Weidman <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup
Subject: Re: Utterly clueless about PPP
Date: Fri, 08 Jan 1999 04:17:02 GMT

Juergen Fiedler wrote:

> Hi,
>
> I'm trying to get PPP to work, but I just can't seem to get anywhere. As
> recommended in the PPP-HOWTO, I first set up my /etc/resolv.conf and
> /etc/ppp/options. My /etc/ppp/options looks like this:
>
>     -detach
>     modem
>     lock
>     crtscts
>     defaultroute
>     asyncmap 0
>     mtu 552
>     mru 552
>     lcp-max-configure 30
>
> After setting up everything, I use minicom to connect to my ISP and upon
> establishing the connection, quit without resetting the modem. Then, I type
>
>      pppd file /etc/ppp/options /dev/modem 57600
>
> This produces some lines in /var/log/messages that look like that:
>
>     Jan  7 22:08:14 CaveMaus kernel: PPP: version 2.2.0 (dynamic channel
> allocation)
>     Jan  7 22:08:14 CaveMaus kernel: PPP Dynamic channel allocation code
> copyright 1995 Caldera, Inc.
>     Jan  7 22:08:14 CaveMaus kernel: PPP line discipline registered.
>     Jan  7 22:08:14 CaveMaus kernel: registered device ppp0
>     Jan  7 22:08:14 CaveMaus pppd[539]: pppd 2.3.3 started by root, uid 0
>     Jan  7 22:08:14 CaveMaus pppd[539]: Using interface ppp0
>     Jan  7 22:08:14 CaveMaus pppd[539]: Connect: ppp0 <--> /dev/modem
>     Jan  7 22:09:27 CaveMaus pppd[539]: Modem hangup
>     Jan  7 22:09:27 CaveMaus pppd[539]: Connection terminated.
>     Jan  7 22:09:28 CaveMaus pppd[539]: Exit.
>
> Having watched the activity with 'tail -f /var/log/messages', I can say that
> it takes a while for the modem to hang up - as you can see from the log
> file.
> If I leave the 'lcp-max-configure 30' line out of the options file, I get a
>
>     Jan  7 21:58:50 CaveMaus pppd[494]: LCP: timeout sending Config-Requests
>
> instead of the modem hangup.
> I am completely stumped. And very frustrated, too. I managed to hook my
> Linux machine up to the Net using WinGate - but using a Windows proxy for a
> Linux machine is a shame and an abomination.
> Could someone please help me get online the Linux way? I'm really desperate.
>
> TIA,
> Juergen

Do you have a file /etc/ppp/pap-secrets with your password and whatnot? If so,
then you may need to add the option for ppp that points to the pap-secrets
file. See the man page for pppd for the command because my version is old and
uses obsolete syntax for the equivalent command. Also, it may help to add the
'user <your username here>' option.

That sounds like the only thing you're missing.

Cheers!


------------------------------

From: Doug Bryant <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.ppp
Subject: Re: Possible Red Hat pppd routing poblem
Date: Thu, 07 Jan 1999 20:49:30 -0500

Try removing any gateway entries.  I am not sure of the technical details of
why, but I think your computer is getting confused between the internet and
your gateway.

In redhat 5.2 under the Control Panel  |  Network Configuration  |  Routing
remove any entries in the default gateway and default gateway device

Hope this helps

Doug Bryant


James Higgins wrote:

> I just installed Red Hat 5.2 and set up a ppp link using linuxconf.  My ISP,
> Prodigy Internet, uses PAP authentication.  I have successfully configured
> this before in both Linux and FreeBSD.
>
> The session will connect successfully and I see the following in
> /var/log/messages:
>
> <snip from /var/log/messages>
> Jan  7 21:47:49 localhost chat[1247]: ATDT9757702^M^M
> Jan  7 21:47:49 localhost chat[1247]: CONNECT
> Jan  7 21:47:49 localhost chat[1247]:  -- got it
> Jan  7 21:47:49 localhost chat[1247]: send (^M)
> Jan  7 21:47:49 localhost chat[1247]: timeout set to 5 seconds
> Jan  7 21:47:49 localhost chat[1247]: expect (~)
> Jan  7 21:47:49 localhost chat[1247]:  49333/ARQ^M
> Jan  7 21:47:54 localhost chat[1247]: alarm
> Jan  7 21:47:54 localhost chat[1247]: send (^M)
> Jan  7 21:47:54 localhost chat[1247]: send (^M)
> Jan  7 21:47:54 localhost pppd[1245]: Serial connection established.
> Jan  7 21:47:55 localhost kernel: PPP: version 2.2.0 (dynamic channel
> allocation)
> Jan  7 21:47:55 localhost kernel: PPP Dynamic channel allocation code
> copyright 1995 Caldera, Inc.
> Jan  7 21:47:55 localhost kernel: PPP line discipline registered.
> Jan  7 21:47:55 localhost kernel: registered device ppp0
> Jan  7 21:47:55 localhost pppd[1245]: Using interface ppp0
> Jan  7 21:47:55 localhost pppd[1245]: Connect: ppp0 <--> /dev/cua0
> Jan  7 21:47:56 localhost pppd[1245]: Remote message:
> Jan  7 21:47:57 localhost pppd[1245]: local  IP address 166.72.245.138
> Jan  7 21:47:57 localhost pppd[1245]: remote IP address 204.146.251.97
>
> That look ok to me.  If I try ifconfig:
>
> [root@vetex network-scripts]# ifconfig
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>           RX packets:75 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0
>
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:166.72.245.138  P-t-P:204.146.251.97  Mask:255.255.0.0
>           UP POINTOPOINT RUNNING  MTU:1500  Metric:1
>           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0
>           Memory:4f56038-4f56c04
>
> No apparent problems there.  If I try pinging the local ip address I get
> times around 0.1 ms.  If I try the remote IP address I get no response.
> route -n shows:
>
> [root@vetex network-scripts]# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 204.146.251.97  0.0.0.0         255.255.255.255 UH    0      0        1 ppp0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        8 lo
> 0.0.0.0         204.146.251.97  0.0.0.0         UG    0      0       14 ppp0
>
> This has me completely baffled.  I DO specify the defaultroute option to
> pppd.  I also get the same results if I establish the connection with
> minicom and alt-a q then run pppd manually.
>
> Any help would be greatly appreciated.
>
> James Higgins


------------------------------

From: DonJr <donjr@[127.0.0.1]>
Crossposted-To: 
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.misc,comp.os.linux.setup,comp.os.linux.x
Subject: Re: Can't reboot at root from "xdm"
Date: Thu, 07 Jan 1999 23:58:59 -0500

Jon D. Slater wrote:
> 
> Once I log in as root using an XDM login, I've noticed if I type
> "reboot" or "reboot &" in an xterm my machine does not reboot until I
> press <Alt><Ctrl><F1>, switch to a "text based" screen.
> 
> Then the machine (running Redhat 5.2) reboots normally.
> 
> Why can't I reboot my machine from within an XDM login session?
> 
> Or maybe my question sould be "How do I reboot from an xterm run under
> an XDM login?"
> 
> Please send suggestions to:  JSlater<at>Qualcomm<dot>Com
> 
> Thanks in advance!!
> 
> Jon

 Jon

 Ways to REBOOT or HALT an XDM session from the termial:
  # su - shutdown -r now

  Assign a Password to the "user" accounts 'shutdown' and 'reboot'.
  Then logoff and simply login as one of those users.
  ( Note: Pick a "Strong Password" for these accounts if this method is
used. It is possible to telenet into a system and logon as one of theses
users.
  { As this method would allow a system to be ShutDown or Rebooted
remotely :} )

 Or a little more complex to setup, but easy to use and only works from
the system termial.

 The following adds 2 Buttons to your Xbanner screen. One labeled
"Reboot" and one labeled "HALT".
  (note: Requires that the 'tk' package is installed.)

 To /etc/X11/xdm/Xsetup_0 insert the following:

 | colum 0 in the file is here.
 -------- start of text to insert -----
 # reboot & halt buttons
 /usr/bin/wish <<EOF &
 wm geometry . +10+10
 button .halt   -text Halt   -command {exec shutdown -h now}
 button .reboot -text Reboot -command {exec shutdown -r now}
 pack .halt .reboot -side left
 EOF
 echo $! > /var/run/xdmbutton_0.pid

 -------- end of text to insert -------------
 # before the following line
 /usr/X11R6/bin/xbanner


 Then Replace /etc/X11/xdm/GiveConsole with the following:

  ----------------start of file------------------------------------
  #!/bin/sh
  # Assign ownership of the console to the invoking user
  # $XConsortium: GiveConsole,v 1.2 93/09/28 14:29:20 gildea Exp $
  #
  # By convention, both xconsole and xterm -C check that the
  # console is owned by the invoking user and is readable before
attaching
  # the console output.  This way a random user can invoke xterm -C
without
  # causing serious grief.
  #

  # :0 specific startup commands go here

  # stop reboot & halt buttons
  if test -r /var/run/xdmbutton_0.pid; then
      kill `cat /var/run/xdmbutton_0.pid`
      rm /var/run/xdmbutton_0.pid
  fi

  chown $USER /dev/console

  #eof GiveConsole
  --------------------eof-------------------------

  The above is only adding 6 lines to GiveConsole, but it was easier to
show the whole file then explain where to put it.


Note the above will allow any user who has access to the system Termial
and Mouse to Halt or Reboot the system.

  But, since having access to the system Mouse means they also most
likely have access to the "Power Switch" no big deal.

  At least now there is a chance that the system will be properly
shutdown now, instead of just pulling the Plug.


The easiest way to switch from a "text based" system to 'xdm' mode on a
RedHat based system (as root) is:
  $ telinit 5



--
 -----------------------
  Don E. Groves, Jr.
  my Email is jetnick AT erols DOT com
   
  I'll add a witty saying here later.

================

------------------------------

From: "Kyle J. Lee" <[EMAIL PROTECTED]>
Subject: Help! Ethernet problem!!!
Date: Thu, 07 Jan 1999 22:16:10 -0500

I have installed Inter EtherExpress PCI nic in my system (redhat 5.0)
When the system boots up everything seems normal.
the card is recognized without a problem.
when i type ifconfig, i get lo and eth0 listings.
but, when i try to ping other machines in our lan, it fails.
using netcfg, i entered correct dns information, domain name, default
gateway, etc.
i cannot think of anything that may be causing this problem.
please help me!!!!

Kyle


------------------------------

From: "endlessknot" <[EMAIL PROTECTED]>
Subject: Modules for Dec 21140 NICs
Date: Thu, 7 Jan 1999 22:52:58 -0700

I have several Addtron NICs that use the DEC 21140 chip for their 10/100
cards.  Does anyone know what modules, if any, work with the 21140 and where
I can download the module?  I'm looking at putting two NICs in the same
system so I can configure it as a router.
I'll confess that I'm new to all of the Linux stuff.  I'm looking for an
alternative to buying an expensive router for the test lab I work in.

BTW:  I'm running the SlackWare 3.6 distribution right now, but also have
the Redhat 4.2 dist.

Thanks in advance...
Brian Jarrett
[EMAIL PROTECTED]



------------------------------

From: Luigi Fabbro <[EMAIL PROTECTED]>
Subject: telnet problem: connects than diconnects before login. PLEASE HELP !
Date: Fri, 08 Jan 1999 14:10:49 +0100

I have been tryng telnet from Win95 to a Linux server.
The telnet worked fine, but when exit'ing the bash session it
disconnected trashing the
utmp file While I was tryng to solve this problem ( I have not yet ) the
telnet also stopped
 functioning and now I can not even telnet from the linux server to the
loopback
device (localhost): I can however still ping it an rlogin to it.
Running in-telnetd with -D option I have found out that it disconnects
just before
td recvd option TERMINAL TYPE IS "linux" (that is. this an the following
messages
displayed in the correctly functioning telnet session are not displayed
in the malfunctioning telnet session)

I have read the manual pages (inetd,telnet, in.telnedd , tcpd) the
HOWTOS Linux Nework Administrator and Linux.NET-3 as well as some telnet
RFC but have not
found any thing.
I  believe that I have not changed any configuration files (but I am not
100 percen certain)
and that probably  permissions were not set correctly and thus the Win95
telnet program
trashed not only the utmp file but also something else.

I  shall be grateful for any suggestion.

Luigi Fabbro

[EMAIL PROTECTED]


------------------------------

From: [EMAIL PROTECTED] (John Beppu)
Subject: Re: No FTP Under ipfwadm (Additional Info)
Date: 9 Jan 1999 00:39:22 GMT

In article <3694d2b8.0@news>, Pat Crean <[EMAIL PROTECTED]> wrote:

>insmod ip_masq_ftp

    You the man, Pat!#@  I had the exact same problem.

    Thank you!


>Chris Hanrahan wrote in message <3693a973.9970165@news>...
>>Additional information regarding this problem:  I can surf the web
>>just fine, send and receive email and (obviously) usenet.


-- 
/** [EMAIL PROTECTED] ......................................................... */

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.networking) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Networking Digest
******************************

Reply via email to