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? >>> >> >>

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 automatical

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 start

Re: [DNG] vdev status update: eventfs

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

Re: [DNG] vdev status update: eventfs

dear Jude, On Mon, 21 Sep 2015, Jude Nelson wrote: >I'm going to migrate my production machine to using eventfs with >libudev-compat this weekend.  Once I'm satisfied that it works as >expected, I'll begin packaging all of vdev's components for Devuan. >Questions, comments, and f

Re: [DNG] vdev status update: eventfs

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? /scooby On 2015-09-22 04:44, Jude Nelson wrote: Hey everyone, I promise, I'm not dead :)  I've been working on vdev off and on over the past

[DNG] vdev status update: eventfs

Hey everyone, I promise, I'm not dead :) I've been working on vdev off and on over the past couple months as time permitted, but I haven't had anything interesting to report here (mostly bug fixes, which are tracked on the project's Github [1]). This past week I've been able to spend more time o

Re: [DNG] vdev status update: performance, bugfixes, and udev events

__ From: shraptor<mailto:shrap...@bahnhof.se> Sent: ‎7/‎7/‎2015 10:41 AM To: dng@lists.dyne.org<mailto:dng@lists.dyne.org> Subject: Re: [DNG] vdev status update: performance, bugfixes, and udev events On 2015-07-07 17:45, Jude Nelson wrote: > Hey everyone, >

Re: [DNG] vdev status update: performance, bugfixes, and udev events

On 2015-07-07 21:39, ibid...@gmail.com wrote: On Tue, Jul 07, 2015 at 07:40:51PM +0200, shraptor wrote: On 2015-07-07 17:45, Jude Nelson wrote: >Hey everyone, > >I have the latest news for vdev: > >* [EXPERIMENTAL] Vdevd now has actions and helpers that will cause it >to generate and propagate d

Re: [DNG] vdev status update: performance, bugfixes, and udev events

On Tue, Jul 07, 2015 at 07:40:51PM +0200, shraptor wrote: > On 2015-07-07 17:45, Jude Nelson wrote: > >Hey everyone, > > > >I have the latest news for vdev: > > > >* [EXPERIMENTAL] Vdevd now has actions and helpers that will cause it > >to generate and propagate device events to libudev-compat clie

Re: [DNG] vdev status update: performance, bugfixes, and udev events

On 2015-07-07 17:45, Jude Nelson wrote: Hey everyone, I have the latest news for vdev: * [EXPERIMENTAL] Vdevd now has actions and helpers that will cause it to generate and propagate device events to libudev-compat clients.  Libudev-compat clients should receive hotplug events as they would hav

[DNG] vdev status update: performance, bugfixes, and udev events

Hey everyone, I have the latest news for vdev: * [EXPERIMENTAL] Vdevd now has actions and helpers that will cause it to generate and propagate device events to libudev-compat clients. Libudev-compat clients should receive hotplug events as they would have with libudev, and they should be able to

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

Hi Isaac, On Mon, Jun 29, 2015 at 10:12 AM, Isaac Dunham wrote: > On Fri, Jun 26, 2015 at 04:40:33PM +0200, Didier Kryn wrote: > > Le 25/06/2015 07:04, Jude Nelson a écrit : > > > In time, it will also work the busybox tools, but I am still working > on > > >getting busybox's blkid to work here

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

On Fri, Jun 26, 2015 at 04:40:33PM +0200, Didier Kryn wrote: > Le 25/06/2015 07:04, Jude Nelson a écrit : > > In time, it will also work the busybox tools, but I am still working on > >getting busybox's blkid to work here (specifically, we need the "-p" flag > >to work in order to get low-level pa

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

Hi Didier, On Fri, Jun 26, 2015 at 10:40 AM, Didier Kryn wrote: > Le 25/06/2015 07:04, Jude Nelson a écrit : > >> In time, it will also work the busybox tools, but I am still working on >> getting busybox's blkid to work here (specifically, we need the "-p" flag >> to work in order to get low-

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

Le 25/06/2015 07:04, Jude Nelson a écrit : In time, it will also work the busybox tools, but I am still working on getting busybox's blkid to work here (specifically, we need the "-p" flag to work in order to get low-level partition table information and filesystem metadata). Cheers Jud

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

Thank you very much! On 2015-06-25 02:04, Jude Nelson wrote: Hey everyone, After a longer-than-expected development cycle, I have the latest news for vdev. The TL;DR is that vdev has gained enough infrastructure to generate the information that normally gets put in /run/udev. This is importan

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

On Thu, Jun 25, 2015 at 01:04:24AM -0400, Jude Nelson wrote: > Hey everyone, > > After a longer-than-expected development cycle, I have the latest news for > vdev. > > The TL;DR is that vdev has gained enough infrastructure to generate the > information that normally gets put in /run/udev. This

Re: [DNG] [Dng] vdev status update: device properties and udev compatibility

On 25/06/15 17:04, Jude Nelson wrote: Hey everyone, After a longer-than-expected development cycle, I have the latest news for vdev. The TL;DR is that vdev has gained enough infrastructure to generate the information that normally gets put in /run/udev. This is important for most libudev clien

[DNG] [Dng] vdev status update: device properties and udev compatibility

Hey everyone, After a longer-than-expected development cycle, I have the latest news for vdev. The TL;DR is that vdev has gained enough infrastructure to generate the information that normally gets put in /run/udev. This is important for most libudev clients, because this information gets used t

Re: [Dng] vdev status update (May 25 2015)

On 27/05/15 19:06, Jude Nelson wrote: Hi Anto, On Wed, May 27, 2015 at 6:19 AM, Anto > wrote: On 25/05/15 18:29, Jude Nelson wrote: Hey everyone, I have the latest news for vdev: . . Thoughts and feedback to the above w

Re: [Dng] vdev status update (May 25 2015)

Hi Anto, On Wed, May 27, 2015 at 6:19 AM, Anto wrote: > > > On 25/05/15 18:29, Jude Nelson wrote: > >> Hey everyone, >> >> I have the latest news for vdev: >> >> . > > . > >> Thoughts and feedback to the above welcome :) >> -Jude >> >> > Thanks a lot Jude for all your efforts. > > Since you pu

Re: [Dng] vdev status update (May 25 2015)

On 25/05/15 18:29, Jude Nelson wrote: Hey everyone, I have the latest news for vdev: . . Thoughts and feedback to the above welcome :) -Jude Thanks a lot Jude for all your efforts. Since you put a big fat warning "**CURRENTLY BROKEN. DO NOT ATTEMPT. WE ARE MIGRATING TO .DEB PACKAGES

Re: [Dng] vdev status update (May 25 2015)

Great news, Jude! Keep up the good work :D El 2015-05-25 12:29, Jude Nelson: Hey everyone, I have the latest news for vdev: ... Thoughts and feedback to the above welcome :) -Jude -- Saludos cordiales, Ángel Ramírez Isea. Usuario de Devuan y Canaima GNU / Linux # 460737. Coordinador Gene

Re: [Dng] vdev status update (May 25 2015)

Le 26/05/2015 12:23, Didier Kryn a écrit : Le 25/05/2015 20:50, Jude Nelson a écrit : Just wondering what happens if process A creates a directory in eventfs, process B makes it its working directory, and then process A dies. Does process B end up with a nonexistent working dir

Re: [Dng] vdev status update (May 25 2015)

On Mon, May 25, 2015 at 12:29:12PM -0400, Jude Nelson wrote: > Hey everyone, > > I have the latest news for vdev: > > * Added support for /dev/snd/by-id symlinks (thanks Jack L. Frost aka > openfbt!) > > * Merged support for static linking vdev, building a libvdev.a archive > file, and building

Re: [Dng] vdev status update (May 25 2015)

Le 25/05/2015 20:50, Jude Nelson a écrit : Just wondering what happens if process A creates a directory in eventfs, process B makes it its working directory, and then process A dies. Does process B end up with a nonexistent working directory? umount won't let me do this. WOul

Re: [Dng] vdev status update (May 25 2015)

Hi Hendrik, On Mon, May 25, 2015 at 2:25 PM, Hendrik Boom wrote: > On Mon, May 25, 2015 at 12:29:12PM -0400, Jude Nelson wrote: > ... > > What I'm working on going is the following: > > * fork runfs to create eventfs, a RAM-backed userspace filesystem that > > looks and smells like tmpfs, but is

