Author Topic: FYI: OS4 forked Remastersys!  (Read 2072 times)

ozitraveller

  • Posts: 385
    • View Profile
    • Star
FYI: OS4 forked Remastersys!
« on: April 29, 2013, 11:45:09 PM »
http://distrowatch.com/weekly.php?issue=20130429#news

Among the developers of many Debian-based Linux distribution the Remastersys utility is a well-known tool that facilitates the creation of customised live CD and DVD images. Following the recent unexpected announcement about the developer's decision to stop all work on Remastersys (without giving any concrete reason), OS4's Roberto Dohnert brings us some good news. He has decided to fork Remastersys and to continue developing the tool under the name of "System Imager": "OK guys, as many of you know Fragadelic who created Remastersys has decided to quit. Myself and Tony (aka Fragadelic) have decided that we here at OS4 will continue to develop and use the great tool that is Remastersys. We are changing the name to System Imager as per his request. To do this it's going to take some financial backing so any donations you guys can make, $5 to $10 to as much as you want to make will be appreciated and helpful. We also need some developers for System Imager. If you guys wish to help drop me an e-mail." On a separate note, the founder of OS4 also announced that future versions of the distributions would no longer be based on Ubuntu, but on Debian GNU/Linux.

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: FYI: OS4 forked Remastersys!
« Reply #1 on: April 29, 2013, 11:52:12 PM »
I have used Remastersys for VSIDO and used to stand by it proudly, but after recent developments (being on the shit end of someone with an ax to grind which led to the 'without giving any concrete reason') and the announcement that OS4 needs developers and money to begin, I do not see a bright future for it

I need to talk to you Ozi, when you get time to run some ideas by you on how your builds are going with debian-live
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

ozitraveller

  • Posts: 385
    • View Profile
    • Star
Re: FYI: OS4 forked Remastersys!
« Reply #2 on: April 30, 2013, 01:35:23 AM »
I've got a debian sid laptop that I used for the first test build.

I'm in the process of setting up a wheezy VM to be my build machine. I want stable live-build scripts. I've done a couple of test builds, which haven't worked, because I've missed some dependent package for grub. Once setup I should be able to build an image for just about any type of hardware.

I tried the kali scripts but had a problem trying to build with cdebootstrap. And checking their forums other have the problem too.

Would Philip be willing to devulge his secrets?

I found this,
Create a Custom Debian Live Environment (CD or USB)
http://blog.willhaley.com/create-a-custom-debian-live-environment/#comments

Use debian-live to Create Customized PXE Live Debian
http://onebitbug.me/2011/04/06/use-debian-live-to-create-customized-pxe-live-debian/

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: FYI: OS4 forked Remastersys!
« Reply #3 on: April 30, 2013, 01:43:29 AM »
I have asked Philip before and never got an answer

It is like a State Secret

My issues are with SID and the installer, they do not seem to work at all

I like what I see from the link you posted and have tried most of what he has detailed.  The issue I see is knowing and then listing every single app I need that makes VSIDO what it is

The file system of VSIDO is a little over 4 gig... thats a lot of apps!
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

ozitraveller

  • Posts: 385
    • View Profile
    • Star
Re: FYI: OS4 forked Remastersys!
« Reply #4 on: April 30, 2013, 02:25:24 AM »
You've probably seen this before too
Code: [Select]
dpkg-query -lhttp://wiki.debian.org/ListInstalledPackages

Code: [Select]
dpkg --get-selections > /backup/installed-software.log
dpkg --set-selections < /backup/installed-software.log
aptitude install $(cat /backup/installed-software.log)

When I was creating the build on sid I specified the installer should be from wheezy. I had problems when  I let it default to sid, and maybe it's broken in the sid repo.

I have thought of trying to copy what the kali people do, without success, so far.