'Add to Existing Ubuntu' Install assumes /home folder is local. Fails on NFS share mounted via autofs.

[CarbonPepper]

Like many other users, my home folder is non-standard.
Can the install script be modified to cater for this?

Mine uses autofs to mount a share over NFS. The autofs prevents any manual creation of anything, even by root, in the /home folder.

I can work around this. But I propose the assumption that all users go into a local /home folder is unsafe.

[Mario Limonciello (superm1)]

I'm assuming that the part failing is the creation of the mythtv
daemon user's home folder. We could look into storing it in /var/lib
instead by default I suppose.

The only problem I forsee is that a lot of scripts are expecting to
find it in /home, so we may need to configure them to use getent
instead to figure out the best place for storage.

On 01/07/2010, abssorb <email address hidden> wrote:
> Public bug reported:
>
> Like many other users, my home folder is non-standard.
> Can the install script be modified to cater for this?
>
> Mine uses autofs to mount a share over NFS. The autofs prevents any
> manual creation of anything, even by root, in the /home folder.
>
> I can work around this. But I propose the assumption that all users go
> into a local /home folder is unsafe.
>
> ** Affects: mythbuntu
> Importance: Undecided
> Status: New
>
> --
> 'Add to Existing Ubuntu' Install assumes /home folder is local. Fails on NFS
> share mounted via autofs.
> https://bugs.launchpad.net/bugs/504317
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

--
Sent from my mobile device

Mario Limonciello
<email address hidden>

[CarbonPepper (carbonpepper)]

How about a prompt in the install script asking if /home is the chosen location for user folders? That would solve my problem I think.

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.