February 1998 - openSUSE Users - openSUSE Mailing Lists

Re: [S.u.S.E. Linux] problems with update rpm for ggmp
by bb＠suse.de 02 Feb '98

02 Feb '98

Tom Schaefer wrote: > > I have had major problems trying to upgrade Gimp. > > The gimp.rpm on the 5.1 CD DOES NOT ALLOW FOR FILES TO BE OPENED. > Try to remove your .gimprc and .gimp folder and restart the gimp. The format has changed in the new version and it wouldn't find the plugins with the old rc files... 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: SuSE Linux evaluation (Part 3)
by wtopa＠ix.netcom.com 02 Feb '98

02 Feb '98

Subject: Re: [S.u.S.E. Linux] Re: SuSE Linux evaluation (Part 3) Date: Mon, Feb 02, 1998 at 12:27:54PM -0800 In reply to:Bodo Bauer Quoting Bodo Bauer (bb(a)suse.de): > > Wayne Topa wrote: > > > > Subject: Re: SuSE Linux evaluation (Part 3) > > Date: Sat, Jan 31, 1998 at 07:17:10PM +0100 > > > > > > The problem was that altho I have compiled the 2.0.33 kernel OK, and > > /vmlinuz & /System.map are 2.0.33 (same time/date as zImage), AND > > the cylinder for /dev/hda3 (suse /) is 977 ie < 1024, lilo gives an > error. > > Is 977 the first, or the last cylinder of the partition. Remember that > / has to be completly , 1024. But why don't you put the kernel on your > slackware partition mount this into SuSE and tell lilo that the kernel > is there? > > A known problem with lilo 20 is that the behavior of the 'linear' > flag has changed. So try to remove this flag and see if it boots > now?! Bodo From Page 123 of SuSE 5.1 book, Section 8.3.4 QUOTE "ANY part of LILO has to be on the first 1024 cylinders on the hard disk." From Yast.debug "/dev/hda3 * 977 977 1518 256095 83 Linux native" Yes I could put the kernel on hda1. BUT I have the SuSE kernel where the BOOK says it should work. Lilo 19 DID work with the Debian kernel on hda3 (start cylinder 977), so is the problem with lilo 20? Which statement is true: All of the kerner MUST be on cylinders < 1024, (BB) OR ANY part of the kernel has to be on the FIRST 1024 cylinders??? (Book) Thanks for your help. Chus (Is that spelled right ?) Wayne -- Windows95 (noun): 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition. -- 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] problems with update rpm for ggmp
by deem＠wdm.com 02 Feb '98

02 Feb '98

Tom Schaefer <netd(a)fastrans.net> wrote: > > I have had major problems trying to upgrade Gimp. > > The gimp.rpm on the 5.1 CD DOES NOT ALLOW FOR FILES TO BE OPENED. > > *sigh* > > Is there a fix for this? I installed S.u.S.E. 5.1 and Gimp works just fine. What are you doing or how are you trying to install ? -Dee W.D.McKinney (Dee) -=- deem(a)wdm.com No claim to fame, just saved by Grace. -- 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] Installer Problems
by netd＠fastrans.net 02 Feb '98

02 Feb '98

Some areas for you to fix: 1. When installing from CD 1, packages determined to be on CD 2 and 3 are not allowed to be installed during the first pass install. The friggin' installer just blows past the prompt and the user is not allowed to insert the other CDs. There is some sort of bug that does not prompt for CD 2 or 3. I have found that if I insert the CD I want to install from, then run YAst, Yast seems to determine that there are a bunch of packages that weren't installed. DUH. Then, it seems to install them - but only the packages for the CD that is currently in the drive. This behavior is somewhat inconsistent, but predictable. Then, after installing packages from the second CD, I can exit Yast, remove the CD, then insert CD 3 and run Yast, who happens to "discover" that there are packages that weren't installed. The I can install them. I thought you would have fixed this, as it was a problem in 5.0. 2. After the install "appears" to be done, leaving the user with a login prompt and no clue that you have a bunch of background processes running, and no idea of whether rebooting at this time is wise or not. However, by probing around, I see the Yast installer is unpacking MAN pages and all sorts of other stuff, unbeknownst to the user. You need to alert the installer that something else is happening. I have noticed that if you reboot too soon, Yast appears to be activated at boot up to either finish or do MORE stuff, which is not properly explained. So I never really know if everything has been installed properly. -- 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] problems with update rpm for ggmp
by netd＠fastrans.net 02 Feb '98

02 Feb '98

I have had major problems trying to upgrade Gimp. The gimp.rpm on the 5.1 CD DOES NOT ALLOW FOR FILES TO BE OPENED. *sigh* Is there a fix for this? -- 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] problems with update rpm for ggmp
by bb＠suse.de 02 Feb '98

02 Feb '98

Scott Gray wrote: > > Hi, > > I get the following when I try to install the updated gimp rpm: > > bobcat:/home/sgray1 # rpm -Uvh --force gimp.rpm > failed dependencies: > libxdelta.so.0 is needed by gimp-0.99.17-0 > libgimp.so.1 is needed by photocd-1.12-8 > libgimp.so.1 is needed by sane-0.63-4 > > I did install the gtk.rpm prior to this. Has anyone else had simular probems? Yes, me. Finally I installed it whit rpm -i --nodeps ... And it works fine now... 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: SuSE Linux evaluation (Part 3)
by bb＠suse.de 02 Feb '98

