May 2001 - openSUSE Users - openSUSE Mailing Lists

Re: starting scripts. was: [SLE] network conf touchdown !
by Marcel Broekman 04 May '01

04 May '01

---- Begin Original Message ---- From: stephane parenton <sparenton(a)experia.com> Sent: Fri, 04 May 2001 18:28:48 +0200 To: marcelbr(a)zap.a2000.nl CC: suse-linux-e(a)suse.com Subject: Re: [SLE] network conf touchdown ! Marcel Broekman wrote: > > OK! great! > > Did you add this route also to route.conf? I'm > not sure, but i think a simple route add from the > console won't stick after a reboot. Please > correct me if i wrong. no, it won't stick.... But i think that there is a place to put scripts so they are launched at each reboot, after the system launches every needed stuff and before any user can login... I'll add this to route.conf and find the place for the other bits of the script to be launched anyway... Stephane -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com ---- End Original Message ---- Place the scripts in /etc/init.d and make a link to these scripts in rcx.d, where the x is the runlevel you want to execute these scripts. BTW, most of the common stuff will allready be there and you can tweak 'm with Yast. mazzel, Marcel Get your Free E-mail at http://thepenguin.zzn.com ____________________________________________________________ Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.

1 0

Re: [SLE] network conf
by Marcel Broekman 04 May '01

04 May '01

On 04 May 2001 10:00:11 +0200, stephane parenton wrote: > hi... > > I'm using SuSE 7.0 on a p166 box with 2 nics.... eth0 is connected to a router and is the external nic. tr0 is the internal nic but we have an AS/400 that has to be seen from the outside. So this nic has 2 adresses : tr0 is 192.168.0.x and tr0:0 is > xxx.xxx.xxx.xxx. > > Is it normal, when using yast, to have the same gateway adress for both nics ?.... I mean as far as I understand the thing (but I'm quite a newbie...), eth0 should have the router adress as gateway, and the internal nic should have the external as gateway > ?.... Please tell me if I'm wrong, and if I'm not, then why yast doesn't allow me to have these individual gateways for the nics and what can I do to change this ... > > TIA > Stephane > Hi Stephane, The gateway you set with Yast is the default gateway. You can only set one default gateway! It 's not quite clear to me what you are trying to achieve. Do you want to use the SuSE-box as a router for the "outside" to the AS/400 (and vice-versa)? Anyway, you need to add a static route in /etc/route.conf pointing to the other gateway and if you want the SuSE-box to be a router to/from your internal network, you have to enable IP_FORWARD in /etc/rc.config. If you need more info, please explain your network setup a bit more specific. mazzel, Marcel Get your Free E-mail at http://thepenguin.zzn.com ____________________________________________________________ Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.

3 2

Re: Re: [SLE] network conf touchdown !
by Marcel Broekman 04 May '01

04 May '01

OK! great! Did you add this route also to route.conf? I'm not sure, but i think a simple route add from the console won't stick after a reboot. Please correct me if i wrong. Mazzel, Marcel ---- Begin Original Message ---- From: stephane parenton <sparenton(a)experia.com> Sent: Fri, 04 May 2001 17:53:38 +0200 To: marcelbr(a)zap.a2000.nl CC: suse-linux-e(a)suse.com Subject: Re: [SLE] network conf touchdown ! Marcel Broekman wrote: > > Stephane, > > My guess is that the rules on the firewall are > not complete yet. You have to allow access from > the lan network to the internet and the > NAT-network. If i'm correct, you can check if the > packages are dropped/denied by the firewall in > the firewall logfile (/var/log/ ). well, i'll check that also, but jeffrey taylor did answer me about the routes... I've added route add 192.168.0.x gw xxx.xxx.xxx.aaa (the eth0 ip) and here it works at least.... now i can take a rest and tune the system more precisely.... thank you everyone for answering..... Regards Stephane Parenton -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com ---- End Original Message ---- Get your Free E-mail at http://thepenguin.zzn.com ____________________________________________________________ Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.

