Messages in this thread | | | From | Jonathan Hudson <> | Subject | Re: Linux 2.4.19pre1-ac1 | Date | Thu, 28 Feb 2002 00:19:04 GMT |
| |
In article <fa.g63p78v.1e7kv8e@ifi.uio.no>, Alan Cox <alan@lxorguk.ukuu.org.uk> writes: >> >> With 19-pre1-ac1 on a reiserfs partition I cannot patch a kernel. Patch >> >> fails with "Invalid cross-device link" or "Out of disk space". >> AF> >> AF> I can reproduce this too on ext2, so this does not seem to be FS related. >> >> Likewise (reiserfs here). Numerous fuzz or outright patch failures >> with 2.4.19-pre1-ac1. AC> AC> See the other mail for the questions - and reply to that too if you can. AC> Right now I've not managed to reproduce it. Do you see the problem on AC> 2.4.19-pre1 (non -ac) [that has the same reiserfs changes in as -ac does]
There were no problems with 2.4.19-pre1, to which I reverted, pulled the full 2.4.18, and patched back up to 2.4.19-pre1-ac2.
Booted into 2.4.19-pre1-ac2.
Patched back down to 2.4.18 and then back up to 2.4.19-pre1-ac2 again, no problems seen.
Rebuilt 2.4.19-pre1-ac2 in 2.4.19-pre1-ac2. Reboot.
Ran the following twice.
for i in $(seq 1 10) do bzcat /net/tw/home/jrh/dl/patch-2.4.19-pre1-ac2.bz2 | patch -p1 -R bzcat /net/tw/home/jrh/dl/patch-2.4.19-pre1.bz2 | patch -p1 -R sleep 1 bzcat /net/tw/home/jrh/dl/patch-2.4.19-pre1.bz2 | patch -p1 bzcat /net/tw/home/jrh/dl/patch-2.4.19-pre1-ac2.bz2 | patch -p1 echo "===========>" Step $i done
No problems seen. ac1 would have not have survived the above, so I'm pretty sure that 2.4.19-pre1-ac2 has fixed the pre1 problems.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |