I don't understand,

My fault. I misunderstood the problem. Basically, I made the same mistake you did.

Starting fresh:

If you wanted to read to EOF, you'd write

while (<STDIN>) {
   print;
}
[download]

You want to read to EOF twice, so you'd write

for (1..2) {
   while (<STDIN>) {
      print;
   }
}
[download]

You don't want to read a line at a time, so

local $/;
for (1..2) {
   while (<STDIN>) {
      print;
   }
}
[download]

Now count the number of times <STDIN> executed: 4.

local $/;

$_ = <STDIN>;  # Returns first chunk
print;

$_ = <STDIN>;  # Returns EOF

$_ = <STDIN>;  # Returns second chunk
print;

$_ = <STDIN>;  # Returns EOF
[download]

In all but the last snippet, you are calling readline (<>) in scalar context. It returns undef on eof (and on error).

readline (like glob and each) needs to signal when it has finished return results when used as an iterator. You're forgetting to absorb this signal.

The simplest solution is to call readline in list context.

local $/;
($_) = <STDIN>;  # Returns first chunk
($_) = <STDIN>;  # Returns second chunk
[download]

Okay, yes, I can see that's what it is doing - the second time it returns EOF.

But I don't understand why then, if I am reading a line at a time, ($/ = \n) I don't have to read twice - once to read the chunk, and once to read the newline.

Also, why doesn't it work in the case when I made $/ local and undefined it in its own namespace, and the other case where I set $/ back to a newline immediately after the read.

I agree, reading it in list context is the simplest way, but I'd like to understand what is going on.