From inode0 at gmail.com Wed Apr 2 15:29:48 2008 From: inode0 at gmail.com (inode0) Date: Wed, 2 Apr 2008 10:29:48 -0500 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages Message-ID: I've run across this situation a few times in the past and again this morning. https://rhn.redhat.com/errata/RHSA-2008-0197.html was released this morning and fixes a security issue in the version of the package in the base channel (gnome-screensaver-2.16.1-5.el5_1.1 is the new fixed version) but in the fastrack channel there exists version 2.16.1-6 which does not have an errata at this time. The changelog for the fastrack package suggests nothing about this errata so I'm again asking for some mechanism to be found whereby users who are concerned about security can determine whether a package such as this is vulnerable or not. If it is known to be not vulnerable please include this information in the released errata. And if someone could tell me whether or not it is vulnerable that would be swell too for this case. Thanks, John From inode0 at gmail.com Wed Apr 2 16:02:12 2008 From: inode0 at gmail.com (inode0) Date: Wed, 2 Apr 2008 11:02:12 -0500 Subject: [rhn-users] rpm versioning Message-ID: Recent (at least recently noticed by me) changes in the way Red Hat is versioning rpms had an unexpected negative impact on some of our custom packages that replace RHEL base channel packages. What we do is a rather long story and not very relevant to my question which is more about consistency and understanding what Red Hat is doing when they version and re-version rpms they provide. $ rpm -q --qf "%{RELEASE}\n" gnome-screensaver 6.el5 That is typical of how things have been and minor updates bumped something before the .el5 bit. $ rpm -q --qf "%{RELEASE}\n" cups 11.14.el5_1.6 This is showing up more and more and minor bumps are occurring after the .el5 bit. Rather than explaining how this affects the way I version packages locally could someone just explain the actual way Red Hat is now doing package versioning so I can adjust? Thanks, John From mh1272 at gmail.com Wed Apr 2 16:04:04 2008 From: mh1272 at gmail.com (hike) Date: Wed, 2 Apr 2008 12:04:04 -0400 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: References: Message-ID: On Wed, Apr 2, 2008 at 11:29 AM, inode0 wrote: > I've run across this situation a few times in the past and again this > morning. > > https://rhn.redhat.com/errata/RHSA-2008-0197.html was released this > morning and fixes a security issue in the version of the package in > the base channel (gnome-screensaver-2.16.1-5.el5_1.1 is the new fixed > version) but in the fastrack channel there exists version 2.16.1-6 > which does not have an errata at this time. > > The changelog for the fastrack package suggests nothing about this > errata so I'm again asking for some mechanism to be found whereby > users who are concerned about security can determine whether a package > such as this is vulnerable or not. If it is known to be not vulnerable > please include this information in the released errata. > > And if someone could tell me whether or not it is vulnerable that > would be swell too for this case. > > Thanks, > John > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users > you might consider opening a ticket and asking Red Hat. if you have a current subscription, this support is included. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bressers at redhat.com Wed Apr 2 16:41:59 2008 From: bressers at redhat.com (Josh Bressers) Date: Wed, 02 Apr 2008 12:41:59 -0400 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: References: Message-ID: <28409.1207154519@devserv.devel.redhat.com> > I've run across this situation a few times in the past and again this morning. > > https://rhn.redhat.com/errata/RHSA-2008-0197.html was released this > morning and fixes a security issue in the version of the package in > the base channel (gnome-screensaver-2.16.1-5.el5_1.1 is the new fixed > version) but in the fastrack channel there exists version 2.16.1-6 > which does not have an errata at this time. > > The changelog for the fastrack package suggests nothing about this > errata so I'm again asking for some mechanism to be found whereby > users who are concerned about security can determine whether a package > such as this is vulnerable or not. If it is known to be not vulnerable > please include this information in the released errata. > > And if someone could tell me whether or not it is vulnerable that > would be swell too for this case. > Hello John, The FasTrack channel provides early access to content scheduled for an upcoming minor release of Red Hat Enterprise Linux. In the case of gnome-screensaver we released an asynchronous update today, prior to 5.2, to fix a moderate severity security issue. This means that we needed to respin the gnome-screensaver update for 5.2 and repush the FasTrack package so it correctly reflects what will go out in 5.2. We did plan on repushing the FasTrack package today, but our Quality Engineering team spotted a regression which required a package rebuild. Updated gnome-screensaver packages will be pushed to FasTrack this week, but it will probably not be today to allow time for proper testing. In general if you have any questions about security vulnerabilities and how they affect any Red Hat product or service you can contact Red Hat Support Services or ask the Red Hat Security Response Team directly: http://www.redhat.com/security/team/contact/ Let me know if you have any additional questions. Thanks, Josh -- Josh Bressers // Red hat Security Response Team From inode0 at gmail.com Wed Apr 2 18:13:34 2008 From: inode0 at gmail.com (inode0) Date: Wed, 2 Apr 2008 13:13:34 -0500 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: <28409.1207154519@devserv.devel.redhat.com> References: <28409.1207154519@devserv.devel.redhat.com> Message-ID: On Wed, Apr 2, 2008 at 11:41 AM, Josh Bressers wrote: > Hello John, > > The FasTrack channel provides early access to content scheduled for an > upcoming minor release of Red Hat Enterprise Linux. In the case of > gnome-screensaver we released an asynchronous update today, prior to 5.2, > to fix a moderate severity security issue. This means that we needed to > respin the gnome-screensaver update for 5.2 and repush the FasTrack > package so it correctly reflects what will go out in 5.2. > > We did plan on repushing the FasTrack package today, but our Quality > Engineering team spotted a regression which required a package rebuild. > Updated gnome-screensaver packages will be pushed to FasTrack this > week, but it will probably not be today to allow time for proper testing. > > In general if you have any questions about security vulnerabilities and > how they affect any Red Hat product or service you can contact Red Hat > Support Services or ask the Red Hat Security Response Team directly: > http://www.redhat.com/security/team/contact/ > > Let me know if you have any additional questions. Hi Josh, Thanks so much for the explanation. I'll try to be more patient for fastrack updates in the future now that I better understand the build process involved for those. The Red Hat Security Response Team is in my opinion the crown jewel of Red Hat support. You do a great job both in terms of providing timely security fixes and in terms of helping users understand issues that arise that concern them. I have in the past sent inquiries to the address indicated above and received timely and detailed information about those concerns. But for something this trivial I hate to pester the SRT. One shortcoming in the security offerings provided by Red Hat is an easy way to audit for known vulnerabilities in installed packages. The security plugin is a wonderful addition in this regard but still doesn't (or perhaps I just don't quite know how to use it yet) cover the case where there is a known vulnerability but no errata has been issued (or sometimes will ever be issued) for it. When a decision is made not to fix security issues in a package I would really like this to be documented somewhere so users like me can learn why and understand what I should or shouldn't do as a consequence of Red Hat's decision. Issuing something like WONTFIX errata would be something I'd very much like to see. It seems the only way to get this information now is to contact the Security Response Team directly and ask. Thanks, John From bressers at redhat.com Wed Apr 2 18:52:10 2008 From: bressers at redhat.com (Josh Bressers) Date: Wed, 02 Apr 2008 14:52:10 -0400 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: References: <28409.1207154519@devserv.devel.redhat.com> Message-ID: <3148.1207162330@devserv.devel.redhat.com> > > Thanks so much for the explanation. I'll try to be more patient for > fastrack updates in the future now that I better understand the build > process involved for those. > > The Red Hat Security Response Team is in my opinion the crown jewel of > Red Hat support. You do a great job both in terms of providing timely > security fixes and in terms of helping users understand issues that > arise that concern them. Thank you! We're always glad to receive feedback, especially positive feedback. > > I have in the past sent inquiries to the address indicated above and > received timely and detailed information about those concerns. But for > something this trivial I hate to pester the SRT. This certainly wouldn't have been a problem. We're happy to answer all inquiries. None are too big or too small. > > One shortcoming in the security offerings provided by Red Hat is an > easy way to audit for known vulnerabilities in installed packages. The > security plugin is a wonderful addition in this regard but still > doesn't (or perhaps I just don't quite know how to use it yet) cover > the case where there is a known vulnerability but no errata has been > issued (or sometimes will ever be issued) for it. > > When a decision is made not to fix security issues in a package I > would really like this to be documented somewhere so users like me can > learn why and understand what I should or shouldn't do as a > consequence of Red Hat's decision. Issuing something like WONTFIX > errata would be something I'd very much like to see. It seems the only > way to get this information now is to contact the Security Response > Team directly and ask. > This information is currently captured via bugzilla and NVD. We are working on a better solution, but for the moment, you have to know how the process works to get your answers. As always, you can mail the Security Response Team with questions. We track all public CVE ids via bugzilla, assigning the CVE id to the bug alias. This means for example that if you wanted information regarding CVE-2008-0887, you could issue this query: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-0887 We tend not to include CVE ids for issues that don't affect Red Hat products in bugzilla, so we issue NVD statements for that purpose. For example, there was recently a GnuPG flaw that did not affect Red Hat Enterprise Linux (See the Vendor Statements section): https://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1530 Thanks again. -- Josh Bressers // Red Hat Security Response Team From fedora at scrunch.net Fri Apr 4 02:53:00 2008 From: fedora at scrunch.net (Bob - Fedora) Date: Thu, 03 Apr 2008 22:53:00 -0400 Subject: [rhn-users] Lanscape Printing Fails under RHEL5.1 Message-ID: <47F5980C.6030202@scrunch.net> I migrated from RHEL4.6 with cups-1.1.22 to RHEL5.1 with cups-1.2.4 and I find that I can not print landscape. Normally I do this: date | lp -o landscape But that no longer works. This is using HP printers, direct to the socket 9100. I've tried several model, including: HP LaserJet 4 with the hpijs driver HP LaserJet 4000 with postscript driver And several PPDs, those bundled with the os as part of foomatic and current ones from linuxprinting.org. With '-o landscape' it still prints in portrait. With '-o orientation-requested=4' there is no output, or it is rotated off the page. I don't know where to turn or how to resolv this. Any ideas on how to proceed will be greatly appreciated! From akrherz at iastate.edu Sun Apr 6 03:37:18 2008 From: akrherz at iastate.edu (Daryl Herzmann) Date: Sat, 5 Apr 2008 22:37:18 -0500 (CDT) Subject: [rhn-users] RHN 5.0.5 release notes? Message-ID: Hi, Are there any release notes for the 5.0.5 hosted release this morning? thanks! daryl From mark.ballard at murraystate.edu Sun Apr 6 15:59:07 2008 From: mark.ballard at murraystate.edu (mark.ballard at murraystate.edu) Date: Sun, 6 Apr 2008 10:59:07 -0500 Subject: [rhn-users] Autoreply: rhn-users Digest, Vol 50, Issue 4 Message-ID: <200804061802.m36I20BT011743@mx3.redhat.com> Thank you for your e-mail. I will be out of the office until April 14th and not have any access to e-mail during this time. I will respond to any e-mails Monday 4/14/08. If you need immediate assistance, please contact Dave McKenna (dave.mckenna at MurrayState.edu) at 809-3909, or the Help Desk at 809-2346. Thanks, Mark R. Ballard Database Administrator Murray State University mark.ballard at murraystate.edu Office: (270) 809-5393 Dept: (270) 809-2154 Fax: (270) 809-3465 From msuchy at redhat.com Tue Apr 8 08:34:48 2008 From: msuchy at redhat.com (=?ISO-8859-1?Q?Miroslav_Such=FD?=) Date: Tue, 08 Apr 2008 10:34:48 +0200 Subject: [rhn-users] Re: [rhn-satellite-users] Announcing Red Hat Network Satellite 5.1.0 In-Reply-To: References: <47F96D97.8070100@redhat.com> Message-ID: <47FB2E28.9020306@redhat.com> Moralejo, Alfredo wrote: > Just to be sure, In the mail it's mentioned Red Hat Network Satellite > (v5.1 for AS v4 amd64). All x86_64 archs, including EM64T, are > supported, right? IMO amd64 == x86_64 == EM64T > Regarding proxy, is there any updated documentation?, last manual I find > is installation guide for version 4.1.0, maybe I'm looking in the wrong > place... Member of our team, who used to write doc, suddenly left our team. So we did not manage to write up Proxy documentation. It will be released in version 5.1.1. But only one major feature in Proxy documentation is that from now, you can remove and install proxy again without the need to reinstall OS. -- Miroslav Suchy RHN Satellite Engineering, Red Hat From samer.azmy at gmail.com Tue Apr 8 09:06:59 2008 From: samer.azmy at gmail.com (sazmy) Date: Tue, 8 Apr 2008 09:06:59 +0000 Subject: [rhn-users] sazmy wants to keep up with you on Twitter Message-ID: <47fb35b36a933_31da15555672002c156df@twitter-web052.twitter.com.tmail> To find out more about Twitter, visit the link below: http://twitter.com/i/857f376373f5cfc5cb23ab1c94fdb168c63682ef Thanks, -The Twitter Team About Twitter Twitter is a unique approach to communication and networking based on the simple concept of status. What are you doing? What are your friends doing?right now? With Twitter, you may answer this question over SMS, IM, or the Web and the responses are shared between contacts. From inode0 at gmail.com Wed Apr 9 05:44:27 2008 From: inode0 at gmail.com (inode0) Date: Wed, 9 Apr 2008 00:44:27 -0500 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: <3148.1207162330@devserv.devel.redhat.com> References: <28409.1207154519@devserv.devel.redhat.com> <3148.1207162330@devserv.devel.redhat.com> Message-ID: On Wed, Apr 2, 2008 at 1:52 PM, Josh Bressers wrote: > > > > One shortcoming in the security offerings provided by Red Hat is an > > easy way to audit for known vulnerabilities in installed packages. The > > security plugin is a wonderful addition in this regard but still > > doesn't (or perhaps I just don't quite know how to use it yet) cover > > the case where there is a known vulnerability but no errata has been > > issued (or sometimes will ever be issued) for it. > > > > When a decision is made not to fix security issues in a package I > > would really like this to be documented somewhere so users like me can > > learn why and understand what I should or shouldn't do as a > > consequence of Red Hat's decision. Issuing something like WONTFIX > > errata would be something I'd very much like to see. It seems the only > > way to get this information now is to contact the Security Response > > Team directly and ask. > > > > This information is currently captured via bugzilla and NVD. We are > working on a better solution, but for the moment, you have to know how the > process works to get your answers. As always, you can mail the Security > Response Team with questions. > > We track all public CVE ids via bugzilla, assigning the CVE id to the bug > alias. This means for example that if you wanted information regarding > CVE-2008-0887, you could issue this query: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-0887 I'm not really seeing how this is useful to me in general. For example, consider https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-0005 While we get a hit there is no comment about RHEL versions of httpd and I'm denied access to bz entries depending on this one. Consider also https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2007-5000 Again nothing about RHEL versions. Both of these were covered by https://rhn.redhat.com/errata/RHSA-2008-0006.html and related errata. I can tell from the errata released that all the versions of apache that lived in the base channels were affected. However if I am running another version of apache for example, which did not have an errata released for it, I can tell nothing about exposures to these vulnerabilities. > We tend not to include CVE ids for issues that don't affect Red Hat > products in bugzilla, so we issue NVD statements for that purpose. For > example, there was recently a GnuPG flaw that did not affect Red Hat > Enterprise Linux (See the Vendor Statements section): > https://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1530 So I go check https://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-0005 and I see links from Red Hat for the various errata they released. There is no information that I can find about any statement from Red Hat describing affected packages that are supported by Red Hat but not covered by those errata. Statements that such and such a package is not affected are very nice, but I want to know when such and such a package is affected and is not being fixed and the reason for that decision. Typically those decisions are made based on assumptions, and I want those assumptions to be true if I am running a package with unpatched known vulnerabilities. Asking the customer to wade through 5 errata, notice that some installed package wasn't covered by any of them, visit bugzilla and NVD, throw up his hands and send you email is I think asking too much from the customer. If Red Hat chooses to leave some package unpatched, for reasons that may be justifiable (incredibly low risk, not exploitable in default or common configurations, etc.) I think Red Hat has an obligation to make that decision known to customers using the affected packages - well, really all customers. We might not be running them in a way that fits your assumptions and we should be aware of the risk. The customer should not need to recognize the danger and ask you, the customer should be informed by you when you make such decisions (in my dreamworld at least). I really can't see why delivering a notification of this sort is any harder than delivering an errata to me, unless the reason isn't technical. Thanks again Josh. John From bressers at redhat.com Wed Apr 9 11:18:39 2008 From: bressers at redhat.com (Josh Bressers) Date: Wed, 09 Apr 2008 07:18:39 -0400 Subject: [rhn-users] Security Errata not covering all versions of RHEL packages In-Reply-To: References: <28409.1207154519@devserv.devel.redhat.com> <3148.1207162330@devserv.devel.redhat.com> Message-ID: <8902.1207739919@devserv.devel.redhat.com> > > I'm not really seeing how this is useful to me in general. For example, consider > > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2008-0005 > > While we get a hit there is no comment about RHEL versions of httpd > and I'm denied access to bz entries depending on this one. This is true. We don't make this terribly clear. I shall see what I can do to clear that up in the near future. > > Asking the customer to wade through 5 errata, notice that some > installed package wasn't covered by any of them, visit bugzilla and > NVD, throw up his hands and send you email is I think asking too much > from the customer. It's not ideal, I agree. I was just pointing out that there are a handful of places one could get this information. As always, just mail secalert at redhat.com with your question. It's easy and we'll get back to you promptly. > > If Red Hat chooses to leave some package unpatched, for reasons that > may be justifiable (incredibly low risk, not exploitable in default or > common configurations, etc.) I think Red Hat has an obligation to make > that decision known to customers using the affected packages - well, > really all customers. We might not be running them in a way that fits > your assumptions and we should be aware of the risk. The customer > should not need to recognize the danger and ask you, the customer > should be informed by you when you make such decisions (in my > dreamworld at least). > > I really can't see why delivering a notification of this sort is any > harder than delivering an errata to me, unless the reason isn't > technical. > We will take this into consideration. It's never really occurred to us honestly. We put a great deal of effort into fixing everything and anything that poses an imminent risk to our customers. It's the opinion of the Security Response Team that a great deal of our added value is that customers don't have to worry about every little security thing that comes along since we handle them. Thank you for your feedback, it's most appreciated. -- Josh Bressers // Red Hat Security Response Team From duffy at redhat.com Thu Apr 10 21:46:08 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Thu, 10 Apr 2008 17:46:08 -0400 Subject: [rhn-users] Satellite Multi-Org Survey - We'd Love Your Feedback! Message-ID: <47FE8AA0.5050605@redhat.com> Hi folks, The RHN Satellite Engineering Team has put together a survey to learn how we can best improve this feature in the next release of Satellite. (Not sure what the multiple organization support feature is all about? [1]) You do not need to have made use of the multiple organization support feature in order to fill out this survey - the survey presents some details about how the feature works and asks for you to talk about how different parts of it may or may not fit your organization's needs. The survey also has a lot of free-form questions; depending on how many questions you choose to answer it may take between 15-40 minutes to complete. We would really appreciate any feedback you might have time to give us to help us improve the Satellite product. Your feedback will have a direct impact on the future development of this feature. Here is a link to the survey: http://www.keysurvey.com/survey/198531/2301 Thanks for helping us make Satellite a better product! ~m (P.S. In the past few days I've received a lot of feedback about both the multi-org feature and the proposed read-only user feature both here on list and directly. Thank you so much!! It will take me a little time to sort through everything but we will definitely be following up on your feedback.) [1] See https://rhn-satellite.108.redhat.com/wiki/index.php/Satellite_5.1_MultiOrg_Feature_Preview From duffy at redhat.com Fri Apr 11 16:41:55 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Fri, 11 Apr 2008 12:41:55 -0400 Subject: [rhn-users] Satellite 5.1 Multi-Org Whitepaper Now Available Message-ID: <47FF94D3.6080207@redhat.com> Hi folks, The Satellite team has written a new whitepaper to cover best practices for using the new multiple organization support feature in Satellite 5.1. We've outlined how we intended for the feature to be used in a task-oriented manner with recommendations and explanations of the reasons behind the recommendations. We've also included a section entitled 'Pitfalls to Watch Out For' which is essentially a troubleshooting guide for the feature and also outlines some of the changes you can expect to occur after upgrading a previous installation of Satellite to version 5.1. RHN Satellite: Best Practices for Multiple Organizations https://rhn-satellite.108.redhat.com/wiki/images/a/ac/Satellite-51-multiorg-whitepaper.pdf Parts of this document are based on the questions and feedback we've received from many of you regarding the feature. We believe that this document is much more useful than it would have been without your feedback, so thank you for your help! :) Thanks again, ~m From akrherz at iastate.edu Fri Apr 11 19:23:56 2008 From: akrherz at iastate.edu (Daryl Herzmann) Date: Fri, 11 Apr 2008 14:23:56 -0500 (CDT) Subject: [rhn-users] Re: RHN 5.0.5 release notes? In-Reply-To: References: Message-ID: On Sat, 5 Apr 2008, Daryl Herzmann wrote: > Hi, > > Are there any release notes for the 5.0.5 hosted release this morning? Sorry to be a bother, but could the release notes be put somewhere? I probably come off as a jerk about this, but why does redhat keep doing this? Could the rhn hosted release manager explain why the lack of release notes is not a blocker for a rhn hosted release? Rewording, shouldn't the release notes be a requirement for a release? If this was an isolated incident, maybe it wouldn't be such a big deal. But this has happend with 5.0.1 , 5.0.2 , 5.0.3 and perhaps others prior to rhn 5. 5.0.3 http://www.redhat.com/archives/rhn-users/2007-October/msg00003.html 5.0.2 https://wiki.108.redhat.com/wiki/index.php/Hosted502Documentation 5.0.1 https://www.redhat.com/archives/rhn-users/2007-May/msg00034.html Frustrated, daryl From duffy at redhat.com Tue Apr 15 21:19:32 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Tue, 15 Apr 2008 17:19:32 -0400 Subject: [rhn-users] Re: [rhn-satellite-users] Announcing Red Hat Network Satellite 5.1.0 In-Reply-To: References: <47F96D97.8070100@redhat.com> Message-ID: <48051BE4.2090109@redhat.com> Hi Alfredo, Moralejo, Alfredo wrote: > Just to be sure, In the mail it's mentioned Red Hat Network Satellite > (v5.1 for AS v4 amd64). All x86_64 archs, including EM64T, are > supported, right? We updated the channel name so it now reads: "Red Hat Network Satellite (v5.1 for AS v4 AMD64 / Intel64)" It absolutely works on all x86_64 arches, so hopefully the updated channel name will help reduce confusion. Thanks for pointing this out! ~m From duffy at redhat.com Tue Apr 15 21:23:14 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Tue, 15 Apr 2008 17:23:14 -0400 Subject: [rhn-users] Re: [rhn-satellite-users] Satellite Multi-Org Survey - We'd Love Your Feedback! In-Reply-To: <47FE8AA0.5050605@redhat.com> References: <47FE8AA0.5050605@redhat.com> Message-ID: <48051CC2.3030004@redhat.com> Hi folks, M?ir?n Duffy wrote: > We would really appreciate any feedback you might have time to give us > to help us improve the Satellite product. Your feedback will have a > direct impact on the future development of this feature. Here is a link > to the survey: > > http://www.keysurvey.com/survey/198531/2301 I just wanted to send out a quick reminder about this survey; I'll send out another one a week before it closes. I haven't seen as many responses as I was hoping for (thank you to those who did respond!) so I thought it might be a good idea to bring it up again. This survey is a great opportunity to help shape the next release of Satellite; if you have the time to fill it out (even if only partially) we would very much appreciate it. Thanks again, ~m From james.a.sterling at boeing.com Wed Apr 16 12:30:48 2008 From: james.a.sterling at boeing.com (Sterling, James A) Date: Wed, 16 Apr 2008 08:30:48 -0400 Subject: [rhn-users] Re: [rhn-satellite-users] Satellite Multi-Org Survey -We'd Love Your Feedback! In-Reply-To: <48051CC2.3030004@redhat.com> References: <47FE8AA0.5050605@redhat.com> <48051CC2.3030004@redhat.com> Message-ID: <2D40BC237027834D92174FD129DDF71304CA00B6@XCH-NE-1V1.ne.nos.boeing.com> Tried to do the survey.. Keep getting error message of enter value greater then 1 ??? Sorry Jim Sterling Subject: [rhn-users] Re: [rhn-satellite-users] Satellite Multi-Org Survey -We'd Love Your Feedback! Hi folks, > > http://www.keysurvey.com/survey/198531/2301 would very much appreciate it. Thanks again, ~m _______________________________________________ rhn-users mailing list rhn-users at redhat.com https://www.redhat.com/mailman/listinfo/rhn-users From duffy at redhat.com Wed Apr 16 13:25:14 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Wed, 16 Apr 2008 09:25:14 -0400 Subject: [rhn-users] Re: [rhn-satellite-users] Satellite Multi-Org Survey -We'd Love Your Feedback! In-Reply-To: <2D40BC237027834D92174FD129DDF71304CA00B6@XCH-NE-1V1.ne.nos.boeing.com> References: <47FE8AA0.5050605@redhat.com> <48051CC2.3030004@redhat.com> <2D40BC237027834D92174FD129DDF71304CA00B6@XCH-NE-1V1.ne.nos.boeing.com> Message-ID: <4805FE3A.2090608@redhat.com> Hi Jim, Sterling, James A wrote: > Tried to do the survey.. Keep getting error message of enter value > greater then 1 ??? Hmm did you fill out all the questions? It could be the radio button ones really want you to fill in something. Could you fill out 'don't know' for each if you want to skip it? Or, if you still have it open (I realize probably not likely at this point), if you'd be willing to copy & paste your answers and email to me that would be great. ~m From duffy at redhat.com Wed Apr 16 17:25:45 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Wed, 16 Apr 2008 13:25:45 -0400 Subject: [rhn-users] Re: [rhn-satellite-users] Satellite 5.1 Multi-Org Whitepaper Now Available In-Reply-To: <47FF94D3.6080207@redhat.com> References: <47FF94D3.6080207@redhat.com> Message-ID: <48063699.8040708@redhat.com> Hi folks, M?ir?n Duffy wrote: > RHN Satellite: Best Practices for Multiple Organizations > https://rhn-satellite.108.redhat.com/wiki/images/a/ac/Satellite-51-multiorg-whitepaper.pdf Please note that this paper has been updated and a new version uploaded to the URL above (a corrected version will also appear at redhat.com/rhn shortly). There was a mistake in the 'Pitfalls' section that incorrectly described how the new activation key format affects pre-existing activation keys (pages 17-18). Thanks to Jack who brought up the question that made this mistake evident. I apologize if this error tripped anyone up! ~m From tsutter at cincom.com Thu Apr 17 16:13:29 2008 From: tsutter at cincom.com (Sutter, Tim) Date: Thu, 17 Apr 2008 12:13:29 -0400 Subject: [rhn-users] RHES for the s390x platform Message-ID: Hi, New to this. I have been trying, unsuccessfully, to get a copy of RHES, to run on my IBM z9 mainframe. I have signed up for the 30 day evaluation, but this system does not appear as an option to download. I opened a support question, they said check with sales. I sent an email to sales, they don't seem to care, since they have never returned my email. Does anyone know how to get a copy, so that I can evaluate it. Thanks Tim From duffy at redhat.com Tue Apr 22 14:15:32 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Tue, 22 Apr 2008 10:15:32 -0400 Subject: [rhn-users] Satellite Inter-Satellite Sync Customer Call-In next Thursday Message-ID: <480DF304.6000402@redhat.com> Hi folks, One potential Satellite feature some of you have mentioned might be useful for your organizations is inter-Satellite sync - the ability for Satellites to register to one another and sync content from each other. In the recent Satellite 5.1 release, we have made some progress towards this feature with the new Satellite exporter tool. (For more information on the exporter tool, please refer to [1].) We'd like to learn more about your needs and issues-to-solve with respect to this feature, so we are holding an hour-long call next Thursday to discuss the inter-Satellite sync feature. This is a great opportunity to interact directly with the Satellite engineering team and to make sure that your use case for this feature is considered in its development. If you'd like to participate in this meeting, sign up by dropping me an email and I will send the dial-in information back to you. We will be limiting the call to about 20 participants; if there is sufficient demand we'll schedule another meeting. Date: May 1, 2008 Time: 11 AM EDT (1500 UTC) Thanks! ~m [1] http://www.redhatmagazine.com/2008/04/03/how-to-populate-content-on-a-disconnected-satellite/ From duffy at redhat.com Mon Apr 28 19:10:53 2008 From: duffy at redhat.com (=?ISO-8859-1?Q?M=E1ir=EDn_Duffy?=) Date: Mon, 28 Apr 2008 15:10:53 -0400 Subject: [rhn-users] Satellite Inter-Satellite Sync Customer Call-In (this) Thursday In-Reply-To: <480DF304.6000402@redhat.com> References: <480DF304.6000402@redhat.com> Message-ID: <4816213D.1000807@redhat.com> Hi folks, Just wanted to let you know that there are still spaces left in this call this Thursday, so if you think you might be interested just let me know and I'll send you the dial-in details. (Also, I apologize for the poor timing on Labor Day in many countries; if you are interested but can't make this day let me know and we might be able to hold another session.) Thanks! ~m M?ir?n Duffy wrote: > Hi folks, > > One potential Satellite feature some of you have mentioned might be > useful for your organizations is inter-Satellite sync - the ability for > Satellites to register to one another and sync content from each other. > In the recent Satellite 5.1 release, we have made some progress towards > this feature with the new Satellite exporter tool. (For more information > on the exporter tool, please refer to [1].) > > We'd like to learn more about your needs and issues-to-solve with > respect to this feature, so we are holding an hour-long call next > Thursday to discuss the inter-Satellite sync feature. This is a great > opportunity to interact directly with the Satellite engineering team and > to make sure that your use case for this feature is considered in its > development. > > If you'd like to participate in this meeting, sign up by dropping me an > email and I will send the dial-in information back to you. We will be > limiting the call to about 20 participants; if there is sufficient > demand we'll schedule another meeting. > > Date: May 1, 2008 > Time: 11 AM EDT (1500 UTC) > > Thanks! > ~m > > [1] > http://www.redhatmagazine.com/2008/04/03/how-to-populate-content-on-a-disconnected-satellite/ > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users