On 08-Apr-00 juergen.braukmann@ruhr-west.de wrote:
TRBishop wrote:
Well, I put my money on the counter and got 6.4. Beautiful! Yast2 worked perfectly. Wish I hadn't gone for the install -almost -everything this time 'cause this is HUGE! Won't be long and I suppose distros will be including hard drives with their software. Feeling a little claustrophobic in my 10Gig's. Which brings me to my little problems: Is Kpackage broken in 6.4? Wanted to weed out some of the extras, but it will not load packages. Did rebuilddb, -U kpackage, etc. but no go in either root or user. Also, that damn upsd is back and I have tried everything to drive a stake through its heart, but it IS persistent. Wouldn't care except it keeps kppp from closing the connection. Help? With as good as 6.4 looks, I can hardly wait for 7.0 (?) and KDE2...that will be an awesome change. Thanks again SuSE for a great product and a great value for my money. Tom
Yes. It took me some time to (start to) install it too. Again, Yast2 looks beautiful, never the less it was a bit confusing to me, since I am sooo used to yast1. I missed the chance to load a selection from floppy. I did a complete new install, since I wanted Reiser FS. I saved my old selection to disk and hadn't a chance to load it. So I did a minimal install from yast2 and used my floppy with yast1 afterwards. Never the less, yast2 looks so good! I had *particular* fun reading the extra manual that came with it: At some point in the X-install you're offered the chance to insert your *windows* driver disk for your monitor. I laughed for minutes. ;-) (I know that this works and how; just the idea made me laugh) On bootup, my SCSI card is detected and the module loaded. If my scanner is on, boot hangs after loading the module. ;-( Still need to configure my TrueTypes, logging of ISDN and a problem with syslog. I used some of my old config files, since some stuff has changed the problem might be there. The install went fine and quick, that's the best.
Juergen
I too just upgraded to SuSE 6.4. My experience was not quite as positive as the above comments, though most things are working ok now. More as a passing on of problems for future fixes than as complaints I list the following observations. 1) I first tried to use yast1. At one point it requested that I insert the 'modules disk' (after I said I wanted to install modules; not sure I needed to but thought I would look at what the options were.) I have a ls120 superdisk as the floppy drive, and it was not recognized. I've had no trouble using it previously, though it is necessary to compile in the appropriate option. They are sufficiently common now that it seems SuSE should incorporate support in the installation kernel that boots with yast. Anyway, I used yast2 and it seemed to work ok (though I agree a few more choices of what to install would be nice) 2) As usual oss sound doesn't work without reinstallation. Seems like it should be possible for the reinstallation to be done by yast. 3) This is on a laptop which I use at home and work with different network settings. I had worked out a simple way to make the change using cardctl scheme. After updating, networking did not work at all. It took considerable effort to find all the settings yast had changed during the upgrade. I finally have it working at home, but I'm not sure the cardctl will work at work without more tweaking. I see no reason at all for any network settings to be changed during an update. Surely it is reasonable to assume that if the user is interested in networking he has worked it out before the update, and the update procedure shouldn't change anything related to it! 4) This is minor in terms of impact, but annoying and very strange. I normally run setiathome in the background and use tkseti to start and monitor it. This had worked fine before. Now when tkseti starts, it says it can't execute "/home/bernie/setiathome, no such file or directory". This is true because I have a seti subdirectory, which is properly pointed to in the tkseti setup, and that had worked fine in the past. Something is changed in the way the wish file executes tkseti. Again, it doesn't seem there is any good reason for such a change. 5) Some of the kde settings were changed. Nothing major, but again annoying that yast thinks it knows better than me how to set things on an upgrade. It's reasonable to have defaults for a new install, but wherever possible the upgrade should default to the previous settings. 6) Some kde programs don't work at all. In particular, kpackage fails with the message "kpackage: error in loading shared libraries: libpopt.so.0: cannot open shared object file: No such file or directory" I haven't had a chance to track that down much yet but it's dissapointing that working programs are broken by an upgrade. 7) Finally, I have also been trying to get wpo200 to work. It was basically working before the upgrade, but not at all now. I think this is more of a problem with wpo2000 than with SuSE, and will pursue it in the corel newsgroups, but if anybody has any suggestions they would be most appreciated. I have tried all the fixes mentioned here and on the corel newsgroups, including the 'exportC_ALL=en' fix for glibc2.1.3, and I've reinstalled wpo200 two more times (i've just about got the order of rpm's memorized!) Trying to run any of the applications results in a page fault error from wine. As I said at the beginning this post is meant as a suggesitions of future improvements in an already great product, not a rant about SuSE's shortcomings. They sell an amazing amount of well packaged software for a surprisingly low price. I bought 6.4 at Compusa for about $30. That's less than most books of comparable length to the SuSE manual, which provides a lot of useful information. (Of course its possible that answers to some of the above comments are in the manual and I haven't seen them yet...;-) Bernie Gardner bernieg1@mediaone.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/