December 1998 - openSUSE Users - openSUSE Mailing Lists

Re: [SuSE Linux] TX Pro motherboard :-(
by kester＠cwcom.net 15 Dec '98

15 Dec '98

Whoops, that should be M577 not M5770, but I guess it makes no difference... k. -----Original Message----- From: Kester Clegg <kester(a)cwcom.net> To: suse-linux-e(a)suse.com <suse-linux-e(a)suse.com> Date: 15 December 1998 09:58 Subject: Re: [SuSE Linux] TX Pro motherboard :-( > >Aaargh, my computer company (UK Campus Computers) have ripped me off with >the above cheap motherboard (PC100 AGP Pro M5770) instead of the DFI one I >wanted on a brand new machine. But the question now is whether the UDMA on >the Seagate hard drive is supported - does anyone know of a patch anywhere, >or if the kernal with SuSe 5.3 will support this motherboard? Should I ring >up and start screaming at the company or will everything work just fine? >(Bear in mind that the company is unlikely to change anything - shucks, they >didn't even send me an invoice / bill / receipt of any kind!). > >Kester Clegg >York, UK > >kester(a)mcmail.com > >--------------------------------------------------------------------------- - >------------ >Linux Lovers do it in the Open.... >--------------------------------------------------------------------------- - >------------ > >- >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 >archiv 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 archiv 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

[SuSE Linux] Masquerading not working..
by Maqish＠wish.net 15 Dec '98

15 Dec '98

Hello all.. i finally have a normal link between mij win98 pc and linux so samba is finally working.. but now i cannot seem to get linux working well with that masquerading stuff.. i read a few how-to's but still it won't work... please help me - 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 archiv 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] wvdial tip: "Stupid Mode = yes"
by zentara＠netfrog.net 15 Dec '98

15 Dec '98

Hi, Since wvdial is getting so popular, I thought I would share this tip I came across yesterday. I changed my isp, and my new isp wouldn't let wvdial do it's conventional heuristic login. But in the release notes, it mentions "Stupid Mode =yes", which is placed in wvdial.conf. This just forces wvdial to send pap-secrets and start pppd immediately. This worked. It also prevents the password from being shown on screen. It does need the pap-secrets written properly though. Wvdial will do this automatically the first time it runs, as long as the file permission on pap-secrets is set to allow group read-write. You can also write the pap-secret manually, and leave permission set to read-write by root only. In that case wvdial will work, and report a flaky pap-secret file. The pap-secret file should look as follows: username * password - 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 archiv 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] TX Pro motherboard :-(
by kester＠cwcom.net 15 Dec '98

15 Dec '98

Aaargh, my computer company (UK Campus Computers) have ripped me off with the above cheap motherboard (PC100 AGP Pro M5770) instead of the DFI one I wanted on a brand new machine. But the question now is whether the UDMA on the Seagate hard drive is supported - does anyone know of a patch anywhere, or if the kernal with SuSe 5.3 will support this motherboard? Should I ring up and start screaming at the company or will everything work just fine? (Bear in mind that the company is unlikely to change anything - shucks, they didn't even send me an invoice / bill / receipt of any kind!). Kester Clegg York, UK kester(a)mcmail.com ---------------------------------------------------------------------------- ------------ Linux Lovers do it in the Open.... ---------------------------------------------------------------------------- ------------ - 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 archiv 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

[SuSE Linux] jpeg and SUSE 5.3 errors - ???
by deem＠wdm.com 15 Dec '98

15 Dec '98

I grabbed the source for XNC to compile my own and it pukes at : /src/xnc/jpeg -ljpeg image/libie.a(jpeg.o): In function `LoadJFIF': jpeg.o(.text+0x156): undefined reference to `jpeg_create_decompress' make: *** [nc] Error 1 Is this due to the lib upgrades in 5.3 ? Any workaround ? XNC source is at <A HREF="http://www.xnc.dubna.su/downloads.html"><A HREF="http://www.xnc.dubna.su/downloads.html</A">http://www.xnc.dubna.su/downloads.html</A</A>> -Dee W.D.McKinney (Dee) deem(a)wdm.com Faith is acting on your passions & beliefs. - 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 archiv 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

[SuSE Linux] Intermittent boot hang
by jkarns＠ares.csd.net 15 Dec '98

15 Dec '98

I have experienced a problem where the machine hangs just after the volumes are mounted and (I believe) the network interface line is displayed (refers to eth0). This has occurred on three different boxes, all with SuSE 5.1. Two of the mchines are virtually identical (different kernel config's) and have a K6/300 mobo. The other is a P166. All have 3Com 3c509b ethernet cards. I have looked at the logs, but can't see the line about eth0, since the kernel logging stops before it gets to the problem point during successful boots. It has happened at least once on each machine. Admittedly it happens very infrequently, but on two of the machines a manual run of e2fsck was necessary, and on one of those, there were numerous errors and broken links. These machines are in an office environment, and I am very uneasy about the whole thing! I am still in the preparation stage with all of them, so they are not yet in daily use. Is this a phenomenon experienced by others running 5.x SuSE? --------------------------------------------------------------------- John Karns jkarns(a)ares.csd.net - 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 archiv 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: Sticky Bit
by CanteraD＠bis.adp.com 15 Dec '98

15 Dec '98

to all, using the sticky bit, as george indicated, is also a very usefull tool. the sticky bit has different meaning on files and executables... one problem you have to watch out for is the /tmp directory as it should NOT have the sticky bit 't' set... in some cases, the 't' sticky bit on a directory does not allow the creation of files, only the appending to an existing file. this is mainly used in NFS mounting (i.e. exporting) the /var/spool/mail directory from your mail server to other hosts used for login, compiling, and other computing needs where you don't want people creating files in the mail directory. some programs in my linux infomagic distribution and in solaris and dec ultrix, I'm assuming the remaining distributions as well, will set the /tmp directory with a 't' sticky bit... it should be removed... the hard way is to delete everything in /tmp, remove the dir, then make it: rm -rf /tmp mkdir /tmp the easy way is to: chmod o-t /tmp thanks to all who post and respond to issues in this list, it is this kind of knowledge transfer that we need! dc ---------- From: George Toft To: suse-linux-e(a)suse.com Subject: Re: [SuSE Linux] Re: Sticky Bit Date: Monday, December 14, 1998 6:43PM Stefan Troeger wrote: > > Hi, > > On Mon, Dec 14, 1998 at 17:00 +0100, James (Jim) Hatridge wrote: > > > In Chmod, what do they mean by "Sticky Bit", ie 1000? > > If you set it on a directory (e. g. /tmp), users can only delete > their own files in it. Have a look at /tmp's permissions: > > drwxrwxrwt 4 root root 1024 Dec 14 20:38 /tmp > > without the sticky bit every user would have permission to > remove someone elses files. > > On files the sticky bit doesn't have an effect (at least in > Linux). > > Ciao, > Stefan My interpretation on the sticky bit was that (on older Unix system) it would keep the file in RAM to prevent continuously reloading it. I read about this, then applied it to a CGI script and noticed about a 30 0ncrease in response from the web server, after all, speed is everything on a 486. George - 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 archiv 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 archiv 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] Re: NFS won't serve / (the root) directory properly
by A.Crowe＠OPENMAIL1.TSEA-E.sukepabe.simis.com 15 Dec '98

15 Dec '98

Chris, I've got a Linux box, and a Linux / Solaris x86 box, and I can export / on the Linux-only box to either Linux or Solaris 7 without problems. I don't remember using the no_root_squash option, though.... Alan. - 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 archiv 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] Applix Upgrades
by andyford＠nothnbut.net 15 Dec '98

15 Dec '98

I downloaded the Applix upgrades and was tring to install them, but a couple gave errors: "Broken pipe, install aborted". I'm using yast for the install. Looking at the modification times of the files to be installed shows that the whole directory path gets modified till the final files, which don't get upgraded. For example, the "myodbc_something.tgz" installs two files in /axpblah/axshlibs/data. The directories axpblah, axshlibs, data have mod dates from today, but the actual files in /axpblah/axshlibs/data don't get updated and YaST gives the "broken pipe" error. I also checked the integrity of the packages by untarring them by hand and got no errors. The packages are definately intact. Any similar experiences? -- yours, Andy - 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 archiv 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] Problem with warm reboot to Win95
by hlarons＠ComCAT.COM 15 Dec '98

15 Dec '98

Once in a while I do a "shutdown -r now" and then start to Win95 from the Win95 bootup menu. When I do that I have a problem whenever I attempt to print from MS Word. I get a BSOD and must cold boot to restore printing. This never happens after a direct boot to Win95 or after a 'shutdown -h now' followed by a reset. Any idea why this should be happening? Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Mutt 0.93.2 - 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 archiv 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 3