<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Redhat on Salman's Blog</title><link>https://salmanfs.ca/tags/redhat/</link><description>Recent content in Redhat on Salman's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Jan 2020 07:47:28 +0000</lastBuildDate><atom:link href="https://salmanfs.ca/tags/redhat/index.xml" rel="self" type="application/rss+xml"/><item><title>RPM Packaging for JMC</title><link>https://salmanfs.ca/posts/rpm-packaging-for-jmc/</link><pubDate>Thu, 02 Jan 2020 07:47:28 +0000</pubDate><guid>https://salmanfs.ca/posts/rpm-packaging-for-jmc/</guid><description>&lt;p&gt;When JDK Mission Control (JMC) was open-sourced, one of the main tasks for our team at Red Hat was to make it widely available to our developer community.
This meant packaging the application for Fedora.&lt;/p&gt;
&lt;p&gt;Fedora is a distribution of Linux sponsored by Red Hat.
It is the bleeding edge of free software and the upstream source of Red Hat&amp;rsquo;s flagship Enterprise Linux distribution, RHEL.&lt;/p&gt;
&lt;p&gt;I was tasked with packaging an RPM for JMC.
This allowed me to take a deep dive into Maven, Eclipse RCP and RPM build tools.&lt;/p&gt;</description></item><item><title>JDK Mission Control</title><link>https://salmanfs.ca/posts/jdk-mission-control/</link><pubDate>Thu, 02 Jan 2020 07:42:10 +0000</pubDate><guid>https://salmanfs.ca/posts/jdk-mission-control/</guid><description>&lt;p&gt;This was the project my team was working on during my coop at Red Hat in Toronto.
Formerly Java Mission Control, the tool was a proprietary offering in Oracle&amp;rsquo;s Java subscription.
It was open-sourced by Oracle in early 2018 (just before the start of my internship) as JDK Mission Control (JMC).
It is now a project under the OpenJDK umbrella.&lt;/p&gt;
&lt;p&gt;There was previously a similar open-source tool developed by the OpenJDK team at Red Hat called Thermostat.
Red Hat decided to focus their efforts on improving JMC rather than working on Thermostat since JMC was already the de facto industry standard.&lt;/p&gt;</description></item><item><title>Coop @ Red Hat (and IBM?)</title><link>https://salmanfs.ca/posts/coop-red-hat-and-ibm/</link><pubDate>Wed, 17 Jul 2019 21:18:57 +0000</pubDate><guid>https://salmanfs.ca/posts/coop-red-hat-and-ibm/</guid><description>&lt;p&gt;I will be completing the fourth and final semester of my coop at Red Hat as a Software Engineering Intern at the end of summer. It has been an exciting opportunity to learn and develop my skills as a software developer in a real-world environment.&lt;/p&gt;
&lt;p&gt;Over these 16 months, I was given the chance to work on a wide variety of challenges. I began with little to no knowledge about programming in Java. The OpenJDK team, which I joined in my second week, was about to begin working on a tool for JVM performance monitoring. The tool, JDK Mission Control (JMC), was open sourced by Oracle in early 2018 so my team was still wrapping up their old project.&lt;/p&gt;</description></item></channel></rss>