[ale] Origins of Linux, do we care?

[Steve Litt]

On Sun, 20 Sep 2015 06:18:42 -0400
Paul Cartwright <pbcartwright at gmail.com> wrote:

> On 09/18/2015 01:00 PM, James Sumners wrote:
> >
> > On Fri, Sep 18, 2015 at 11:16 AM, leam hall <leamhall at gmail.com
> > <mailto:leamhall at gmail.com>> wrote:
> >
> >     systemd bothers me at a visceral level
> >
> >
> > I am moving to Void Linux[1] for my personal projects specifically
> > because of it. First up, my "router" build. Then my VPS instance and
> > my HTPC. I will have to deal with this systemd crap at work when I
> > eventually have to use RHEL7, but I will not continue to use it
> > outside of work.
> >
> > [1] -- http://www.voidlinux.eu/
> >
> >
>  tried installing void in a VM on my desktop.. install went ok, after
> I figured out the partitioning, but at the very end I got an error
> message that it couldn't install grub, so when I rebooted the vm, no
> OS.. bummer..
> 

Void has really sucky documentation, making it almost impossible to do
it right the first time. So when (notice I don't say if) your Void
install fails to reboot, what you need to do is once again boot from
DVD (or in qemu from a .iso file), mount, chroot, and do your best to
check out your grub.

When I installed it on my laptop last night, I found that the
instructions I was using (efi instructions because I couldn't find mbr
instructions) failed to build /boot/grub/grub.cfg. I did grub-mkconfig
-o /boot/grub/grub.cfg to solve that problem, and when I exited chroot,
unmounted /, and rebooted, I got my grub menu and was able to boot to
Void. Be sure also that your initrd and kernel are right, and that
during the dracut part of the instructions you do just what it says.

It's a lot of work on the user's part, and someone (maybe I) should
document it better, but the results are well worth it.

SteveT

Steve Litt 
August 2015 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust