May 2016 - Dev - lists.clearlinux.org

by Abraham Arce

Great, thank you. On Fri, May 20, 2016, 7:35 PM Victor Rodriguez <vm.rod25(a)gmail.com> wrote: > Done , will be in the next external release > > Regards > > Victor Rodriguez > > > On Mon, May 16, 2016 at 6:44 PM, Abraham Arce <xe1gyq(a)gmail.com> wrote: > > Great, thanks Jim, Victor. > > > > > > On Mon, May 16, 2016, 6:41 PM Victor Rodriguez <vm.rod25(a)gmail.com> > wrote: > >> > >> Sure Jim > >> > >> I will sync with Avraham on this > >> > >> Thanks for the support > >> > >> Regards > >> > >> Victor Rodriguez > >> > >> On May 16, 2016 6:16 PM, "Chamings, James E" <jim.chamings(a)intel.com> > >> wrote: > >>> > >>> Hi, > >>> > >>> > >>> > >>> The overall goal of bundles is to provide a collective functional > >>> capability. So really, the example of message-broker-rabbitmq is not > ideal > >>> in this case; it was mostly included that way as a part of the > openstack > >>> deployment in ClearLinux and really should have just been called > >>> ‘message-broker’ or even ‘openstack-message-broker’. > >>> > >>> > >>> > >>> For this one, since mosquitto is relatively unique to iot, I would > prefer > >>> to see it included in the ‘iot’ bundle directly, as part of that > functional > >>> technology. Your point about wanting to run a server standalone is > >>> well-taken, however, so may I suggest ‘iot-message-broker’ as a new > bundle, > >>> that includes mosquitto/mqtt, and that is then included as you have > >>> suggested in ‘iot’. > >>> > >>> > >>> > >>> Having a generic bundle of message brokers would not be particularly > >>> useful, since very very few people would ever want to have both > running in > >>> the same place. > >>> > >>> > >>> > >>> Summary: > >>> > >>> 1) New bundle: ‘iot-message-broker’, contents ‘mosquitto’. > >>> > >>> 2) Add ‘include(iot-message-broker)’ to ‘iot’ bundle. > >>> > >>> > >>> > >>> [ Victor, if there’s no issue with this layout, feel free to do it up > and > >>> merge it… ] > >>> > >>> > >>> > >>> Cheers, > >>> > >>> Jim Chamings > >>> > >>> > >>> > >>> > >>> > >>> From: Dev <dev-bounces(a)lists.clearlinux.org> on behalf of Abraham Arce > >>> <xe1gyq(a)gmail.com> > >>> Date: Monday, May 16, 2016 at 8:35 AM > >>> To: Victor Rodriguez <vm.rod25(a)gmail.com> > >>> Cc: "dev(a)lists.clearlinux.org" <dev(a)lists.clearlinux.org> > >>> Subject: Re: [Dev] Bundle Mqtt Broker > >>> > >>> > >>> > >>> Arjan, Victor, > >>> > >>> Thanks for your quick response and comments... > >>> > >>> > >>> First, the reason for my request is we are going to use Clear Linux as > a > >>> Learning Platform for Cloud as part of "The IoT Learning Initiative" > >>> https://theiotlearninginitiative.gitbooks.io/master/content/ > >>> https://twitter.com/IoTLearningInit > >>> > >>> Second, by looking at the List of Bundles we have a couple which looks > >>> related: > >>> > >>> > >>> Bundle message-broker-rabbitmq > >>> > >>> > https://github.com/clearlinux/clr-bundles/blob/master/bundles/message-broke… > >>> > >>> Bundle iot > >>> https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot > >>> > >>> I don't think neither iot bundle nor lamp-basic are the right place to > >>> include Mosquitto Mqtt Broker, I might want only to have Clear Linux > server > >>> work as a messaging broker alone. If we want to follow a convention to > what > >>> Victor Morales maintains with rabbitmq, then we could probably call it > >>> "message-broker-mosquitto" > >>> > >>> > >>> They are part of "Messaging Protocols" / "Message Brokers" / > >>> "Connectivity Protocol" and since IoT is having a big impact on them, > some > >>> people called them "IoT Protocols". > >>> Should we start creating a bundle with some of the previous names to > >>> group them? how about "message-brokers" since we are dealing with > specific > >>> application and not the protocol and once we have this new bundle we > can > >>> make iot to "include(message-brokers)" bundle? > >>> > >>> We can start with Mosquitto for now and add other protocols as required > >>> in future, in summary the proposal is: > >>> > >>> message-broker-mosquitto New Bundle > >>> > >>> + mosquitto > >>> > >>> > >>> > >>> message-brokers New Bundle > >>> + include(message-broker-mosquitto) > >>> + include(message-broker-rabbitmq) > >>> > >>> iot Modified Bundle > >>> ... > >>> + include(message-brokers) > >>> > >>> > >>> > >>> Please let me know your comments... > >>> > >>> > >>> > >>> Best Regards > >>> > >>> Abraham > >>> > >>> > >>> > >>> On Mon, May 16, 2016 at 8:27 AM, Victor Rodriguez <vm.rod25(a)gmail.com> > >>> wrote: > >>> > >>> Hi > >>> > >>> As far as I can see mosquito provides a lightweight method of > >>> carrying out messaging using a publish/subscribe model for the IoT > >>> devices. > >>> > >>> So Clear Linux might have an IoT bundle; however, in my opinion, it > >>> might not be the best place for it. We might need to put this in a > >>> server bundle , like LAMP ( just saying one ) . But sure a bundle > >>> from the server point of view with more protocols that the industry > >>> uses to communicate IoT devices. > >>> > >>> Abraham , do you know if there is more of these protocols that might > >>> be worth to include . Would be nice to have a bundle that supports the > >>> most used IoT communication protocols. > >>> > >>> Best regards > >>> > >>> Victor Rodriguez > >>> > >>> > >>> > >>> > >>> On Mon, May 16, 2016 at 8:00 AM, Arjan van de Ven < > arjan(a)linux.intel.com> > >>> wrote: > >>> > On 5/15/2016 10:37 PM, Abraham Arce wrote: > >>> >> > >>> >> Hi Clear Linux Team, > >>> >> > >>> >> How possible is it you can integrate Mosquitto Mqtt Broker as part > of > >>> >> a > >>> >> bundle? > >>> >> Thanks! > >>> >> > >>> >> http://mosquitto.org/download/ > >>> >> > >>> > > >>> > since bundles are use/functionality based.... for us to know where to > >>> > put > >>> > it.... > >>> > > >>> > How would you use this component ? > >>> > >>> > _______________________________________________ > >>> > Dev mailing list > >>> > Dev(a)lists.clearlinux.org > >>> > https://lists.clearlinux.org/mailman/listinfo/dev > >>> > >>> >

