[mythtv-users] Bind mount to keep mythtv files in one place?
Stephen Worthington
stephen_agent at jsw.gen.nz
Fri Nov 30 16:18:10 UTC 2018
On Fri, 30 Nov 2018 07:30:26 -0600, you wrote:
>On Fri, Nov 30, 2018 at 2:12 AM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Fri, 30 Nov 2018 08:07:45 +0530, you wrote:
>>
>> >On Fri, 30 Nov 2018 07:28 Richard Shaw <hobbes1069 at gmail.com wrote:
>> >
>> >> Anyone see other options?
>> >>
>> >
>> >Or create symbolic links in /var on the new SSD pointing to the correct
>> >directories on the old HD mounted under /mnt, e.g.:
>> >
>> >cd /var
>> >sudo ln - s /mnt/oldhd/pictures .
>> >sudo ln - s /mnt/oldhd/mythvideos .
>> >sudo ln - s /mnt/oldhd/mythmusic .
>> >
>> >Cheers, Ian
>>
>> Actually, there is no need to do anything so complicated. All those
>> directories can simply be changed in the MythTV settings. And those
>> settings are now out of date, as all of them can also be set up as
>> storage groups now. So you should probably just go into mythtv-setup
>> > Storage Groups and add the groups you need. Note that storage
>> groups are referenced from the backend - the data is sent to
>> mythfrontend from mythbackend, and mythbackend accesses the
>> directories. The old settings are used by mythfrontend to directly
>> access the directories, so if you are running separate frontends, you
>> need to have network paths to access the data if it is actually stored
>> on the backend box.
>>
>
>Well, my question is more about the file system hierarchy than mythtv
>settings. I am using Storage Groups but I'd like to stay within the
>defaults of the RPM Fusion package (which I help maintain) if possible.
>
>It could be that it's wildly out of date but it's also very difficult to
>migrate major changes automagically for users so thing tend to stay the way
>they're established.
>
>I may need to do a "fresh" install in a VM so I can see how things default.
>My combined FE/BE installation is >10 years old at this point.
>
>The problem is there is not a single "root" folder for mythtv the way it's
>currently packaged. It could have been:
>
>/var/lib/mythtv/{pictures,mythmusic,mythvideos,recordings}
>
>Which would have given me a single directory to tie things in but instead
>it's:
>
>/var/lib/{pictures,mythmusic,mythvideos,recordings}
>
>Plus a bunch of other stuff in /var/lib...
>
>So it looks like the simplest solution if I don't want to move things
>around is my original idea.
>
>Thanks,
>Richard
You are still misunderstanding. Using the storage groups the way
MythTV is designed allows you to put things wherever you want. Just
move them to where you want them, then point the storage groups to
where they are. That is the correct and simplest solution. That is
the way MytTV is designed to work. Things in MythTV are not designed
to have a single "root" directory, as that has far too many
limitations and problems. The initial setup provided by the packages
is just so that MythTV will work when it is installed. It is not
intended to be the way a real system is set up - it does not work well
as things scale up.
My system is way too big to have everything on one drive. I have
seven recording drives and three video drives, for example. That is
easy with storage groups - just add each new partition on each drive
as one entry in the appropriate storage groups. I have two locations
where I store pictures - one for all my camera photos and one for
downloads. They are on different drives, with an entry in the storage
group for each location.
In Ubuntu, the packages install the initial setup in /var/lib/mythtv,
as you have suggested. But there is no need at all to keep things
there. It seems that the packages you are using do it differently,
but there is still no need to keep using those locations. Just put
things where ever *you* want them.
More information about the mythtv-users
mailing list