alin 05/07/16 11:45:41 Modified: xml/htdocs/doc/en alsa-guide.xml Log: - killing a program with KILL (-9) signal is recommended only when it's really necesarry. Instead, using the default signal (TERM) should kill [in this case] udevd without any problems. Also, -9 may cause an unclean exit for the program (if it does not handle the signal properly). - surrounded /dev with <path>
Revision Changes Path 1.58 +6 -6 xml/htdocs/doc/en/alsa-guide.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.58&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml?rev=1.58&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/alsa-guide.xml.diff?r1=1.57&r2=1.58&cvsroot=gentoo Index: alsa-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v retrieving revision 1.57 retrieving revision 1.58 diff -u -r1.57 -r1.58 --- alsa-guide.xml 14 Jul 2005 19:22:54 -0000 1.57 +++ alsa-guide.xml 16 Jul 2005 11:45:41 -0000 1.58 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.57 2005/07/14 19:22:54 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.58 2005/07/16 11:45:41 alin Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -18,8 +18,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>2.6</version> -<date>2005-07-14</date> +<version>2.7</version> +<date>2005-07-16</date> <chapter> <title>Introduction</title> @@ -543,9 +543,9 @@ <impo> If you have issues starting up <c>alsamixer</c> and get errors such as alsamixer: function snd_ctl_open failed for default: No such file or directory, -this is usually an issue with udev setting up the devices. Run <c>killall -9 -udevd; udevstart</c> to reload /dev entries and fire up <c>alsamixer</c>. It -should solve the issue. +this is usually an issue with udev setting up the devices. Run <c>killall +udevd; udevstart</c> to reload <path>/dev</path> entries and fire up +<c>alsamixer</c>. It should solve the issue. </impo> <p> -- [email protected] mailing list