7 years

1
0
0 0

Re: [Dev] Bundle Mqtt Broker

by Victor Rodriguez

Done , will be in the next external release Regards Victor Rodriguez On Mon, May 16, 2016 at 6:44 PM, Abraham Arce <xe1gyq(a)gmail.com> wrote: > Great, thanks Jim, Victor. > > > On Mon, May 16, 2016, 6:41 PM Victor Rodriguez <vm.rod25(a)gmail.com> wrote: >> >> Sure Jim >> >> I will sync with Avraham on this >> >> Thanks for the support >> >> Regards >> >> Victor Rodriguez >> >> On May 16, 2016 6:16 PM, "Chamings, James E" <jim.chamings(a)intel.com> >> wrote: >>> >>> Hi, >>> >>> >>> >>> The overall goal of bundles is to provide a collective functional >>> capability. So really, the example of message-broker-rabbitmq is not ideal >>> in this case; it was mostly included that way as a part of the openstack >>> deployment in ClearLinux and really should have just been called >>> ‘message-broker’ or even ‘openstack-message-broker’. >>> >>> >>> >>> For this one, since mosquitto is relatively unique to iot, I would prefer >>> to see it included in the ‘iot’ bundle directly, as part of that functional >>> technology. Your point about wanting to run a server standalone is >>> well-taken, however, so may I suggest ‘iot-message-broker’ as a new bundle, >>> that includes mosquitto/mqtt, and that is then included as you have >>> suggested in ‘iot’. >>> >>> >>> >>> Having a generic bundle of message brokers would not be particularly >>> useful, since very very few people would ever want to have both running in >>> the same place. >>> >>> >>> >>> Summary: >>> >>> 1) New bundle: ‘iot-message-broker’, contents ‘mosquitto’. >>> >>> 2) Add ‘include(iot-message-broker)’ to ‘iot’ bundle. >>> >>> >>> >>> [ Victor, if there’s no issue with this layout, feel free to do it up and >>> merge it… ] >>> >>> >>> >>> Cheers, >>> >>> Jim Chamings >>> >>> >>> >>> >>> >>> From: Dev <dev-bounces(a)lists.clearlinux.org> on behalf of Abraham Arce >>> <xe1gyq(a)gmail.com> >>> Date: Monday, May 16, 2016 at 8:35 AM >>> To: Victor Rodriguez <vm.rod25(a)gmail.com> >>> Cc: "dev(a)lists.clearlinux.org" <dev(a)lists.clearlinux.org> >>> Subject: Re: [Dev] Bundle Mqtt Broker >>> >>> >>> >>> Arjan, Victor, >>> >>> Thanks for your quick response and comments... >>> >>> >>> First, the reason for my request is we are going to use Clear Linux as a >>> Learning Platform for Cloud as part of "The IoT Learning Initiative" >>> https://theiotlearninginitiative.gitbooks.io/master/content/ >>> https://twitter.com/IoTLearningInit >>> >>> Second, by looking at the List of Bundles we have a couple which looks >>> related: >>> >>> >>> Bundle message-broker-rabbitmq >>> >>> https://github.com/clearlinux/clr-bundles/blob/master/bundles/message-broke… >>> >>> Bundle iot >>> https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot >>> >>> I don't think neither iot bundle nor lamp-basic are the right place to >>> include Mosquitto Mqtt Broker, I might want only to have Clear Linux server >>> work as a messaging broker alone. If we want to follow a convention to what >>> Victor Morales maintains with rabbitmq, then we could probably call it >>> "message-broker-mosquitto" >>> >>> >>> They are part of "Messaging Protocols" / "Message Brokers" / >>> "Connectivity Protocol" and since IoT is having a big impact on them, some >>> people called them "IoT Protocols". >>> Should we start creating a bundle with some of the previous names to >>> group them? how about "message-brokers" since we are dealing with specific >>> application and not the protocol and once we have this new bundle we can >>> make iot to "include(message-brokers)" bundle? >>> >>> We can start with Mosquitto for now and add other protocols as required >>> in future, in summary the proposal is: >>> >>> message-broker-mosquitto New Bundle >>> >>> + mosquitto >>> >>> >>> >>> message-brokers New Bundle >>> + include(message-broker-mosquitto) >>> + include(message-broker-rabbitmq) >>> >>> iot Modified Bundle >>> ... >>> + include(message-brokers) >>> >>> >>> >>> Please let me know your comments... >>> >>> >>> >>> Best Regards >>> >>> Abraham >>> >>> >>> >>> On Mon, May 16, 2016 at 8:27 AM, Victor Rodriguez <vm.rod25(a)gmail.com> >>> wrote: >>> >>> Hi >>> >>> As far as I can see mosquito provides a lightweight method of >>> carrying out messaging using a publish/subscribe model for the IoT >>> devices. >>> >>> So Clear Linux might have an IoT bundle; however, in my opinion, it >>> might not be the best place for it. We might need to put this in a >>> server bundle , like LAMP ( just saying one ) . But sure a bundle >>> from the server point of view with more protocols that the industry >>> uses to communicate IoT devices. >>> >>> Abraham , do you know if there is more of these protocols that might >>> be worth to include . Would be nice to have a bundle that supports the >>> most used IoT communication protocols. >>> >>> Best regards >>> >>> Victor Rodriguez >>> >>> >>> >>> >>> On Mon, May 16, 2016 at 8:00 AM, Arjan van de Ven <arjan(a)linux.intel.com> >>> wrote: >>> > On 5/15/2016 10:37 PM, Abraham Arce wrote: >>> >> >>> >> Hi Clear Linux Team, >>> >> >>> >> How possible is it you can integrate Mosquitto Mqtt Broker as part of >>> >> a >>> >> bundle? >>> >> Thanks! >>> >> >>> >> http://mosquitto.org/download/ >>> >> >>> > >>> > since bundles are use/functionality based.... for us to know where to >>> > put >>> > it.... >>> > >>> > How would you use this component ? >>> >>> > _______________________________________________ >>> > Dev mailing list >>> > Dev(a)lists.clearlinux.org >>> > https://lists.clearlinux.org/mailman/listinfo/dev >>> >>>

7 years

1
0
0 0

Re: [Dev] Kernel panic when passing noatime in bootargs on bare metal install

by fb.dev.clx

Hi William, Thank you for your answer. I use a bare metal install updated with Clear Linux rev. 8210. Here is the list of the currently installed bundles: ``` ls -1 /usr/share/clear/bundles bootloader dev-utils editors file-utils internet-console-utils kernel-native kvm-host libX11client network-basic network-proxy-client os-core os-core-update os-utils os-utils-gui python-basic sysadmin-basic xfce4-desktop ``` The problem occurs with `noatime` option within the `rootflags=` settings added in any of the three `Clear-linux-native-4.5.4-2XX.conf` files currently present in `/boot/loader/entries/` directory. So here is what I've done so far: 1. edit any of the `Clear-linux-native-4.5.4-2XX.conf` files currently present in `/boot/loader/entries/` directory, only adding the `rootflags=noatime` parameter: ``` options console=tty0 console=ttyS0,115200n8 quiet [...] rootfstype=ext4,btrfs,xfs rootflags=noatime rw [...] ``` 2. reboot 3. this results in a kernel panic: ``` [...] Error: unrecognized mount option 'noatime' or missing value [...] [...] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-> > block(8,3) ``` Regards, -- Ben On Mon, 2016-05-16 at 16:16 -0700, Douglas, William wrote: > Could you include your configuration used to boot the system? Or > maybe > describe what you did to add/change parameters? > > On Mon, May 16, 2016 at 4:04 PM, fb.dev.clx <fb.dev.clx(a)gmail.com> > wrote: > > > > Hi all, > > > > As I wanted to experiment a few kernel parameters on a bare metal > > install, this resulted in a kernel panic with `rootflags=noatime` > > passed in `/boot/loader/entries/Clear-linux-native-*.conf` file: > > > > ``` > > Error: unrecognized mount option 'noatime' or missing value > > [...] > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown- > > block(8,3) > > > > ``` > > > > Any suggestion? > > > > -- Ben > > _______________________________________________ > > Dev mailing list > > Dev(a)lists.clearlinux.org > > https://lists.clearlinux.org/mailman/listinfo/dev

