February 2000 - openSUSE Users - openSUSE Mailing Lists

[SLE] Semi-OT: Anybody try Corel's linux download? I did....
by btm77＠home.com 02 Feb '00

02 Feb '00

Hey folks: I know this is little of topic, Has Anybody tried Corel's Linux? I did and I DO NOT recommend it. I figured this is the best place to vent some bitterness about Corel's Linux. 1. The Silly thing gave me a new master boot record and an active corel root partition, without even telling me it was going to do it. 2. It mounted all of my ext2 partitions. Without asking me, good thing it didn't crash. 12 in all. 3. It only comes with their version of KDE only or that is what I can tell so far. no session choices, forget about the 20 something other window managers out there. 4. Their kernel can't load the appropriate modules for my NIC card an ISA one in ISA mode. SCO, windures, BSD, and of coarse SuSE can on the same machine. 5. It automatically configures everything including X. gave me 1024x768 @60 Hz on a g200 and forget about custom modes. 6. It couldn't load the modules for my sound blaster 16 , come on. 7. Their documentation quite frankly "sucks". There was some hypertext documentation that doesn't cover the basics like loading modules etc. It had the kind of information that one would find in that news-print manual that came with your windures upgrade. like how to play a sound file. I have been trying various flavours UNIX/Linux for the past three years. I'm no IT/MIS professional, but I only want to use a computer if it can be personalized. I have to have the control that is what I thought was integral with the any thing that is a UNIX flavour. The Corel distribution is the closest of any distribution to windures that I ever seen. I thought I would share my experience with you and to say that SuSE has come out on top again! Cheers, -Btm77 -- 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/Doku/FAQ/

3 2

[SLE] "mail being received" ???
by Ted.Harding＠nessie.mcc.ac.uk 02 Feb '00

02 Feb '00

