[DNG] virtualbox-dkms fails to build on Devuan
Greetings! I have been using Devuan Jessie 1.0 Beta2 for nearly two months. I regularly update the system. Once I had virtualbox running fine but then removed it. Since then the kernel has been upgraded at least twice. I have reinstalled virtualbox and all the components are working except virtualbox-dkms fails to build. This means there is no vboxdrv driver. Below please find the install error and the build make log. Advice would be appreciated. Thaddeus Nielsen When attempting to (re)install virtualbox-dkms, here is the output to the screen: Setting up virtualbox-dkms (5.1.8-dfsg-6~bpo8+2) ... Loading new virtualbox-5.1.8 DKMS files... Building for 4.9.0-0.bpo.2-amd64 Building initial module for 4.9.0-0.bpo.2-amd64 Error! Bad return status for module build on kernel: 4.9.0-0.bpo.2-amd64 (x86_64) Consult /var/lib/dkms/virtualbox/5.1.8/build/make.log for more information. [ ok ] Unloading VirtualBox kernel modules [] Loading VirtualBox kernel modules...[] No suitable module for running[FAILel found ... failed! failed! invoke-rc.d: initscript virtualbox, action "restart" failed. And here is /var/lib/dkms/virutalbox/5.1.8/build/make.log: DKMS make.log for virtualbox-5.1.8 for kernel 4.9.0-0.bpo.2-amd64 (x86_64) Sat Mar 25 14:57:30 CDT 2017 make: Entering directory '/usr/src/linux-headers-4.9.0-0.bpo.2-amd64' LD /var/lib/dkms/virtualbox/5.1.8/build/built-in.o LD /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/built-in.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/SUPDrvSem.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/SUPDrvTracer.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/SUPLibAll.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/alloc-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/initterm-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/memobj-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/mpnotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/powernotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’: /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1053:33: warning: passing argument 4 of ‘get_user_pages’ makes pointer from integer without a cast fWrite, /* force write access. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0, from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31: /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/mm.h:1302:6: note: expected ‘struct page **’ but argument is of type ‘int’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1054:33: warning: passing argument 5 of ‘get_user_pages’ from incompatible pointer type &pMemLnx->apPages[0], /* Page array. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0, from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31: /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/mm.h:1302:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1050:18: error: too many arguments to function ‘get_user_pages’ rc = get_user_pages(R3Ptr, /* Where from. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0, from /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31: /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/mm.h:1302:6: note: declared here long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /var/lib/dkms/virtualbox/5.1.8/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1067:33: warning: passing argument 6 of ‘get_user_pages_remote’ makes pointer from integer without a cast fWrite, /* force write access. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.
[DNG] bug on initramfs-tools
I was gone for three weeks, sorry if I missed something and am being redundant here. Upon return I updated devuan 1.0.0 with apt-get and then upgraded everything except the kernel failed to upgrade. Here is the message: Setting up linux-image-3.16.0-4-amd64 (3.16.43-2+deb8u1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /boot/initrd.img-3.16.0-4-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.0-4-amd64.postinst line 634. dpkg: error processing package linux-image-3.16.0-4-amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-3.16.0-4-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) The output from mount is: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=913694,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=731592k,mode=755) 801 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) pstore on /sys/fs/pstore type pstore (rw,relatime) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=7754620k) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) /dev/sda3 on /home type ext4 (rw,relatime,data=ordered) The output from cat /proc/mounts is: rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=913694,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=731592k,mode=755 0 0 /dev/root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 pstore /sys/fs/pstore pstore rw,relatime 0 0 tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=7754620k 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/sda3 /home ext4 rw,relatime,data=ordered 0 0 Advice on how to upgrade this kernel would be appreciated. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan.org inaccessible two days
On Fri, 19 May 2017 11:28:04 -0400 etech3 wrote: > Working fine for me. I suggest maybe doing a trace route > FWIW, the stock /etc/dhcp/dhclient.conf includes requests for netbios-name-servers and netbios-scope. When I deleted those two and restarted the network, then I can access devuan.org; but with those two being requested, I could go everywhere I wanted except devuan.org. Odd, eh? RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan.org inaccessible two days
On Fri, 19 May 2017 11:28:04 -0400 etech3 wrote: Working fine for me. I suggest maybe doing a trace route Thanks for the replies. My ISP technical support was able to access devuan.org, so I knew it was my problem. As soon as I put my router between my machine and the ISP modem (which changed the network configuration), I was able to update this machine. Now need to clean up my networking config. RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] devuan.org inaccessible two days
For the second consecutive day my end of the internet cannot find devuan.org Did I miss an announcement? RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan Jessie 1.0.0 stable release candidate
On Fri, 21 Apr 2017 18:14:08 +0200 Veteran Unix Admins wrote: > Dear Init Freedom Lovers, > > Once again the Veteran Unix Admins salute you! > > Our April 2017 gift to you is the long-awaited release of Devuan > Jessie stable release candidate (1.0.0-RC). If all goes as planned, > this will be our first Devuan stable release and our first long term > support (LTS) release as well. > Please advise if there is any difference between this release candidate and an installed beta release that has been kept up-to-date. RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Printing -- now a permissions problem
On Mon, 19 Oct 2015 12:11:08 -0400 Hendrik Boom wrote: > On Mon, Oct 19, 2015 at 10:32:04AM -0500, Thaddeus Nielsen wrote: > > On Mon, 19 Oct 2015 10:47:22 -0400 > > Hendrik Boom wrote: > > > > > On Mon, Oct 19, 2015 at 09:38:20AM -0500, Thaddeus Nielsen wrote: > > > > On Mon, 19 Oct 2015 16:05:37 +0200 > > > > Didier Kryn wrote: > > > > > > > > > Le 19/10/2015 15:24, Hendrik Boom a écrit : > > > > > > On Mon, Oct 05, 2015 at 05:13:40PM -0400, Hendrik Boom wrote: > > > > > >> On Mon, Oct 05, 2015 at 09:47:02PM +0200, Riccardo Boninsegna > > > > > >> wrote: > > > > > >>> On Mon, Oct 5, 2015 at 9:12 PM, Hendrik Boom > > > > > >>> wrote: > > > > > >>>> I installed lpr, and it did take a lot of cups off. Do I really > > > > > >>>> need cups? > > > > > >>> Nope, especially with a Brother that's very LPR-friendly! > > > > > >>> As you found out, cups-bsd is just a port of LPR programs to CUPS. > > > > > >>> > > > > > >>>> But I still don't know how to specify my network printer. > > > > > >>> I'm not familiar at all with LPR, but I know a printcap entry for > > > > > >>> the > > > > > >>> printer is created (if it's currently connected via USB) by the > > > > > >>> driver's postinst somewhere under /opt/Brother; according to the > > > > > >>> printcap manpage, you'd have to edit the "lp" option -- the > > > > > >>> description says "local printer device, or port@host for remote"! > > > > > >> Presumeably that would be port 515 at whatever the IP number for > > > > > >> the > > > > > >> printer is. Will try that wen I'm home near the priniter again. > > > > > >> > > > > > >> And what's there in the way of termcap is a shell script > > > > > >> /opt/brother/Printers/hl3170cdw/inf/setupPrintcapij that creates a > > > > > >> termcap. I hope it will get executed at the right time. At > > > > > >> bootup, > > > > > >> perhaps? > > > > > >> > > > > > >> I'll see when I'm home again. > > > > > > Hand-edited /etc/termcap: > > > > > > root@notlookedfor:/home/hendrik# cat /etc/printcap > > > > > > HL3170CDW:\ > > > > > > :mx=0:\ > > > > > > :sd=/var/spool/lpd/hl3170cdw:\ > > > > > > :sh:\ > > > > > > :lp=515@172.25.1.122:\ > > > > > > :if=/opt/brother/Printers/hl3170cdw/lpd/filterhl3170cdw: > > > > > > root@notlookedfor:/home/hendrik# > > > > > > > > > > > > Now I get > > > > > > > > > > > > hendrik@notlookedfor:~$ lpr -h -PHL3170CDW > > > > > > Documents/math/Librationism=1407.3877v3.ps > > > > > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > > > > > hendrik@notlookedfor:~$ > > > > > > > > > > > > This happens even if I run as root: > > > > > > > > > > > > root@notlookedfor:/home/hendrik# lpr -h -PHL3170CDW > > > > > > Documents/math/Librationism=1407.3877v3.ps > > > > > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > > > > > root@notlookedfor:/home/hendrik# > > > > > > > > > > > > That directory is owned by the lp daemon: > > > > > > > > > > > > oot@notlookedfor:/home/hendrik# ls -al > > > > > > /var/spool/lpd/hl3170cdwtotal 8 > > > > > > drwx-- 2 daemon lp 4096 Oct 5 14:40 . > > > > > > drwxr-xr-x 5 root root 4096 Oct 19 09:02 .. > > > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 acct > > > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 log > > > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 status > > > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 status.pr > > > > > > root@notlookedfor:/home/hendrik# > > > > > > > > > > > > and it contains no .seq file.
Re: [DNG] Printing -- now a permissions problem
On Mon, 19 Oct 2015 10:47:22 -0400 Hendrik Boom wrote: > On Mon, Oct 19, 2015 at 09:38:20AM -0500, Thaddeus Nielsen wrote: > > On Mon, 19 Oct 2015 16:05:37 +0200 > > Didier Kryn wrote: > > > > > Le 19/10/2015 15:24, Hendrik Boom a écrit : > > > > On Mon, Oct 05, 2015 at 05:13:40PM -0400, Hendrik Boom wrote: > > > >> On Mon, Oct 05, 2015 at 09:47:02PM +0200, Riccardo Boninsegna wrote: > > > >>> On Mon, Oct 5, 2015 at 9:12 PM, Hendrik Boom > > > >>> wrote: > > > >>>> I installed lpr, and it did take a lot of cups off. Do I really > > > >>>> need cups? > > > >>> Nope, especially with a Brother that's very LPR-friendly! > > > >>> As you found out, cups-bsd is just a port of LPR programs to CUPS. > > > >>> > > > >>>> But I still don't know how to specify my network printer. > > > >>> I'm not familiar at all with LPR, but I know a printcap entry for the > > > >>> printer is created (if it's currently connected via USB) by the > > > >>> driver's postinst somewhere under /opt/Brother; according to the > > > >>> printcap manpage, you'd have to edit the "lp" option -- the > > > >>> description says "local printer device, or port@host for remote"! > > > >> Presumeably that would be port 515 at whatever the IP number for the > > > >> printer is. Will try that wen I'm home near the priniter again. > > > >> > > > >> And what's there in the way of termcap is a shell script > > > >> /opt/brother/Printers/hl3170cdw/inf/setupPrintcapij that creates a > > > >> termcap. I hope it will get executed at the right time. At bootup, > > > >> perhaps? > > > >> > > > >> I'll see when I'm home again. > > > > Hand-edited /etc/termcap: > > > > root@notlookedfor:/home/hendrik# cat /etc/printcap > > > > HL3170CDW:\ > > > > :mx=0:\ > > > > :sd=/var/spool/lpd/hl3170cdw:\ > > > > :sh:\ > > > > :lp=515@172.25.1.122:\ > > > > :if=/opt/brother/Printers/hl3170cdw/lpd/filterhl3170cdw: > > > > root@notlookedfor:/home/hendrik# > > > > > > > > Now I get > > > > > > > > hendrik@notlookedfor:~$ lpr -h -PHL3170CDW > > > > Documents/math/Librationism=1407.3877v3.ps > > > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > > > hendrik@notlookedfor:~$ > > > > > > > > This happens even if I run as root: > > > > > > > > root@notlookedfor:/home/hendrik# lpr -h -PHL3170CDW > > > > Documents/math/Librationism=1407.3877v3.ps > > > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > > > root@notlookedfor:/home/hendrik# > > > > > > > > That directory is owned by the lp daemon: > > > > > > > > oot@notlookedfor:/home/hendrik# ls -al /var/spool/lpd/hl3170cdwtotal 8 > > > > drwx-- 2 daemon lp 4096 Oct 5 14:40 . > > > > drwxr-xr-x 5 root root 4096 Oct 19 09:02 .. > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 acct > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 log > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 status > > > > -rw--- 1 daemon lp 0 Oct 5 14:32 status.pr > > > > root@notlookedfor:/home/hendrik# > > > > > > > > and it contains no .seq file. Preumably that fle would be created as > > > > needed. > > > > And presumably the permissions are checked in some way that can exclude > > > > root. > > > > > > > > > > > > > > Hi Hendrik. > > > > > > I can see one reason for root to be unable to get the permission: > > > lpr being owned by another user than root and being suid; this is fine > > > at the condidiont that this owner is 'daemon', given the owner and > > > permissions of /var/spool/lpd. > > > > > > Didier > > > > > Another thing to examine: lp is the group on the directory but that > > directory had no write permission for the group, if I recall > > correctly. > > Correct: > root@notlookedfor:/home/hendrik# ls -ald /var/spool/lpd/hl3170cdw > drwx-- 2 daemon lp 4096 Oct 5 14:40 /var/spool/lpd/hl3170cdw > root@notlookedfor:/home/hendrik# > > But with lpr being suid root, should that matter? At least, I think > tht's what the s's mean: > > root@notlookedfor:/home/hendrik# which lpr > /usr/bin/lpr > root@notlookedfor:/home/hendrik# ls -l /usr/bin/lpr > -rwsr-sr-x 1 root lp 26536 Nov 20 2014 /usr/bin/lpr > root@notlookedfor:/home/hendrik# > > -- hendrik Sorry, I missed that; yes, I agree that the setuid should allow a user to print. Does lpr.log have any helpful message? RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Printing -- now a permissions problem
On Mon, 19 Oct 2015 16:05:37 +0200 Didier Kryn wrote: > Le 19/10/2015 15:24, Hendrik Boom a écrit : > > On Mon, Oct 05, 2015 at 05:13:40PM -0400, Hendrik Boom wrote: > >> On Mon, Oct 05, 2015 at 09:47:02PM +0200, Riccardo Boninsegna wrote: > >>> On Mon, Oct 5, 2015 at 9:12 PM, Hendrik Boom > >>> wrote: > I installed lpr, and it did take a lot of cups off. Do I really need > cups? > >>> Nope, especially with a Brother that's very LPR-friendly! > >>> As you found out, cups-bsd is just a port of LPR programs to CUPS. > >>> > But I still don't know how to specify my network printer. > >>> I'm not familiar at all with LPR, but I know a printcap entry for the > >>> printer is created (if it's currently connected via USB) by the > >>> driver's postinst somewhere under /opt/Brother; according to the > >>> printcap manpage, you'd have to edit the "lp" option -- the > >>> description says "local printer device, or port@host for remote"! > >> Presumeably that would be port 515 at whatever the IP number for the > >> printer is. Will try that wen I'm home near the priniter again. > >> > >> And what's there in the way of termcap is a shell script > >> /opt/brother/Printers/hl3170cdw/inf/setupPrintcapij that creates a > >> termcap. I hope it will get executed at the right time. At bootup, > >> perhaps? > >> > >> I'll see when I'm home again. > > Hand-edited /etc/termcap: > > root@notlookedfor:/home/hendrik# cat /etc/printcap > > HL3170CDW:\ > > :mx=0:\ > > :sd=/var/spool/lpd/hl3170cdw:\ > > :sh:\ > > :lp=515@172.25.1.122:\ > > :if=/opt/brother/Printers/hl3170cdw/lpd/filterhl3170cdw: > > root@notlookedfor:/home/hendrik# > > > > Now I get > > > > hendrik@notlookedfor:~$ lpr -h -PHL3170CDW > > Documents/math/Librationism=1407.3877v3.ps > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > hendrik@notlookedfor:~$ > > > > This happens even if I run as root: > > > > root@notlookedfor:/home/hendrik# lpr -h -PHL3170CDW > > Documents/math/Librationism=1407.3877v3.ps > > lpr: cannot open /var/spool/lpd/hl3170cdw/.seq: Permission denied > > root@notlookedfor:/home/hendrik# > > > > That directory is owned by the lp daemon: > > > > oot@notlookedfor:/home/hendrik# ls -al /var/spool/lpd/hl3170cdwtotal 8 > > drwx-- 2 daemon lp 4096 Oct 5 14:40 . > > drwxr-xr-x 5 root root 4096 Oct 19 09:02 .. > > -rw--- 1 daemon lp 0 Oct 5 14:32 acct > > -rw--- 1 daemon lp 0 Oct 5 14:32 log > > -rw--- 1 daemon lp 0 Oct 5 14:32 status > > -rw--- 1 daemon lp 0 Oct 5 14:32 status.pr > > root@notlookedfor:/home/hendrik# > > > > and it contains no .seq file. Preumably that fle would be created as > > needed. > > And presumably the permissions are checked in some way that can exclude > > root. > > > > > > Hi Hendrik. > > I can see one reason for root to be unable to get the permission: > lpr being owned by another user than root and being suid; this is fine > at the condidiont that this owner is 'daemon', given the owner and > permissions of /var/spool/lpd. > > Didier > Another thing to examine: lp is the group on the directory but that directory had no write permission for the group, if I recall correctly. RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan compared to AntiX
On Sat, 8 Aug 2015 15:02:07 +0800 Robert Storey wrote: > Hi everyone. It's been a little while since I last posted. > > Some of you might remember that I occasionally write reviews for > DistroWatch. Not too often, because it's my policy to only write about a > distro that I actually use (or would use) in everyday life. Ever since > systemd starting contaminating Linux, the number of distros I consider > usable has been drastically reduced. > > Until a few months ago I was using Ubuntu 14.04, but finally dropped it. > The replacement was Manjaro OpenRC, which is pretty good but has a little > systemd contamination from dbus or udev (not sure of the details). I wrote > a DistroWatch of Manjaro-OpenRC which you can view here: > > http://distrowatch.com/weekly.php?issue=20150601#manjaro > > As you might have guessed from the title of this thread, the next review I > hope to write will be about AntiX. I just installed it yesterday and I'm > using it right now. All things considered, it's very nice and functionally > equivalent to Manjaro-OpenRC. The author of AntiX, Anticapitalista, says > that there are no systemd libraries or systemd-shim in AntiX. The following > command produces zero output: > > dpkg --get-selections | grep systemd > > So my big question here: in what ways will Devuan differ from AntiX? I'm > guessing that vdev will be part of the answer, but surely there is more. I > think that the DistroWatch readership will be interested, and any thoughts > that you all have along these longs will be greatly appreciated. I will try > to incorporate the best informed comments into the review, in the hopes of > piquing interested in both Devuan and AntiX. > > Thank you all in advance, > - Robert I installed antiX on my wife's old machine about five weeks ago. Though I obtain the same results as you when using your dpkg command, I get different results when I simply run locate systemd. You might want to try that before writing your review. RPTN ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