7 years

4
7
0 0

[Dev] Is a reboot required each time the kernel is updated?

by fb.dev.clx

Hi all, With all updates coming with Clear Linux, I was wondering if a reboot is required each time the kernel is updated as a few methods (kpatch, kexec, Ksplice, KernelCare) have emerged lately for loading a whole new Linux kernel from a running system. Any comments? -- Ben

7 years

2
1
0 0

Re: [Dev] Kernel panic when passing noatime in bootargs on bare metal install

by Miguel Bernal Marin

Hi Ian, On 05/16/16 18:10, Ian Frost wrote: > I cant even get Firefox to work:-( > What is your problem with Firefox? -- Regards, Miguel Bernal Marin Open Source Technology Center https://clearlinux.org Intel Corporation

7 years

1
0
0 0

Re: [Dev] Bundle Mqtt Broker

by Abraham Arce

Great, thanks Jim, Victor. On Mon, May 16, 2016, 6:41 PM Victor Rodriguez <vm.rod25(a)gmail.com> wrote: > Sure Jim > > I will sync with Avraham on this > > Thanks for the support > > Regards > > Victor Rodriguez > On May 16, 2016 6:16 PM, "Chamings, James E" <jim.chamings(a)intel.com> > wrote: > >> Hi, >> >> >> >> The overall goal of bundles is to provide a collective functional >> capability. So really, the example of message-broker-rabbitmq is not >> ideal in this case; it was mostly included that way as a part of the >> openstack deployment in ClearLinux and really should have just been called >> ‘message-broker’ or even ‘openstack-message-broker’. >> >> >> >> For this one, since mosquitto is relatively unique to iot, I would prefer >> to see it included in the ‘iot’ bundle directly, as part of that functional >> technology. Your point about wanting to run a server standalone is >> well-taken, however, so may I suggest ‘iot-message-broker’ as a new bundle, >> that includes mosquitto/mqtt, and that is then included as you have >> suggested in ‘iot’. >> >> >> >> Having a generic bundle of message brokers would not be particularly >> useful, since very very few people would ever want to have both running in >> the same place. >> >> >> >> Summary: >> >> 1) New bundle: ‘iot-message-broker’, contents ‘mosquitto’. >> >> 2) Add ‘include(iot-message-broker)’ to ‘iot’ bundle. >> >> >> >> [ Victor, if there’s no issue with this layout, feel free to do it up and >> merge it… ] >> >> >> >> Cheers, >> >> Jim Chamings >> >> >> >> >> >> *From: *Dev <dev-bounces(a)lists.clearlinux.org> on behalf of Abraham Arce >> <xe1gyq(a)gmail.com> >> *Date: *Monday, May 16, 2016 at 8:35 AM >> *To: *Victor Rodriguez <vm.rod25(a)gmail.com> >> *Cc: *"dev(a)lists.clearlinux.org" <dev(a)lists.clearlinux.org> >> *Subject: *Re: [Dev] Bundle Mqtt Broker >> >> >> >> Arjan, Victor, >> >> Thanks for your quick response and comments... >> >> >> First, the reason for my request is we are going to use Clear Linux as a >> Learning Platform for Cloud as part of "The IoT Learning Initiative" >> https://theiotlearninginitiative.gitbooks.io/master/content/ >> https://twitter.com/IoTLearningInit >> >> Second, by looking at the List of Bundles >> <https://clearlinux.org/documentation/bundles_in_clr.html> we have a >> couple which looks related: >> >> >> *Bundle message-broker-rabbitmq >> <https://github.com/clearlinux/clr-bundles/tree/master/bundles/message-broke…>* >> >> https://github.com/clearlinux/clr-bundles/blob/master/bundles/message-broke… >> >> *Bundle iot >> <https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot>* >> https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot >> >> I don't think neither *iot* bundle nor *lamp-basic* are the right place >> to include Mosquitto Mqtt Broker, I might want only to have Clear Linux >> server work as a messaging broker alone. If we want to follow a convention >> to what Victor Morales maintains with rabbitmq, then we could probably call >> it "message-broker-mosquitto" >> >> >> They are part of "Messaging Protocols" / "Message Brokers" / >> "Connectivity Protocol" and since IoT is having a big impact on them, some >> people called them "IoT Protocols". >> Should we start creating a bundle with some of the previous names to >> group them? how about "message-brokers" since we are dealing with specific >> application and not the protocol and once we have this new bundle we can >> make iot to "include(message-brokers)" bundle? >> >> We can start with Mosquitto for now and add other protocols as required >> in future, in summary the proposal is: >> >> message-broker-mosquitto *New Bundle* >> >> + mosquitto >> >> >> >> message-brokers *New Bundle* >> + include(message-broker-mosquitto) >> + include(message-broker-rabbitmq) >> >> iot >> >> * Modified Bundle ... *+ include(message-brokers) >> >> >> >> Please let me know your comments... >> >> >> >> Best Regards >> >> Abraham >> >> >> >> On Mon, May 16, 2016 at 8:27 AM, Victor Rodriguez <vm.rod25(a)gmail.com> >> wrote: >> >> Hi >> >> As far as I can see mosquito provides a lightweight method of >> carrying out messaging using a publish/subscribe model for the IoT >> devices. >> >> So Clear Linux might have an IoT bundle; however, in my opinion, it >> might not be the best place for it. We might need to put this in a >> server bundle , like LAMP ( just saying one ) . But sure a bundle >> from the server point of view with more protocols that the industry >> uses to communicate IoT devices. >> >> Abraham , do you know if there is more of these protocols that might >> be worth to include . Would be nice to have a bundle that supports the >> most used IoT communication protocols. >> >> Best regards >> >> Victor Rodriguez >> >> >> >> >> On Mon, May 16, 2016 at 8:00 AM, Arjan van de Ven <arjan(a)linux.intel.com> >> wrote: >> > On 5/15/2016 10:37 PM, Abraham Arce wrote: >> >> >> >> Hi Clear Linux Team, >> >> >> >> How possible is it you can integrate Mosquitto Mqtt Broker as part of a >> >> bundle? >> >> Thanks! >> >> >> >> http://mosquitto.org/download/ >> >> >> > >> > since bundles are use/functionality based.... for us to know where to >> put >> > it.... >> > >> > How would you use this component ? >> >> > _______________________________________________ >> > Dev mailing list >> > Dev(a)lists.clearlinux.org >> > https://lists.clearlinux.org/mailman/listinfo/dev >> >> >> >

