July 1999 - openSUSE Users - openSUSE Mailing Lists

Protection from intruders
by gh＠simteam.com 30 Jul '99

30 Jul '99

Hi, I'm linked to the internet trough a cable modem ( motorola cyber surf) what I would like to know is: Can I protect myself against potetial intruders ?? What is my level of exposure. I have a single machine which is my workstation at the end of this install, I never work as root except when needed root has a complex passsword remote login is forbidden for root , "." is not in the root password that s all for now. the ISP is supposed to protect my comms between him and I. I m looking for any kind of advices. regards GH Portefait -- "Computers are like air conditioners - they stop working properly when you open Windows" -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CC d-@ s+:- C++(++++)UL++>++++ P++>++++ L++>+++ E-W+(++) N++ !o K- w !O M(++) V? !PS !PE y+ PGP+++ t+ 5? X R* tv b+ DI? D+ G+++ e+++ h+ r y? ------END GEEK CODE BLOCK------ http://www.geekcode.com

8 9

Re: [SLE] Tar's and File Choppers
by Michael.Salmon＠uab.ericsson.se 30 Jul '99

30 Jul '99

+----- On Thu, 29 Jul 1999 21:58:04 PDT, "Jon Pennington" writes: | Is there a way to divide a tar file (or any file, for that matter) into | 95-meg files? I'd like to take an ISO CD-ROM image and put it onto Zip | disks, but I've never seen anything that was a drop-and-run solution. plit usually does the job. /Michael

1 0

Sendmail connection errors
by dward＠basair.com.au 30 Jul '99

30 Jul '99

Using Sendmail 8.9.3, I keep getting lots of these sorts of messages: Jul 24 00:46:57 server sendmail[32297]: AAA32297: collect: premature EOM: Connec tion reset by fepa.mail.ozemail.net Jul 23 16:37:19 server sendmail[30719]: QAA30719: SYSERR(root): collect: I/O err or on connection from fep7.mail.ozemail.net, from=<abc(a)abc.com>: Connection reset by fep7.mail.ozemail.net It only seems to happen with some servers. Does anyone know if I have something configured incorrectly? Regards, Darrin Ward, Chief Flying Instructor, Basair Australia. dward(a)basair.com.au http://www.basair.com.au Phone (+612) 9791 0111 Fax (+612) 9791 0065 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HEAD> <META content="text/html; charset=us-ascii" http-equivntent-Type> <META content="MSHTML 5.00.2014.210" name=GENERATOR></HEAD> <BODY bgColor=#ffffff> <DIV><FONT face="Courier New" sizeUsing Sendmail 8.9.3, I keep getting lots of these sorts of messages:</FONT></DIV> <DIV> </DIV> <DIV><STRONG><FONT face="Courier New" sizeJul 24 00:46:57 server sendmail[32297]: AAA32297: collect: premature EOM: Connection reset by fepa.mail.ozemail.net</FONT></STRONG></DIV> <DIV> </DIV> <DIV><FONT face="Courier New" size<STRONG>Jul 23 16:37:19 server sendmail[30719]: QAA30719: SYSERR(root): collect: I/O error on connection from fep7.mail.ozemail.net, from=<<A href="mailto:abc@abc.com">abc(a)abc.com</A>>: Connection reset by fep7.mail.ozemail.net</STRONG></FONT></DIV> <DIV> </DIV> <DIV><FONT face="Courier New" sizeIt only seems to happen with some servers.</FONT></DIV> <DIV> </DIV> <DIV><FONT face="Courier New" sizeDoes anyone know if I have something configured incorrectly?</FONT></DIV></BODY> Regards, Darrin Ward, Chief Flying Instructor, Basair Australia. dward(a)basair.com.au http://www.basair.com.au Phone (+612) 9791 0111 Fax (+612) 9791 0065

1 0

RE: [SLE] The Linux Declined and SETI@home
by kpeiruza＠lgcirsa.com 30 Jul '99

30 Jul '99

