[U-Boot-Users] NFS TFTP problem

[U-Boot-Users] NFS TFTP problem

[cjjoy1980]

I have enabled nfs booting on ppc based embedded board.  I had placed my
kernel and rootfs in tftp directory, and had set the u-boot enivironment
varialbes as: 
   setenv bootfile /image/kernel 
   setenv root_path /tftpboot/image 

The board was booting with this configuration... 

Now I have placed the kernel image and rootfs in /exports directory and have
set the uboot variables as: 
   setenv bootfile /exports/image/kernel 
   setenv root_path /exports/image 

I am not able to boot the board with the above directory.  I am getting the
error 

       Loading: T 
       TFTP error: 'File not found' (1) 
       Starting again. 

TFTP by default looks for /tftpboot directory.. How can we make the server
to fetch files apart from the default one??

-- 
View this message in context: http://www.nabble.com/NFS-TFTP-problem-tp18843233p18843233.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot-Users] NFS TFTP problem

[Ben Warren]

On Tue, Aug 5, 2008 at 7:24 PM, cjjoy1980 <cjjoy1980@gmail.com> wrote:
>
> I have enabled nfs booting on ppc based embedded board.  I had placed my
> kernel and rootfs in tftp directory, and had set the u-boot enivironment
> varialbes as:
>   setenv bootfile /image/kernel
>   setenv root_path /tftpboot/image
>
> The board was booting with this configuration...
>
> Now I have placed the kernel image and rootfs in /exports directory and have
> set the uboot variables as:
>   setenv bootfile /exports/image/kernel
>   setenv root_path /exports/image
>
> I am not able to boot the board with the above directory.  I am getting the
> error
>
>       Loading: T
>       TFTP error: 'File not found' (1)
>       Starting again.
>
> TFTP by default looks for /tftpboot directory.. How can we make the server
> to fetch files apart from the default one??
>

Your question is completely off-topic and you should put more effort
into figuring out simple problems like this before asking for help.
That said...
Here are three options:
1. Put the files back in /tftpboot
2. Figure out how to configure your TFTP server.  They're usually quite flexible
3. $ ln -s /exports/image /tftpboot/image

regards,
Ben

[U-Boot-Users] NFS TFTP problem

[Hebbar]

Hi,

TFTP Server running on your system needs to be configured when you change
the directory.

If you have installed xinetd, the configuration files are stored in 
/etc/xinetd.d/ folder

edit  /etc/xinetd.d/tftp & change the server_args to pint to new directory

[root @linux]# vi /etc/xinetd.d/tftp
#
# File /etc/xinetd.d/tftp
#
service tftp
{
       protocol        = udp
       socket_type    = dgram
       wait            = yes
       user            = root
       server          = /usr/sbin/in.tftpd
       server_args    = -s /tftpboot
       disable         = no
}


Hope this helps

Regards
Gururaja



-- 
View this message in context: http://www.nabble.com/NFS-TFTP-problem-tp18843233p18845192.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot-Users] NFS TFTP problem

[Jerry Van Baren]

cjjoy1980 wrote:
> I have enabled nfs booting on ppc based embedded board.  I had placed my
> kernel and rootfs in tftp directory, and had set the u-boot enivironment
> varialbes as: 
>    setenv bootfile /image/kernel 
>    setenv root_path /tftpboot/image 
> 
> The board was booting with this configuration... 
> 
> Now I have placed the kernel image and rootfs in /exports directory and have
> set the uboot variables as: 
>    setenv bootfile /exports/image/kernel 
>    setenv root_path /exports/image 
> 
> I am not able to boot the board with the above directory.  I am getting the
> error 
> 
>        Loading: T 
>        TFTP error: 'File not found' (1) 
>        Starting again. 
> 
> TFTP by default looks for /tftpboot directory.. How can we make the server
> to fetch files apart from the default one??

You cannot make the TFTP server fetch files apart from the default one. 
  Furthermore, you don't want to.

TFTP inherently has *NO* concept of security: no authentication - 
*anybody* can read *any* file in the TFTP directory and potentially can 
write any file they want into the TFTP directory.

As a result, TFTP servers are (and should be) severely restrictive of 
what directories they serve files out of and are willing to store files 
into (if configured to allow writing - generally a bad idea).

You can configure your TFTP server to serve the same directory as you 
export via NFS and your TFTP load will start working again.
****THIS IS A VERY, VERY BAD IDEA!****

As pointed out by Ben, you can symlink your image file so that it 
appears in your TFTP directory again - this is the best solution if you 
*must* move your image into the NFS directory.  You need to decide if 
you have a good reason to move your image *out* of your TFTP directory.

Best regards,
gvb