Sunday, July 20, 2014

Black Lab Image Creator 1.3 released

Today we are pleased to announce the release of Black Lab Image Creator 1.3, with this release we have fixed the following issues.

1.  Ubuntu 14.04 support is complete
2.  Mint 17  support is complete
3.  kernel wont sync issue - This is due to the filesystem being btrfs during the compilation

4. Deb package now provided

With this newest release you can now build Unity and KDE desktops, here are some issues that need to be addressed and before you file any bug reports please follow these know issues.

- The build system must have an ext4 filesystem.  The default btrfs filesystem that Ubuntu uses WILL NOT WORK.  You can install your image on any filesystem you wish but the build system MUST BE EXT4.  One of our contributors is working on btrfs support but we have no arrival date as of yet.

- If you get a command not found when running blacklabimager you must run the following commands

sudo chmod a+x /usr/bin/BlackLabImager
sudo chmod a+x /usr/bin/BlackLabImager-skelcopy

- If you get a home directory size error you must bring the size down below 4 gigs.  This is a left over issue from  remastersys.

- Your image presents you with a login screen:  Leave the user name as is and click on login, no password is necessary

To download Black Lab Image Creator visit our sourceforge page where the .deb and source files are available

Download Black Lab Image Creator

Wednesday, July 16, 2014

Kickstarter launched

We have started a project on Kickstarter to help fund development of Black Lab Image Creator.  With the funding we plan to continue to develop Black Lab Image Creator and hopefully get some of the bugs fixed that currently plague us.

Wednesday, July 9, 2014

Remastering Ubuntu 14.04

There have been some people who have complained about the functionality on 14.04 so we have tracked down the problems and here are some workarounds:

1.  You must be using the ext4 filesystems - 14.04 uses BTRFS by default, BTRFS was created after Black Lab Image Creator, what happens is that it doesnt know how to appropriately count the inodes in the BTRFS filesystem.  Before you ask, no, I dont intend to implement BTRFS support, I dont have the motivation or time to do this.  We did implement XFS support in 1.3 because of the commercial release thats in Black Lab Linux for Enterprise so customers can clone their Red Hat 7 and Oracle 7 installs so we filtered that down to 1.3.  If you are knowledgeable enough to use this tool, then you are knowledge enough to format your drive in ext4 or in 1.3 XFS.

2.  Do not deb copy the 1.3 install in Black Lab Linux 5.1 - ALPHA, it is tuned to Black Lab Linux and will not work on any other distribution, please wait for the official release next week.  Do not deb copy from BLL 5.1 Alpha and then cuss me out that it doesnt work, you have been warned.

3.  If you use sudo BlackLabImager disk in 1.3 it uses destructive partitioning, it will ignore any partition requests that you may make to the installer.  Its designed to do this.  This is for Red Hat 7 and Oracle 7.  To remaster Red Hat 7 or Oracle 7 you must do it from a LiveCD session rather than from an installed system.  It will break.

4.  Black Lab Image Creator 1.3 will work with Black Lab Linux 5.1 onwards and Ubuntu 14.04.  Do not use it for Ubuntu 12.04.  Ubuntu 12.04 users should use Black Lab Image Creator 1.1 or the legacy remastersys 3.04.  This is because some of the packages have changed in 14.04 and dont exist in 12.04 if you use remastersys or BLIC 1.1 in Ubuntu 14.04 make sure you install discover, sudo apt-get install discover.

5.  EFI support - No, quit asking.  Its not gonna happen.  Disable secureboot, or install with Secureboot disabled and install the signed kernels from the installed system.  I have no motivation or time to implement UEFI support.

Friday, July 4, 2014

Black Lab Image Creator 1.3 coming in 2 weeks

Hey folks,

We have finished on the latest round of bug fixes for Black Lab Image Creator 1.3 and will be releasing an updated bundle on that day.  We are also working on packaging in Deb format to make the installation easier.

Saturday, March 1, 2014

Black Lab Imager 1.1 Source Code available today

Today we are releasing the source code for Black Lab Imager, a utility for creating a backup of your system in a redistributable ISO or backup copy for your own use.  As you guys recall we have forked this over from Remastersys.

Now, we lack a GUI because Fragadelic did not give us the source code as promised so for right now its command line only.  We havent debanized the project files yet because we are still in the process of testing and building but we believe we have reached a level of stability that we are confident in its performance.

Why are we releasing the source code only?  We are still testing this release on 14.04 although users can contact us and let us know what works, what doesnt, and any fixes they may have in mind

How do I install this?  Right now because its not debainized, copy the blacklabimager folder and blacklabimager.conf file over to /etc/ and copy the blacklabimager and blacklabimager-skelcopy scripts over to /opt/  also make sure you run the dependencies script to download and install all your dependencies.

Where is the GUI?  When Fragadelic left he did not give me the source code for the GUI, so we will be making one ourselves outside of our webmin plugin.

What systems has this been tested with?  Black Lab Linux 4.x, Ubuntu 12.x, Ubuntu 13.x partially tested on Ubuntu 14.x.  What do we mean by partially?  We have rebuilt Xubuntu 14.04 and not pure Ubuntu

You guys can download the source code from sourceforge


For some reason Sourceforge keeps saying its pending, so we have uploaded the file to an alternate download section

Friday, August 2, 2013

Remastersys / System Imager source code availability and license changes

It has come to my attention that Fragadelic has started charging $50.00 USD for the source code for Remastersys.  With all due respect to Tony, we completely disagree with that decision.  Since he doesnt develop Remastersys anymore and hasnt put up his promised updates well, its time for us to act.  As of Saturday, August 3rd 2013 at 2:00 am.  The PC OpenSystems team has released the source code for his last update, Remastersys 3.0.4-2 and hereby license that source code and the source code for System Imager 1.0 under the GNU GPLv2 source license.  All recipients of the Remastersys and System Imager source code are granted all rights and privileges as any other GNU GPLv2 source code, including the rights to modify and redistribute that code.

We do hope Fragadelic does join us and releases the source code for the GUI wrapper although we are not expecting him too.  Nonetheless a new GUI is being developed with System Imager

You can download the source code here

Friday, July 19, 2013

System Imager 1.0 released for OS/4 Enterprise Linux 4.1.3 and status

Ok, so I finished System Imager 1.0 and I released it with OS/4 Enterprise Linux 4.1.3.   Its a great piece of work and we have made it so you dont have to worry about what kernel you are running, as long as you have the squashfs modules built it will boot your image.   We have tested it on Ubuntu 13.04 and we have had preliminary success.  We are comfortable now after our Enterprise customers have tested it to say its ready for public consumption.

I have had some people ask me,  "How come you released it in OS/4 Enterprise, but you havent released it for Ubuntu or Red Hat."  First, we did it for Enterprise because we integrated it with our release of Webmin, so users can create images of their servers and install across multiple servers and we integrated it into our proprietary Disk utility.  Second, NO ONE contributed code, ideas or cash.  We got a lot of feature requests and those will be worked on when time permits.  We are releasing the Disk Utility integrated with OS/4 OpenLinux 13.6 and we will work on the others when time permits.  When we get done with our SPARC port of OS/4 Enterprise Linux we will work on System Imager for Ubuntu and Red Hat.  But, when I have to fund development myself, and work on it myself then sorry guys, it goes into my own product first.  We are committed to doing a build for Ubuntu and Debian and Red Hat, which wont be integrated into those three it will be more like the approach  Remastersys took.