7 years

1
0
0 0

Re: [Dev] Bundle Mqtt Broker

by Chamings

Hi, The overall goal of bundles is to provide a collective functional capability. So really, the example of message-broker-rabbitmq is not ideal in this case; it was mostly included that way as a part of the openstack deployment in ClearLinux and really should have just been called ‘message-broker’ or even ‘openstack-message-broker’. For this one, since mosquitto is relatively unique to iot, I would prefer to see it included in the ‘iot’ bundle directly, as part of that functional technology. Your point about wanting to run a server standalone is well-taken, however, so may I suggest ‘iot-message-broker’ as a new bundle, that includes mosquitto/mqtt, and that is then included as you have suggested in ‘iot’. Having a generic bundle of message brokers would not be particularly useful, since very very few people would ever want to have both running in the same place. Summary: 1) New bundle: ‘iot-message-broker’, contents ‘mosquitto’. 2) Add ‘include(iot-message-broker)’ to ‘iot’ bundle. [ Victor, if there’s no issue with this layout, feel free to do it up and merge it… ] Cheers, Jim Chamings From: Dev <dev-bounces(a)lists.clearlinux.org> on behalf of Abraham Arce <xe1gyq(a)gmail.com> Date: Monday, May 16, 2016 at 8:35 AM To: Victor Rodriguez <vm.rod25(a)gmail.com> Cc: "dev(a)lists.clearlinux.org" <dev(a)lists.clearlinux.org> Subject: Re: [Dev] Bundle Mqtt Broker Arjan, Victor, Thanks for your quick response and comments... First, the reason for my request is we are going to use Clear Linux as a Learning Platform for Cloud as part of "The IoT Learning Initiative" https://theiotlearninginitiative.gitbooks.io/master/content/ https://twitter.com/IoTLearningInit Second, by looking at the List of Bundles<https://clearlinux.org/documentation/bundles_in_clr.html> we have a couple which looks related: Bundle message-broker-rabbitmq<https://github.com/clearlinux/clr-bundles/tree/master/bundles/message-broke…> https://github.com/clearlinux/clr-bundles/blob/master/bundles/message-broke… Bundle iot<https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot> https://github.com/clearlinux/clr-bundles/blob/master/bundles/iot I don't think neither iot bundle nor lamp-basic are the right place to include Mosquitto Mqtt Broker, I might want only to have Clear Linux server work as a messaging broker alone. If we want to follow a convention to what Victor Morales maintains with rabbitmq, then we could probably call it "message-broker-mosquitto" They are part of "Messaging Protocols" / "Message Brokers" / "Connectivity Protocol" and since IoT is having a big impact on them, some people called them "IoT Protocols". Should we start creating a bundle with some of the previous names to group them? how about "message-brokers" since we are dealing with specific application and not the protocol and once we have this new bundle we can make iot to "include(message-brokers)" bundle? We can start with Mosquitto for now and add other protocols as required in future, in summary the proposal is: message-broker-mosquitto New Bundle + mosquitto message-brokers New Bundle + include(message-broker-mosquitto) + include(message-broker-rabbitmq) iot Modified Bundle ... + include(message-brokers) Please let me know your comments... Best Regards Abraham On Mon, May 16, 2016 at 8:27 AM, Victor Rodriguez <vm.rod25(a)gmail.com<mailto:vm.rod25(a)gmail.com>> wrote: Hi As far as I can see mosquito provides a lightweight method of carrying out messaging using a publish/subscribe model for the IoT devices. So Clear Linux might have an IoT bundle; however, in my opinion, it might not be the best place for it. We might need to put this in a server bundle , like LAMP ( just saying one ) . But sure a bundle from the server point of view with more protocols that the industry uses to communicate IoT devices. Abraham , do you know if there is more of these protocols that might be worth to include . Would be nice to have a bundle that supports the most used IoT communication protocols. Best regards Victor Rodriguez On Mon, May 16, 2016 at 8:00 AM, Arjan van de Ven <arjan(a)linux.intel.com<mailto:arjan(a)linux.intel.com>> wrote: > On 5/15/2016 10:37 PM, Abraham Arce wrote: >> >> Hi Clear Linux Team, >> >> How possible is it you can integrate Mosquitto Mqtt Broker as part of a >> bundle? >> Thanks! >> >> http://mosquitto.org/download/ >> > > since bundles are use/functionality based.... for us to know where to put > it.... > > How would you use this component ? > _______________________________________________ > Dev mailing list > Dev(a)lists.clearlinux.org<mailto:Dev(a)lists.clearlinux.org> > https://lists.clearlinux.org/mailman/listinfo/dev

