On 04/26/2014 05:15 AM, Ken Moffat wrote:
>  I've now got to section 8.3, and as-expected I need to change my
> kernel config from what I've been using, if I hope it will support
> booting with systemd.  But I'd like to query if a few of these
> settings really are necessary, and also to suggest that we ought to
> distinguish between what is required for sysvinit with the LFS
> bootscripts (just devtmpfs last time I looked), and those options
> which are only needed for systemd.  After all, we already know that
> some users have no wish to run lennart from scratch.
> 
>  I know that Control Group support is needed by systemd, the items
> I'm querying are :
> 
> 1. open by fhandle syscalls - this is supposedly for userspace file
> servers (according to the kernel help).
> 

It is required by udev, I forgot why. All my partitions failed to mount
without it.

> 2. Enable seccomp to safely compute untrusted bytecode - I happen to
> have this set (I'm a sucker for enabling new options if they look as
> if they might be useful), but it doesn't look like something that I
> normally _need_.
> 

Kind of security thing, not really sure what it does. systemd also uses
libsecomp library which might be the interface to this. It was part of
systemd before version 210, later versions use external lib. You may be
safe without it.

> 3. The IPv6 protocol - again I have it set (ISTR one of the LFS
> testsuites likes it), but many of us have no expectation of being
> able to use this in the near future - is it really required ?
> 

It's recommended in readme. Probably for ipv6 sockets support (intetd
like activation and stuff).

> 4. Kernel automounter version 4 support - this fills me with horror
> (I hate it if my system tries to second-guess what I want to do with
> a CD or something purporting to be a drive (e.g. something with
> compact flash, i.e. using usb-storage) which has been connected by
> USB).  The kernel help says this needs userspace tools - I am
> guessing that systemd replaces the autofs daemon in this context,
> but it also says that NFS file system support is needed.  Not a
> problem for me, because a lot of my data is on nfs, but perhaps
> misleading if automounting really is required and people also read
> the kernel help - we've always had a tradition of minimal kernels.
> 

Not sure on this one either, probably for systemd automount features
(whatever that could be).

> 5. Tmpfs POSIX ACLs and extended attributes.  Again, not something
> I've ever needed.
> 

Required by systemd-logind so an user could access nodes in /dev (such
as audio, video, etc) without being a root user or a member of group
which has the write access to the node.

>  I can willingly believe that systemd is so monolithic that all of
> these things really are needed, but I thought I might as well ask -
> if some of these enable functionality which might be epected to be
> present in systemd, perhaps we should list what they enable, with a
> warning that omitting them may cause problems if you run systemd ?
> 
> ĸen
> 


-- 
Note: My last name is not Krejzi.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to