5 May
2016
5 May
'16
1:19 p.m.
Hi all!
As pointed out in the LiMeCat notes, Chef adds to Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Byyee!
Ilario
10 Jul
10 Jul
5:48 p.m.
On 05/05/2016 03:19 PM, Ilario wrote:
As pointed out in the LiMeCat notes, Chef adds to
Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Hey...
I resurrect this issue I consider very important to address before the
next stable release.
You can find attached the files included by chef in the Libre-Mesh
images (neither present in lime-build nor in lime-packages).
Bye!
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
7:07 p.m.
I haven't been able to build successfully yet using lime-build, I'm
guessing because of this. Also agree that it is an important thing to
address.
I took the liberty of creating an issue on Github,
<https://github.com/libre-mesh/lime-packages/issues/50>. I'm sure
someone else can resolve it faster, but I'll try to look into this later
this week if nobody else has. Sorry, if posting to Github isn't proper
protocol.
marvin
On 07/10/2016 12:48 PM, Ilario Gelmetti wrote:
On 05/05/2016 03:19 PM, Ilario wrote:
As pointed out in the LiMeCat notes, Chef adds to
Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).I
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Hey...
I resurrect this issue I consider very important to address before the
next stable release.
You can find attached the files included by chef in the Libre-Mesh
images (neither present in lime-build nor in lime-packages).
Bye!
Ilario
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev 
7:54 p.m.
Hi.
I was thinking about spending some time trying to modify lime-build to
make it really useful in LibreMesh. I know there are some people which
do not like the way it works. But still I think we need a tool like that
to have a way to produce a very exact firmware version. Chef is cool but
it has another purpose. IMO Chef must use an ImageBuilder generated with
lime-build, so anyone can generate the same set of binaries.
Marvin, what are your problems regarding lime-build?
In relation with these Chef files, I also think we should create a
package with most of them (not all of them are required actually). And
most important, the developers who are creating the Chef images should
fix the issues not only as a Chef ugly patch but also as a lime-packages
ugly patch. Maybe we can call it lime-ugly-patches :)
On 10/07/16 21:07, Marvin Arnold wrote:
I haven't been able to build successfully yet
using lime-build, I'm
guessing because of this. Also agree that it is an important thing to
address.
I took the liberty of creating an issue on Github,
<https://github.com/libre-mesh/lime-packages/issues/50>. I'm sure
someone else can resolve it faster, but I'll try to look into this
later this week if nobody else has. Sorry, if posting to Github isn't
proper protocol.
marvin
On 07/10/2016 12:48 PM, Ilario Gelmetti wrote:
On 05/05/2016 03:19 PM, Ilario wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev As pointed out in the LiMeCat notes, Chef adds to
Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).I
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Hey...
I resurrect this issue I consider very important to address before the
next stable release.
You can find attached the files included by chef in the Libre-Mesh
images (neither present in lime-build nor in lime-packages).
Bye!
Ilario
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev 
11 Jul
11 Jul
12:04 a.m.
On 10/07/16 21:54, p4u wrote:
Hi.
I was thinking about spending some time trying to modify lime-build to
make it really useful in LibreMesh. I know there are some people which
do not like the way it works. But still I think we need a tool like that
to have a way to produce a very exact firmware version. Chef is cool but
it has another purpose. IMO Chef must use an ImageBuilder generated with
lime-build, so anyone can generate the same set of binaries.
I agree, and that's actually the case since 15.04 :)
Marvin, what are your problems regarding lime-build?
In relation with these Chef files, I also think we should create a
package with most of them (not all of them are required actually). And
most important, the developers who are creating the Chef images should
fix the issues not only as a Chef ugly patch but also as a lime-packages
ugly patch. Maybe we can call it lime-ugly-patches :)
Also agree. If I haven't done it yet it's simply because of lack of
focus on this, but i'll +1 any pull request
thanks ilario for all the help!!
gui
On 10/07/16 21:07, Marvin Arnold wrote:
I haven't been able to build successfully
yet using lime-build, I'm
guessing because of this. Also agree that it is an important thing to
address.
I took the liberty of creating an issue on Github,
<https://github.com/libre-mesh/lime-packages/issues/50>. I'm sure
someone else can resolve it faster, but I'll try to look into this
later this week if nobody else has. Sorry, if posting to Github isn't
proper protocol.
marvin
On 07/10/2016 12:48 PM, Ilario Gelmetti wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
On 05/05/2016 03:19 PM, Ilario wrote:
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev As pointed out in the LiMeCat notes, Chef adds to
Libre-Mesh a few scripts.
Some of these are needed for Chef to customize the build, some others
should be included in lime-packages if we want lime-build to produce
images as good as the ones from chef.
For example
/etc/uci-defaults/95_add-sshkeys
/etc/config/lime-defaults
/etc/chef_version
are needed for some of the customization features of chef (but the
lime-defaults file should be up to date with the one in
lime-packages).I
While *in my opinion* these files should be moved from chef to
somewhere in lime-packages:
/usr/sbin/reset_deaf_phys.sh
/etc/uci-defaults/93_enable-reset-deaf-phys
/etc/config/libremap
/etc/uci-defaults/93_ugly-fixes
/etc/uci-defaults/95_reboot-daily
/etc/uci-defaults/95_snmpd
/etc/uci-defaults/95_set-timezone
/etc/uci-defaults/95_set-remote-syslog
Gui, is there some of these files we can skip as won't be useful in
the next stable release?
Hey...
I resurrect this issue I consider very important to address before the
next stable release.
You can find attached the files included by chef in the Libre-Mesh
images (neither present in lime-build nor in lime-packages).
Bye!
Ilario
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
10 Jul
10 Jul
7:59 p.m.
On 07/10/2016 09:07 PM, Marvin Arnold wrote:
I haven't been able to build successfully yet
using lime-build, I'm
guessing because of this. Also agree that it is an important thing to
address.
I don't think it's because of this... Could you start a new topic
describing how lime-build fails and pasting its output?
I just did this today: cloning the lime-build repository, checkout the
develop branch, make T=ar71xx build (I got images with the original
name, amazing, was the renomination "feature" removed?) and the build
process worked (I still have to test the image anyway).
I took the liberty of creating an issue on Github,
<https://github.com/libre-mesh/lime-packages/issues/50>. I'm sure
someone else can resolve it faster, but I'll try to look into this later
this week if nobody else has.
Great!!
I think that we should think which of these files are really needed and
find a good way to include them into lime-system (not in a new package).
Sorry, if posting to Github isn't proper
protocol.
Absolutely no problem! Indeed, thanks!
Ciao,
Ilario
--
Ilario Gelmetti
iochesonome(a)gmail.com
igelmetti(a)iciq.es
ilario.gelmetti(a)estudiants.urv.cat
3085
days inactive
3152
days old
5 comments
5 participants
participants (5)
-
Gui Iribarren -
Ilario -
Ilario Gelmetti
-
Marvin Arnold -
p4u