Re: [Dng] vdev status update (May 25 2015)

On Mon, May 25, 2015 at 12:29:12PM -0400, Jude Nelson wrote: ... > What I'm working on going is the following: > * fork runfs to create eventfs, a RAM-backed userspace filesystem that > looks and smells like tmpfs, but is designed such that (1) files and > directories share fate with the process th

[Dng] vdev status update (May 25 2015)

Hey everyone, I have the latest news for vdev: * Added support for /dev/snd/by-id symlinks (thanks Jack L. Frost aka openfbt!) * Merged support for static linking vdev, building a libvdev.a archive file, and building vdev with non-GNU libc (thanks Didier Kryn!) * Added support for optionally ru

Re: [Dng] [dng] vdev status update (2015-05-03)

Le 14/05/2015 23:16, shraptor shraptor a écrit : am not a 100% with what toolchain means. did you compile for 32bit or 64bit? Toolchain generally means the stuff necessary to build new programs from source. It includes gcc, binutils, the system libraries, the system headers and the kern

Re: [Dng] [dng] vdev status update (2015-05-03)

dows Phone From: Jude Nelson<mailto:jud...@gmail.com> Sent: ‎5/‎14/‎2015 12:33 AM To: James Powell<mailto:james4...@hotmail.com> Cc: dng@lists.dyne.org<mailto:dng@lists.dyne.org> Subject: Re: [Dng] [dng] vdev status update (2015-05-03) Hi James, On T

Re: [Dng] [dng] vdev status update (2015-05-03)

On 14/05/2015 23:16, shraptor shraptor wrote: I even could try myself, did openssl static with musl a while ago but am not a 100% with what toolchain means. I compile everything statically with musl. OpenSSL is doable; the annoying thing IIRC is the Perl dependency at build-time, and of cours

Re: [Dng] [dng] vdev status update (2015-05-03)

On Thursday, May 14, 2015, Didier Kryn wrote: > > Le 14/05/2015 15:40, shraptor shraptor a écrit : > >> I would be interested in a static Vdev. >> >> Didier could you please give some info >> how this was done especially any gotcha's >> you found? >> > > Hi Shraptor. > > I have been work

Re: [Dng] [dng] vdev status update (2015-05-03)

Hi Steve, On Thu, May 14, 2015 at 11:03 AM, Steve Litt wrote: > On Wed, 13 May 2015 23:24:42 -0400 > Jude Nelson wrote: > > > Hey everyone, > > > > I have the latest news for vdev: > > > > * vdev now creates symlinks for: > > -- /dev/v4l/by-path > > -- /dev/disk/by-partuuid > > -- /dev/disk/by-

Re: [Dng] [dng] vdev status update (2015-05-03)

Le 14/05/2015 15:40, shraptor shraptor a écrit : I would be interested in a static Vdev. Didier could you please give some info how this was done especially any gotcha's you found? Hi Shraptor. I have been working for almost one year, partial time, on building a sysrooted gcc-4.7 b

Re: [Dng] [dng] vdev status update (2015-05-03)

On Wed, 13 May 2015 23:24:42 -0400 Jude Nelson wrote: > Hey everyone, > > I have the latest news for vdev: > > * vdev now creates symlinks for: > -- /dev/v4l/by-path > -- /dev/disk/by-partuuid > -- /dev/disk/by-partlabel Thank you Jude. It's astounding what you've been able to accomplish. >

Re: [Dng] [dng] vdev status update (2015-05-03)

On Thu, 14 May 2015 15:40:59 +0200 shraptor shraptor wrote: > I would be interested in a static Vdev. So would I. I could just slide that right onto my Valentine VM, without compilation and dependencies. Once I get familiar with vdev itself, I could install one with loadable modules. SteveT

Re: [Dng] [dng] vdev status update (2015-05-03)

I would be interested in a static Vdev. Didier could you please give some info how this was done especially any gotcha's you found? On Thursday, May 14, 2015, Jack L. Frost wrote: > On Thu, May 14, 2015 at 03:33:06AM -0400, Jude Nelson wrote: > > I'm not a Slackware or Arch user, but please le

