Re: Solving the syslogd problem

2020-02-04 Thread Thor Lancelot Simon
On Tue, Feb 04, 2020 at 07:38:34AM +1030, Brett Lymn wrote: > > and mounted. So, so what if you get / first and then have to wait for > the rest of the fsck's to happen vs a fsck of a single large file > system? At the end of the day it will take about the same amount f time > to get the machine

Re: Solving the syslogd problem

2020-02-04 Thread Thor Lancelot Simon
On Tue, Feb 04, 2020 at 08:36:56AM -0500, Thor Lancelot Simon wrote: > > Moving part of the system to /usr was a *necessary evil* when it was done. > There is no real rhyme nor reason to what's in /bin vs /usr/bin, even less > to /sbin vs /usr/sbin, except "huh, I need _this_ and I'm willing to ma

Re: Solving the syslogd problem

2020-02-04 Thread Robert Elz
Date:Mon, 3 Feb 2020 22:57:21 +0100 From:Joerg Sonnenberger Message-ID: <20200203215721.ga26...@bec.de> | I don't think the size distribution for / is really that much different | from most of /usr. Most of /usr or all of /usr ? jinx$ df -i / /usr Filesystem

Re: Solving the syslogd problem

2020-02-04 Thread Brett Lymn
On Mon, Feb 03, 2020 at 10:45:22PM -, Michael van Elst wrote: > > Then you have a running system that can e.g. talk to the network. > Better than fighting against WAPBL with a damaged journal that > you cannot skip. > Well, rationally, there is no guarantee that won't happen with a separate

Re: merging /usr/bin etc. to / (was: Solving the syslogd problem)

2020-02-04 Thread Greg A. Woods
At Thu, 30 Jan 2020 12:00:13 +0100, Edgar Fuß wrote: Subject: merging /usr/bin etc. to / (was: Solving the syslogd problem) > > > This is elegant and I would like to see it. Just remove /usr entirely and > > collapse its contents into / - no /usr/bin, no /usr/lib, etc. > > This thread started b