Andy,
Please try to keep everything on the list so that it is documented for
others.
[EMAIL PROTECTED] wrote:
>William M. Quarles wrote:
Andy,
First of all, are you keeping up with Red Hat's regular package updates
properly? Please make sure that you do that before anything else.
No I haven't yet.
Sign up for the Red Hat Network Demo service using rhn_register, if you
haven't done so already from the machine that you are working on. It's
free, and all that you have to do is put up with filling out a survey
about the service once per quarter.
Also, be sure that you install the glibc-kernheaders, ncursees-devel,
and kernel-source packages first, if you haven't done that.
If you already have an RHN account:
1. certain accounts (including the Demo service) only have one computer
allowed. If an outdated installation or a computer that you are not
going to run RHN on (anymore) is still on your account, then sign on to
the RHN website and delete it, and transfer the service rights to the
new installation/machine. If this is an upgrade from an old
installation, RHN should have figured that out for you already, however.
2. A way to get around signing up only one computer is to use multiple
e-mail addresses, if you need to do this. Check out
http://www.endjunk.com for that. Also, after signing up with one e-mail
address, you can move it to any other e-mail address, even if that
e-mail address is already in use on another account. You just can't
start a new account on an e-mail that is already in use.
If you have signed up yourself and your machine already, run up2date
--config to configure your up2date program. Also right-click on your
RHN network monitor (a little docklet on your GUI panel that is probably
flashing bright red with a white exclamation point), and select
"Configuration..." to set that up. Once this is done, you can left
click on the RHN monitor to bring up a list of available updates, and
then pick the "Launch up2date" button, or right click on the monitor and
select "Launch up2date..."
It will ask you whether or not you want to update stuff on your
blocklist. Be sure to update the kernel stuff.
Also, are you using the kernel provided by Red Hat, or have you compiled
your own?
It's the out-of-the-box kernel from RH itself.
It's a good idea to compile your own kernel from the Red Hat
kernel-source package. Check out
<http://www.tldp.org/HOWTO/Kernel-HOWTO/index.html>
Configuration files are in /boot/ for any kernels that you installed in
RPM format. You can use one of those and modify it to meet your own
system and desires a lot better. Change your processor to what you
actually use (especially if you own a Coppermine Celeron, Pentium-III,
Petium-IV, or an AMD chip), and take out a lot of stuff that you don't
need (like bugfixes for chipsets that hardly any one uses). I reccomend
'make menuconfig' over 'make xconfig' personally.
I've never compiled ALSA for an RPM-installed kernel, but if you would
like to try, I can also try and follow along with you. It is likely
that you will need the kernel-source package installed even if you are
compiling for an RPM-installed kernel.
By the way, if you don't care to install ALSA by compiling it, and you
would prefer an RPM-based installation, check out these sites:
http://freshrpms.net/
http://www-ccrma.stanford.edu/software/
--
William M. Quarles
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
