On Wed, Feb 11, 2015 at 04:54:09PM +0800, Jean-Christophe PLAGNIOL-VILLARD wrote: > > > On Feb 11, 2015, at 4:35 PM, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote: > > > > On Wed, Feb 11, 2015 at 03:26:46PM +0800, Bo Shen wrote: > >> Hi J, > >> > >> On 02/11/2015 01:06 PM, Jean-Christophe PLAGNIOL-VILLARD wrote: > >>> Hi, > >>> > >>> as state before I use the atmel board for bootp everyday as the defaultenv-2 does not support > >>> this Nack until it’s fixed > >> > >> Do you mean the defaultenv-2 doesn't support the bootp feature or do > >> you mean let Doug to keep the default boot from net? > >> > >>> I did send patch for this in the past but they did not hit the mainline > >> > >> Can you point us this? Thanks. > > > > He meant this patch: > > > > http://lists.infradead.org/pipermail/barebox/2012-September/thread.html#9304 > > > > Reading this discussion again I still have mostly the same opinion: > > an /env/boot/* script should be simple, it should be adjustable. > > > > We should resolve this now. > > > > So Jean-Christophe, What you want is to boot your board with > > informations provided by the dhcp server. Looking again at your patch > > back then the following should do it: > > > > /env/boot/bootp: > > > > | #!/bin/sh > > | > > | path="/mnt/tftp" > > | > > | ifup eth0 > > | > > | # Set variables based on information provided by the dhcp request > > | nfsroot="${global.dhcp.rootpath}" > > | global.bootm.image="${path}/${global.dhcp.bootfile}" > > | global.bootm.oftree="${path}/${global.dhcp.oftree_file}” > > this is not possible unfortunately > > As if you use symlink the nfs will not work > it was work on defaultenv as it’s use the nfs commande and not FS > The nfs command handle symlink; Let me recap: On the host you have some directory exported as NFS. It contains a link to some other position: /export/somelink -> /some/other/file Now if I mount /export on barebox 'somelink' points to /some/other/file, a path that doesn't exist in barebox, some the file cannot be read. The NFS command implementation now mounts '/some/other' from the NFS server and reads 'file' from that location. This is really a misfeature is something that we shouldn't support at all. Can't you just make your link a relative one inside the exported directory? That works just fine and as expected. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
