Are you a Network Manager?

Someone reminded me of this so I decided to post it. If you're one of the many few (haha) who are trying out the ISO I would like to point out this is a developer release. If you're not a developer by all means feel free to download and try it.. I'm not a RTFM type of guy, but I just want to save you the frustration up front of everything being done for you.. like Network Management.

For now I don't have a Network Manager included. Something that will detect your network interface bring it up and grab an IP.. you have to be the Network Manager.. Yes you.. go look in the mirror and say "I am the network manager". If all went well on boot and your network card was found to have a driver.. it should be loaded so now do this Mr. (or Mrs.) Network Manager in the command line:

ifconfig eth0 up

now press enter and do a:


you should see information now for eth0 (yay!). However there's no IP.. Sad.. let's get one by doing

udhcpc eth0

and now eth0 should be assigned whatever IP your network gave it. At this point you can do any number of things with wget.. and maybe install the one package that isn't already installed.. and that's really it for now, but hey it works (or should)! If you have any questions check out the IRC link. Thanks

A Storm is a brewin'

I alluded to this post in the last post... 

Things are progressing (I'm a broken record with this statment), I have changed some init and boot settings to reflect our true boot opions. So any any ISO releases before 44 (I think) will be more complex in these areas then they need to be.  There's now a very short string (4) of currently used boot options when you press "TAB" on the boot menu.

The one to really pay attention to is ramdisk_size=. This defines the size of the ramdisk for the livecd/usb session. Some machines have quite a bit of ram so you can make your ram disk quite large and still have a decent amount left over for actual ram use and not disk use. I think 512M is a happy middle ground. If you're like me though and still have a few machines laying around with 512M or less you may want to bring that ram disk down to 256000 (or loosely 256M). So basically this option allows you to tweak the ramdisk size as a measn to get the best performance for a particular system running live.

Long time no news, but there was work..

Maybe I need to update this more often.. maybe I don't. I don't know of to many people that are reading this or that might really even care about this little pet project, but it's here and it's moving forward. 

Yesterday I was able to get a bootable ISO up and running, at least on VirtualBox and Qemu. The live init script and makelive script, are based off my previous work on Synergy when I repackaged most of Fedora 16 and ported over the Chakra installer. That was a long time ago. So there has been quite a few tweaks that have had to happen to get things going. I thought the inclusion of overlayfs into Kernel 3.18 was going to make my life easier as I could drop specialized kernel builds for aufs. If you don't know what I am talking about then I will try and make it simple, overlayfs, aufs also unionfs allow you to create a writable ram disk and merge or overlay that with something that is not writable, ie. a mounted squashfs image to make the system writable (at least to ram). It was once said overlay file systems had no place in the kernel, though soon after they did include one but the better aufs (in my opinion) was left out. Enter 3.18 and a more advanced system call overlayfs is included. It's a litte conveluted and been a bit tricky for me to figure out, but it seems I have gotten it to work, though I will most likey do some more tweaking.

At this point in time the LiveISO is still somewhat crippled, as CA-Certs are broken and various things are missing. However, every development package (every package for that matter) Unity has is included on the ISO. You can build rpms on it if you so wish and know how to set the ram size in the boot params (more on that in a later post). You can also bring up the network (tested on a VM with e1000 module).

This ISO, though not impressive marks the ground work for a working MUSL Based RPM Distribution that is using YUM. I don't think one such distribution exists and we might be the first. That's pretty neat to me.

Find the ISO (though very much unfinished) Here: 


Just wanted to give a quick update unless you haven't been watching Unity-Linux on github we now have over 110 x86_64 packages that have been built. I have about 20-30 more to build before I can incorporate my plans for a package manager and see if the particular one I have in mind will work with rpm5, that might be a task in itself. I'm keeping mum about it until I know it will work, but unlike dnf the text based frontend won't depend on SystemD. When I get it working there will be a full story on it. I would also like to build eudev and maybe even dracut. A few days ago I finished off mkisofs so I am tempted to build an ISO, but my goal is to have a package manager, dracut, eudev and createrepo provided. In the mean time I am pulling in a ton of dependencies including X11 libs and protos. This is mildly frustrating, because there's a lot and it's tedious, but in the long run it's less I have to do when it comes time to build Xorg. My goal is to keep Unity-Linux proper under 300 packages. Crazy you may say, because everyone one will want to run xyz.. My goal for Unity-Linux is to have it be a stable, flexible and small base, not a desktop distribution, however it can and will provide the base for Synergy Linux, which will be your standard (as much as a desktop distribution based on musl and rpm5 can be) desktop based distribution. Right now there's a long way to go however, at some point I will need to go multi-lib when I start building for x86, then there's my distant future plans of an Arm port. So we are gettinthere just slowly a chip at a time.

Simple news update

Hello all who are interested. Work has progressed at a slow but some what fulfilling pace. I have been able to build and compile various base packages. Enough base packages have been built now that I can create a chrooted enviroment with these packages to build more packages. Building in a chroot allows me to build musl-libc based packages on machines that are running glibc, like my CentOS 7 build server. 

At this point in the game my focus is now shifting to a bootable format. Which means init generation and decisions about what ramdisk system to use etc.. along with some kernel development. Initially I will be using syslinux (extlinux) as a boot manager and we will go from there and see where things take us.

Work is (almost) constantly being done in git. Very simple scripts have been added in seed to help build a chroot (or build) enviroment, they are no where close to being finished, but do make my life easier. Package spec files are coming along as well, dependancy and requires are being figured out and added. Documention (ie man pages) are not being included in any package at this point but will be added as sub packages in the near future. For right now only 64bit is our focus, but with the number of EeePCs I still have laying around you better believe we will have a 32bit version as well.

For me I have seen some major progress in the last week or so, I would like to have seen a lot more. To many of you, there most likely hasn't been much. If you want a sense of progress please check git from time to time, or just ask on the IRC channel. Thanks

Kind regards,


Published on  July 29th, 2017