Re: [Dng] [dng] vdev status update (2015-05-03)

On Thu, May 14, 2015 at 03:33:06AM -0400, Jude Nelson wrote: > I'm not a Slackware or Arch user, but please let me know if there's > anything I can do to make packaging easier? I don't want to make things > needlessly difficult :) I've dropped an issue on github about the new Makefiles, yeah :)

Re: [Dng] [dng] vdev status update (2015-05-03)

easier? I don't want to make things needlessly difficult :) -Jude > Sent from my Windows Phone > -- > From: Jude Nelson > Sent: 5/13/2015 8:24 PM > To: dng@lists.dyne.org > Subject: [Dng] [dng] vdev status update (2015-05-03) > > H

Re: [Dng] [dng] vdev status update (2015-05-03)

Windows Phone From: Jude Nelson<mailto:jud...@gmail.com> Sent: ‎5/‎13/‎2015 8:24 PM To: dng@lists.dyne.org<mailto:dng@lists.dyne.org> Subject: [Dng] [dng] vdev status update (2015-05-03) Hey everyone, I have the latest news for vdev: * vdev now crea

[Dng] [dng] vdev status update (2015-05-03)

Hey everyone, I have the latest news for vdev: * vdev now creates symlinks for: -- /dev/v4l/by-path -- /dev/disk/by-partuuid -- /dev/disk/by-partlabel Thank you Scooby for helping me confirm this! * vdev now sets the proper ownership and permissions for: -- /dev/mISDNtimer -- /dev/mwave -- /dev

Re: [Dng] Fwd: [dng] vdev status update

On 20/04/15 06:09, Jude Nelson wrote: That is not my intention when it comes to packaging vdev. Devuan is all about preserving the user's freedom to run the software they want, so the ultimate goal is to make it possible for multiple different device managers to coexist. How about if I w

Re: [Dng] Fwd: [dng] vdev status update

On 20/04/15 06:08, Jude Nelson wrote: Hi Anto, [Snip] I took the picture of my screen, vdev debugging log and dmesg from (initramfs) prompt. The picture is still quite bad from photographic point of view, but I think it is good enough to give you information. Please find them on

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, > > I am confused now about your comment that we can "install any/all device > managers and pick one that gets started at boot-time via the alternatives > system". > > I initially thought that vdev requires udev or any other device managers > to work. But since you added the command to d

Re: [Dng] Fwd: [dng] vdev status update

On 19/04/15 05:56, Jude Nelson wrote: Hi Anto, On Sat, Apr 18, 2015 at 2:19 PM, Anto > wrote: Hello Jude, Sorry for keep sending emails instead of sending them at once. I just thought it will be good to have comparison of the logs with the successful

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, On Sat, Apr 18, 2015 at 2:19 PM, Anto wrote: > On 18/04/15 19:46, Anto wrote: > >> >> Hello Jude, >> >> I have tried a lot other combinations but the problem remains, that is >> the init fails to mount the root partition. >> >> I am not sure why as I can manually mount any disks that ar

Re: [Dng] Fwd: [dng] vdev status update

On 18/04/15 19:46, Anto wrote: Hello Jude, I have tried a lot other combinations but the problem remains, that is the init fails to mount the root partition. I am not sure why as I can manually mount any disks that are available on /dev at (initramfs) prompt. I had to do that in order to be

Re: [Dng] Fwd: [dng] vdev status update

On 18/04/15 12:44, Anto wrote: Hello Jude, I have just tried to boot with vdev's initrd, wheezy init, example's init on /usr/share/initramds-tools, and only /etc/init.d/vdev on /etc/runlevel.conf but the result is the same, i.e. ends up at (initramfs) prompt. I only focus on testing your v

Re: [Dng] Fwd: [dng] vdev status update

On 18/04/15 18:29, Steve Litt wrote: On Sat, 18 Apr 2015 12:44:55 +0200 Anto wrote: Hello Jude, I have just tried to boot with vdev's initrd, wheezy init, example's init on /usr/share/initramds-tools, and only /etc/init.d/vdev on /etc/runlevel.conf but the result is the same, i.e. ends up a

