rPath Linux:Migrating to rPath Linux 2
From rPath Wiki
Migrating An Appliance You Maintain
RPL-2083 has some initial information on how to convert an rPL1-based appliance into an rPL2-based appliance.
One of the changes in rPath Linux 2 is that it uses the newer "libata" modules to access ATA (PATA and SATA) hard drives. Note that when you migrate an existing appliance based on rPath Linux 1 to a new software version based on rPath Linux 2, it will convert all necessary files to reference the hard drives via device names that continue to work even if the appropriate driver for the hardware changes.
Q&A
For now, some core questions and answers. If you have a question that is not answered here, please add your question to the discussion page, or contact info@rpath.com for more details.
Q: I'm currently using rPath Linux as my desktop; what should I do?
A: Foresight Linux is the most widely-used Conary-based desktop distribution available. Most developers at rPath prefer it for their own desktop development environment.
Q: I'm building an appliance and want to make sure rPath takes my needs into account; what should I do?
A: Please browse our online issue tracker at https://issues.rpath.com/ and feel free to file new issues with suggestions. If you want more direct input, our sales staff at info@rpath.com are always willing to talk with you!
Q: I'm an appliance developer. Do I have to change my groups? My group currently references group-core from rPath Linux 1. What should I do?
A: rPath Linux 1 and rPath Linux 2 both have a group called group-appliance-platform which will be our recommended base for appliances. It adds several management tools, and will include the rPath Appliance Platform Agent (rAPA, formerly known as rAA). In addition, both rPath Linux 1 and rPath Linux 2 contain a superclass called group-appliance which is designed to make the process of maintaining an appliance much simpler.
Q: What does this do to my deployed units? Do my users have to know anything about this?
A: When you choose to migrate your appliance to be based on rPath Linux 2, the change should be generally invisible to your users, except that you will be able to make use of new features. That is, your users should have an even better appliance experience, but the migration process should be painless.
Q: What about rPath Linux 1? Will you continue to maintain it? How soon do I have to adapt?
A: Relax, you have plenty of time. rPath will continue to publish maintenance updates to rPath Linux 1 for at least six months after rPath Linux 2 has been released. If you require maintenance of rPath Linux 1 for a longer period of time, contact info@rpath.com.
Conary makes it easy for you to make whatever modifications you want even after that time, but we hope that rPath Linux 2 features are so compelling that you will want to move forward!
Q: I have shadowed from rPath Linux 1. What do I need to do? Do I have to re-shadow?
A: We recommend building a new version (major or minor revision) of your product based on rPath Linux 2, when you are ready for your appliance's consumers to move to an rPath Linux 2 base. For example, if you currently have built your appliance on example.rpath.org@example:myproduct-1 based on rPath Linux 1, you might build a minor revision on example.rpath.org@example:myproduct-1.1 or you might build a major new version on example.rpath.org@example:myproduct-2
Q: My question isn't here!
A: That's not a question, but please add your questions on the discussion page.