02 Feb '98

Wayne Topa wrote: > > Subject: Re: SuSE Linux evaluation (Part 3) > Date: Sat, Jan 31, 1998 at 07:17:10PM +0100 > > In reply to:Michael Burghart > > Quoting Michael Burghart (smb(a)suse.de): > > > > Hi Wayne.. > > > > On Sat, 31 Jan 1998, Wayne Topa wrote: > > > > > > Thank you for your reply. Your answer to the wavplay question was > > > close but incorrect. The file is play, nor playwav. Thats OK tho as > > > I was too dumb to check the CONTENTS of wavplay, I thought it was the > > > same as I had used in Slackware, Debian and RedHat! I am sorry to > > > have bothered you with That question! > > > > no prob!..;)) > > I just installed it a couple of days ago as I got a TV module for my > > screen..but even I forgot the name...well..at last we found it. > > > > > > Thanks again for your reply. My initial problems with SuSE are > > > slowly going away and I am beginning to really like it. I am still > > > concerned with the lilo-kernel problem. I hope that it turns out to > > > be MY stupid mistake. Until I get that answer, I will continue to > > > boot via the floppy. > > > > sounds great..:-) > > I'm sure we will solve the problem..did you discuss it with Bodo? > > What exactly was the problem...I forgot.. > > > > The problem was that altho I have compiled the 2.0.33 kernel OK, and > /vmlinuz & /System.map are 2.0.33 (same time/date as zImage), AND > the cylinder for /dev/hda3 (suse /) is 977 ie < 1024, lilo gives an Is 977 the first, or the last cylinder of the partition. Remember that / has to be completly , 1024. But why don't you put the kernel on your slackware partition mount this into SuSE and tell lilo that the kernel is there? A known problem with lilo 20 is that the behavior of the 'linear' flag has changed. So try to remove this flag and see if it boots now?! 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] S.u.S.E. pronunciation
by bb＠suse.de 02 Feb '98

02 Feb '98

Mitch Wyle wrote: > > i had heard "sooo-zie" (as in English Susie) > and Soo-zeh (as in German suse) Hi, this is a funny subject to talk about, as we are ourself not sure how to pronounce it in english... :-) But I think we should try to get the german pronounciation established here in the US too. This is the way the most SuSE users pronounce it. If there are more SuSE users in the US than in germany we can change... :)) 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] Metro X server vs SuSE
by bb＠suse.de 02 Feb '98

02 Feb '98

Luis A. Costabile wrote: > > On Sat, 31 Jan 1998, Benjamin van Ruyssevelt wrote: > > > > > I have recently installed RedHat 5.0 on my notebook. everything is working > > fine. I try to use it as my main OS, but I have W95 on the side because I > > regularly use dos-software. I was wondering if anybody had any experience > > or opinions regarding the installation of the X server included in the SuSE > > package. > > > > Does anubody have any experience with this card and the installation of the > > SuSE server(s).. > > Benjamin, I used one of SuSE's X servers with my XFree86 because the > regular X servers didn't support my AGP card. Their server works very > well, no problems that I've found. My understanding is they will give to > the XFree86 group the code they've developed to incorporate into the > regular XFree86. Yes they will. We're very close to the XFree86 team and our servers have the same copyrights etc as the netive XFree86 servers. 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] Pap, PPP,and EZPPP...my luck
by zentara＠mindspring.com 02 Feb '98

02 Feb '98

Eric L. Green wrote: > Please don't! Just use YaST to set up your nameserver! > > Not needed. Just add the user to the "uucp" group and the "dialout" group. > > > 3. chown root.root /usr/sbin/pppd > > PLEASE please don't! It's already chown'ed and chmod'ed! The SuSE people > did this one right (unlike Red Hat, sigh). > > > 8. put the ezppp binary in each dialout users home directory > > and let them own it. > > Err, just stick it into /usr/local/bin. The setup file(s) will still be > stored into each dialout users' home directory. > > Or better yet, just download the "ezppp" rpm from ftp.redhat.com and let > 'rpm' manage where it is installed. > > The chmod's and chown's are NOT needed with SuSE. I dialout just fine > using ezppp with the default permissions. Just add the user to the > "dialout" and "uucp" groups. The chmod's and chown's are only needed with > distributions (such as Red Hat) that don't have pppd already chown'ed, > chgrp'ed, and chmod'ed with the proper permissions. Well Gary, thanks for pointing all this out.!!!!! To be honest, I have been having trouble with security and Suse, the way I had it set up. Yesterday after I posted that message, I was online for about an hour, and after rebooting.........MY ROOT PASSWORD was gone!!!!! The login would accept my users password, but not root. Someone did something while I was online. I only had the yast security set to easy, but it is scary to realize how vulnerable you can be with a faulty setup. What do you think happened, did they knock out my shadowed password? I'm learning the hard way. -- 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