Ollie Lho <[EMAIL PROTECTED]> writes:
> "Eric W. Biederman" wrote:
> >
> > Marty Connor <[EMAIL PROTECTED]> writes:
> >
> > > On 6/21/2001 4:10 AM Eric W. Biederman [EMAIL PROTECTED] wrote:
> > >
> > > >[EMAIL PROTECTED] (Eric W. Biederman) writes:
> > > >> Anyway I'll see if I can get a good patch out in the next couple of
> > > >> days.
> > >
> > > >Make that hours.
> > > >Here is my preliminar patch.
> > >
> > > This is great news! I can't keep up with all the good news lately in
> > > fact. I hope you can make it to LinuxWorld Expo in San Francisco. There
> > > will be an Etherboot booth again, and we will be able to show off some of
> > > the new technology. Ken is going to be there, and Markus and who knows
> > > who else. I hope lots of people stop by to say hello and have fun.
> >
> > I haven't a clue. I haven't made any plans yet. If you want a motherboard
> > for playing with linuxBIOS I'd recommend one based on either the SiS630 or
> > the SiS730 chipset. The chipsets are well supported in linuxBIOS
> > currently, and motherboard based on them should be relatively
> > inexpensive.
> >
>
> Eric,
> Does your code works on SiS630/730 with the internal SiS900
> LAN ?? Can you give me a little description how can I reproduce
> it here. I am still reading those Diskless/Netboot/Etherboot HOWTOs.
> Sorry, the last time I played with remote boot was on Sun SPARC and
> IBM RS6000 workstations 6 years ago back in the university.
O.k.
The code I added simply allows etherboot to work under linuxbios.
It compiles into an ELF image, that I can boot with the elfboot.c
So etherboot should be as simple to use as a linux kernel.
There is SiS900 code in etherboot. I haven't tested it, I don't have
the hardware, but it should work.
If you compile in multiboot support into etherboot right now,
you can use my mkelfImage code in the linuxBIOS cvs tree to create
a bootable kernel image. mknbi might work but I haven't tested it,
and I think it still keeps some bios calls around, which is a show
stopper.
Basically the setup is a dhcp server that gives a node an ip address,
and a file name to download and boot. Plus a tftp server that serves
a file over the network. It takes a little work to setup but it
isn't to hard. The only tricky piece is at the moment it really helps
to have the network booting machine on a seperate subnet from the
company network, otherwise you get clash of the dual dhcp servers.
Eric
