On Wed, 26 Apr 2017 12:08:48 +1000, Ralph wrote in message
<2fab2208-e0dc-27f5-dd3d-f9d7156bbaa7@???>:

>
>
> Arnt Karlsen wrote on 26/04/17 11:18:
> > On Mon, 24 Apr 2017 14:49:06 +1000, Ralph wrote in message
> > <be1216c5-c463-a069-b1e4-f405ee658809@???>:
> >
> >>
> >> Arnt Karlsen wrote on 24/04/17 09:13:
> >>> On Wed, 19 Apr 2017 18:54:07 +0200, Arnt wrote in message
> >>> <20170419185407.228cd18a@???>:
> >>>
> >>>> On Thu, 20 Apr 2017 02:21:53 +1000, Ralph wrote in message
> >>>> <d3a264ce-a767-dffc-845d-d1eb26027a3e@???>:
> >>>>
> >>>>>
> >>>>>
> >>>>> Arnt Karlsen wrote on 19/04/17 23:17:
> >>>>> [cut]
> >>>>>>
> >>>>>> ...wiped udev off my box and wound up with a box that boots oh
> >>>>>> soo fine until it tries to load my new vdev
> >>>>>> initrd.img-4.9.0-2-rt-amd64 ...am I the first one here to try
> >>>>>> this on a rt kernel?
> >>>>>>
> >>>>>> ..recovery ideas? Do we have any vdev live-cd?
> >>>>>>
> >>>>>> ..last time I did this stunt, I chrooted in off a Knoppix? iso,
> >>>>>> I have memdisk and a few iso links handy in /boot, and Debian's
> >>>>>> Sid vmlinuz-4.8.0-2-amd64, vmlinuz-4.8.0-2-rt-amd64 and
> >>>>>> vmlinuz-4.9.0-1-rt-amd64 with systemd-udev initrd's, but they
> >>>>>> all depend on a working install of udev AFAIK, and I'd prefer
> >>>>>> pushing thru with vdev rather than going back to udev.
> >>>>>>
> >>>>>> ..has anyone here tried downgrading to Debian Wheezy era udev?
> >>>>>>
> >>>>>>
> >>>>>> ..looking for recovery live-cd idea starting points, I came
> >>>>>> across 32-bit
> >>>>>> https://debiandog.github.io/doglinux/zz02debiandogwheezy.html
> >>>>>> which could work both as a starting point for a live-cd and as
> >>>>>> a starting point for an upgrade path for stuck Debian Wheezy
> >>>>>> people via "Devuan-0.x Wheezy" to current Devuan-1.x Jessie.
> >>>>>>
> >>>>>> ..according to https://debiandog.github.io/doglinux/ "DebianDog
> >>>>>> is very small Debian Live CD shaped to look and act like Puppy
> >>>>>> Linux. Debian structure and Debian behaviour are untouched and
> >>>>>> Debian documentation is 100% valid for DebianDog. You have
> >>>>>> access to all debian repositories using apt-get or synaptic.",
> >>>>>> creating "Devuan-0.x Wheezy Live-CD" etc is trivial, toss their
> >>>>>> repos for ours, update, upgrade and remaster, the 64-bit
> >>>>>> version likely needs to be built off deb-src lines.
> >>>>>>
> >>>>>>
> >>>>>> ..but first comes the classic chicken-and-egg 64 bit recovery
> >>>>>> I need now. ;o)
> >>>>>>
> >>>>>
> >>>>> I'm not sure it helps you, but I've made a vdev variant of most
> >>>>> recent devuan_jessie_RC_amd64_minimal_live.iso (time stamped
> >>>>> 2017-Mar-27 20:57) that I got from the official mirror
> >>>>> http://mirror.sfo12.us.leaseweb.net/devuan/
> >>>>>
> >>>>> I purged a couple of things from it, then added and installed
> >>>>> "my" vdev_0.1.1_amd64.deb, and made a refractasnapshot of this,
> >>>>> into devuan_jessie_RC_amd64_minimal_live_vdev.iso, which is
> >>>>> downloadable at https://www.uk.realsam.co.uk/files/devuan/
> >>>>>
> >>>>> It boots with vdev rather than udev, and udev remains installed,
> >>>>> though with all its "competing" files tucked away. As you might
> >>>>> know, this vdev packaging is different from aitor's packaging
> >>>>> for gnuinos by not declaring a udev competition, but rather
> >>>>> attempting to manage a dynamic choice of which one is in use.
> >>>>> The software is otherwise the same, I believe.
> >>>>
> >>>> ..thanks, we shall find out. ;o)
> >>>
> >>> ..no joy this far, vdev does not work with any of my installed
> >>> kernels, neither my dpkg variant of your vdev-assistant nor your
> >>> original restores udev, so I'm stuck with live-CDs when I need to
> >>> go online to chk things to read up on.
> >>>
> >>> ..you packaged your vdev differently than aitor, do I then use
> >>> your deb(-src) lines in /etc/apt/sources.list and comment out
> >>> his?
> >>>
> >>> ..another approach is ignore apt and dpkg, and simply drop in all
> >>> files with tar or cpio or somesuch, haven't done that kinda stunt
> >>> since my RH-5.2 days.
> >>>
> >>> ..if that fails, are you able to build me an old fashion monster
> >>> monolithic kernel with nouveau, vdev and everything else compiled
> >>> into the kernel, and not as modules, that I can boot without an
> >>> initrd?
> >>> Big size is no problem, I have 8GB ram, but no build box.
> >>>
> >>> ..if not, what do I need to build a vdev kernel myself on my
> >>> box running your devuan_jessie_RC_amd64_minimal_live_vdev.iso?
> >>
> >> If the live iso works, you can restore udev via chroot to your root
> >> file system. It's a relatively simple sequence:
> >> # mnt /dev/sdaX /mnt
> >> # chroot /mnt
> >> # mount -t proc none proc
> >> # mount -t sysfs none /sys
> >> # mount -t devpts none /dev/pts
> >> # apt-get install udev
> >> # apt-get purge *vdev* <-- all aitor's vdev packages
> >
> > ..er, something went wrong here, I forgot? to mention
> > my bad apt database means doing things rpm-hell style
> > with dpkg or tarball style, and forgot to umount -v \
> > /mnt/proc et al before exiting my chroot, and wound
> > up hitting the power button, on reboot, it decided to
> > fsck a weird "/rootfs" and failed, so I did one off a
> > live iso and tried a new boot, and now I just need to
> > get vdev's mousepad 'n keybd input working in X too,
> > all is fine in the console. ;oD
> >
> >> [cut]
>
> I believe keyboard and mouse needs the "evdev" module to be loaded
> before something; certainly before starting X.

