![[Valid RSS]](images/valid-rss-rogers.png "Valid RSS")
This is a valid RSS feed.
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
line 33, column 0: (11 occurrences) [help]
<site xmlns="com-wordpress:feed-additions:1">64334160</site> <item>
<content:encoded><![CDATA[
<?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/" xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" > <channel> <title>Bictor Tips</title> <atom:link href="http://www.bictor.com/feed/" rel="self" type="application/rss+xml" /> <link>http://www.bictor.com</link> <description>Your Help In Digital World</description> <lastBuildDate>Sat, 27 Apr 2024 11:23:28 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod> hourly </sy:updatePeriod> <sy:updateFrequency> 1 </sy:updateFrequency> <generator>https://wordpress.org/?v=6.2.5</generator> <image> <url>https://i0.wp.com/www.bictor.com/wp-content/uploads/2018/05/cropped-CompleteLogo_small.jpg?fit=32%2C32</url> <title>Bictor Tips</title> <link>http://www.bictor.com</link> <width>32</width> <height>32</height></image> <site xmlns="com-wordpress:feed-additions:1">64334160</site> <item> <title>Ubuntu Rescue Guide</title> <link>http://www.bictor.com/2024/04/27/ubuntu-rescue-guide/</link> <comments>http://www.bictor.com/2024/04/27/ubuntu-rescue-guide/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sat, 27 Apr 2024 16:53:25 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=485</guid> <description><![CDATA[Common commands useful when debugging in rescue mode Checking login sessions for various server can be done using View the most recent logins If you just want to check the most recent logins, it’s even simpler. Back in the command-line,]]></description> <content:encoded><![CDATA[<p>Common commands useful when debugging in rescue mode</p> <p>Checking login sessions for various server can be done using </p> <pre class="wp-block-code"><code>sudo less /var/log/auth.log</code></pre> <h3 class="wp-block-heading" id="view-the-most-recent-logins">View the most recent logins</h3> <p>If you just want to check the most recent logins, it’s even simpler. Back in the command-line, type <code>last</code> and press Enter.</p> <p>The output will look something like this:</p> <pre class="wp-block-code"><code>root pts/0 12.34.567.89 Fri Jan 8 15:30 still logged inroot pts/0 12.34.567.89 Fri Jan 8 15:13 - 15:29 (00:16)reboot system boot 5.4.0-1009-kvm Fri Jan 8 15:07 still running</code></pre> <p>The <code>last</code> tool pulls its data from <code>/var/log/wtmp</code>, which is written to each time a user logs in. It’ll show username, tty, IP address, date and time, and session start/stop times.</p> <p>If that’s too verbose, you can apply filters to the command with the following syntax:</p> <pre class="wp-block-code"><code>last [OPTIONS] [USER] [<TTY>...]</code></pre> <p>Let’s look at an example. If we wanted to view all of the logins from the root user, we could run:</p> <pre class="wp-block-code"><code>last root</code></pre> <pre class="wp-block-code"><code>OUTPUT:root pts/0 12.345.678.90 Fri Jan 8 15:30 still logged inroot pts/0 12.345.678.90 Fri Jan 8 15:13 - 15:29 (00:16)</code></pre> <h3 class="wp-block-heading" id="see-when-users-last-logged-in">See when users last logged in</h3> <p>If you notice an unauthorized change to the system, it’s often useful to see when each user last logged in. This way, you can determine who made the adjustment. We can do this via the <code>lastlog</code> command, which pulls data from <code>/etc/log/lastlog</code> and sorts them by <code>/etc/password</code> entries:</p> <pre class="wp-block-code"><code>lastlog</code></pre> <pre class="wp-block-code"><code>Username Port From Latestroot pts/0 12.345.678.90 Fri Jan 8 15:30:06 +0000 2021daemon **Never logged in**bin **Never logged in**sys **Never logged in**sync **Never logged in**bitlaunch pts/1 83.253.230.46 Fri Jan 8 16:09:53 +0000 2021hack0r pts/1 83.253.230.46 Fri Jan 8 16:10:20 +0000 2021</code></pre> <p>You’ll notice quite a few users with a <code>**Never logged in**</code> entry in the <code>Latest</code> column. This is normal on account of them being system users.</p> <h2 class="wp-block-heading" id="mounting-the-drives-in-the-rescue-system">Mounting the drive(s) in the Rescue System</h2> <p>First, you should determine the partition identifiers of your system by running the command <code>lsblk</code>.</p> <pre class="wp-block-code"><code>root@rescue ~ # lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTloop0 7:0 0 4G 1 loopsda 8:0 0 447.1G 0 disk├─sda1 8:1 0 4G 0 part├─sda2 8:2 0 512M 0 part└─sda3 8:3 0 442.6G 0 partsdb 8:16 0 447.1G 0 disk└─sdb1 8:17 0 446G 0 part</code></pre> <p>Now you can mount the correct partition within an empty folder, for example, using <code>/mnt</code>.</p> <p><code>mount /dev/md2 /mnt</code></p> <h2 class="wp-block-heading" id="resetting-the-root-password">Resetting the root password</h2> <p>To reset the root password of an installed Linux or BSD system, you need to <code>mount</code> the system partition as explained in the previous section of this article: <em>“Mounting the Drive(s) in the Rescue System”</em>. Then use <code>chroot</code> to switch into the root environment of the mounted system.</p> <pre class="wp-block-code"><code>chroot-prepare /mntchroot /mnt</code></pre> <p>You can now change the password of the user “root”.</p> <pre class="wp-block-code"><code>passwd</code></pre> <p>Finally, exit the root environment.</p> <pre class="wp-block-code"><code>exit</code></pre>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2024/04/27/ubuntu-rescue-guide/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">485</post-id> </item> <item> <title>Ubuntu bug affecting Firefox Chromium and other Keyboard Issues</title> <link>http://www.bictor.com/2023/12/17/ubuntu-bug-affecting-firefox-chromium-and-other-keyboard-issues/</link> <comments>http://www.bictor.com/2023/12/17/ubuntu-bug-affecting-firefox-chromium-and-other-keyboard-issues/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 17 Dec 2023 21:24:39 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">https://www.bictor.com/?p=478</guid> <description><![CDATA[The main problem was AppArmor not giving permission to connect to ibus in the root account Workaround was to change the input method from ibus to none im-config -n none]]></description> <content:encoded><![CDATA[<p>The main problem was AppArmor not giving permission to connect to ibus in the root account</p> <p>Workaround was to change the input method from ibus to none</p> <p><code>im-config -n none</code></p> <p></p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2023/12/17/ubuntu-bug-affecting-firefox-chromium-and-other-keyboard-issues/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">478</post-id> </item> <item> <title>Ubuntu 22.04 LAMP Installation</title> <link>http://www.bictor.com/2023/07/09/ubuntu-22-04-lamp-installation/</link> <comments>http://www.bictor.com/2023/07/09/ubuntu-22-04-lamp-installation/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 09 Jul 2023 16:43:34 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=468</guid> <description><![CDATA[To install the LAMP stack on Ubuntu 22.04 LTS, follow these steps.]]></description> <content:encoded><![CDATA[<p>To install the LAMP stack on Ubuntu 22.04 LTS, follow these steps.</p> <ol><li>Using <code>apt</code>, update the Ubuntu packages:<br><code>sudo apt update <strong>&&</strong> sudo apt upgrade</code><br></li> <li>Install the Apache web server using <br><code>apt</code>:<code>sudo apt install apache2</code><br></li> <li>Install the MySQL web server:<br><code>sudo apt install mysql-server</code><br></li> <li>Install PHP, along with additional PHP modules for Apache and MySQL:<br><code>sudo apt install php libapache2-mod-php php-mysql</code><br></li> <li><strong>(Optional)</strong> Install the following commonly-used PHP modules.<br><code>sudo apt install php-curl php-json php-cgi</code><br></li> <li><strong>(Optional)</strong> To host a WordPress site on the server, install the following PHP components:<br><code>sudo apt install php-curl php-gd php-mbstring php-xml php-xmlrpc</code><br></li></ol>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2023/07/09/ubuntu-22-04-lamp-installation/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">468</post-id> </item> <item> <title>Ubuntu 22.04 Modify Open File Limits</title> <link>http://www.bictor.com/2022/07/17/ubuntu-16-04-modify-open-file-limits/</link> <comments>http://www.bictor.com/2022/07/17/ubuntu-16-04-modify-open-file-limits/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 17 Jul 2022 15:19:52 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=452</guid> <description><![CDATA[To check current limits Edit /etc/security/limits.conf – Add the following lines, also remember like root is a username, you should add all the usernames on which you wish to increase the limit Edit /etc/pam.d/common-session – Add the following line Edit]]></description> <content:encoded><![CDATA[<p>To check current limits </p> <pre class="wp-block-code"><code>ulimit -a</code></pre> <p>Edit /etc/security/limits.conf – Add the following lines, also remember like root is a username, you should add all the usernames on which you wish to increase the limit</p> <pre class="wp-block-code"><code>* soft nproc 9999999* hard nproc 9999999* soft nofile 9999999* hard nofile 9999999root soft nproc 9999999root hard nproc 9999999root soft nofile 9999999root hard nofile 9999999</code></pre> <p>Edit /etc/pam.d/common-session – Add the following line</p> <pre class="wp-block-code"><code>session required pam_limits.so</code></pre> <p>Edit the following file <code>/etc/systemd/user.conf</code>: – Add the following line</p> <pre class="wp-block-code"><code>DefaultLimitNOFILE=9999999</code></pre> <p>Edit /etc/sysctl.conf – Add the following line</p> <pre class="wp-block-code"><code>fs.file-max=9999999vm.max_map_count=9999999</code></pre> <p>Edit individual service file like for MongoDB Database – Edit /lib/systemd/system/mongod.service</p> <pre class="wp-block-code"><code>[Unit]Description=MongoDB Database ServerDocumentation=https://docs.mongodb.org/manualAfter=network.target [Service]User=mongodbGroup=mongodbEnvironmentFile=-/etc/default/mongodExecStart=/usr/bin/mongod --config /etc/mongod.confPIDFile=/var/run/mongodb/mongod.pid# file sizeLimitFSIZE=infinity# cpu timeLimitCPU=infinity# virtual memory sizeLimitAS=infinity# open filesLimitNOFILE=9999999# processes/threadsLimitNPROC=9999999# locked memoryLimitMEMLOCK=infinity# total threads (user+kernel)TasksMax=infinityTasksAccounting=false # Recommended limits for for mongod as specified in# http://docs.mongodb.org/manual/reference/ulimit/#recommended-settings [Install]WantedBy=multi-user.target</code></pre> <p>Run the following command in terminal</p> <pre class="wp-block-code"><code>systemctl daemon-reload</code></pre> <p>Done</p> <p></p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2022/07/17/ubuntu-16-04-modify-open-file-limits/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">452</post-id> </item> <item> <title>MacBook Pro 2009 – Ubuntu 20.04 Installation</title> <link>http://www.bictor.com/2021/06/16/macbook-pro-2009-ubuntu-20-04-installation/</link> <comments>http://www.bictor.com/2021/06/16/macbook-pro-2009-ubuntu-20-04-installation/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Wed, 16 Jun 2021 08:45:20 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=421</guid> <description><![CDATA[Download Ubuntu for Desktop (20.04) Burn on Pen Drive using Rufus (UEFI mode) Install normally as per the instructions provided on the screen Install full kde using sudo apt-get install kde-full sudo lshw -businfo -class bridge -class display Bus info]]></description> <content:encoded><![CDATA[<ol><li>Download Ubuntu for Desktop (20.04)</li><li>Burn on Pen Drive using Rufus (UEFI mode)</li><li>Install normally as per the instructions provided on the screen</li><li>Install full kde using</li></ol> <p><code>sudo apt-get install kde-full</code></p> <p>sudo lshw -businfo -class bridge -class display</p> <p style="font-size:11px">Bus info Device Class Description<br>========================================================<br>pci@0000:00:00.0 bridge MCP79 Host Bridge<br>pci@0000:00:03.0 bridge MCP79 LPC Bridge<br>pci@0000:00:09.0 bridge MCP79 PCI Bridge<br>pci@0000:00:0c.0 bridge MCP79 PCI Express Bridge<br><strong>pci@0000:00:10.0 bridge MCP79 PCI Express Bridge<br>pci@0000:03:00.0 display C79 [GeForce 9400M]</strong><br>pci@0000:00:15.0 bridge MCP79 PCI Express Bridge<br>pci@0000:00:16.0 bridge MCP79 PCI Express Bridge<br><br>Note: The addresses are of the display entry and PCI-E just before the display entry<br>It might vary and you might need to find the correct one</p> <p>Now create a new file 01_enable_vga.conf</p> <p class="has-small-font-size"><strong>Contents of the file created above : </strong><br>sudo setpci -s “00:10.0” 3e.b=8<br>sudo setpci -s “03:00.0” 04.b=7</p> <p>sudo chmod 755 01_enable_vga.conf<br>sudo mv 01_enable_vga.conf /etc/grub.d<br>sudo update-grub</p> <p>Reboot and Check</p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2021/06/16/macbook-pro-2009-ubuntu-20-04-installation/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">421</post-id> </item> <item> <title>Fix Old MacBook Windows 10 Reboot Issue</title> <link>http://www.bictor.com/2020/06/07/fix-old-macbook-windows-10-reboot-issue/</link> <comments>http://www.bictor.com/2020/06/07/fix-old-macbook-windows-10-reboot-issue/#comments</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 07 Jun 2020 21:46:49 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=383</guid> <description><![CDATA[I have MacBook 5,2 which i needed with Windows 10 as new MacOS is no further supported on it and i didn’t wanted to waste some good hardware engineering by Apple in it 🙂 However the installation of Windows 10]]></description> <content:encoded><![CDATA[<p>I have MacBook 5,2 which i needed with Windows 10 as new MacOS is no further supported on it and i didn’t wanted to waste some good hardware engineering by Apple in it <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p> <p>However the installation of Windows 10 was pretty straight forward – I made the installation disk with Rufus (with UEFI option) and put it in the MacBook and installed everything on the hardware. After initial installation I copied bootcamp drivers which i saved from Windows 7 disk and installed them also on the notebook which made almost all the functionality come alive on the MacBook. Along with those drivers Nvidia Display drivers were also intalled.</p> <p>Initially working without reboot everything was working fine but as soon it got rebooted it got stuck in the reboot loop .. with Windows Automatic Repair showing again and again. Finally i started researching on the problem and found that the problem was in the UEFI</p> <p><code>While Windows 10 no longer expects an EFI system to have VGA-compatible video, Nvidia drivers apparently still do and crash if they don’t detect it. The above commands are supposed to enable the VGA support in the graphics card."</code></p> <p>In order to fix the above issue, we need to somehow enable this in the UEFI firmware and i used the below technique to achieve it.</p> <ul><li>Boot your windows in Safe mode With Networking</li><li>Open DiskPart utility of windows</li></ul> <p><code>diskpart<br>select disk 0<br>select partition 2<br>assign letter=f</code></p> <p>In the above commands we assume that Disk 0 is where Windows are installed, Partition 2 is your boot partition made by Windows</p> <ul><li>Download Explorer++ from the net, its free –<a href="https://explorerplusplus.com/">https://explorerplusplus.com/</a></li><li>Open explorer++</li><li>Navigate to folder F:\EFI\Microsoft\Boot</li><li>Rename the original file bootmgfw.efi to bootmgfw_o.efi</li><li>Download the EFI shell from <a href="http://www.softcruise.com/shell_full.efi">http://www.softcruise.com/shell_full.efi</a></li><li>Copy shell_full.efi to F:\EFI\Microsoft\Boot</li><li>Make a new file by the name startup.nsh in the same folder</li><li>Write the following lines in it</li></ul> <p><code>mm 0010003E 1 ;PCI :8<br>mm 03000004 1 ;PCI :7<br>fs0:\EFI\Microsoft\Boot\bootmgfw_o.efi</code></p> <p>Now reboot your computer and it should boot without any trouble what-so-ever</p> <blockquote class="wp-block-quote"><p><strong><em>Note:</em></strong><br>Registers on your MacBook might be different from<br>mm 0010003E 1 ;PCI :8<br>mm 03000004 1 ;PCI :7<br><br>In order to identify the right registers you can make use of the following commands</p><p>03 00 00 is Display VGA<br>00 10 00 is Bridge Control<br><br>To find out the register value through efi shell</p><p>Shell> pci -b<br>Shell> pic -i 00 10 00 -b<br>Shell> mm 0001003E -PCI 8<br>Shell> pci -i 03 00 00 -b<br>Shell> mm 03000004 -PCI 7</p><p>As I found out in another older mac the VGA controller was with id 02 instead of 03, so your’s might differ</p></blockquote> <p><code><br></code></p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2020/06/07/fix-old-macbook-windows-10-reboot-issue/feed/</wfw:commentRss> <slash:comments>3</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">383</post-id> </item> <item> <title>Running VLC in Ubuntu as root</title> <link>http://www.bictor.com/2020/05/24/running-vlc-in-ubuntu-as-root/</link> <comments>http://www.bictor.com/2020/05/24/running-vlc-in-ubuntu-as-root/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 24 May 2020 10:57:18 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=374</guid> <description><![CDATA[Run the sed command below to make changes in the VLC binary file, it will replace the geteuid variable (which determines the effective user ID of the calling process) with getppid (which will determine the parent process ID of the calling process). In this command, ‘s/geteuid/getppid/‘]]></description> <content:encoded><![CDATA[<p>Run the <a href="https://www.tecmint.com/linux-sed-command-tips-tricks/" target="_blank" rel="noreferrer noopener">sed command</a> below to make changes in the VLC binary file, it will replace the <strong>geteuid</strong> variable (which determines the effective user ID of the calling process) with <strong>getppid</strong> (which will determine the parent process ID of the calling process).</p> <p>In this command, ‘<strong>s/geteuid/getppid/</strong>‘ (<strong>regexp=geteuid, replacement=getppid</strong>) does the magic.</p> <pre class="wp-block-preformatted">$ sudo sed -i 's/geteuid/getppid/' /usr/bin/vlc</pre>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2020/05/24/running-vlc-in-ubuntu-as-root/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">374</post-id> </item> <item> <title>Enable root user in Ubuntu 20.04</title> <link>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-20-04/</link> <comments>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-20-04/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 26 Apr 2020 13:41:55 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=368</guid> <description><![CDATA[Step 1: Login into your account and open terminal Step 2: Type the following command to setup password for root account sudo passwd root Step 3: Open file /etc/pam.d/gdm-password sudo nano /etc/pam.d/gdm-password Step 4: Comment out the following line by]]></description> <content:encoded><![CDATA[<p>Step 1: Login into your account and open terminal</p> <p>Step 2: Type the following command to setup password for root account</p> <pre class="wp-block-preformatted">sudo passwd root</pre> <p>Step 3: Open file /etc/pam.d/gdm-password</p> <pre class="wp-block-preformatted">sudo nano /etc/pam.d/gdm-password</pre> <p>Step 4: Comment out the following line by placing # infront of it</p> <pre class="wp-block-preformatted">#auth required pam_succeed_if.so user != root quiet_success</pre> <p>Step 5: sudo gedit<strong> /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf</strong></p> <p>Step 6: At the end of the file append <strong>greeter-show-manual–login = true</strong></p> <p>Step 7: Reboot the server</p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-20-04/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">368</post-id> </item> <item> <title>Enable root user in Ubuntu 16.04</title> <link>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-16-04/</link> <comments>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-16-04/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Sun, 26 Apr 2020 13:30:35 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=364</guid> <description><![CDATA[By default root user account is disabled for login in Ubuntu. Steps mentioned below will allow you to enable the root user and login as root on the OS. Login to your account and open Terminal sudo passwd root Type]]></description> <content:encoded><![CDATA[<p>By default root user account is disabled for login in Ubuntu. Steps mentioned below will allow you to enable the root user and login as root on the OS.</p> <ol><li>Login to your account and open Terminal</li><li>sudo passwd root</li><li>Type in the new password for UNIX</li><li>sudo gedit<strong> /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf</strong></li><li>At the end of the file append <strong>greeter-show-manual–login = true</strong></li></ol> <p>That’s all, now reboot the system and you can login to root account using manual login.</p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2020/04/26/enable-root-user-in-ubuntu-16-04/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">364</post-id> </item> <item> <title>MySQL on Ubuntu 18.04</title> <link>http://www.bictor.com/2020/04/24/mysql-on-ubuntu-18-04/</link> <comments>http://www.bictor.com/2020/04/24/mysql-on-ubuntu-18-04/#respond</comments> <dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator> <pubDate>Fri, 24 Apr 2020 12:58:31 +0000</pubDate> <category><![CDATA[Linux]]></category> <guid isPermaLink="false">http://www.bictor.com/?p=362</guid> <description><![CDATA[Introduction MySQL is an open-source database management system, commonly installed as part of the popular LAMP (Linux, Apache, MySQL, PHP/Python/Perl) stack. It uses a relational database and SQL (Structured Query Language) to manage its data. The short version of the installation is simple:]]></description> <content:encoded><![CDATA[<h3 class="wp-block-heading" id="introduction">Introduction</h3> <p><a href="https://www.mysql.com/">MySQL</a> is an open-source database management system, commonly installed as part of the popular <a href="https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-ubuntu-18-04">LAMP</a> (Linux, Apache, MySQL, PHP/Python/Perl) stack. It uses a relational database and SQL (Structured Query Language) to manage its data.</p> <p>The short version of the installation is simple: update your package index, install the <code>mysql-server</code> package, and then run the included security script.</p> <pre class="wp-block-code"><code>sudo apt updatesudo apt install mysql-serversudo mysql_secure_installation</code></pre> <p>This tutorial will explain how to install MySQL version 5.7 on an Ubuntu 18.04 server. However, if you’re looking to update an existing MySQL installation to version 5.7, you can read <a href="https://www.digitalocean.com/community/tutorials/how-to-prepare-for-your-mysql-5-7-upgrade">this MySQL 5.7 update guide</a> instead.</p> <h2 class="wp-block-heading" id="prerequisites">Prerequisites</h2> <p>To follow this tutorial, you will need:</p> <ul><li>One Ubuntu 18.04 server set up by following <a href="https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-18-04">this initial server setup guide</a>, including a non-<strong>root</strong> user with <code>sudo</code> privileges and a firewall.</li></ul> <h2 class="wp-block-heading" id="step-1-—-installing-mysql">Step 1 — Installing MySQL</h2> <p>On Ubuntu 18.04, only the latest version of MySQL is included in the APT package repository by default. At the time of writing, that’s MySQL 5.7</p> <p>To install it, update the package index on your server with <code>apt</code>:</p> <pre class="wp-block-code"><code>sudo apt update</code></pre> <p>Then install the default package:</p> <pre class="wp-block-code"><code>sudo apt install mysql-server</code></pre> <p>This will install MySQL, but will not prompt you to set a password or make any other configuration changes. Because this leaves your installation of MySQL insecure, we will address this next.</p> <h2 class="wp-block-heading" id="step-2-—-configuring-mysql">Step 2 — Configuring MySQL</h2> <p>For fresh installations, you’ll want to run the included security script. This changes some of the less secure default options for things like remote root logins and sample users. On older versions of MySQL, you needed to initialize the data directory manually as well, but this is done automatically now.</p> <p>Run the security script:</p> <pre class="wp-block-code"><code>sudo mysql_secure_installation</code></pre> <p>This will take you through a series of prompts where you can make some changes to your MySQL installation’s security options. The first prompt will ask whether you’d like to set up the Validate Password Plugin, which can be used to test the strength of your MySQL password. Regardless of your choice, the next prompt will be to set a password for the MySQL <strong>root</strong> user. Enter and then confirm a secure password of your choice.</p> <p>From there, you can press <code>Y</code> and then <code>ENTER</code> to accept the defaults for all the subsequent questions. This will remove some anonymous users and the test database, disable remote root logins, and load these new rules so that MySQL immediately respects the changes you have made.</p> <p>To initialize the MySQL data directory, you would use <code>mysql_install_db</code> for versions before 5.7.6, and <code>mysqld --initialize</code> for 5.7.6 and later. However, if you installed MySQL from the Debian distribution, as described in Step 1, the data directory was initialized automatically; you don’t have to do anything. If you try running the command anyway, you’ll see the following error:Output</p> <pre class="wp-block-code"><code>mysqld: Can't create directory '/var/lib/mysql/' (Errcode: 17 - File exists). . .2018-04-23T13:48:00.572066Z 0 [ERROR] Aborting</code></pre> <p>Note that even though you’ve set a password for the <strong>root</strong> MySQL user, this user is not configured to authenticate with a password when connecting to the MySQL shell. If you’d like, you can adjust this setting by following Step 3.</p> <h2 class="wp-block-heading" id="step-3-—-optional-adjusting-user-authentication-and-privileges">Step 3 — (Optional) Adjusting User Authentication and Privileges</h2> <p>In Ubuntu systems running MySQL 5.7 (and later versions), the <strong>root</strong> MySQL user is set to authenticate using the <code>auth_socket</code> plugin by default rather than with a password. This allows for some greater security and usability in many cases, but it can also complicate things when you need to allow an external program (e.g., phpMyAdmin) to access the user.</p> <p>In order to use a password to connect to MySQL as <strong>root</strong>, you will need to switch its authentication method from <code>auth_socket</code> to <code>mysql_native_password</code>. To do this, open up the MySQL prompt from your terminal:</p> <pre class="wp-block-code"><code>sudo mysql</code></pre> <p>Next, check which authentication method each of your MySQL user accounts use with the following command:</p> <pre class="wp-block-code"><code>SELECT user,authentication_string,plugin,host FROM mysql.user;</code></pre> <pre class="wp-block-code"><code>Output+------------------+-------------------------------------------+-----------------------+-----------+| user | authentication_string | plugin | host |+------------------+-------------------------------------------+-----------------------+-----------+| root | | auth_socket | localhost || mysql.session | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost || mysql.sys | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost || debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |+------------------+-------------------------------------------+-----------------------+-----------+4 rows in set (0.00 sec)</code></pre> <p>In this example, you can see that the <strong>root</strong> user does in fact authenticate using the <code>auth_socket</code> plugin. To configure the <strong>root</strong> account to authenticate with a password, run the following <code>ALTER USER</code> command. Be sure to change <code>password</code> to a strong password of your choosing, and note that this command will change the <strong>root</strong> password you set in Step 2:</p> <pre class="wp-block-code"><code>ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';</code></pre> <p>Then, run <code>FLUSH PRIVILEGES</code> which tells the server to reload the grant tables and put your new changes into effect:</p> <pre class="wp-block-code"><code>FLUSH PRIVILEGES;</code></pre> <p>Check the authentication methods employed by each of your users again to confirm that <strong>root</strong> no longer authenticates using the <code>auth_socket</code> plugin:</p> <pre class="wp-block-code"><code>SELECT user,authentication_string,plugin,host FROM mysql.user;</code></pre> <pre class="wp-block-code"><code>Output+------------------+-------------------------------------------+-----------------------+-----------+| user | authentication_string | plugin | host |+------------------+-------------------------------------------+-----------------------+-----------+| root | *3636DACC8616D997782ADD0839F92C1571D6D78F | mysql_native_password | localhost || mysql.session | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost || mysql.sys | *THISISNOTAVALIDPASSWORDTHATCANBEUSEDHERE | mysql_native_password | localhost || debian-sys-maint | *CC744277A401A7D25BE1CA89AFF17BF607F876FF | mysql_native_password | localhost |+------------------+-------------------------------------------+-----------------------+-----------+4 rows in set (0.00 sec)</code></pre> <p>You can see in this example output that the <strong>root</strong> MySQL user now authenticates using a password. Once you confirm this on your own server, you can exit the MySQL shell:</p> <pre class="wp-block-code"><code>exit</code></pre> <p>Alternatively, some may find that it better suits their workflow to connect to MySQL with a dedicated user. To create such a user, open up the MySQL shell once again:</p> <pre class="wp-block-code"><code>sudo mysql</code></pre> <p><strong>Note:</strong> If you have password authentication enabled for <strong>root</strong>, as described in the preceding paragraphs, you will need to use a different command to access the MySQL shell. The following will run your MySQL client with regular user privileges, and you will only gain administrator privileges within the database by authenticating:</p> <pre class="wp-block-code"><code>mysql -u root -p</code></pre> <p>From there, create a new user and give it a strong password:</p> <pre class="wp-block-code"><code>CREATE USER 'sammy'@'localhost' IDENTIFIED BY 'password';</code></pre> <p>Then, grant your new user the appropriate privileges. For example, you could grant the user privileges to all tables within the database, as well as the power to add, change, and remove user privileges, with this command:</p> <pre class="wp-block-code"><code>GRANT ALL PRIVILEGES ON *.* TO 'sammy'@'localhost' WITH GRANT OPTION;</code></pre> <p>Note that, at this point, you do not need to run the <code>FLUSH PRIVILEGES</code> command again. This command is only needed when you modify the grant tables using statements like <code>INSERT</code>, <code>UPDATE</code>, or <code>DELETE</code>. Because you created a new user, instead of modifying an existing one, <code>FLUSH PRIVILEGES</code> is unnecessary here.</p> <p>Following this, exit the MySQL shell:</p> <pre class="wp-block-code"><code>exit</code></pre> <p>Finally, let’s test the MySQL installation.</p> <h2 class="wp-block-heading" id="step-4-—-testing-mysql">Step 4 — Testing MySQL</h2> <p>Regardless of how you installed it, MySQL should have started running automatically. To test this, check its status.</p> <pre class="wp-block-code"><code>systemctl status mysql.service</code></pre> <p>You’ll see output similar to the following:Output</p> <pre class="wp-block-code"><code>● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en Active: active (running) since Wed 2018-04-23 21:21:25 UTC; 30min ago Main PID: 3754 (mysqld) Tasks: 28 Memory: 142.3M CPU: 1.994s CGroup: /system.slice/mysql.service └─3754 /usr/sbin/mysqld</code></pre> <p>If MySQL isn’t running, you can start it with <code>sudo systemctl start mysql</code>.</p> <p>For an additional check, you can try connecting to the database using the <code>mysqladmin</code> tool, which is a client that lets you run administrative commands. For example, this command says to connect to MySQL as <strong>root</strong> (<code>-u root</code>), prompt for a password (<code>-p</code>), and return the version.</p> <pre class="wp-block-code"><code>sudo mysqladmin -p -u root version</code></pre> <p>You should see output similar to this:Output</p> <pre class="wp-block-code"><code>mysqladmin Ver 8.42 Distrib 5.7.21, for Linux on x86_64Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or itsaffiliates. Other names may be trademarks of their respectiveowners. Server version 5.7.21-1ubuntu1Protocol version 10Connection Localhost via UNIX socketUNIX socket /var/run/mysqld/mysqld.sockUptime: 30 min 54 sec Threads: 1 Questions: 12 Slow queries: 0 Opens: 115 Flush tables: 1 Open tables: 34 Queries per second avg: 0.006</code></pre> <p>This means MySQL is up and running.</p>]]></content:encoded> <wfw:commentRss>http://www.bictor.com/2020/04/24/mysql-on-ubuntu-18-04/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <post-id xmlns="com-wordpress:feed-additions:1">362</post-id> </item> </channel></rss> If you would like to create a banner that links to this page (i.e. this validation result), do the following:
Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):
If you would like to create a text link instead, here is the URL you can use:
http://www.feedvalidator.org/check.cgi?url=http%3A//www.bictor.com/feed/