2 1

sax2 no longer works
by Jerry Davis 04 May '01

04 May '01

sax2 no longer works. it comes up the prompt to use the configuration <yes> | no --> and I press CR or type yes (either way) it prints startup on the terminal but then comes right back to the prompt why? it worked before when I installed? I wanted to add 3d hw acceleration for my G400 and I can't seem to bring sax2 up to add it. Jerry -- Boycott the outlaw Microsoft - and use Linux - the Software that gives you Freedom to choose!

3 3

Re: Re: [SLE] network conf one down one to go
by Marcel Broekman 04 May '01

04 May '01

Stephane, My guess is that the rules on the firewall are not complete yet. You have to allow access from the lan network to the internet and the NAT-network. If i'm correct, you can check if the packages are dropped/denied by the firewall in the firewall logfile (/var/log/ ). Mazzel, Marcel ---- Begin Original Message ---- From: stephane parenton <sparenton(a)experia.com> Sent: Fri, 04 May 2001 16:11:56 +0200 To: marcelbr(a)zap.a2000.nl CC: suse-linux-e(a)suse.com Subject: Re: [SLE] network conf one down one to go Marcel Broekman wrote: > The gateway you set with Yast is the default > gateway. You can only set one default gateway! It > 's not quite clear to me what you are trying to > achieve. Do you want to use the SuSE-box as a > router for the "outside" to the AS/400 (and > vice-versa)? ok, now this problem is solved, for I can ping the outside world from my box.... still I have another problem ,that I intentionnaly keep vague, for I want to verify thinks by myself before being precise.... and therefor guided by the hand :))) Suse 7.0 box is xxx.xxx.xxx.aaa Another1 box is xxx.xxx.xxx.bbb Another2 box is xxx.xxx.xxx.ccc the Suse box has 2 nics, the eth0 is external and is connected to a router directly to the net, the tr0 is internal and links to the nat'ed lan. >From the box : I ping eth0, tr0, another1 and another2 as well as the outside world, and the computer on the nat'ed lan (192.168.0.x). This is ok.... From the outside world : I see Suse 7.0, another1 and another2 which is fine... From the inside (lan), I can ping the SuSE box, but NOT another1 and another2.... and not the outside world... I have modified my etc/route.conf, I run a script that run rules for ipchains.... The point is : I want to know what files to check to see what is wrong .... The SuSE box replaces a "RH6.0 another0" box (this box runs fine when connected) that should be no longer connected.... what files must I check in order to solve the problem (any files related to the problem....). I certainly have missed something, but what and where I don't know... i've checked and checked, but maybe i overlooked and didn't see the evidence.... and missed the one file that could be helpfull TIA Stephane Parenton -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com ---- End Original Message ---- Get your Free E-mail at http://thepenguin.zzn.com ____________________________________________________________ Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.

2 1

KDE Zombies
by NOC - Kulish Consulting 04 May '01

04 May '01

I am getting the following reported via top. What exactly does this mean, and what can I do about it? 401 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 402 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 403 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 404 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 406 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 411 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct 413 root 0 0 0 0 0 Z 0 0.0 0.0 0:00 kde <defunct Thanks! Chris Kulish

1 0

Re: [SLE] Does Realtek 8139 chip work with kernel 2.4.2?
by Purple Shirt 04 May '01

04 May '01

