You know how once you solve a computer (or any other type of) problem, you tell yourself that you’ll never forget how to solve it if it happens again, since you just wasted 27 hours of your life figuring out the solution?
And what happend next month after you’ve had to deal with a dozen other issues, and same problem comes up again? Yes, you end up spending 22 hours (because you remembered 5% of the original solution)…
Anyhoo, I’m vowing not to make that mistake again. And since I’ve had to re-install SuSE several times since I started donw this linux road, I’m going to try to make this blog a record of the issues I’ve come across, and how I resolved them. Because _I’m 100% SURE_ it will come in handy again.

So in that light;
– Getting Alsa to output to all channels on a soundcard: (contents of /etc/asound.conf)
pcm.!default {
type plug
slave.pcm "dmixer"
}

pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm “hw:0,0”
channels 6
period_time 0
period_size 1024
buffer_time 0
buffer_size 4096
rate 44100
}
}

pcm.duplicate {
type plug
slave.pcm “dmixer”
slave.channels 6
route_policy duplicate
}

– What to do if the Windows is re-installed, and the boot loader is gone
Put the SuSE installation disk back in the drive (it’s SLICK SuSE 10.0 at time of writing) and boot off it, as if you want to install the OS. Accept the license agreement, and then select other (instead of upgrade ot new install).
A list will show up, and choose the bottom option (expert).
Choose the ‘Install boot loader’ and it will do the rest.

– Starting KDE at vncserver boot time

– Getting Samba shares to work: Did it once, but forgot how to. This link should help for next time.

http://www.linuxforums.org/forum/linux-tutorials-howtos-reference-material/54415-fileserver-samba-printserver-cups-howto.html

I think what I forgot this time is the ‘smbpasswd -a username‘ command.

– Back up the /etc (and other setting) folders regularly in case things go horribly wrong, I won’t have to re-research everything and figure things out.