----- Original Message ----- From: <mlmayo(a)texas.net> To: <chris(a)kulish.com> Cc: <suse-linux-e(a)suse.com> Sent: Friday, July 30, 1999 5:51 AM Subject: Re: [SLE] The Linux Declined and SETI@home > > > > > Hello Chris, > > If you have a pentium or K6 use the i386, for PII and above use the i686 > versions. As for gnulibc I'm using setiathome-1.3.i386-pc-linux-gnu-gnulibc2 > 1.tar on SuSE 6.1 on a K6-333 > And what about K6-II? > > > Hope this helps, > Mike > > > > On Thu, 29 Jul 1999, Chris wrote: > > > > > Quick question. I want to run the seti@home <mailto:seti@home> client > on > my new Linux box but I am unsure of the gnulibc(?) version that SuSE > 6.1 is > > > using. If anyone has gotten this to work, please drop me a line. > > > > > > TIA > > Chris > > > > > > > > -- > To unsubscribe, e-mail: suse-linux-e-unsubscribe(a)suse.com > For additional commands, e-mail: suse-linux-e-help(a)suse.com > > > ---------------------------------------------------------------------------- ---- >

1 0

[Fwd: Re: [SLE] Run at Boot]
by sgroarke＠nortelnetworks.com 30 Jul '99

30 Jul '99

Ooops, almost forgot one other thing. EITHER: 1) Edit /etc/rc.config and insert a 'START_MYDAEMON=yes' 2) SuSEconfig OR 1) Comment out the two test lines in the header of your file mydaemon - the ones that check to see if START_MYDAEMON are set to yes. Sorry... Sean -------- Original Message -------- Subject: Re: [SLE] Run at Boot Date: Fri, 30 Jul 1999 08:29:45 +0200 From: Sean Groarke <sgroarke(a)nortelnetworks.com> Reply-To: Sean Groarke <sgroarke(a)nortelnetworks.com> Organization: Nortel Networks EMEA To: "suse-linux-e(a)suse.com" <suse-linux-e(a)suse.com> This is something I got to grips with for the first time a few weeks ago, so while it's still fresh in my mind, here's my newbie recollections of how to do it: 1) As root, go to /sbin/init.d 2) Take the skeleton file, copy it into the same diretory as something sensible (let's say 'mydaemon'). Or copy one of the other existing files in the directory. 3) Edit mydaemon - at first sight, it looks hairy, but look more closely and there's actually very little to change in it. The minimum you really need IMHO is: a) Change the 'FOO's to 'MYDAEMON' in the header area. b) Edit for the 'start' option: (i) foo -> mydaemon (ii) Uncomment the startproc line (iii) Change the startproc line to reflect your program. c) Similarly for the 'stop' option, but this time it's a killproc you edit. d) If you feel so inclined, do similar stuff for restart, reload, status, probe - although the first time I did this I just commented them all out! 4) Now you have a single file, 'mydaemon' in /sbin/init.d. Don't go doing what I did - trying to drop copies and links to in into the /sbin/init.d/rc2.d type directories.... 5) Now the really neat bit: do 'rctab -e'. This drops you into the editor, with a table of all the different startup tasks in columns, where each column reflects a different run level. This sounds complex, but is actually very simple when you do it. Now simply go to the bottom of the column for, say, run level 2 and 3, and insert 'mydaemon' in place of the dashes that are currently there. 6) Do a normal vi :wq to leave the editor, and you will now find that in (in this case) rc2.d and rc3.d there are now magically Snnmydaemon and Knnmydaemon links, back up to your original file. 7) That's about it! Do an 'init s' then back up with 'init 2' and see what happens. I hope you feel as satisfied as I did when this first worked for me...!!! Cheers, Sean > >-------- Original Message -------- >Subject: [SLE] Run at Boot > Date: Thu, 29 Jul 1999 21:50:38 -0500 > From: Chris <chris(a)kulish.com> > To: SuSE Email List <suse-linux-e(a)suse.com > > > Ok, I tried to run something at boot (boot.local), with one problem.It seems that it was running >before the network drivers >were loaded.I need this daemon to run at runlevel 2(?), whichever is the last one it reaches before it >drops you to the login prompt. > > TIA > > > CK -- To unsubscribe, e-mail: suse-linux-e-unsubscribe(a)suse.com For additional commands, e-mail: suse-linux-e-help(a)suse.com