Hi Folks, I'm having an intermittent problem (SuSE-6.3 with KDE & all the gizmos) with MUAs hanging while retrieving mail from /var/spool/mail/userid. When this happens, XFMail simply hangs on it, indefinitely. Elm announces that it is "attempting to read mail while mail is being received", retries a number of times, then quits. However, to the best of my awareness mail is NOT being received at these times. Again when it happens, whatever is causing it goes on for a long time, though it eventually clears (especially if I shut down preactically everything else including the user's 'kfm'). What I'm trying to find out, is where is the lock-file or other marker that tells these MUAs that "mail is being received"? Or how otherwise do they tell that "mail is being received"? If I could find where that's lurking, I could suppress it. (Very occasionally, procmail is indeed trying a delivery; mostly, it isn't: 'ps -aux' shows nothing relevant.) Any useful hints will be much appreciated. Best wishes to all, Ted. -------------------------------------------------------------------- E-Mail: (Ted Harding) <Ted.Harding(a)nessie.mcc.ac.uk> Date: 02-Feb-00 Time: 01:01:12 ------------------------------ XFMail ------------------------------ -- 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/Doku/FAQ/

1 0

[SLE] X Server f/S3 Trio?
by jdenning＠pobox.com 02 Feb '00

02 Feb '00

I need an X Server for an S3 Trio3D 4MB onboard video adapter. This is on a new PIII 450 IBM computer. I tried the S3 on the 6.3 DVD and the SVGA Servers. Neither work at all. Anyone know of one? John W Denning -JD- ( ( ( ) ) ) jdenning(a)pobox.com Salt Lake City, UT ) ) )( ( ( (801)322-2056 JD's UnderWater Photo Course - http://www.pobox.com/~jdenning/uwpc.html -- 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/Doku/FAQ/

2 2

[SLE] voice synthesis
by mdb＠ucnsb.net 01 Feb '00

01 Feb '00

is anyone familiar with state of voice synthesis/screen readers in linux today? i have a couple of blind friends who are interested in using learning how to use linux, and i'm researching the feasibility. how good is the software available? is it enough for everyday use of the system? finally, will suse be including emacspeak, rsynth, festival, or the like in any upcoming distrobutions? (i did look on my 6.3 cd's as well as my 5.3 and didn't see any of these programs.) thanks, derek -- 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/Doku/FAQ/

2 1

Re: [SLE] `(null)' in `/var/adm/messages'
by pinard＠iro.umontreal.ca 01 Feb '00

01 Feb '00

"Jack Barnett" <jbarnett(a)axil.netmate.com> écrit: > > Under SuSE 6.2, while revising some older `/var/adm/messages' today, I > > noticed a few strange `(null)' fields, and in one case one empty field. > I am not sure what this is, but could it /possiably/ be someone just > hitting the "enter" key for the login prompt? The string `(null)' is often the result of: printf ("%s", 0) and indicative of a C programming error. It is possible, but rather unlikely, that someone crafter the string "(null)" in the `syslog'. It more looks like a genuine bug. If you find a recipe for reproducing the cases at will, that's good, as it would help finding the bug(s). -- François Pinard http://www.iro.umontreal.ca/~pinard -- 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/Doku/FAQ/

1 0

[SLE] nedit memory leak?
by weberdr＠bellsouth.net 01 Feb '00

01 Feb '00

Just curious if anyone else had this problem? I have nedit version 5.0.2 on my 6.2 install. I use it at work sometimes to write my perl scripts because of the nice context highlighting. I decided to do a little work at home. I hadn't used nedit on this install before. I opened it up it was working fine. I switched the language setting to perl and things went nuts. My system got slow REALLY quickly. I saw the memory meter start creeping up. I tried to catch it but it was too late. My terminal came to a stop, couldn't type, tried everything. . .even tried to kill my X server from the keyboard. . .nothing. The disk was writing constantly by this point and it forced me to do a hard reboot. After restarting I tried to start it again to confirm that it was the problem and as soon as I switched the language setting it started again. This time I was ready so I caught it before it brought me down. First question - Is there anything else I can do the next time this happens other than the hard reboot? Question 2 - Does anyone know if there is a fix for this bug, or should I just forget it and use a different editor for working with perl? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Darren R. Weber drw(a)linuxfan.com ICQ# 2849193 http://drw.penguinpowered.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 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/Doku/FAQ/

1 0

[SLE] Major problems upgrading to 6.3
by adrian＠halodule.tamu.edu 01 Feb '00

01 Feb '00

OK, I've found it impossible to upgrade from 6.2 to 6.3. This is the first time I've ever had problems upgrading a Suse distribution (and I started with Suse at 5.2 and have upgraded at every release since then). System: PII - 300Mhz Asus Motherboard WD 9.2Gb IDE hard drive (for Linux) Seagate 2Gb SCSI (for WinDoze) 128Mb Ram Problem: Well, there I was actually reading the documentation since I'd heard about Yast 2. I decided to forget about it and use Yast 1.03 for upgrade so booted from CD-2 (after which the upgrade says to use CD-1). Everything went fine - nice installation, set up X-windows, everything's fine. THEN, I rebooted. Lilo hung at LI. Well, that the FIRST time I've ever had that happen on me. Had a look at lilo.conf...everything's fine (same lilo.conf as with 6.2 which worked like a dream). Eventually, after a couple of days tinkering around and finding nothing out-of-place I decided to do a fresh install - I make regular back-ups. So I do a fresh install and take the opportunity to repartition the IDE drive. Again, Lilo hangs. Then in desperation I think, let's try Yast2. Ugh! Well, having said that, it did work and I did get to a set up that I can reboot. But, the partitioning is less than ideal for the work I do as well as a host of other minor annoyances. BUT, at least I know there is nothing inherently wrong with the system. So, I go back to the Expert Install. Same problems. I've even tried different kernels - I usually use the EIDE kernel, the standard kernel gives a kernel panic on boot. So, does anyone have any suggestions as to how to get a good Expert Install or suggestions as to what is going wrong and how to fix it? I'm rapidly running out of options (apart from going to back to RedHat (yes, I admit it, I ran RedHat until I switched to Suse))? Adrian -- 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/Doku/FAQ/

2 1

[SLE] YaST 1 - incomplete `Updating' messages
by pinard＠iro.umontreal.ca 01 Feb '00

01 Feb '00

Hello. I'm not sure that using this list is always appropriate for reporting bugs which do not have a critical nature. I used to bother Burchard directly with those, and I'm not sure what is the best channel. And, you will laugh, I do not know yet how to report a Linux bug! Please be kind and educate me :-). This is for YaST 1 with SuSE 6.2. I noticed this for a long while. When YaST is producing its `Updating ...' messages, it does not properly list the last sub-directory for `man' directories. The result is a bit boring, while it could be made more entertaining :-). The following lines are excerpted from `/var/log/Config.bootup'. I merely edited out two `mandb' diagnostics in `/usr/local/man', presuming these are not related to SuSE. Oh, YaST does not seem to identify itself in that `Config.bootup' file. Since there are many YaST versions, this might be a useful thing to do. ----------------------------------------------------------------------> Processing index files of all manpages... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... Updating index cache for path `/usr/man'. Wait... done. Updating index cache for path `/usr/share/man'. Wait... Updating index cache for path `/usr/share/man'. Wait... Updating index cache for path `/usr/share/man'. Wait... done. Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... Updating index cache for path `/usr/local/man'. Wait... done. Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... Updating index cache for path `/usr/X11R6/man'. Wait... done. Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... Updating index cache for path `/usr/openwin/man'. Wait... done. ----------------------------------------------------------------------< -- François Pinard http://www.iro.umontreal.ca/~pinard -- 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/Doku/FAQ/

1 0

[SLE] mp3 to wav
by mircea.andrei＠wanadoo.fr 01 Feb '00

01 Feb '00

I would like to convert mp3 files back to wav in order to save them on to a CD to be played on ordinary CD-players (not on a computer). Does anybody know how to do that ? Thanks. -- # \\\|/// # (-@-@-) # ====oOO==(_)==OOo========================================== # Andrei Mircea <mircea.andrei(a)wanadoo.fr> # .oooO Oooo. Yerres (91) FRANCE # ====( )==( )=========================================== # \ ( ) / # \_) (_/ -- 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/Doku/FAQ/

1 0

Re: [SLE] failed services in runlevel 0= at
by r1r2＠ugrad.cs.ubc.ca 01 Feb '00

01 Feb '00

I had this problem with my SuSE 6.2 system too. For me the problem turned out to be that my root partition was running out of space. I have my /, /root, /var and /tmp directories on the same 180Mb partition, and between all the files that I was collecting in my /root directory and the old files accumulating in /tmp, I ran out of space. This caused all kinds of crazy, hard-to-figure out problems, including this one. It seems that on bootup, when the "at" daemon was started, the system was trying to write the process ID of the daemon into a file called at.pid somewhere in the /var directory. This was not succeeding. As a result, when the system shutdown scripts were running, they were unable to kill the at daemon because they had no record of it's PID. The solution was to free up some space. I cleared out all the .tar and .gz files and other large files I'd stored in my /root directory, which freed up about 45Mb. I also cleared out my /tmp directory, which had files that dated back to the day I installed Linux. I don't understand why these weren't cleared out automatically by the cron daemon at night, and I haven't had time to figure it out since. The command df is useful for diagnosing this particular problem. It shows you a list of your filesystems, and tells you how full they are. Good luck --Fraser -- 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/Doku/FAQ/

1 0