- openSUSE Users

[S.u.S.E. Linux] News Server Authentication, error 502
by zentara＠mindspring.com 01 Feb '98

01 Feb '98

Hi, Well I'm trying to get News going. I'm used to Agent under windows, and I have used it under Wabi with some minor drawbacks. I would like to get Knews or Xrn going, they connect but return either ---error 502, authentication failed or --- failed to get list I'm sure this is the authentication problem. Is there a way around this? I have seen mention of a perl module that will log on to newsserver requiring authentication. Anyone know anything about this? Is a perl script available that I can use to log on then , launch Knews? I don't want to go back to wabi and agent, it requires that Xkeyboard is disabled, and it makes the backspace key useless in X. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[S.u.S.E. Linux] Pap, PPP,and EZPPP...my luck
by zentara＠mindspring.com 01 Feb '98

01 Feb '98

Hi, The docs for ppp-up don't give alot of attention to logins using pap. I've just set it up very easily with EZPPP. These are the basic steps: AS root you must 1. chmod 666 /etc/resolv.conf 2. chmod 666 /dev/modem 3. chown root.root /usr/sbin/pppd 4. chmod 555 /usr/sbinpppd 5. chmod +s /usr/sbin/pppd 6. you must empty /etc/ppp/options to a zero file, since it interferes with ezppp 7. put any users who can dialout in the dialout group 8. put the ezppp binary in each dialout users home directory and let them own it. 9. Set up the /etc/ppp/pap-secrets file: For example at Mindspring: ***************************************************** #pap-secrets # client server secret ip ms999999 mindspring yuk2yak ***************************************************** Then set up the pppd arguments in ezppp: Here is the script that works perfectly: -detach defaultroute lock modem noipdefault user ms999999 remotename mindspring This script probably could be adapted to work with ppp-up, but ezppp is so easy, I have no urge to try. It will probably work with kppp under KDE. I'm going to try it later. Well this works great for me. I don't know what the security implications are of the chmod's and chown's. Since the user is owner of the binary, I doubt if it can do much havoc. Please write if you see a flaw in this. I really barely know the basics of security. zentara -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: R: [S.u.S.E. Linux] ESS Audio 1878
by marca＠netscout.com 01 Feb '98

01 Feb '98

Guys: I have an ESS-1888 card in my Gateway 2200 Laptop that runs just fine. I don't know if the stand alone cards are any different, but I downloaded the OSS/Free sound libraries from www.4front.com, recompiled the kernel (using irq 5 instead of 7, the rest defaults) and the sound works great! marc. "Moreno Daltin" <daltin(a)tin.it> on 12/31/97 10:16:57 AM Please respond to suse-linux-e(a)suse.com To: suse-linux-e(a)suse.com cc: (bcc: Marc Abrams) Subject: R: [S.u.S.E. Linux] ESS Audio 1878 -----Messaggio originale----- Da: M.J.Medjeral <seamar(a)singnet.com.sg> A: suse-linux-e(a)suse.com <suse-linux-e(a)suse.com> Data: domenica 1 febbraio 1998 0.31 Oggetto: [S.u.S.E. Linux] ESS Audio 1878 > >In SuSE Linux 5.1 has anybody had luck configuring sound with >ESS Audio 1878? >Regards >Mario Jose Medjeral Would like to know too.... :-( -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Package upgrade question
by wtopa＠ix.netcom.com 01 Feb '98

01 Feb '98

Subject: Re: [S.u.S.E. Linux] Package upgrade question Date: Sun, Feb 01, 1998 at 01:40:46PM -0500 In reply to:Luis A. Costabile Quoting Luis A. Costabile (luis(a)lac.resonet.com) > > > On Sun, 1 Feb 1998, Wayne Topa wrote: > > > compiled it , and installed via the mutt make file (/usr/local/bin). > > When I tried to run the new mutt I got an odd error, /usr/bin/mutt > > no such file or directory. Of course /usr/local/bin/mutt worked fine. > > On rebooting the system, the next day, mutt worked as expected. > > > > It seems like SuSE works differently then other distributions I am > > used to. As /usr/local/bin is in my path, I expected the program to > > Maybe the install script changed the PATH environment on you. Should not > need to reboot, maybe next time just try logging out and in to re-instate > your profile. > No, I checked $PATH and it had not changed. I have since found /sbin/SuSEconfig which I think may have solved the problem(?). I think the key here is the message I got then I entered mutt. ie /usr/bin/mutt no such file or directory. Something KNEW that mutt used to be there and that it wasn't any more. That is very different then I have seen before! I wonder why SuSE has changed the way normal Unix's work(???). > > -- > Lou A. Costabile Voice and Fax: [613] 781-7061 > <A HREF="mailto:luis@lac.resonet.com">mailto:luis@lac.resonet.com</A> > To get Receipt Notification include %rec% anywhere in the Subject field. > > You must restart your computer before the new message will take effect. > Do you want to restart your computer now? Yes or Yes > -- > > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Package upgrade question
by stugreen＠bga.com 01 Feb '98

01 Feb '98

Luis, There is a package (/cdrom/suse/a1/eazy.rpm) that provides the appearance of an fssstd file system layout. Once installed, downloading, decompressing and installing packages in .tgz, .tar or .gz format is more easily accomplished. The package has been include for the purposes of compatibility, it needs to be manually selected at installation or installed manually following installation. Regards, Stu -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] Package upgrade question
by luis＠lac.resonet.com 01 Feb '98

01 Feb '98

