<?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>Linux &#8211; LarryLai</title>
	<atom:link href="https://larrylai.com/category/it/system/os/linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://larrylai.com</link>
	<description>兼聽則明 偏聽則暗</description>
	<lastBuildDate>Sun, 01 Sep 2019 11:09:46 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://larrylai.com/wp-content/uploads/2017/03/larrylai_com-favicon.png</url>
	<title>Linux &#8211; LarryLai</title>
	<link>https://larrylai.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>CentOS VM Client Can&#8217;t Boot Up</title>
		<link>https://larrylai.com/centos-vm-client-cant-boot-up/</link>
					<comments>https://larrylai.com/centos-vm-client-cant-boot-up/#respond</comments>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Fri, 30 Aug 2019 15:59:24 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[System]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Boot Up]]></category>
		<category><![CDATA[CentOS7]]></category>
		<category><![CDATA[SELINUX]]></category>
		<category><![CDATA[VirtualBox6]]></category>
		<guid isPermaLink="false">http://larrylai.com/?p=3695</guid>

					<description><![CDATA[<p>Issue VirtualBox client CentOS can&#8217;t boot up with error message: [FAILED] Failed to start Virtual Machine and Container Registration Service. [FAILED] Failed to start Login Service. Solution Disable SELINUX config with the following steps during boot up sequence: During Grub boot up stage, press &#039;e&#039; to edit grub sequence; Add systemd.unit=rescue.target to the end of [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/centos-vm-client-cant-boot-up/">CentOS VM Client Can&#8217;t Boot Up</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h3>Issue</h3>
<p>VirtualBox client CentOS can&#8217;t boot up with error message: </p>
<ol>
<li>[FAILED] Failed to start Virtual Machine and Container Registration Service.</li>
<li>[FAILED] Failed to start Login Service.<br />
<img decoding="async" src="http://larrylai.com/wp-content/uploads/2019/08/Screenshot-2019-08-30-at-12.20.17-PM.png" alt="" /></li>
</ol>
<h3>Solution</h3>
<p>Disable SELINUX config with the following steps during boot up sequence:</p>
<ol>
<li>During Grub boot up stage, press <code>&#039;e&#039;</code> to edit grub sequence;</li>
<li>Add <code>systemd.unit=rescue.target</code> to the end of line with linux16 and boot with rescue mode;</li>
<li>Press ctrl+x to continue boot sequence</li>
</ol>
<h3>Config</h3>
<ul>
<li>CentOS 7 3.10</li>
<li>VirtualBox 6.0.10</li>
</ul>
<h3>Tricks</h3>
<ul>
<li>The cause of this boot up issue was difficult to found and the original setting of SELINUX was &#8216;permissive&#8217; not &#8216;enabled&#8217;. However, this issue may also be owing to bugs in VirtualBox 6.</li>
<li>During boot up process, by default the boot up is quiet, i.e. no system message will be displayed, only the boot up progress bar is seen. However, pressing <code>Esc</code> key will let you see the detail boot up messages.</li>
</ul>
<p>The post <a rel="nofollow" href="https://larrylai.com/centos-vm-client-cant-boot-up/">CentOS VM Client Can&#8217;t Boot Up</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://larrylai.com/centos-vm-client-cant-boot-up/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OpenSUSE Boot Up Issue</title>
		<link>https://larrylai.com/opensuse-boot-up-issue/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Sat, 13 Feb 2016 23:08:45 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<category><![CDATA[OpenSUSE]]></category>
		<category><![CDATA[Storage]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=2079</guid>

					<description><![CDATA[<p>Issue: OpenSUSE suddenly could not boot to GUI mode, but being kicked out to recovery mode with the CLI mode with the warning of something like no space to write on device, and the hard disk activity light was unexpectedly always on. Solution: At the recovery mode, login as root and delete some snapshots. Execute [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/opensuse-boot-up-issue/">OpenSUSE Boot Up Issue</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>OpenSUSE suddenly could not boot to GUI mode, but being kicked out to recovery mode with the CLI mode with the warning of something like no space to write on device, and the hard disk activity light was unexpectedly always on.</p>
<p><strong>Solution:</strong></p>
<ul>
<li>At the recovery mode, login as root and delete some snapshots.</li>
<li>Execute &#8220;snapper ls&#8221; to get the snapshot numbers</li>
<li>Execute &#8220;snapper delete [start number] &#8211; [end number]&#8221;</li>
<li>Reboot</li>
</ul>
<p><strong>Tricks:</strong></p>
<ol>
<li>This issue probably occurs only on linux system with <a href="https://en.wikipedia.org/wiki/Btrfs" target="_blank" rel="noopener">btrfs</a> partition in which snapshots are automatically generated. Thus, it should be paid extra care to decide whether to use traditional ext3 or ext4 instead of the default partition option: btrfs suggested by OpenSUSE during installation.</li>
<li>When typing &#8220;df -h&#8221;, the storage usage seems to be normal. No storage or any partition full could be noticed.</li>
<li>When hard disk activity light always on, it seems that something related to hardware is wrong but actually it doesn&#8217;t.</li>
<li>My partition config. fully agreed OpenSUSE suggestion that btrfs for / directory and xfs for /home directory. Yesterday, due to some video files transfer from desktop PC to iPhone using FTP, I setup FTP server on desktop using proftpd, the default directory on server side is /srv/ftp. Probably the new video files are so large that btrfs generated large snapshots under / directory.</li>
</ol>
<p><strong>Config:</strong></p>
<ul>
<li>OpenSUSE 13.2</li>
<li>KDE4 1.0</li>
</ul>
<p>The post <a rel="nofollow" href="https://larrylai.com/opensuse-boot-up-issue/">OpenSUSE Boot Up Issue</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ugly Font Appearance in Linux</title>
		<link>https://larrylai.com/ugly-font-appearance-in-linux/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Fri, 06 Feb 2015 16:04:19 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1915</guid>

					<description><![CDATA[<p>Issue: Suddenly found that the Serif fonts appeared in Linux is uglier than those appeared on Mac OS X. Solution: Configure Desktop by enabling Use sub-pixel rendering, and choose Slight in Hinting style. Config: OpenSuse 13.1 KDE 4.11 Tricks: Some suggestion was to install Microsoft fonts, actually this could be done but still ugly Serif [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/ugly-font-appearance-in-linux/">Ugly Font Appearance in Linux</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>Suddenly found that the Serif fonts appeared in Linux is uglier than those appeared on Mac OS X.</p>
<p><strong>Solution:</strong></p>
<p>Configure Desktop by enabling Use sub-pixel rendering, and choose Slight in Hinting style.</p>
<p><strong>Config:</strong></p>
<ul>
<li>OpenSuse 13.1</li>
<li>KDE 4.11</li>
</ul>
<p><strong>Tricks:</strong></p>
<p>Some suggestion was to install Microsoft fonts, actually this could be done but still ugly Serif fonts was shown.</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/ugly-font-appearance-in-linux/">Ugly Font Appearance in Linux</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Laser Printer for Linux</title>
		<link>https://larrylai.com/laser-printer-for-linux/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Sun, 01 Feb 2015 15:16:39 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1866</guid>

					<description><![CDATA[<p>Issue: Installed Linux driver for Brother DCP-L2540DW printer driver, then found out that printing for one page or double-sided page is fine, but it always shows error &#8220;ERROR NAME; memoryfull&#8221; printed on a page then stop. when starting to print multiple pages from a file. Not working even tune down the resolution from 600dpi to [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/laser-printer-for-linux/">Laser Printer for Linux</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>Installed Linux driver for Brother DCP-L2540DW printer driver, then found out that printing for one page or double-sided page is fine, but it always shows error</p>
<p>&#8220;ERROR NAME; memoryfull&#8221; printed on a page then stop.</p>
<p>when starting to print multiple pages from a file. Not working even tune down the resolution from 600dpi to 300dpi as suggested by Brother&#8217;s official support site.</p>
<p><strong>Solution:</strong></p>
<p>Replace driver:</p>
<p>Brother DCP-L2540DW with driver Brother DCP-8045D BR-Script3</p>
<p>by:</p>
<p>Brother DCP-8045D &#8211; CUPS+Gutenprint v5.2.9</p>
<p><strong>Tricks:</strong></p>
<p>After installing the rpm package downloaded from Brother&#8217;s official support site, there is no driver with name specific for DCP-L2540DW, thus installing 8045D instead.</p>
<p><strong>Config:</strong></p>
<ul>
<li>Brother Monochrome Laser Printer DCP-L2540DW</li>
<li>OpenSUSE 13.1-13.6.1</li>
<li>CUPS ver. 1.5.4-12.13.1</li>
</ul>
<p>The post <a rel="nofollow" href="https://larrylai.com/laser-printer-for-linux/">Laser Printer for Linux</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>CentOS Not Bootable after Install Kernel-devel rpm</title>
		<link>https://larrylai.com/centos-not-bootable-after-install-kernel-devel-rpm/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Fri, 10 Jan 2014 16:01:50 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1470</guid>

					<description><![CDATA[<p>Issue: OS unbootable and show the following message: Kernel panic &#8211; not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Solution: At waiting to boot loader click any key to access the boot kernel menu Select previous kernel version other than the default latest installed one Config: CentOS    6.4 Kernel      2.6.32-431.1.2.0.1.el6.x86_64 [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/centos-not-bootable-after-install-kernel-devel-rpm/">CentOS Not Bootable after Install Kernel-devel rpm</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue: </strong></p>
<p>OS unbootable and show the following message:</p>
<p style="margin-left: 40px;"><span style="line-height: 1.5;">Kernel panic &#8211; not syncing: VFS: Unable to mount root fs on unknown-block(0,0)</span></p>
<p><strong>Solution:</strong></p>
<ul>
<li>At waiting to boot loader</li>
<li>click any key to access the boot kernel menu</li>
<li>Select previous kernel version other than the default latest installed one</li>
</ul>
<p><strong>Config</strong>:</p>
<ul>
<li>CentOS    6.4</li>
<li>Kernel      2.6.32-431.1.2.0.1.el6.x86_64</li>
</ul>
<p><strong>Tricks:</strong></p>
<p>Upon upgrading the kernel or installed the kernel-devel packages, the system was still running the current kernel until next system reboot. In case, the reboot schedule was long after this kernel-devel, it is not easy to remember kernel-devel was installed and as a side effect also upgraded the kernel.</p>
<p style="margin-left: 40px;">
<p>The post <a rel="nofollow" href="https://larrylai.com/centos-not-bootable-after-install-kernel-devel-rpm/">CentOS Not Bootable after Install Kernel-devel rpm</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>OpenSuse Chinese Input Issue with SCIM</title>
		<link>https://larrylai.com/opensuse-chinese-input-issue-with-scim/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Wed, 20 Nov 2013 09:23:30 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1485</guid>

					<description><![CDATA[<p>Issue: Using SCIM happily to input Chinese characters with my previous Linux distribution &#8211; Ubuntu, but using SCIM in my current OpenSuse is painful as the screen refeashing always crawls after selecting a chinese character, sometimes like system hangs. Solution: Uninstall SCIM Install fcitx packages Add Secondary Language from Yast to include Traditional Chinese such [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/opensuse-chinese-input-issue-with-scim/">OpenSuse Chinese Input Issue with SCIM</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>Using SCIM happily to input Chinese characters with my previous Linux distribution &#8211; Ubuntu, but using SCIM in my current OpenSuse is painful as the screen refeashing always crawls after selecting a chinese character, sometimes like system hangs.</p>
<p><strong>Solution:</strong></p>
<ol>
<li>Uninstall SCIM</li>
<li>Install <a href="https://fcitx-im.org/wiki/Fcitx" target="_blank" rel="noopener">fcitx</a> packages</li>
<li>Add Secondary Language from Yast to include Traditional Chinese such that appropriate fonts are to be installed.</li>
</ol>
<p><strong>Configuration:</strong></p>
<ul>
<li>OpenSuse     12.3 (x86_64)</li>
<li>fcitx               4.2.7</li>
</ul>
<p>The post <a rel="nofollow" href="https://larrylai.com/opensuse-chinese-input-issue-with-scim/">OpenSuse Chinese Input Issue with SCIM</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Bootable USB with UNetbootin</title>
		<link>https://larrylai.com/bootable-usb-with-unetbootin/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Wed, 27 Feb 2013 06:49:44 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1617</guid>

					<description><![CDATA[<p>Issue: Worked with UNetbootin to make bootable USB to install new OS or rescue OS several times happily, but didn&#8217;t work anymore for OpenSuse. UNetbootin silently could not successfully Extracting and Copying Files (i.e. Step 2). Solution: Use MagicDisc to mount the OpenSuse ISO file Copy the content of the ISO to a temp directory [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/bootable-usb-with-unetbootin/">Bootable USB with UNetbootin</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue: </strong></p>
<p>Worked with UNetbootin to make bootable USB to install new OS or rescue OS several times happily, but didn&#8217;t work anymore for OpenSuse. UNetbootin silently could not successfully Extracting and Copying Files (i.e. Step 2).</p>
<p><strong>Solution:</strong></p>
<p>Use MagicDisc to mount the OpenSuse ISO file</p>
<p>Copy the content of the ISO to a temp directory</p>
<p>Use All FreeISO Creator to create ISO</p>
<p><strong>Config:</strong></p>
<ul>
<li>Windows 7</li>
<li>UNetbootin583</li>
<li>MagicDisc 2.7 build 106</li>
<li>All FreeISO Creator 3.1.9</li>
</ul>
<p><strong>Tricks:</strong></p>
<p>Seems that funny to extract the ISO and wrap it again, but found no other way to make the bootable USB.</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/bootable-usb-with-unetbootin/">Bootable USB with UNetbootin</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>unable to set superblock flags</title>
		<link>https://larrylai.com/superblock/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Sat, 16 Aug 2008 02:27:12 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1891</guid>

					<description><![CDATA[<p>Issue: System hang, then reboot but unable to boot up! system suggested &#8220;e2fsck&#8221;. after fixing/ cleaning some files, &#8220;unable to set superblock flags&#8221; on /user/local Solution: execute: e2fsck -b 32768 /dev/hda2 reboot Tricks: system suggested: e2fsck -b 8136 &#60;device&#62; can&#8217;t run this command as 8136 is not a good magic no. visit: http://ge.ubuntuforums.com/showthread.php?p=5060346 &#160;</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/superblock/">unable to set superblock flags</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>System hang, then reboot but unable to boot up!</p>
<p>system suggested &#8220;e2fsck&#8221;. after fixing/ cleaning some files, &#8220;unable to set superblock flags&#8221; on /user/local</p>
<p><strong>Solution:</strong></p>
<ul>
<li>execute: e2fsck -b 32768 /dev/hda2</li>
<li>reboot</li>
</ul>
<p><strong>Tricks:</strong></p>
<ul>
<li>system suggested: e2fsck -b 8136 &lt;device&gt;</li>
<li>can&#8217;t run this command as 8136 is not a good magic no.</li>
<li>visit: http://ge.ubuntuforums.com/showthread.php?p=<a href="tel:5060346">5060346</a></li>
</ul>
<p>&nbsp;</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/superblock/">unable to set superblock flags</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>yum quited unexpectedly</title>
		<link>https://larrylai.com/yum-quited-unexpectedly/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Sat, 03 Jun 2006 14:16:48 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1875</guid>

					<description><![CDATA[<p>Issue: Run: Yum install postgreSQL for SQL-Ledger, but appear: unable to find pid then the shell running yum as root quited unexpectedly Solution: Run: rpm &#8211;rebuilddb; yum clean all Tricks: After the weird behaviour of yum being quited unexpectedly, there are 0 Highmem, 0 free page messages in /var/log/messages, but it finally seems that there is nothing [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/yum-quited-unexpectedly/">yum quited unexpectedly</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>Run:</p>
<p style="margin-left: 40px;">Yum install postgreSQL</p>
<p>for SQL-Ledger, but appear:</p>
<p style="margin-left: 40px;">unable to find pid</p>
<p>then the shell running yum as root quited unexpectedly</p>
<p><strong>Solution:</strong></p>
<p>Run:</p>
<p style="margin-left: 40px;">rpm &#8211;rebuilddb; yum clean all</p>
<p><strong>Tricks:</strong></p>
<p>After the weird behaviour of yum being quited unexpectedly, there are 0 Highmem, 0 free page messages in /var/log/messages, but it finally seems that there is nothing wrong with the memory management. The reason why rpm db corrupt may be due to interruption of a running yum process.</p>
<p><strong>Configuration:</strong></p>
<ul>
<li>HW: Dell SC1425 w/ Xeon 2.8GHz x1, 512MB x2 memory</li>
<li>OS: CentOS 3.4</li>
</ul>
<p>The post <a rel="nofollow" href="https://larrylai.com/yum-quited-unexpectedly/">yum quited unexpectedly</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Using Scanner</title>
		<link>https://larrylai.com/using-scanner/</link>
		
		<dc:creator><![CDATA[larry]]></dc:creator>
		<pubDate>Sun, 30 Apr 2006 04:52:26 +0000</pubDate>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[System]]></category>
		<guid isPermaLink="false">http://blog.larrylai.com/?p=1863</guid>

					<description><![CDATA[<p>Issue: install application for scanning images in Linux Solution: install sane-backends, xsane, Tricks: also install xsane-gimp if having xsane as a plugin of gimp (instead of ln -s /usr/bin/xsane ~/.gimp*/plug-ins this DOESN&#8217;T work!!!) if connecting more than 1 scanner device, or having video card installed run: xsane [backendname:device] to start xsane with corrent device without [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/using-scanner/">Using Scanner</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><strong>Issue:</strong></p>
<p>install application for scanning images in Linux</p>
<p><strong>Solution:</strong></p>
<p>install sane-backends, xsane,</p>
<p><strong>Tricks:</strong></p>
<p>also install xsane-gimp if having xsane as a plugin of gimp (instead of ln -s /usr/bin/xsane ~/.gimp*/plug-ins this DOESN&#8217;T work!!!)<br />
if connecting more than 1 scanner device, or having video card installed<br />
run:</p>
<p style="margin-left: 40px;">xsane [backendname:device]</p>
<p>to start xsane with corrent device without trouble of choosing device immediately after startup of xsane.</p>
<p>backendname:device can be obtained by:</p>
<p style="margin-left: 40px;">scanimage -L</p>
<p>The post <a rel="nofollow" href="https://larrylai.com/using-scanner/">Using Scanner</a> appeared first on <a rel="nofollow" href="https://larrylai.com">LarryLai</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