1 0

RE: [SLE] Re: [suse-linux-e] networking...
by psims＠lombard.co.uk 30 Jul '99

30 Jul '99

make sure that your interface is defined in smb.conf > -----Original Message----- > From: Teresa D. Dodson [SMTP:tdodson@rapidnet.com] > Sent: Friday, July 30, 1999 8:25 AM > To: Greg Thomas > Cc: suse-linux-e(a)suse.com > Subject: Re: [SLE] Re: [suse-linux-e] networking... > > Hi, > > I would supply more information, but since my last attempt to get it to > work(a couple of weeks ago and before I joined this list), I have some > how completely broken it. I can't see my Samba server from the NT/Win95 > side now at all. I am going to start from scratch again and see what > happens. If I get completely stuck again, I will document errors and all > and submit them. I appreciate all the responses from everyone. This > leaves me very hopeful that I will get this up and going with everyone's > help. Thanks. > > Teresa > > Greg Thomas wrote: > > > > Need a bit more info here. What arguments are you giving to smbmount > when > > you try to mount a Windows share from Linux? Also, for Dave's Mac issue > > he would need to install client software on the Macs to access Windows > > shares (I believe one of the programs is called Dave). > > > > Greg > > > > On Wed, 28 Jul 1999, Teresa D. Dodson wrote: > > > > > I too have had problems with that. I have been able to get my Windows > > > machines to see and work with my box but I can not get my linux box to > > > do it the other way around. Any help on this matter would be > > > appreciated. > > > > > > Dave Kelly wrote: > > > > > > > > I've got a bit of a problemette at the moment. Our network is an > amalgamation > > > > of Windows 9x, Windows NT (Workstation and Server), SuSE Linux and > MacOS > > > > machines. The Windows machines are all on a TCP/IP ethernet, with > the MacOS > > > > machines on their own little AppleTalk network. The Linux machines > are NFS/NIS > > > > sharing to each other. I'd like to integrate all of the different > networks > > > > into one, so that all of the resources are sharable. > > > > > > > > I've begin to do this by moving over to TCP/IP. I've been trying to > use Samba, > > > > and have successfully managed to get Windows to connect to a Linux > machine. > > > > The other way around, however, is a big no-no. I can't, and I've > tried many > > > > times, to get Linux to access a Windows share. I have yet to try it > with > > > > MacOS, but expect the same, if not more, problems. > > > > > > > > Any suggestions as to how I can get the Linux boxes to see Windows? > I need all > > > > of the machines, and can't move them all to Linux (much to my > despair). Any > > > > help would be appreciated! > > -- > To unsubscribe, e-mail: suse-linux-e-unsubscribe(a)suse.com > For additional commands, e-mail: suse-linux-e-help(a)suse.com

1 0

Tar's and File Choppers
by jon_pennington＠excite.com 30 Jul '99

30 Jul '99

Is there a way to divide a tar file (or any file, for that matter) into 95-meg files? I'd like to take an ISO CD-ROM image and put it onto Zip disks, but I've never seen anything that was a drop-and-run solution. Any ideas/thoughts/flames? :) -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.0 jon_pennington(a)excite.com | Kernel 2.2.7+ Kansas City, Missouri, USA | K6-2 350 ________________________________________________________________ Get FREE voicemail, fax and email at http://voicemail.excite.com Talk online at http://voicechat.excite.com

2 1

Re: [SLE] Printing + Zip
by rjohns＠otenet.gr 30 Jul '99

30 Jul '99

