Colin Guthrie writes:
> I don't think this really applies here. The day-to-day commands are
> really systemctl, journalctl and loginctl (although the last one is
> likely not often used).
I think it's a bit annoying that systemctl is
a) so long, and
b) tab-completes poorly
'sc'?
--
Henrik Gr
Thierry Reding writes:
> Hi,
>
> Would anyone know why the latest releases no longer work on 3.1 kernels?
> I tried to update from 187 to 196 today and booting the system on a
> vendor kernel based on 3.1.10 no longer gets to the boot prompt. It
> hangs somewhere near where it should actually be
On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote:
> > Any ideas?
>
> I'm running 196 just fine on a 3.0 vendor kernel, so it's not a
> universal problem. I also use getty on the serial port, with no local
> modifications.
>
> I believe the requirement for a 3.4 (or something
On 11/23/2012 02:27 AM, Henrik Grindal Bakken wrote:
> Colin Guthrie writes:
>
>> I don't think this really applies here. The day-to-day commands are
>> really systemctl, journalctl and loginctl (although the last one is
>> likely not often used).
>
> I think it's a bit annoying that systemctl i
On Wed, Nov 21, 2012 at 2:26 PM, Holger Freyther wrote:
> Koen pointed me to a jenkins but it doesn't run make check.
I have it configured right now to run "make test," which does nothing
in systemd builds. I'm happy to update it to include a proper
post-build test, but I'd like consensus on what
I am just starting to experiment with systemd.
My first 'problem' is that the build process does not seem to properly
obey the --prefix= directive.
I get some stuff installed where I tell it with --prefix, and some other
stuff installed in /usr/bin and /usr/lib.
I can get around this easily enou
On Fri, Nov 23, 2012 at 9:43 AM, David Humphreys wrote:
> I am just starting to experiment with systemd.
>
> My first 'problem' is that the build process does not seem to properly
> obey the --prefix= directive.
>
> I get some stuff installed where I tell it with --prefix, and some other
> stuff i
Hi,
My distribution has many isolated services with his /dev/log are
disposed within the environment of isolation, for example:
/var/lib/ldap/dev/log
/var/lib/openvpn/dev/log
/var/spool/postfix/dev/log
How to configure a journalD, which he could read such isolated sockets?
Now I see only one solu
On Fri, 23.11.12 04:31, David Strauss (da...@davidstrauss.net) wrote:
>
> On Wed, Nov 21, 2012 at 2:26 PM, Holger Freyther wrote:
> > Koen pointed me to a jenkins but it doesn't run make check.
>
> I have it configured right now to run "make test," which does nothing
> in systemd builds. I'm ha
On Thu, 22.11.12 11:19, Shea Levy (s...@shealevy.com) wrote:
> Hi all,
>
> rngd currently supports three sources of randomness to increase the
> kernel's entropy pool: The hwrng device, the trusted platform module
> device, and the RdRand x86 instruction. We don't want to start the
> daemon when
On Thu, 22.11.12 13:27, Thomas Bächler (tho...@archlinux.org) wrote:
> For me, the major problem is that the selection of "seat master devices"
> is hard-coded in logind (it selects devices of type "graphics" from
> udev, [1]). Step 1 would be to move that to a udev rule: Add a
> "seatmaster" tag
On Thu, 22.11.12 23:04, Oleg Samarin (osamari...@gmail.com) wrote:
> В Ср., 21/11/2012 в 20:23 +0100, Lennart Poettering пишет:
>
> > I think there are other ways thinkable, where we don't have to add
> > explicit nvidia-compatibility switches. For example, instead of
> > explicitly watching for
El 23/11/12 11:38, Lennart Poettering escribió:
That said, what's the reason for having a userspace component for this
at all? Why isn't all of this done inside the kernel? I mean, the kernel
/dev/random stuff already has hooks into various subsystems to get
entropy, it sounds trivial to also ho
On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote:
> Thierry Reding writes:
>
> > Hi,
> >
> > Would anyone know why the latest releases no longer work on 3.1 kernels?
> > I tried to update from 187 to 196 today and booting the system on a
> > vendor kernel based on 3.1.10 no
On Fri, Nov 23, 2012 at 10:41:20AM +0100, Tomasz Torcz wrote:
> On Fri, Nov 23, 2012 at 10:29:53AM +0100, Henrik Grindal Bakken wrote:
> > > Any ideas?
> >
> > I'm running 196 just fine on a 3.0 vendor kernel, so it's not a
> > universal problem. I also use getty on the serial port, with no local
---
shell-completion/systemd-zsh-completion.zsh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/shell-completion/systemd-zsh-completion.zsh
b/shell-completion/systemd-zsh-completion.zsh
index 7799bf6..a58f4ae 100644
--- a/shell-completion/systemd-zsh-completion.zsh
+++ b/shell
Currently on Slackware 14.0 and that came with udev 182 and kernel 3.2.29.
Under this configuration udev works properly, specifically
/etc/udev/rules.d/70-persistent-cd.rules gets recreated if it doesn't exist
and it is also USED to create certain links and dev nodes such as
/dev/dvdrom. Once I m
On Saturday 2012-11-24 06:08, Nelson wrote:
>Currently on Slackware 14.0 and that came with udev 182 and kernel 3.2.29.
> Under this configuration udev works properly, specifically
>/etc/udev/rules.d/70-persistent-cd.rules gets recreated if it doesn't exist
>and it is also USED to create certain
According to bootup(7) stopping services and unmounting of filesystems
happens in parallel. Is there any sort of implicit dependencies between
running services and filesystems? I do not see anything besides
dependencies explicitly listed in unit files.
So am I right to assume that systemd just con
While my issue is still with udev 182 and kernel 3.6.7,
does 70-persistent-cd.rules even get USED at all if it was created
beforehand with 183?
On Sat, Nov 24, 2012 at 12:35 AM, Jan Engelhardt wrote:
>
> On Saturday 2012-11-24 06:08, Nelson wrote:
>
> >Currently on Slackware 14.0 and that came
20 matches
Mail list logo
