On 8/19/19 1:20 PM, Ken Moffat via blfs-dev wrote:
On Mon, Aug 19, 2019 at 02:19:26PM +0200, Pierre Labastie via blfs-dev wrote:
On 19/08/2019 05:30, Bruce Dubbs via blfs-dev wrote:
On 8/18/19 9:36 PM, Ken Moffat via blfs-dev wrote:
On Sun, Aug 18, 2019 at 11:46:41PM +0100, Ken Moffat via blfs-dev wrote:
More to the point: I just started to try to prepare this on the
running 9.0-rc system. On 5.2.8, CONFIG_MEMCFG is for some reason
not set (I've been trying different kernels / configs and went back
to an oldeer one when I was doing this build) but things seem to
work fine, although I definitely seemed to need that before.
So, for the moment only requiring CONFIG_CGROUPS=y and
CONFIG_INOTIFY_USER=y.
Just a comment here. When building a new kernel I start by copying my most
recent config to .config and running 'make oldconfig'. I then consider new
options as they are presented, but generally take the presented default. I
just looked and all my configs going back to a 4.10 kernel have
CONFIG_CGROUPS=y and CONFIG_INOTIFY_USER=y.
FWIIW, same here. At some point, I wanted to try systemd, so I added those
options into my saved .config, and have always kept them (they did not hurt
with SysV).
I do the same, but I have two machines where I'm actively doing
desktop stuff, and two older machines where kernels have tended not
to be updated so much in recent months.
And of each pair, one and CGROUPS enabled, and one did not.
Maybe we should add that if no CONFIG_CGROUP_XXX switch is ticked, the
mountcgroupfs script returns an error (or remove the script completely, but
maybe not because we are to close to a release).
I say change the text to ONLY starting the dbus bootscript. And
therefore remove both the elogind and mountcgroupfs scripts.
(What is the text emoticon for "evil grin" ?)
But realistically I'm waiting for DJ's explorations on other
hardware, and still trying to understand why Bruce didn't have a
mouse or keyboard, and his log was in a different place.
I'm 90% sure that the mouse/kb problem was because my user was not set
up properly because those packages were built after login. A
logout/login would have probably fixed it.
Actually the *proper* place for Xorg logs is in ~/.local. What if two
users want to run xorg at the same time? They should have different
configurations and possibly different HW.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
