Messages in this thread |  | | | Date | Sat, 12 Jan 2002 20:38:27 -0500 (EST) | | From | Alexander Viro <> | | Subject | Re: [RFC] klibc requirements, round 2 |
| |
On 12 Jan 2002, Juan Quintela wrote:
> >>>>> "greg" == Greg KH <greg@kroah.com> writes: > > Hi > > greg> To summarize, here's a partial list of the programs people want to run: > greg> - mount
I _really_ doubt it. /init calling mount(2) - sure, but mount(8)? Not really.
> greg> - hotplug > greg> - busybox > greg> - dhcpcd > greg> - image viewer > greg> - mkreiserfs > greg> - partition discovery (currently in the kernel)
Assuming that it moves to userland, which is non-obvious. Going other way (i.e. clean kernel API for parsing _and_ changing partitioning) might be better. Current mechanisms for notifying kernel about partition table changes are really gross.
> greg> - lots of other, existing in kernel code.
nfsroot mounting (socket/sendto/recvfrom/open/close/read/write/malloc/free/ snprintf/memcpy/strlen/mount).
> I still think that fsck at this point will be great. You will > minimize the need to have the kernel special case for fsck the root fs > with respect to the rest of fs.
_Kernel_ has no special-casing of that kind.
- 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/
|  |