Re: [Dng] Fwd: [dng] vdev status update

On Sat, 18 Apr 2015 12:44:55 +0200 Anto wrote: > Hello Jude, > > I have just tried to boot with vdev's initrd, wheezy init, example's > init on /usr/share/initramds-tools, and only /etc/init.d/vdev on > /etc/runlevel.conf but the result is the same, i.e. ends up at > (initramfs) prompt. I a

Re: [Dng] Fwd: [dng] vdev status update

On 18/04/15 06:08, Jude Nelson wrote: Hi Anto, [snip] 1. compile and install vdev 2. copy vdev's initrd into /boot 3. rename /sbin/init to /sbin/init.novdev 4. copy vdev's init file into /sbin The init program in example/initramfs/init goes into /usr/share/initramfs-tools/

Re: [Dng] Fwd: [dng] vdev status update

On Sat, Apr 18, 2015 at 12:08:54AM -0400, Jude Nelson wrote: [snip] > > I am still using file-rc instead of sysv-rc, but I didn't clean up > > /etc/rc?.d directories. I tried to use sysv-rc, but my mouse and keyboard > > are not being detected when using kernel 3.18.11. They are only being > > dete

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, [snip] > 1. compile and install vdev > 2. copy vdev's initrd into /boot > 3. rename /sbin/init to /sbin/init.novdev 4. copy vdev's init file into /sbin > The init program in example/initramfs/init goes into /usr/share/initramfs-tools/init, not /sbin/init :) The initramfs's init scrip

Re: [Dng] Fwd: [dng] vdev status update

On Fri, Apr 17, 2015 at 08:03:36PM +0200, Anto wrote: > After I pulled your commit from github.com, I have done the following: > > 1. compile and install vdev > 2. copy vdev's initrd into /boot > 3. rename /sbin/init to /sbin/init.novdev > 4. copy vdev's init file into /sbin > 5. manually set the

Re: [Dng] Fwd: [dng] vdev status update

