Re: [DNG] vdev status update: eventfs
@shraptor > So how to get eventfs going with vdev. > ./eventfs /run/udev > or where should eventfs be mounted? > Eventfs mounting will not be handled by vdev, right? Vdev won't set up eventfs. I'll ship a sysv init script with it that will mount it automatically (probably shortly after init starts, since libudev-compat programs will need it relatively early in the boot process). I was planning on having it mounted on /run/events, in order to make it available as a generic IPC system for other programs to use for their own purposes. Eventfs isn't specific to vdev; I'm hoping to use it as a partial alternative to dbus. I'm open to alternative mount points, though. @jaromil > Amazing news. noone here doubts you are continuing to build up on the > solid foundations you laid, I am sure vdev will become a relevant > component for many mission-critical GNU/Linux system installations. > Please do not hesitate to ask for anything you need in terms of > infrastructure and funding we can contribute from our donation pot. Thank you for your generous offer! I think I'm fine for now insofar as development infrastructure, but one thing that will be particularly tricky is creating the packaging scripts needed to replace udev automatically, but without rendering the host unbootable if something goes wrong. Thanks, Jude On Tue, Sep 22, 2015 at 6:20 AM, vmlinux wrote: > Great news! Thank you for all your efforts! > > On September 21, 2015 9:44:12 PM CDT, Jude Nelson > wrote: > > ::I'm pleased to announce the availability of eventfs > > -- > Sent from a Mobile device. > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev status update: eventfs
On 2015-09-23 17:14, Jude Nelson wrote: @shraptor So how to get eventfs going with vdev. ./eventfs /run/udev or where should eventfs be mounted? Eventfs mounting will not be handled by vdev, right? Vdev won't set up eventfs. I'll ship a sysv init script with it that will mount it automatically (probably shortly after init starts, since libudev-compat programs will need it relatively early in the boot process). Is it a hard dependency on eventfs? Or will some functionality work without eventfs? Is it the same data as was made availible in /run/udev before?? I was planning on having it mounted on /run/events, in order to make it available as a generic IPC system for other programs to use for their own purposes. Eventfs isn't specific to vdev; I'm hoping to use it as a partial alternative to dbus. I'm open to alternative mount points, though. @jaromil Amazing news. noone here doubts you are continuing to build up on the solid foundations you laid, I am sure vdev will become a relevant component for many mission-critical GNU/Linux system installations. Please do not hesitate to ask for anything you need in terms of infrastructure and funding we can contribute from our donation pot. Thank you for your generous offer! I think I'm fine for now insofar as development infrastructure, but one thing that will be particularly tricky is creating the packaging scripts needed to replace udev automatically, but without rendering the host unbootable if something goes wrong. Thanks, Jude On Tue, Sep 22, 2015 at 6:20 AM, vmlinux wrote: Great news! Thank you for all your efforts! On September 21, 2015 9:44:12 PM CDT, Jude Nelson wrote: ::I'm pleased to announce the availability of eventfs -- Sent from a Mobile device. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
They are ready, but it is a test: http://gnuinos.org/netman/ I think something goes wrong, because if i run netman in the command line i get the following message: $ netman TApplication.HandleException Executable not found: "/usr/lib/netman/bin/backend " Stack trace: $005B6822 $00461464 $00461FD7 $0045EB7D $00447342 $0042E3C1 $0060BC44 $00449460 $0061976D $0060909A $00608FC0 $0044D5E8 $006075D8 $00626042 $00622398 $00446EAA $0044BE82 and an applet saying: Executable not found: "/usr/lib/netman/bin/backend ". Press OK to ignore and risk data corruption. Press Cancel to kill the program. Building the packages, i get something like this: Target OS: Linux for i386 Compiling netman.lpr Compiling mainform.pas Compiling backend.pas backend.pas(98,47) Hint: Local variable "s" does not seem to be initialized backend.pas(152,3) Note: Local variable "i" not used backend.pas(211,30) Hint: Local variable "s" does not seem to be initialized backend.pas(238,30) Hint: Local variable "s" does not seem to be initialized backend.pas(261,30) Hint: Local variable "s" does not seem to be initialized backend.pas(271,31) Hint: Local variable "s" does not seem to be initialized backend.pas(343,47) Hint: Local variable "Buffer" does not seem to be initialized backend.pas(307,5) Note: Local variable "aline" not used backend.pas(380,10) Warning: Function result does not seem to be set backend.pas(488,3) Note: Local variable "equalPos" not used backend.pas(27,63) Hint: Unit "BaseUnix" not used in backend Compiling formeditconnectprops.pas Compiling detailed_info.pas detailed_info.pas(36,28) Hint: Parameter "Sender" not used formeditconnectprops.pas(51,40) Hint: Parameter "Sender" not used formeditconnectprops.pas(52,24) Hint: Parameter "Sender" not used formeditconnectprops.pas(53,24) Hint: Parameter "Sender" not used formeditconnectprops.pas(54,42) Hint: Parameter "Sender" not used formeditconnectprops.pas(54,59) Hint: Parameter "User" not used formeditconnectprops.pas(55,27) Hint: Parameter "Sender" not used formeditconnectprops.pas(46,29) Hint: Parameter "Sender" not used formeditconnectprops.pas(111,3) Note: Local variable "s" not used formeditconnectprops.pas(47,32) Hint: Parameter "Sender" not used formeditconnectprops.pas(122,3) Note: Local variable "i" not used formeditconnectprops.pas(48,28) Hint: Parameter "Sender" not used formeditconnectprops.pas(49,35) Hint: Parameter "Sender" not used formeditconnectprops.pas(50,28) Hint: Parameter "Sender" not used mainform.pas(60,27) Hint: Parameter "Sender" not used mainform.pas(61,26) Hint: Parameter "Sender" not used mainform.pas(62,24) Hint: Parameter "Sender" not used mainform.pas(63,30) Hint: Parameter "Sender" not used mainform.pas(64,36) Hint: Parameter "Sender" not used mainform.pas(167,24) Hint: Mixing signed expressions and longwords gives a 64bit result mainform.pas(65,27) Hint: Parameter "Sender" not used mainform.pas(215,34) Hint: Local variable "pw" does not seem to be initialized mainform.pas(58,28) Hint: Parameter "Sender" not used mainform.pas(259,45) Hint: Local variable "Buffer" does not seem to be initialized mainform.pas(228,13) Note: Local variable "s" not used mainform.pas(59,36) Hint: Parameter "Sender" not used mainform.pas(299,10) Note: Local variable "pw" not used mainform.pas(56,30) Hint: Parameter "Sender" not used mainform.pas(327,10) Note: Local variable "backend_text" not used mainform.pas(327,24) Note: Local variable "prev_caption" not used mainform.pas(55,31) Hint: Parameter "Sender" not used mainform.pas(54,35) Hint: Parameter "Sender" not used mainform.pas(57,34) Hint: Parameter "Sender" not used mainform.pas(30,29) Hint: Unit "ComCtrls" not used in mainform Compiling resource /tmp/buildd/netman-0.1.0-c296e06/lib/i386-linux/netman.or Linking netman ... ... Sender is a parameter used to send signals, something similar to the SIGNAL/SLOTS system in Qt. Anyway, the proccess ends successfully. Cheers, Aitor. > On 21/09/2015, tilt! wrote: >> > Hi Edward, >> > >> > congratulations on wrapping this up! >> > >> > However, attempting to build "netman" from branch "master" at >> > >> > https://git.devuan.org/edbarx/netman.git >> > >> > i get the following errors: >> > >> > * directory ./backend_src/obj missing >> > * directory ./bin missing >> > * link-time error: >> > >> > backend_src/src/backend.c:248: >> >undefined reference to `autoWirelessScanPlus' >> > >> > Also, wasn't there a Debian packaging effort? Can it be downloaded >> > somewhere? >> > >> > Best regards, >> > T. >> > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
Hi Aitor, Sender is the originating object sending initiating the event. For example, let us consider Button: TButton. The latter's OnClick event can be used to call method: ButtonOnClick(Sender: TObject); Sender points at Button. So, inside the event handler, the cast TButton(Sender) can be used to operate directly on the calling object. However, Sender need not be used and it is normal practice in Lazarus/Delphi code not to use it. Regarding the following exeption, this is caused because "/usr/lib/netman/bin/backend " was not found and the exception was forwarded to the TApplication object. TApplication.HandleException Executable not found: "/usr/lib/netman/bin/backend " I think, the error is simply an extra space at the end of: backend=/usr/lib/netman/bin/backend Edit the file /etc/netman.conf and see what happens. If you are not using /etc/netman.conf, something else is causing the error, but I doubt this is what is happening. Also, as a test, try to remove the --auto-conn parameter and check whether netman loads. If it loads, it would corroborate my conclusion that the cause is an extra space at the end of the line mentioned above. Edward On 23/09/2015, aitor_czr wrote: > They are ready, but it is a test: > > http://gnuinos.org/netman/ > > I think something goes wrong, because if i run netman in the command > line i get the following message: > > $ netman > TApplication.HandleException Executable not found: > "/usr/lib/netman/bin/backend " > Stack trace: > $005B6822 > $00461464 > $00461FD7 > $0045EB7D > $00447342 > $0042E3C1 > $0060BC44 > $00449460 > $0061976D > $0060909A > $00608FC0 > $0044D5E8 > $006075D8 > $00626042 > $00622398 > $00446EAA > $0044BE82 > > and an applet saying: > > Executable not found: "/usr/lib/netman/bin/backend ". > Press OK to ignore and risk data corruption. > Press Cancel to kill the program. > > > > Building the packages, i get something like this: > > Target OS: Linux for i386 > Compiling netman.lpr > Compiling mainform.pas > Compiling backend.pas > backend.pas(98,47) Hint: Local variable "s" does not seem to be initialized > backend.pas(152,3) Note: Local variable "i" not used > backend.pas(211,30) Hint: Local variable "s" does not seem to be > initialized > backend.pas(238,30) Hint: Local variable "s" does not seem to be > initialized > backend.pas(261,30) Hint: Local variable "s" does not seem to be > initialized > backend.pas(271,31) Hint: Local variable "s" does not seem to be > initialized > backend.pas(343,47) Hint: Local variable "Buffer" does not seem to be > initialized > backend.pas(307,5) Note: Local variable "aline" not used > backend.pas(380,10) Warning: Function result does not seem to be set > backend.pas(488,3) Note: Local variable "equalPos" not used > backend.pas(27,63) Hint: Unit "BaseUnix" not used in backend > Compiling formeditconnectprops.pas > Compiling detailed_info.pas > detailed_info.pas(36,28) Hint: Parameter "Sender" not used > formeditconnectprops.pas(51,40) Hint: Parameter "Sender" not used > formeditconnectprops.pas(52,24) Hint: Parameter "Sender" not used > formeditconnectprops.pas(53,24) Hint: Parameter "Sender" not used > formeditconnectprops.pas(54,42) Hint: Parameter "Sender" not used > formeditconnectprops.pas(54,59) Hint: Parameter "User" not used > formeditconnectprops.pas(55,27) Hint: Parameter "Sender" not used > formeditconnectprops.pas(46,29) Hint: Parameter "Sender" not used > formeditconnectprops.pas(111,3) Note: Local variable "s" not used > formeditconnectprops.pas(47,32) Hint: Parameter "Sender" not used > formeditconnectprops.pas(122,3) Note: Local variable "i" not used > formeditconnectprops.pas(48,28) Hint: Parameter "Sender" not used > formeditconnectprops.pas(49,35) Hint: Parameter "Sender" not used > formeditconnectprops.pas(50,28) Hint: Parameter "Sender" not used > mainform.pas(60,27) Hint: Parameter "Sender" not used > mainform.pas(61,26) Hint: Parameter "Sender" not used > mainform.pas(62,24) Hint: Parameter "Sender" not used > mainform.pas(63,30) Hint: Parameter "Sender" not used > mainform.pas(64,36) Hint: Parameter "Sender" not used > mainform.pas(167,24) Hint: Mixing signed expressions and longwords gives > a 64bit result > mainform.pas(65,27) Hint: Parameter "Sender" not used > mainform.pas(215,34) Hint: Local variable "pw" does not seem to be > initialized > mainform.pas(58,28) Hint: Parameter "Sender" not used > mainform.pas(259,45) Hint: Local variable "Buffer" does not seem to be > initialized > mainform.pas(228,13) Note: Local variable "s" not used > mainform.pas(59,36) Hint: Parameter "Sender" not used > mainform.pas(299,10) Note: Local variable "pw" not used > mainform.pas(56,30) Hint: Parameter "Sender" not used > mainform.pas(327,10) Note: Local variable "backend_text" not used > mainform.pas(327,24) Note: L
Re: [DNG] What can I do after netman?
Hi Tilt, I was referring to a branch into the netman project in Git, including three branches: 1.- Upstream branch 2.- Debian branch 3.- Pristine-tar branch Being a branch in Git, the name is not confusing. See here: https://gitlab.com/aitor_cz/linux-libre/tree/gbp-master Aitor. On 07/04/21 23:21, aitor_czr wrote: > Good idea :-) > > On 22/09/15 11:20, tilt! wrote: >> On 04/07/2021 10:54 PM, aitor_czr wrote: >>> gpg-netman (git-buildpackage) >> >> People will think it's related to "gpg", which it isn't. >> >> I would like to suggest the name "netman-package" for that project. >> >> Greetings, >> T. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
Hi Aitor, I used your netman .deb packages to install netman on my computer so that I can test it to discover what is the cause of the error. As I told you, it was an extra space in /etc/netman.conf. Remove the space and netman should start without errors. Please, also note that before adding "iface wlan0 inet dhcp" to /etc/network/interfaces, you check whether this line already exists so that it wouldn't be replicated. On my system it was replicated and netman failed due to that. Removing the replication, netman worked. Edward On 23/09/2015, aitor_czr wrote: > Hi Tilt, > > I was referring to a branch into the netman project in Git, including > three branches: > > 1.- Upstream branch > 2.- Debian branch > 3.- Pristine-tar branch > > Being a branch in Git, the name is not confusing. See here: > > https://gitlab.com/aitor_cz/linux-libre/tree/gbp-master > > Aitor. > > On 07/04/21 23:21, aitor_czr wrote: >> Good idea :-) >> >> On 22/09/15 11:20, tilt! wrote: >>> On 04/07/2021 10:54 PM, aitor_czr wrote: gpg-netman (git-buildpackage) >>> >>> People will think it's related to "gpg", which it isn't. >>> >>> I would like to suggest the name "netman-package" for that project. >>> >>> Greetings, >>> T. > > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev status update: eventfs
Hi shraptor, On Wed, Sep 23, 2015 at 1:30 PM, shraptor wrote: > On 2015-09-23 17:14, Jude Nelson wrote: > >> @shraptor >> >>> So how to get eventfs going with vdev. >>> ./eventfs /run/udev >>> or where should eventfs be mounted? >>> Eventfs mounting will not be handled by vdev, right? >>> >> >> Vdev won't set up eventfs. I'll ship a sysv init script with it that >> will mount it automatically (probably shortly after init starts, since >> libudev-compat programs will need it relatively early in the boot >> process). >> > > Is it a hard dependency on eventfs? > Vdev does not need eventfs. Libudev-compat benefits from using it, but does not need it for correct operation. It's a soft dependency. Or will some functionality work without eventfs? > Yes--it will remain possible to use libudev-compat without eventfs. > > Is it the same data as was made availible in /run/udev before?? > No, eventfs will handle the contents of /dev/metadata/udev/events and /dev/events. If you look in /dev/metadata/udev/events, you'll see that libudev-compat processes will have created a bunch of directories there--one for each struct udev_monitor--into which vdev's udev-compat.sh helper writes device events. Currently, there is no straightforward and automatic way to clean this directory out, but doing so is nevertheless necessary since the directories for a process's struct udev_monitor instances will persist after the process dies (I've written a script to clean the dead directories out periodically, but it's not perfect). By having libudev-compat clients write to eventfs, we can ensure that these directories are automatically removed after the process that created them dies. -Jude > > > >> I was planning on having it mounted on /run/events, in order to make >> it available as a generic IPC system for other programs to use for >> their own purposes. Eventfs isn't specific to vdev; I'm hoping to >> use it as a partial alternative to dbus. I'm open to alternative >> mount points, though. >> >> @jaromil >> >>> Amazing news. noone here doubts you are continuing to build up on >>> >> the >> >>> solid foundations you laid, I am sure vdev will become a relevant >>> component for many mission-critical GNU/Linux system installations. >>> >> >> Please do not hesitate to ask for anything you need in terms of >>> infrastructure and funding we can contribute from our donation pot. >>> >> >> Thank you for your generous offer! I think I'm fine for now insofar >> as development infrastructure, but one thing that will be particularly >> tricky is creating the packaging scripts needed to replace udev >> automatically, but without rendering the host unbootable if something >> goes wrong. >> >> Thanks, >> Jude >> >> On Tue, Sep 22, 2015 at 6:20 AM, vmlinux wrote: >> >> Great news! Thank you for all your efforts! >>> >>> On September 21, 2015 9:44:12 PM CDT, Jude Nelson >>> wrote: >>> >>> ::I'm pleased to announce the availability of eventfs >>> >>> -- >>> Sent from a Mobile device. >>> >> >> >> ___ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >> > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
My bad, thanks for explaining - perfectly fine of course. Best regards, T. Am 23.09.2015 um 20:57 schrieb aitor_czr: Hi Tilt, I was referring to a branch into the netman project in Git, including three branches: 1.- Upstream branch 2.- Debian branch 3.- Pristine-tar branch Being a branch in Git, the name is not confusing. See here: https://gitlab.com/aitor_cz/linux-libre/tree/gbp-master Aitor. On 07/04/21 23:21, aitor_czr wrote: Good idea :-) On 22/09/15 11:20, tilt! wrote: On 04/07/2021 10:54 PM, aitor_czr wrote: gpg-netman (git-buildpackage) People will think it's related to "gpg", which it isn't. I would like to suggest the name "netman-package" for that project. Greetings, T. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
Thanks Edward, i will apply the changes :-) Aitor. On 23/09/15 21:26, Edward Bartolo wrote: > Hi Aitor, > > I used your netman .deb packages to install netman on my computer so > that I can test it to discover what is the cause of the error. > > As I told you, it was an extra space in /etc/netman.conf. Remove the > space and netman should start without errors. > > Please, also note that before adding "iface wlan0 inet dhcp" to > /etc/network/interfaces, you check whether this line already exists so > that it wouldn't be replicated. On my system it was replicated and > netman failed due to that. Removing the replication, netman worked. > > Edward > > On 23/09/2015, aitor_czr wrote: >> > Hi Tilt, >> > >> > I was referring to a branch into the netman project in Git, including >> > three branches: >> > >> > 1.- Upstream branch >> > 2.- Debian branch >> > 3.- Pristine-tar branch >> > >> > Being a branch in Git, the name is not confusing. See here: >> > >> > https://gitlab.com/aitor_cz/linux-libre/tree/gbp-master >> > >> > Aitor. >> > >> > On 07/04/21 23:21, aitor_czr wrote: >>> >> Good idea :-) >>> >> >>> >> On 22/09/15 11:20, tilt! wrote: >>> On 04/07/2021 10:54 PM, aitor_czr wrote: > gpg-netman (git-buildpackage) >>> >>> People will think it's related to "gpg", which it isn't. >>> >>> I would like to suggest the name "netman-package" for that project. >>> >>> Greetings, >>> T. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [announce] s6-rc, a s6-based service manager for Unix systems
if you can confirm the plan of releasing s6-rc within september
I confirm it.
And, lo and behold, I'm on schedule for once.
s6-rc-0.0.1.0 is out.
s6-rc is a service manager for Unix systems, running on top of
a s6 supervision tree. It manages the live state of the machine,
defined by a set of services, by bringing those services up or
down as ordered by the user.
It handles long-lived processes, a.k.a. "longruns", ensuring they're
supervised by the s6 tree. It also handles one-time initialization
scripts, a.k.a. "oneshots", running them in a reproducible environment
without needing the usual sanitizer boilerplate.
It manages dependencies between services, no matter whether they are
oneshots or longruns; it can intertwine oneshot starts and longrun
starts, or oneshot stops and longrun stops. When changing the machine
state, it always ensures the consistency of the dependency graph.
Services can be grouped in collections named "bundles", for easier
manipulation. Bundles are like runlevels, but more powerful and
flexible.
s6-rc allows an arbitrary number of longrun services to be pipelined.
s6, and other supervision suites, can maintain a pipe between a
producer and a consumer ("logger"), so the producer or the consumer
can restart without breaking the pipe and losing any data; s6-rc
extends this idea to an arbitrary chain of producers piping their
data into consumers that themselves pipe their data into...
s6-rc features the shortest run-time code path of any service manager
to this day: this includes systemd, sysv-rc, and OpenRC.
http://skarnet.org/software/s6-rc/
git://git.skarnet.org/s6-rc
Enjoy,
Bug-reports welcome.
Please send your reports and suggestions to the
skaw...@list.skarnet.org mailing-list. (You can subscribe by sending
a mail to skaware-subscr...@list.skarnet.org.) That is where s6-rc
is discussed, even if we can of course talk about a possible use in
Devuan here. Thanks!
--
Laurent
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What can I do after netman?
Hi Aitor, fsmithred found that /etc/network/interfaces should not contain partially commented lines. Please make sure comments are whole lines. Edward On 23/09/2015, tilt! wrote: > My bad, thanks for explaining - perfectly fine of course. > > Best regards, > T. > > Am 23.09.2015 um 20:57 schrieb aitor_czr: >> Hi Tilt, >> >> I was referring to a branch into the netman project in Git, including >> three branches: >> >> 1.- Upstream branch >> 2.- Debian branch >> 3.- Pristine-tar branch >> >> Being a branch in Git, the name is not confusing. See here: >> >> https://gitlab.com/aitor_cz/linux-libre/tree/gbp-master >> >> Aitor. >> >> On 07/04/21 23:21, aitor_czr wrote: >>> Good idea :-) >>> >>> On 22/09/15 11:20, tilt! wrote: On 04/07/2021 10:54 PM, aitor_czr wrote: > gpg-netman (git-buildpackage) People will think it's related to "gpg", which it isn't. I would like to suggest the name "netman-package" for that project. Greetings, T. > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
