June 1999 - openSUSE Users - openSUSE Mailing Lists

RE: [SuSE Linux] Querk in my setup ?
by psims＠lombard.co.uk 07 Jun '99

07 Jun '99

reboot with your system boot floppy (you did make one....?) or the installation disk, do "Boot Installed System". cd /usr/src/linux "make install" will do the installation stuff correctly, identifying if it needs to do "make zlilo" or "make bzlilo"; alternatively, if you remember how you compiled the kernel (make zImage or bzImage) use the corresponding make command for lilo manually. Reboot from hdd as normal. > -----Original Message----- > From: W.D.McKinney [SMTP:deem@wdm.com] > Sent: Sunday, June 06, 1999 6:46 PM > To: suse-linux-e(a)suse.com > Subject: [SuSE Linux] Querk in my setup ? > > > How is this corrected : > > Inspecting /boot/System.map > Symbol table has incorrect version number. > > > Thanks so much. > -Dee > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

RE: [SuSE Linux] Re: Mouse problem after kernel compile
by psims＠lombard.co.uk 07 Jun '99

07 Jun '99

hmm, I use a serial mouse, had no such problems. Just make sure standard/generic serial support is compiled in, or use as a module with kerneld. You may be plagued with char-major-4 errors - comment out the lines for char-major-4 = serial in /etc/conf.modules. > -----Original Message----- > From: Hubert Mantel [SMTP:mantel@suse.de] > Sent: Sunday, June 06, 1999 4:02 PM > To: suse-linux-e(a)suse.com > Subject: [SuSE Linux] Re: Mouse problem after kernel compile > > > Hi, > > On Fri, Jun 04, Barbara Pfieffer wrote: > > > I have Suse 6.1. I wanted to compile the kernel to add PPP support. > > I added that and a few other things, which I may not need, like > > parellel port support. This is kernel 2.2.5, I haven't touched the > > source or upgraded anything. > > > > Anyway, now, in X Windows, my mouse won't work. Any ideas as to what > > in the kernel would cause this? I have a serial MS mouse, which works > > fine with the kernel as shipped with 6.1. > > There's a bug in the kernel wrt modules: If you add the serial support to > the kernel, it will additionally try to load as a module. The bad thing: > It "succeeds", rendering your serial ports unusable. > > Solution: Use the serial driver as module or delete > /lib/modules/2.2.5/misc/serial.o so that it cannot longer be loaded as > module. > > > I'm kind of new, so let me know if you need any more information. > > > > Thanks! > > > > Barbara > -o) > Hubert Mantel Goodbye, dots... /\\ > _\_v > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

[SuSE Linux] KDE 1.1.1
by root＠tcob1.tele2.co.uk 07 Jun '99

07 Jun '99

Has anyone installed KDE 1.1.1 on Suse 6. I keep getting a message that libz.so is missing but I cannot find any refernce to it on the CD. Sean -- Sysop and Webmaster of There Can Only Be 1 <A HREF="http://www.tcob1.tele2.co.uk"><A HREF="http://www.tcob1.tele2.co.uk</A">http://www.tcob1.tele2.co.uk</A</A>> <A HREF="ftp://212.19.67.58"><A HREF="ftp://212.19.67.58</A">ftp://212.19.67.58</A</A>> finger root(a)212.19.67.58 for status and PGP keys Linux User: #124682 (<A HREF="http://counter.li.org"><A HREF="http://counter.li.org</A">http://counter.li.org</A</A>>) ICQ: 679813 irc: thecivvie on irc.sysopnet.org -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

3 5

[SuSE Linux] Netscape Error Messages
by M-Norman＠dfid.gov.uk 07 Jun '99

07 Jun '99

Hi All I am a newbie to Lunux and have just installed SuSe 6.1. All is fine except for trying to browse the web. I have a successful connection to my ISP but when I try to use Netscape I get the following error messages : "error 2: Netscape is unable to locate the server (whatever on I try) Please check the server name and try again, error : the following hosts are unknown : home.netscape.com (and a couple of others I forgot to write down) Perhaps there is a problem with your name server ? If your site must use a non-root name server, you will need to set the $SOCKS_NS environment variable to point at the appropriate name server. It may (or may not be) necessary to set this variable, or the SOCKS host preference, to the IP address of the host in question rather than its name." I've read all I can find about connecting to ISP's configuring modems etc, etc. But I'm still confused, can someone explain what the error messages mean, and how I go about setting the parameters mentioned ? Am I right in thinking it's something to do with settings in my box, and not at the ISP end ? Thanks Mike Norman ****************************************** This email and any files transmitted with it have been swept by MIMEsweeper for the presence of computer viruses. dfid.gov.uk ****************************************** -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

2 1

RE: [SuSE Linux] Unable to access localhost in browser after 6.1 upgrade
by psims＠lombard.co.uk 07 Jun '99

07 Jun '99