On 17/04/15 06:00, Jude Nelson wrote: Hi Anto, I just committed preliminary support for using vdevd with devtmpfs. vdevd should automatically detect whether or not devtmpfs is mounted on /dev, and nevertheless run device setup scripts (by using its own device metadata tree in /dev/vdev/ to s

Re: [Dng] Fwd: [dng] vdev status update

On 17/04/15 06:00, Jude Nelson wrote: Hi Anto, I just committed preliminary support for using vdevd with devtmpfs.  vdevd should automatically detect whether or not devtmpfs is mounted on /dev, and nevertheless run device setup scripts (by using its own device metadata tree in /dev/vdev/ t

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, I push code to both github and git.devuan.org. Either one works :) Thanks, -Jude On Fri, Apr 17, 2015 at 9:40 AM, Anto wrote: > On 17/04/15 06:00, Jude Nelson wrote: > >> Hi Anto, >> >> I just committed preliminary support for using vdevd with devtmpfs. >> vdevd should automatically

Re: [Dng] Fwd: [dng] vdev status update

On 17/04/15 06:00, Jude Nelson wrote: Hi Anto, I just committed preliminary support for using vdevd with devtmpfs. vdevd should automatically detect whether or not devtmpfs is mounted on /dev, and nevertheless run device setup scripts (by using its own device metadata tree in /dev/vdev/ to s

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, I just committed preliminary support for using vdevd with devtmpfs. vdevd should automatically detect whether or not devtmpfs is mounted on /dev, and nevertheless run device setup scripts (by using its own device metadata tree in /dev/vdev/ to see whether or not the device was actually p

Re: [Dng] Fwd: [dng] vdev status update

On 16/04/15 21:49, Jude Nelson wrote: Hi Anto, Sorry for the late reply; I had been super busy with work over the last 24 hours. Don't worry, Jude. You are not working for anyone or any companies who breath on your neck to complete vdev tomorrow, are you? :) Thanks for sending me the pic

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, Sorry for the late reply; I had been super busy with work over the last 24 hours. On Wed, Apr 15, 2015 at 2:43 PM, Anto wrote: > On 15/04/15 05:20, Jude Nelson wrote: > >> Hi Anto, >> >> >> Don't you want to know my setup? >> >> Yes, eventually :) Â However, I don't want to waste y

Re: [Dng] Fwd: [dng] vdev status update

On 15/04/15 05:20, Jude Nelson wrote: Hi Anto, Don't you want to know my setup? Yes, eventually :) Â However, I don't want to waste your time either, at least until I am more confident that the vdev installation process works correctly. Â Maybe there are some packages required b

Re: [Dng] [dng] vdev status update

cheers to vdev! On Tue, 14 Apr 2015, Jude Nelson wrote: > >I'm using it as the device manager in my copy of the alpha Vagrant image, >and others have tested it locally (but not for booting, AFAIK).* I'm >working on getting it to boot the the qcow2 image, which boots from LVM. FYI an

Re: [Dng] Fwd: [dng] vdev status update

Hi Anto, > > Don't you want to know my setup? Yes, eventually :) However, I don't want to waste your time either, at least until I am more confident that the vdev installation process works correctly. > Maybe there are some packages required by your vdev, but I don't have them > installed on

Re: [Dng] Fwd: [dng] vdev status update

On 14/04/15 22:25, Jude Nelson wrote: Hey Anto, On Tue, Apr 14, 2015 at 3:38 PM, Anto > wrote: Thanks for giving it a try again! I'm going to try to reproduce it on my VM and I'll get back to you (could be a few days, though). Perhaps I was not quite clear o

Re: [Dng] Fwd: [dng] vdev status update

Hey Anto, On Tue, Apr 14, 2015 at 3:38 PM, Anto wrote: > On 14/04/15 21:18, Anto wrote: > >> >> Hello Jude, >> >> I have just done the following: >> >> - remove /etc/vdev >> - |git pull https://github.com/jcnelson/vdev|- remove /etc/vdev >> - make clean >> - compile and install libvdev, vdevd an

Re: [Dng] Fwd: [dng] vdev status update

On 14/04/15 21:18, Anto wrote: Hello Jude, I have just done the following: - remove /etc/vdev - |git pull https://github.com/jcnelson/vdev|- remove /etc/vdev - make clean - compile and install libvdev, vdevd and example (step 1) - for step 2, I need to use root account as otherwise I got the

Re: [Dng] Fwd: [dng] vdev status update

On 14/04/15 20:46, Jude Nelson wrote: It just occurred to me that my reply wasn't CC'ed to the ML. -- Forwarded message -- From: *Jude Nelson* mailto:jud...@gmail.com>> Date: Tue, Apr 14, 2015 at 2:12 PM Subject: Re: [Dng] [dng] vdev status update To:

[Dng] Fwd: [dng] vdev status update

It just occurred to me that my reply wasn't CC'ed to the ML. -- Forwarded message -- From: Jude Nelson Date: Tue, Apr 14, 2015 at 2:12 PM Subject: Re: [Dng] [dng] vdev status update To: Anto Hi Anto, thank you for giving that a try! > I am not sure if at this

Re: [Dng] [dng] vdev status update

On Tue, Apr 14, 2015 at 07:40:41PM +0200, Anto wrote: > On 14/04/15 17:48, Jude Nelson wrote: > >I'm using it as the device manager in my copy of the alpha Vagrant image, > >and others have tested it locally (but not for booting, AFAIK).?? I'm > >working on getting it to boot the the qcow2 image,

Re: [Dng] [dng] vdev status update

On 14/04/15 17:48, Jude Nelson wrote: Hi Anto, Thanks a lot for all your efforts on this. My pleasure :) Â It looks like we are getting closer now, or at least to be able to compile vdev as a deb package. And it seems the only package that needs to be re-compile is initramfs.

Re: [Dng] [dng] vdev status update

Hi Anto, Thanks a lot for all your efforts on this. > My pleasure :) > > It looks like we are getting closer now, or at least to be able to compile > vdev as a deb package. And it seems the only package that needs to be > re-compile is initramfs. Do you think it is reasonable now to start > pac

Re: [Dng] [dng] vdev status update

On 14/04/15 17:11, Jude Nelson wrote: Hey everyone, I didn't have much time to work on vdev this weekend, but I did manage to make the vdev installation process easier. The build process automatically generates the host-specific /etc files for you (i.e. including rules for persistent interfa

[Dng] [dng] vdev status update

Hey everyone, I didn't have much time to work on vdev this weekend, but I did manage to make the vdev installation process easier. The build process automatically generates the host-specific /etc files for you (i.e. including rules for persistent interface names), as well as an initramfs with vde

Re: [Dng] [dng] vdev status update

Hi Isaac, On Wed, Apr 8, 2015 at 7:04 PM, Isaac Dunham wrote: > On Tue, Apr 07, 2015 at 05:22:55PM -0400, Jude Nelson wrote: > > > > > "report every kind of device, since it listens to the kernel's > driver > > > core > > > > > (i.e. libudev learns about network interfaces, buses, power > suppli

Re: [Dng] [dng] vdev status update

On Tue, Apr 07, 2015 at 05:22:55PM -0400, Jude Nelson wrote: > > > > "report every kind of device, since it listens to the kernel's driver > > core > > > > (i.e. libudev learns about network interfaces, buses, power supplies, > > > > etc.--stuff for which there are no device files" > > > > Currentl

Re: [Dng] [dng] vdev status update

Hi Isaac, [snip] > > > > libsysdev is meant to help clients pull information from sysfs. I don't > > think it is supposed to help clients run privileged ioctls (Isaac, please > > correct me if I'm wrong!). > > Not at present. > It basically maps a device to a sysfs directory and possibly gets a

