On Wed, 2010-12-01 at 09:21 +0100, Per Sjoholm wrote:
> Hi
> There is also the issue of missing ioctl's for a disk.img

Per: Sorry, I don't understand. Could you explain please?

> What about bypassing the problem?
> We could solve more than one problem at once.
> Support for PXE boot/install https://sourceforge.net/apps/trac/leaf/ticket/3

We should definitely pursue that anyway.

> I like Martins suggestion below.
> 
> What if we create a Leaf application  that can
> * be installed by cdrom, PXE-install  on real HW or using qemu, Virtualbox
>     for Virtual environment we could use a raw disk.img
>     we could connect to existing network. Users would not need a server 
> infrastructure.
> * act as a PXE-server or install a separate system on local hd/flash/ssd
> * Configuration can be saved using a floppy, real or image.
> 
> It should be possible to use latest Leaf 3.1 as a base.
> When 4.0 is released, we update the application.

I guess all the building blocks are there: dnsmasq and tftpd for PXE
booting, wget if we need to transfer files via HTTP.

> 
> /Per
> 
> On 2010-11-30 23:16, Martin Hejl wrote:
> > Hi dMb,
> >
> > Am 30.11.2010 22:51, schrieb e-mail dmb.leaf-devel:
> >> It *should* work but right now we have a problem with
> >> /sbin/fdisk from hdsupp.lrp which I have just confirmed - See
> >> http://sourceforge.net/apps/trac/leaf/ticket/11 :-(
> > Well, if all else fails, you might try booting with Bering uClinc 3.x,
> > using the hdsupp that from that distro to set things up, and then copy
> > the files for Bering uClinc onto the target drive. I'm not sure if it
> > will work, but there's a good chance that syslinux from Bering uClibc
> > 3.x will boot 4.0 as well (just as a workaround for the time being,
> > until the hdsupp package of 4.x is fixed).

Yep, using 3.x should work. I think 4.x still uses the same syslinux
version as 3.x anyway (though a newer one is available).

<snip>

> > I'm not saying it can't be done - I just never managed to get that
> > approach to work reliably. Maybe I simply overlooked something, and it
> > actually works if done correctly.
> >
> > Martin
> >

Martin: Thanks for contributing your insight and experience. PXE booting
is high up on the enhancements list and you have convinced me to work on
that before battling with a dd'able disk image any further. I build my
other systems via PXE so why not BuC too?

One practical challenge is that AFAIK most systems only PXE boot from
the "WAN" NIC, so a bit of cable swapping will be required in order to
boot from a machine on the internal network. Would be nice to avoid
that. Maybe make eth0 the "LAN" NIC and eth1 the "WAN" NIC ?????

dMb


------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to