On Mon, Aug 19, 2019 at 08:45:28PM +0100, Ken Moffat via blfs-dev wrote:
>
> Please discard my past contributions to this thread, it appears I
> installed Xorg suid and with the wrapper on this build. Worse, on
> my previous test build it was still suid (without the wrapper).
>
The wrapper is of
On Mon, Aug 19, 2019 at 01:29:39PM -0500, Bruce Dubbs via blfs-dev wrote:
> 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
On 8/19/19 2:18 PM, Pierre Labastie via blfs-dev wrote:
Bruce Dubbs via blfs-dev wrote:
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.
Actually, I do not th
Bruce Dubbs via blfs-dev wrote:
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.
Actually, I do not think it is possible to run two Xorg servers with the
same
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
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 ju
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:
>>> On Sun, Aug 18, 2019 at 04:44:30PM -0500, Bruce Dubbs via blfs-dev wrote:
On 8/18/19 4:00 PM, Ken Moffat via
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:
On Sun, Aug 18, 2019 at 04:44:30PM -0500, Bruce Dubbs via blfs-dev wrote:
On 8/18/19 4:00 PM, Ken Moffat via blfs-dev wrote:
i.e.
or will that break something ?
Proba
On Sun, Aug 18, 2019 at 11:46:41PM +0100, Ken Moffat via blfs-dev wrote:
> On Sun, Aug 18, 2019 at 04:44:30PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 8/18/19 4:00 PM, Ken Moffat via blfs-dev wrote:
> > >
> > > i.e.
> > > or will that break something ?
> >
> > Probably OK for the most part,
On Sun, Aug 18, 2019 at 04:44:30PM -0500, Bruce Dubbs via blfs-dev wrote:
> On 8/18/19 4:00 PM, Ken Moffat via blfs-dev wrote:
> >
> > i.e.
> > or will that break something ?
>
> Probably OK for the most part, but the entire elogind sect1 is sysv only.
>
> -- Bruce
slapped-head.
Of course.
On 8/18/19 4:00 PM, Ken Moffat via blfs-dev wrote:
On Mon, Aug 05, 2019 at 03:24:55AM +0100, Ken Moffat via blfs-dev wrote:
On Mon, Aug 05, 2019 at 01:42:15AM +, DJ Lucas via blfs-dev wrote:
On 8/4/2019 9:26 AM, Pierre Labastie via blfs-dev wrote:
t would be useful.
Concerning cgroup v2
On Mon, Aug 05, 2019 at 03:24:55AM +0100, Ken Moffat via blfs-dev wrote:
> On Mon, Aug 05, 2019 at 01:42:15AM +, DJ Lucas via blfs-dev wrote:
> >
> >
> > On 8/4/2019 9:26 AM, Pierre Labastie via blfs-dev wrote:
> > > t would be useful.
> > >
> > > Concerning cgroup v2, "man cgroups" tells:
>
On Mon, Aug 05, 2019 at 01:42:15AM +, DJ Lucas via blfs-dev wrote:
>
>
> On 8/4/2019 9:26 AM, Pierre Labastie via blfs-dev wrote:
> > t would be useful.
> >
> > Concerning cgroup v2, "man cgroups" tells:
> > "Note that on many modern systems, systemd(1) automatically mounts the
> > cgroup2
On 8/4/2019 9:26 AM, Pierre Labastie via blfs-dev wrote:
t would be useful.
Concerning cgroup v2, "man cgroups" tells:
"Note that on many modern systems, systemd(1) automatically mounts the
cgroup2 filesystem at /sys/fs/cgroup/unified during the boot process".
According to what I see, elogin
On 04/08/2019 07:48, DJ Lucas via blfs-dev wrote:
>
>
> On 8/2/2019 3:12 PM, Pierre Labastie via blfs-dev wrote:
>> On 02/08/2019 17:23, Ken Moffat via blfs-dev wrote:
>>> On Fri, Aug 02, 2019 at 11:05:02AM +0200, Pierre Labastie via blfs-dev
>>> wrote:
On 02/08/2019 04:54, Ken Moffat via b
On 8/2/2019 3:12 PM, Pierre Labastie via blfs-dev wrote:
On 02/08/2019 17:23, Ken Moffat via blfs-dev wrote:
On Fri, Aug 02, 2019 at 11:05:02AM +0200, Pierre Labastie via blfs-dev wrote:
On 02/08/2019 04:54, Ken Moffat via blfs-dev wrote:
However, I had a bit of fun and games getting mountcg
On Fri, Aug 02, 2019 at 10:12:48PM +0200, Pierre Labastie via blfs-dev wrote:
>
> I think we'd better check whether mountcgroupfs is needed at all. elogind
> seems to do most of what is in this script.
>
> Pierre
Specifically, mountcgroupfs creates
/sys/fs/cgroup/{cgroup1,unified}
and elogind
On 02/08/2019 17:23, Ken Moffat via blfs-dev wrote:
> On Fri, Aug 02, 2019 at 11:05:02AM +0200, Pierre Labastie via blfs-dev wrote:
>> On 02/08/2019 04:54, Ken Moffat via blfs-dev wrote:
>>>
>>> However, I had a bit of fun and games getting mountcgroupfs to
>>> I'd got CONFIG_CGROUPS CONFIG_INOTIFY
On Fri, Aug 02, 2019 at 04:23:15PM +0100, Ken Moffat via blfs-dev wrote:
> On Fri, Aug 02, 2019 at 11:05:02AM +0200, Pierre Labastie via blfs-dev wrote:
> >
> > From my investigations, no... And the whole mountcgroupfs bootscript can be
> > omitted, because elogind takes care of mounting those. OT
On Fri, Aug 02, 2019 at 11:05:02AM +0200, Pierre Labastie via blfs-dev wrote:
> On 02/08/2019 04:54, Ken Moffat via blfs-dev wrote:
> >
> > However, I had a bit of fun and games getting mountcgroupfs to
> > I'd got CONFIG_CGROUPS CONFIG_INOTIFY_USER and CONFIG_FHANDLE
[...]
> >
> > CONFIG_MEMCFG
On 02/08/2019 04:54, Ken Moffat via blfs-dev wrote:
> First, the good news:
>
> On intel (haswell, built-in graphics) I've got Xorg working as
> expected, without the suid settings.
>
> However, I had a bit of fun and games getting mountcgroupfs to
> start.
>
> I'd got CONFIG_CGROUPS CONFIG_INOT
First, the good news:
On intel (haswell, built-in graphics) I've got Xorg working as
expected, without the suid settings.
However, I had a bit of fun and games getting mountcgroupfs to
start.
I'd got CONFIG_CGROUPS CONFIG_INOTIFY_USER and CONFIG_FHANDLE
already all set to Y. But when I tried to
22 matches
Mail list logo