Re: [Dng] [dng] vdev status update

On Tue, Apr 07, 2015 at 02:04:36PM -0400, Jude Nelson wrote: > Hi Scooby, > > >> My tentative solution is to require the device manager (whatever it > >> happens to be) to take one extra step in addition to adding/removing device > >> files: record driver core uevents in a well-defined location in

Re: [Dng] [dng] vdev status update

On Tue 07 April 2015 14:04:36 Jude Nelson wrote: > Over in systemd-land, I'm pretty sure the plan going forward is to replace > netlink with kdbus to do the same task. me starts throwing up a little :-o But yes, sounds plausible /j signature.asc Description: This is a digitally signed message pa

Re: [Dng] [dng] vdev status update

Hi Scooby, [Snip] > > >> However, this has proven to be a somewhat challenging problem, for a >> couple reasons. First, inotify(2) does not work on pseudo-filesystems like >> sysfs or devtmpfs, so we can't just watch /sys for changes, and we can't >> use devtmpfs for /dev. This means that syste

Re: [Dng] [dng] vdev status update

Scooby, John Carline, lepoitr, and others (who wish to remain anonymous) > have been sending me logs filesystem listings from running vdev locally. I > very much appreciate it--it helped me discover and fix bugs relating to > persistent paths for disk devices, seeding /dev with initial device file

[Dng] [dng] vdev status update

Hey everyone, Scooby, John Carline, lepoitr, and others (who wish to remain anonymous) have been sending me logs filesystem listings from running vdev locally. I very much appreciate it--it helped me discover and fix bugs relating to persistent paths for disk devices, seeding /dev with initial de

Re: [Dng] [dng] vdev status update

>Given the fraction of replies you got so far devoted to the puppy >(100%) and to the technical content (0%), I suspect this community's >hearts are in the right place. >-- hendrik ^ +1 Linux O'Beardly @LinuxOBeardly http://o.beard.ly linux.obear...@gmail.com On Tue, Mar 31, 2015 at 11:45 AM, H

Re: [Dng] [dng] vdev status update

On Tue, Mar 31, 2015 at 11:44:25AM -0400, Jude Nelson wrote: > Thankfully, the puppy should be fine :) She only ate a few capsules, and > we caught her just after the fact, so we were able to get her proper > treatment before the toxicity could set in. We get to take her home from > the vet eithe

Re: [Dng] [dng] vdev status update

Thankfully, the puppy should be fine :) She only ate a few capsules, and we caught her just after the fact, so we were able to get her proper treatment before the toxicity could set in. We get to take her home from the vet either tonight or tomorrow. -Jude On Tue, Mar 31, 2015 at 3:15 AM, Archa

Re: [Dng] [dng] vdev status update

