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 30, 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/"
>
<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>Mon, 08 Jul 2024 06:34:53 +0000</lastBuildDate>
<language>en</language>
<sy:updatePeriod>
hourly </sy:updatePeriod>
<sy:updateFrequency>
1 </sy:updateFrequency>
<generator>https://wordpress.org/?v=6.7.2</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 24.04 Problems & Solutions</title>
<link>http://www.bictor.com/2024/07/02/ubuntu-24-04-problems-solutions/</link>
<comments>http://www.bictor.com/2024/07/02/ubuntu-24-04-problems-solutions/#respond</comments>
<dc:creator><![CDATA[thinkofashish@gmail.com]]></dc:creator>
<pubDate>Tue, 02 Jul 2024 06:03:12 +0000</pubDate>
<category><![CDATA[Linux]]></category>
<guid isPermaLink="false">http://www.bictor.com/?p=488</guid>
<description><![CDATA[Problem 1: Slow booting after fresh installation Problem could be seen when rebooting that Networkd is trying to continuously connect online, however it fails after 2 minutes of wait Solution: systemctl edit systemd-networkd-wait-online.service Add following lines ###Editing /etc/systemd/system/systemd-networkd-wait-online.service.d/override>###Anything between here]]></description>
<content:encoded><![CDATA[
<p><strong>Problem 1: Slow booting after fresh installation</strong></p>
<p>Problem could be seen when rebooting that Networkd is trying to continuously connect online, however it fails after 2 minutes of wait</p>
<p>Solution: </p>
<p><code>systemctl edit systemd-networkd-wait-online.service</code></p>
<p>Add following lines</p>
<h3 class="wp-block-heading"><code>###Editing /etc/systemd/system/systemd-networkd-wait-online.service.d/override><br>###Anything between here and the comment below will become the contents of the><br>[Service]<br>ExecStart=<br>ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --interface=ens33<br>###Edits below this comment will be discarded</code></h3>
<p>Please note that –interface option should match with your active interfaces which can be seen using the ifconfig command</p>
<p></p>
<p><strong>Problem 2: VMWare Tools setup</strong></p>
<p>By default VMWare tools are not installed inside the VM and requires to install the following</p>
<p><code>apt install open-vm-tools open-vm-tools-desktop</code></p>
<p></p>
<p><strong>Problem 3: VMWare Display Freeze</strong></p>
<p>If VMWare is freezing Ubuntu 24.04 Display then we need to update drivers</p>
<p><code>sudo add-apt-repository ppa:oibaf/graphics-drivers<br>sudo apt update && sudo apt upgrade</code></p>
]]></content:encoded>
<wfw:commentRss>http://www.bictor.com/2024/07/02/ubuntu-24-04-problems-solutions/feed/</wfw:commentRss>
<slash:comments>0</slash:comments>
<post-id xmlns="com-wordpress:feed-additions:1">488</post-id> </item>
<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 11:23: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 in
root 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 in
root 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 Latest
root pts/0 12.345.678.90 Fri Jan 8 15:30:06 +0000 2021
daemon **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 2021
hack0r 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 ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4G 1 loop
sda 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 part
sdb 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 /mnt
chroot /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 15:54: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 11:13: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 class="wp-block-list">
<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 09:49: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 9999999
root soft nproc 9999999
root hard nproc 9999999
root soft nofile 9999999
root 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=9999999
vm.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 Server
Documentation=https://docs.mongodb.org/manual
After=network.target
[Service]
User=mongodb
Group=mongodb
EnvironmentFile=-/etc/default/mongod
ExecStart=/usr/bin/mongod --config /etc/mongod.conf
PIDFile=/var/run/mongodb/mongod.pid
# file size
LimitFSIZE=infinity
# cpu time
LimitCPU=infinity
# virtual memory size
LimitAS=infinity
# open files
LimitNOFILE=9999999
# processes/threads
LimitNPROC=9999999
# locked memory
LimitMEMLOCK=infinity
# total threads (user+kernel)
TasksMax=infinity
TasksAccounting=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 03:15: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 class="wp-block-list"><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 16:16: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/15.0.3/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 class="wp-block-list"><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 class="wp-block-list"><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 is-layout-flow wp-block-quote-is-layout-flow"><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 05:27: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 08:11: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 08:00: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 class="wp-block-list"><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>
</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/