They responded to the warning by moving the password stuff back into the main
systemd package:
https://git.openembedded.org/openembedded-core/commit/meta/recipes-core/systemd?id=a87d523ab24e4ea87d1b19ea3a0c515cc47db1b6
-James M
password-agent inside
libsystemd-shared-255.so.
I wonder if systemd-tty-ask-password-agent should be moved into the main
systemd package.
-James M
> Is systemd-tty-ask-password real or a typo?
Sorry, I meant systemd-tty-ask-password-agent.
I dropped “-agent” by mistake (at least I had it right in the subject).
> Also if you're already in a root session, why is it asking for more
> authentication?
I suspect some services need to query for
(v255.10).
The following commit adds a log statement to exec-util,c and that is why it has
appeared:
https://github.com/systemd/systemd-stable/commit/76fe6ebee8
Any comment on my other question: is systemd-tty-ask-password an optional
component?
-James M
>> Is systemd-tty-ask-password still an optional component?
>>
>> Is this new behaviour (where systemd-tty-ask-password is repeatedly
>> executed) intentional?
>
> It is not new behavior. systemctl did it for as long as I remember.
Okay. But the display of the warning is new behaviour.
Was the
-ask-password still an optional component?
Is this new behaviour (where systemd-tty-ask-password is repeatedly executed)
intentional?
-James M
> > Is there a conf option or an environment variable I can use to disable the
> > unsafe path transition check?
>
> No there is not. It's a security hole what you are doing there...
>
> > Failing that, is there a way I can change the ownership systemd-tmpfiles
> > sees?
>
> Why not just fix the
is there a way I can change the ownership systemd-tmpfiles sees?
Thanks,
-James M
On Thu, 2025-02-13 at 22:07 +0100, Lennart Poettering wrote:
> On Mo, 10.02.25 19:09, James Feeney ([email protected]) wrote:
>
> >
>
> > systemd[1]: Got message type=method_call sender=n/a
> > destination=org.freedesktop.systemd1 path=/org/freedesk
I am chasing a bug in the systemd response to the initiation of an ethernet
interface "device" unit by the kernel. When an ethernet interface "device"
unit is initiated by the kernel, systemd will Start an associated service unit
in response, but will subsquently "Enqueue" that same already run
pen).
Unfortunately, the switch-root operation somehow causes /proc/schedstat to
become inaccessible, so systemd-bootchart is broken with "rdinit=" as well.
-James M
t; > > Note that we'll also possibly reinitialize the tty on switch root,
> > > maybe your tool has the tty open and gets a SIGHUP because of that.
> >
> > Brian M also suggested that might be the cause, but I don't see any
> > ttys when I do "ls -l /proc//fd".
>
> it's not so much about that, but about which ctty your process has.
There is no controlling tty listed in the output of "ps".
-James M
way), then you will hit this SIGHUP (and bootchart
exits when it receives SIGHUP, so this breaks it).
That appears to have been not working for a while (e.g. it does not work with
systemd v251).
There is an strace log here:
https://github.com/systemd/systemd-bootchart/issues/58
-James M
ignore_proc()).
Also, my process does not have a controlling tty (it is being invoked using the
“init” kernel param).
There is no tty shown when I view its details using ps, and I also don’t see
any ttys when I do “ls -l /proc//fd”.
Any other suggestions?
Maybe I should open a github issue for this.
-James M
sent when init-jm is
invoked using “rdinit”.
Thanks,
-James M
> Isn't systemd-bootchart, like, dead? Last release is nine years old or so.
The last release of systemd-bootchart, v235, was done in November 2023:
https://github.com/systemd/systemd-bootchart/tags
There hasn’t been much activity lately, but I wouldn’t call it dead (there are
a few PRs open th
> I opened https://github.com/systemd/systemd-bootchart/issues/58 to track
> this.
Could someone explain why systemd-bootchart is being sent SIGHUP?
Changing systemd-bootchart to ignore that signal isn’t difficult, but I would
like to understand why PID 1 is sending it.
Note that systemd-boot
> **1. systemd-bootchart stops too early**
>
> According to "man systemd-bootchart", the recommended way to invoke bootchart
> is via a kernel parameter:
>
> init=/usr/lib/systemd/systemd-bootchart
>
> That parameter causes systemd-bootchart to be executed as the new init
> process when we swit
/ time-of-use issue in the code -- it checks
that the proc filesystem is available, but then when it goes to read
/proc/schedstat the file is not there (ENOENT).
Has anyone else come across these?
Should I open github issues?
I can try creating a PR to fix issue 2.
Thanks,
-James M
gt;
> > Thanks for your reply.
> >
> > Is my second statement also correct?
> >
> > i.e. is there no way to prevent mounting a private /tmp when executing
> > generators using something like an environment variable or config setting?
>
> There is none.
I am considering preparing a patch that makes it configurable via system.conf.
e.g., "GeneratorsUsePrivateTmp=yes"
Would a contribution like that be welcome?
-James M
config setting?
I see the condition !MANAGER_IS_TEST_RUN(m) guards the flag FORK_PRIVATE_TMP
but that seems to be just for testing.
-James M
using,
say, an environment variable or a config file setting.
Is that correct?
Thanks,
-James M
'The name of the full unit is formed by inserting the instance
name between "@" and the unit type suffix'. So the complete Unit Name character set then includes
also the character "@".
Of course, that is the cause of the "invalid environment assignment" error. The dash
"-" character, which is allowed and required in the Unit Name character set, is *not*
included or allowed in the Environment File character set.
Why is that? That seems like a pointless and unnecessary limitation, having an
Environment File Variable Name character set *different from* the Unit Name
character set.
Furthermore, notice that the "escaping" name specifiers, "%P", "%J", and "%I", cannot be used with
the Environment File variable names generally, and cannot be used to work-around the dash "-" character limitation, because the
backslash "\" character is also required and used with systemd String Escaping in Unit Names, and is also *not* included or
allowed in the Environment File Variable Name character set.
So, finally, unless there is some use case that can be discovered prohibiting this, it would be best to conform the Unit Name and
the Environment File Variable Name character sets, by simply expanding the Environment File Variable Name character set to
include and allow those additional characters, ":", "-", ".", "\", and "@",
from the Unit Name character set.
James
How do I create a persistent systemd-journald namespace?
I have a backup service that is run by a systemd timer. I would like that
to use it's own namespace. I can create the namespace manually using
systemctl start [email protected]. However I cannot find
a way to do that s
ing been subsequently
"vandalized" by a rather persistent inexperienced and arrogant user.
James
ary Clock and
Ordinary Clock client service, ptp4l.
Are you having a problem with network bonding? Or a problem with your ptp4l?
James
e,
you might simply hard-code what you want, if you are not looking for a generic
solution, and all you want is bonding on a couple of interfaces.
Still, when properly setup, you can individually "start" and "stop" any of the
target units or network service units and get correct behavior.
James
On 1/2/19 5:38 PM, Tom H wrote:
>> Some developers and some users are not native English speakers. In
>> some cases, systemd terminology can be ... less than optimal, while,
>> in other situations, users will simply misunderstand the conventional
>> meaning of words.
> You might not like how "Requ
On 1/2/19 12:50 AM, Olaf van der Spek wrote:
> Activation by itself guarantees basically nothing.
"Activation" guarantees activation. Activating, for instance, a service unit
is quite a bit more significant than "nothing".
>> Because, as far as I know, "Requisite=" is completely broken in syste
On 1/2/19 3:21 AM, Reindl Harald wrote:
> it's
> pretty obvious when i REQUIRE something that it should be there when i
> get started
Not only is it not "obvious" that "something should be there", it is not true.
You are confusing "Requires=" and "Requisite=".
Some developers and some users are
On 1/1/19 8:33 PM, Reindl Harald wrote:
> "After" is a soft dependency, if that unit isn't enabled or don#t exist
> at all it don't matter
>
> "Requires" is a hard dependency and it makes no sense not imply ordering
And then, what do you mean by "soft dependency" and "hard dependency"? It
sound
> It's about Requires and After. I think a unit in Requires should imply
> that unit in After too, otherwise the requirement isn't really met.
> Is there a use case for Requires but not After?
Olaf, previously, on GitHub, you had said:
>> I think I understand Requires and After ...
and, I would
Hi,
I will try to comply:-). I have been building forward from a raspbian
stretch 232 version for my test nodes. But I should be able to switch to
and ubuntu bionic system to test this. I would like to test in a fakeroot,
container or stick; so I am thinking that I need look at mkosi. Any
poi
Hello,
I have been testing the uses of systemd-networkd to configure wireless mesh
networks, and have encountered a problem which manifests itself as a
failure to correctly configure the additional dchp options offered by the
inbuilt dhcpv4 server.
This is related to the following commit.
h
Hello,
It looks like I figured out my problem, I have to use:
result = sd_bus_message_enter_container(msgCall, 'a', "o");
before I try reading the array with :
result = sd_bus_message_read(msgCall, "o", &ptr);
Thanks,
Jimmy
On Thu, Aug 17, 2017 at 1:43
Hello,
Can someone please point me to the correct method for reading an "ao"
signature dbus message using the sd_bus C api?
I am trying to read all the network devices with the following call:
result = sd_bus_get_property(m_bus, "org.freedesktop.NetworkManager",
here a more complete listing anywhere of
what scenarios correspond to what states? If not, what's the expected behavior
here?
--
Thanks,
James Forcier
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
oup* of unit files.
Currently, systemd restricts passing unit names with "enable" template files,
allowing only two parameters to be passed, to resolve template unit names.
Either unit A declares "A Stops B", or unit B declares "B Stopped By A". For
instance, "PartOf
On 15 May 2016 at 08:11, James Hogarth wrote:
>
> On 15 May 2016 06:32, "Andrei Borzenkov" wrote:
> >
> > 15.05.2016 06:36, Chris Murphy пишет:
> > > On Thu, May 12, 2016 at 12:38 PM, James Hogarth <
> [email protected]> wrote:
> > &
On 15 May 2016 06:32, "Andrei Borzenkov" wrote:
>
> 15.05.2016 06:36, Chris Murphy пишет:
> > On Thu, May 12, 2016 at 12:38 PM, James Hogarth
wrote:
> >>
> >> On 2 May 2016 18:58, "James Hogarth" wrote:
> >>>
> >>>
&g
On 2 May 2016 18:58, "James Hogarth" wrote:
>
>
> On 24 Apr 2016 21:31, "poma" wrote:
> >
> > On 20.04.2016 22:42, Chris Murphy wrote:
> > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger <
[email protected]> wrote:
> >
> &g
>
> On 12 May 2016 18:28, "Chris Friesen" wrote:
> >
> > Hi,
> >
> > Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
> >
> > Alternately, can someone suggest a way to get equivalent behaviour (the
ability to set "ethX" names based on MAC
On 24 Apr 2016 21:31, "poma" wrote:
>
> On 20.04.2016 22:42, Chris Murphy wrote:
> > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger
wrote:
>
> [...]
>
> > Anyway, the most complete solution for BIOS, UEFI, and UEFI Secure
> > Boot systems, is fast startups as possible (which helps all kinds of
>
On 20 April 2016 at 10:20, Lennart Poettering
wrote:
> On Wed, 20.04.16 08:00, James Hogarth ([email protected]) wrote:
>
> > Regardless of how the hibernate generator might potentially be changed to
> > attempt to locate a valid swap partition with hibernate data, or
On 20 Apr 2016 05:47, "Chris Murphy" wrote:
>
> On Tue, Apr 19, 2016 at 4:10 AM, Lennart Poettering
> wrote:
>
> >
> > So what precisely are you proposing? That we actively search for the
> > swap partition in the hibernate-resume generator?
>
> I t
On 19 Apr 2016 08:05, "Andrei Borzenkov" wrote:
>
> On Tue, Apr 19, 2016 at 9:45 AM, James Hogarth
wrote:
>
> >
> > Seeing as systemd decides the swap to hibernate to in the first place,
can't
>
> No, it does not. Device to hibernate to is set by prev
On 19 Apr 2016 04:53, "Andrei Borzenkov" wrote:
>
> 19.04.2016 01:19, James Hogarth пишет:
> > Hi all,
> >
> > There's been some discussion today about the impact of
> > https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the
prob
acut cmdline coming
later than the hibernate generator wouldn't be a problem.
Cheers,
James
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
here.
I'm running into this issue on Ubuntu 15.04 (Vivid). If there are any
pointers on how to best determine the script / root cause I'd be very
much appreciative.
Thank you.
On Thu, Oct 1, 2015 at 2:31 PM, Kay Sievers wrote:
> On Thu, Oct 1, 2015 at 7:21 PM, James wrote:
>>
Hello, just following up to see if there were any ideas on what may be
causing this.
Any thoughts appreciated.
On Wed, Sep 23, 2015 at 10:17 PM, James wrote:
> Hello,
>
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name (eth0 -&
Hello,
Hoping someone can point me in the right direction. I'm attempting to
change the interface name (eth0 -> wired) on one of my servers.
Here's the output from the journal:
~# journalctl --no-pager | grep -i wired
Sep 23 17:11:15 vivid systemd-udevd[399]: error changing net interface
name 'e
On 24 Jul 2015 11:55, "Dimitri John Ledkov"
wrote:
>
> On 24 July 2015 at 10:38, James Hogarth wrote:
> > I want a user to be able to systemctl start sslh and use listening
> > addresses in /etc/sslh.cfg as always (so I'm reluctant to put a
> > straight So
On 24 July 2015 at 10:38, James Hogarth wrote:
> Hi,
>
> I'm in the process of adding systemd native sockets to a service
> (rather than using inetd compatibility) and am trying to get my head
> around the proper way to configure the unit files so that the socket
>
d an associated that
has not explicit need of the socket?
Regards,
James
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 8 March 2015 at 22:32, Lennart Poettering wrote:
> On Thu, 05.03.15 22:07, James Hogarth ([email protected]) wrote:
>
>> > Tried to put together a reduced testcase via a yum installroot style
>> > container to switch-root into to see what that behaviour is like an
On 5 March 2015 at 17:07, James Hogarth wrote:
> On 5 March 2015 at 15:10, Lennart Poettering wrote:
>>
>>
>> Right before switch rooting systemd will kill all remaining processes
>> of the initrd, including the strace, hence the strace logs aren't that
>&
On 5 March 2015 at 15:10, Lennart Poettering wrote:
>
>
> Right before switch rooting systemd will kill all remaining processes
> of the initrd, including the strace, hence the strace logs aren't that
> useful either, they end before the transition.
>
> Please boot with "systemd.log_level=debug sy
the crash along
with coredumps that have been generated on the bug.
These tests were carried out with enforcing=0 at the kernel command line so
I'm reasonably confident the bug is not SELinux related.
Cheers,
James
___
systemd-devel mailing lis
Everything works great now, thanks for all of your help!
> On Oct 10, 2014, at 2:13 AM, Lennart Poettering
> wrote:
>
>> On Thu, 09.10.14 23:53, James Lott ([email protected]) wrote:
>>
>> I am using a setup which retains the CAP_NET_ADMIN capability inside t
:12:02 you wrote:
> On Fri, Oct 10, 2014 at 12:13 AM, James Lott wrote:
> > Trying to start up an openvpn connection yields the following error:
> >
> > Thu Oct 9 15:01:52 2014 ERROR: Cannot open TUN/TAP dev /dev/net/tun:
> > Operation not permitted (errno=1)
>
Whoops.. Meant to send the message:
Installing the latest systemd from git fixed this issue. Thanks again for
pointing that out!
On Thursday 09 October 2014 15:14:18 James Lott wrote:
> Hi Lennart!
>
> Thanks for your response! I observed this issue on Arch Linux ARM running
> s
14:08:07 Lennart Poettering wrote:
> On Fri, 03.10.14 10:58, James Lott ([email protected]) wrote:
> > Hello,
> >
> > A little bit back I wrote in about having some difficulties adding network
> > devices to containers. With some help from the list, I figured out how to
process as it attempts to setup the connection. Please let me know if there's
anything else I can provide to be helpful, and thanks again for the help!
On Wednesday 08 October 2014 15:59:03 you wrote:
> On Fri, Oct 3, 2014 at 7:46 PM, James Lott wrote:
> > Hello, list!
> >
> &
Does anyone have any feedback on this thread? If it's not possible for a
container to create its own /dev/net/tun device (or use the host system's),
I'll just move on to finding a less preferable solution.
> On Oct 3, 2014, at 10:46 AM, James Lott wrote:
>
> Hello,
Hello,
A little bit back I wrote in about having some difficulties adding network
devices to containers. With some help from the list, I figured out how to add
my network devices to an already running container using 'iw phy' and 'ip
link'.
However, I have not yet successfully added an interfa
Hello, list!
In some work I've been doing with systemd-nspawn containers, I've been trying
to connect one of my containers to an openvpn network. This conteiner is being
run with the --network-bridge flag to setup its networking, so according to the
documentation, should retain CAP_NET_ADMIN ca
t.
> On Sep 26, 2014, at 4:28 PM, James Lott wrote:
>
> Hello again!
>
> Once again, thanks for all the help with getting my wireless interface moved
> into the container! Now I just have one more interface I'm having trouble
> with. I can't seem to move my et
/net/eth0
lrwxrwxrwx 1 root root 0 Dec 31 1969 eth1 ->
../../devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.0/net/eth1
On Thursday 25 September 2014 17:05:34 James Lott wrote:
> Shame on me for not spending more time trying to figure this out before
> responding. Please
to be coordinating the movement of this
interface within a service file, so I don't need to do it manually when
starting the container... but I suppose I can write an ExecStartPost script
which can manage this.
Thanks again for all your help!
On Thursday 25 September 2014 16:25:02 James
ent solution. I guess
that's what I get for living life on the edge ;)
On Thursday 25 September 2014 18:23:47 Leonid Isaev wrote:
> Hi,
>
> On Wed, Sep 24, 2014 at 08:14:55PM -0700, James Lott wrote:
> > Hello,
> >
> > There is no .network file for the br
>> On Thu, Sep 25, 2014 at 10:40:42AM -0700, James Lott wrote:
>> Hi Mantas,
>>
>> Thanks for the clarification. The first thing I tried actually was using the
>> PID
>> of the systemd-nspawn instance, like so
>>
>> [root@host01 lanvpn]# ps aux | g
that?
On Thursday 25 September 2014 20:11:56 Mantas Mikulėnas wrote:
> On Thu, Sep 25, 2014 at 7:49 PM, James Lott wrote:
> > Hi Marcel,
> >
> > Thanks for the help pointing that one out! With your guidance I was able
> > to
> > figure out that I'll need
884 1128 pts/3S+ 09:15 0:00 systemd-
nspawn --private-network
[root@host01 lanvpn]# ip netns list
[root@host01 lanvpn]#
Any nudges in the right direction are welcome, and appreciated!
On Thursday 25 September 2014 10:21:16 Marcel Holtmann wrote:
> Hi James,
>
> > I'm h
Hello again!
I'm having another issue with private networking in systemd-nspawn. This one
I'm not so certain is a bug, but probably some kind of mistake on my part.
Base on my reading of the systemd-nspawn man page though, I can't figure out
what the problem is. Basically, all I'm tring to do i
service is included in that email
as well).
On Wednesday 24 September 2014 22:44:17 Leonid Isaev wrote:
> Hi,
>
> On Wed, Sep 24, 2014 at 07:16:03PM -0700, James Lott wrote:
> > However, when I try to acquire a dhcp lease through the bridge
> > interface, I am unable to do so
Hello!
With some help from the kind people on this list, I was able to get my basic
network interfaces up and runnign with systemd-networkd. Now I've moved on to
playing with some slightly more complex setups, and have run into some issues
that as far as I can tell may be bugs (but I'm not quit
be? I
want to make sure I keep my eyes peeled for it!
On Friday 19 September 2014 23:04:40 Tom Gundersen wrote:
> On Fri, Sep 19, 2014 at 6:37 PM, James Lott wrote:
> > I am trying to setup and play around with some of the private networking
> > features of systemd, and one of the
Holy smokes, that did it! Many thanks for taking time out of your day to help
me find my silly mistake :)
On Friday 19 September 2014 22:51:41 Tom Gundersen wrote:
> On Fri, Sep 19, 2014 at 6:59 PM, James Lott wrote:
> > Hello again!
> >
> > I've been eager to play wi
Hello again!
I've been eager to play with networking features, in case you couldn't tell ;)
This patricular issue seems separate from my first one though, so I thought it
would be best to discuss separately.
I am trying to use systemd-networkd to essentially replace vconfig. I am using
eth0 as
t@utility01 ~]# pacman -Q systemd
systemd 216-3
I'm happy to run any additional tests or provide any additional information
needed to help try to reproduce. Thanks in advance for any help!
--
James Lott
___
systemd-devel mailing list
systemd-de
/their/
> session on :0.
>
> ...sometimes I think Xorg should start at :1 instead, and reserve :0
> for annoying cronjobs and services that have DISPLAY=":0" hardcoded,
> to remind everyone that they're using a multi-
On Mon, 2013-08-26 at 11:35 +0800, Gao feng wrote:
> On 08/26/2013 11:19 AM, James Bottomley wrote:
> > Yes, we are discussing this problem in this whole thread.
I wasn't really watching that bit, since the problem looks solved to me.
I was just reacting against the unfortunate
On Mon, 2013-08-26 at 09:06 +0800, Gao feng wrote:
> On 08/26/2013 02:16 AM, James Bottomley wrote:
> > On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote:
> >> On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley
> >> wrote:
> >>> On Wed, 2013-08-21 at 11:51
On Sun, 2013-08-25 at 19:37 +0200, Kay Sievers wrote:
> On Sun, Aug 25, 2013 at 7:16 PM, James Bottomley
> wrote:
> > On Wed, 2013-08-21 at 11:51 +0200, Kay Sievers wrote:
> >> On Wed, Aug 21, 2013 at 9:22 AM, Gao feng wrote:
> >> > On 08/21/2013 03:06 PM, Eric W
se it doesn't serve, the hoster
usually has separate container hosting (for a higher price, of course).
James
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Files such as /etc/machine-info have an incompatibility with systemd in regards
to how
it writes and/or parses them. Take the following sample:
PRETTY_HOSTNAME="\'\"\$\`\\"
Systemd will translate this to: '"$`\
However, the shells bash and dash will translate this to: \'"$`\
So, it appears to b
On 1 March 2013 07:24, Cristian Rodríguez wrote:
> Having this confessed non-ideal ReloadOnResume ,StopOnSuspend in unit
> files etc will make extremely easy to avoid relying on either pm-utils
> hooks or those new in /usr/lib/systemd/systemd-sleep and having to patch
> buggy software, most likel
On Tue, 2012-07-10 at 21:29 +0200, David Herrmann wrote:
> Hi Kristian
>
> On Tue, Jul 10, 2012 at 8:15 PM, Kristian Høgsberg
> wrote:
> > On Tue, Jul 10, 2012 at 12:22:13PM -0400, Casey Dahlin wrote:
> >> On Mon, Jul 09, 2012 at 06:17:13PM -0400, Kristian Høgsberg wrote:
> >> > No, wayland is t
On Wed, 2012-07-04 at 20:13 +0200, David Herrmann wrote:
> Hi guys
>
> (CC'ing systemd-ML as they proved to be very helpful and interested in this
> ;))
>
> I am currently working on kmscon and am planning on writing some
> user-space VT logic similar to CONFIG_VT in the kernel. The idea is to
>
On Mon, May 16, 2011 at 2:46 PM, Lennart Poettering
wrote:
> > It takes about 5-6s for udev to run input_id on the keyboard + touchpad,
> and
> > thus for them to be available to X.
>
> How come this takes so long?
>
> Does this actually delay X? Nromally X should be fine without kbd/mouse
> and t
On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering
wrote:
> Our entire userspace bootup takes <1s here on an older X300. I think
> nobody expects that the mouse reacts any quicker than that.
>
> Your "older X300" is probably rather more powerful than a single-core Atom
CPU.
> But as mentioned e
On Thu, May 12, 2011 at 6:59 PM, Gustavo Sverzut Barbieri <
[email protected]> wrote:
>
> Well, maybe you didn't get the activation part or you're trolling :-)
>
> Neither...
> As I said in my mail about the bluetooth part, the problem with kernel
> modules is that "you don't know what's in
On Mon, May 9, 2011 at 4:32 PM, Lennart Poettering
wrote:
> On Mon, 09.05.11 13:13, Scott James Remnant ([email protected]) wrote:
>
> > The System Daemon seems to be where systemd is much more clever; a
> Bluetooth
> > device unit would "want" the System Daemon
On Mon, May 9, 2011 at 12:43 PM, Lennart Poettering
wrote:
> > This means there are a large number of devices already known to the
> kernel
> > at the point that systemd starts, especially if you build the drivers
> into
> > the kernel for those devices. It's possible to get going straight away
>
On Tue, May 10, 2011 at 9:39 AM, Lennart Poettering
wrote:
> Note that you need to delay execution of user code after the base system
> is set up anyway, in order to ensure that the right perms are set on the
> volatile and other directories. That means having a single transaction
> for both user
On Tue, May 10, 2011 at 7:41 AM, Gustavo Sverzut Barbieri <
[email protected]> wrote:
> I'm not following all the user-session discussion, but AFAIU this
> management will be done by the same code, but not same process (it's not
> PID1). PAM (or another entity that has a role in the login/lo
On Mon, May 9, 2011 at 12:16 PM, Gustavo Sverzut Barbieri <
[email protected]> wrote:
>
>> Well, right now let's make clear that Firefox/Chromium or other X clients
>> won't be started by systemd as they are user session applications, and
>> systemd itself will just deal with system context
Thanks for the reply!
On Mon, May 9, 2011 at 11:04 AM, Lennart Poettering
wrote:
> On Mon, 09.05.11 09:10, Scott James Remnant ([email protected]) wrote:
>
> > This seems to assume that it's a free cost to start a service or process
> and
> > have it block on a socke
Thanks for your answers so far, I haven't had a chance to fully read and
digest them yet, but will do so before replying on those threads (if I even
need to, it's likely your responses are complete in of themselves).
My third question is about communicating need; for this I'd like to outline
a use
Another question I wasn't able to find an answer to in the documentation
I've read so far.
The use of device units seems to very much rely on udevd running on the
system, and not only that, udev rules having been parsed for the device and
a systemd tag "set" in the udevdb. udev obviously starts af
1 - 100 of 107 matches
Mail list logo
