> Which... makes sbrk() implementation a bit tricky. I was suggesting that sbrk simply returned a single, perhaps preallocated, block in the first call and fail in subsequent calls.
