February 1998 - openSUSE Users - openSUSE Mailing Lists

[S.u.S.E. Linux] EArlier problems - some solutions; still questions abound
by mperry＠basin.com 04 Feb '98

04 Feb '98

I posted recently about problems I had with upgrading from SuSE 6.0 to 5.1 and got a few responses primarily regarding issues with KDE. I would like to thank th email followups for setting me straight. I would like to address the inability of YAST to correctly identify key components or applications previously installed in my system and then allow a package to update itself over the existing version. I also am somewhat concerned with the upgrade process wiping out files like /etc/profile and not making copies of them whatsoever. I have found that generating a new .fvwm2rc file has become downright dangerous lately; any changes I make at even a minor level are not kept. As an example, I change knews to slrn and pine to mutt and these changes are not kept. I found that with netscape-communicator 4.04 rpm, that starting it with the -install switch gets rid of module errors I get when starting it by typing netscape alone. Each new .fvwm2rc rewrites this change back to the original. The continuing problems with mislinked libraries are rather perplexing since these were libs I compiled on my own. With programs, I do not understand why SuSE 5.1 upgrade would wipe out my compiled slrn 0943 with its own slrn 0943. I also am a bit puzzled about WABI and the file called /dev/zero (whatever in heck that is). Any enlightenment would be quite appreciated. And Bodo and SuSE list serving administrators... - email problems should be over now. I apologize. We had some dns routing errors here that are now resolved. -- --Michael Perry-- mperry(a)basin.com -- 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] S.u.S.E. pronunciation
by jmarkevich＠mindless.com 03 Feb '98

03 Feb '98

> > I like your approach, Gordy :) We like to leave lots of latitude, too. > Before we opened up the US office I did a poll with friends to ask them > how they would say the name so as to give me some guidance. Well, it was > no help at all b/c I got 4-5 different pronunciations with almost no > regularity to it. I personally say "SUE-zeh" but I encourage everyone to > say just what rolls off of their tongues! > > At least YaST is a little easier... ;) Does anyone else here pronounce YaST like "mangrove throat-warbler"? --- Jonathan Markevich <jmarkevich(a)mindless.com> "Today, of course, it is considered very poor taste to use the F-word except in major motion pictures." -- Dave Barry, "$#$%#^%!^%&@%@!" -- 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] Re: Package install requires re-boot
by netd＠fastrans.net 03 Feb '98

03 Feb '98

> Wayne Topa wrote: > > WHY does loading of packages or files with or without YaST, REQUIRE > that the system be RE-BOOTED??? Not a SuSE expert here, or even a LInux expert, but I have noticed that a few packages require a lib file update of some kind, using ldconfig - is that true? ldconfig is run automatically on boot up, and I noticed Slack and some of the others do this also. Perhaps all he needs to do is ldconfig to update the libs?Please educate/correct me if I'm wrong. :) -- 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] Re: Package install requires re-boot
by bb＠suse.de 03 Feb '98

03 Feb '98

Bodo Bauer wrote: Hi, just an idea - is your system time correct? If your system runs in the past, that means your time is much before the time we packed the CD, strange things may happen... Ciao, BB > Wayne Topa wrote: > > > > Bodo > > > > I just loaded up the "easy" package as I required ginstall for a > > tar.gz package compile. After yast finished loading the package I > > used your hint go check what files contained ginstall (F2 Search). > > It found easy and also another package ( forgot the name ) BUT > > the file in THAT package was genstall NOT ginstall. Somehow the > > search found a mis-spelled word. Thought you might want to check > > that. > > Thanks for the Hint, I think we get this fixed on the next release... > > > > > When I exited YaST, it ran SuSEconfig ( as usual) and then finished. > > I then tried to get on the net to get my email. I couldn't. ppp-up > > did not run pppd. Thought I would check everything and all looked OK > > so I rebooted the system. ppp-up works fine now. > > > > Bodo, this HAS to be fixed. WHY does loading of packages or files > > with or without YaST, REQUIRE that the system be RE-BOOTED??? As > > I have said this on the list before I don't think that it would good for > > SuSE for me to keep repeating it. But I have NEVER received an answer > > from you guys as to what or why this is happening. > > > > I have received other mail from people on the list who are wanting > > to know the answer as well. Please, for SuSE's sake, post an answer > > to this problem on the list! This is not a very good thing to just > > forget about. > > I asked our german office if they know about the problem. Nobody > had heard something about this. But let's try to get closer to > the problem. Is realy a reboot needed? Can you try to switch to > runlevel 1 and back to 2 (init 1 ; init 2 ) and see if this helps? > > With which packets do you get this problem? I can't reproduce > the error here... :-(( > > -- > Bodo Bauer S.u.S.E., LLC fon +1-510-835 > 7873 > bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 > 7875 > http//www.suse.com Oakland CA, 94610 USA > -- > To get out of this list, please send email to majordomo(a)suse.com with > this text in its body: unsubscribe suse-linux-e -- Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- 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] Re: Package install requires re-boot
by bb＠suse.de 03 Feb '98

