In the RHN Classic model, to register a freshly installed RHEL 6.4 system to EUS content, I run:

rhnreg_ks --use-eus-channel --username <some_user> --password <some_pass>

Afterwards, I am registered to the 'rhel-x86_64-server-6.4.z' channel. The above command provides the following:

"Register the system to the EUS content stream that matches my minor release" RHEL 6.4 in this case. 


In the RHSM model, I have to do :

* subscription-manager register --username=<some_user> --password=<some_password> --auto-attach

[For the purposes of this BZ, I'll assume that the subscription that gets auto-attached contains EUS)

* subscription-manager release --set 6.4
	to properly set the $releasever variable so that I get the correct repo from the CDN
* yum-config-manager --disable
	to disable all the repos that I don't need
* yum-config-manager --enable rhel-6-server-eus-rpms
	to enable the repo that I want


If I neglect to run the above 'subscription-manager release' command, the system will pull EUS content from the 6Server repos, which points to the latest minor release. That is:

	* Usually not wanted. (If I built a 6.4 system, I usually want 6.4.z content)
	* A change in behavior from the RHN Classic methodology


What would be beneficial is a similar switch to the '--use-eus-channel' switch, which allows the end user to register a system and configure it with the proper repos for EUS.