On Sun, 1 Feb 1998, Wayne Topa wrote: > compiled it , and installed via the mutt make file (/usr/local/bin). > When I tried to run the new mutt I got an odd error, /usr/bin/mutt > no such file or directory. Of course /usr/local/bin/mutt worked fine. > On rebooting the system, the next day, mutt worked as expected. > > It seems like SuSE works differently then other distributions I am > used to. As /usr/local/bin is in my path, I expected the program to Maybe the install script changed the PATH environment on you. Should not need to reboot, maybe next time just try logging out and in to re-instate your profile. -- Lou A. Costabile Voice and Fax: [613] 781-7061 <A HREF="mailto:luis@lac.resonet.com">mailto:luis@lac.resonet.com</A> To get Receipt Notification include %rec% anywhere in the Subject field. You must restart your computer before the new message will take effect. Do you want to restart your computer now? Yes or Yes -- -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

R: [S.u.S.E. Linux] ESS Audio 1878
by daltin＠tin.it 01 Feb '98

01 Feb '98

-----Messaggio originale----- Da: M.J.Medjeral <seamar(a)singnet.com.sg> A: suse-linux-e(a)suse.com <suse-linux-e(a)suse.com> Data: domenica 1 febbraio 1998 0.31 Oggetto: [S.u.S.E. Linux] ESS Audio 1878 > >In SuSE Linux 5.1 has anybody had luck configuring sound with >ESS Audio 1878? >Regards >Mario Jose Medjeral Would like to know too.... :-( -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[S.u.S.E. Linux] Package upgrade question
by wtopa＠ix.netcom.com 01 Feb '98

01 Feb '98

SuSE 5.1 Question. As 5.1 includes mutt-0.85 and I had been using mutt-0.88 (on Slackware) I decided to upgrade mutt. I used yast to remove the mutt-0.85 package. I then downloaded the new version, (.tar.gz), compiled it , and installed via the mutt make file (/usr/local/bin). When I tried to run the new mutt I got an odd error, /usr/bin/mutt no such file or directory. Of course /usr/local/bin/mutt worked fine. On rebooting the system, the next day, mutt worked as expected. It seems like SuSE works differently then other distributions I am used to. As /usr/local/bin is in my path, I expected the program to run, WITHOUT a reboot. SuSE does something different. As I have not finished the 5.1 book it is possible that the answer lies there but as this is so much different than I am used to, I thought that it might be helpful, to the list, if this might be explained. Thanks Wayne -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

Re: [S.u.S.E. Linux] A few Simple questions for a Suse newbie
by brauki＠cww.de 01 Feb '98

01 Feb '98

zentara wrote: > > Juergen Braukmann wrote: > > > zentara wrote: > > > > > > Hi, > > > I'm trying to move from Caldera to Suse. > > > All is going fairly well , except for a few things. > > > > > > 1. Where is my .bashrc file ? There isn't one in the root directory? > > > Why does Suse do it different? Do I just create my own? > > > > a .bashrc file should be in your home directory. if it is not there > > create it. > > > > Hi, thanks guys for the tips. I did get the widgets out by edit the.fvwm2rc > file. But I guess I should use KDE for "drag and drop". > Although the empty fvwm2 desktop sure is nice; I'll just have > to figure out how to add my programs to the menus. > just read the configuration file. after a while it gets clear how to do things. I added a few features myself, but as I pointed out earlier, as soon as I regenerate a .fvwm*rc all is gone and has to be replaced again by hand. > I still have one problem which perplexes me. I have the .bashrc files > in my root and user directories, but it dosn't affect the root bash. hmmm. I have seen that on our SINIX system at work. root is trated differently. maybe there is some file in /etc that contains info about this, what I did on SINIX was quite obvious: I added an other entry in /etc/profile that is (hopefully) run for every terminal login. disadvantage: this sets the editor for everyone. > Let me clarify. > Being a beginner, I prefer to use Joe as my editor, instead of the default > vi. I basically use Midnight Commander for everything. If I put the line > "export EDITOR= /usr/bin/joe" in the .bashrc file, Joe will open up > my files in MC when I hit the F4 button. > This works fine for my user's home directories. > However, when I put it in the root's .bashrc ; vi still comes up > when root hits MC's F4 button. > What am I missing? > I know it pays to know vi, but I prefer joe. it realy pays. i prefer asedit from X. my knowledge of vi -although I use it much- is almost zero. Jürgen -- ========================================== __ _ Jürgen Braukmann e-mail: brauki(a)cww.de | / / (_)__ __ ____ __ Tel: 0201-743648 dk4jb(a)db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / ========================================== /____/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0

[S.u.S.E. Linux] Package question (SuSE)
by wtopa＠ix.netcom.com 01 Feb '98

01 Feb '98

Just found an interesting command, which is new to me, tcpdchk, it checks out the inetd file for errors. Mine ( from SuSE 5.1) seems to have a few errors that I wonder if SuSE might know about: > tcpdchk warning: /etc/inetd.conf, line 91: /usr/lib/xcept4/bin/ceptd: not found: No such file or directory warning: /etc/inetd.conf, line 99: in.midinetd: not found in /usr/sbin: No such file or directory As of now they are not affecting me (I don't think ?) but you never know. They are probably for some package I haven't loaded but thought Yast would handle that as part of the configuration administration(?). Also found that there are no man pages or Info files for inetd.conf(5) and tlid.conf(5). I found this out while reading up on tcpdck. SuSE guys, are these available on your site somewhere?? Thanks Wayne -- To get out of this list, please send email to majordomo(a)suse.com with this text in its body: unsubscribe suse-linux-e

1 0