Re: Why /command ?

[Kevin Berry]

Steve,

Have you checked for the source package to runit-run?  You may find trouble
getting the Devuan devs to accept a slackpackage install, since it doesn't
meet the FHS.  runit-run is a package that used to exist in Debian (and
Ubuntu imported it until 12.04, I believe), that Gerrit made to fit in the
FHS.  Some other De(bi|vu)an -run packages still exist that work in a
similar manner.

On Sat, Jul 1, 2017 at 11:37 PM, Steve Litt 
wrote:

> Hi all,
>
> I'm writing a document on how to install runit on Devuan, with the hope
> that some day it will lead to a Devuan package that makes sense and to
> the best degree possible implements the goals of the software's author.
>
> Most of it's pretty straightforward, but the runit install scripts
> (package/upgrade to be specific) create /command right off the root,
> and the runit docs suggest I create /package right off the root. These
> are things that most distros would refuse to do.
>
> So I was wondering what the original intent was in having these two
> directories directly off the root? Is it so the init and supervision
> can proceed even before partition mounts are complete? Is there some
> other reason? Can anyone recommend setups that fulfill the reasons for
> the direct-off-root dirs without having direct-off-root dirs?
>
> By the way, if the runit docs go well, I'll do the same thing with s6.
>
> Thanks,
>
> SteveT
>
> Steve Litt
> June 2017 featured book: The Key to Everyday Excellence
> http://www.troubleshooters.com/key
>



-- 
Kevin Berry

Why /command ?

[Steve Litt]

Hi all,

I'm writing a document on how to install runit on Devuan, with the hope
that some day it will lead to a Devuan package that makes sense and to
the best degree possible implements the goals of the software's author.

Most of it's pretty straightforward, but the runit install scripts
(package/upgrade to be specific) create /command right off the root,
and the runit docs suggest I create /package right off the root. These
are things that most distros would refuse to do.

So I was wondering what the original intent was in having these two
directories directly off the root? Is it so the init and supervision
can proceed even before partition mounts are complete? Is there some
other reason? Can anyone recommend setups that fulfill the reasons for
the direct-off-root dirs without having direct-off-root dirs?

By the way, if the runit docs go well, I'll do the same thing with s6.

Thanks,

SteveT

Steve Litt 
June 2017 featured book: The Key to Everyday Excellence
http://www.troubleshooters.com/key

Re: Problems with Step 4

[Daniel GSJ]

Hello,
Problem solved.
To be honest, I was not aware of CTRL + Alt + F5, and I was trying to get
the login
prompt through chvt 5... but it doesn't work.

Thank you!


2017-06-29 2:58 GMT+02:00 Guillermo :

> Hi,
>
> 2017-06-27 16:51 GMT-03:00 Daniel GSJ:
> >
> > Once stage 2 is reached, the computer hangs in the same way than when
> > executing *agetty* in an active console tty, and doesn't login neither.
> >
> > My o.s. is build with Linux-from-scratch, and is running SystemV, so it
> is
> > a pretty simple system.
> >
> > I've tried different possibilities like:
> >
> > #!/bin/sh
> >
> > exec setsid /sbin/agetty tty5 linux
> >
> > or
> >
> > #!/bin/sh
> >
> > exec chpst -P /sbin/agetty tty5 linux
>
> 'chpst -P' from the runit package and setsid from the util-linux
> package do the same thing. And this works on my Gentoo machine (using
> a minimal setup with almost nothing else running, for testing
> purposes). Of course, I have to press CTRL + Alt + F5 to get a login
> prompt, otherwise I just see the kernel's and runit's messages. You do
> not provide enough context about your problem, e.g. you do not say
> where your /etc/runit/1 comes from (did you write it yourself? did you
> copy one from somewhere? official instructions from
> www.linuxfromscratch.org only mention sysvinit or systemd, so it is
> not from there), how you know the stage 2 is reached, what you see on
> the console when everything hangs, ...
>
> /root/scan/getty-tty1:
> total 8
> -rw-r--r-- 1 root root0 Jun 28 20:11 down
> -rwxr-xr-x 1 root root   48 Jun 28 20:03 run
> drwx-- 2 root root 4096 Jun 28 20:07 supervise
>
> /root/scan/getty-tty5:
> total 8
> -rwxr-xr-x 1 root root   48 Jun 28 20:03 run
> drwx-- 2 root root 4096 Jun 28 20:09 supervise
>
> /root/scan/getty-tty1/run:
> #!/bin/sh
> exec chpst -P /sbin/agetty tty1 linux
>
> /root/scan/getty-tty5/run:
> #!/bin/sh
> exec chpst -P /sbin/agetty tty5 linux
>
>   PID  PPID  PGRP COMMAND
> 1 0 1 runit
>   674 1   674 runsvdir -P /root/scan log: 
>   675   674   675  \_ runsv getty-tty1
>   676   674   676  \_ runsv getty-tty5
>   677   676   677  \_ /bin/login --
>   682   677   682  \_ -bash
>   685   682   685  \_ ps axf -o pid,ppid,pgrp,args
>
> And after doing 'sv up ./scan/getty-tty1' and CTRL + Alt + F1, I can
> log on tty1 too:
>
>   PID  PPID  PGRP COMMAND
> 1 0 1 runit
>   674 1   674 runsvdir -P /root/scan log: 
>   675   674   675  \_ runsv getty-tty1
>   687   675   687  |   \_ /bin/login --
>   693   687   693  |   \_ -bash
>   694   693   694  |   \_ ps axf -o pid,ppid,pgrp,args
>   676   674   676  \_ runsv getty-tty5
>   691   676   691  \_ /sbin/agetty tty5 linux
>
> G.
>