[Buildroot] question about /tftpboot

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

Hi all !

I would like my tftp server provides access to another directory (e.g
/var/... param configured with /etc/inetd.conf  with my GNU Debian)

'/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
'make menuconfig'

How do i do ? Many thanks

-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Habib Bouaziz-Viallet a ?crit :
> Hi all !
> 
> I would like my tftp server provides access to another directory (e.g
> /var/... param configured with /etc/inetd.conf  with my GNU Debian)
> 
> '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
> 'make menuconfig'
> 
> How do i do ? Many thanks
> 

There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found 
it broken by the target/linux/Makefile.in.advanced file and I proposed a 
patch in this bug report: http://bugs.uclibc.org/view.php?id=2384

Maybe the situation is better now.
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
> Habib Bouaziz-Viallet a ?crit :
>
> > Hi all !
>  >
>  > I would like my tftp server provides access to another directory (e.g
>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>  >
>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>  > 'make menuconfig'
>  >
>  > How do i do ? Many thanks
>  >
>
>
> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>  it broken by the target/linux/Makefile.in.advanced file and I proposed a
>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
Ok. Did you apply this successfully ? If so how to ?
>
>  Maybe the situation is better now.
Best regards
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Habib Bouaziz-Viallet a ?crit :
> 2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
>> Habib Bouaziz-Viallet a ?crit :
>>
>>> Hi all !
>>  >
>>  > I would like my tftp server provides access to another directory (e.g
>>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>>  >
>>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>>  > 'make menuconfig'
>>  >
>>  > How do i do ? Many thanks
>>  >
>>
>>
>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>>  it broken by the target/linux/Makefile.in.advanced file and I proposed a
>>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
> Ok. Did you apply this successfully ? If so how to ?

The patch was for the version some weeks ago, I don't expect it will 
apply cleanly now. But the change it make to the 
arget/linux/Makefile.in.advanced file are very easy to do by hand. I can 
make a new patch if it will be accepted into the repository.

-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Habib Bouaziz-Viallet a ?crit :
> 2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
>> Habib Bouaziz-Viallet a ?crit :
>>
>>> Hi all !
>>  >
>>  > I would like my tftp server provides access to another directory (e.g
>>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>>  >
>>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>>  > 'make menuconfig'
>>  >
>>  > How do i do ? Many thanks
>>  >
>>
>>
>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>>  it broken by the target/linux/Makefile.in.advanced file and I proposed a
>>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
> Ok. Did you apply this successfully ? If so how to ?

You can apply with the "patch -p0" command like this:

buildroot$ patch -p0 < patch-tftpboot-kernel.diff
patching file target/linux/Makefile.in.advanced
Hunk #1 succeeded at 227 (offset 18 lines).
Hunk #2 succeeded@387 (offset 19 lines).

I have attached an updated patch that don't show "offset lines".

I am interested to know if it work for your case.
-- 
Jean-Christian de Rivaz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-tftpboot-kernel.diff
Type: text/x-patch
Size: 1042 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080321/077472de/attachment.bin 

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Jean-Christian de Rivaz a ?crit :
> Habib Bouaziz-Viallet a ?crit :
>> 2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
>>> Habib Bouaziz-Viallet a ?crit :
>>>
>>>> Hi all !
>>>  >
>>>  > I would like my tftp server provides access to another directory (e.g
>>>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>>>  >
>>>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>>>  > 'make menuconfig'
>>>  >
>>>  > How do i do ? Many thanks
>>>  >
>>>
>>>
>>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>>>  it broken by the target/linux/Makefile.in.advanced file and I 
>>> proposed a
>>>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>> Ok. Did you apply this successfully ? If so how to ?
> 
> You can apply with the "patch -p0" command like this:
> 
> buildroot$ patch -p0 < patch-tftpboot-kernel.diff
> patching file target/linux/Makefile.in.advanced
> Hunk #1 succeeded at 227 (offset 18 lines).
> Hunk #2 succeeded at 387 (offset 19 lines).
> 
> I have attached an updated patch that don't show "offset lines".
> 
> I am interested to know if it work for your case.

Ooops! The attached patch need to be applyed with the -p1 option like this:

buildroot$ patch -p1 < ../buildroot-patch/patch-tftpboot-kernel.diff
patching file target/linux/Makefile.in.advanced

Sorry for the mistake.
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
> Jean-Christian de Rivaz a ?crit :
>
> > Habib Bouaziz-Viallet a ?crit :
>  >> 2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
>  >>> Habib Bouaziz-Viallet a ?crit :
>  >>>
>  >>>> Hi all !
>  >>>  >
>  >>>  > I would like my tftp server provides access to another directory (e.g
>  >>>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>  >>>  >
>  >>>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>  >>>  > 'make menuconfig'
>  >>>  >
>  >>>  > How do i do ? Many thanks
>  >>>  >
>  >>>
>  >>>
>  >>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>  >>>  it broken by the target/linux/Makefile.in.advanced file and I
>  >>> proposed a
>  >>>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>  >> Ok. Did you apply this successfully ? If so how to ?
>  >
>  > You can apply with the "patch -p0" command like this:
>  >
>  > buildroot$ patch -p0 < patch-tftpboot-kernel.diff
>  > patching file target/linux/Makefile.in.advanced
>  > Hunk #1 succeeded at 227 (offset 18 lines).
>  > Hunk #2 succeeded at 387 (offset 19 lines).
>  >
>  > I have attached an updated patch that don't show "offset lines".
>  >
>  > I am interested to know if it work for your case.
>
>
> Ooops! The attached patch need to be applyed with the -p1 option like this:
>
>  buildroot$ patch -p1 < ../buildroot-patch/patch-tftpboot-kernel.diff
>
> patching file target/linux/Makefile.in.advanced
>
>
> Sorry for the mistake.
Ok thanks Jean-Christian i'll give it a try.
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
> Jean-Christian de Rivaz a ?crit :
>
> > Habib Bouaziz-Viallet a ?crit :
>  >> 2008/3/21, Jean-Christian de Rivaz <jc@eclis.ch>:
>  >>> Habib Bouaziz-Viallet a ?crit :
>  >>>
>  >>>> Hi all !
>  >>>  >
>  >>>  > I would like my tftp server provides access to another directory (e.g
>  >>>  > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>  >>>  >
>  >>>  > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>  >>>  > 'make menuconfig'
>  >>>  >
>  >>>  > How do i do ? Many thanks
>  >>>  >
>  >>>
>  >>>
>  >>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found
>  >>>  it broken by the target/linux/Makefile.in.advanced file and I
>  >>> proposed a
>  >>>  patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>  >> Ok. Did you apply this successfully ? If so how to ?
>  >
>  > You can apply with the "patch -p0" command like this:
>  >
>  > buildroot$ patch -p0 < patch-tftpboot-kernel.diff
>  > patching file target/linux/Makefile.in.advanced
>  > Hunk #1 succeeded at 227 (offset 18 lines).
>  > Hunk #2 succeeded at 387 (offset 19 lines).
>  >
>  > I have attached an updated patch that don't show "offset lines".
>  >
>  > I am interested to know if it work for your case.
Oh it does not work for me ... unfortunately. I resolved the pb by a
symbolic link.

Thanks for the topic anyway.

>
>
> Ooops! The attached patch need to be applyed with the -p1 option like this:
>
>  buildroot$ patch -p1 < ../buildroot-patch/patch-tftpboot-kernel.diff
>
> patching file target/linux/Makefile.in.advanced
>
>
> Sorry for the mistake.
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Habib Bouaziz-Viallet a ?crit :

>>  > I am interested to know if it work for your case.
> Oh it does not work for me ... unfortunately. I resolved the pb by a
> symbolic link.

Ok. Can you give me the error message or the configuration to reproduce 
the problem ? I have some motivation to solve this issue.

Thanks anyway for your test.
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
> Habib Bouaziz-Viallet a ?crit :
>
>
> >>  > I am interested to know if it work for your case.
>  > Oh it does not work for me ... unfortunately. I resolved the pb by a
>  > symbolic link.
>
>
> Ok. Can you give me the error message or the configuration to reproduce
>  the problem ? I have some motivation to solve this issue.
As i noticed in my previous post i make a symlink from /tftpboot -->
/home/ ..../buildroot/tftpboot and build process works fine now

habib at mizar:~/PROJETS/PERSO/buildroot$ ls tftpboot/
at91sam9260dfc-dataflashcardboot-2.3.bin        autoscript.loopee!  vmlinux
at91sam9260dfc-u-boot-1.2.0-atmel-20080322.bin  bzImage

So what configuration would you see ? Is it my .config in buildroot root tree ?

>
>  Thanks anyway for your test.
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Habib Bouaziz-Viallet a ?crit :
> 2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
>> Habib Bouaziz-Viallet a ?crit :
>>
>>
>>>>  > I am interested to know if it work for your case.
>>  > Oh it does not work for me ... unfortunately. I resolved the pb by a
>>  > symbolic link.
>>
>>
>> Ok. Can you give me the error message or the configuration to reproduce
>>  the problem ? I have some motivation to solve this issue.
> As i noticed in my previous post i make a symlink from /tftpboot -->
> /home/ ..../buildroot/tftpboot and build process works fine now
> 
> habib at mizar:~/PROJETS/PERSO/buildroot$ ls tftpboot/
> at91sam9260dfc-dataflashcardboot-2.3.bin        autoscript.loopee!  vmlinux
> at91sam9260dfc-u-boot-1.2.0-atmel-20080322.bin  bzImage
> 
> So what configuration would you see ? Is it my .config in buildroot root tree ?

Initially yes, but finally no.

I see now that you use an Atmel target. Atmel target have an other 
symbol used to copy file into the tftpboot directory. I suspect that the 
patch you tryed only solve the tftpboot issue with the kernel, but not 
the issue with the Atmel target. I really don't know the rational for 
having two symbols for the tftpboot directory, this is maybe the result 
of some historic of the Atmel targets. Anyone know ?

I was hoping that you used a target other than Atmel to see if my patch 
was helpful. I am now back to the staring point. Sorry for having lost 
some of your time.

Still, I will be very happy if some maintainers can give to me an guess 
if the BR2_TARGET_ATMEL_COPYTO should be replaced by to BR2_LINUX_COPYTO 
symbol. I am motivated to provide a appropriate patch to make the 
tftpboot directory working correctly if it is not exactly "/tftpboot".

Have a good day,
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
> Habib Bouaziz-Viallet a ?crit :
>  > 2008/3/22, Jean-Christian de Rivaz <jc@eclis.ch>:
>  >> Habib Bouaziz-Viallet a ?crit :
>  >>
>  >>
>  >>>>  > I am interested to know if it work for your case.
>  >>  > Oh it does not work for me ... unfortunately. I resolved the pb by a
>  >>  > symbolic link.
>  >>
>  >>
>  >> Ok. Can you give me the error message or the configuration to reproduce
>  >>  the problem ? I have some motivation to solve this issue.
>  > As i noticed in my previous post i make a symlink from /tftpboot -->
>  > /home/ ..../buildroot/tftpboot and build process works fine now
>  >
>  > habib at mizar:~/PROJETS/PERSO/buildroot$ ls tftpboot/
>  > at91sam9260dfc-dataflashcardboot-2.3.bin        autoscript.loopee!  vmlinux
>  > at91sam9260dfc-u-boot-1.2.0-atmel-20080322.bin  bzImage
>  >
>  > So what configuration would you see ? Is it my .config in buildroot root tree ?
>
>
> Initially yes, but finally no.
>
>  I see now that you use an Atmel target. Atmel target have an other
>  symbol used to copy file into the tftpboot directory. I suspect that the
>  patch you tryed only solve the tftpboot issue with the kernel, but not
>  the issue with the Atmel target. I really don't know the rational for
>  having two symbols for the tftpboot directory, this is maybe the result
>  of some historic of the Atmel targets. Anyone know ?
>
Yes my work is derived from Atmel AT91 Dev Kit but with a VGA
controller from EPSON. I read somewhere that buildroot allows us to
create own board support.

All are going smoothly for the moment (make menuconfig, make
busybox-menuconfig, make linux26-menuconfig ...etc.)


>  I was hoping that you used a target other than Atmel to see if my patch
>  was helpful. I am now back to the staring point. Sorry for having lost
>  some of your time.
>
>  Still, I will be very happy if some maintainers can give to me an guess
>  if the BR2_TARGET_ATMEL_COPYTO should be replaced by to BR2_LINUX_COPYTO
>  symbol. I am motivated to provide a appropriate patch to make the
>  tftpboot directory working correctly if it is not exactly "/tftpboot".
>
>  Have a good day,
>  --
>
> Jean-Christian de Rivaz
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[Ulf Samuelsson]

Habib Bouaziz-Viallet a ?crit :
> Hi all !
> 
> I would like my tftp server provides access to another directory (e.g
> /var/... param configured with /etc/inetd.conf  with my GNU Debian)
> 
> '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
> 'make menuconfig'
> 
> How do i do ? Many thanks
> 

There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found 
it broken by the target/linux/Makefile.in.advanced file and I proposed a 
patch in this bug report: http://bugs.uclibc.org/view.php?id=2384

Maybe the situation is better now.
-- 

The linux kernel should possibly be copied several times, and
you cannot use a single symbol for this.


Best Regards
Ulf Samuelsson

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Ulf Samuelsson a ?crit :
>> 
>> Habib Bouaziz-Viallet a ?crit :
>>> Hi all !
>>>
>>> I would like my tftp server provides access to another directory (e.g
>>> /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>>>
>>> '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
>>> 'make menuconfig'
>>>
>>> How do i do ? Many thanks
>>>
>> 
>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found 
>> it broken by the target/linux/Makefile.in.advanced file and I proposed a 
>> patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>> 
>> Maybe the situation is better now.
 >
 >The linux kernel should possibly be copied several times, and
 >you cannot use a single symbol for this.

Thanks Ulf for your hint, but did you have a more precise example ? I 
observed that only the Atmel targets uses a second symbol 
BR2_TARGET_ATMEL_COPYTO.

I have updated my two proposed patchs 
http://bugs.uclibc.org/view.php?id=2384 and 
http://bugs.uclibc.org/view.php?id=2394 to match the current SVN head. 
There don't change the fact that there is two symbols, there only make 
the COPYTOP symbols possibly work if the tftpboot directory is anything 
other than "/tftpboot" like this is more and more the case on the new 
distributions.

The idea to use only one symbol cam after I see that there is two of 
them for Atmel targets. I still don't see why something would go wrong 
if the BR2_TARGET_ATMEL_COPYTO will be replaced by the BR2_LINUX_COPYTO. 
 From my point of view this remove the confusion for the users to set 
two symbols instead of a single one. I will propose a patch to do that 
only if the first two will be accepted as this one will obviously be 
useless without them.

Best Regards,
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[Ulf Samuelsson]

>>> There is a symbol BR2_LINUX_COPYTO to adjust that. Some time ago I found 
>>> it broken by the target/linux/Makefile.in.advanced file and I proposed a 
>>> patch in this bug report: http://bugs.uclibc.org/view.php?id=2384
>>> 
>>> Maybe the situation is better now.
> >
> >The linux kernel should possibly be copied several times, and
> >you cannot use a single symbol for this.
> 
> Thanks Ulf for your hint, but did you have a more precise example ? I 
> observed that only the Atmel targets uses a second symbol 
> BR2_TARGET_ATMEL_COPYTO.
> 
> I have updated my two proposed patchs 
> http://bugs.uclibc.org/view.php?id=2384 and 
> http://bugs.uclibc.org/view.php?id=2394 to match the current SVN head. 
> There don't change the fact that there is two symbols, there only make 
> the COPYTOP symbols possibly work if the tftpboot directory is anything 
> other than "/tftpboot" like this is more and more the case on the new 
> distributions.
> 
> The idea to use only one symbol cam after I see that there is two of 
> them for Atmel targets. I still don't see why something would go wrong 
> if the BR2_TARGET_ATMEL_COPYTO will be replaced by the BR2_LINUX_COPYTO. 

Not running Linux on my laptop at the moment, so I cannot check the svn
but as I see it, you want to be able to copy the linux image to

1) BINARIES_DIR
2) root file system (option)
3) A place where it is easy to download to the target using tftp,
    which defaults to "/tftpboot".
    It is OK, to make this programmable as long the default is used.
    As an option, we could add a shell symbol "BUILDROOT_TFTP_DIR"
    which overrides the menuconfig.



Best Regards
Ulf Samuelsson

[Buildroot] question about /tftpboot

[Jean-Christian de Rivaz]

Ulf Samuelsson a ?crit :
>> The idea to use only one symbol cam after I see that there is two of 
>> them for Atmel targets. I still don't see why something would go wrong 
>> if the BR2_TARGET_ATMEL_COPYTO will be replaced by the BR2_LINUX_COPYTO. 
> 
> Not running Linux on my laptop at the moment, so I cannot check the svn
> but as I see it, you want to be able to copy the linux image to
> 
> 1) BINARIES_DIR
> 2) root file system (option)
> 3) A place where it is easy to download to the target using tftp,
>     which defaults to "/tftpboot".
>     It is OK, to make this programmable as long the default is used.
>     As an option, we could add a shell symbol "BUILDROOT_TFTP_DIR"
>     which overrides the menuconfig.

Ok, thanks for the explanation.

My two proposed patches only take care of the point number 3 in your 
list. Currently there is two symbols used to copy some file into the 
tftpboot directory: BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO.


a) Each of this symbols cannot be set to anything other than "/tftpboot" 
because the scripts that use them have hard coded "/tftpboot" into them. 
  The 2 patches only fix for this simple problem. Without those patches 
the BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO are actually almost 
useless as modifying them are granted to fail because of the hard coded 
path in the scripts.

Take for example the "target/linux/Makefile.in.advanced" file. It 3 
lines with the path "/tftpboot" hard coded into it. My patch only 
replace those "/tftpboot" by the symbol "$(BR2_LINUX_COPYTO)". Same 
logic apply for the patch that replace the hard coded "/tftpboot" ba the 
symbol "$(BR2_TARGET_ATMEL_COPYTO)" into the files 
"target/device/Atmel/at91bootstrap/at91bootstrap.mk" and 
"target/device/Atmel/u-boot/u-boot.mk".

Did you see anything wrong that prevent those small patches to be applyed ?


b) Yes there is several symbols that are used to copy the linux kernel, 
but only the two symbols BR2_LINUX_COPYTO and BR2_TARGET_ATMEL_COPYTO 
are set by default to copy files into the /tftpboot directory. In my 
understanding there are both used for the exact same purpose: copy some 
files (not only the linux kernel) into the right tftpboot directory 
(possibly not alway "/tftpboot"). As there carry the same semantic, I 
wonder why we need two of them as there will alway have the same value 
to get a working setup. If there are alway the same, why not simply use 
one of them (BR2_LINUX_COPYTO) and replace the second 
(BR2_TARGET_ATMEL_COPYTO) by the first ?

Best Regards,
-- 
Jean-Christian de Rivaz

[Buildroot] question about /tftpboot

[John Voltz]

I think this is done by changing the tftp configuration file in /etc after
it is installed. There might also be something under /etc/inet.d

John

On Fri, Mar 21, 2008 at 1:40 PM, Habib Bouaziz-Viallet <
habib.bouaziz@gmail.com> wrote:

> Hi all !
>
> I would like my tftp server provides access to another directory (e.g
> /var/... param configured with /etc/inetd.conf  with my GNU Debian)
>
> '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
> 'make menuconfig'
>
> How do i do ? Many thanks
>
> --
> M. Bouaziz-Viallet
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080321/f7c4f289/attachment.htm 

[Buildroot] question about /tftpboot

[Habib Bouaziz-Viallet]

2008/3/21, John Voltz <john.voltz@gmail.com>:
> I think this is done by changing the tftp configuration file in /etc after
> it is installed. There might also be something under /etc/inet.d
Hi John !

In fact tftp server is not involved in this issue, the fact is the
'/tftpboot' location choice in make menuconfig did not work, i.e
changing 'tftpboot' by '/var/tftpboot' did not work
>
> John
>
Best regards
>
> On Fri, Mar 21, 2008 at 1:40 PM, Habib Bouaziz-Viallet
> <habib.bouaziz@gmail.com> wrote:
>
> >
> > Hi all !
> >
> > I would like my tftp server provides access to another directory (e.g
> > /var/... param configured with /etc/inetd.conf  with my GNU Debian)
> >
> > '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
> > 'make menuconfig'
> >
> > How do i do ? Many thanks
> >
> > --
> > M. Bouaziz-Viallet
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org
> > http://busybox.net/mailman/listinfo/buildroot
> >
>
>
> _______________________________________________
>  buildroot mailing list
>  buildroot at uclibc.org
>  http://busybox.net/mailman/listinfo/buildroot
>


-- 
M. Bouaziz-Viallet

[Buildroot] question about /tftpboot

[JS]

On Fri, 2008-03-21 at 18:40 +0100, Habib Bouaziz-Viallet wrote:
> I would like my tftp server provides access to another directory (e.g
> /var/... param configured with /etc/inetd.conf  with my GNU Debian)
> 
> '/ tftpboot'. Changing '/ tftpboot' is apparently not possible from
> 'make menuconfig'

I usually symlink /tftpboot to whereever I want.. 

-- 
HiPro Solutions
http://hipro.co.in/