recreate /etc/hosts. Unfortunately the upgrade likes to lunch on config files. > -----Original Message----- > From: Dwight Johnson [SMTP:dwj@aaronsrod.com] > Sent: Sunday, June 06, 1999 8:46 AM > To: SuSE List--English > Subject: [SuSE Linux] Unable to access localhost in browser after 6.1 > upgrade > > > Under 5.2 I used to browse Web pages on my local workstation using URLs > like: > > <A HREF="http://localhost/"><A HREF="http://localhost/</A">http://localhost/</A</A>> > <A HREF="http://192.168.1.1/"><A HREF="http://192.168.1.1/</A">http://192.168.1.1/</A</A>> > <A HREF="http://runner/"><A HREF="http://runner/</A">http://runner/</A</A>> #My machine name > > After upgrading to 6.1, none of these work. > > Thanks in advance for any help. > > Dwight > -- > Dwight Johnson All the Latest > dwj(a)linuxtoday.com Linux News > 360-681-6961 > ------------------->><A HREF="http://linuxtoday.com"><A HREF="http://linuxtoday.com</A">http://linuxtoday.com</A</A>> > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

[SuSE Linux] ioctl(PPPIOCGUNIT) : Operation always not permitted
by peter.pilgrim＠db.com 07 Jun '99

07 Jun '99

Martijn.van.den.Burg(a)asml.nl wrote: > Hi, > > From: Peter Pilgrim <peter.pilgrim(a)db.com> > > > > > > Hi > > > > I am still very much at a lost! > > > > I recently upgraded my laptop computer from Slackware 3.4 to > > SuSE Linux 6.1. I am trying to get SuSE Linux to > > connect to Demon Internet, but I keep getting errors > > from `pppd' where it said `operation not permitted' > > in the file `/var/log/messages'. I have also downloaded > > latest `pppd' 2.5.8 and it still did not work. Here are the > > messages: > > > > pppd[345]: pppd 2.3.8 started by root, uid 0 > > pppd[345]: kernel tty_io.c process (345) pppd used obsolete > > `/dev/cua2' up date software to use `/dev/ttyS2' > > ... > > ... > > pppd[345]: Serial connection established > > pppd[345]: ioctl(PPPIOCGUNIT): Operation not permitted > > pppd[345]: tcsetattr: Operation not permitted > > pppd[345]: Exit > > > > I checked everything that I could think of. I made sure that I tried > > to connect as the superuser. I checked that `/dev/modem' is > > symbolically linked to `/dev/ttyS2'. I also checked that the access > > permissions for the program `pppd' and device files were set to > > `root'. I have no difficulty dialing up to my ISP with my modem, but > > everytime the connection is completed, the `pppd' collapses. I suspect > > that has something to do with the second message about the obsolete > > `/dev/cua2'. I am clueless where to look next. > > > > /dev/cua<x> used to be the 'old' name for /dev/ttyS<x> serial devices, > it became obsolete with kernel 2.2.x (but it may have been 2.1.x, I'm not sure). > > A workaround could be to make a symlink from cua to ttS (as root): > > ln -s /dev/ttyS2 /dev/cua2 > > this does not solve the actual cause of the problem, I'm too much of > a newbie to know the exact details - maybe you should install 6.1 from > scratch instead of upgrading from a different distro? > > > I did also type `find /etc -type f -print | xargs grep -n cua2' , but I > > could > > not find any configuration file to help me. > > > > Any help greatly appreciated. > > > > Success, > > Martijn ATTACHMENTS INCLUDED I did this symbolic linking, and it still did not work. I search using `find /etc -print | xarg grep -n /dev/cua.' for anything like `/dev/cua2' in the relevant config files. One thing I have noticed that the SuSE Linux keep removing the symbolic link I set, changing it back to `/dev/modem' -> `/dev/cua2'. Why? I explicity did this. /etc/pcmcia stop; /etc/serial stop; rm -f /dev/modem ; ln -s /dev/ttyS2 /dev/modem /etc/serial start; /etc/pcmcia start; Where is this _****ing_ modem setting in `rc.config' , Eh ? I have even changed the syslogd config to send to send messages to `/var/log/ppplog' as the PPPD-HOWTO described, but I get the same messages put in `/var/log/ppplog' as I did in `/var/log/messages'. The HOWTO does not have anything about PPPIOCGUNIT within it. This really bulls**t!!! Is this bloody `/dev/cua2' compiled into the kernel or something? What the hell else can I do? I cannot find the solution to this problem. I have place the attachments with this file in hope someone out there can help me. !Viancuolo! -- Cheers Peter ----------------------------------------------------------------- import std.disclaimer; // More Lava for ya Java, mate! "Who put the ball in the Munich net? Ollie Gunnar Solkjaer!" </PRE> <PRE> #!/bin/sh # # file: /etc/ppp/redialer # # This script is based on the script "redialer" found at # <A HREF="ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz"><A HREF="ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz</A">ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz</A</A>> # It should work with previous versions of chat too # ################################################################### # # These parameters control the attack dialing sequence. # # Maximum number of attempts to reach the telephone number(s) MAX_ATTEMPTS=8 # Delay between each of the attempts (in seconds). SLEEP_DELAY=5 # Terminal to echo output, exported from "ppp-on" if [ "w$TERMINAL" = "w" ]; then TERMINAL=/dev/console fi ################################################################### # # This is a list of telephone numbers. ## PHONE1=314730 ## PHONE2=31420920 ## PHONE3=31420988 ## PHONE4=39991099 ## numbers=4 # Demon Internet COLT PHONE1=01716640666 # Purple Romp PHONE2=0845-212-1666 # Demon 1 PHONE3=08450798666 # Demon 2 PHONE4=08453535666 # ISDN NEW Sun May 23 23:59:25 BST 1999 ISDN_PHONE=0845-212-0667 numbers=4 ################################################################### ## ## ACCOUNT=AliBaba ## PASSWORD=OpenSesame ACCOUNT=xenonsoft PASSWORD=loVebugg ################################################################### # # Script to dial a telephone # You probably have to change the initialization string # Check your modem manual function callnumber { /usr/sbin/chat -v -t60 \ TIMEOUT 35 \ ABORT '\nBUSY\r' \ ABORT '\nNO CARRIER\r' \ ABORT '\nRING\r\n\r\nRING\r' \ ABORT '\nNO DIALTONE\r' \ ABORT '\nERROR\r' \ ABORT 'Login incorrect' \ ABORT '** Bad Password' \ '' \ ATH0 OK \ ATZ OK \ ATL1M3 OK \ ATDT$1 CONNECT \ '' \ ogin:--ogin: $ACCOUNT \ word: $PASSWORD \ ocol: ppp,nolqm,idle=300 \ HELLO ### TIMEOUT 30 \ ### 'CONNECT 115200/REL' '' \ # # decide what to do depending on exitcode of chat # case $? in 0) echo Connection established > $TERMINAL; exit 0;; 1) echo chat: exit 1, see manpage for details. > $TERMINAL; exit 1;; 2) echo chat: exit 2, see manpage for details. > $TERMINAL; exit 2;; 3) echo chat: exit 3, see manpage for details. > $TERMINAL; exit 3;; 4) echo Line busy. > $TERMINAL;; 5) echo No Carrier. > $TERMINAL;; 6) echo A call is coming. Exiting! > $TERMINAL; exit 1;; 7) echo No dialtone. > $TERMINAL;; 8) echo An error occured. Exiting! > $TERMINAL; exit 1;; esac return } ################################################################### # # Function, that displays the rest of time before the next number # is dialed function sleeping { REST=$SLEEP_DELAY while [ $REST -ne 0 ]; do echo -ne Next trial in $REST seconds. "\r" > $TERMINAL sleep 1s REST=`expr $REST - 1` done echo "Next trial now. " "\r" > $TERMINAL return } ################################################################### # # Dial telephone numbers until one answers attempt=0 while : ; do echo -e "\n" > $TERMINAL attempt=`expr $attempt + 1` echo "Dialing attempt number: $attempt" > $TERMINAL n=`expr $attempt % $numbers` if [ $n -eq 0 ]; then n=$numbers fi NUMBER=`eval echo '$PHONE'$n` callnumber $NUMBER if [ $attempt -eq $MAX_ATTEMPTS ]; then exit 1 fi sleeping done # fini </PRE> <PRE> ls -l /dev/cua[0-3] /dev/ttyS[0-3] crw-rw---- 1 root uucp 5, 64 Apr 15 06:14 /dev/cua0 lrwxrwxrwx 1 root root 10 Jun 6 15:18 /dev/cua1 -> /dev/ttyS1 lrwxrwxrwx 1 root root 10 Jun 6 15:18 /dev/cua2 -> /dev/ttyS2 crw-rw---- 1 root uucp 5, 67 May 31 00:08 /dev/cua3 crw-rw---- 1 root uucp 4, 64 Apr 15 06:14 /dev/ttyS0 crw-rw---- 1 root uucp 4, 65 Apr 15 06:14 /dev/ttyS1 crw-rw-rw- 1 root uucp 4, 66 Jun 6 16:11 /dev/ttyS2 crw-rw---- 1 root uucp 4, 67 Apr 15 06:14 /dev/ttyS3 -r-sr-sr-x 1 root root 130132 May 31 20:53 /usr/sbin/pppd* ls -l /usr/sbin/pppd -r-sr-sr-x 1 root root 130132 May 31 20:53 /usr/sbin/pppd* ls -dl /etc/ppp drwxr-xr-x 3 root root 1024 Jun 6 16:26 /etc/ppp/ ls -l /etc/ppp total 57 lrwxrwxrwx 1 root root 7 May 11 02:18 auth-down -> auth-up* -rwxr-x--x 1 root root 469 Mar 6 1998 auth-up* -rw------- 1 root root 99 Jun 6 15:20 chap-secrets -rw------- 1 root dialout 450 Jun 6 15:50 connect-errors -rw-r----- 1 root root 283 May 29 1997 ioptions -rw-r----- 1 root root 1369 Oct 27 1997 ioptions.YaST lrwxrwxrwx 1 root root 5 May 11 02:18 ip-down -> ip-up* -rwxr-x--x 1 root root 3027 Apr 8 09:30 ip-up* -rw-r--r-- 1 root root 6327 Jun 6 16:12 options -rw-r--r-- 1 root root 6105 May 30 23:05 options.bak -rw-r--r-- 1 root root 6327 Jun 6 16:10 options.demon -rw-r--r-- 1 root root 6105 Jun 6 14:55 options.demon~ -rw-r--r-- 1 root root 6105 May 23 23:41 options~ -rw------- 1 root root 1083 Jun 6 16:23 pap-secrets -rw------- 1 root root 0 May 30 20:50 pap-secrets.new drwxr-xr-x 2 root root 1024 May 30 23:08 peers/ -rwxr-xr-x 1 root root 998 May 22 18:54 ppp-off* -rwxr-xr-x 1 root root 1764 Jun 6 16:15 ppp-on* -rwxr-xr-x 1 root root 1733 May 30 23:01 ppp-on~* -rwxr-xr-x 1 root root 3301 May 31 21:35 redialer* -rwxr-xr-x 1 root root 3303 May 23 23:59 redialer~* find /etc -type f -print | xargs grep -n /dev/cua /etc/rc.config:103:# Which device is the modem ? (e.g. "/dev/cua1") /etc/powerd.conf:68:#serialline /dev/cua3 /etc/rc.config.old:103:# Which device is the modem ? (e.g. "/dev/cua1") /etc/rc.config.old.o:103:# Which device is the modem ? (e.g. "/dev/cua1") /etc/pcmcia/serial:27:if [ -c /dev/cua1 ] ; then /etc/rc.config~:103:# Which device is the modem ? (e.g. "/dev/cua1") </PRE> <PRE> #!/bin/sh # (c) '97, S.u.S.E. GmbH, Fuerth, Germany # Klaus Franken <kfr(a)suse.de> # 25.02.98 # # Remo Behn <sray(a)suse.de> # 18.07.98 BASENAME=`basename $0` INTERFACE=$1 DEVICE=$2 SPEED=$3 LOCALIP=$4 REMOTEIP=$5 if [ -z "$REMOTEIP" ]; then echo "Usage: $0 <INTERFACE> <DEVICE> <SPEED> <LOCALIP> <REMOTEIP>" exit 1 fi case "$INTERFACE" in ippp*) . /etc/rc.config # find the device found=0 for I in $NETCONFIG; do eval NETDEV=\$NETDEV$I if [ $NETDEV = $INTERFACE ]; then found=1 break; fi done if [ $found -eq 0 ]; then echo "Device '$INTERFACE' not configured in '/etc/rc.config'" exit 1 fi eval IFCONFIG=\$IFCONFIG$I DEST=`grep -v "^#" /etc/route.conf | grep "$INTERFACE\$" | awk '{ print $1}'` DEFAULT=`grep -v "^#" /etc/route.conf | grep default | awk '{ print $2}'` #echo "ok, NETDEV:$NETDEV; IFCONFIG:$IFCONFIG." #echo " DEST: $DEST; DEFAULT: $DEFAULT" case "$BASENAME" in ip-up) # default deny #ipfwadm -I -p deny #ipfwadm -O -p deny # flush #ipfwadm -I -f #ipfwadm -O -f # accept dns #ipfwadm -O -a accept -P udp -S 0/0 53 1024:65535 -D 0/0 53 -W $INTERFACE #ipfwadm -I -a accept -P udp -D 0/0 53 1024:65535 -S 0/0 53 -W $INTERFACE #ipfwadm -O -a accept -P tcp -S 0/0 53 1024:65535 -D 0/0 53 -W $INTERFACE #ipfwadm -I -a accept -P tcp -D 0/0 53 1024:65535 -S 00/0 53 -k -W $INTERFACE # accept conect from client to internet #ipfwadm -O -a accept -P tcp -S 0/0 1024:65535 -D 0/0 -W $INTERFACE #ipfwadm -I -a accept -P tcp -D 0/0 1024:65535 -S 0/0 -k -W $INTERFACE # deny, last match #ipfwadm -I -a deny -P tcp -S 0/0 -D 0/0 -W $INTERFACE #ipfwadm -I -a deny -P udp -S 0/0 -D 0/0 -W $INTERFACE # default accept #ipfwadm -I -p accept -W $INTERFACE #ipfwadm -O -p accept -W $INTERFACE /sbin/route add default gw $REMOTEIP dev $INTERFACE # maybe you want to start mail services: # set follow variables in /etc/rc.config # SENDMAIL_TYPE="yes" # SENDMAIL_SMARTHOST="<ISP-mailserver>" # SENDMAIL_ARGS="-bd -om" # SENDMAIL_EXPENSIVE="yes" # SENDMAIL_NOCANONIFY="yes" #/usr/bin/fetchmail -a -v >>/var/log/fetchmail 2>&1 & #/usr/sbin/sendmail -q & ;; ip-down) # restart interface /sbin/ifconfig $INTERFACE down # workaround due to kernel problem with 'kernd': sleep 1 /sbin/ifconfig $INTERFACE $IFCONFIG # flush, del all rules #ipfwadm -I -f #ipfwadm -O -f # set routes from /etc/route.conf test -z "$DEST" || /sbin/route add -host $DEST dev $INTERFACE test -z "$DEFAULT" || /sbin/route add default gw $DEFAULT ;; *) ;; esac ;; ppp*) # Analog-PPP, add commands if you need... ;; *) # dont know... ;; esac </PRE> <PRE> # /etc/ppp/options # The name of this server. Often, the FQDN is used here. #name <host> # Enforce the use of the hostname as the name of the local system for # authentication purposes (overrides the name option). #usehostname # If no local IP address is given, pppd will use the first IP address # that belongs to the local hostname. If "noipdefault" is given, this # is disabled and the peer will have to supply an IP address. noipdefault # With this option, pppd will accept the peer's idea of our local IP # address, even if the local IP address was specified in an option. #ipcp-accept-local # With this option, pppd will accept the peer's idea of its (remote) IP # address, even if the remote IP address was specified in an option. #ipcp-accept-remote # Specify which DNS Servers the incoming Win95 or WinNT Connection should use # Two Servers can be remotely configured #ms-dns 192.168.1.1 #ms-dns 192.168.1.2 # Specify which WINS Servers the incoming connection Win95 or WinNT should use #wins-addr 192.168.1.50 #wins-addr 192.168.1.51 # enable this on a server that already has a permanent default route #nodefaultroute # *PP* Sun May 23 22:36:31 BST 1999 defaultroute # Run the executable or shell command specified after pppd has terminated # the link. This script could, for example, issue commands to the modem # to cause it to hang up if hardware modem control signals were not # available. # If mgetty is running, it will reset the modem anyway. So there is no need # to do it here. #disconnect "chat -- \d+++\d\c OK ath0 OK" # Increase debugging level (same as -d). The debug output is written # to syslog LOG_LOCAL2. ## *PP* Sun Jun 06 16:05:40 BST 1999 ## debug # Enable debugging code in the kernel-level PPP driver. The argument n # is a number which is the sum of the following values: 1 to enable # general debug messages, 2 to request that the contents of received # packets be printed, and 4 to request that the contents of transmitted # packets be printed. #kdebug n # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. noauth # authentication can either be pap or chap. As most people only want to # use pap, you can also disable chap: #require-pap #refuse-chap # Use hardware flow control (i.e. RTS/CTS) to control the flow of data # on the serial port. crtscts # Specifies that pppd should use a UUCP-style lock on the serial device # to ensure exclusive access to the device. # *PP* Sun May 23 22:36:12 BST 1999 lock # Use the modem control lines. modem /dev/modem 115200 # async character map -- 32-bit hex; each bit is a character # that needs to be escaped for pppd to receive it. 0x00000001 # represents '\x01', and 0x80000000 represents '\x1f'. # To allow pppd to work over a rlogin/telnet connection, ou should escape # XON (^Q), XOFF (^S) and ^]: (The peer should use "escape ff".) # Changed *PP* Sun Jun 06 16:06:26 BST 1999 # asyncmap 200a0000 asyncmap 0a0000 # Specifies that certain characters should be escaped on transmission # (regardless of whether the peer requests them to be escaped with its # async control character map). The characters to be escaped are # specified as a list of hex numbers separated by commas. Note that # almost any character can be specified for the escape option, unlike # the asyncmap option which only allows control characters to be # specified. The characters which may not be escaped are those with hex # values 0x20 - 0x3f or 0x5e. #escape 11,13,ff # Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd # will ask the peer to send packets of no more than <n> bytes. The # minimum MRU value is 128. The default MRU value is 1500. A value of # 296 is recommended for slow links (40 bytes for TCP/IP header + 256 # bytes of data). #mru 542 ## *PP* Sun May 23 22:36:49 BST 1999 mru 576 # Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer # requests a smaller value via MRU negotiation, pppd will request that # the kernel networking code send data packets of no more than n bytes # through the PPP network interface. #mtu <n> ## *PP* Sun May 23 22:36:53 BST 1999 mtu 576 # Set the interface netmask to <n>, a 32 bit netmask in "decimal dot" # notation (e.g. 255.255.255.0). #netmask 255.255.255.0 # Don't fork to become a background process (otherwise pppd will do so # if a serial device is specified). # nodetach # Set the assumed name of the remote system for authentication purposes # to <n>. #remotename <n> # Add an entry to this system's ARP [Address Resolution Protocol] # table with the IP address of the peer and the Ethernet address of this # system. {proxyarp,noproxyarp} # Commented out *PP* # noproxyarp # Use the system password database for authenticating the peer using # PAP. Note: mgetty already provides this option. If this is specified # then dialin from users using a script under Linux to fire up ppp wont work. #login # If this option is given, pppd will send an LCP echo-request frame to # the peer every n seconds. Under Linux, the echo-request is sent when # no packets have been received from the peer for n seconds. Normally # the peer should respond to the echo-request by sending an echo-reply. # This option can be used with the lcp-echo-failure option to detect # that the peer is no longer connected. #lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. #lcp-echo-failure 4 # Specifies that pppd should disconnect if the link is idle for n seconds. #idle 600 # Disable the IPXCP and IPX protocols. # Commented out *PP* Sun Jun 06 16:05:04 BST 1999 ## noipx # Disable VJ ## Commented out *PP* Sun Jun 06 16:05:06 BST 1999 ## novj ## novjccomp # ---<End of File>--- </PRE> <PRE> # /etc/ppp/options # The name of this server. Often, the FQDN is used here. #name <host> # Enforce the use of the hostname as the name of the local system for # authentication purposes (overrides the name option). #usehostname # If no local IP address is given, pppd will use the first IP address # that belongs to the local hostname. If "noipdefault" is given, this # is disabled and the peer will have to supply an IP address. noipdefault # With this option, pppd will accept the peer's idea of our local IP # address, even if the local IP address was specified in an option. #ipcp-accept-local # With this option, pppd will accept the peer's idea of its (remote) IP # address, even if the remote IP address was specified in an option. #ipcp-accept-remote # Specify which DNS Servers the incoming Win95 or WinNT Connection should use # Two Servers can be remotely configured #ms-dns 192.168.1.1 #ms-dns 192.168.1.2 # Specify which WINS Servers the incoming connection Win95 or WinNT should use #wins-addr 192.168.1.50 #wins-addr 192.168.1.51 # enable this on a server that already has a permanent default route #nodefaultroute # *PP* Sun May 23 22:36:31 BST 1999 defaultroute # Run the executable or shell command specified after pppd has terminated # the link. This script could, for example, issue commands to the modem # to cause it to hang up if hardware modem control signals were not # available. # If mgetty is running, it will reset the modem anyway. So there is no need # to do it here. #disconnect "chat -- \d+++\d\c OK ath0 OK" # Increase debugging level (same as -d). The debug output is written # to syslog LOG_LOCAL2. ## *PP* Sun Jun 06 16:05:40 BST 1999 ## debug # Enable debugging code in the kernel-level PPP driver. The argument n # is a number which is the sum of the following values: 1 to enable # general debug messages, 2 to request that the contents of received # packets be printed, and 4 to request that the contents of transmitted # packets be printed. #kdebug n # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. noauth # authentication can either be pap or chap. As most people only want to # use pap, you can also disable chap: #require-pap #refuse-chap # Use hardware flow control (i.e. RTS/CTS) to control the flow of data # on the serial port. crtscts # Specifies that pppd should use a UUCP-style lock on the serial device # to ensure exclusive access to the device. # *PP* Sun May 23 22:36:12 BST 1999 lock # Use the modem control lines. modem /dev/modem 115200 # async character map -- 32-bit hex; each bit is a character # that needs to be escaped for pppd to receive it. 0x00000001 # represents '\x01', and 0x80000000 represents '\x1f'. # To allow pppd to work over a rlogin/telnet connection, ou should escape # XON (^Q), XOFF (^S) and ^]: (The peer should use "escape ff".) # Changed *PP* Sun Jun 06 16:06:26 BST 1999 # asyncmap 200a0000 asyncmap 0a0000 # Specifies that certain characters should be escaped on transmission # (regardless of whether the peer requests them to be escaped with its # async control character map). The characters to be escaped are # specified as a list of hex numbers separated by commas. Note that # almost any character can be specified for the escape option, unlike # the asyncmap option which only allows control characters to be # specified. The characters which may not be escaped are those with hex # values 0x20 - 0x3f or 0x5e. #escape 11,13,ff # Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd # will ask the peer to send packets of no more than <n> bytes. The # minimum MRU value is 128. The default MRU value is 1500. A value of # 296 is recommended for slow links (40 bytes for TCP/IP header + 256 # bytes of data). #mru 542 ## *PP* Sun May 23 22:36:49 BST 1999 mru 576 # Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer # requests a smaller value via MRU negotiation, pppd will request that # the kernel networking code send data packets of no more than n bytes # through the PPP network interface. #mtu <n> ## *PP* Sun May 23 22:36:53 BST 1999 mtu 576 # Set the interface netmask to <n>, a 32 bit netmask in "decimal dot" # notation (e.g. 255.255.255.0). #netmask 255.255.255.0 # Don't fork to become a background process (otherwise pppd will do so # if a serial device is specified). # nodetach # Set the assumed name of the remote system for authentication purposes # to <n>. #remotename <n> # Add an entry to this system's ARP [Address Resolution Protocol] # table with the IP address of the peer and the Ethernet address of this # system. {proxyarp,noproxyarp} # Commented out *PP* # noproxyarp # Use the system password database for authenticating the peer using # PAP. Note: mgetty already provides this option. If this is specified # then dialin from users using a script under Linux to fire up ppp wont work. #login # If this option is given, pppd will send an LCP echo-request frame to # the peer every n seconds. Under Linux, the echo-request is sent when # no packets have been received from the peer for n seconds. Normally # the peer should respond to the echo-request by sending an echo-reply. # This option can be used with the lcp-echo-failure option to detect # that the peer is no longer connected. #lcp-echo-interval 30 # If this option is given, pppd will presume the peer to be dead if n # LCP echo-requests are sent without receiving a valid LCP echo-reply. # If this happens, pppd will terminate the connection. Use of this # option requires a non-zero value for the lcp-echo-interval parameter. # This option can be used to enable pppd to terminate after the physical # connection has been broken (e.g., the modem has hung up) in # situations where no hardware modem control lines are available. #lcp-echo-failure 4 # Specifies that pppd should disconnect if the link is idle for n seconds. #idle 600 # Disable the IPXCP and IPX protocols. # Commented out *PP* Sun Jun 06 16:05:04 BST 1999 ## noipx # Disable VJ ## Commented out *PP* Sun Jun 06 16:05:06 BST 1999 ## novj ## novjccomp # ---<End of File>--- </PRE> <PRE> #!/bin/sh # # file: /etc/ppp/ppp-off # ###################################################################### # # Determine the device to be terminated. # if [ "$1" = "" ]; then DEVICE=ppp0 else DEVICE=$1 fi ###################################################################### # # If the ppp0 pid file is present then the program is running. Stop it. if [ -r /var/run/$DEVICE.pid ]; then kill -INT `cat /var/run/$DEVICE.pid` # # If the kill did not work then there is no process running for this # pid. It may also mean that the lock file will be left. You may wish # to delete the lock file at the same time. if [ ! "$?" = "0" ]; then rm -f /var/run/$DEVICE.pid echo "ERROR: Removed stale pid file" exit 1 fi # # Success. Let pppd clean up its own junk. echo "PPP link to $DEVICE terminated." exit 0 fi # # The ppp process is not running for ppp0 echo "ERROR: PPP link is not active on $DEVICE" exit 1 </PRE> <PRE> #!/bin/sh # # file: /etc/ppp/ppp-on # # This script is based on the script "ppp-on" found at # <A HREF="ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz"><A HREF="ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz</A">ftp://sunsite.unc.edu/pub/Linux/system/Network/serial/ppp/ppp-2.2.0f.tar.gz</A</A>> # # Script to initiate a ppp connection. This is the first part of the # pair of scripts. This is not a secure pair of scripts as the codes # are visible with the 'ps' command. However, it is simple. # # These are the parameters. Change as needed. LOCAL_IP=0.0.0.0 # Local IP address if known. Dynamic = 0.0.0.0 REMOTE_IP=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0 DEVICE=/dev/modem LOCAL_IP=192.237.75.1 REMOTE_IP=158.152.1.222 DEVICE=/dev/ttyS2 NETMASK=255.255.255.0 # The proper netmask if needed # # export current tty to enable output in dialer script # export TERMINAL=`tty` # # This is the location of the script which dials the phone and logs # in. Please use the absolute file name as the $PATH variable is not # used on the connect option. (To do so on a 'root' account would be # a security hole so don't ask.) # DIALER_SCRIPT=/etc/ppp/redialer # # Initiate the connection # # I put most of the common options on this command. Please, don't # forget the 'lock' option or some programs such as mgetty will not # work. The asyncmap and escape will permit the PPP link to work with # a telnet or rlogin connection. You are welcome to make any changes # as desired. Don't use the 'defaultroute' option if you currently # have a default route to an ethernet gateway. # # ### PPP_FLAGS="38400 mru 1500 modem debug kdebug 0 defaultroute crtscts noipdefault asyncmap 20A0000 escape FF" PPP_FLAGS="115200 mru 576 mtu 576 modem debug defaultroute crtscts noipdefault escape FF" /usr/sbin/pppd lock connect $DIALER_SCRIPT $DEVICE $PPP_FLAGS $LOCAL_IP:$REMOTE_IP # fini </PRE> <PRE> #!/bin/sh # Example for /etc/ppp/auth-up, /etc/ppp/auth-down # Klaus Franken <kfr(a)suse.de> # 01.06.97 DEBUG=/var/log/ipppd_auth.log BASENAME=`basename $0` IFNAME=$1 AUTHNAME=$2 USER=$3 DEVNAME=$4 SPEED=$5 case "$BASENAME" in auth-up) NAME='up ' if [ "$AUTHNAME" = 'BillGates' ]; then /sbin/isdnctrl hangup $IFNAME fi ;; auth-down) NAME='down' ;; *) ;; esac echo "$NAME: `date`: $IFNAME, $DEVNAME, $AUTHNAME" >> $DEBUG

1 0

Re: [SuSE Linux] PPPIOCGUNIT Operation (still) not permitted
by peter.pilgrim＠db.com 07 Jun '99

07 Jun '99

Martijn.van.den.Burg(a)asml.nl wrote: > Hi, > > From: Peter Pilgrim <peter.pilgrim(a)db.com> > > > > > > Hi > > > > I am still very much at a lost! > > > > I recently upgraded my laptop computer from Slackware 3.4 to > > SuSE Linux 6.1. I am trying to get SuSE Linux to > > connect to Demon Internet, but I keep getting errors > > from `pppd' where it said `operation not permitted' > > in the file `/var/log/messages'. I have also downloaded > > latest `pppd' 2.5.8 and it still did not work. Here are the > > messages: > > > > pppd[345]: pppd 2.3.8 started by root, uid 0 > > pppd[345]: kernel tty_io.c process (345) pppd used obsolete > > `/dev/cua2' up date software to use `/dev/ttyS2' > > ... > > ... > > pppd[345]: Serial connection established > > pppd[345]: ioctl(PPPIOCGUNIT): Operation not permitted > > pppd[345]: tcsetattr: Operation not permitted > > pppd[345]: Exit > > > > I checked everything that I could think of. I made sure that I tried > > to connect as the superuser. I checked that `/dev/modem' is > > symbolically linked to `/dev/ttyS2'. I also checked that the access > > permissions for the program `pppd' and device files were set to > > `root'. I have no difficulty dialing up to my ISP with my modem, but > > everytime the connection is completed, the `pppd' collapses. I suspect > > that has something to do with the second message about the obsolete > > `/dev/cua2'. I am clueless where to look next. > > > > /dev/cua<x> used to be the 'old' name for /dev/ttyS<x> serial devices, > it became obsolete with kernel 2.2.x (but it may have been 2.1.x, I'm not sure). > > A workaround could be to make a symlink from cua to ttS (as root): > > ln -s /dev/ttyS2 /dev/cua2 > > this does not solve the actual cause of the problem, I'm too much of > a newbie to know the exact details - maybe you should install 6.1 from > scratch instead of upgrading from a different distro? > > > I did also type `find /etc -type f -print | xargs grep -n cua2' , but I > > could > > not find any configuration file to help me. > > > > Any help greatly appreciated. > > > > Success, > > Martijn I did this symbolic linking, and it still did not work. I search using `find /etc -print | xarg grep -n /dev/cua.' for anything like `/dev/cua2' in the relevant config files. One thing I have noticed that the SuSE Linux keep removing the symbolic link I set, changing it back to `/dev/modem' -> `/dev/cua2'. Why? I explicity did this. /etc/pcmcia stop; /etc/serial stop; rm -f /dev/modem ; ln -s /dev/ttyS2 /dev/modem /etc/serial start; /etc/pcmcia start; Where is this _****ing_ modem setting in `rc.config' , Eh ? I have even changed the syslogd config to send to send messages to `/var/log/ppplog' as the PPPD-HOWTO described, but I get the same messages put in `/var/log/ppplog' as I did in `/var/log/messages'. The HOWTO does not have anything about PPPIOCGUNIT within it. This really bulls**t!!! Is this bloody `/dev/cua2' compiled into the kernel or something? What the hell else can I do? I cannot find the solution to this problem. I have place the attachments with this file in hope someone out there can help me. !Viancuolo! -- Cheers Peter ----------------------------------------------------------------- import std.disclaimer; // More Lava for ya Java, mate! "Who put the ball in the Munich net? Ollie Gunnar Solkjaer!" -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

[SuSE Linux] sendmail upgrade ?? security fix
by neonatus＠gimp.thz.net 07 Jun '99

07 Jun '99

-----BEGIN PGP SIGNED MESSAGE----- Hi *! I have just checked my local lan with saint and have noticed that it has found a few sendmail holes!!! I would like tu upgrade sendmail from an rpm, but there was no sendmail upgrade rpm on the suse upgrade www site. If anyone knows where to get SuSE 6.0 sandmail version 8.9.x please reply. THX in advance! Bo&scaron;tjan ___ Bo&scaron;tjan Müller [NEONATUS], NEONATUS(a)bigfoot.com, <A HREF="http://surf.to/NEONATUS"><A HREF="http://surf.to/NEONATUS</A">http://surf.to/NEONATUS</A</A>> ICQ #:7506644, For my PGP key finger: neonatus(a)gimp.thz.net RSA id: 0x90178DBD, Powered by S.u.S.E. Linux 6.0. Indifference will be the downfall of mankind, but who cares? -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Comment: PGPEnvelope - <A HREF="http://www.bigfoot.com/~ftobin/resources"><A HREF="http://www.bigfoot.com/~ftobin/resources</A">http://www.bigfoot.com/~ftobin/resources</A</A>> Charset: noconv iQEVAwUBN1vjlFLaN4+QF429AQG0hQf/QNjS1dxOHMTRx/UF0tbTdCNvI0LZuHro xbHNfYjPyj3W7gONawR8KLY1D51Mek5rG5SpBEBKF5vSvho4+8TpjbWTpp1dHF8I /hnQA2uwi2GSJsYgvWEO5inOPfinzAW4M6J1Y58SYWLMPLyHkrmiuubNGcPKqLfo DzTE6pxkioQ53aH8K5jwiyDnOtHmsbUnQbxZLsN/qy01kzLPyZxit9xARL0GH9GM eckN7QeVOoa041E3N6M7SgYXA/Iw48dPpWHFw9npPEIuWEaB16V+c8BupaN5VD1/ KZQvRhF8PxhG2DC6s2BOr7qh4JtrWs+qL7FWAEaxc3rn44mzu14wKQ== =y1qr -----END PGP SIGNATURE----- -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

RE: [SuSE Linux] Upgrading to 2.2.7 and adding 3c905B ethernet but one BIG question is ...
by psims＠lombard.co.uk 07 Jun '99

07 Jun '99

(1)change the symlink /usr/src/linux to point to the new kernel - do this in midnight commander via F9 menu if unsure of syntax of ln. (2) no > -----Original Message----- > From: Jerry Lynn Kreps [SMTP:jlkreps@navix.net] > Sent: Saturday, June 05, 1999 11:01 PM > To: suse-linux-e(a)suse.com > Subject: [SuSE Linux] Upgrading to 2.2.7 and adding 3c905B ethernet > but one BIG question is ... > > > Question #1: > The how-to says to CD to /usr/src/linux and run make menuconfig.... > I've recompiled an existing kernel, but I've never recompiled a new > kernel... > /usr/src/linux is a link to /usr/src/linux-2.2.5.SuSE, so I just can't > CD to /usr/src/linux and do the config, etc... > > So, do I cd /usr/src/linux-2.2.7.SuSE and begin the process and just > ignore the /usr/src/linux link? Will that link interfer with the > recompile? Do I redirect that link to the 2.2.7 directory? > > Question #2; > The 2.2.x kernel has support for the 3c905B-TX NM ethernet card > ("Boomerang") built in. Since I will be connecting that card to a Cisco > 675 router (configurationless ASDL), do I have to have the router on and > working before I compile the kernel? I don't have a loopback cable or a > second box here at home. Would just having the router on and connected > to the ethernet card work, even though it won't be connected to the > phone jack because I don't get connected till Monday. Should I wait > till after the ADSL hookup is completed before I recompile the kernel? > -- > > JLK > Linux, because it's STABLE, the source code is included, the price is > right. > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0

[SuSE Linux] Loading module for scsi card
by JHammer609＠aol.com 07 Jun '99

07 Jun '99

I am new to SuSE but not linux. I have always used a monolithic kernel. I just got the 6.1 release of SuSE and they say you shouldn't rebuild the kernel else whey won't support you in the first 60 days. So, I need to use modules to configure my scsi card for my scanner. In my old lilo.conf I had the following line: append=aha152x=0x340,12,7 which worked very nicely. Now, when I try to load the module for my card, I get device busy error. I don't know the format for loading a scsi module and I haven't yet found a good discussion of modules in the SuSE documentation. I looked in conf.modules but didn't see anything like my scsi card. Any help appreciated. Thanks, Joel -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

1 0