Hi Ralph, Richard:
On 08/12/2016 03:50 AM, Ralph Ronnquist wrote:
The set up I now have, does the right thing on boot. I think.
Firstly, it loads vdev from initrd during the first stage boot, and then
it exits. A snapshot of /dev taken before the next start shows all
filemod settings to be fi
On 08/13/2016 10:45 AM, aitor_czr wrote:
*vdev-example.postinst*_
#!/bin/sh
set -e
PREFIX=/
if [ $# -gt 1 ]; then
PREFIX=$1
shift 1
fi
update-rc.d -f udev remove
update-rc.d -f udev-finish remove
ln -s /usr/etc/init.d/vdev /etc/init.d/vdev
ln -s /usr/etc/vdev
On 08/13/2016 10:48 AM, aitor_czr wrote:
On 08/13/2016 10:45 AM, aitor_czr wrote:
*vdev-example.postinst*_
#!/bin/sh
set -e
PREFIX=/
if [ $# -gt 1 ]; then
PREFIX=$1
shift 1
fi
update-rc.d -f udev remove
update-rc.d -f udev-finish remove
ln -s /usr/etc/init.
On Fri, 12 Aug 2016 08:03:20 +1000
Ralph Ronnquist wrote:
> Firstly, it loads vdev from initrd during the first stage boot, and
> then it exits. A snapshot of /dev taken before the next start shows
> all filemod settings to be fine.
>
> Secondly it loads vdev anew at the sysvinit startup, and th
On Fri, 12 Aug 2016 09:50:11 +0800
Robert Storey wrote:
> > So, please join the Group Of Three who are testing vdev. Without
> > vdev or any other standalone udev version Devuan is stillborn. This
> > whole vdev beast is much more complicated than a single daemon. We
> > need testing, input, othe
On Thu, 11 Aug 2016 15:01:47 -0400
fsmithred wrote:
> Anyway, I'm going to start with Jude's directions and see if I can
> catch up. Meanwhile, I did do something useful, and I can answer your
> question about eudev - yeah, I tried it, and it seems to work (with
> minimal testing). I used the deb
Hi,
My apololgies for sounding a bit emotional about this issue.
If, up to now, you have "runit" running as pid 1 and managed to
maintain the ability to boot from the kernel commandline using
the sysv-init read on.
The latest update to package 'runit' *wipes* out the 2 binaries
/sbin/runit-init
Hi Richard,
On 08/12/2016 11:28 AM, richard lucassen wrote:
We need a vdev package that depends on an empty systemd-udev package.
All the other packages that depend on systemd-udev will otherwise be
uninstalled.
vdev will provide udev in teh same way as libudev-compat-dev will
provide libud
On 13/08/2016 11:52, aitor_czr wrote:
> [Snip}
>
> Yes, we need testers :)
>
> Best,
>
> Aitor.
Oh yes, I will test it once it hits 'ascii' or
perhaps even the 'unstable' branch. Sorry can't
do better bacause I am just a user with a fairly
good head on its shoulder.
Regards
Fred
__
On 08/13/2016 04:45 AM, aitor_czr wrote:
>
>
> I'm applying changes to the packages. This is my vdev.conf file:
>
> *vdev.conf*_
>
> [vdev-config]
> firmware=/usr/lib/firmware
> acls=/etc/vdev/acls
> actions=/etc/vdev/actions
> helpers=/usr/lib/vdev
> hwdb=/usr/lib/vdev/
On Fri, 12 Aug 2016 06:33:50 -0400
fsmithred wrote:
> > firmware=/usr/lib/firmware
>
> I think firmware should be set to /lib/firmware. That's where my
> firmware is. I have no /usr/lib/firmware.
Yep. I agree. Firmware is AFAIK in /lib/firmware
--
richard lucassen
http://contact.xaq.nl/
_
On Fri, Aug 12, 2016 at 11:17:13AM +0200, richard lucassen wrote:
> We need a vdev package that depends on an empty systemd-udev package.
> All the other packages that depend on systemd-udev will otherwise be
> uninstalled.
Use Provides:. This can nowadays even give a version.
--
An imaginary f
On Sat, 13 Aug 2016 11:52:55 +0200
aitor_czr wrote:
> > We need a vdev package that depends on an empty systemd-udev
> > package. All the other packages that depend on systemd-udev will
> > otherwise be uninstalled.
>
> vdev will provide udev in teh same way as libudev-compat-dev will
> provide
On Fri, 12 Aug 2016 12:54:54 +0200
Adam Borowski wrote:
> On Fri, Aug 12, 2016 at 11:17:13AM +0200, richard lucassen wrote:
> > We need a vdev package that depends on an empty systemd-udev
> > package. All the other packages that depend on systemd-udev will
> > otherwise be uninstalled.
>
> Use
On Sat, Aug 13, 2016 at 3:45 AM, aitor_czr wrote:
>
> Hi Ralph, Richard:
>
-- Snipped (a lot) -
> *vdev-example.postinst*_
>
> #!/bin/sh
>
> set -e
>
> PREFIX=/
>
> if [ $# -gt 1 ]; then
>PREFIX=$1
>shift 1
> fi
>
> update-rc.d -f udev remove
> update-rc
On 12/08/2016 13:43, Tom H wrote:
>> On 12/08/2016 11:49, Tom H wrote:
>>>
>>> Off-list
>>>
>>> Install
>>> runic-init
>>> in order to restore
>>> /sbin/init
>>> and
>>> /sbin/runit
>>
>> Thanks for the suggestion. Unfortunately 'runic-init' it is not in
>> 'ascii' and googling didn't help neither.
Hi fsr,
On 08/12/2016 02:00 PM, fsmithred wrote:
On 08/13/2016 04:45 AM, aitor_czr wrote:
>
>
>I'm applying changes to the packages. This is my vdev.conf file:
>
>*vdev.conf* _
>
>[vdev-config]
>firmware=/usr/lib/firmware
>acls=/etc/vdev/acls
>actions=/etc/vdev/actions
>he
On Fri, 12 Aug 2016 08:08:42 -0500
Jim Murphy wrote:
> I'm not a dev and haven't done a lot of research on how things
> should work with multiple *dev(s). It would appear that there
> could be at least 2 or maybe 3 that will be part of devuan's
> offerings(udev, vdev and eudev). The above examp
On Sat, 13 Aug 2016 16:12:27 +0200
aitor_czr wrote:
> Finally i decided to use the following config file:
>
> [vdev-config]
> firmware=/lib/firmware
> acls=/etc/vdev/acls
> actions=/etc/vdev/actions
> helpers=/lib/vdev
> hwdb=/lib/vdev/hwdb/hwdb.squashfs
> ifnames=/etc/vdev/ifnames.conf
> pidfil
Le 05/08/2016 21:45, Steve Litt a écrit :
Readhttps://wiki.gentoo.org/wiki/Mdev . mdev means no Gnome allowed,
and neither KDE nor its apps allowed. That don't cross my eyes none, I
banned all KDE software from my computers in 2012, and I haven't used
Gnome since they went to the lame Gnome3. Bu
On Fri, 12 Aug 2016 17:41:42 +0200, richard wrote in message
<20160812174142.f82635d8a4201d3119759...@lucassen.org>:
>
> That's a good point. Devuan means "freedom of choice" and it would be
> nice if a Devuan user could opt for udev,
..best way would be advice of the looming systemd "support"
On Fri, 12 Aug 2016 11:32:41 +0200
Fred DC wrote:
> Hi,
>
> My apololgies for sounding a bit emotional about this issue.
The behavior of the poetterists is enough to make anybody indignant.
>
> If, up to now, you have "runit" running as pid 1 and managed to
> maintain the ability to boot from
Steve Litt [2016-08-12 19:47]:
> I don't understand. Do you perhaps mean that sysvinit is PID1, and you
> use runit strictly as a process supervisor? The reason I ask this is,
> whatever acts as PID1 is what boots the kernel.
No. The kernel starts PID1.
--
Hilsen Harald
_
Harald Arnesen wrote:
<<
Steve Litt [2016-08-12 19:47]:
> I don't understand. Do you perhaps mean that sysvinit is PID1, and you
> use runit strictly as a process supervisor? The reason I ask this is,
> whatever acts as PID1 is what boots the kernel.
No. The kernel starts PID1.
>>
Steve Litt kno
On Fri, Aug 12, 2016 at 03:25:27PM +0200, Fred DC wrote:
> On 12/08/2016 13:43, Tom H wrote:
> >>From the changelog of 2.1.2-4:
> > New binary package 'runit-init', that provides /sbin/init replacement
> > out-of-box.
> >
> > I'd say that it's badly packaged. For sysvinit, there's
> >
> > - sysvi
On 08/12/2016 12:32 PM, Arnt Karlsen wrote:
> On Fri, 12 Aug 2016 17:41:42 +0200, richard wrote in message
> <20160812174142.f82635d8a4201d3119759...@lucassen.org>:
>
>>
>> That's a good point. Devuan means "freedom of choice" and it would be
>> nice if a Devuan user could opt for udev,
>
> ..b
On Fri, 12 Aug 2016 20:34:07 +0200
Harald Arnesen wrote:
> Steve Litt [2016-08-12 19:47]:
>
> > I don't understand. Do you perhaps mean that sysvinit is PID1, and
> > you use runit strictly as a process supervisor? The reason I ask
> > this is, whatever acts as PID1 is what boots the kernel.
>
> I have to do some work now, I look forward to the packages. Maybe you
> can add a small README.txt for those who are willing to test vdev.
Yes please. A small README.TXT explaining what we have to do to set up and
install vdev will work wonders at attracting testers. Having to sift
through the a
Quoting Steve Litt (sl...@troubleshooters.com):
> LOL, you're right. The bootloader or UEFIwhatever starts the kernel.
Everyone who's read your excellent troubleshooters.com artlces about
inits figured out that your fingers were merely on autopilot or
something, but you _definitely_ knew that PID
> On August 13, 2016 at 4:45 AM aitor_czr wrote:
As you know, today is August 12, not August 13.
PLEASE FIX YOUR COMPUTER CLOCK
Here is the trace of your message:
START >
Received: from [192.168.0.10] (114.62-99-112.dynamic.clientes.euskaltel.es
[62.99.112.114]) (Authenticated sender
On Sat, 13 Aug 2016 00:22:43 -0400 (EDT)
Peter Olson wrote:
> > On August 13, 2016 at 4:45 AM aitor_czr
> > wrote:
>
> As you know, today is August 12, not August 13.
>
> PLEASE FIX YOUR COMPUTER CLOCK
>
> Here is the trace of your message:
>
> START >
>
> Received: from [192.168.
On Sat, 13 Aug 2016 02:24:14 -0400
Steve Litt wrote:
> On Sat, 13 Aug 2016 00:22:43 -0400 (EDT)
> Peter Olson wrote:
>
> > > On August 13, 2016 at 4:45 AM aitor_czr
> > > wrote:
> >
> > As you know, today is August 12, not August 13.
> >
> > PLEASE FIX YOUR COMPUTER CLOCK
> >
> > He
32 matches
Mail list logo
