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/

ds wrote:

Bernie Gardner wrote:

...

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!

I installed SuSE 6.2 on my Compaq Armada 7800 Laptop also. I am having BIG problems going from my Ethernet network at work to my Ethernet network here at home. Everytime it starts up, there is no networking and as of this morning, my Eth0 interface is gone. Yast says it is still there, but ifconfig says it doesn't exist.

1. What is CardCtl? Where do you get it? Is it a package that is with the distribution? 2. When I change networks, you can use Yast to make network changes, but it doesn't re-start the network with the new changes. What do I execute to get SuSE to except my changes?

Have you tried switching to single user mode (with 'init 1') and back to your current runlevel (with 'init 2' for command prompt logon, or 'init 3' for xdm/kdm logon)? Good luck, Chris -- Apologies to everyone who has been waiting for replies off me over the past few weeks - I've been away from my computer. I'll try to catch up with my email over the coming days, but don't be surprised if you get a reply in a month's time... __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- 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/

Arjen Runsink wrote:

ds wrote:

...

BI installed SuSE 6.2 on my Compaq Armada 7800 Laptop also. I am having BIG problems going from my Ethernet network at work to my Ethernet network here at home. Everytime it starts up, there is no networking and as of this morning, my Eth0 interface is gone. Yast says it is still there, but ifconfig says it doesn't exist.

1. What is CardCtl? Where do you get it? Is it a package that is with the distribution? 2. When I change networks, you can use Yast to make network changes, but it doesn't re-start the network with the new changes. What do I execute to get SuSE to except my changes?

I too have an ARMADA 7800 and am running SuSE 62 without a problem.

First do not configure the network via Yast and remove all ethernet devices from it. You should in install the PCMCIA package and edit the network config in /etc/pcmcia/network.opts

If you use DHCP make sure you have IPADDR="" or else it interferes. I have DHCP in the office and at home. I can just take out the PCMCIA, hibernate and then put it back in at home and continue. No swea at all.

BTW to have PCMCIA services working better compile APM in the kernel and download and compile latest PCMCIA package. for some reason APM support is not compiled with the SuSE package ??? At least with 6.2 it isn't.

BB, Arjen

Hello Everybody, reading this thread, I started to think how to boot up different Hardware or Network configs, particulary with labtops and wether there is something like that in linux. I am either reinventing the wheel or more likely inventing a way to rape the system IV boot concept and of course SuSE's boot concept ;-). Basicly, there are two runlevels "unused" by SuSE: 4 and 5. These could be used for different HW configs (or Network "work", network "home") 1) booting: on bootup type "linux 4" to boot into your "home" config. I guess, this parameter can be passed on by lilo, so requiring an extra entry in lilo.conf 2) change inittab this requires uncommenting one line for init 4 or init 5. The parameter for the runlevel is given on to /sbin/init.d/rc as $1, it should be saved for further use in the init scripts. 3) prepare your runlevel copy all links from your "normal" runlevel (/sbin/init.d/rcX.d) to your new runlevel. Booting now woldn't do any change. But if you... 4) tailor the "different" scripts OK, lets speak of a different network, OK? You'd need to change the .../rc4.d/S05network that aktually points to /sbin/init.d/network. To be able to master two choices: create a /etc/rc.config.d/my.rc.config and cut and paste the nessesarry vars from rc.config to there and edit them to your needs 4) Modifiing the system IV scripts (/sbin/init.d/*) All scripts start like . /etc/rc.config This means, all vars from rc.config get set. if you place a . /etc/rc.config.d/my.rc.config *afterwards* your vars win. ;-) This points to solution 4a) copy network to mynetwork, add the above line and let the link from your newly created runlevel point there. There is a elite solution 4b ;-)) if it's possible (OK all stuff is called from the rc script and a simple DES_LEVEL=$1;export DES_LEVEL could do it) to access the desired level you could: . /etc/rc.config ... if test "$DES_LEVEL" = "4"; then . /etc/rc.config.d/my.rc.config fi With that, you'd change the original bootscript file according to your needs. Other scripts that might be affected as well could be handled accordingly. Btw. there are runlevels 7,8,9 as well (in theory, but noone bothered yet) Suggestions? (flames to /dev/null please) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- 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/

On 11-Apr-00 ds wrote:

Bernie Gardner wrote:

...

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!

I installed SuSE 6.2 on my Compaq Armada 7800 Laptop also. I am having BIG problems going from my Ethernet network at work to my Ethernet network here at home. Everytime it starts up, there is no networking and as of this morning, my Eth0 interface is gone. Yast says it is still there, but ifconfig says it doesn't exist.

1. What is CardCtl? Where do you get it? Is it a package that is with the distribution? 2. When I change networks, you can use Yast to make network changes, but it doesn't re-start the network with the new changes. What do I execute to get SuSE to except my changes?

Thanks

--

1) Cardctl is a program which allows various operations on pcmcia cards. The only function I've used is 'cardctl scheme ...' which allows you to change network settings (and other settings as well though I've only used the network settings) between different situations quickly. I have it set up so I can just type a single man before leaving home/work and the network is set up correctly for work/home. I have to get to work now, but if you are interested I'll send you the files I use when I get home this evening. 2) To restart the network after changes try 'rcnetwork restart' but as Arjen said, if you want to use the pcmcia scheme method don't configure the network with Yast. I forgot that after I upgraded to 6.4 over the weekend and wasted lots of time until I discovered that SuSE had changed my cardctl file for some reason but had at least saved a copy of my original. If anyone from SuSE reads this ***please*** condider changing this behavior! If there is a configuration file which is changed from SuSE's original it probably means the user has his system working the way he wants it. If you feel obligated to show him a better way, rename your new version instead of the user's old one so the system comes up functioning as it did before the upgrade. 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/