Yes, that's my thinking too. A DHCP/BOOTP option seems to be the obvious
way, and I'd hate to use non-obvious ways when there is a perfectly good
> The first thing is the kernel: just wrap around printk so as soon as eth0
> is up, you set up a session and start sending packets.
My thinking at the moment is to require kernel IP configuration (either
ip= or RARP/BOOTP/DHCP). It seems to be the only practical way;
otherwise you miss too much at the beginning. However, that mechanism is
already in place, and shouldn't be too hard to piggy-back on.
> I'll do a server to receive these sessions - simple text (no vt100 etc),
> one window per session - and work on the protocol spec. Anyone willing
> to do the client end of things - lilo, grub, kernel, etc??
I'll do PXELINUX, for sure. I'd prefer to do the protocol spec, if you
don't mind -- having done PXELINUX I think I know the kinds of pitfalls
that you run into doing an implementation in firmware or firmware-like
programming (PXELINUX isn't firmware, but it might as well be.)
Doing it in LILO would be extremely difficult, since LILO has no ability
to handle networking, and no reasonable way to graft it on (you need a
driver for networking.) GRUB I can't really comment on.
I might just decide to do the kernel as well.
Hmmm... this sounds like it's turning into a group effort. Would you (or
someone else) like to set up a sourceforge project for this? I would
prefer not to have to deal with that end myself.
-- <firstname.lastname@example.org> at work, <email@example.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://vger.kernel.org/lkml/