From solarflow99 at gmail.com Fri Jan 4 02:20:15 2013 From: solarflow99 at gmail.com (solarflow99) Date: Thu, 3 Jan 2013 21:20:15 -0500 Subject: [rhelv6-list] dhcpd question: limiting scope to mac address identifiers In-Reply-To: References: Message-ID: Thanks for the tip, I got it working, but still couldn't stop the dhcp servers from interfering with each other. I see a lot of messages like this in syslog: DHCPDISCOVER from 1c:b0:94:31:20:98 via eth0: network 192.168.2.0/24: no free leases It might be a client side problem for not ignoring the NAK offer and picking up the right one from the other dhcp server, since some clients do work. On Fri, Dec 28, 2012 at 9:21 AM, Greg Swift wrote: > > > > On Thu, Dec 27, 2012 at 7:41 PM, solarflow99 wrote: >> >> I have been testing with a second dhcp server on the same vlan, and >> wanted to limit the scope to only serve out to clients that have mac >> addresses that start with the same 3 octets, something like this >> maybe? >> >> >> class "custom-clients" { >> match if substring (option dhcp-client-identifier, 00:50:56); >> } >> >> deny unknown-clients; >> > > you are very close. if you search for 'isc dhcp match vendor' you should > get a lot of helpful information. You can simply use the hardware address > rather than an option. Plus unknown-clients refers to systems that do not > have a host entry in your file. In this case none do, so all clients would > be denied. You can either do an allow block: > > or > > class "good" { > match if substring(hardware,1,3) = AA:BB:CC; > } > > allow members of "good"; > > > > > or a deny block > > > class "bad" { > match if not substring(hardware,1,3) = AA:BB:CC; > } > > deny members of "bad"; > > > In an ideal world they work the same, but test it out and see how they do > for your use case. > > -greg > > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list From greg at nytefyre.net Fri Jan 4 03:50:10 2013 From: greg at nytefyre.net (Greg Swift) Date: Thu, 3 Jan 2013 21:50:10 -0600 Subject: [rhelv6-list] dhcpd question: limiting scope to mac address identifiers In-Reply-To: References: Message-ID: are you using non-authoritative ? I'm not sure exact way to implement it in your environment, but it might work. -greg On Thu, Jan 3, 2013 at 8:20 PM, solarflow99 wrote: > Thanks for the tip, I got it working, but still couldn't stop the dhcp > servers from interfering with each other. I see a lot of messages > like this in syslog: > > DHCPDISCOVER from 1c:b0:94:31:20:98 via eth0: network 192.168.2.0/24: > no free leases > > It might be a client side problem for not ignoring the NAK offer and > picking up the right one from the other dhcp server, since some > clients do work. > > > > > On Fri, Dec 28, 2012 at 9:21 AM, Greg Swift wrote: > > > > > > > > On Thu, Dec 27, 2012 at 7:41 PM, solarflow99 > wrote: > >> > >> I have been testing with a second dhcp server on the same vlan, and > >> wanted to limit the scope to only serve out to clients that have mac > >> addresses that start with the same 3 octets, something like this > >> maybe? > >> > >> > >> class "custom-clients" { > >> match if substring (option dhcp-client-identifier, 00:50:56); > >> } > >> > >> deny unknown-clients; > >> > > > > you are very close. if you search for 'isc dhcp match vendor' you should > > get a lot of helpful information. You can simply use the hardware > address > > rather than an option. Plus unknown-clients refers to systems that do > not > > have a host entry in your file. In this case none do, so all clients > would > > be denied. You can either do an allow block: > > > > or > > > > class "good" { > > match if substring(hardware,1,3) = AA:BB:CC; > > } > > > > allow members of "good"; > > > > > > > > > > or a deny block > > > > > > class "bad" { > > match if not substring(hardware,1,3) = AA:BB:CC; > > } > > > > deny members of "bad"; > > > > > > In an ideal world they work the same, but test it out and see how they do > > for your use case. > > > > -greg > > > > > > _______________________________________________ > > rhelv6-list mailing list > > rhelv6-list at redhat.com > > https://www.redhat.com/mailman/listinfo/rhelv6-list > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias at saou.eu Fri Jan 4 12:01:23 2013 From: matthias at saou.eu (Matthias Saou) Date: Fri, 4 Jan 2013 13:01:23 +0100 Subject: [rhelv6-list] Trying to find utilities to manage a Dell Perc 5i (not integrated) from RHEL6 In-Reply-To: <50D75316.7090108@camerontech.com> References: <50D73B80.4010002@camerontech.com> <50D75316.7090108@camerontech.com> Message-ID: <20130104130123.3e4777f7@r2d2.marmotte.net> On Sun, 23 Dec 2012 12:53:10 -0600 Thomas Cameron wrote: > I found out in #rhel on Freenode that the "integrated" PERC 5i is only > called that because it's on a dedicated PCI-E slot. So the device I > have *is* considered the "integrated" version. Weird. > > I just drilled down in the PowerEdge 2950 at Dell.com and found the > latest firmware and utilities for the PERC 5i integrated. They > installed just fine, the firmware is as modern as it gets. > > Sorry for the noise, but I hope anyone else who is confused by the > "integrated" label on this controller finds this post and it helps. My rule of thumb regarding PERC controllers : * 'i' means 'Internal', as in "only internal connectors" * 'E' (uppercase) means 'External', as in "external connectors" * 'e' (lowercase) meant 'PCI expresss', when PCI-X was still common And if you ever want to manage those cards' firmware without having to hunt for the right binary on the Dell website, nor having to install a full blown OMSA (I like minimal systems, for instance), then you could also checkout this disposable chroot I've created : http://glee.thias.es/OMSA HTH, Matthias -- Matthias Saou ?? ?? ?? ?? Web: http://matthias.saou.eu/ ?????????????? Mail/XMPP: matthias at saou.eu ???? ?????? ???? ?????????????????????? GPG: 4096R/E755CC63 ?? ?????????????? ?? 8D91 7E2E F048 9C9C 46AF ?? ?? ?? ?? 21A9 7A51 7B82 E755 CC63 ???? ???? From solarflow99 at gmail.com Sun Jan 6 23:13:57 2013 From: solarflow99 at gmail.com (solarflow99) Date: Sun, 6 Jan 2013 18:13:57 -0500 Subject: [rhelv6-list] dhcpd question: limiting scope to mac address identifiers In-Reply-To: References: Message-ID: hmm, looks like that did it. now its ignoring all the client dhcp requests except from the correct ones. Thanks, On Thu, Jan 3, 2013 at 10:50 PM, Greg Swift wrote: > are you using non-authoritative ? I'm not sure exact way to implement it in > your environment, but it might work. > > -greg > > > On Thu, Jan 3, 2013 at 8:20 PM, solarflow99 wrote: >> >> Thanks for the tip, I got it working, but still couldn't stop the dhcp >> servers from interfering with each other. I see a lot of messages >> like this in syslog: >> >> DHCPDISCOVER from 1c:b0:94:31:20:98 via eth0: network 192.168.2.0/24: >> no free leases >> >> It might be a client side problem for not ignoring the NAK offer and >> picking up the right one from the other dhcp server, since some >> clients do work. >> >> >> >> >> On Fri, Dec 28, 2012 at 9:21 AM, Greg Swift wrote: >> > >> > >> > >> > On Thu, Dec 27, 2012 at 7:41 PM, solarflow99 >> > wrote: >> >> >> >> I have been testing with a second dhcp server on the same vlan, and >> >> wanted to limit the scope to only serve out to clients that have mac >> >> addresses that start with the same 3 octets, something like this >> >> maybe? >> >> >> >> >> >> class "custom-clients" { >> >> match if substring (option dhcp-client-identifier, 00:50:56); >> >> } >> >> >> >> deny unknown-clients; >> >> >> > >> > you are very close. if you search for 'isc dhcp match vendor' you >> > should >> > get a lot of helpful information. You can simply use the hardware >> > address >> > rather than an option. Plus unknown-clients refers to systems that do >> > not >> > have a host entry in your file. In this case none do, so all clients >> > would >> > be denied. You can either do an allow block: >> > >> > or >> > >> > class "good" { >> > match if substring(hardware,1,3) = AA:BB:CC; >> > } >> > >> > allow members of "good"; >> > >> > >> > >> > >> > or a deny block >> > >> > >> > class "bad" { >> > match if not substring(hardware,1,3) = AA:BB:CC; >> > } >> > >> > deny members of "bad"; >> > >> > >> > In an ideal world they work the same, but test it out and see how they >> > do >> > for your use case. >> > >> > -greg >> > >> > >> > _______________________________________________ >> > rhelv6-list mailing list >> > rhelv6-list at redhat.com >> > https://www.redhat.com/mailman/listinfo/rhelv6-list >> >> _______________________________________________ >> rhelv6-list mailing list >> rhelv6-list at redhat.com >> https://www.redhat.com/mailman/listinfo/rhelv6-list > > > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list From rhelv6-list at redhat.com Tue Jan 8 16:13:26 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Tue, 8 Jan 2013 16:13:26 +0000 Subject: [rhelv6-list] Headless to desktop server? Message-ID: Hi, I have a headless RHEL 6.3 server which I now wish to add a GUI desktop environment to. What's the best way to add all the packages to support a desktop GUI? Is there a RPM meta package which will install all the required RPMS ? Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhelv6-list at redhat.com Tue Jan 8 18:47:01 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Tue, 08 Jan 2013 13:47:01 -0500 Subject: [rhelv6-list] Red Hat Enterprise Linux 5.9 GA Announcement Message-ID: <50EC69A5.4080800@redhat.com> Today, Red Hat announced the general availability of the next minor release of Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 5.9. We continue to work with our partners, customers and the open source community to deliver technology that is tested and stable ? and Red Hat Enterprise 5.9 illustrates that ongoing commitment. This release marks the beginning of Production Phase 2 of Red Hat Enterprise Linux 5, demonstrating the company's continued effort to promote stability and the preservation of customers' investments. The Red Hat Enterprise Linux 10-year lifecycle provides stability for customers who wish to remain on Red Hat Enterprise Linux 5 until they are ready to migrate to a newer version of Red Hat Enterprise Linux [1]. This release includes new functionality in the areas of virtualization, security, and networking; new support for standards and certifications; and enhancements to certificate-based Red Hat Subscription Management. New drivers for Microsoft Hyper-V enable customers to run Red Hat Enterprise Linux 5.9 as a virtual guest on Hyper-V with improved performance. Also included in this release are additions to capabilities for developers as well as support for our hardware partners that take advantage of the latest performance enhancements. Key functionality in Red Hat Enterprise Linux 5.9 includes: Enhanced Hardware Enablement Red Hat Enterprise Linux 5.9 showcases Red Hat's strong relationships with industry-leading hardware vendors. This minor release contains support for the latest CPU, chip set, and device driver enhancements from leading hardware vendors. Continued Commitment to Security, Standards, and Certifications Red Hat Enterprise Linux has always been built with security in mind ? a commitment that Red Hat Enterprise Linux 5.9 helps solidify. This update features tighter security controls, the ability to verify and check the robustness of new passwords, and support for the latest government password policy requirements. It also adds support for using Federal Information Processing Standard (FIPS) mode with dmraid root devices. FIPS mode now supports RAID device discovery, RAID set activation, and the creation, removal, rebuilding, and displaying of properties. New Developer Tools Red Hat Enterprise Linux 5.9 includes several new developer-friendly features and tools, including the ability to develop and test with the latest version of open source Java available through OpenJDK 7. Many new SystemTap improvements have been added to Red Hat Enterprise Linux 5.9, including compile-server and client support for IPv6 networks, smaller SystemTap files, faster compiles, and compile server support for multiple concurrent connections. Enhanced Application Support Red Hat Enterprise Linux 5.9 includes a new rsyslog5 package that upgrades rsyslog to major version 5. The rsyslog5 package runs faster and is more reliable than existing rsyslog packages. Samba has been updated to version 3.6. New features include fully featured SMB2 support, a reworked print server, and security default improvements for all versions of Samba. New Virtualization Capabilities and Flexibility in Multi-vendor Environments Red Hat Enterprise Linux 5.9 enhances the operating system's usability in multi-vendor environments by introducing Microsoft Hyper-V drivers for improved performance. This enhances the usability of Red Hat Enterprise Linux 5 for guests in a heterogeneous, multi-vendor virtualized environment and provides improved flexibility and interoperability for our customers. Enhanced Red Hat Subscription Management Red Hat Enterprise Linux 5.9 uses Red Hat Subscription Management as the default, allowing customers to effectively and more easily manage their Red Hat Enterprise Linux subscriptions locally or with tools such as Subscription Asset Manager which was enhanced to easily run reports on subscription distribution and utilization and an improved user interface. For more detail on how Red Hat customers can manage their subscriptions, please visit the Subscription Management section of the Red Hat Customer Portal. Although Red Hat Enterprise Linux will remain stable with only bug and security fixes during Production Phase 2 of its life cycle [1], we encourage our Red Hat Enterprise Linux 5 customers to consider upgrading to Red Hat Enterprise Linux 6 so they can take advantage of the latest features and hardware support available from our hardware partners. We greatly appreciate the dedication and collaboration within the company and with our community and customers to develop and deliver the highest quality enterprise platform available today. Sincerely, The Red Hat Enterprise Linux Team [1] All details of the Red Hat Enterprise Linux Life Cycle and release schedules are available here: https://access.redhat.com/support/policy/updates/errata/ To read the Red Hat Enterprise Linux 5.9 press release with supporting customer quote, please visit: http://www.redhat.com/about/news/press-archive/2013/1/red-hat-announces-general-availability-of-red-hat-enterprise-linux-5-9 To access and download an evaluation copy for Red Hat Enterprise Linux 5.9, please visit: https://rhn.redhat.com/rhn/software/channels/All.do Please note that this requires an active account on the Red Hat customer portal, and the user must filter and navigate to Red Hat Enterprise Linux 5 and the architecture of interest (e.g., x86_64, Power, System z, etc.). For access to the documentation for Red Hat Enterprise Linux 5.9 including the release notes, please visit: https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/ From rhelv6-list at redhat.com Tue Jan 8 19:02:25 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Tue, 8 Jan 2013 12:02:25 -0700 Subject: [rhelv6-list] Red Hat Enterprise Linux 5.9 GA Announcement In-Reply-To: <50EC69A5.4080800@redhat.com> References: <50EC69A5.4080800@redhat.com> Message-ID: <50EC6D41.1020602@rincon.com> On 01/08/13 11:47, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > Today, Red Hat announced the general availability of the next minor release of Red Hat Enterprise > Linux 5, Red Hat Enterprise Linux 5.9. > > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list Wouldn't it be more appropriate to post this to the rhelv5-list ? I'm interested ... but there are probably more interested parties on the other list. Cheers, -Bob Arendt From rhelv6-list at redhat.com Tue Jan 8 19:03:24 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Tue, 8 Jan 2013 13:03:24 -0600 Subject: [rhelv6-list] Headless to desktop server? In-Reply-To: References: Message-ID: <50EC6D7C.5070509@fnal.gov> On 01/08/2013 10:13 AM, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > Hi, > > I have a headless RHEL 6.3 server which I now wish to add a GUI > desktop environment to. What's the best way to add all the packages to > support a desktop GUI? Is there a RPM meta package which will install > all the required RPMS ? > > Paul > > > Depending on your desktop of choice, there are are options for Gnome or KDE. yum grouplist should give you something to work with. Pat -- Pat Riehecky From rhelv6-list at redhat.com Tue Jan 8 19:11:08 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Tue, 08 Jan 2013 14:11:08 -0500 Subject: [rhelv6-list] Headless to desktop server? In-Reply-To: References: Message-ID: <50EC6F4C.5010200@vt.edu> Paul, "yum grouplist" will show you the available groups that can be installed. "yum groupinstall desktop" would probably get you what you wanted. Thanks, Brandon On 01/08/2013 11:13 AM, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > Hi, > > I have a headless RHEL 6.3 server which I now wish to add a GUI > desktop environment to. What's the best way to add all the packages to > support a desktop GUI? Is there a RPM meta package which will install > all the required RPMS ? > > Paul > > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhelv6-list at redhat.com Wed Jan 9 01:55:43 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Wed, 09 Jan 2013 11:55:43 +1000 Subject: [rhelv6-list] Headless to desktop server? In-Reply-To: References: Message-ID: <50ECCE1F.90304@uq.edu.au> On 01/09/13 02:13, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > I have a headless RHEL 6.3 server which I now wish to add a GUI > desktop environment to. What's the best way to add all the > packages to support a desktop GUI? Is there a RPM meta package > which will install all the required RPMS ? This should be a reasonable start: @x11 @basic-desktop @desktop-debugging @desktop-platform @general-desktop @internet-browser @fonts @internet-applications @legacy-x nedit thunderbird vim-X11 alacarte seahorse-plugins gedit-plugins For KDE add: @kde-desktop xsettings-kde Install groups (@...) with yum groupinstall. -- Ian From rhelv6-list at redhat.com Fri Jan 11 10:33:02 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Fri, 11 Jan 2013 11:33:02 +0100 Subject: [rhelv6-list] Info on kernel module priority when different one with same name Message-ID: Hello, I'm testing an updated be2net kernel module provided by HP on their driver page. The system is 6.2 and I built be2net version 4.1.450.7 as it seems it is required for a virtual connect upgrade where the physical HP blade is. My kernel is 2.6.32-220.4.2 and comes with be2net driver 4.0.160r . The latest available from Red Hat is 2.6.32-279.19.1 that contains 4.1.307r Reading depmod docs I see that currently I have (default) configuration: /etc/depmod.d/dist.conf search updates extra built-in weak-updates Is it correct to say that this mean that if the HP rpm binary I built installs be2net.ko in extra, I'm ok without doing anything? And that if I want to test the two ones and sometimes to revert to old driver loading without removing the HP one, I can then add when I need it the line: override be2net * built-in ? Thanks in advance, Gianluca -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhelv6-list at redhat.com Fri Jan 11 15:02:33 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Fri, 11 Jan 2013 16:02:33 +0100 Subject: [rhelv6-list] Andreas Reschke is out of the office Message-ID: Ich werde ab 11.01.2013 nicht im B?ro sein. Ich kehre zur?ck am 21.01.2013. From rhelv6-list at redhat.com Sat Jan 12 19:01:35 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Sat, 12 Jan 2013 15:31:35 -0330 Subject: [rhelv6-list] Info on kernel module priority when different one with same name In-Reply-To: References: Message-ID: <20130112190135.GA29324@plebeian> Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > Hello, > I'm testing an updated be2net kernel module provided by HP on their driver > page. > The system is 6.2 and I built be2net version 4.1.450.7 as it seems it is > required for a virtual connect upgrade where the physical HP blade is. > > My kernel is 2.6.32-220.4.2 and comes with be2net driver 4.0.160r . > The latest available from Red Hat is 2.6.32-279.19.1 that contains 4.1.307r > > Reading depmod docs I see that currently I have (default) configuration: > > /etc/depmod.d/dist.conf > search updates extra built-in weak-updates > > Is it correct to say that this mean that if the HP rpm binary I built > installs be2net.ko in extra, I'm ok without doing anything? Correct. We use precisely this same module at work (compiled from source for each kernel version we use), and installing the RPM means it 'just works'. > And that if I want to test the two ones and sometimes to revert to old > driver loading without removing the HP one, I can then add when I need it > the line: > > override be2net * built-in > ? We've never tried this, largely because we've found that the HP module works better than the RedHat-supplied module (largely surrounding firmware updates). In theory, I think this would do what you want. Note that we've found some issues in the past with running a module built for a different (read: older) kernel version, where, IIRC, the kernel will prefer the RedHat-supplied driver. To work around any wonkiness, we simply custom-compile the module for every kernel, and drop it into our internal yum repository. From rhelv6-list at redhat.com Fri Jan 25 16:05:49 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Fri, 25 Jan 2013 11:05:49 -0500 (EST) Subject: [rhelv6-list] Red Hat Developer Toolset 1.1 Now Available through Developer-focused Subscriptions In-Reply-To: <1110687.199.1359128062168.JavaMail.gcase@localhost.localdomain> Message-ID: <33412827.215.1359129945003.JavaMail.gcase@localhost.localdomain> Today Red Hat announces the general availability of version 1.1 of Red Hat Developer Toolset through Red Hat Enterprise Linux Developer Subscriptions. For developers, having ready access to the latest, stable development tools is key to taking advantage of open source innovation. Red Hat Developer Toolset 1.1 bridges development agility with production stability by delivering the latest stable versions of essential C and C++ development tools. By employing Red Hat Developer Toolset, organizations can significantly increase developer productivity and improve deployment times. Red Hat Developer Toolset helps to reduce development and deployment time by allowing users to compile once for multiple versions of Red Hat Enterprise Linux and more easily diagnose and debug applications in development. Using Red Hat Developer Toolset, software developers can develop applications that run on multiple versions of Red Hat Enterprise Linux. Applications developed on Red Hat Enterprise Linux 5 can run on both Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Red Hat Developer Toolset 1.1 delivers the following significant enhancements: * Updated GNU Compiler Collection (GCC) 4.7.2, providing a number of fixes and improvements to the compiler and associated runtimes. * Updated GNU Project Debugger (GDB) 7.5, so developers using GCC 4.7 can also use the latest version of GDB to gain visibility into applications while they execute and to identify what occurred during a crash. * SystemTap 1.8, a diagnostic tool that allows developers to gather information about running Linux systems without going through a tedious and disruptive instrument, recompile, install, and reboot sequence. * OProfile 0.9.7, providing Linux developers with a low-overhead profiler for all code running on a system, enabling system-wide performance analysis. * Valgrind 3.8.1, an instrumentation framework for building dynamic analysis tools to detect many memory management and threading bugs, and profile programs in detail. * elfutils 0.154, a collection of utilities for processing compiled objects. * DWZ 0.7 optimizes DWARF debugging information contained in ELF shared libraries and ELF executables by compressing them into smaller debuginfo files. * Fortran in GCC 4.7, providing support for scientific and research communities through the latest version of GCC with Fortran. Red Hat Developer Toolset is available for users who develop applications for Red Hat Enterprise Linux 5 and 6 through a variety of developer-focused subscriptions. Please see the release notes for support of specific minor releases. The version of the tools included in Red Hat Developer Toolset is an alternative to the version bundled in Red Hat Enterprise Linux releases. Developers can choose to use older versions of the tools provided with Red Hat Enterprise Linux or the versions provided with the Red Hat Developer Toolset. You can obtain Red Hat Developer Toolset by subscribing to one of the following offerings: * Red Hat Enterprise Linux Developer Suite * Red Hat Enterprise Linux Developer Support Subscriptions * Red Hat Enterprise Linux Developer Workstation * NFR subscriptions for qualifying Partners Sign up for a Red Hat Enterprise Linux Developer Workstation 30-day evaluation at the following link to try Red Hat Developer Toolset today: https://www.redhat.com/wapps/eval/index.html?evaluation_id=1023 To learn more about Red Hat developer offerings, visit: http://developer.redhat.com/rhel DOCUMENTATION To access documentation for Red Hat Developer Toolset (requires login), visit: Red Hat Developer Toolset documentation: https://access.redhat.com/knowledge/docs/Red_Hat_Developer_Toolset/ Documentation for Red Hat Enterprise Linux: https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/ Red Hat Enterprise Linux Developer Guide: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/index.html Latest Red Hat Developer Toolset release notes: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Developer_Toolset/1/html/1.1_Release_Notes/index.html ADDITIONAL RESOURCES Red Hat Developer Program information: http://www.redhat.com/developers/rhel https://access.redhat.com/products/Red_Hat_Enterprise_Linux/Developer/ Red Hat Developer Blog: http://developerblog.redhat.com/ The Red Hat Enterprise Linux Developer Program online user group: https://access.redhat.com/groups/red-hat-enterprise-linux-developer-program Sincerely, The Red Hat Enterprise Linux Team From rhelv6-list at redhat.com Fri Jan 25 23:43:30 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Fri, 25 Jan 2013 15:43:30 -0800 Subject: [rhelv6-list] Perl-5.6.12 RPM Dependency Message-ID: Hello, I have built an RPM of perl-5.6.12 from source. When I try to install this RPM it throws following dependency issues, # rpm -ivh /home/nirmal/rpmbuild/RPMS/x86_64/perl-5.16.2-1.el6.x86_64.rpm error: Failed dependencies: perl(FCGI) is needed by perl-5.16.2-1.el6.x86_64 perl(Mac::BuildTools) is needed by perl-5.16.2-1.el6.x86_64 perl(Mac::InternetConfig) is needed by perl-5.16.2-1.el6.x86_64 perl(Your::Module::Here) is needed by perl-5.16.2-1.el6.x86_64 perl(unicore::Name) is needed by perl-5.16.2-1.el6.x86_64 I can not find RPMs of these Perl modules anywhere. Is there a way in a .spec file where I can specify not to build these modules or ignore the modules? Let me know if you need my .spec file to review. Thanks, -- Nirmal D Pathak. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Let me help my fellow beings; that is all I seek. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhelv6-list at redhat.com Sat Jan 26 13:09:27 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Sat, 26 Jan 2013 14:09:27 +0100 Subject: [rhelv6-list] Perl-5.6.12 RPM Dependency In-Reply-To: References: Message-ID: On Sat, Jan 26, 2013 at 12:43 AM, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > Hello, > > I have built an RPM of perl-5.6.12 from source. > > When I try to install this RPM it throws following dependency issues, > > # rpm -ivh /home/nirmal/rpmbuild/RPMS/x86_64/perl-5.16.2-1.el6.x86_64.rpm > error: Failed dependencies: > perl(FCGI) is needed by perl-5.16.2-1.el6.x86_64 > perl(Mac::BuildTools) is needed by perl-5.16.2-1.el6.x86_64 > perl(Mac::InternetConfig) is needed by perl-5.16.2-1.el6.x86_64 > perl(Your::Module::Here) is needed by perl-5.16.2-1.el6.x86_64 > perl(unicore::Name) is needed by perl-5.16.2-1.el6.x86_64 > > I can not find RPMs of these Perl modules anywhere. > > Is there a way in a .spec file where I can specify not to build these > modules or ignore the modules? > > Let me know if you need my .spec file to review. > I have not here on hand the official Red Hat public source rpm repo link, but CentOS ones should be the same as of their binary compatibility: For example you can extact from this src.rpm the corresponding .spec file for 6.2 http://vault.centos.org/6.2/os/Source/SPackages/perl-5.10.1-119.el6_1.1.src.rpm 6.3 http://vault.centos.org/6.3/os/Source/SPackages/perl-5.10.1-127.el6.src.rpm Other ones can eventually give you the RHEL links. Gianluca From rhelv6-list at redhat.com Mon Jan 28 21:21:02 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Mon, 28 Jan 2013 13:21:02 -0800 Subject: [rhelv6-list] [Solved] Perl-5.6.12 RPM Dependency Message-ID: On 26 January 2013 05:09, Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list wrote: > On Sat, Jan 26, 2013 at 12:43 AM, Red Hat Enterprise Linux 6 > (Santiago) discussion mailing-list wrote: > > Hello, > > > > I have built an RPM of perl-5.6.12 from source. > > > > When I try to install this RPM it throws following dependency issues, > > > > # rpm -ivh /home/nirmal/rpmbuild/RPMS/x86_64/perl-5.16.2-1.el6.x86_64.rpm > > error: Failed dependencies: > > perl(FCGI) is needed by perl-5.16.2-1.el6.x86_64 > > perl(Mac::BuildTools) is needed by perl-5.16.2-1.el6.x86_64 > > perl(Mac::InternetConfig) is needed by perl-5.16.2-1.el6.x86_64 > > perl(Your::Module::Here) is needed by perl-5.16.2-1.el6.x86_64 > > perl(unicore::Name) is needed by perl-5.16.2-1.el6.x86_64 > > > > I can not find RPMs of these Perl modules anywhere. > > > > Is there a way in a .spec file where I can specify not to build these > > modules or ignore the modules? > > > > Let me know if you need my .spec file to review. > > > > I have not here on hand the official Red Hat public source rpm repo > link, but CentOS ones should be the same as of their binary > compatibility: > For example you can extact from this src.rpm the corresponding .spec file > for > 6.2 > > http://vault.centos.org/6.2/os/Source/SPackages/perl-5.10.1-119.el6_1.1.src.rpm > > 6.3 > http://vault.centos.org/6.3/os/Source/SPackages/perl-5.10.1-127.el6.src.rpm > > Other ones can eventually give you the RHEL links. > Gianluca > Thanks for pointing me to the .spec file. I recreated my .spec file from old perl version which you mentioned. The trick is to use filter-requires.sh script in .spec file to exclude the modules in question. --- #!/bin/sh # The original script name has been passed as the first argument: "$@" | awk ' $0 != "perl(FCGI)" && $0 != "perl(Your::Module::Here)" && $0 != "perl(unicore::Name)" && $0 != "perl(Tk)" && $0 !~ /^perl\(Tk::/ && $0 !~ /^perl\(Mac::/ ' # We used to filter also these: # NDBM perl(v5.6.0) perl(Tie::RangeHash) # but they don't seem to be present anymore. -- Thanks, -- Nirmal D Pathak. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Let me help my fellow beings; that is all I seek. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhelv6-list at redhat.com Mon Jan 28 23:42:03 2013 From: rhelv6-list at redhat.com (Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list) Date: Mon, 28 Jan 2013 17:42:03 -0600 (CST) Subject: [rhelv6-list] Perl-5.6.12 RPM Dependency In-Reply-To: References: Message-ID: > I have built an RPM of perl-5.6.12 from source. > > When I try to install this RPM it throws following dependency issues, > > # rpm -ivh /home/nirmal/rpmbuild/RPMS/x86_64/perl-5.16.2-1.el6.x86_64.rpm > error: Failed dependencies: > perl(FCGI) is needed by perl-5.16.2-1.el6.x86_64 > perl(Mac::BuildTools) is needed by perl-5.16.2-1.el6.x86_64 > perl(Mac::InternetConfig) is needed by perl-5.16.2-1.el6.x86_64 > perl(Your::Module::Here) is needed by perl-5.16.2-1.el6.x86_64 > perl(unicore::Name) is needed by perl-5.16.2-1.el6.x86_64 > > I can not find RPMs of these Perl modules anywhere. This happens because the automatic dependency checker for perl modules detects that one or more modules either "require" or "use" these modules. The issue is that the dependency checker doesn't realize that they're optional. perl is a complicated language to parse ("only perl can parse perl"), so it would be a lot more work to make the dependency checker realize this. When I've run into this issue, I find the modules that are causing the spurious requires and patch them to not have the require/use statements. For example, my spec for perl 5.16.1 has this in the %pre section, after the %setup: # # white-out some dependencies we don't want to acquire. # cd cpan/CPAN/lib chmod u+w CPAN.pm cp CPAN.pm CPAN.pm.orig sed -e 's/^require Mac::BuildTools /#require Mac::BuildTools /' \ < CPAN.pm.orig > CPAN.pm rm -f CPAN.pm.orig cd ../../.. cd cpan/libnet/Net chmod u+w Config.pm cp Config.pm Config.pm.orig sed -e 's/^use Mac::InternetConfig/#use Mac::InternetConfig/' \ < Config.pm.orig > Config.pm rm -f Config.pm.orig cd ../../.. cd cpan/CPANPLUS/lib/CPANPLUS/Internals/Constants chmod u+w Report.pm cp Report.pm Report.pm.orig sed -e 's/^use Your::Module::Here/#use Your::Module::Here/' \ < Report.pm.orig > Report.pm rm -f Report.pm.orig cd ../../../../../.. Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164