On Fri, 2019-08-16 at 08:26 -0700, Mike Wright wrote:
On 8/16/19 6:09 AM, Patrick O'Callaghan wrote:
> On Fri, 2019-08-16 at 08:29 -0400, Tom Horsley wrote:
> > On Fri, 16 Aug 2019 13:18:03 +0100
> > Patrick O'Callaghan wrote:
> >
> > > PS Suggestions on how to move /var without all this jiggery-pokery are
> > > also welcome.
> >
> > What you want is a "bind" mount. Something like this:
> >
> > /zooty/home /home none rw,bind 0 0
> >
> > I use this to put /home on a bigger disk than the OS was installed on
> > (and recover /home from previous installs since /zooty/home hangs around).
>
> That "works" (i.e. doesn't give an error and does mount the
directory)
> ...
>
> > Of course, I have no idea if something during boot might want
> > /var prior to even looking at the fstab, so this might not work.
>
> ... however the system refuses to boot (SDDM throws an error, then
> system reboots). Something doesn't like /var being moved around after
> starting, or doesn't like bind mounts for some reason.
My strong hunch is that boot logging gets clobbered.
Possibly, though it's not clear why (it complains about not being able
to write to a log file under /var/log, but /var/log exists). Anyway,
it's a secondary consideration and will presumably disappear once I fix
the main issue.
poc