Hi, If your 720c is like my 722 and the 820 you need to check out - http://www.httptech.com/ppa/software.html You need a special driver to be able to print with my 722 it is a bit of a pain to set up. I still haven't gotten everything perfectly straight but I have been trying for a couple of weeks and I am a Linux neophyte. By the way, color support is only at the alpha stage. Rod -----Original Message----- From: Alexandre Maneu i Victòria <nexus.mansoft(a)ctv.es> >Hello. > >Surely the problem regarding printers and parallel port zip drives has been >discussed before. I also think there's a web at www.torque.net, but I can't >remember well. Anyway, I'll ask you the question :-) > >As I told you in my last message, I use SuSE 5.3, with kernel 2.2.10. I've >tried to recompile the kernel so that it supports my parallel zip drive and >my printer. I've tried nearly everything (including all the options in the >kernel, compiling them as modules...) but nothing works. > >My printer is a HP 720c. It seems I have configured my "printcap" ok with >YaST, but the thing is that it doesn't print. >When I try to print sth with the lpr command, and then do "lpq" to see the >queue, at the top it says "Waiting for printer (offline?)". Of course my >printer is on when I try to print or to see the queue. > >How can I configure my kernel or whatever so that it works? (if you think >it's better to give me the URL I won't have any problems; I'm a bit lost >with this subject so any help is very useful). > >Regards, >

1 0

Re: [SLE] Pt. II ATAPI zip drive mounting;
by rjohns＠otenet.gr 30 Jul '99

30 Jul '99

>> 1) My ATAPI ZIP drive (hdd) Is now mounted! Thanks everybody The entry in fstab was changed from "/dev/hdd" to "/dev/hdd4" and everything worked perfectly. Rod

1 0

Re: [SLE] Run at Boot
by sgroarke＠nortelnetworks.com 30 Jul '99

30 Jul '99

This is something I got to grips with for the first time a few weeks ago, so while it's still fresh in my mind, here's my newbie recollections of how to do it: 1) As root, go to /sbin/init.d 2) Take the skeleton file, copy it into the same diretory as something sensible (let's say 'mydaemon'). Or copy one of the other existing files in the directory. 3) Edit mydaemon - at first sight, it looks hairy, but look more closely and there's actually very little to change in it. The minimum you really need IMHO is: a) Change the 'FOO's to 'MYDAEMON' in the header area. b) Edit for the 'start' option: (i) foo -> mydaemon (ii) Uncomment the startproc line (iii) Change the startproc line to reflect your program. c) Similarly for the 'stop' option, but this time it's a killproc you edit. d) If you feel so inclined, do similar stuff for restart, reload, status, probe - although the first time I did this I just commented them all out! 4) Now you have a single file, 'mydaemon' in /sbin/init.d. Don't go doing what I did - trying to drop copies and links to in into the /sbin/init.d/rc2.d type directories.... 5) Now the really neat bit: do 'rctab -e'. This drops you into the editor, with a table of all the different startup tasks in columns, where each column reflects a different run level. This sounds complex, but is actually very simple when you do it. Now simply go to the bottom of the column for, say, run level 2 and 3, and insert 'mydaemon' in place of the dashes that are currently there. 6) Do a normal vi :wq to leave the editor, and you will now find that in (in this case) rc2.d and rc3.d there are now magically Snnmydaemon and Knnmydaemon links, back up to your original file. 7) That's about it! Do an 'init s' then back up with 'init 2' and see what happens. I hope you feel as satisfied as I did when this first worked for me...!!! Cheers, Sean > >-------- Original Message -------- >Subject: [SLE] Run at Boot > Date: Thu, 29 Jul 1999 21:50:38 -0500 > From: Chris <chris(a)kulish.com> > To: SuSE Email List <suse-linux-e(a)suse.com > > > Ok, I tried to run something at boot (boot.local), with one problem.It seems that it was running >before the network drivers >were loaded.I need this daemon to run at runlevel 2(?), whichever is the last one it reaches before it >drops you to the login prompt. > > TIA > > > CK

1 0