[mythtv-users] Move to new master backend
msmall at eastlink.ca
Wed Nov 18 23:16:49 UTC 2009
On November 18, 2009 16:11:51 Johnny Walker wrote:
> I think in that case the only diferrence is the actual kernel. If my
> memory serves me, I was advised in debian to use aptitude to download
> the new kernel on the old hardware and then set the boot.1st file to
> point at that new kernel and shutdown. After that you can move the hdd
> (or use dd to create an image and move that) to the new machine and
> boot back up with the new kernel.
> You'd have to recompile anything that was based on your previous kernel
> You still don't have to start from scratch.
> Hope this helps.
Since ARM is completely different from X86, all binaries would need to be
replaced, not just the kernel. A drive swap just won't do the job.
Thankfully I've gotten some good hints from the list. I'll do the transfer
sometime in the next week or so.
This whole project should allow me to turn off the 110W backend for about 20
hours a day and run a 10-15 W backend in its place. At that rate, the new
box will pay for itself a few years. My office will be a whole lot quieter
> On Wed, Nov 18, 2009 at 2:03 PM, Mark J. Small <msmall at eastlink.ca> wrote:
> > On November 18, 2009, Johnny Walker wrote:
> >> One of the great things about most Linux distros is that you can
> >> simply move the HDD into the new box and it will most likely boot
> >> right up. There's no complicated HAL (Hardware Abstraction Layer)
> >> workaround needed to migrate an install to new hardware.
> >> Is this what you were asking?
> > That's what I did on my last 2 upgrades, but now I'm changing
> > architectures so a drive swap won't work for me. The new frontend is an
> > ARM powered NAS (QNAP TS-219P, same processor as the sheevaplug) The old
> > backend will become a slave backend, powered on demand to do the heavy
> > lifting (commflagging, some recording).
> > BTW, I'm running debian stable, using the debian-multimedia.org repos for
> > now. I may have to roll my own for 0.22.
> > Thanks though,
> > Mark
> >> On Wed, Nov 18, 2009 at 1:10 PM, Mark J. Small <msmall at eastlink.ca>
> >> > Hi everybody,
> >> >
> >> > I'm planning to move my current mythtv backend to a new box. What is
> >> > the best method? Do I simply back up the database, install myth on
> >> > the new box, copy the existing recordings and restore the database
> >> > there?
> >> >
> >> > Also, I currently have 3 disks for storage, set up as /mnt/store,
> >> > /mnt/big, and /mnt/huge. On the new box, I will only have 2 disks for
> >> > now. Do I have to recreate all 3 folders? Are the recordings tied to
> >> > the file location in some way, or just the file names.
> >> >
> >> > Any advice would be appreciated.
> >> >
> >> > Mark
> >> > _______________________________________________
> >> > mythtv-users mailing list
> >> > mythtv-users at mythtv.org
> >> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >> _______________________________________________
> >> mythtv-users mailing list
> >> mythtv-users at mythtv.org
> >> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users