..aye: root@box:~# lsmod |grep evdev
evdev                  24576  26
root@box:~# lsmod |grep vdev |grep -v evdev
root@box:~# lsmod |grep dev |grep -v evdev
input_polldev          16384  1 lis3lv02d
ipmi_devintf           20480  0
ipmi_msghandler        49152  3 ipmi_devintf,ipmi_poweroff,ipmi_watchdog
ppdev                  20480  0
parport                49152  3 lp,parport_pc,ppdev
videodev              180224  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media                  40960  2 uvcvideo,videodev
joydev                 20480  0
root@box:~# 

> "My" vdev scripts for
> initramfs does that by adding a line "vdev" to the file
> "/conf/modules" in the initrd, which makes it be loaded at the
> pre-pivot stage.

..thanks, I look where?

..anything more we wanna find out before I modprobe -v vdev?

> Actually, as I'm confused about which vdev variant you are using,
> maybe we can identify the as "Gnuinos' vdev" and "Devuan's vdev"
> hence.

..me too, and the binaries have md5sums so we _can_ find out. ;o)
Oneliner ideas, please? ;o)

> In any case, it may well be some other reason why it's not working.
>
> Ralph.

..well, the vdev and the hardware works, AFAICT, it's X not seeing
the vdev_s_ way of doing things. And I guess we wanna know WTF 'n
HTF my vdev combination works as well as it does. :o)

..remember, many of the best things in history was caused by
stupid luck. ;oD

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.