Hi there, I have some problem with alsa after returning from Suspend to disk. In suse there was a solution based on editing "/etc/sysconfig/powersave/sleep" and adding "alsasound" parameter to SUSPEND2DISK_RESTART_SERVICES. array. In 10.0 it's not working anymore. Manual restart of alsasound is required. Any idea where's the problem? I'm running 10.0 OSS i386, default kernel and Audigy2 soundcard Thank's Michal

Danny Kukawka wrote:

On Wednesday 19 October 2005 18:35, Michal Libra wrote:

...

Hi there,

I have some problem with alsa after returning from Suspend to disk. In suse there was a solution based on editing "/etc/sysconfig/powersave/sleep" and adding "alsasound" parameter to SUSPEND2DISK_RESTART_SERVICES. array. In 10.0 it's not working anymore. Manual restart of alsasound is required. Any idea where's the problem?

Looks as /etc/init.d/ is not in PATH of root. Did you tried to use full path (/etc/init.d/alsasound) or rcalsasound instead of alsasound?

Danny

Yes, I tried this, but with the same result.

Danny Kukawka wrote:

On Wednesday 19 October 2005 19:00, Michal Libra wrote:

...

Yes, I tried this, but with the same result.

Please file a bug, select 'Mobile Devices' as Component.

Danny

Danny, please send me a link to the right one bug-reporting system. Since the SuSE is a part of Novell the orientation on the pages is getting little bit complex... Thanks, Michal

On Wed 19. Oct 19:00:51, Michal Libra wrote:

Danny Kukawka wrote:

...

On Wednesday 19 October 2005 18:35, Michal Libra wrote:

...

Hi there,

I have some problem with alsa after returning from Suspend to disk. In suse there was a solution based on editing "/etc/sysconfig/powersave/sleep" and adding "alsasound" parameter to SUSPEND2DISK_RESTART_SERVICES. array. In 10.0 it's not working anymore. Manual restart of alsasound is required. Any idea where's the problem?

Looks as /etc/init.d/ is not in PATH of root. Did you tried to use full path (/etc/init.d/alsasound) or rcalsasound instead of alsasound?

Danny

Yes, I tried this, but with the same result.

Did you try to restart the alsa service manually after a suspend to dist? If this does not work either, it would be great if you could open a bugreport at http://bugzilla.novell.com for this, taking me into CC. Thanks, Holger

Am Mittwoch 19 Oktober 2005 18:41 schrieb Jean-François Simon :

...

...

I want to upgrade my pc running suse 9.1 while keeping the user accounts. By upgrading I mean a fresh install on the / partition and keeping the user partition. just keep /etc/passwd. /etc/shadow and homes ;-)

Hi, STOP! What about /etc/group? And if you just copy the old passwd file, you will loose all changed system users!

...

But if you have some more space do a backup of whole /etc/.

Do a full backup.

Great ! It is simpler than what I guessed.

According to your system it can be simple... -- mdc

Am Donnerstag 20 Oktober 2005 09:49 schrieb Jean-François Simon :

...

...

...

...

I want to upgrade my pc running suse 9.1 while keeping the user accounts. By upgrading I mean a fresh install on the / partition and keeping the user partition. just keep /etc/passwd. /etc/shadow and homes ;-) STOP! What about /etc/group? And if you just copy the old passwd file, you will loose all changed system users! Can I just copy and paste the regular users in the old /etc/passwd, /etc/shadow and /etc/group to the new one ?

Hi Jean-François, only if you use the same method to crypt the passwords. Look in your old /etc/shadow and compare the password field to the one in the new /etc/shadow. If your old passwords use another encryption, you must change the method on 10.0 via YaST. This only works if you use "local(/etc/passwd)" for authentification. -- mdc

On Thursday 20 October 2005 21:31, meister@netz00.com wrote:

Am Donnerstag 20 Oktober 2005 09:49 schrieb Jean-François Simon

:

...

...

...

...

...

I want to upgrade my pc running suse 9.1 while keeping the user accounts. By upgrading I mean a fresh install on the / partition and keeping the user partition.

just keep /etc/passwd. /etc/shadow and homes ;-)

STOP! What about /etc/group? And if you just copy the old passwd file, you will loose all changed system users!

Can I just copy and paste the regular users in the old /etc/passwd, /etc/shadow and /etc/group to the new one ?

Hi Jean-François,

only if you use the same method to crypt the passwords. Look in your old /etc/shadow and compare the password field to the one in the new /etc/shadow. If your old passwords use another encryption, you must change the method on 10.0 via YaST. This only works if you use "local(/etc/passwd)" for authentification.

JFYI -- passwords encrypted with different algorithms are different enough to figure out the algorithm used, and to process it correctly. Right now I have blowfish selected as a default, but still have a few users with md5-encrypted passwords. -- Best regards, Alexander.

On Friday 21 October 2005 11:43, meister@netz00.com wrote:

Am Freitag 21 Oktober 2005 02:30 schrieb "Alexander S. Usov"

:

...

...

... If your old passwords use another encryption, you must change the method on 10.0 via YaST. This only works if you use "local(/etc/passwd)" for authentification.

JFYI -- passwords encrypted with different algorithms are different enough to figure out the algorithm used, and to process it correctly. Right now I have blowfish selected as a default, but still have a few users with md5-encrypted passwords.

Hi Alexander,

thanks for that information. Is this a new feature? As far as I remember, in older SuSE versions all passwords must have the same encryption. Or am I wrong?

No idea. I am a new suse user, however I am very surprized if it didn't really worked before. In the case of FreeBSD it worked this way for ages. -- Best regards, Alexander.