[mdlug] Bringing up Linux with Suckless Init plus daemontools-encore

Sun Sep 6 22:57:04 EDT 2015

Hey Steve,

I got daemontools-encore to install and everything is working fine. I am
having a fun time working my way through that tutorial because I am
learning a lot. I am now up to the point of installing Littkit.

I am not sure if you know this but you have a couple of broken links on
that page. When I try and go to these pages:

(http://troubleshooters.com/linux/diy/dolog_ax_suckless_init_on_plop.txt)
and
(http://troubleshooters.com/linux/diy/ps_ax_suckless_init_on_plop.txt)

all I get is a HTTP 404 file not found error.

I looked at Void Linux and Funtoo and they both look like really nice
distros. I think I will give them a closer look at some point.

Thanks,

Jeremy

On Sat, Aug 8, 2015 at 3:02 PM, Steve Litt <slitt at troubleshooters.com>
wrote:

> Hi Jeremy,
>
> daemontools has a well known compile error on Linux involving error.h.
> Your error didn't look to me like that, but who knows.
>
> I'd try using daemontools-encore at
> http://untroubled.org/daemontools-encore/ . It's an easier compile, and
> that's what I actually used at
> http://troubleshooters.com/linux/diy/suckless_init_on_plop.htm .
>
> I prefer Funtoo to Gentoo for one reason: Funtoo has gone on record
> never to ram systemd on your box.
>
> About Gentoo's taking too much time updating the system, I imagine this
> is true only if it's your first update, or you've waited 2 weeks to
> update. Or if you're running on a very slow computer or very slow web
> connection. OORR, if you're running on a machine that doesn't have
> hardware virtualization or you aren't using hardware virtualization. Be
> sure to use -enable-kvm! You might need to be root to do it, or make
> yourself a member of group kvm.
>
> As far as Virtualbox vs Qemu, on my machine, Virtualbox often
> terminates for no good reason, so I switched to Qemu and never looked
> back. Here is my runfuntoo.sh, by which I run Funtoo:
>
> ============================================
> #!/bin/sh
>
> qemu-system-x86_64  -m 4096 -hda funtoo.img -boot d -ctrl-grab \
>  -cdrom /scratch/linuxinst/sysrescuecd/systemrescuecd-x86-4.3.0.iso \
>  -vga std  -enable-kvm \
> -netdev user,id=mynet0  -device e1000,netdev=mynet0
>
> # -show-cursor
>
>
> #-netdev user,id=mynet0          -device e1000,netdev=mynet0
> # -netdev tap,id=mynet0 -device e1000,netdev=mynet0
>
> #/scratch/linuxinst/sysrescuecd/systemrescuecd-x86-4.3.0.iso
>
> #lubuntu-15.04-desktop-amd64.iso
>
> # -show-cursor
>
> ============================================
>
> You'll notice a lot of commented out stuff. I put that in and out as
> needed. Also, you switch to booting off hard drive or booting from iso
> image by using -boot d for iso "cdrom", and -boot c for hard drive.
>
> Yesterday I installed Void Linux. No systemd, inits with runit. Appears
> to have a good package manager called xbps. However, it's the worst
> ever documented distro. So if you install it, boot the live CD, MAKE
> SURE you're in bash and not some other shell, and then as a normal user,
> do the following:
>
> sudo void-installer
>
> The preceding command is a secret, passed from member to member of
> the Secret Society of Void Linux, not to be given to the great
> unwashed. In fact, the Void website goes out of its way to give you
> difficult and outdated installation methods, and never once utters the
> phrase "void-installer". Especially secretive is that 8db low sound
> Youtube video, that always sorts to the top in a search, by a guy who
> rushes and mumbles. He fast-mumbles what sounds like might
> "void-installer", but then doesn't pause before hitting enter on the
> command, so you can't read what he actually typed. And you can't really
> understand what he's mumbling.
>
> As far as I can tell, the scattered Void documentation telling you that
> you must partition the disk before installation is outdated:
> void-installer gives you a chance to partition at the proper time.
>
> Also confusing is that when you're finished declaring your filesystems,
> there's no "Done" tabtarget, so you must use "Back", not knowing if
> that will dump all your work (it won't). If you had partitioned ahead
> and skipped partitioning in void-installer, using "Back" in the
> filesystem declarion part brings the cursor back one, to "partition".
> Ugh!
>
> Everything you do with Void, make sure you're in bash, or your command
> completion won't work like you expect. Once you get past the incredibly
> bad and contradictory Void documentation spread all over the web,
> you'll find it's a pretty darn good distro, that boots to a good init
> rather than simply declining to boot to the bad one.
>
> If you'd like something simplistic, that inits with runit, doesn't
> force you to use a Display Manager, and has few dependencies, Void
> Linux is something to investigate.
>
> SteveT
>
> Steve Litt
> July 2015 featured book: Rapid Learning for the 21st Century
> http://www.troubleshooters.com/rl21
>
>
>
>
> On Sat, 8 Aug 2015 13:48:57 -0400
> JeremyBekka C <jrchristophel at gmail.com> wrote:
>
> > Hey Steve,
> >
> > I have been working on installing daemontools but am having troubles.
> > When I try and run the make command from within the daemontools
> > directory I get the following error. I included some extra
> > information for context.
> >
> > ./compile svscan.c
> > ./load svscan unix.a byte.a
> > cat warn-auto.sh svscanboot.sh > svscanboot
> > chmod 755 svscanboot
> > ./compile svstat.c
> > ./load svstat svpath.o time.a unix.a byte.a
> > ./compile svup.c
> > ./load svup svpath.o unix.a byte.a
> > ./compile tai64n.c
> > ./load tai64n timestamp.o time.a unix.a byte.a
> > ./compile tai64nlocal.c
> > ./load tai64nlocal unix.a byte.a
> > cat rts.tests/*.sh > rts.sh
> > cat rts.tests/*.exp > rts.exp
> > env - /bin/sh rts.sh 2>&1 | cat -v > rts
> > diff -u rts.exp rts
> > --- rts.exp    2015-08-08 17:13:57.000000000 +0200
> > +++ rts    2015-08-08 17:14:29.000000000 +0200
> > @@ -266,6 +266,7 @@
> >  Caught WINCH
> >  Caught CONT
> >  Caught TERM
> > +rts.sh: line 471:  3392 Terminated              svscan `pwd`/service
> > > svscan.log 2>&1
> >  ==> svc0/output <==
> >  svc0 ran
> >
> > Makefile:352: recipe for target 'rts' failed
> > make: *** [rts] Error 1
> >
> >
> > I have also tried the directions given from his website (
> > http://cr.yp.to/daemontools/install.html) on how to install
> > daemontools and get another error as well. That error is as follows:
> >
> > stralloc_pend.o strerr_die.o strerr_sys.o subgetopt.o wait_nohang.o \
> > wait_pid.o
> > ./load envdir unix.a byte.a
> > /usr/lib/gcc/x86_64-unknown-
> >
> > linux-gnu/4.9.2/../../../../x86_64-unknown-linux-gnu/bin/ld: errno:
> > TLS definition in /lib64/libc.so.6 section .tbss mismatches non-TLS
> > reference in envdir.o
> > /lib64/libc.so.6: error adding symbols: Bad value
> > collect2: error: ld returned 1 exit status
> > Makefile:111: recipe for target 'envdir' failed
> > make: *** [envdir] Error 1
> >
> >
> >  I think I am following all the directions correctly but cannot
> > figure out what is going on. Could this be a problem with virtualbox
> > and should I try Qemu?
> >
> >
> > Also, regarding Gentoo, I actually had it running on my laptop before
> > I installed Manjaro OpenRC. Gentoo was a lot of work to install but I
> > did learn a lot from that process. I took the manual kernel
> > configuration route in order to learn a little more about the kernel.
> > I liked Gentoo, but I did get a little annoyed with how slow it was
> > to install software and to update the system. It would take me 24hrs
> > to do a full system update unless I held back Libreoffice from being
> > upgraded also. Even then it would take a few hours.
> >
> > Thanks,
> >
> > Jeremy
> >
> >
> > On Wed, Jul 22, 2015 at 11:35 PM, Steve Litt
> > <slitt at troubleshooters.com> wrote:
> >
> > > On Wed, 22 Jul 2015 23:03:57 -0400
> > > JeremyBekka C <jrchristophel at gmail.com> wrote:
> > >
> > >
> > > > So, I started working on my home desktop computer. I did have one
> > > > problem but I figured it out and now have Plop installed on my VM.
> > >
> > > Excellent!
> > >
> > > > The problem that I ran into was when I went to tar the
> > > > plop-linux-desktop file to /mnt/xfer all would start working but
> > > > then part way through the process it stopped coping the files
> > > > because the device did not have enough room. I solved this
> > > > problem by making a larger virtual hard drive (15gb hda1, 30gb
> > > > swap), and everything worked just fine.
> > >
> > > I think you could have gotten  away with 2GB of swap, but you're
> > > right, life's too short to risk running short of time.
> > >
> > > > I had previously tried a partition of 2gb hda1 and
> > > > 6gb swap setup but the same problem occurred. So, next thing on my
> > > > list is to do the Suckless install.
> > >
> > > After you get Suckless Init plus daemontools-encore with LittKit
> > > installed, I predict you'll never view the Init process the same
> > > way, and you'll find very amusing all the authorities who crawl out
> > > of the woodwork when that certain init system gets discussed.
> > >
> > > By the way, if you ever install Gentoo or Funtoo, use 28GB for your
> > > VDI disk and take 2GB of that for swap. Gentoo and Funtoo require
> > > gobs of RAM for kernel compilation.
> > >
> > > Oh, also, I gave up on VirtualBox after it became too unreliable for
> > > me, and I'm using strictly Qemu now.
> > >
> > > SteveT
> > >
> > > Steve Litt
> > > July 2015 featured book: Rapid Learning for the 21st Century
> > > http://www.troubleshooters.com/rl21
> > > _______________________________________________
> > > mdlug mailing list
> > > mdlug at mdlug.org
> > > http://mdlug.org/mailman/listinfo/mdlug
> > >
> > _______________________________________________
> > mdlug mailing list
> > mdlug at mdlug.org
> > http://mdlug.org/mailman/listinfo/mdlug
>
>
>
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
>