<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Linux on Debian Addict</title>
    <link>https://debianaddict.com/tags/linux/</link>
    <description>Recent content in Linux on Debian Addict</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 08 Mar 2013 10:47:46 +0000</lastBuildDate>
    <atom:link href="https://debianaddict.com/tags/linux/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>su&#43;screen: &#34;Cannot open your terminal &#39;/dev/pts/0&#39; - please check.&#34;</title>
      <link>https://debianaddict.com/2013/03/08/gnu-screen-cannot-open-terminal-when-you-su-to-a-user/</link>
      <pubDate>Fri, 08 Mar 2013 10:47:46 +0000</pubDate>
       <guid isPermaLink="false">http://debianaddict.com/?p=56</guid> 
      <description>&lt;p&gt;Quick tip this time.&lt;/p&gt;
&lt;p&gt;Often enough, one is logged in as root and decides to su - to an underprivileged user. Due to the tty for the root shell being owned by the user root, the su&amp;rsquo;d environment is unable to run screen:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;root@whitegirl:~# su - joe joe@whitegirl:~$ screen Cannot open your terminal &#39;/dev/pts/0&#39; - please check. joe@whitegirl:~$ &lt;/code&gt;&lt;/p&gt;
&lt;p&gt;This is resolved by setting the owner of the terminal device to the target user before running su, so the user then has write privileges on the pseudo teletype device:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fixing a dpkg io error</title>
      <link>https://debianaddict.com/2011/08/18/fixing-a-dpkg-io-error/</link>
      <pubDate>Fri, 19 Aug 2011 03:20:10 +0000</pubDate>
       <guid isPermaLink="false">http://blog.joegillotti.com/?p=13</guid> 
      <description>&lt;p&gt;I encountered a &lt;code&gt;dpkg&lt;/code&gt; related error a little while ago while upgrading packages on my Ubuntu Lucid server. I couldn&amp;rsquo;t find a fix on the internet and spent a little while investigating the cause. You can see from the command output that &lt;code&gt;dpkg&lt;/code&gt; failed to properly install the Linux kernel package:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;root@aeroplane:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-2.6.32-33-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0B/31.6MB of archives. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? y (Reading database ... 178303 files and directories currently installed.) Preparing to replace linux-image-2.6.32-33-generic 2.6.32-33.70 (using .../linux-image-2.6.32-33-generic_2.6.32-33.71_i386.deb) ... Done. Unpacking replacement linux-image-2.6.32-33-generic ... dpkg-deb: subprocess paste killed by signal (Broken pipe) dpkg: error processing /var/cache/apt/archives/linux-image-2.6.32-33-generic_2.6.32-33.71_i386.deb (--unpack): short read in buffer_copy (backend dpkg-deb during `./lib/modules/2.6.32-33-generic/kernel/drivers/ata/sata_mv.ko&#39;) No apport report written because the error message indicates a dpkg I/O error Running postrm hook script /usr/sbin/update-grub. Generating grub.cfg ... Found initrd image: /boot/initrd.img-2.6.32-33-generic Found linux image: /boot/vmlinuz-2.6.32-32-generic Found initrd image: /boot/initrd.img-2.6.32-32-generic Found linux image: /boot/vmlinuz-2.6.32-31-generic Found initrd image: /boot/initrd.img-2.6.32-31-generic Found linux image: /boot/vmlinuz-2.6.32-30-generic Found initrd image: /boot/initrd.img-2.6.32-30-generic Found linux image: /boot/vmlinuz-2.6.32-29-generic Found initrd image: /boot/initrd.img-2.6.32-29-generic Found linux image: /boot/vmlinuz-2.6.32-28-generic Found initrd image: /boot/initrd.img-2.6.32-28-generic Found linux image: /boot/vmlinuz-2.6.32-27-generic Found initrd image: /boot/initrd.img-2.6.32-27-generic Found linux image: /boot/vmlinuz-2.6.32-26-generic Found initrd image: /boot/initrd.img-2.6.32-26-generic Found linux image: /boot/vmlinuz-2.6.32-25-generic Found initrd image: /boot/initrd.img-2.6.32-25-generic Found linux image: /boot/vmlinuz-2.6.32-24-generic Found initrd image: /boot/initrd.img-2.6.32-24-generic Found linux image: /boot/vmlinuz-2.6.32-21-generic Found initrd image: /boot/initrd.img-2.6.32-21-generic Found memtest86+ image: /boot/memtest86+.bin done Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.32-33-generic_2.6.32-33.71_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@aeroplane:~#&lt;/code&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
