Bug#826290: libc6-i686: Neither "$ aptitude show" or "$ apt-cache show" says libc6-i686 is a virtual package

2016-06-03 Thread Kingsley G. Morse Jr.
Package: libc6-i686 Version: 2.22-7 Severity: minor Hey guys, I hope you're well. * What led up to the situation? While installing security patches, aptitude asked if it would be OK to remove libc6-i686, and neither $ apt-cache show libc6-i686 or $ aptitude

Bug#629983: More old files to look for

2011-06-12 Thread Kingsley G. Morse Jr.
If you see A non-dpkg owned copy of the C library was found in /lib. and if I understand this bug correctly, you might want to check if the following files are on your computer lrwxrwxrwx 1 root root 182008-07-10 11:41 /lib/ld-linux.so.1 - ld-linux.so.1.9.11 -rwxr-xr-x 1 root

Bug#189011: A better errno

2003-04-20 Thread Kingsley G. Morse Jr.
On Sun:11:56, GOTO Masanori wrote: all programs check ENOSPC, not ENOINO. This means that you have to change all programs which uses ENOSPC Compatibility is a good point. Thanks. [...] So please consider ENOSPC is something has no more space. I'm OK with that. Here's the big but. BUT,

Bug#189011: libc6: Change ENOSPC 28 to /* No space or inodes left on device */

2003-04-16 Thread Kingsley G. Morse Jr.
, GOTO Masanori wrote: At Mon, 14 Apr 2003 21:33:05 -0700, Kingsley G. Morse Jr. [EMAIL PROTECTED] wrote: On Mon:16:09, Ben Collins wrote: Kingsley wrote: glibc currently returns errno 28, which is defined as No space left on device

Bug#189011: libc6: Change ENOSPC 28 to /* No space or inodes left on device */

2003-04-15 Thread Kingsley G. Morse Jr.
On Mon:16:09, Ben Collins wrote: Kingsley wrote: glibc currently returns errno 28, which is defined as No space left on device and is misleading. It should mention inodes. Inodes are a specific term that does not apply to all cases where ENOSPC is used. What happens if

Bug#45912: Bug 45912: ping, and name resolution in general, hangs

1999-10-08 Thread Kingsley G. Morse Jr.
I fixed a similar bug after upgrading to 2.2.12. Like you, I was using a bogus IP address internally and a real IP address for the rest of the web. In my case, the breakthrough was using tcpdump to diagnose the problem. I think tcpdump may well help you too. For example, you could first run