well I don't compile kernels myself anymore since suse is always ahead of stock kernel.org kernel's. it makes no sense to compile some kernel to get some useless feature if it breaks your system (see reiserfs in suse 6.4). I used suse compiled kernel and it works. >From: Paul Abrahams <abrahams(a)acm.org> >To: SuSE listserve <suse-linux-e(a)suse.com> >Subject: Re: [SLE] Does Realtek 8139 chip work with kernel 2.4.2? >Date: Fri, 04 May 2001 10:02:47 -0400 > >Purple Shirt wrote: > > > I don't know but I got a rtl8139 card working with 2.4.2 and I never had >to > > change anything in modules.conf. I'd check what is in modules.conf but I > > don't have access to the machine right now. > > > > The module is called rtl8139.o and I don't think 8139too will work. The >card > > worked right off the bat for me. > > /lib/modules/2.4.2-4GB/kernel/drivers/net > >This whole topic has been the subject of massive confusion for me. The >2.4.2 >kernel sources don't include an rtl8139.c file (or rtl8139.o for that >matter) >since the kernel gurus have decided to go with the 8139too driver. The >diskette that came with my network card includes an rtl8139.c file, which I >copied to /usr/src/linux/drivers/net (the same directory where 8139too.c >lives). But when I tried to compile rtl8139.c in various ways, including >using the makefile on the diskette, I got lots of compilation errors and no >rtl8139.o file. > >It's possible that rtl8139.c has to be compiled in the context of the 2.2.x >kernel sources. I haven't tried that, especially since I now have an >up-to-date kernel and the things that are the first not to work are >working. > >I've solved the problem now in a different way, which works so far. I've >installed the stock (from kernel.org) 2.4.4 kernel (and, of course, the >newer >modutils). Both networking and sound are working. Sound might have been >a >problem because of some difficulties with alsa, but it wasn't. Of course, >there's no telling when something else might show up as a nasty problem. > >Paul > > > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/support/faq and the >archives at http://lists.suse.com > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

1 0

Re: [SLE] Does Realtek 8139 chip work with kernel 2.4.2?
by Purple Shirt 04 May '01

04 May '01

I don't know but I got a rtl8139 card working with 2.4.2 and I never had to change anything in modules.conf. I'd check what is in modules.conf but I don't have access to the machine right now. The module is called rtl8139.o and I don't think 8139too will work. The card worked right off the bat for me. /lib/modules/2.4.2-4GB/kernel/drivers/net mk >From: Paul Abrahams <abrahams(a)acm.org> >To: "SuSE listserve ." <suse-linux-e(a)suse.com> >Subject: Re: [SLE] Does Realtek 8139 chip work with kernel 2.4.2? >Date: Thu, 03 May 2001 22:42:04 -0400 > >Purple Shirt wrote: > > > I may be wrong but did you turn on the network card using yast? Are you > > doing this by hand or using yast to set the card up. I did an >installation > > using 2.2 kernel the other day. I set up the network card. Then I >installed > > 2.4 kernel and the network card would fault on me. I went into yast and >the > > settings were gone. It was like I had to set the card up twice, once for >2.2 > > and once for 2.4. > >Yast merely writes an appropriate alias to the modules.conf file. >Actually, >in the case of this card the alias isn't quite right . Yast writes > > alias eth0 rtl8139 > >rather than > > alias eth0 8139too > >The SuSE website has a page on this subject, noting that 8139too is what >should >be used with 2.4.x kernels. > >In any event, switching kernels normally does not modify /etc/modules.conf. > >Paul Abrahams > > > >-- >To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com >For additional commands send e-mail to suse-linux-e-help(a)suse.com >Also check the FAQ at http://www.suse.com/support/faq and the >archives at http://lists.suse.com > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

4 4

Re: SuSE pricing and upgrades
by Andrei Verovski 04 May '01

04 May '01

Hi, I am completely agree, upgrade pricing is meaningless. If I would buy all upgrades, SuSE Linux (x86 + PPC) would cost me $400/year (roughly $100 for each quarterly version), including shipment cost. I cannot say it is very cheap. So, am agree to buy full pro version (x86 + PPC) once a year (and already did), and then 3 quarterly upgrades for $15 or so. I just do not need manuals for each upgrade, I see no reasons to waste a paper. I am understand that SuSE GmbH somehow have to survive and continue development, but I am not sure $400/year is a reasonable price for Linux distribution, albeit a very good one. Andrei

1 0

SuSE 7.1 PPC Download
by Andrei Verovski 04 May '01

04 May '01

Hi, Anyone knows when SuSE 7.1 PPC will be available for download? Thanks Andrei

1 0