From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: NFS boot - could not open /.tftp_tmp_path
Date: Thu, 09 Aug 2018 13:07:22 +0200 [thread overview]
Message-ID: <6rzhxvhk7p.fsf@pengutronix.de> (raw)
In-Reply-To: <20180809095146.GA26594@ravnborg.org>
Hi Sam,
Sam Ravnborg <sam@ravnborg.org> writes:
> I try to boot my target using NFS - but something does not work.
> I have a server (192.168.86.201) where I have exported
> an nfs mount like this:
> $ sudo exportfs
> /nfsboot/arm9 <world>
> $ cat /etc/exports.d/nfsboot.exports
> /nfsboot/arm9 *(insecure,no_subtree_check,no_root_squash,rw,nohide)
>
> On my barebox target I can then mount the nfs like this:
> barebox: mkdir /mnt
> barebox: /mnt/nfs
> barebox: mount -t nfs 192.168.86.201:/nfsboot/arm9
>
> barebox: mount
> none on / type ramfs
> none on /dev type devfs
> 192.168.86.201:/nfsboot/arm9 on /mnt/nfs type nfs
>
> barebox: ls /mnt/nfs <= shows the file I have on the server
>
> Then when I try to boot from nfs I get the following output:
>
> barebox: boot nfs://192.168.86.201/nfsboot/arm9/
you already have the slash separating the host part of the URL and the
path part, but you missed the slash that is needed at the beginning of
the absolute path:
boot nfs://192.168.86.201//nfsboot/arm9/
(with a two slashes) should hopefully do the trick.
Best regards
Ulrich
> eth0: DHCP client bound to address 192.168.86.20
> T T T T T T T T T T T T T T could not open /.tftp_tmp_path/zImage-at91sam9263ek
>
> When I grep the barebox source I can only find 'tftp_tmp_path' in some
> tftp code.
>
> It looks like it somehow revert back to tftp despite I have specified nfs.
> I hope there is something trivial I do wrong.
>
> Any hints?
>
> Sam
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
--
Pengutronix e.K. | Ulrich Ölmann |
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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-09 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 9:51 Sam Ravnborg
2018-08-09 11:07 ` Ulrich Ölmann [this message]
2018-08-09 11:14 ` Sam Ravnborg
2018-08-09 12:31 ` Ulrich Ölmann
2018-08-10 6:08 ` Sam Ravnborg
2018-08-10 6:26 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6rzhxvhk7p.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox