SCIENTIFIC-LINUX-USERS Archives

July 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Reply To:
Konstantin Olchanski <[log in to unmask]>
Date:
Wed, 12 Jul 2017 08:42:26 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
On Wed, Jul 12, 2017 at 02:20:09PM +0200, David Sommerseth wrote:
>
> Systemd isn't standing in my way any more.
>

I do not feel this way.

Specifically, NFS-Root is an important function for us - we often
run "diskless" machines - and I feel it only works with systemd "by accident".

In theory, systemd does not care if "/" is a disk or an nfs mount,
but while evaluating BTRFS I discovered that it does, and it all happens
inside a binary blob, and if anything goes wrong, it is unfixable without
building systemd from sources and hacking at their c code. Big difference
from editing a shell script.

Already the status of nfs-root support in el7 is under question, as packages
like iputils, wireshark and httpd cannot be installed/updated because
they are packaged to use extended attributes (setcap), unsupported on NFS,
and yum/rpm bombs with no possibility of "--force".

Plus the current experience that filing bug reports on bugzilla and whining
on the forums does not get results.

So if something major like nfs-root suddenly stops working, we will be
forced to switch to a systemd-free linux, and not by choice or by religion.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2