Re: EOVERFLOW while accessing /dev/pts/256
On Sep 13, William Lee Irwin III <wli@holomorphy.com> wrote:
>> Reply-To: debian-kernel@lists.debian.org, md@Linux.IT
>> Mail-Followup-To: debian-kernel@lists.debian.org
On Mon, Sep 13, 2004 at 11:02:18AM +0200, Marco d'Itri wrote:
> Sorry, my mutt was misconfigured... Anyway, if you do not want to
> generate or use Mail-Followup-To headers you can just use the
> $followup_to and $honor_followup_to configuration variables.
Might be easier than ripping it out of the source (and considerably
less painful to look at .muttrc's than mutt source itself), thanks.
On Sep 13, William Lee Irwin III <wli@holomorphy.com> wrote:
>> screen(1) wasn't properly compiled with -D_FILE_OFFSET_BITS=64; it
>> wouldn't see -EOVERFLOW for such if it used stat64. The minor < 256
>> check is only used in old_valid_dev(), which in turn is only used in
>> the non-stat64 syscall variants. new_valid_dev() always returns 1.
On Mon, Sep 13, 2004 at 11:02:18AM +0200, Marco d'Itri wrote:
> OK, I recompiled it and it works. I opened a bug against the screen
> package.
On Mon, Sep 13, 2004 at 11:02:18AM +0200, Marco d'Itri wrote:
> What about the old pts numbers not being reused? Is this a bug? Known?
ISTR there being some kind of bogon and/or bad interaction with common
userspace resolved sometime before 2.6.8
-- wli
Reply to: