diff options
| author | Eric Andersen <andersen@codepoet.org> | 2000-06-26 10:45:52 +0000 |
|---|---|---|
| committer | Eric Andersen <andersen@codepoet.org> | 2000-06-26 10:45:52 +0000 |
| commit | 10dc9d4d17e6880bfdfd253716ce72ec1243227f (patch) | |
| tree | f3c2aa6ab3dadf1b4bf710c7957e72faddebd75f /TODO | |
| parent | 8a24a6783af7a0d54b1f2ebcda5b07757bd19c99 (diff) | |
| download | busybox-w32-10dc9d4d17e6880bfdfd253716ce72ec1243227f.tar.gz busybox-w32-10dc9d4d17e6880bfdfd253716ce72ec1243227f.tar.bz2 busybox-w32-10dc9d4d17e6880bfdfd253716ce72ec1243227f.zip | |
Updates to handle Linux 2.4.0 kernels (kludged around the "none" entries in
/proc/mounts, added a hack to make sysinfo work with both old and new kernels).
-Erik
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 23 |
1 files changed, 3 insertions, 20 deletions
| @@ -39,31 +39,14 @@ list discussion): | |||
| 39 | 39 | ||
| 40 | Linux 2.4.x kernels | 40 | Linux 2.4.x kernels |
| 41 | 41 | ||
| 42 | BusyBox 0.45 currently will not work with the Linux 2.4.x kernels. | 42 | BusyBox 0.46 currently will not work with the Linux 2.4.x kernels. |
| 43 | I know of the following problems: | 43 | I know of the following problems: |
| 44 | 44 | ||
| 45 | 1) The sysinfo syscall has changed what it does (binary incompatable), breaking | 45 | 1) BusyBox NFS support is broken with 2.4.x (needs to be adjusted for NFSv3 and |
| 46 | init and free. | ||
| 47 | 2) BusyBox NFS support is broken with 2.4.x (needs to be adjusted for NFSv3 and | ||
| 48 | kernel header changes). | 46 | kernel header changes). |
| 49 | 3) mount,umount,and df are all broken by the "none" entries for fake filesystems | ||
| 50 | such as the shared mem one. Al Viro claims these will be disappearing soon... | ||
| 51 | |||
| 52 | I made a kernel patch that reverts the sysinfo changes | ||
| 53 | http://kernelnotes.org/lnxlists/linux-kernel/lk_0006_01/msg00619.html | ||
| 54 | |||
| 55 | and I have been fighting with Alan Cox to get these changes fixed in a binary | ||
| 56 | compatable way, but Alan has so far not been very receptive. I am planning on | ||
| 57 | appealing to Linus (when he gets back from vacation) and then going with | ||
| 58 | whatever he decides... | ||
| 59 | |||
| 60 | So my thought is, 2.4.x just isn't ready for BusyBox to target it, and even if | ||
| 61 | it was, BusyBox isn't ready yet either. Seems to me like this will not be | ||
| 62 | ready for a while, and we should just not worry about it yet. | ||
| 63 | 47 | ||
| 64 | As long as I have BB_FEATURE_NFSMOUNT turned off, everything compiles cleanly | 48 | As long as I have BB_FEATURE_NFSMOUNT turned off, everything compiles cleanly |
| 65 | for me with linux2.4.0test1-ac22-riel (i.e. I don't see the freeramdisk.c | 49 | for me with linux2.4.0test2. I use Debian potato (gcc 2.95.2, GNU libc 2.1.3). |
| 66 | problem you reported). I use Debian potato (gcc 2.95.2, GNU libc 2.1.3). | ||
| 67 | Of course, as noted above, compiling != working. | 50 | Of course, as noted above, compiling != working. |
| 68 | 51 | ||
| 69 | ----------- | 52 | ----------- |