> > Can we take IP autoconfig out of the kernel?
How big is this thing?
> > You should be able to accomplish the same thing with dhcpcd, bootp,
> > pump, etc.
>
> Some of it you cant do without userspace (eg dhcp). I'd like to lose the
> IP autoconfig code, it doesnt handle some interface types, it can't handle
> some of the common bootp daemon extras and it has some unfunny routing
> interaction wiht the kernel which are not clean (tm).
>
> On the other hand for 2.4 we can only do this if someone has or will do the
> usermode initrd for it and put it up somewhere. Post 2.4 it has-to-go.
> DHCP is the routine system now, we already cant handle it without an initrd
Great. Now instead of just catting my kernel to a floppy and it just
'works', I'll have to make a boot disk with ext2 or minix on it and figure
out what files out of what packages I need just to query a bootp server.
ATM, I don't know how to leave initrd (I never looked)
I understand that DHCP can just change your IP while you're running. No
problem since I haven't been using DHCP (and wouldn't use it for diskless
boxes).
Personally, for diskless machines which boots the kernel directly (no lilo,
no syslinux, etc) this is a good thing. (Or atleast I believe so) I've
never used ip autoconfig using arp except once where I had a digiport server
that would do this but not bootp. Anyway, I atleast hope that bootp
autoconfig isn't removed from the kernel for this reason.
-- Lab tests show that use of micro$oft causes cancer in lab animals- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:22 EST