7 years

2
1
0 0

[Dev] Kernel panic when passing noatime in bootargs on bare metal install

by fb.dev.clx

Hi all, As I wanted to experiment a few kernel parameters on a bare metal install, this resulted in a kernel panic with `rootflags=noatime` passed in `/boot/loader/entries/Clear-linux-native-*.conf` file: ``` Error: unrecognized mount option 'noatime' or missing value [...] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,3) ``` Any suggestion? -- Ben

7 years

3
2
0 0

[Dev] Custom kernel parameters (boot options) in systemd-boot's entry configuration files

by fb.dev.clx

Hi all, As I wanted to use custom kernel parameters (boot options), I realized that it seems that there is no way to set custom settings that will be integrated in systemd-boot's entry configuration files each time the kernel is updated, is there? -- Ben

7 years

2
1
0 0

[Dev] Clear Linux bare metal install SSD optimization

by fb.dev.clx

Hi all, As I would like to use Clear Linux as my main system on a laptop with 2 SSDs, I was wondering what should be prefered to improve the performance and life span of these SSDs in terms of: - partition scheme (dedicated partition for virtual disk images?) - partitions alignment - filesystem (EXT4, XFS, etc.) - automatic trimming method - mount options (noatime, etc.) - I/O scheduler - swappiness setting - others? Also, is there a Clear Linux way to set all of this settings? Regards, -- FB

7 years

3
11
0 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev May 2016