patch to add autoload via NFS
The patch to add autoload via NFS after bootp or dhcp.
If you want to use, please define CONFIG_AUTOLOAD_VIA_NFS in your configuration file.
What do you think about this patch ? (although I don't need autoload so much.)
Best regards.
Masami Komiya @ Tokyo.JP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfs-autoload.patch.gz
Type: application/x-gzip
Size: 318 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040225/3661f84d/attachment.bin
Quoted 7 lines · Masami Komiya
The patch to add autoload via NFS after bootp or dhcp.
If you want to use, please define
CONFIG_AUTOLOAD_VIA_NFSin your configuration file.What do you think about this patch ? (although I don't need autoload so much.)
Hmm. If you do it this way you can't have autoload enabled for both NFS and TFTP! Is that a good thing?
Is there a way the DHCP server can tell the client how to load the file? I.e. to use tftp or nfs or something else? So you can decide based answer from the DHCP server how to load it...
Signature · 1 line
Steven Scholz
Quoted 4 lines · Steven Scholz
Quoted 2 lines · Masami Komiya
The patch to add autoload via NFS after bootp or dhcp.
Quoted 8 lines
Quoted 5 lines
If you want to use, please define
CONFIG_AUTOLOAD_VIA_NFSin your configuration file.What do you think about this patch ? (although I don't need autoload so much.)
Hmm. If you do it this way you can't have autoload enabled for both NFS and TFTP! Is that a good thing?
I want to enable the both. But I didn't have the idea how to decide the protocol TFTP or NFS.
Quoted 3 lines
Is there a way the DHCP server can tell the client how to load the file? I.e. to use tftp or nfs or something else? So you can decide based answer from the DHCP server how to load it...
I can't find out the such keyword in the manual of dhcpd.conf.
Otherwise, to use the new environment variable like "autoload-nfs" or "autoload-protocol" to decide the protocol.
Does anyone have the idea ?
Best regards.
Masami Komiya @ Tokyo.JP
Quoted 11 lines
Quoted 3 lines
Is there a way the DHCP server can tell the client how to load the file? I.e. to use tftp or nfs or something else? So you can decide based answer from the DHCP server how to load it...
I can't find out the such keyword in the manual of dhcpd.conf.
Otherwise, to use the new environment variable like "autoload-nfs" or "autoload-protocol" to decide the protocol.
Does anyone have the idea ?
The idea is already in your mail: Use the existing environment variable autoload like
autoload=n -> no autoload
autoload=y -> tftp (for historical reasons)
autoload=tftp -> use tftp
autoload=nfs -> use NFS
How about that?
Signature · 6 lines
Steven Scholz imc Measurement & Control imc Me?systeme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin 13355 Berlin Germany Deutschland
Quoted 8 lines · Steven Scholz
Quoted 4 lines
Otherwise, to use the new environment variable like "autoload-nfs" or "autoload-protocol" to decide the protocol.
Does anyone have the idea ?
The idea is already in your mail: Use the existing environment variable autoload like
Quoted 6 lines
autoload=n -> no autoload
autoload=y -> tftp (for historical reasons)
autoload=tftp -> use tftp
autoload=nfs -> use NFSHow about that?
Very nice, I agree with you.
I'll wait the other idea for a while before making.
Masami Komiya @ Tokyo.JP
Quoted 7 lines · Steven Scholz
The idea is already in your mail: Use the existing environment variable autoload like
autoload=n -> no autoload
autoload=y -> tftp (for historical reasons)
autoload=tftp -> use tftp
autoload=nfs -> use NFS
nfs-autoload-eval-01.patch follows above.
Another simple idea is (nfs-autoload-eval-02.patch)
if (autoload==n)
no autoload
else if (autoload==N)
use NFS
else
use TFTP
Thank you for your comment.
Best regards.
Masami komiya
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfs-autoload-eval-02.patch.gz
Type: application/x-gzip
Size: 300 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040226/065f85f0/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nfs-autoload-eval-01.patch.gz
Type: application/x-gzip
Size: 507 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040226/065f85f0/attachment-0001.bin
Quoted 9 lines · In message <[email protected]> you wrote:
Another simple idea is (nfs-autoload-eval-02.patch)
if (autoload==n)
no autoload
else if (autoload==N)
use NFS
else
use TFTP
I will apply this patch but modify it to test for autoload==NFS.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Vulcans believe peace should not depend on force. -- Amanda, "Journey to Babel", stardate 3842.3
Quoted 4 lines · Wolfgang Denk
Quoted 2 lines · In message <[email protected]> you wrote:
Another simple idea is (nfs-autoload-eval-02.patch)
Quoted 8 lines
Quoted 6 lines
if (autoload==n)
no autoload
else if (autoload==N)
use NFS
else
use TFTPI will apply this patch but modify it to test for autoload==NFS.
Plase modify and apply as you like.
It's my pleasure!!
Masami Komiya
Quoted 6 lines · In message <[email protected]> you wrote:
Another simple idea is (nfs-autoload-eval-02.patch)
if (autoload==n)
no autoload
else if (autoload==N)
... else if (autoload=="NFS")
Quoted 3 lines
use NFS
else
use TFTP
Added.
Quoted 1 line
Thank you for your comment.
Thanks again for your contributions.
Best regards,
Wolfgang Denk
Signature · 3 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Of course there's no reason for it, it's just our policy.
Quoted 8 lines · In message <[email protected]> you wrote:
The idea is already in your mail: Use the existing environment variable autoload like
autoload=n -> no autoload
autoload=y -> tftp (for historical reasons)
autoload=tftp -> use tftp
autoload=nfs -> use NFS
So far, anything but "n*" will enable TFTP download. We should not break this behaviour. My suggestion is:
autoload=n* => suppress autoload
autoload=NFS => use NFS
anything else => use TFTP
Best regards,
Wolfgang Denk
Signature · 3 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de If you're not part of the solution, you're part of the problem.