Re: [systemd-devel] [packaging] split of systemd package

Zbigniew Jędrzejewski-Szmek píše v Čt 12. 11. 2015 v 06:13 +: > I prepared a package for rawhide with [1,2] the following > subpackages: > systemd-journal-remote (remote, upload, gatewayd) > systemd-container (nspawn, machinectl, machined, importd, pull, var > -lib-machines.mount) >

Re: [systemd-devel] network interface renaming via PCI ID w/ systemd-udevd

On Thu, Nov 12, 2015 at 10:29 AM, Matthew Hall wrote: > > Let me try and put this another way. I have been using UNIX 24 years. I have > typed the characters eth0 so long that it's long since been hardcoded into my > fingers; trying to change it would drive me crazy and

Re: [systemd-devel] [packaging] split of systemd package

On Wed, 11.11.15 13:38, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: > > > systemd-firstboot (firstboot,sysusers?,factory stuff?) > > I wonder if this is worth the trouble. The binaries are currently > fairly big, but do they bring in any external dependencies? > Maybe we should instead

Re: [systemd-devel] [packaging] split of systemd package

Zbigniew Jędrzejewski-Szmek píše v Čt 12. 11. 2015 v 05:42 +: > On Wed, Nov 11, 2015 at 02:33:52PM +0100, Lukáš Nykrýn wrote: > > > > systemd-firstboot (firstboot,sysusers?,factory stuff?) > > > > > > I'd really not bother with this stuff. This should be in the > > > base, > > > and > > > it

Re: [systemd-devel] [packaging] split of systemd package

On Wed, 11.11.15 12:58, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello all, > > in case it's useful, this is how we split them in Debian. > > However, is this even a topic for upstream, apart from giving > recommendations? I. e. do you actually consider putting this kind of > split into

Re: [systemd-devel] [packaging] split of systemd package

Lennart Poettering [2015-11-12 9:46 +0100]: > > Another reason is to make it easy to enable/disable a particular > > feature (e. g. libnss-myhostname). > > I don't see why one would ever disable this feature... I doubt this > makes senseto split out really. We have to do that because it's a

Re: [systemd-devel] [packaging] split of systemd package

On Thu, 12.11.15 08:49, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello Zbigniew, > > Zbigniew Jędrzejewski-Szmek [2015-11-12 6:39 +]: > > Installed size of systemd-udev is 6.5MB, systemd-container is 3.5MB, > > systemd is 19MB, so the gain is modest. We also lose some dependencies. >

Re: [systemd-devel] [packaging] split of systemd package

Am 12.11.2015 um 09:46 schrieb Lennart Poettering: On Wed, 11.11.15 12:58, Martin Pitt (martin.p...@ubuntu.com) wrote: Hello all, in case it's useful, this is how we split them in Debian. However, is this even a topic for upstream, apart from giving recommendations? I. e. do you actually

Re: [systemd-devel] network interface renaming via PCI ID w/ systemd-udevd

On Thu, 12.11.15 02:29, Matthew Hall (mh...@mhcomputing.net) wrote: > On Thu, Nov 12, 2015 at 07:59:03AM +0200, Mantas Mikul??nas wrote: > > I'm not sure if udev even still _allows_ renaming to eth*, but even if it > > does, that's explicitly not supported. (For example, between the time eth0 > >

Re: [systemd-devel] [packaging] split of systemd package

On Wed, 11.11.15 14:33, Lukáš Nykrýn (lnyk...@redhat.com) wrote: > > > > > systemd-machine (machined,nspawn,importd) > > > > I'd call this "systemd-nspawn.rpm", really... The name of the daemon > > is irrelevant. > > > > > systemd-firstboot (firstboot,sysusers?,factory stuff?) > > > > I'd

Re: [systemd-devel] network interface renaming via PCI ID w/ systemd-udevd

On Thu, Nov 12, 2015 at 10:52 AM, Matthew Hall wrote: > On Thu, Nov 12, 2015 at 09:56:28AM +0200, Mantas Mikul??nas wrote: > > You begin with saying that eth# is good because that's how it's been done > > for decades ??? but then you say the exact same thing is now *bad*

Re: [systemd-devel] [packaging] split of systemd package

On Wed, 11.11.15 16:03, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > On 11/11/2015 03:51 PM, Zbigniew Jędrzejewski-Szmek wrote: > >Why not systemd-devel? > > Because these aren't development related discussion and there is a need for > separated collaborated git repository to

Re: [systemd-devel] [packaging] split of systemd package

On Thu, 12.11.15 09:07, Lukáš Nykrýn (lnyk...@redhat.com) wrote: > Zbigniew Jędrzejewski-Szmek píše v Čt 12. 11. 2015 v 06:13 +: > > I prepared a package for rawhide with [1,2] the following > > subpackages: > > systemd-journal-remote (remote, upload, gatewayd) > > systemd-container (nspawn,

Re: [systemd-devel] [packaging] split of systemd package

Lennart Poettering [2015-11-12 9:59 +0100]: > THere's no point in shipping the non-binary version of the hwdb. The > hwdb isn't a cache, it's a compiled version of the hwdb, and you don't > the sources around for this. Won't you need it for udevadm hwdb --update, after you add a new hwdb.d/

Re: [systemd-devel] [packaging] split of systemd package

Lennart Poettering [2015-11-12 10:01 +0100]: > > However, the gain through the extra dependencies is nontrivial: On a > > minimal system, installing systemd-container pulls in some 20 extra > > packages (libldap, sasl2-modules, libkrb5, libssh, ca-certificates > > etc.) > > ldap, sasl, kerberos,

Re: [systemd-devel] [packaging] split of systemd package

On Wed, 11.11.15 23:09, Michael Chapman (m...@very.puzzling.org) wrote: > On Wed, 11 Nov 2015, Lukáš Nykrýn wrote: > >Hi, > > > >During systemd.conf we have discussed some recommendation for > >downstreams, how they could split systemd to subpackages, so lets > >continue that discussion here. > >

Re: [systemd-devel] Detect if a script runs during bootup

Reindl Harald wrote >> This is not possible as it is an opensuse system script that I cannot >> replace. > > says who? > > thats why /etc/systemd/system/ exists - override sysvinit scripts and > even systemd-units from packages - just name it identical and it will win Right, but it's the

Re: [systemd-devel] [packaging] split of systemd package

Lennart Poettering [2015-11-12 11:15 +0100]: > > Won't you need it for udevadm hwdb --update, after you add a new > > hwdb.d/ file? Or can we now have multiple compiled dbs, one shipped by > > the package and one built dynamically by hwdb --update? > > Well, if you do add those locally. But

Re: [systemd-devel] [packaging] split of systemd package

On 12/11/15 08:59, Lennart Poettering wrote: > The > other option of course is to declare all internal APIs exported .so > symbols, but that would mean to commit to a stable API for them (which > is completely out of the question), or to bump the soname on each > release (which is not an option

Re: [systemd-devel] systemctl suspend

On Wed, 11.11.15 16:13, Steve Abner (pheonix@att.net) wrote: > I have an issue of the console not turning back on. I have a new build, > linux 4.2, amd64, systemd, kdbus > on a mac mini. The first try was hybrib-sleep, failed so tried suspend. From > journalctl there seems to be > no related

Re: [systemd-devel] systemctl suspend

On 11/12/2015 01:04 AM, Mantas Mikulėnas wrote: On Wed, Nov 11, 2015 at 11:13 PM, Steve Abner > wrote: I have an issue of the console not turning back on. I have a new build, linux 4.2, amd64, systemd, kdbus on a mac mini. The

Re: [systemd-devel] about socket

On Wed, 11.11.15 16:21, yan...@iscas.ac.cn (yan...@iscas.ac.cn) wrote: > Hi guys: > How can I find what systemd does for sockets? For example,if A and B > requires C,and when C has not start,the message of A and the message of B is > in the same queue? or else? Thank you! Sorry, I cannot

Re: [systemd-devel] [packaging] split of systemd package

On Thu, 12.11.15 10:46, Martin Pitt (martin.p...@ubuntu.com) wrote: > Lennart Poettering [2015-11-12 9:59 +0100]: > > THere's no point in shipping the non-binary version of the hwdb. The > > hwdb isn't a cache, it's a compiled version of the hwdb, and you don't > > the sources around for this. >

Re: [systemd-devel] [PATCH] v3 Read NIC partitions on Dell Servers

On Tue, 10.11.15 14:57, jhar...@gmail.com (jhar...@gmail.com) wrote: > From: Jordan Hargrave > > I removed the SMBIOS-specific code, this code is for partition detection only. > > This patch will read NIC partition info from VPD on Dell Servers > > It creates a new

Re: [systemd-devel] Detect if a script runs during bootup

Zbigniew Jędrzejewski-Szmek wrote on 11/11/15 15:55: > On Wed, Nov 11, 2015 at 04:39:23PM +0100, Frank Steiner wrote: >> Isn't there an easy way to figure out if this script is running >> inside the boot process? Some variable set or not yet set? > You can use systemctl is-system-running (see the

Re: [systemd-devel] Detect if a script runs during bootup

Le jeudi 12 novembre 2015 à 11:31 +0100, Frank Steiner a écrit : > Reindl Harald wrote > > > > This is not possible as it is an opensuse system script that I > > > cannot > > > replace. > > > > says who? > > > > thats why /etc/systemd/system/ exists - override sysvinit scripts > > and > > even

Re: [systemd-devel] systemctl suspend

On 11/12/2015 07:56 AM, Lennart Poettering wrote: On Wed, 11.11.15 16:13, Steve Abner (pheonix@att.net) wrote: >I have an issue of the console not turning back on. I have a new build, >linux 4.2, amd64, systemd, kdbus >on a mac mini. The first try was hybrib-sleep, failed so tried

Re: [systemd-devel] [packaging] split of systemd package

On Thu, Nov 12, 2015 at 09:59:34AM +0100, Lennart Poettering wrote: > The other option of course is to declare all internal APIs exported > .so symbols, but that would mean to commit to a stable API for them > (which is completely out of the question), or to bump the soname on > each release

[systemd-devel] Network/Block device PCI Slot map utility

I've developed a script that will display useful information for all block and network devices. It displays the PCI slot number, SR-IOV physical device, model/vendor, driver, and NIC port number. The script will also display the bay and slot number for installed Dell PCIe-SSDs. The script

Re: [systemd-devel] network interface renaming via PCI ID w/ systemd-udevd

On Thu, Nov 12, 2015 at 10:37:56AM +0100, Lennart Poettering wrote: > Since time began eth* is where the kernel automatically picked iface > names from. If you want to assign your own names go for some other > namespace, or be prepared to race against the kernel, and deal with > it. > > Lennart