<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>centos Archives - Tech Antidote</title>
	<atom:link href="https://techantidote.com/tag/centos/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>‎ &#124; LINUX &#124; Tech &#124; Security &#124;</description>
	<lastBuildDate>Sun, 25 Jun 2017 17:13:47 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://techantidote.com/wp-content/uploads/2016/02/cropped-google-plus-profile-picture-32x32.png</url>
	<title>centos Archives - Tech Antidote</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">106369530</site>	<item>
		<title>How to check if a partition is primary in CentOS+Screenshots</title>
		<link>https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/</link>
					<comments>https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sun, 25 Jun 2017 17:13:47 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[check partition type]]></category>
		<category><![CDATA[extended]]></category>
		<category><![CDATA[fdisk]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[parted]]></category>
		<category><![CDATA[primary]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=1922</guid>

					<description><![CDATA[<p>This is a guide on how to check if a partition is primary in centos or not? Use the following command: # parted /dev/sda print Alternative: # cfdisk /dev/sda As shown above, the field under &#8220;Part Type&#8221; would suggest if that partition is Primary/Secondary. To exit out of the cfdisk menu, use your arrow keys &#8230; <a href="https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/" class="more-link">Continue reading <span class="screen-reader-text">How to check if a partition is primary in CentOS+Screenshots</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/">How to check if a partition is primary in CentOS+Screenshots</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This is a guide on how to check if a partition is primary in centos or not? Use the following command:</p>
<pre><strong># parted /dev/sda print</strong></pre>
<p><img fetchpriority="high" decoding="async" class="alignnone wp-image-2244 size-full" src="http://techantidote.com/wp-content/uploads/2016/06/2-1.png" alt="parted /dev/sda print centos" width="660" height="245" srcset="https://techantidote.com/wp-content/uploads/2016/06/2-1.png 660w, https://techantidote.com/wp-content/uploads/2016/06/2-1-300x111.png 300w" sizes="(max-width: 660px) 100vw, 660px" /></p>
<p><span style="color: #0000ff;"><strong>Alternative</strong>:</span></p>
<pre><strong># cfdisk /dev/sda
</strong></pre>
<p><img decoding="async" class="alignnone wp-image-2245 size-full" src="http://techantidote.com/wp-content/uploads/2016/06/cfdisk.png" alt="centos cfdisk sample output" width="721" height="396" srcset="https://techantidote.com/wp-content/uploads/2016/06/cfdisk.png 721w, https://techantidote.com/wp-content/uploads/2016/06/cfdisk-300x165.png 300w" sizes="(max-width: 721px) 100vw, 721px" /></p>
<p>As shown above, the field under &#8220;Part Type&#8221; would suggest if that partition is Primary/Secondary.</p>
<p>To exit out of the cfdisk menu, use your arrow keys and move the selection to &#8220;<strong>Quit</strong>&#8221; and hit <strong>Enter</strong> in your keyboard.</p>
<p>Source: <a href="http://askubuntu.com/questions/689742/when-using-fdisk-how-do-i-find-what-partition-numbers-are-already-in-use" target="_blank" rel="noopener">Link</a></p>
<p><strong>As always stay Happy!</strong> Happy Blogging! <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p><strong>ΞXΤЯ3МΞ</strong></p>
<p>The post <a href="https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/">How to check if a partition is primary in CentOS+Screenshots</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/how-to-check-if-a-partition-is-primary-in-centos/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1922</post-id>	</item>
		<item>
		<title>Make CentOS virtual machine in VirtualBox use the host&#8217;s VPN Connection</title>
		<link>https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/</link>
					<comments>https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sun, 06 Nov 2016 18:18:28 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[virtualbox]]></category>
		<category><![CDATA[vpn]]></category>
		<category><![CDATA[windows 10]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=2290</guid>

					<description><![CDATA[<p>If your host PC (in my case Windows 10) is connected to a VPN but your CentOS 6.x VM is not using the VPN, then do the following: 1: Power off your CentOS VM. 2: Right click your centos machine in virtualbox and then click &#8220;Settings&#8220;. 3: Click &#8220;Network&#8221; and change the Adapter Settings to &#8220;NAT&#8220;. &#8230; <a href="https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/" class="more-link">Continue reading <span class="screen-reader-text">Make CentOS virtual machine in VirtualBox use the host&#8217;s VPN Connection</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/">Make CentOS virtual machine in VirtualBox use the host&#8217;s VPN Connection</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>If your host PC (in my case Windows 10) is connected to a VPN but your CentOS 6.x VM is not using the VPN, then do the following:</p>
<p><strong>1</strong>: Power off your CentOS VM.</p>
<p><strong>2</strong>: Right click your centos machine in virtualbox and then click &#8220;<strong>Settings</strong>&#8220;.</p>
<p><img decoding="async" class="alignnone wp-image-2325 size-full" src="http://techantidote.com/wp-content/uploads/2016/11/select-settings.png" alt="right click your centos virtual machine and click settings (Screenshot)" width="421" height="222" srcset="https://techantidote.com/wp-content/uploads/2016/11/select-settings.png 421w, https://techantidote.com/wp-content/uploads/2016/11/select-settings-300x158.png 300w" sizes="(max-width: 421px) 100vw, 421px" /></p>
<p><strong>3</strong>: Click &#8220;<strong>Network</strong>&#8221; and change the Adapter Settings to &#8220;<strong>NAT</strong>&#8220;.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2324" src="http://techantidote.com/wp-content/uploads/2016/11/change-settings-to-NAT.png" alt="change virtualbox network settings to NAT (Screenshot)" width="551" height="364" srcset="https://techantidote.com/wp-content/uploads/2016/11/change-settings-to-NAT.png 651w, https://techantidote.com/wp-content/uploads/2016/11/change-settings-to-NAT-300x198.png 300w" sizes="auto, (max-width: 551px) 100vw, 551px" /></p>
<p><strong>4</strong>: Now power on your centos virtual machine.</p>
<p><strong>5</strong>: Once your VM boots up, login and then restart the network service. You can use the following CLI command &#8220;<strong>service network restart</strong>&#8220;.</p>
<p>Your CentOS virtual machine should now to able to use the VPN connection and use it accordingly. Do verify the same in your virtual machine. Hope this helps!</p>
<p>Do like and subscribe if this guide helped you. Cheers!</p>
<p>The post <a href="https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/">Make CentOS virtual machine in VirtualBox use the host&#8217;s VPN Connection</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/make-centos-virtual-machine-in-virtualbox-use-the-hosts-vpn-connection/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2290</post-id>	</item>
		<item>
		<title>Protect against vulnerability CVE-2016-5696 in CentOS 6.8</title>
		<link>https://techantidote.com/cve-2016-5696-centos-6-8-fix/</link>
					<comments>https://techantidote.com/cve-2016-5696-centos-6-8-fix/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sat, 24 Sep 2016 03:30:33 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[6.8]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[CVE-2016-5696]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[net.ipv4.tcp_challenge_ack_limit]]></category>
		<category><![CDATA[offpath tcp]]></category>
		<category><![CDATA[sysctl.conf]]></category>
		<category><![CDATA[vulnerability]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=2295</guid>

					<description><![CDATA[<p>This guide on how to protect against Off-path TCP vulnerability CVE-2016-5696 in a CentOS 6.8 machine. Run the following command to check the kernel version that your box is running: uname -r Run the following to verify your Centos version details: cat /etc/redhat-release Below is a screenshot for the outputs for the above commands from my CentOS &#8230; <a href="https://techantidote.com/cve-2016-5696-centos-6-8-fix/" class="more-link">Continue reading <span class="screen-reader-text">Protect against vulnerability CVE-2016-5696 in CentOS 6.8</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/cve-2016-5696-centos-6-8-fix/">Protect against vulnerability CVE-2016-5696 in CentOS 6.8</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This guide on how to protect against Off-path TCP vulnerability CVE-2016-5696 in a CentOS 6.8 machine.</p>
<p>Run the following command to check the kernel version that your box is running:</p>
<pre><strong>uname -r</strong></pre>
<p>Run the following to verify your Centos version details:</p>
<pre><strong>cat /etc/redhat-release</strong></pre>
<p>Below is a screenshot for the outputs for the above commands from my CentOS 6.8 box.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2296 size-full" src="http://techantidote.com/wp-content/uploads/2016/09/release-info.png" alt="release information screenshot CentOS 6.8" width="658" height="173" srcset="https://techantidote.com/wp-content/uploads/2016/09/release-info.png 658w, https://techantidote.com/wp-content/uploads/2016/09/release-info-300x79.png 300w" sizes="auto, (max-width: 658px) 100vw, 658px" /></p>
<h4><strong><span style="color: #0000ff;">Workaround against the attack:</span></strong></h4>
<p>Open your sysctl.conf file:</p>
<pre><strong>vi /etc/sysctl.conf</strong></pre>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2297 size-full" src="http://techantidote.com/wp-content/uploads/2016/09/edit-sysctl-conf.png" alt="edit config file command CentOS 6.8" width="543" height="67" srcset="https://techantidote.com/wp-content/uploads/2016/09/edit-sysctl-conf.png 543w, https://techantidote.com/wp-content/uploads/2016/09/edit-sysctl-conf-300x37.png 300w" sizes="auto, (max-width: 543px) 100vw, 543px" /></p>
<p>Below is a screenshot of my default sysctl.conf file which does not contain &#8220;net.ipv4.tcp_challenge_ack_limit&#8221;.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2298 size-full" src="http://techantidote.com/wp-content/uploads/2016/09/default-config-file.png" alt="default sysctl.conf in CentOS 6.8" width="774" height="851" srcset="https://techantidote.com/wp-content/uploads/2016/09/default-config-file.png 774w, https://techantidote.com/wp-content/uploads/2016/09/default-config-file-273x300.png 273w, https://techantidote.com/wp-content/uploads/2016/09/default-config-file-768x844.png 768w" sizes="auto, (max-width: 774px) 100vw, 774px" /></p>
<p>Now add the following line at the end of the config file:</p>
<pre><strong>net.ipv4.tcp_challenge_ack_limit = 999999999</strong></pre>
<p>Below is a screenshot after editing the config file.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2299 size-full" src="http://techantidote.com/wp-content/uploads/2016/09/edited-config-file.png" alt="edited-config-file screenshot in CentOS 6.8" width="731" height="822" srcset="https://techantidote.com/wp-content/uploads/2016/09/edited-config-file.png 731w, https://techantidote.com/wp-content/uploads/2016/09/edited-config-file-267x300.png 267w" sizes="auto, (max-width: 731px) 100vw, 731px" /></p>
<p>Save and exit the file. (Press ESC and then type :wq and hit Enter in your keyboard).</p>
<p>Use the command below to verify if the value of net.ipv4.tcp_challenge_ack_limit is 999999999.</p>
<pre><strong>sysctl -p</strong></pre>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-2300 size-full" src="http://techantidote.com/wp-content/uploads/2016/09/sysctl-p.png" alt="sysctl -p in CentOS 6.8" width="515" height="277" srcset="https://techantidote.com/wp-content/uploads/2016/09/sysctl-p.png 515w, https://techantidote.com/wp-content/uploads/2016/09/sysctl-p-300x161.png 300w" sizes="auto, (max-width: 515px) 100vw, 515px" /></p>
<p>If you are able to see the line in the above screenshot, this means that it will make the exploit extremely hard to perform (practically impossible). The above is a workaround to mitigating the Off-Path TCP attack in a CentOS 6.8 machine and will also work for redhat 6.8.</p>
<h4><span style="color: #0000ff;"><strong>The Fix:</strong></span></h4>
<p>If you are not looking for the workaround but for a permanent fix, then you can upgrade your Linux kernel to 4.6 or above.</p>
<p>If this article helped you, do leave a comment below and like us on <a href="http://twitter.com/techantidote">Twitter</a> and <a href="http://facebook.com/techantidote">Facebook</a>. Cheers!</p>
<p><strong>Source</strong>: <a href="https://bobcares.com/blog/fix-linux-off-path-tcp-attacks-cve-2016-5696/2/">Bobcares</a></p>
<p><strong>References</strong>: <a href="https://access.redhat.com/security/cve/cve-2016-5696" target="_blank">Redhat Portal</a>, <a href="https://access.redhat.com/security/vulnerabilities/challengeack" target="_blank">Redhat Shared Ack Vulnerability</a></p>
<p>The post <a href="https://techantidote.com/cve-2016-5696-centos-6-8-fix/">Protect against vulnerability CVE-2016-5696 in CentOS 6.8</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/cve-2016-5696-centos-6-8-fix/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2295</post-id>	</item>
		<item>
		<title>Useful Linux Terminal shortcuts</title>
		<link>https://techantidote.com/linux-terminal-shortcuts/</link>
					<comments>https://techantidote.com/linux-terminal-shortcuts/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Sat, 28 May 2016 12:12:56 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[linux terminal]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[shortcuts]]></category>
		<category><![CDATA[sysadmin]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=1942</guid>

					<description><![CDATA[<p>Here are some useful Linux Terminal Shortcuts: Shortcut 1: Run previous typed command In your Linux terminal, type: # ls -l Now, if you want to run this command again i.e the (previous command), type the following and hit ENTER: # !! This will run the command which was previously typed i.e &#8216;ls -l&#8217;. Shortcut 2: Run command with last &#8230; <a href="https://techantidote.com/linux-terminal-shortcuts/" class="more-link">Continue reading <span class="screen-reader-text">Useful Linux Terminal shortcuts</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/linux-terminal-shortcuts/">Useful Linux Terminal shortcuts</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Here are some useful Linux Terminal Shortcuts:</p>
<p><span style="color: #3366ff;"><strong>Shortcut 1:</strong> <strong>Run previous typed command</strong></span></p>
<p>In your Linux terminal, type:</p>
<pre><strong># ls -l</strong></pre>
<p>Now, if you want to run this command again i.e the (previous command), type the following and hit ENTER:</p>
<pre><strong># !!</strong></pre>
<p>This will run the command which was previously typed i.e &#8216;<strong>ls -l&#8217;</strong>.</p>
<p><span style="color: #3366ff;"><strong>Shortcut 2: Run command with last argument from previous command</strong></span></p>
<p>For this example, lets create an empty file one.txt:</p>
<pre><strong># touch one.txt</strong></pre>
<p>Now, lets use the following command:</p>
<pre><strong># cp one.txt one.bak</strong></pre>
<p>Lets break down this command according to its arguments:</p>
<p>1st argument &#8211; <strong>one.txt</strong></p>
<p>2nd argument / last argument &#8211; <strong>one.bak</strong></p>
<p>[ <strong>Note</strong>: We can logically say that the 0th argument is the command <strong>cp</strong> itself. ]</p>
<p>Lets say we want to edit the file &#8220;<strong>one.bak</strong>&#8221; (which is the last argument for command <strong>cp</strong>, we can use:</p>
<pre><strong># vi !$</strong></pre>
<p>The above command is same as running &#8216;<strong>vi one.back</strong>&#8216;. Also note that the !<strong>$</strong> passes the <strong>last argument of the previous command</strong> to the current command vi.</p>
<p><span style="color: #3366ff;"><strong>Shortcut 2 (Alternative)</strong></span>:</p>
<p>Now, lets use the following command:</p>
<pre><strong># cp one.txt one.bak</strong></pre>
<p>An alternative way to provide an argument from the previous command to another command is by using !:&lt;argument number&gt;. For example, to pass the 2nd argument of the last command, we use <strong>!:2 </strong>as follows:</p>
<pre><strong># vi !:2</strong></pre>
<p>Here <strong>!:2</strong> means that we are passing the 2nd argument of the previous command.</p>
<p><span style="color: #3366ff;"><strong>Shortcut 3 : Linux Terminal Keyboard shortcuts</strong></span></p>
<p>To get the previous command: Press the <strong>UP</strong> arrow in the keyboard.</p>
<p>To kill a process when you are in the Linux terminal: Press &lt;<strong>CTRL&gt;</strong> + <strong>C </strong>in your keyboard.</p>
<p><span style="color: #3366ff;"><strong>Shortcut 4 : Autocomplete:</strong></span></p>
<p>Trust me when I say this, this shortcut makes your life easier. If you need to auto complete a command, you can use the <strong>TAB</strong> key in your keyboard. This is one the shortcuts that is used by most Linux users.</p>
<p><strong>Example:</strong></p>
<p>If you want to type <strong>ifconfig</strong> in your Linux terminal, you can start typing the command and then press the TAB key to auto complete it. In this case, type <strong>ifcf</strong> and then press <strong>TAB </strong>and it will autocomplete the command.</p>
<p>The TAB feature can also be used to autocomplete known information such as file names which are passed as arguments.</p>
<p>For example: Lets assume in the current directory that you are on has only two files <strong>first.txt</strong> and <strong>second.txt. </strong>Now, if you need to type this command &#8216;<strong>cat first.txt second.txt</strong>&#8216;, then you can use the <strong>TAB</strong> shortcut to auto-complete it by following these steps:</p>
<p>Type <strong>cat</strong> and then type <strong>f </strong>and then<strong> press TAB </strong>to autocomplete it to:</p>
<pre><strong> cat first.txt</strong></pre>
<p>Then type the first letter of the next argument i.e. type <strong>s </strong>and then press<strong> TAB, </strong>which it autocomplete the command to<strong>:</strong></p>
<pre><strong>cat first.txt second.txt
</strong></pre>
<p><span style="color: #3366ff;"><strong>Shortcut 5: Move between words</strong></span></p>
<ul>
<li><span style="color: #3366ff;"><strong>Navigate to the next word from current position:</strong></span></li>
</ul>
<p>Press <strong>&lt;CTRL&gt;</strong> and <strong>&lt;Right Arrow key&gt;</strong> in your keyword to move to the next word(towards the right side of current cursor position) in your terminal. This is also applicable in Linux editors such as <strong>vi</strong> or <strong>vim</strong>.</p>
<ul>
<li><span style="color: #3366ff;"><strong>Move to previous word in terminal from current position:</strong></span></li>
</ul>
<p>Press <strong>&lt;CTRL&gt;</strong> and <strong>&lt;Left Arrow key&gt;</strong> in your keyword to move to the previous word/the word to the left side from current cursor position in your Linux terminal (or most editors). You can press it again accordingly, if you need to move the cursor one word at a time towards the left direction.</p>
<p>The above two shortcuts are useful when you are entering commands in the Linux terminal and need to correct a particular word in the command. This helps navigating back and forth between words/parameters in the command with ease.</p>
<p><span style="color: #3366ff;"><strong>Other Bash Shortcuts:</strong></span></p>
<p>To go to the 1st terminal, press <strong>CTRL</strong>, <strong>ALT</strong> and the function key <strong>F1</strong> in your keyboard.</p>
<p>To go the nth terminal, press <strong>CTRL</strong>, <strong>ALT</strong> and <strong>Fn</strong> (where Fn can be function keys F1, F2, F3 etc).</p>
<p>To<strong> paste </strong>previously copied text to your Linux terminal/editor, you can press the <strong>middle button</strong> in your <strong>mouse</strong>. Now, How cool is that uh? <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>To lock your Linux machine press <strong>&lt;CTRL&gt; &lt;ALT&gt;</strong> and the letter <strong>l</strong> in your keyboard.</p>
<p>And that&#8217;s it for now, hope its been informative. I will be updating this article in the future with more Linux terminal shortcuts  as soon as I find new ones, so stay tuned! If this article helped you, do leave a comment below and like us on <a href="http://twitter.com/techantidote">Twitter</a> and <a href="http://facebook.com/techantidote">Facebook</a>. <span style="color: #3366ff;"><strong>Cheers!</strong></span></p>
<p>Hope this helps!</p>
<p>The post <a href="https://techantidote.com/linux-terminal-shortcuts/">Useful Linux Terminal shortcuts</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/linux-terminal-shortcuts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1942</post-id>	</item>
		<item>
		<title>Double quotes not working in Linux terminal &#8211; [Solution]</title>
		<link>https://techantidote.com/double-quotes-not-working-in-linux-terminal/</link>
					<comments>https://techantidote.com/double-quotes-not-working-in-linux-terminal/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Thu, 17 Mar 2016 22:25:25 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[double]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[not displayed]]></category>
		<category><![CDATA[quotes does not work in Linux]]></category>
		<category><![CDATA[setxkbmap]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[terminal]]></category>
		<category><![CDATA[tilde]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[virtualbox]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=1924</guid>

					<description><![CDATA[<p>I encountered an issue in my CentOS VM where whenever I type the &#8216; (single quote) or the &#8220; (double quotes) in the terminal, they don&#8217;t get displayed. I did the following to fix the issue: In your terminal window, type the following: # setxkbmap -layout us You should now be able to use single, double quotes or tilde symbols in &#8230; <a href="https://techantidote.com/double-quotes-not-working-in-linux-terminal/" class="more-link">Continue reading <span class="screen-reader-text">Double quotes not working in Linux terminal &#8211; [Solution]</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/double-quotes-not-working-in-linux-terminal/">Double quotes not working in Linux terminal &#8211; [Solution]</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>I encountered an issue in my CentOS VM where whenever I type the <strong>&#8216;</strong> (single quote) or the <strong>&#8220;</strong> (double quotes) in the terminal,<strong> </strong>they don&#8217;t get displayed. I did the following to fix the issue:</p>
<p>In your terminal window, type the following:</p>
<blockquote><p># setxkbmap -layout us</p></blockquote>
<p>You should now be able to use <strong>single</strong>, <strong>double</strong> quotes or <strong>tilde</strong> <strong>symbols</strong> in your terminal.</p>
<p>The above command simply <span style="color: #3366ff;"><strong>changes</strong> the <strong>keyboard layout</strong> to <strong>English (US)</strong></span> and this is under the assumption that you are actually using a <strong>English (US) </strong>keyboard in your PC.</p>
<p>[<strong>Note</strong>: English (US) layout is different from English (US) International keyboard layout].</p>
<p>You can check the screenshot below for reference.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-1925 size-full" title="setxkbmap -layout us - ISSUE FIXED" src="http://techantidote.com/wp-content/uploads/2016/03/1.png" alt="setxkbmap -layout us" width="660" height="152" srcset="https://techantidote.com/wp-content/uploads/2016/03/1.png 660w, https://techantidote.com/wp-content/uploads/2016/03/1-300x69.png 300w" sizes="auto, (max-width: 660px) 100vw, 660px" /></p>
<p><span style="line-height: 1.6;">Thanks and credits to </span><a style="line-height: 1.6;" href="http://askubuntu.com/questions/69306/tilde-and-double-quote-keys-dont-work-on-the-command-line" target="_blank">this post</a><span style="line-height: 1.6;"> that helped me resolve this issue.</span></p>
<p>Feel free to leave a comment in the comments section down below. <span style="color: #3366ff;"><strong>Happy troubleshooting!</strong> <strong>Cheers!</strong></span></p>
<p>The post <a href="https://techantidote.com/double-quotes-not-working-in-linux-terminal/">Double quotes not working in Linux terminal &#8211; [Solution]</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/double-quotes-not-working-in-linux-terminal/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1924</post-id>	</item>
		<item>
		<title>How To fix “This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in RHEL 7.” when booting from VirtualBox</title>
		<link>https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/</link>
					<comments>https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/#comments</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Wed, 03 Feb 2016 21:11:41 +0000</pubDate>
				<category><![CDATA[Linux / Redhat]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[centos 7]]></category>
		<category><![CDATA[i686 cpu]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[rhel 7]]></category>
		<category><![CDATA[this kernel requires an x86-64 CPU]]></category>
		<category><![CDATA[unsupported]]></category>
		<category><![CDATA[virtual box]]></category>
		<category><![CDATA[virtualbox]]></category>
		<category><![CDATA[virtualization]]></category>
		<guid isPermaLink="false">http://techantidote.com/?p=23</guid>

					<description><![CDATA[<p>Error: This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in RHEL 7.  [Note: This tutorial is under the assumption that your physical CPU is 64-bit and your installed host OS is 64-bit and will only work in these circumstances.] Cause: This mainly happens due two reasons: If you have &#8230; <a href="https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/" class="more-link">Continue reading <span class="screen-reader-text">How To fix “This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in RHEL 7.” when booting from VirtualBox</span> <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/">How To fix “This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in RHEL 7.” when booting from VirtualBox</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong><span style="color: #ff0000;">Error:</span></strong> <strong>This kernel requires an x86-64 CPU, but only detected an i686 CPU.</strong><br />
<strong>This processor is unsupported in RHEL 7. </strong></p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-24 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/centos-boot-error.png" alt="centos-boot-error" width="711" height="75" srcset="https://techantidote.com/wp-content/uploads/2016/02/centos-boot-error.png 711w, https://techantidote.com/wp-content/uploads/2016/02/centos-boot-error-300x32.png 300w, https://techantidote.com/wp-content/uploads/2016/02/centos-boot-error-250x26.png 250w, https://techantidote.com/wp-content/uploads/2016/02/centos-boot-error-150x16.png 150w" sizes="auto, (max-width: 711px) 100vw, 711px" /></p>
<p>[<strong>Note</strong>: This tutorial is under the assumption that your physical CPU is 64-bit and your installed host OS is 64-bit and will only work in these circumstances.]</p>
<p><span style="color: #ff0000;"><strong><span style="color: #0000ff;">Cause:</span></strong></span></p>
<p>This mainly happens due two reasons:</p>
<ol>
<li>If you have a <strong>64-bit</strong> OS installed but the VirtualBox OS <strong>type </strong>is accidentally changed/set to <strong>32-bit</strong> after installation.</li>
<li>If <strong>Vt-X</strong> (Virtualization) is <strong>disabled</strong> in the BIOS. (This can happen if you reset your BIOS to default settings which may have disabled Vt-X  bit).</li>
</ol>
<p><span style="color: #0000ff;"><strong><span style="color: #3366ff;">Solution</span>:</strong></span></p>
<p><span style="color: #0000ff;"><strong>Step 1:</strong> <span style="color: #000000;">Right Click on the Centos/RHEL OS which is giving you the error and then click on “<strong>Settings</strong>“.</span></span></p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-25 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/1-settings.png" alt="virtualbox settings" width="1280" height="1024" srcset="https://techantidote.com/wp-content/uploads/2016/02/1-settings.png 1280w, https://techantidote.com/wp-content/uploads/2016/02/1-settings-300x240.png 300w, https://techantidote.com/wp-content/uploads/2016/02/1-settings-768x614.png 768w, https://techantidote.com/wp-content/uploads/2016/02/1-settings-1024x819.png 1024w, https://techantidote.com/wp-content/uploads/2016/02/1-settings-188x150.png 188w, https://techantidote.com/wp-content/uploads/2016/02/1-settings-150x120.png 150w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p><strong><span style="color: #3366ff;">Step 2</span>: </strong>In <strong>General</strong> Tab, check the OS Type and see if you are able to<strong> change to “Redhat 64-bit” </strong>and<strong> follow step 4</strong>.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-26 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/2-os-type1.png" alt="change os type" width="1280" height="1024" srcset="https://techantidote.com/wp-content/uploads/2016/02/2-os-type1.png 1280w, https://techantidote.com/wp-content/uploads/2016/02/2-os-type1-300x240.png 300w, https://techantidote.com/wp-content/uploads/2016/02/2-os-type1-768x614.png 768w, https://techantidote.com/wp-content/uploads/2016/02/2-os-type1-1024x819.png 1024w, https://techantidote.com/wp-content/uploads/2016/02/2-os-type1-188x150.png 188w, https://techantidote.com/wp-content/uploads/2016/02/2-os-type1-150x120.png 150w" sizes="auto, (max-width: 1280px) 100vw, 1280px" /></p>
<p><strong><span style="color: #3366ff;">Step 3</span>: </strong>If you are only able to see 32-bit entries in the OS type list and your physical CPU supports 64-bit, this means that <strong>Vt-X</strong> is disabled in your <strong>BIOS</strong>. So, restart your PC and boot into your BIOS, enable <strong>Vt-X</strong>.</p>
<p>For reference, I have a Asus Maximus VII Ranger Motherboard and here is how I enabled<strong> Vt-X</strong> in my BIOS.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-27 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/enable-vtx.jpg" alt="enable vt-x" width="614" height="360" srcset="https://techantidote.com/wp-content/uploads/2016/02/enable-vtx.jpg 614w, https://techantidote.com/wp-content/uploads/2016/02/enable-vtx-300x176.jpg 300w, https://techantidote.com/wp-content/uploads/2016/02/enable-vtx-250x147.jpg 250w, https://techantidote.com/wp-content/uploads/2016/02/enable-vtx-150x88.jpg 150w" sizes="auto, (max-width: 614px) 100vw, 614px" /></p>
<p>[<span style="color: #ff0000;"><strong>Optional</strong></span>: If your CPU supports <strong>Vt-d</strong>, enable that too, it will improve functionality and performance of your Virtual Machine. Some CPUs will not have the Vt-d function, if you dont have it then you can ignore it]</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-28 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd.jpg" alt="optional step to enabled vt-d" width="4151" height="2777" srcset="https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd.jpg 4151w, https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd-300x201.jpg 300w, https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd-768x514.jpg 768w, https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd-1024x685.jpg 1024w, https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd-224x150.jpg 224w, https://techantidote.com/wp-content/uploads/2016/02/optional-enable-vtd-150x100.jpg 150w" sizes="auto, (max-width: 4151px) 100vw, 4151px" /></p>
<p><strong><span style="color: #0000ff;">Step 4</span>: </strong>Restart your computer and boot back your CentOS/RHEL VM and it should come right up.</p>
<p><img loading="lazy" decoding="async" class="alignnone wp-image-29 size-full" src="http://techantidote.com/wp-content/uploads/2016/02/issue-fixed.png" alt="centos boot error fixed" width="707" height="107" srcset="https://techantidote.com/wp-content/uploads/2016/02/issue-fixed.png 707w, https://techantidote.com/wp-content/uploads/2016/02/issue-fixed-300x45.png 300w, https://techantidote.com/wp-content/uploads/2016/02/issue-fixed-250x38.png 250w, https://techantidote.com/wp-content/uploads/2016/02/issue-fixed-150x23.png 150w" sizes="auto, (max-width: 707px) 100vw, 707px" /></p>
<p><strong>Hope this fixed the issue. If this tutorial helped you,do  leave a thumbs up a comment below. Hope this helps! <span class="wp-smiley wp-emoji wp-emoji-smile" title=":)"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span></strong></p>
<p>If you have any sort of queries,  just leave a comment below and will get back to you. Don’t forget to follow my blog to get future updates! <span class="wp-smiley wp-emoji wp-emoji-bigsmile" title=":D"><span class="wp-smiley wp-emoji wp-emoji-bigsmile" title=":D"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span></span></p>
<p>Regards,<br />
<strong>ΞXΤЯ3МΞ</strong></p>
<p>The post <a href="https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/">How To fix “This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in RHEL 7.” when booting from VirtualBox</a> appeared first on <a href="https://techantidote.com">Tech Antidote</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://techantidote.com/how-to-fix-this-kernel-requires-an-x86-64-cpu-but-only-detected-an-i686-cpu-this-processor-is-unsupported-in-rhel-7-when-booting-from-virtualbox/feed/</wfw:commentRss>
			<slash:comments>11</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">23</post-id>	</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 
Minified using Disk

Served from: techantidote.com @ 2026-11-18 00:24:19 by W3 Total Cache
-->