Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Disk Space Way Wrong

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


treythompson at gmail

Apr 19, 2012, 7:20 AM

Post #1 of 74 (2944 views)
Permalink
Disk Space Way Wrong

I've got myth installed on a compact flash card, and a 2TB SATA drive for
media. There's currently nothing at all on the sata drive except the
directories.

On the system status pages (Mythweb and the Mac FrontEnd and the Ubuntu
Frontend, it says:
Total Space: 1,905,900 MB (Looks good)
Space Used: 124,701 MB (um, where?!)

A df -k and a du both show about 29GB in use on my sata drive.

??


mythtv-users at lists

Apr 19, 2012, 8:13 AM

Post #2 of 74 (2887 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Trey Thompson wrote:
> I've got myth installed on a compact flash card, and a 2TB SATA drive
> for media. There's currently nothing at all on the sata drive except
> the directories.
>
> On the system status pages (Mythweb and the Mac FrontEnd and the Ubuntu
> Frontend, it says:
> Total Space: 1,905,900 MB (Looks good)
> Space Used: 124,701 MB (um, where?!)
>
> A df -k and a du both show about 29GB in use on my sata drive.
>
> ??

Shot in the dark, 5% reserved space?

What does "du --max-depth 1 /mount_point" say?

You can change the amount of the reserved space with tune2fs.

HTH
Thomas
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


treythompson at gmail

Apr 19, 2012, 8:30 AM

Post #3 of 74 (2877 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Thu, Apr 19, 2012 at 10:13 AM, Thomas Boehm <
mythtv-users [at] lists> wrote:

> Trey Thompson wrote:
> > I've got myth installed on a compact flash card, and a 2TB SATA drive
> > for media. There's currently nothing at all on the sata drive except
> > the directories.
> >
> > On the system status pages (Mythweb and the Mac FrontEnd and the Ubuntu
> > Frontend, it says:
> > Total Space: 1,905,900 MB (Looks good)
> > Space Used: 124,701 MB (um, where?!)
> >
> > A df -k and a du both show about 29GB in use on my sata drive.
> >
> > ??
>
> Shot in the dark, 5% reserved space?
>
> What does "du --max-depth 1 /mount_point" say?
>
> You can change the amount of the reserved space with tune2fs.
>
>
1036304 /media/sata1/mythtv
1036308 /media/sata1

I don't need the space, and I'd hate to mess with the default reserved
space. I was really just curious.
Thanks for the info.


mythtv-users at lists

Apr 19, 2012, 8:35 AM

Post #4 of 74 (2875 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Trey Thompson wrote:
> On Thu, Apr 19, 2012 at 10:13 AM, Thomas Boehm wrote:
> What does "du --max-depth 1 /mount_point" say?
>
> You can change the amount of the reserved space with tune2fs.
>
>
> 1036304/media/sata1/mythtv
> 1036308/media/sata1
>
> I don't need the space, and I'd hate to mess with the default reserved
> space. I was really just curious.
> Thanks for the info.

If this filesystem is only used for data, it's save to set the reserved
space to 0. Why wasting 124 GB?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


drescherjm at gmail

Apr 19, 2012, 8:46 AM

Post #5 of 74 (2874 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

> If this filesystem is only used for data, it's save to set the reserved
> space to 0. Why wasting 124 GB?

Agreed. Reserved space is there mostly for your root filesystem to
prevent users from filling the entire root preventing the OS from
working. It does not really help you for a data only disk.

John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 19, 2012, 8:47 AM

Post #6 of 74 (2871 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/19/2012 11:35, Thomas Boehm wrote:
> Trey Thompson wrote:
>> On Thu, Apr 19, 2012 at 10:13 AM, Thomas Boehm wrote:
>> What does "du --max-depth 1 /mount_point" say?
>>
>> You can change the amount of the reserved space with tune2fs.
>>
>>
>> 1036304/media/sata1/mythtv
>> 1036308/media/sata1
>>
>> I don't need the space, and I'd hate to mess with the default reserved
>> space. I was really just curious.
>> Thanks for the info.
> If this filesystem is only used for data, it's save to set the reserved
> space to 0. Why wasting 124 GB?

Traditionally, filesystems reserve 5-10% of the total space as a
mechanism to prevent fragmentation. With today's gigantic disks and
arrays, that could be a bit excessive, however setting it to zero is a
very bad idea.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv-users at lists

Apr 19, 2012, 9:06 AM

Post #7 of 74 (2876 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Raymond Wagner wrote:
> Traditionally, filesystems reserve 5-10% of the total space as a
> mechanism to prevent fragmentation. With today's gigantic disks and
> arrays, that could be a bit excessive, however setting it to zero is a
> very bad idea.

Not if you use xfs, set the "minimum free space" and run "xfs_db -rc
frag ..." every night ;-)

Ok, setting the reserved space to 1% on an ext4 filesystem should do...
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 19, 2012, 9:10 AM

Post #8 of 74 (2874 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/19/2012 12:06, Thomas Boehm wrote:
> Raymond Wagner wrote:
>> Traditionally, filesystems reserve 5-10% of the total space as a
>> mechanism to prevent fragmentation. With today's gigantic disks and
>> arrays, that could be a bit excessive, however setting it to zero is a
>> very bad idea.
> Not if you use xfs, set the "minimum free space" and run "xfs_db -rc
> frag ..." every night ;-)
>
> Ok, setting the reserved space to 1% on an ext4 filesystem should do...

I know at least for UFS on FreeBSD, dropping the reserved space below 8%
would cause the filesystem to switch strategies to one that was more
space efficient, but noticeably slower.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 19, 2012, 9:59 AM

Post #9 of 74 (2876 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-19 10:20 AM, Trey Thompson wrote:
> I've got myth installed on a compact flash card, and a 2TB SATA drive for media. There's currently
> nothing at all on the sata drive except the directories.
>
> On the system status pages (Mythweb and the Mac FrontEnd and the Ubuntu Frontend, it says:
> Total Space: 1,905,900 MB (Looks good)
> Space Used: 124,701 MB (um, where?!)
>
> A df -k and a du both show about 29GB in use on my sata drive.

Most likely it's the old bug whereby Mythtv shows the space free
on the root filesystem rather than on the filesystem where
recordings are kept.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gjhurlbu at gmail

Apr 19, 2012, 7:04 PM

Post #10 of 74 (2858 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord <mythtv [at] rtr> wrote:
> Most likely it's the old bug whereby Mythtv shows the space free
> on the root filesystem rather than on the filesystem where
> recordings are kept.

What old bug is that? I do not recall ever having seen this. Got a
trac ticket number?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 19, 2012, 7:35 PM

Post #11 of 74 (2854 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord <mythtv [at] rtr> wrote:
>> Most likely it's the old bug whereby Mythtv shows the space free
>> on the root filesystem rather than on the filesystem where
>> recordings are kept.
>
> What old bug is that? I do not recall ever having seen this. Got a
> trac ticket number?

Nope. It just reports wrong on every system I've set up,
always showing the root partition free space instead of
where the recordings are kept.

I think perhaps it trips up on symlinks or something.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


linux at thehobsons

Apr 19, 2012, 11:59 PM

Post #12 of 74 (2857 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Mark Lord wrote:

>Nope. It just reports wrong on every system I've set up,
>always showing the root partition free space instead of
>where the recordings are kept.
>
>I think perhaps it trips up on symlinks or something.

Mine is working fine. But have you perhaps set the storage group to a
location which is on the root volume, but is actually a symlink to
another drive (or some variation of that) ? I could see that tripping
it up.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 20, 2012, 6:02 AM

Post #13 of 74 (2844 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/19/2012 22:35, Mark Lord wrote:
> On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
>> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord<mythtv [at] rtr> wrote:
>>> Most likely it's the old bug whereby Mythtv shows the space free
>>> on the root filesystem rather than on the filesystem where
>>> recordings are kept.
>> What old bug is that? I do not recall ever having seen this. Got a
>> trac ticket number?
> Nope. It just reports wrong on every system I've set up,
> always showing the root partition free space instead of
> where the recordings are kept.
>
> I think perhaps it trips up on symlinks or something.

Here is the code in question.

https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythbase/mythcoreutil.cpp#L39

It's not doing anything fancy, it just runs statfs on the path you give
it. If that path lies on some other filesystem, and you're tricking it
with symlinks, it makes no attempt to outsmart you.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 8:58 AM

Post #14 of 74 (2840 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 09:02 AM, Raymond Wagner wrote:
> On 4/19/2012 22:35, Mark Lord wrote:
>> On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
>>> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord<mythtv [at] rtr> wrote:
>>>> Most likely it's the old bug whereby Mythtv shows the space free
>>>> on the root filesystem rather than on the filesystem where
>>>> recordings are kept.
>>> What old bug is that? I do not recall ever having seen this. Got a
>>> trac ticket number?
>> Nope. It just reports wrong on every system I've set up,
>> always showing the root partition free space instead of
>> where the recordings are kept.
>>
>> I think perhaps it trips up on symlinks or something.
>
> Here is the code in question.
>
> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythbase/mythcoreutil.cpp#L39
>
> It's not doing anything fancy, it just runs statfs on the path you give it.

There's the bug. It should open the path, and the use fstatfs(fd, ..).
Doing it that way would make symlinks transparent to it, as they should be.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 9:20 AM

Post #15 of 74 (2843 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 11:58 AM, Mark Lord wrote:
> On 12-04-20 09:02 AM, Raymond Wagner wrote:
>> On 4/19/2012 22:35, Mark Lord wrote:
>>> On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
>>>> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord<mythtv [at] rtr> wrote:
>>>>> Most likely it's the old bug whereby Mythtv shows the space free
>>>>> on the root filesystem rather than on the filesystem where
>>>>> recordings are kept.
>>>> What old bug is that? I do not recall ever having seen this. Got a
>>>> trac ticket number?
>>> Nope. It just reports wrong on every system I've set up,
>>> always showing the root partition free space instead of
>>> where the recordings are kept.
>>>
>>> I think perhaps it trips up on symlinks or something.
>>
>> Here is the code in question.
>>
>> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythbase/mythcoreutil.cpp#L39
>>
>> It's not doing anything fancy, it just runs statfs on the path you give it.
>
> There's the bug. It should open the path, and then use fstatfs(fd, ..).
> Doing it that way would make symlinks transparent to it, as they should be.

Like this, but undoubtedly prettier than this: :)

--- mythtv/libs/libmythdb/mythcoreutil.cpp.orig 2012-04-18 18:29:45.000000000 -0400
+++ mythtv/libs/libmythdb/mythcoreutil.cpp 2012-04-20 12:15:58.688776954 -0400
@@ -31,6 +31,19 @@
#include "mythverbose.h"
#include "unzip.h"

+int statfs_wrapper(const char *path, struct statfs *st)
+{
+ int ret, fd = open(path, O_RDONLY);
+
+ if (fd != -1) {
+ ret = fstatfs(fd, st);
+ close(fd);
+ if (ret != -1)
+ return ret;
+ }
+ return statfs(path, st);
+}
+
/** \fn getDiskSpace(const QString&,long long&,long long&)
* \brief Returns free space on disk containing file in KiB,
* or -1 if it does not succeed.
@@ -50,7 +63,7 @@
// others are invalid and set to 0 (such as when an automounted directory
// is not mounted but still visible because --ghost was used),
// so check to make sure we can have a total size > 0
- if ((statfs(cstr.constData(), &statbuf) == 0) &&
+ if ((statfs_wrapper(cstr.constData(), &statbuf) == 0) &&
(statbuf.f_blocks > 0) &&
(statbuf.f_bsize > 0))
{
--- mythtv/programs/mythbackend/mainserver.cpp.orig 2012-04-18 18:29:45.000000000 -0400
+++ mythtv/programs/mythbackend/mainserver.cpp 2012-04-20 12:15:46.298844076 -0400
@@ -4117,6 +4117,8 @@
return totalKBperMin;
}

+extern int statfs_wrapper(const char *path, struct statfs *buf); // libs/libmythdb/mythcoreutil.cpp
+
void MainServer::BackendQueryDiskSpace(QStringList &strlist, bool consolidated,
bool allHosts)
{
@@ -4179,7 +4181,7 @@
localStr = "1"; // Assume local
bSize = 0;

- if (!statfs(currentDir.toLocal8Bit().constData(), &statbuf))
+ if (!statfs_wrapper(currentDir.toLocal8Bit().constData(), &statbuf))
{
#if CONFIG_DARWIN
char *fstypename = statbuf.f_fstypename;
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 20, 2012, 9:32 AM

Post #16 of 74 (2841 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/20/2012 11:58, Mark Lord wrote:
> On 12-04-20 09:02 AM, Raymond Wagner wrote:
>> On 4/19/2012 22:35, Mark Lord wrote:
>>> On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
>>>> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord<mythtv [at] rtr> wrote:
>>>>> Most likely it's the old bug whereby Mythtv shows the space free
>>>>> on the root filesystem rather than on the filesystem where
>>>>> recordings are kept.
>>>> What old bug is that? I do not recall ever having seen this. Got a
>>>> trac ticket number?
>>> Nope. It just reports wrong on every system I've set up,
>>> always showing the root partition free space instead of
>>> where the recordings are kept.
>>>
>>> I think perhaps it trips up on symlinks or something.
>>
>> Here is the code in question.
>>
>> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythbase/mythcoreutil.cpp#L39
>>
>> It's not doing anything fancy, it just runs statfs on the path you give it.
>
> There's the bug. It should open the path, and the use fstatfs(fd, ..).
> Doing it that way would make symlinks transparent to it, as they should be.

So less a bug, and more a feature request (with a patch) for a strange
and uncommon configuration.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 9:40 AM

Post #17 of 74 (2848 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 12:32 PM, Raymond Wagner wrote:
> On 4/20/2012 11:58, Mark Lord wrote:
>> On 12-04-20 09:02 AM, Raymond Wagner wrote:
>>> On 4/19/2012 22:35, Mark Lord wrote:
>>>> On 12-04-19 10:04 PM, Gavin Hurlbut wrote:
>>>>> On Thu, Apr 19, 2012 at 9:59 AM, Mark Lord<mythtv [at] rtr> wrote:
>>>>>> Most likely it's the old bug whereby Mythtv shows the space free
>>>>>> on the root filesystem rather than on the filesystem where
>>>>>> recordings are kept.
>>>>> What old bug is that? I do not recall ever having seen this. Got a
>>>>> trac ticket number?
>>>> Nope. It just reports wrong on every system I've set up,
>>>> always showing the root partition free space instead of
>>>> where the recordings are kept.
>>>>
>>>> I think perhaps it trips up on symlinks or something.
>>>
>>> Here is the code in question.
>>>
>>> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythbase/mythcoreutil.cpp#L39
>>>
>>> It's not doing anything fancy, it just runs statfs on the path you give it.
>>
>> There's the bug. It should open the path, and the use fstatfs(fd, ..).
>> Doing it that way would make symlinks transparent to it, as they should be.
>
> So less a bug, and more a feature request (with a patch) for a strange and uncommon configuration.

All eight mythtv setups that I know about have the same style of configuration.

Symlinks are a "normal" (not "strange") thing on Linux,
and are often overlooked by folks more familiar with
only Microsoft systems (which lack them).

Fortunately, correctly written code rarely has to be bothered about them,
as they should be transparent. statfs() is one of the few syscalls that
doesn't follow them automatically (for good reason).

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 20, 2012, 9:51 AM

Post #18 of 74 (2842 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/20/2012 12:40, Mark Lord wrote:
>>>> It's not doing anything fancy, it just runs statfs on the path you give it.
>>> There's the bug. It should open the path, and the use fstatfs(fd, ..).
>>> Doing it that way would make symlinks transparent to it, as they should be.
>> So less a bug, and more a feature request (with a patch) for a strange and uncommon configuration.
> All eight mythtv setups that I know about have the same style of configuration.

So they're all strange. Why not just point MythTV directly at the
directory? MythTV only ever records to the root of the directory you
give it, so it's not like symlinking in multiple folders is going to get
you more storage space. You still have to define each in mythtv-setup.
It's not going to allow you to bypass some file permissions
restrictions. Even if you frequently move the mount location of those
storage drives, symlinks are only slightly more convenient to change
than the values in mythtv-setup.

I'm just not understanding what benefit doing it that way could provide.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 4:02 PM

Post #19 of 74 (2841 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 12:51 PM, Raymond Wagner wrote:
> On 4/20/2012 12:40, Mark Lord wrote:
>>>>> It's not doing anything fancy, it just runs statfs on the path you give it.
>>>> There's the bug. It should open the path, and the use fstatfs(fd, ..).
>>>> Doing it that way would make symlinks transparent to it, as they should be.
>>> So less a bug, and more a feature request (with a patch) for a strange and uncommon configuration.
>> All eight mythtv setups that I know about have the same style of configuration.
>
> So they're all strange. Why not just point MythTV directly at the directory? MythTV only ever
> records to the root of the directory you give it, so it's not like symlinking in multiple folders is
> going to get you more storage space. You still have to define each in mythtv-setup. It's not going
> to allow you to bypass some file permissions restrictions. Even if you frequently move the mount
> location of those storage drives, symlinks are only slightly more convenient to change than the
> values in mythtv-setup.
>
> I'm just not understanding what benefit doing it that way could provide.

It lets me move the storage directories around without having to
fuss with mythtv-setup and other places that might have a hardcoded path.

Symlinks are an incredibly useful feature, you should discover them someday.

Meanwhile, one more patch for the hundred or so workarounds already in my local tree.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jyavenard at gmail

Apr 20, 2012, 4:12 PM

Post #20 of 74 (2835 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 21 April 2012 09:02, Mark Lord <mythtv [at] rtr> wrote:
> Meanwhile, one more patch for the hundred or so workarounds already in my local tree.

Such constructive criticisms as usual...
which trac ticket and pull requests are you referring to ?

because surely, that's how you contribute no ?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 4:41 PM

Post #21 of 74 (2832 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 07:12 PM, Jean-Yves Avenard wrote:
> On 21 April 2012 09:02, Mark Lord <mythtv [at] rtr> wrote:
>> Meanwhile, one more patch for the hundred or so workarounds already in my local tree.
>
> Such constructive criticisms as usual...
> which trac ticket and pull requests are you referring to ?
>
> because surely, that's how you contribute no ?

No, I contribute by helping keep the kernel running
underneath all of this stuff. That's been both my hobby
and my day job for 20 years now.

For projects outside the kernel, I try to show people how to
use Linux correctly, and illustrate it with working code
and patches. Not with obscure tickets in a database somewhere.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jyavenard at gmail

Apr 20, 2012, 5:08 PM

Post #22 of 74 (2828 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 21 April 2012 09:41, Mark Lord <mythtv [at] rtr> wrote:
> For projects outside the kernel, I try to show people how to
> use Linux correctly, and illustrate it with working code
> and patches.  Not with obscure tickets in a database somewhere.

I see.. you're like Jesus, spreading the good word to whomever wants
to listen, but don't write anything :)

Your wisdom is so much appreciated.. Thanks again for showing people
"how to use Linux correctly". I'm sure that thanks to you MythTV has
progressed tremendously today, and probably all other days as well
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


zarthan at gmail

Apr 20, 2012, 5:25 PM

Post #23 of 74 (2832 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

No, I believe Mark is a Linux Kernel developer.


jyavenard at gmail

Apr 20, 2012, 6:04 PM

Post #24 of 74 (2829 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Saturday, 21 April 2012, Zarthan South wrote:

> No, I believe Mark is a Linux Kernel developer.


I'm very well aware of his contributions to the kernel and his work on
libata.
That doesn't prevent the fact that contributing a patch on trac or
submitting a pull request would take far less time than all this arguing
and complaining and would contribute much more to this project.


mythtv at rtr

Apr 20, 2012, 7:29 PM

Post #25 of 74 (2829 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 08:08 PM, Jean-Yves Avenard wrote:
> On 21 April 2012 09:41, Mark Lord <mythtv [at] rtr> wrote:
>> For projects outside the kernel, I try to show people how to
>> use Linux correctly, and illustrate it with working code
>> and patches. Not with obscure tickets in a database somewhere.
>
> I see.. you're like Jesus, spreading the good word to whomever wants
> to listen, but don't write anything :)

Yeah, my name I was born with.
If you prefer to mock it rather than just get along, that's fine.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 7:31 PM

Post #26 of 74 (2553 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 09:04 PM, Jean-Yves Avenard wrote:
>
>
> On Saturday, 21 April 2012, Zarthan South wrote:
>
> No, I believe Mark is a Linux Kernel developer.
>
>
> I'm very well aware of his contributions to the kernel and his work on libata.
> That doesn't prevent the fact that contributing a patch

Patch already contributed, earlier in this thread.
If you want it, then grab it, please.

For a casual user (that's what I am here) to figure out an entire new
system and drop the patch into the vast ignored pool of patches already
in trac would be a complete waste of my time.

But for somebody already "in the system", like you, it would be much simpler.
Go for it.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 20, 2012, 7:35 PM

Post #27 of 74 (2559 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-20 09:04 PM, Jean-Yves Avenard wrote:
>
>
> On Saturday, 21 April 2012, Zarthan South wrote:
>
> No, I believe Mark is a Linux Kernel developer.
>
>
> I'm very well aware of his contributions to the kernel and his work on libata.

I should take the opportunity to publicly thank-you for your recent audio work
in mythtv. I just pulled your 0.24-fixes branch the other day to get the 0.25 stuff,
and it works fairly well.

Once in a while (about 1/5) mythfrontend starts up without audio,
but that's only to be expected I suppose. I just quit and restart
the player and then it works second try.

Probably PulseAudio getting in the way -- so I've now removed pulseaudio
from the system and we'll see how things manage going forward.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gjhurlbu at gmail

Apr 20, 2012, 11:47 PM

Post #28 of 74 (2550 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Fri, Apr 20, 2012 at 7:31 PM, Mark Lord <mythtv [at] rtr> wrote:
> Patch already contributed, earlier in this thread.
> If you want it, then grab it, please.

As I'm sure you know, this isn't the chosen venue for patches for this
project. I don't care how other projects may do it, honestly, here we
try to use trac to track such things.

> For a casual user (that's what I am here) to figure out an entire new
> system and drop the patch into the vast ignored pool of patches already
> in trac would be a complete waste of my time.

Now you are claiming that you, who maintains "a hundred or so" patches
is a casual user? Hardly. You've already determined enough about the
codebase to make the patches. That and your bio from Linux Symposium
2010 claims you have the "most complex MythTV installation in the
world". You are not a "casual user". I dare say you likely aren't
even close on that other claim either.

Trac is hardly a "vast ignored pool of patches". Seems to me that
you're making this up as you go along, and with absolutely no
reference into reality. With 329 open tickets out of nearly 11000
tickets, most of which have no patches at all, you are certainly
mischaracterizing the nature of our trac setup. What this comes down
to is that you can't be bothered to contribute in a way that's helpful
to those running the project, but would prefer to take nasty sniping
shots at us as often as possible.

No, if there is a complete waste of time involved here, it wouldn't be
in you creating tickets.

> But for somebody already "in the system", like you, it would be much simpler.
> Go for it.

This is idiotic. You claim there is a bug, you don't report it, you
mumble about it much later on, and then waste everyone's time by
trying to pretend that you are better than everyone else, and that
putting in proper bug reports is beneath you. It is dead simple to
put in a bug report, and even to attach a ticket to it. Writing all
these emails saying it would be a waste of your time has taken you
more time than it would have to report the bugs you've found in a way
that benefits all.

Let me be very clear here: If you have identified up to "a hundred or
so" patches that you feel need to be in MythTV for proper operation,
by not submitting bug reports, you are doing a disservice to every
other user out there.

As for your condescending attitude about proper use of symlinks, I
barely know where to start. Excessive symlinks degrade system
performance, particularly when every open of every file in every
storage group will now take at least twice as long as it needs to
dereference the symlink and do yet another seek on the harddrive and
read yet another set of inodes. As someone who actually knows what
that means, I'm quite honestly shocked that you think it's correct
operating procedure to use symlinks instead of mount points for this
job, just to save you the few extra seconds to change paths in
mythtv-setup the few times that you DO move it.

What you should be doing is mounting the storage group file systems at
mount points where ever you want them, and not to move them around.
The fact that you want to move them around just screams out that you
don't know what you are doing as you feel you need to rearchitect your
filesystem structure, and apparently, repeatedly. Set it up the way
you want it, then set MythTV to point to the real mount points, then
leave it alone. It works for thousands of other users, what's so
special about your setup that would require otherwise?
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


lists at glidos

Apr 21, 2012, 12:19 AM

Post #29 of 74 (2564 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 21/04/2012 03:35, Mark Lord wrote:
> On 12-04-20 09:04 PM, Jean-Yves Avenard wrote:
>>
>>
>> On Saturday, 21 April 2012, Zarthan South wrote:
>>
>> No, I believe Mark is a Linux Kernel developer.
>>
>>
>> I'm very well aware of his contributions to the kernel and his work on libata.
>
> I should take the opportunity to publicly thank-you for your recent audio work
> in mythtv. I just pulled your 0.24-fixes branch the other day to get the 0.25 stuff,
> and it works fairly well.

Ok, while we are at it, make that a +1. I haven't managed to upgrade to
0.25 yet, but I've been using personal/jyavenard/backports/fixes/0.24
just to get some of the audio improvements.

Cheers,
Paul.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


linux at thehobsons

Apr 21, 2012, 12:53 AM

Post #30 of 74 (2556 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Gavin Hurlbut wrote:

<much good comment snipped>

> > But for somebody already "in the system", like you, it would be
>much simpler.
>> Go for it.
>
>This is idiotic. You claim there is a bug, you don't report it, you
>mumble about it much later on, and then waste everyone's time by
>trying to pretend that you are better than everyone else, and that
>putting in proper bug reports is beneath you.

I find myself wondering what response someone would get from the
kernel developers if he was (as you point out) most definitely not
ignorant about code, knew of a heap of bugs, had fixes for them, but
refused to submit either bug reports or the patches through the
proper channel.

I agree, does come across as a "better than you because I work on the
kernel" attitude.

<more good comment snipped>

I agree entirely with your well written rebuttal.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at rtr

Apr 21, 2012, 7:02 AM

Post #31 of 74 (2544 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 12-04-21 02:47 AM, Gavin Hurlbut wrote:
..
> Trac is hardly a "vast ignored pool of patches". Seems to me that
> you're making this up as you go along, and with absolutely no
> reference into reality. With 329 open tickets out of nearly 11000
> tickets, most of which have no patches at all, you are certainly
> mischaracterizing the nature of our trac setup. What this comes down
> to is that you can't be bothered to contribute in a way that's helpful
> to those running the project, but would prefer to take nasty sniping
> shots at us as often as possible.

The only people taking nasty shots at anyone here seem to be
folks like you, and the others here who misconstrue my intents
based upon the surname I was born with.

I found a bug, I posted code showing how to fix it.
That's all. On the kernel mailing lists, code like that would
be picked up by the maintainers and End of Story.

I'm not interested in spending a huge amount of time and effort
to figure out the trac system, the git system, and mostly the
people system that all have to be solved to actually get that
code into the mythtv code base.

It's just too much time and effort.
The barriers to entry are too high for the time I have available.

It's not that I don't contribute (I do, hugely, just not to the mythtv git repo),
nor is that I don't want to help. I do, otherwise I wouldn't post code
and help others on this list with issues.

So tone down your overreactions and perhaps try to get along.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ron at ronfrazier

Apr 21, 2012, 10:13 AM

Post #32 of 74 (2540 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

This thread makes me so sad. The way Mark has been responded to in
this thread is just uncalled for. He was nothing but respectful in
this thread, helped identify a problem, and even provided code to deal
with it. The only thing he said that was perhaps questionable was
"Symlinks are an incredibly useful feature, you should discover them
someday." That last part of that could certain be better worded, but I
took it as more tounge-in-cheek than insulting.

Meanwhile, he has been responded to by sarcastically comparing him to
Jesus, mocking for his attempts to contribute in the way he chooses,
told that he thinks he's better than everyone else, and told he
doesn't know what he's doing in organizing a file system. I understand
that some posters get pretty nasty around here in their bitching about
what a poor job they think the devs do, and it make some people around
here sensitive to comments. But what Mark posted was nothing like
that, and he did not deserve the response he got.

The comment about "hundred or so workarounds already in my local tree"
was not something I took as an attack on myth. I too have a bunch of
patches (though not 100). Some I submit. Other I attempt to discuss
for possible inclusion and don't get a positive response. Others I
just dont bother with because, frankly, you sort of get a feel for
what sorts of things the devs aren't interested in and don't want to
waste time debating the merits of something you think will go nowhere
(admittedly, I've been wrong in that assumption once). Other patches I
feel are for something very particular to what I want, or at the very
least would need to be configurable for other users taste and I just
don't feel like taking the time to add the config options to the setup
screens. Others patches are quite hacky and work for me, but they
aren't very clean and I'd be embarrassed to submit them. In short,
there are a lot of reason one would just hack together patches for
themselves and not submit it. But that's not some insult to the devs
to say that you do.

--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


briandlong at gmail

Apr 21, 2012, 10:46 AM

Post #33 of 74 (2535 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 1:13 PM, Ronald Frazier <ron [at] ronfrazier> wrote:

> This thread makes me so sad. The way Mark has been responded to in
> this thread is just uncalled for. He was nothing but respectful in
> this thread, helped identify a problem, and even provided code to deal
> with it. The only thing he said that was perhaps questionable was
> "Symlinks are an incredibly useful feature, you should discover them
> someday." That last part of that could certain be better worded, but I
> took it as more tounge-in-cheek than insulting.
>
> Meanwhile, he has been responded to by sarcastically comparing him to
> Jesus, mocking for his attempts to contribute in the way he chooses,
> told that he thinks he's better than everyone else, and told he
> doesn't know what he's doing in organizing a file system. I understand
> that some posters get pretty nasty around here in their bitching about
> what a poor job they think the devs do, and it make some people around
> here sensitive to comments. But what Mark posted was nothing like
> that, and he did not deserve the response he got.
>

+1. Let's just try to get along. MythTV is a great open-source project
and I've been privileged to use it for many years. It seems that recently
more and more arguments and general nastiness has broken out on this list
and it's not appreciated. If you don't have something nice to say, don't
say anything at all. :-)

/Brian/


raymond at wagnerrp

Apr 21, 2012, 11:48 AM

Post #34 of 74 (2533 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/21/2012 13:13, Ronald Frazier wrote:
> This thread makes me so sad. The way Mark has been responded to in
> this thread is just uncalled for.

So far, I agree with you completely. At some point the thread degraded
into just a bunch of character attacks from both sides. MythTV
developers should be showing a good public face to the community, and
partake when the discussion reaches that, as amusing as that may
sometimes be...

Example: http://www.gossamer-threads.com/lists/mythtv/dev/187438#187438

On the other hand, if Mark Lord is going to invoke his authoritative
knowledge as a long time kernel developer involved in storage interface
drivers, he should be held to no less of a standard of behavior.

> He was nothing but respectful in this thread, helped identify a problem, and even provided code to deal with it.

At first, yes, however this whole thread started due to his mention of
an "old bug" that none of us had even heard of.

On 4/20/2012 12:40, Mark Lord wrote:
> Symlinks are a "normal" (not "strange") thing on Linux,
> and are often overlooked by folks more familiar with
> only Microsoft systems (which lack them).

This is where the discussion took a turn downhill. Mark "threw the
first punch", as it were. Now he may have meant this as a joke, but
from experience having been corrected by Mark in the past, many times
where he was correct, sometimes where he was not, Mark is never wrong.
This felt like an insult, as if I was a Windows weenie, not experienced
with using Linux. Admittedly, my OS of choice is FreeBSD, rather than
some blend of GNU/Linux, but that's besides the point as symlinks are a
POSIX standard not specific to Linux, and even Windows has support for them.

If there were a rational argument for allowing symlinks as storage
directories, I would gladly apply the patch. However, I just don't see
one, and the only argument for it was that it is how Mark configures his
systems. You can't argue with that, and since I am guilty of getting
into such character arguments in the past, I bowed out at this point.

> The comment about "hundred or so workarounds already in my local tree"
> was not something I took as an attack on myth. I too have a bunch of
> patches (though not 100). Some I submit. Other I attempt to discuss
> for possible inclusion and don't get a positive response. Others I
> just dont bother with because, frankly, you sort of get a feel for
> what sorts of things the devs aren't interested in and don't want to
> waste time debating the merits of something you think will go nowhere
> (admittedly, I've been wrong in that assumption once). Other patches I
> feel are for something very particular to what I want, or at the very
> least would need to be configurable for other users taste and I just
> don't feel like taking the time to add the config options to the setup
> screens. Others patches are quite hacky and work for me, but they
> aren't very clean and I'd be embarrassed to submit them. In short,
> there are a lot of reason one would just hack together patches for
> themselves and not submit it.

Maintaining your own patch set is perfectly fine. Maybe you are
tweaking behavior, or adding new features, in some manner that would not
have significant appeal. Maybe you are adding features that you know
would not be accepted upstream for whatever reason. Maybe you are using
assorted bug fixes for tickets still open on trac. The attack on Myth
was where he claimed it had bugs, knew what they were, but let that
knowledge sit for years without telling anyone so it could be fixed. No
doubt about it, MythTV is full of bugs, but we can't do anything about
it if we don't know where they are. Especially if they are induced by
some sufficiently strange configuration that no one else has experienced
them.

So going back to the original argument, is this a bug, or is it merely
an unsupported configuration? Now one could argue that even if it isn't
supported now, it should be, the the better question is, is there any
reason to try to record to a symlinked directory? The argument for says
that it allows you to conveniently and quickly reorganize your
filesystem structure. The argument against is that MythTV's storage
directories allow you to reorganize your filesystem just as well. Just
run mythtv-setup, spend a few seconds typing in a new path, and you're done.

Now one might not have a partition or disk dedicated towards MythTV
recordings, they may have other content stored on it. Shifting that
around would mean one would have to update MythTV, as well as any other
applications that had content stored on that partition. However,
symlinks would work perfectly fine in this scenario. MythTV would not
be pointed at the symlink directly, but rather at some folder
transparently dereferenced inside that symlink.

That leaves the one scenario where you have symlinks pointed directly at
the recording directories AND you have applications other than MythTV
accessing those directories. This is where the disconnect occurs.
Those directories, and the contents contained therein, are MythTV's and
MythTV's alone. You don't care what's in there. You don't rename them,
besides to change the extension as part of transcoding. If you want to
access them with pretty names, use mythlink.pl to provide symlinks
directory to each recording in whatever format you desire. If you want
more programmatic access to the recordings, you hit the database
directly to discover the filename for the video you want, the defined
storage directories, and then search through them until you find the
absolute path to the recording.

In much shorter words, the patch is to make a particular configuration
work, whose only advantage is to make it easier to perform tasks that we
don't want users doing. Since the behavior is undesirable, there is no
point to the configuration from MythTV's standpoint, making it
unsupported. An unsupported configuration that causes certain things to
break is not a bug, just an unsupported configuration.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 21, 2012, 11:50 AM

Post #35 of 74 (2533 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/21/2012 14:48, Raymond Wagner wrote:
> MythTV developers should be showing a good public face to the
> community, and partake when the discussion reaches that

Make that "NOT partake".
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ron at ronfrazier

Apr 21, 2012, 12:50 PM

Post #36 of 74 (2538 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 2:48 PM, Raymond Wagner <raymond [at] wagnerrp> wrote:
>> He was nothing but respectful in this thread, helped identify a problem,
>> and even provided code to deal with it.
>
>
> At first, yes, however this whole thread started due to his mention of an
> "old bug" that none of us had even heard of.

Saying something is an old bug is disrespectful? Sorry, but that's
just a statement of fact. It is an old bug. I too noticed it quite a
while ago. You know why I never reported it? It just wasn't that
important. I almost certainly was trying to do something at the time,
came across that at the time, said "that aint right", looked at it for
a few minutes, and then went about what I was originally trying to do.
I'll admit I often notice little bugs in software, but I don't halt
everything I'm working on to go report them on the spot. By the time
I'm done with what I'm really trying to do, the bug is far from my
mind.


>> Symlinks are a "normal" (not "strange") thing on Linux,
>> and are often overlooked by folks more familiar with
>> only Microsoft systems (which lack them).
>
>
> This is where the discussion took a turn downhill.  Mark "threw the first
> punch", as it were.   Now he may have meant this as a joke, but from
> experience having been corrected by Mark in the past, many times where he
> was correct, sometimes where he was not, Mark is never wrong.  This felt
> like an insult, as if I was a Windows weenie, not experienced with using
> Linux.  Admittedly, my OS of choice is FreeBSD, rather than some blend of
> GNU/Linux, but that's besides the point as symlinks are a POSIX standard not
> specific to Linux, and even Windows has support for them.

That's a pretty low bar for "the first punch". It is a fact that
windows people don't think about symlinks much. Windows does support
them...sort of. But their implementation is a lot less robust than in
linux, and for what they can do people just don't tend to use them
very often. But that doesn't say anything negative about a windows
user unfamiliar with them (in fact, if anything, you were the one who
just used the term "windows weenie"). It's just not something typical
among windows users. However, for a linux user, I do agree with Mark
that it's a bit odd for someone to consider use of symlinks to be an
odd configuration.


> If there were a rational argument for allowing symlinks as storage
> directories, I would gladly apply the patch.  However, I just don't see one,
> and the only argument for it was that it is how Mark configures his systems.

Wow. You need a rational argument? See, I can clearly see the
explanation that, you know, this isn't really a major issue, it
doesn't affect that many people, and I'm not going to take the time to
write a fix for it. That's perfectly valid. There are a million things
to do, and everyone has limited time, so we need to pick our battles.
But see, first mark is told he needs to go to the effort of making the
patch and creating the ticket, but then you turn around and suggest
you wouldn't apply it anyway unless someone can provide a good reason.
Can you see why some people don't want to go to the effort of
submitting bugs and patches?


> The attack on Myth was where he
> claimed it had bugs, knew what they were, but let that knowledge sit for
> years without telling anyone so it could be fixed.  No doubt about it,
> MythTV is full of bugs, but we can't do anything about it if we don't know
> where they are.  Especially if they are induced by some sufficiently strange
> configuration that no one else has experienced them.

Don't want to repeat myself here...I think this was already addresses
by my first paragraph above.


> So going back to the original argument, is this a bug, or is it merely an
> unsupported configuration?  Now one could argue that even if it isn't
> supported now, it should be, the the better question is, is there any reason
> to try to record to a symlinked directory?  The argument for says that it
> allows you to conveniently and quickly reorganize your filesystem structure.
>  The argument against is that MythTV's storage directories allow you to
> reorganize your filesystem just as well.  Just run mythtv-setup, spend a few
> seconds typing in a new path, and you're done.

I do 99% of my work on my mythbox from my windows system through SSH.
This is very convenient, and if I want to move a symlink, I can do it
in 5 seconds. If I want to change a storage group, my mythbox is in
the basement, tucked away in a corner where it is unobtrusive for the
family. Unfortunately, a side effect of that is that I don't have room
to leave a monitor hooked up. So I have to go downstairs, drag a
monitor over to it and hook it up, do what I need, and then put
everything away after I'm sure I've done. Now, when I need to do
something in mythtv-setup, that's fine. But when I can do something in
5 seconds instead of several minutes, I'm gonna spend the 5 seconds.
If this were some huge ugly hack, that would be one thing, but this is
pretty standard stuff.

As for the rest of what you said about why symlinks aren't a valid
configuration and you shouldn't even want to look at anything in the
folder and so on....I'm going to hugely disagree, but at this point I
don't even care enough to argue. It's not worth my time. But let me
summarize it like this. You complain because he never submitted a bug
report. If he had submitted a bug, you make it clear that it's not a
bug but a feature request. We all know how those get rejected if they
don't contain patches. However, if he had submitted the feature
request with patch, you would still shoot it down because you think
myth should purposely ignore symlinks because it's not a valid
configuration. So tell me, what COULD mark have done that would have
pleased you? Bug report? Rejected. Feature request? Rejected. Feature
request with patch? Rejected. So are you just upset that he didn't go
through the motions of making a futile request?


--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 21, 2012, 1:36 PM

Post #37 of 74 (2532 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/21/2012 15:50, Ronald Frazier wrote:
> You complain because he never submitted a bug report.

Correct. If he's going to go off telling people their issues are caused
by old known bugs, he needs to post a ticket so that we actually know
its a bug.

> If he had submitted a bug, you make it clear that it's not a
> bug but a feature request.

That's really up to the discretion of the person doing triage. If it's
a behavior we don't want MythTV to have, or use of MythTV in some manner
it is not supposed to operate, it would be closed Invalid or Won't Fix.
If it's a behavior we could see useful in MythTV, but outside the scope
of the existing programming, it would be closed as a Feature Request
Without Patch, or left open if patch was included. If it's something
MythTV is supposed to do, but is not doing it, it's a valid bug.

> However, if he had submitted the feature request with patch,
> you would still shoot it down because you think myth should
> purposely ignore symlinks because it's not a valid configuration.

In this case, he actually did provide a patch. However, for the
specific case of definition of recording storage, I don't see any
utility in being able to define it using symlinks. Consider recordings
as MythTV's own internal data, and all access to it must be done by
MythTV's rules. Doing otherwise would be like writing something that
directly tinkered with the binary files of a MySQL database. Sure you
can do it, but MySQL isn't going to support you doing so, or be
responsible if something goes wrong. If you're not supposed to be doing
it in the first place, why support a configuration that only serves to
aid such actions?

With things like videos, music, and artwork switching over to access
through storage groups, these are things that actually do make sense for
external access. If MythTV gains the ability to shuffle such content
around, and more specifically to shuffle it around to balance free space
between multiple partitions, this behavior will have to be revisited,
and at least within the context of non-recorded content, would become a
proper bug.

> So tell me, what COULD mark have done that would have pleased you?

If he comes across something he thinks is a bug, spend 30 seconds and
put a ticket up on Trac. He already spent enough time to figure out it
was his use of symlinks that caused it, which is plenty to figure out
where the problem lies. If there's not enough information to root out
or otherwise verify the issue, it gets marked as Info Needed, and closed
six weeks later if no response is given. He, or anyone else, could
respond to give enough information to properly describe it and keep the
ticket alive. At such point as the ticket is closed as invalid due to
an unsupported configuration, stop calling it a bug. It's not a bug,
it's an unsupported configuration that when used, is known to cause at
least <whatever> incorrect behavior.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


linux at thehobsons

Apr 21, 2012, 2:01 PM

Post #38 of 74 (2526 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Ronald Frazier wrote:

>I do 99% of my work on my mythbox from my windows system through SSH.

Ditto, apart from using a Mac rather than windows.

>... my mythbox is in the basement, tucked away in a corner where it
>is unobtrusive for the family. Unfortunately, a side effect of that
>is that I don't have room to leave a monitor hooked up.

Almost ditto - it's in a cupboard under the roof, it does actually
have an old tiny 10" screen attached but the only time I use that is
if I'm fiddling with it's boot setup etc. Haven't switched the
display on for some time - I could do without it but I'd only have to
find space elsewhere to store it.

>So I have to go downstairs, drag a monitor over to it and hook it
>up, do what I need, and then put everything away after I'm sure I've
>done. Now, when I need to do something in mythtv-setup, that's fine.
>But when I can do something in 5 seconds instead of several minutes,
>I'm gonna spend the 5 seconds.

Why do you waste all that time and effort ? I run mythtv-setup from
my desk - just "ssh -X <user [at] backen address>" and fire up
mythtv-setup. It fires up in an X session right here on my laptop.
OK, many many years ago you needed to "know incantations" to get
remote X displays working, but the "-X" (or "-Y") option in SSH does
it all automagically. It's built in to OS X, dunno what's needed to
make it work in Windows - but if you work with Unix-like system then
it's worth finding out.
I've run entire KDE desktops like this in the past.

It seems really odd when I do have to work on a real console, such as
when I've a machine that won't boot properly.


Having said that, I can see the point of symlinks (all them all the
time myself), but I find it hard to get excited about using them to
point Myth at it's storage directories. I can see why people might
want to use them, but if it matters to you, then you could pick up
the patch and submit it properly - as long as it doesn't break
anything then I'd imagine it could be taken up.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


michael at thewatsonfamily

Apr 21, 2012, 2:52 PM

Post #39 of 74 (2533 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22/04/2012 3:13 AM, Ronald Frazier wrote:
> This thread makes me so sad. The way Mark has been responded to in
> this thread is just uncalled for. He was nothing but respectful in
> this thread, helped identify a problem, and even provided code to deal
> with it. The only thing he said that was perhaps questionable was
> "Symlinks are an incredibly useful feature, you should discover them
> someday." That last part of that could certain be better worded, but I
> took it as more tounge-in-cheek than insulting.
>
> Meanwhile, he has been responded to by sarcastically comparing him to
> Jesus, mocking for his attempts to contribute in the way he chooses,
> told that he thinks he's better than everyone else, and told he
> doesn't know what he's doing in organizing a file system. I understand
> that some posters get pretty nasty around here in their bitching about
> what a poor job they think the devs do, and it make some people around
> here sensitive to comments. But what Mark posted was nothing like
> that, and he did not deserve the response he got.

I agree, and its a very disturbing/disappointing trend. Similar to the
somewhat unwarranted attack on Robert McNamara.

>
> The comment about "hundred or so workarounds already in my local tree"
> was not something I took as an attack on myth. I too have a bunch of
> patches (though not 100). Some I submit. Other I attempt to discuss
> for possible inclusion and don't get a positive response. Others I
> just dont bother with because, frankly, you sort of get a feel for
> what sorts of things the devs aren't interested in and don't want to
> waste time debating the merits of something you think will go nowhere
> (admittedly, I've been wrong in that assumption once). Other patches I
> feel are for something very particular to what I want, or at the very
> least would need to be configurable for other users taste and I just
> don't feel like taking the time to add the config options to the setup
> screens. Others patches are quite hacky and work for me, but they
> aren't very clean and I'd be embarrassed to submit them. In short,
> there are a lot of reason one would just hack together patches for
> themselves and not submit it. But that's not some insult to the devs
> to say that you do.
>

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 21, 2012, 2:54 PM

Post #40 of 74 (2532 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/21/2012 17:01, Simon Hobson wrote:
> It's built in to OS X, dunno what's needed to make it work in Windows
> - but if you work with Unix-like system then it's worth finding out.

Putty can be made to interface with Cygwin/X or Xming on Windows to do
the same kind of authentication, or you can forgo SSH tunneling, perform
the xauth or xhost behavior yourself, and point an xterm or otherwise
directly at your remote X server.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gary.buhrmaster at gmail

Apr 21, 2012, 2:59 PM

Post #41 of 74 (2527 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 13:36, Raymond Wagner <raymond [at] wagnerrp> wrote:
....
> Correct.  If he's going to go off telling people their issues are caused by
> old known bugs, he needs to post a ticket so that we actually know its a
> bug.

I cannot more strongly agree with this.

Unless someone wishes the developers to move to the next
phase, and become omniscient. It is not an issue until it
is in the (bug) tracking database. I have had this exact
discussion with many others. It is not going to be "known
to be broken" until it is documented. It is not going to get
"resourced" until it can be documented as broken.

> ....  It's not a bug, it's an unsupported
> configuration that when used, is known to cause at least <whatever>
> incorrect behavior.

Here is where I have a slight problem. If that space calculation
is used for decisions elsewhere in the code(s), which seems
likely, then the decision to do things like use the space,
or delete recordings, may be (wrongly) influenced by getting
the wrong values for free space. Debugging those cases takes
time too (whether on the users list, or the dev list, or as tickets
for people for which things "do not work right"). Either the codes
should not follow symlinks (that cross file system boundaries),
warn the user and not startup if unsupported configurations are
found, or to (try to) correctly calculate the (free) space which will
be used to influence other MythTV behavior. Pick your feature
request (without a patch :-).

Gary
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


michael at thewatsonfamily

Apr 21, 2012, 3:04 PM

Post #42 of 74 (2524 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22/04/2012 7:54 AM, Raymond Wagner wrote:
> On 4/21/2012 17:01, Simon Hobson wrote:
>> It's built in to OS X, dunno what's needed to make it work in Windows
>> - but if you work with Unix-like system then it's worth finding out.
>
> Putty can be made to interface with Cygwin/X or Xming on Windows to do
> the same kind of authentication, or you can forgo SSH tunneling,
> perform the xauth or xhost behavior yourself, and point an xterm or
> otherwise directly at your remote X server.
> _______________________________________________
Or simply use MobaXterm (Terminal client, with built in X Server)


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dl-mythtv at catspoiler

Apr 21, 2012, 3:14 PM

Post #43 of 74 (2525 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 21 Apr, Simon Hobson wrote:
> Ronald Frazier wrote:

>>So I have to go downstairs, drag a monitor over to it and hook it
>>up, do what I need, and then put everything away after I'm sure I've
>>done. Now, when I need to do something in mythtv-setup, that's fine.
>>But when I can do something in 5 seconds instead of several minutes,
>>I'm gonna spend the 5 seconds.
>
> Why do you waste all that time and effort ? I run mythtv-setup from
> my desk - just "ssh -X <user [at] backen address>" and fire up
> mythtv-setup. It fires up in an X session right here on my laptop.
> OK, many many years ago you needed to "know incantations" to get
> remote X displays working, but the "-X" (or "-Y") option in SSH does
> it all automagically.

Same here. I've got a combined FE/BE, but I still run mythtv-setup more
frequently from my desktop using ssh than I do from the living room
where the FE/BE and TV are located since my desktop has a much more
ergonomic configuration for using a keyboard than what I've got in the
living room.

My only complaints are that mythtv-setup paints the screen very slowly
over ssh, and it takes over the entire screen. I'm looking forward to
the upcoming switch to web based configuration.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Apr 21, 2012, 3:17 PM

Post #44 of 74 (2538 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 04/21/2012 06:14 PM, Don Lewis wrote:
> On 21 Apr, Simon Hobson wrote:
>> Ronald Frazier wrote:
>>> So I have to go downstairs, drag a monitor over to it and hook it
>>> up, do what I need, and then put everything away after I'm sure I've
>>> done. Now, when I need to do something in mythtv-setup, that's fine.
>>> But when I can do something in 5 seconds instead of several minutes,
>>> I'm gonna spend the 5 seconds.
>> Why do you waste all that time and effort ? I run mythtv-setup from
>> my desk - just "ssh -X<user [at] backen address>" and fire up
>> mythtv-setup. It fires up in an X session right here on my laptop.
>> OK, many many years ago you needed to "know incantations" to get
>> remote X displays working, but the "-X" (or "-Y") option in SSH does
>> it all automagically.
> Same here. I've got a combined FE/BE, but I still run mythtv-setup more
> frequently from my desktop using ssh than I do from the living room
> where the FE/BE and TV are located since my desktop has a much more
> ergonomic configuration for using a keyboard than what I've got in the
> living room.
>
> My only complaints are that mythtv-setup paints the screen very slowly
> over ssh, and it takes over the entire screen. I'm looking forward to
> the upcoming switch to web based configuration.

Set your Paint engine in 0.25+ to auto and start mythtv-setup with
-geometry 800x600 (or 1280x720 or whatever)...

Note that auto is not the default--because of all the broken
hardware/drivers/configurations on which OpenGL says it will work, but
doesn't.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ron at ronfrazier

Apr 21, 2012, 3:20 PM

Post #45 of 74 (2523 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 5:01 PM, Simon Hobson <linux [at] thehobsons> wrote:
> Why do you waste all that time and effort ? I run mythtv-setup from my desk
> - just "ssh -X <user [at] backen address>" and fire up mythtv-setup. It fires up
> in an X session right here on my laptop.
> OK, many many years ago you needed to "know incantations" to get remote X
> displays working, but the "-X" (or "-Y") option in SSH does it all
> automagically. It's built in to OS X, dunno what's needed to make it work in
> Windows - but if you work with Unix-like system then it's worth finding out.
> I've run entire KDE desktops like this in the past.

Unforunately, Windopws isn't nearly as friendly as OSX in that
respect. There's no built in support for it, so you have to rely on
3rd party software. I'll admit it's been a number of years since I
last tried, but last time I successfully did it, I found it to be a
huge pain to setup and configure, and it didn't perform very well.
Maybe things have changed since, but I sort of wrote it off back then
due to the unpleasant experience. Guess you could say it scarred me
for life :-) Maybe it's worth getting over my aversion and trying
again, but for as rarely as I need to do so (more often I need to get
into the bios or something) it just never seems worth the trouble of
trying.



--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


gary.buhrmaster at gmail

Apr 21, 2012, 3:31 PM

Post #46 of 74 (2524 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 15:20, Ronald Frazier <ron [at] ronfrazier> wrote:
> ... Maybe it's worth getting over my aversion and trying
> again, but for as rarely as I need to do so (more often I need to get
> into the bios or something) it just never seems worth the trouble of
> trying.

The Lantronix SpiderDuo is an invaluable device for those
that have a need to (occasionally) have a remote KVM
available that allows one access into (even) the bios
screens when the target system was purchased with
out of band remote management (and that includes almost
all of the non-vPro consumer boxes, and all too many
cheaper "servers"). A little pricey (although the prices
recently came down), but sometimes it is worth it
(and it is much easier to carry around in the backback
with a laptop than the screen and keyboard when I have
to go to a remote colo for some "adjustment" that
a remote power reset did not address).

Gary
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


jyavenard at gmail

Apr 21, 2012, 3:37 PM

Post #47 of 74 (2527 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sunday, 22 April 2012, Mark Lord wrote:

>
> The only people taking nasty shots at anyone here seem to be
> folks like you, and the others here who misconstrue my intents
> based upon the surname I was born with.
>
>
Oh come on...

For the record, this is the message I sent to Mark immediately after his
earlier message

"Actually; it's only after posting this that I realised on how it could be
linked to me making fun of your name.
Definitely wasn't the case. I didn't think about your name at all then.

I apologised if it came across that way. "

No one has taken personal shots...

Looks like I should just ignore this user list from now on...


dl-mythtv at catspoiler

Apr 21, 2012, 3:50 PM

Post #48 of 74 (2539 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 20 Apr, Mark Lord wrote:
> On 12-04-20 12:51 PM, Raymond Wagner wrote:
>> On 4/20/2012 12:40, Mark Lord wrote:
>>>>>> It's not doing anything fancy, it just runs statfs on the path
>>>>>>you give it. There's the bug. It should open the path, and the
>>>>>>use fstatfs(fd, ..).
>>>>> Doing it that way would make symlinks transparent to it, as they
>>>>>should be. So less a bug, and more a feature request (with a patch)
>>>>>for a strange and uncommon configuration.
>>> All eight mythtv setups that I know about have the same style of
>>> configuration.
>>
>> So they're all strange. Why not just point MythTV directly at the
>> directory? MythTV only ever records to the root of the directory you
>> give it, so it's not like symlinking in multiple folders is going to
>> get you more storage space. You still have to define each in
>> mythtv-setup. It's not going to allow you to bypass some file
>> permissions restrictions. Even if you frequently move the mount
>> location of those storage drives, symlinks are only slightly more
>> convenient to change than the values in mythtv-setup.
>>
>> I'm just not understanding what benefit doing it that way could
>> provide.
>
> It lets me move the storage directories around without having to
> fuss with mythtv-setup and other places that might have a hardcoded
> path.

If you follow the advice here
<http://www.mythtv.org/wiki/Storage_Groups> about not storing recordings
directly under mount points, you can still use symlinks to point to the
actual mount points and the disk space will be reported correctly.

> Symlinks are an incredibly useful feature, you should discover them
> someday.

I'm not a fan of using symlinks for this for multiple, though minor,
reasons.

There's always the danger of creating a dangling link. It shows
up in the output of ls, but you have to try to do something that
actually follows the link to verify that it actually points
somewhere valid.

The paths in the output of df will differ from mythweb backend
status, which means that I have to expend some additional mental
cycles to translate between the two.

As a csh user, I find it annoying that when I cd to a path that
contains a link, then when I try to return using .., I end up
somewhere else than were I want. Bash hides the fact that a
symbolic link has been followed, but I'm not sure that's always
a feature.

In all the years that I've been running MythTV, I've never felt the need
to move my storage directories around. I've frequently had to use
mythtv-setup edit my storage groups to add directories as I've added
additional drives. This is not something that symbolic links would make
any easier. As a matter of fact that it would be harder because
creating the additional links would just be an extra step.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


michael at thewatsonfamily

Apr 21, 2012, 4:05 PM

Post #49 of 74 (2525 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22/04/2012 8:37 AM, Jean-Yves Avenard wrote:
>
>
> Looks like I should just ignore this user list from now on...
>
Please dont, your input and knowledge is very important and useful, and
much appreciated, as is that of many others.
We need to stick to facts, not personnel agenda's or attacks. (leave
that for facebook)


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ron at ronfrazier

Apr 21, 2012, 4:12 PM

Post #50 of 74 (2526 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sat, Apr 21, 2012 at 6:37 PM, Jean-Yves Avenard <jyavenard [at] gmail> wrote:

> No one has taken personal shots...

From your earlier message:

> I see.. you're like Jesus, spreading the good word to whomever wants
> to listen, but don't write anything :)
>
> Your wisdom is so much appreciated.. Thanks again for showing people
> "how to use Linux correctly". I'm sure that thanks to you MythTV has
> progressed tremendously today, and probably all other days as well


Even if there was no Jesus/Lord link intended, that's still a personal
attack. Or are you trying to say there was no sarcasm intended there,
and you meant every word you said?

And yes, others did make personal attacks too:

On Sat, Apr 21, 2012 at 2:47 AM, Gavin Hurlbut <gjhurlbu [at] gmail> wrote:
> This is idiotic.
...
> and then waste everyone's time by
> trying to pretend that you are better than everyone else, and that
> putting in proper bug reports is beneath you.



> Looks like I should just ignore this user list from now on...

Why, are you unable to participate while remaining civil? I'm not
asking anyone to kiss anyone's ass or anything, but there's no need
for the sort of comments I quoted above, especially when Mark really
didn't do anything to provoke it.

--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ylee at pobox

Apr 21, 2012, 11:49 PM

Post #51 of 74 (1748 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Ronald Frazier <ron [at] ronfrazier> says:
> Even if there was no Jesus/Lord link intended, that's still a
> personal attack. Or are you trying to say there was no sarcasm
> intended there, and you meant every word you said?

I didn't make the possible connection between Jean-Yves' joke about
Jesus' preaching and Mark's name until Mark pointed it out, and
believe Jean-Yves when he says it wasn't intentional.

Of course Jean-Yves was being (otherwise) sarcastic. Mark was the
first to be condescending, though, with his lecture/explanation on
what a symbolic link is. I would hope anyone reading a mailing list on
MythTV, a project that is (and likely always will be)
Linux/POSIX-based, would know what it is.

> Why, are you unable to participate while remaining civil? I'm not
> asking anyone to kiss anyone's ass or anything, but there's no need
> for the sort of comments I quoted above, especially when Mark really
> didn't do anything to provoke it.

I disagree. Trac exists for a reason, and using a ticket system is
hardly unusual among F/OSS projects. That kernel development is done
entirely by offering patches over a mailing list is irrelevant; this
is mythtv-users (not even mythtv-dev), not LKML. Perhaps if the issue
were some life-or-death issue its reception would have been different,
but otherwise MythTV developers have enough work already without also
having to manually create a ticket for a patch *which none of them
needs*, offered by someone who explicitly refuses to and shows
contempt for long-existing procedures.

There probably isn't a single MythTV user who is able to code, knows
how to compile, and has moved beyond the Mythbuntu system-on-a-CD
stage, who doesn't keep a few patches of his own. As already stated on
the list, there are many reasons why one would keep some patches
private. I have them; in my case I release all via the bijou
distribution that ATrpms hosts, but the fact remains that they are not
part of the official source code. Jean-Yves has them, and does
something similar with his Ubuntu repo. Your valuable Ceton work for
0.24 is another example, needless to say.

But 100 (even while calling himself a "casual user")?!? Keeping 100
patches to himself is Mark's own business, but then he really, really
can't complain here about an issue one of them fixes.

--
MythTV FAQ Q: "Cheap frontend/backend?" A: Revo, $200-300 @ Newegg
Q: "Record HD cable/satellite?" A: Hauppauge HD-PVR, $200 @ Newegg
Q: "Can't change Live TV channels w/multirec!" A: Hit NEXTCARD key
More answers @ <URL:http://www.gossamer-threads.com/lists/mythtv/>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mikep at randomtraveller

Apr 22, 2012, 3:39 AM

Post #52 of 74 (1750 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 21/04/12 23:14, Don Lewis wrote:
> On 21 Apr, Simon Hobson wrote:
>> Ronald Frazier wrote:
>
>>> So I have to go downstairs, drag a monitor over to it and hook it
>>> up, do what I need, and then put everything away after I'm sure I've
>>> done. Now, when I need to do something in mythtv-setup, that's fine.
>>> But when I can do something in 5 seconds instead of several minutes,
>>> I'm gonna spend the 5 seconds.
>>
>> Why do you waste all that time and effort ? I run mythtv-setup from
>> my desk - just "ssh -X<user [at] backen address>" and fire up
>> mythtv-setup. It fires up in an X session right here on my laptop.
>> OK, many many years ago you needed to "know incantations" to get
>> remote X displays working, but the "-X" (or "-Y") option in SSH does
>> it all automagically.
>
> Same here. I've got a combined FE/BE, but I still run mythtv-setup more
> frequently from my desktop using ssh than I do from the living room
> where the FE/BE and TV are located since my desktop has a much more
> ergonomic configuration for using a keyboard than what I've got in the
> living room.
>
> My only complaints are that mythtv-setup paints the screen very slowly
> over ssh, and it takes over the entire screen. I'm looking forward to
> the upcoming switch to web based configuration.
>
I do the same (mythtv-setup over SSH) and I've never seen slow painting of
screens. I suggest you look for other reasons for the slowdown.

Why complain that it takes over the entire screen? When I'm doing setup I want
my entire attention to be on a task that it's very easy to screw up. While it's
away doing things I can always Alt+Tab to whatever else I have open.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


sheen.andy at googlemail

Apr 22, 2012, 3:57 AM

Post #53 of 74 (1743 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Mike Perkins wrote on Sun 22 Apr at 11:39 UK time
> Why complain that it takes over the entire screen? When I'm doing setup
> I want my entire attention to be on a task that it's very easy to screw
> up. While it's away doing things I can always Alt+Tab to whatever else I
> have open.
>

Because in the default skin (at least in 0.23 which I'm using) it takes
up THE ENTIRE SCREEN and if you are using dual monitors, that means it
takes up BOTH screens, often putting the bit you are interested across
the split in the screens.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mikep at randomtraveller

Apr 22, 2012, 4:11 AM

Post #54 of 74 (1742 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22/04/12 11:57, Andy Sheen wrote:
>
>
> Mike Perkins wrote on Sun 22 Apr at 11:39 UK time
>> Why complain that it takes over the entire screen? When I'm doing setup
>> I want my entire attention to be on a task that it's very easy to screw
>> up. While it's away doing things I can always Alt+Tab to whatever else I
>> have open.
>>
>
> Because in the default skin (at least in 0.23 which I'm using) it takes
> up THE ENTIRE SCREEN and if you are using dual monitors, that means it
> takes up BOTH screens, often putting the bit you are interested across
> the split in the screens.
>
Ah. I don't have that experience, of course. I have dual monitors, this is true,
but each is connected to a separate workstation.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ylee at pobox

Apr 22, 2012, 4:11 AM

Post #55 of 74 (1752 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Mike Perkins <mikep [at] randomtraveller> says:
> I do the same (mythtv-setup over SSH) and I've never seen slow
> painting of screens.

Wireless connection speed makes a substantial difference. With
802.11g, mythtv-setup over SSH needs several seconds to respond to
each keystroke on my Mac. With 802.11n, the response time is almost as
good as local.

--
MythTV FAQ Q: "Cheap frontend/backend?" A: Revo, $200-300 @ Newegg
Q: "Record HD cable/satellite?" A: Hauppauge HD-PVR, $200 @ Newegg
Q: "Can't change Live TV channels w/multirec!" A: Hit NEXTCARD key
More answers @ <URL:http://www.gossamer-threads.com/lists/mythtv/>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mythtv at theseekerr

Apr 22, 2012, 4:19 AM

Post #56 of 74 (1753 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sun, Apr 22, 2012 at 9:12 AM, Ronald Frazier <ron [at] ronfrazier> wrote:

> On Sat, Apr 21, 2012 at 6:37 PM, Jean-Yves Avenard <jyavenard [at] gmail>
> wrote:
>


> Even if there was no Jesus/Lord link intended, that's still a personal
> attack. Or are you trying to say there was no sarcasm intended there,
> and you meant every word you said?
>
> And yes, others did make personal attacks too:
>

I think we're suffering a cultural divide here - in Australia, and likely
elsewhere, a sarcastic response is generally considered lighthearted
humour, not an "attack".

> Looks like I should just ignore this user list from now on...
>
> Why, are you unable to participate while remaining civil? I'm not
> asking anyone to kiss anyone's ass or anything, but there's no need
> for the sofrt of comments I quoted above, especially when Mark really
> didn't do anything to provoke it.


As above, I wouldn't consider any of JYA's behaviour "uncivil".

- Chris


ron at ronfrazier

Apr 22, 2012, 8:01 AM

Post #57 of 74 (1744 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sun, Apr 22, 2012 at 2:49 AM, Yeechang Lee <ylee [at] pobox> wrote:
>> Why, are you unable to participate while remaining civil? I'm not
>> asking anyone to kiss anyone's ass or anything, but there's no need
>> for the sort of comments I quoted above, especially when Mark really
>> didn't do anything to provoke it.
>
> I disagree. Trac exists for a reason, and using a ticket system is
> hardly unusual among F/OSS projects. That kernel development is done
> entirely by offering patches over a mailing list is irrelevant; this
> is mythtv-users (not even mythtv-dev), not LKML. Perhaps if the issue
> were some life-or-death issue its reception would have been different,
> but otherwise MythTV developers have enough work already without also
> having to manually create a ticket for a patch *which none of them
> needs*, offered by someone who explicitly refuses to and shows
> contempt for long-existing procedures.
>
> There probably isn't a single MythTV user who is able to code, knows
> how to compile, and has moved beyond the Mythbuntu system-on-a-CD
> stage, who doesn't keep a few patches of his own. As already stated on
> the list, there are many reasons why one would keep some patches
> private. I have them; in my case I release all via the bijou
> distribution that ATrpms hosts, but the fact remains that they are not
> part of the official source code. Jean-Yves has them, and does
> something similar with his Ubuntu repo. Your valuable Ceton work for
> 0.24 is another example, needless to say.
>
> But 100 (even while calling himself a "casual user")?!? Keeping 100
> patches to himself is Mark's own business, but then he really, really
> can't complain here about an issue one of them fixes.


First of all, I suggest rereading this thread starting from Marks
original post and then continuing on for the next 7 posts or so. To
summarize:
Mark says "its a bug"
Gavin says "what bug",
Mark says "I think it might have to do with symlinks"
Raymond say "Here's the code"
Mark says "There's the problem"
20 minute later, Mark replies to himself "Here's a rough fix"

Now, it should be obvious that mark wasn't sitting there hoarding his
patch for this. Yes, it seems he knew about it some time ago, as did
I. And yes he didn't report it, as neither did I. I already explained
why I didn't: it was a minor bug, didn't bother me, wasn't important
enough to interrupt what I was doing, and since it was very minor it
was quickly forgotten about by the time I was done. Maybe it was the
same thing for Mark. But I think from the posts it was clear as day
that Mark didn't know what the problem was, and it was only figured
out (and the patch created) on the spot in this thread. I think that's
a worthy contribution on his part. He participated, he found the
solution, and he posted a rough fix. And now people are bitching that
they aren't satisfied he doesn't do more? Most people don't even do
that much. Don't harass a guy because he chooses to participate only
to the level he is comfortable participating. I wouldn't be surprised
if mark stops and thinks twice the next time he thinks he might be
able to help in a thread.

So now we've got a potential patch, and we're sitting here talking
about purposely not including it. Not because it's too much work. Not
because the code in the patch is terrible. Not because it introduces
bugs. Not because it hinders performance. No, we are talking about not
including the patch simply because we can't come up with a good reason
why we shouldn't purposely continue to let myth calculate an incorrect
value in some configurations. Is this the sort of discussion that is
going to make someone MORE likely to want to step forward and
contribute?

--
Ron Frazier
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


raymond at wagnerrp

Apr 22, 2012, 9:06 AM

Post #58 of 74 (1724 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 4/22/2012 06:57, Andy Sheen wrote:
> Mike Perkins wrote on Sun 22 Apr at 11:39 UK time
>> Why complain that it takes over the entire screen? When I'm doing setup
>> I want my entire attention to be on a task that it's very easy to screw
>> up. While it's away doing things I can always Alt+Tab to whatever else I
>> have open.
> Because in the default skin (at least in 0.23 which I'm using) it takes
> up THE ENTIRE SCREEN and if you are using dual monitors, that means it
> takes up BOTH screens, often putting the bit you are interested across
> the split in the screens.

Rather, the default UI settings take up the entire screen, as the UI is
primarily used for the frontend, which makes sense to use the entire
screen. The skin/theme has absolutely nothing to do with it. It will
take however much room you specify it use in the frontend, and will
follow command line overrides such as --geometry XxY, --windowed, and
--mouse-cursor.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


nospam at netrom

Apr 22, 2012, 10:05 AM

Post #59 of 74 (1719 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Apr 21, 2012 6:05 PM, "Michael Watson" <michael [at] thewatsonfamily>
wrote:
>
> Or simply use MobaXterm (Terminal client, with built in X Server)

Thank-you for this information. Awesome looking program.


jedi at mishnet

Apr 22, 2012, 10:34 AM

Post #60 of 74 (1718 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sun, Apr 22, 2012 at 11:39:31AM +0100, Mike Perkins wrote:
> On 21/04/12 23:14, Don Lewis wrote:
> >On 21 Apr, Simon Hobson wrote:
> >>Ronald Frazier wrote:
> >
> >>>So I have to go downstairs, drag a monitor over to it and hook it
> >>>up, do what I need, and then put everything away after I'm sure I've
> >>>done. Now, when I need to do something in mythtv-setup, that's fine.
> >>>But when I can do something in 5 seconds instead of several minutes,
> >>>I'm gonna spend the 5 seconds.
> >>
> >>Why do you waste all that time and effort ? I run mythtv-setup from
> >>my desk - just "ssh -X<user [at] backen address>" and fire up
> >>mythtv-setup. It fires up in an X session right here on my laptop.
> >>OK, many many years ago you needed to "know incantations" to get
> >>remote X displays working, but the "-X" (or "-Y") option in SSH does
> >>it all automagically.
> >
> >Same here. I've got a combined FE/BE, but I still run mythtv-setup more
> >frequently from my desktop using ssh than I do from the living room
> >where the FE/BE and TV are located since my desktop has a much more
> >ergonomic configuration for using a keyboard than what I've got in the
> >living room.
> >
> >My only complaints are that mythtv-setup paints the screen very slowly
> >over ssh, and it takes over the entire screen. I'm looking forward to
> >the upcoming switch to web based configuration.

This is very easy to avoid with the -geometry flag.

The same thing goes for the frontend as well as many other X apps.

> >
> I do the same (mythtv-setup over SSH) and I've never seen slow
> painting of screens. I suggest you look for other reasons for the
> slowdown.
>
> Why complain that it takes over the entire screen? When I'm doing

It's just not how some people are used to dealing with apps in 2012.

[deletia]
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


sheen.andy at googlemail

Apr 22, 2012, 10:47 AM

Post #61 of 74 (1734 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Raymond Wagner wrote on Sun 22 Apr at 17:06 UK time
> On 4/22/2012 06:57, Andy Sheen wrote:
>> Mike Perkins wrote on Sun 22 Apr at 11:39 UK time
>>> Why complain that it takes over the entire screen? When I'm doing setup
>>> I want my entire attention to be on a task that it's very easy to screw
>>> up. While it's away doing things I can always Alt+Tab to whatever else I
>>> have open.
>> Because in the default skin (at least in 0.23 which I'm using) it takes
>> up THE ENTIRE SCREEN and if you are using dual monitors, that means it
>> takes up BOTH screens, often putting the bit you are interested across
>> the split in the screens.
>
> Rather, the default UI settings take up the entire screen, as the UI is
> primarily used for the frontend, which makes sense to use the entire
> screen. The skin/theme has absolutely nothing to do with it. It will
> take however much room you specify it use in the frontend, and will
> follow command line overrides such as --geometry XxY, --windowed, and
> --mouse-cursor.

And that always assumes you run a front end ;) I just use mythbackend. I
don't have a single mythfrontend in the house. I know that makes me odd,
but....

I'll try the --geometry etc. next time I run it though.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheianevans at gmail

Apr 22, 2012, 2:20 PM

Post #62 of 74 (1711 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On Sun, Apr 22, 2012 at 1:05 PM, John <nospam [at] netrom> wrote:
> On Apr 21, 2012 6:05 PM, "Michael Watson" <michael [at] thewatsonfamily>
> wrote:
>> Or simply use MobaXterm  (Terminal client, with built in X Server)
> Thank-you for this information. Awesome looking program.

I tried using MobaXterm and it looks great. Was able to run some gui
pgms just fine. When I tried mythtv-setup, the GUI password box to
shut down the backend popped up.I typed in the password but instead of
appearing in the gui password box it appeared in clear text in the ssh
window. Is there a setting I was missing.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


ylee at pobox

Apr 22, 2012, 6:29 PM

Post #63 of 74 (1706 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Ronald Frazier <ron [at] ronfrazier> says:
> First of all, I suggest rereading this thread starting from Marks
> original post and then continuing on for the next 7 posts or so.

[...]

> 20 minute later, Mark replies to himself "Here's a rough fix"
>
> Now, it should be obvious that mark wasn't sitting there hoarding
> his patch for this.

Yes, I agree that I didn't quite accurately represent the
events. After the above, Raymond Wagner threw the first punch, if you
will, with "So less a bug, and more a feature request (with a patch)
for a strange and uncommon configuration." That parenthetical
statement aside, this was hardly a fair way to respond to a proffered
patch. Mark, however, did not help matters with his multiple replies
insinuating that Raymond and other MythTV developers were Wintards
ignorant of something as basic as symlinks, and his willful refusal to
use Trac.

> And now people are bitching that they aren't satisfied he doesn't do
> more? Most people don't even do that much.

I can't disagree with the above.

> No, we are talking about not including the patch simply because we
> can't come up with a good reason why we shouldn't purposely continue
> to let myth calculate an incorrect value in some configurations.

Setting aside the bad feelings and politics and what not, why *not*
permit the use of symlinks in Storage Group definitions? Just because
I also can't think of a reason why I'd use a symlink in a Storage
Group doesn't meant that others, not just Mark, cannot, and in
Unixland the universal assumption is that symlinks can be used
transparently and are "just as good" as native file nodes except in
unusual cases. Yes, they may slightly impair performance but, again,
such a "risk" exists anywhere symlinks are used and that hasn't
stopped their availability, and popularity, on every POSIX system in
the past 35 years.

I had planned to insert the above paragraph in my previous message in
the thread and am amending that omission now. I still advise Mark to
file a Trac ticket; no matter how much he may protest that that's not
how LKML does things, Trac is what the MythTV project runs on. I also
ask him to consider submitting some of the other 100 patches to Trac;
whether bugfixes or feature enhancements, I have no doubt that others
will benefit from his long experience.

--
MythTV FAQ Q: "Cheap frontend/backend?" A: Revo, $200-300 @ Newegg
Q: "Record HD cable/satellite?" A: Hauppauge HD-PVR, $200 @ Newegg
Q: "Can't change Live TV channels w/multirec!" A: Hit NEXTCARD key
More answers @ <URL:http://www.gossamer-threads.com/lists/mythtv/>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


michael at thewatsonfamily

Apr 22, 2012, 9:33 PM

Post #64 of 74 (1702 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 23/04/2012 7:20 AM, Ian Evans wrote:
> On Sun, Apr 22, 2012 at 1:05 PM, John<nospam [at] netrom> wrote:
>> On Apr 21, 2012 6:05 PM, "Michael Watson"<michael [at] thewatsonfamily>
>> wrote:
>>> Or simply use MobaXterm (Terminal client, with built in X Server)
>> Thank-you for this information. Awesome looking program.
> I tried using MobaXterm and it looks great. Was able to run some gui
> pgms just fine. When I tried mythtv-setup, the GUI password box to
> shut down the backend popped up.I typed in the password but instead of
> appearing in the gui password box it appeared in clear text in the ssh
> window. Is there a setting I was missing.
>
Not found a solution to that, but a work around is to do a "sudo su -",
logout of the root session, then run mythtv-setup, or run "sudo
mythtv-setup"
Not ideal, but works for me. (On ubuntu)

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dl-mythtv at catspoiler

Apr 22, 2012, 9:53 PM

Post #65 of 74 (1701 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22 Apr, Mike Perkins wrote:
> On 21/04/12 23:14, Don Lewis wrote:

>> My only complaints are that mythtv-setup paints the screen very slowly
>> over ssh, and it takes over the entire screen. I'm looking forward to
>> the upcoming switch to web based configuration.
>>
> I do the same (mythtv-setup over SSH) and I've never seen slow painting of
> screens. I suggest you look for other reasons for the slowdown.

It's a 100 Mbit network and file transfers run at the expected speed. My
first suspicion is the default painter. The graphics card on my desktop
probably doesn't support OpenGL very well.

> Why complain that it takes over the entire screen? When I'm doing setup I want
> my entire attention to be on a task that it's very easy to screw up. While it's
> away doing things I can always Alt+Tab to whatever else I have open.

When I do the delete all capture cards and input sources dance, it would
be nice to be able to view my configuration notes in another window
while adding everything back again. It would also be nice to be able to
copy and paste the channel changer commands to avoid typos. On several
occasions I've had recording failures due to incorrectly typed channel
changer commands.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dl-mythtv at catspoiler

Apr 22, 2012, 9:55 PM

Post #66 of 74 (1704 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 22 Apr, Raymond Wagner wrote:
> On 4/22/2012 06:57, Andy Sheen wrote:
>> Mike Perkins wrote on Sun 22 Apr at 11:39 UK time
>>> Why complain that it takes over the entire screen? When I'm doing setup
>>> I want my entire attention to be on a task that it's very easy to screw
>>> up. While it's away doing things I can always Alt+Tab to whatever else I
>>> have open.
>> Because in the default skin (at least in 0.23 which I'm using) it takes
>> up THE ENTIRE SCREEN and if you are using dual monitors, that means it
>> takes up BOTH screens, often putting the bit you are interested across
>> the split in the screens.
>
> Rather, the default UI settings take up the entire screen, as the UI is
> primarily used for the frontend, which makes sense to use the entire
> screen. The skin/theme has absolutely nothing to do with it. It will
> take however much room you specify it use in the frontend, and will
> follow command line overrides such as --geometry XxY, --windowed, and
> --mouse-cursor.

Thanks! I'll try that next time.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mikep at randomtraveller

Apr 23, 2012, 2:15 AM

Post #67 of 74 (1699 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 23/04/12 05:53, Don Lewis wrote:
> On 22 Apr, Mike Perkins wrote:
>> On 21/04/12 23:14, Don Lewis wrote:
>
>>> My only complaints are that mythtv-setup paints the screen very slowly
>>> over ssh, and it takes over the entire screen. I'm looking forward to
>>> the upcoming switch to web based configuration.
>>>
>> I do the same (mythtv-setup over SSH) and I've never seen slow painting of
>> screens. I suggest you look for other reasons for the slowdown.
>
> It's a 100 Mbit network and file transfers run at the expected speed. My
> first suspicion is the default painter. The graphics card on my desktop
> probably doesn't support OpenGL very well.
>
My network is 100 Mbit too. As an extra complication, I'm running this via my
main server which I'm currently logged into via an LTSP 4.2 thin client. The
client runs a crappy SiS 760 video chip the driver of which is so bad I've
overridden it with the VESA driver... still no problems with the display. I can
do anything with myth from the thin client except display video, as you might
expect.

>> Why complain that it takes over the entire screen? When I'm doing setup I want
>> my entire attention to be on a task that it's very easy to screw up. While it's
>> away doing things I can always Alt+Tab to whatever else I have open.
>
> When I do the delete all capture cards and input sources dance, it would
> be nice to be able to view my configuration notes in another window
> while adding everything back again. It would also be nice to be able to
> copy and paste the channel changer commands to avoid typos. On several
> occasions I've had recording failures due to incorrectly typed channel
> changer commands.
>
Yeah, that can be a pain. Alt+Tab is what I use and it's enough. Cut+Paste would
be a useful addition to the toolbox, especially for UK xmltv values, which can
be tedious 30+ character URIs being entered into boxes designed for short
numeric US values. Oh, and our call signs can be a lot longer than 5 characters too.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


John.Veness.mythtv at pelago

Apr 23, 2012, 2:31 AM

Post #68 of 74 (1687 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 23/04/2012 05:53, Don Lewis wrote:
> It's a 100 Mbit network and file transfers run at the expected speed. My
> first suspicion is the default painter. The graphics card on my desktop
> probably doesn't support OpenGL very well.

mythtv-setup uses the mythfrontend settings for which theme painter to
use (and mythfrontend settings for whether to be full screen etc.). If
you don't want to change the mythfrontend theme painter setting, then
you might want to try running mythtv-setup with command-line "-O
ThemePainter=qt".

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


John.Veness.mythtv at pelago

Apr 23, 2012, 2:34 AM

Post #69 of 74 (1698 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 23/04/2012 05:33, Michael Watson wrote:
> On 23/04/2012 7:20 AM, Ian Evans wrote:
>> On Sun, Apr 22, 2012 at 1:05 PM, John<nospam [at] netrom> wrote:
>>> On Apr 21, 2012 6:05 PM, "Michael Watson"<michael [at] thewatsonfamily>
>>> wrote:
>>>> Or simply use MobaXterm (Terminal client, with built in X Server)
>>> Thank-you for this information. Awesome looking program.
>> I tried using MobaXterm and it looks great. Was able to run some gui
>> pgms just fine. When I tried mythtv-setup, the GUI password box to
>> shut down the backend popped up.I typed in the password but instead of
>> appearing in the gui password box it appeared in clear text in the ssh
>> window. Is there a setting I was missing.
>>
> Not found a solution to that, but a work around is to do a "sudo su -",
> logout of the root session, then run mythtv-setup, or run "sudo
> mythtv-setup"
> Not ideal, but works for me. (On ubuntu)

If I'm thinking of the same thing. the GUI password box is a
Mythbuntu-specific addition, i.e. isn't in the MythTV-distributed code.
I don't know why it's not working right with MobaXterm, but as another
workaround you could try manually shutting down the backend first, then
running mythtv-setup.real which is the MythTV-distributed version of
mythtv-setup rather than the Mythbuntu-developed wrapper. That should
mean the GUI password box doesn't appear. Don't forget to manually start
the backend when finished.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


John.Veness.mythtv at pelago

Apr 23, 2012, 2:36 AM

Post #70 of 74 (1690 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 23/04/2012 10:15, Mike Perkins wrote:
> Yeah, that can be a pain. Alt+Tab is what I use and it's enough.
> Cut+Paste would be a useful addition to the toolbox, especially for UK
> xmltv values, which can be tedious 30+ character URIs being entered into
> boxes designed for short numeric US values. Oh, and our call signs can
> be a lot longer than 5 characters too.

I'm also in the UK and I agree that mythtv-setup is awkward for this. My
solution is to use the channel editor in mythweb to enter the xmltv
values as that's much more comfortable.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Apr 23, 2012, 2:55 AM

Post #71 of 74 (1689 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 04/23/2012 05:31 AM, John Veness wrote:
> On 23/04/2012 05:53, Don Lewis wrote:
>> It's a 100 Mbit network and file transfers run at the expected speed. My
>> first suspicion is the default painter. The graphics card on my desktop
>> probably doesn't support OpenGL very well.
>
> mythtv-setup uses the mythfrontend settings for which theme painter to
> use (and mythfrontend settings for whether to be full screen etc.). If
> you don't want to change the mythfrontend theme painter setting, then
> you might want to try running mythtv-setup with command-line "-O
> ThemePainter=qt".

No, do: http://www.gossamer-threads.com/lists/mythtv/users/514815#514815

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


mtdean at thirdcontact

Apr 23, 2012, 2:58 AM

Post #72 of 74 (1691 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

On 04/23/2012 05:15 AM, Mike Perkins wrote:
> On 23/04/12 05:53, Don Lewis wrote:
>> When I do the delete all capture cards and input sources dance,

Which, BTW, is never required, again, after 0.25 upgrade. Specify Live
TV and recording order for your inputs (not priorities, but order), and
you should only ever have to delete/add capture cards when yours break
or you buy new ones.

>> it would
>> be nice to be able to view my configuration notes in another window
>> while adding everything back again. It would also be nice to be able to
>> copy and paste the channel changer commands to avoid typos. On several
>> occasions I've had recording failures due to incorrectly typed channel
>> changer commands.
>>
> Yeah, that can be a pain. Alt+Tab is what I use and it's enough.
> Cut+Paste would be a useful addition to the toolbox, especially for UK
> xmltv values, which can be tedious 30+ character URIs being entered
> into boxes designed for short numeric US values. Oh, and our call
> signs can be a lot longer than 5 characters too.

X Windows copy/paste works fine--the only challenge is finding the text
box (when you do, the mouse cursor appears, then just middle click).
Or, you can specify the setting that says to always show the cursor.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


linux at thehobsons

Apr 23, 2012, 3:46 AM

Post #73 of 74 (1689 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

John Veness wrote:

>My solution is to use the channel editor in mythweb to enter the
>xmltv values as that's much more comfortable.

Even that's a pain if you need to do it more than once (such as when
you need to scan to pick up the latest reshuffle by the broadcasters.
That's why I wrote a SQL script to do it for me - I now only need to
update the script to suit any changes, after which it's a few seconds
to reset them after a new scan.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users


dheianevans at gmail

Apr 23, 2012, 11:12 AM

Post #74 of 74 (1668 views)
Permalink
Re: Disk Space Way Wrong [In reply to]

Thanks for the X suggestions guys.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.