Well how are the puppies? Hey everyone, I don't have as much to report this week as I usually do, since I spent half my weekend dealing with a pet medical emergency (TL;DR: ibuprofen is toxic to puppies, and puppies can chew through child-proof lids). I am happy to report that I was able to extra

Re: [Dng] [dng] vdev status update

How is the puppy?!? On 31 March 2015 at 06:20, Jude Nelson wrote: > Hey everyone, > > I don't have as much to report this week as I usually do, since I spent > half my weekend dealing with a pet medical emergency (TL;DR: ibuprofen is > toxic to puppies, and puppies can chew through child-proof l

[Dng] [dng] vdev status update

Hey everyone, I don't have as much to report this week as I usually do, since I spent half my weekend dealing with a pet medical emergency (TL;DR: ibuprofen is toxic to puppies, and puppies can chew through child-proof lids). I am happy to report that I was able to extract the code for libudev 21

Re: [Dng] [dng] vdev status update and milestone

On Wed 25 March 2015 22:26:02 KatolaZ wrote: > PID1 *cannot* segfault, or we > are just back to the dark days of BSODs. Fullstop. Funny enough my system continued to sprt of work, just creating a bazillion of zombie processes - among them 2 of systemd, iirc systemd-logind and session- foo - and a

Re: [Dng] [dng] vdev status update and milestone

> > If something goes wrong somewhere and X11 segfaults (which I think does > not happen more than once in a few decades, at least with the stable version > of Xorg), then we might complain and make a fuss, but in the end is not that > big deal. Having systemd as PID 1 segfaulting is a completely

Re: [Dng] [dng] vdev status update and milestone

On Wed, Mar 25, 2015 at 04:31:47PM -0500, T.J. Duchene wrote: > KatolaZ, > > > [T.J. ] What I said was: " It should be important to note that a segfault > can be caused by any number of things, that can be unrelated to systemd > itself. I do grant you that systemd has its share of undesirables

Re: [Dng] [dng] vdev status update and milestone

Defaults are not necessarily caused by glibc itself Defaults = Segfaults. Don't you just hate autocorrect? T.J. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [Dng] [dng] vdev status update and milestone

KatolaZ, [T.J. ] What I said was: " It should be important to note that a segfault can be caused by any number of things, that can be unrelated to systemd itself. I do grant you that systemd has its share of undesirables, but it could be exposing a flaw in the lower libraries as well. A lot

Re: [Dng] [dng] vdev status update and milestone

> > Are you for real? > [T.J. ] Just to clear things up. > If so: > > 1) Drepper maintained glibc, not gcc. These are two separate projects. True. I always treat GCC and glibc as somewhat synonymous since they go hand in hand. You can't have one without the other for all intent

Re: [Dng] [dng] vdev status update and milestone

Le 25/03/2015 18:04, Jude Nelson a écrit : > 3) I don't think this is a great place for unsubstantiated attacks on Ulrich Drepper or on Ulrich Drepper's leadership of glibc. Ulrich Drepper's bad attitude is cited as one of the main reasons Debian switched from glibc to eglibc. Source: http:/

Re: [Dng] [dng] vdev status update and milestone

> 3) I don't think this is a great place for unsubstantiated attacks on Ulrich Drepper or on Ulrich Drepper's leadership of glibc. Ulrich Drepper's bad attitude is cited as one of the main reasons Debian switched from glibc to eglibc. Source: http://blog.aurel32.net/47. -Jude On Wed, Mar 25, 20

Re: [Dng] [dng] vdev status update and milestone

On Wed, 25 Mar 2015, T.J. Duchene wrote: For some, it does have to do with the GPL, but for many it has to do with the fact that GCC is a mess. One of the previous maintainers, Ulrich Drepper, was famous for ignoring bug reports. Are you for real? If so: 1) Drepper maintained glibc, not gcc

Re: [Dng] [dng] vdev status update and milestone

On Wed, Mar 25, 2015 at 11:30:05AM -0500, T.J. Duchene wrote: [cut] > > [T.J. ] It should be important to note that a segfault can be caused by any > number of things, that can be unrelated to systemd itself. I do grant you > that systemd has its share of undesirables, but it could be exposing

  1   2   >