03 Feb '98

Wayne Topa wrote: > > Bodo > > I just loaded up the "easy" package as I required ginstall for a > tar.gz package compile. After yast finished loading the package I > used your hint go check what files contained ginstall (F2 Search). > It found easy and also another package ( forgot the name ) BUT > the file in THAT package was genstall NOT ginstall. Somehow the > search found a mis-spelled word. Thought you might want to check > that. Thanks for the Hint, I think we get this fixed on the next release... > > When I exited YaST, it ran SuSEconfig ( as usual) and then finished. > I then tried to get on the net to get my email. I couldn't. ppp-up > did not run pppd. Thought I would check everything and all looked OK > so I rebooted the system. ppp-up works fine now. > > Bodo, this HAS to be fixed. WHY does loading of packages or files > with or without YaST, REQUIRE that the system be RE-BOOTED??? As > I have said this on the list before I don't think that it would good for > SuSE for me to keep repeating it. But I have NEVER received an answer > from you guys as to what or why this is happening. > > I have received other mail from people on the list who are wanting > to know the answer as well. Please, for SuSE's sake, post an answer > to this problem on the list! This is not a very good thing to just > forget about. I asked our german office if they know about the problem. Nobody had heard something about this. But let's try to get closer to the problem. Is realy a reboot needed? Can you try to switch to runlevel 1 and back to 2 (init 1 ; init 2 ) and see if this helps? With which packets do you get this problem? I can't reproduce the error here... :-(( -- Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- 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] Problem; Mach64 server
by bb＠suse.de 03 Feb '98

03 Feb '98

> > Is this a bug in the Mach64 server? Should I be using the Mach64 server? Is > > there some other kind of setting I should use? Is it a configuration > problem? > > It sounds like you maybe overdriving your monitor. Check the spec for it and > make sure that XFree is set up properly. Yes it seems to be a monitor problem. Start X and use xvidtune to play around with different syncrates. Ciao, BB -- Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb(a)suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- 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] Re: Bubba Gump Gimp 99.17
by netd＠fastrans.net 03 Feb '98

03 Feb '98

Thomas Fehr wrote: > I have been urged to provide a version 0.99.17 of gimp because of > instabilities and bugs in 0.99.15 ;-). Gimp is a too big package to perform > a complete test for every release. Usually I install the new version, > try to load, change and save some files in different file formats. > If this things seem to be ok, I make a new version available. > I understand completely > If I refuse to make the newest version available everyone will ask > me for the new version, because he thinks a new version will save > all his problems. ;) > Gimp is really a large powerful piece of software. > Such packages will always have some new bugs in a new release. > Of course ... such is the nature of things ... > If you do not have access to a S.u.S.E. CD you can get xdelta > from: > > <A HREF="ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm"><A HREF="ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm</A">ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm</A</A>> > Fixed - that did the trick ... thanks -tks- -- 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] Re: Bubba Gump Gimp 99.17
by fehr＠suse.de 03 Feb '98

03 Feb '98

Hi, On Tue, 3 Feb 1998, Tom Schaefer wrote: > > I downloaded the gimp.rpm & gtk.rpm from ftp.suse.com last nite and I > have it installed, however, I have a few problems. > > Check these error messages: > > # gimp & > [1] 540 > parsing "/root/.gimp/gtkrc" > parsing "/usr/share/gimp/gimprc" > parsing "/root/.gimp/gimprc" > # parsing "/root/.gimp/pluginrc" > query plug-in: "/usr/lib/gimp/0.99.17/plug-ins/xd" It seems you did not install the shared library libxdelta. It is contained in the package xdelta.rpm ("Binary delta generator and RCS replacement"). It is in the Series ap on the first CD. > /usr/lib/gimp/0.99.17/plug-ins/xd: can't load library 'libxdelta.so.0' > wire_read: unexpected EOF > writing "/root/.gimp/pluginrc" > Starting extensions: extension_script_fu > > Now, at this point, gimp loads and appears to run fine, however, file > operations are a bit tricky. I have seen it crash and appears much more > unstable than .15. > I have been urged to provide a version 0.99.17 of gimp because of instabilities and bugs in 0.99.15 ;-). Gimp is a too big package to perform a complete test for every release. Usually I install the new version, try to load, change and save some files in different file formats. If this things seem to be ok, I make a new version available. If I refuse to make the newest version available everyone will ask me for the new version, because he thinks a new version will save all his problems. Gimp is really a large powerful piece of software. Such packages will always have some new bugs in a new release. > I re-installed the gtk.rpm (-i --force --hash) and it appears to install > ok, and forcing gimp.rpm - (-i --force --hash) to install as well. > > I ran ldconfig also after the install.. (?) > > Just so you know, I have already previously attempted to install the > latest release of gimp from gimp.org. .18 is miserable to work with. > Could not get all of it to compile - something about the plugins not > having all the necessary files etc. I have done my best to cleanse my I compiled gimp 0.99.18 just today and did not have any problems. > system of all of it, but again, things are not installed in a simple > manner, shit is scattered all over the file system. (Is it so difficult > to keep things in a simple directory tree? ). So I believe I installed > the rpm into a "clean" environment but am not certain. Yes I deleted > the ~/.gimp and .gimprc files before installing and running gimp. > > Where do I get that libxdelta.so.0? Perhaps it's not the real problem? It should no have any thing to do with the instabilities of the new version. If you do not have access to a S.u.S.E. CD you can get xdelta from: <A HREF="ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm"><A HREF="ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm</A">ftp://ftp.suse.com/pub/SuSE-Linux/5.1/suse/ap1/xdelta.rpm</A</A>> bye, Thomas Fehr --- Thomas Fehr, S.u.S.E. GmbH, Gebhardtstr. 2, 90762 Fuerth, Germany Tel: +49-911-74053-0, Fax: +49-911-3206727, Email: fehr(a)suse.de PGP public Key available. -- 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] iomaga internal zip drive
by exec＠prysm.net 03 Feb '98

03 Feb '98

On Mon, 2 Feb 1998, gman wrote: > Thanks for the advice. I believe that the SyQuest SparQ is the better deal. > Are you currently using a SparQ? If so, is there anything special other that > the "compile in the IDE Floppy support" recommendation below. Nope, nothing special. Just stick a cart in the drive, boot up into your BIOS setup screen, and tell it about your new hard drive. Then Linux will discover it quite okay. Do note that Linux won't let you eject a mounted disk! (Just like it won't let you eject a mounted CD-ROM). SparQ carts come pre-formatted for Windows 95. To use them under Linux, either mount them as 'vfat' or go into fdisk and change the partition type to 83. Then do an mkfs -text2 /dev/hdx on it (where 'x' is whatever drive it was assigned to). Eric Lee Green exec(a)softdisk.com Executive Consultants Systems Specialist Educational Administration Solutions You might be a redneck if you put on insect repellant prior to a date. -- 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] Bubba Gump Gimp 99.17
by netd＠fastrans.net 03 Feb '98

03 Feb '98

I downloaded the gimp.rpm & gtk.rpm from ftp.suse.com last nite and I have it installed, however, I have a few problems. Check these error messages: # gimp & [1] 540 parsing "/root/.gimp/gtkrc" parsing "/usr/share/gimp/gimprc" parsing "/root/.gimp/gimprc" # parsing "/root/.gimp/pluginrc" query plug-in: "/usr/lib/gimp/0.99.17/plug-ins/xd" /usr/lib/gimp/0.99.17/plug-ins/xd: can't load library 'libxdelta.so.0' wire_read: unexpected EOF writing "/root/.gimp/pluginrc" Starting extensions: extension_script_fu Now, at this point, gimp loads and appears to run fine, however, file operations are a bit tricky. I have seen it crash and appears much more unstable than .15. I re-installed the gtk.rpm (-i --force --hash) and it appears to install ok, and forcing gimp.rpm - (-i --force --hash) to install as well. I ran ldconfig also after the install.. (?) Just so you know, I have already previously attempted to install the latest release of gimp from gimp.org. .18 is miserable to work with. Could not get all of it to compile - something about the plugins not having all the necessary files etc. I have done my best to cleanse my system of all of it, but again, things are not installed in a simple manner, shit is scattered all over the file system. (Is it so difficult to keep things in a simple directory tree? ). So I believe I installed the rpm into a "clean" environment but am not certain. Yes I deleted the ~/.gimp and .gimprc files before installing and running gimp. Where do I get that libxdelta.so.0? Perhaps it's not the real problem? Thanks -tks- -- 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