В Sun, 24 Aug 2014 06:49:39 +0200
Simon Peeters пишет:
> 2014-08-24 6:45 GMT+02:00 Simon Peeters :
> > 2014-08-24 6:23 GMT+02:00 Andrei Borzenkov :
> >> В Sun, 24 Aug 2014 03:04:03 +0200
> >> Simon Peeters пишет:
> >>
> >>> Hej all,
> >>>
> >>> I have a system on wich i wish to randomise the mac
2014-08-24 6:45 GMT+02:00 Simon Peeters :
> 2014-08-24 6:23 GMT+02:00 Andrei Borzenkov :
>> В Sun, 24 Aug 2014 03:04:03 +0200
>> Simon Peeters пишет:
>>
>>> Hej all,
>>>
>>> I have a system on wich i wish to randomise the mac address of one
>>> specific interface. This is important because it is a
2014-08-24 6:23 GMT+02:00 Andrei Borzenkov :
> В Sun, 24 Aug 2014 03:04:03 +0200
> Simon Peeters пишет:
>
>> Hej all,
>>
>> I have a system on wich i wish to randomise the mac address of one
>> specific interface. This is important because it is a wireless vif,
>> and having multiple vif's with th
В Sun, 24 Aug 2014 03:04:03 +0200
Simon Peeters пишет:
> Hej all,
>
> I have a system on wich i wish to randomise the mac address of one
> specific interface. This is important because it is a wireless vif,
> and having multiple vif's with the same mac doesn't work.
>
> I currently have the fol
We assumed that objects in a unique chain are good enough,
and only checked object type. But mmap code crashes when some object
has zero size. This most likely is caused by a corrupted journal
file, but we should fail gracefully.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758392
https://bug
Rather than requiring a third-party tool for this, systemctl should
handle this natively.
---
TODO | 1 +
1 file changed, 1 insertion(+)
diff --git a/TODO b/TODO
index 0fcd3a0..aaf6444 100644
--- a/TODO
+++ b/TODO
@@ -441,6 +441,7 @@ Features:
- Something is wrong with symlink handling of "aut
Hej all,
I have a system on wich i wish to randomise the mac address of one
specific interface. This is important because it is a wireless vif,
and having multiple vif's with the same mac doesn't work.
I currently have the following config in 50-wl-mac.link:
[Match]
Path=/devices/ocp.3/4740.u
On 23 August 2014 13:46, Luca Bruno wrote:
> I'm going to do an experiment with NixOS: replace the whole current initrd
> process made of scripts and hooks with systemd.
What a coincidence... I just switched to NixOS last week, moved some
file systems around, and promptly broke my boot. Badly.
T
On Sat, Aug 23, 2014 at 10:28 PM, Damian Ivanov wrote:
>>Can't these two ports be used instead of buying a usb display link ?
> Yes. That's what it actually mean's. I've read that people want to
> improve the drivers in that part in the future, so this could be done,
> but at the moment, no it's n
>Can't these two ports be used instead of buying a usb display link ?
Yes. That's what it actually mean's. I've read that people want to
improve the drivers in that part in the future, so this could be done,
but at the moment, no it's not possible.
___
sy
Good time of day list, i just want to hear your opinions - pro and con
Pre story:
Before i install bunch of systemd-{networkd,resolved} and
wpa_supplicant (for connecting to HotSpots)
After i spend some time to think about network handling by networkd
and resolved, about some cases and i have ide
On Sat, Aug 23, 2014 at 9:55 PM, arnaud gaboury
wrote:
> On Sat, Aug 23, 2014 at 8:48 PM, Damian Ivanov
> wrote:
>> Yeah, so tl,dr what this is trying to say with one GPU and two
>> connectors, no multiseat possible using logind (yet, though this
>> was/is a planned feature). This is not a syste
On Sat, Aug 23, 2014 at 8:48 PM, Damian Ivanov wrote:
> Yeah, so tl,dr what this is trying to say with one GPU and two
> connectors, no multiseat possible using logind (yet, though this
> was/is a planned feature). This is not a systemd/logind problem rather
> than the driver provides you only one
I have been able to write some udev rules.d for usb mouse/keyboard.
I plugout the device, then
$ dmesg | tail -n 4
~~
[21145.269421] input: Logitech USB-PS/2 Optical Mouse as
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:046D:C03E.000E/input/input30
~~
$ udevadm info --query=a
On Saturday 23 August 2014 at 21:05:13, Tobias Geerinckx-Rice wrote:
> On 23 August 2014 14:47, Ivan Shapovalov wrote:
> > This is my first patch to this project, so feel free to flak me for missing
> > something obvious :)
>
> On 4 August 2014 10:39, Tobias Geerinckx-Rice
> wrote:
> > (As t
Actually use the variable containing the return code of bus_process_wait when
printing the error message as a result of it failing.
---
src/systemctl/systemctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index d9b8bee.
On 23 August 2014 14:47, Ivan Shapovalov wrote:
> This is my first patch to this project, so feel free to flak me for missing
> something obvious :)
On 4 August 2014 10:39, Tobias Geerinckx-Rice
wrote:
> (As this is my first systemd patch, feel free to flak me for missing
> something obvious.)
resume-generator understands resume= kernel command line parameter and
instantiates the [email protected] accordingly if it is passed.
This enables resume from hibernation using device specified on the kernel
command line, where the device path may point to an arbitrary udev-created
symlink,
This patchset allows systemd to parse resume= kernel command line parameter
and initiate resume from the specified device.
It adds:
- a 'systemd-resume' tool which takes path to a device node and
writes its major:minor to /sys/power/state;
- a corresponding '[email protected]' templated un
With this change, it becomes possible to order a unit to activate before any
modifications to the file systems. This is especially useful for supporting
resume from hibernation.
---
units/[email protected] | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/units/systemd-f..
This can be used to initiate a resume from hibernation by path to a swap
device containing the hibernation image.
The respective templated unit is also added. It is instantiated using
path to the desired resume device.
---
Makefile-man.am | 7
Makefile.am
Yeah, so tl,dr what this is trying to say with one GPU and two
connectors, no multiseat possible using logind (yet, though this
was/is a planned feature). This is not a systemd/logind problem rather
than the driver provides you only one path per GPU (not a seperate per
port/connector). You could ge
On 23.08.2014 19:21, arnaud gaboury wrote:
> I do not understand why I can't see any output about my
> /sys/class/drm/card0 when running
> --
> $ loginctl seat-status seat0
> The only entry I see referring to graphics is this line (I boot in EUFI).
> ├─/sys/devices/pla
I do not understand why I can't see any output about my
/sys/class/drm/card0 when running
--
$ loginctl seat-status seat0
The only entry I see referring to graphics is this line (I boot in EUFI).
├─/sys/devices/platform/efi-framebuffer.0/graphics/fb0
>
> $ udevadm info -q env -p /sys/class/drm/card1
> DEVNAME=/dev/dri/card1
> DEVPATH=/devices/pci:00/:00:10.0/:01:00.0/drm/card1
> DEVTYPE=drm_minor
> ID_FOR_SEAT=drm-pci-_01_00_0
> ID_PATH=pci-:01:00.0
> ID_PATH_TAG=pci-_01_00_0
> MAJOR=226
> MINOR=1
> SUBSYSTEM=drm
> TAGS=
>
>
> Don't forget to post config here when you're done. ;)
>
Ok, now I have a roadmap. TY so much.
I will post here AND modify the old multi-seat archwiki, when successful.
Ty for the link to the fedora thread. I guess soon each user will then
be able to start a systemd user instance x session
On 23.08.2014 15:10, arnaud gaboury wrote:
> Archlinux 3.16.1
> systemd 215-4
> Xorg 1.16
>
>
> Until now, I have been enable to set a dual seat following the
> archwiki[1]. In short, I had to modify the /etc/X11/xorg.conf
> accordingly, then $ startx -- layout seat0 -config
> xorg.conf.multiseat
On Saturday 23 August 2014 at 18:22:42, Andrei Borzenkov wrote:
> В Sat, 23 Aug 2014 16:47:51 +0400
> Ivan Shapovalov пишет:
>
> > This patchset allows systemd to parse resume= kernel command line parameter
> > and initiate resume from the specified device.
> >
> > It adds:
> > - a 'systemd-res
В Sat, 23 Aug 2014 17:28:27 +0200
arnaud gaboury пишет:
> > E: TAGS=:seat:uaccess:
>
> Ok, I see. I do not have this tag for my card.
> I see you use xf86-video-nouveau. Am I correct?
No, I use nVidia binary drivers.
> Shall I the install
> xf86-
On Sat, Aug 23, 2014 at 5:26 PM, Damian Ivanov wrote:
> I would try with an openSUSE/Fedora Live CD first, because I know it
> works and if it works for you too but fails on Arch, you may be
> missing some patches/config and we could see where it fails maybe.
> Especially the gdm thing required a
> E: TAGS=:seat:uaccess:
Ok, I see. I do not have this tag for my card.
I see you use xf86-video-nouveau. Am I correct? Shall I the install
xf86-video-nouveau ?
--
google.com/+arnaudgabourygabx
___
systemd-devel mailing list
[email protected]
I would try with an openSUSE/Fedora Live CD first, because I know it
works and if it works for you too but fails on Arch, you may be
missing some patches/config and we could see where it fails maybe.
Especially the gdm thing required a few patches a while ago, don't
know if they are all upstream no
В Sat, 23 Aug 2014 16:50:31 +0200
arnaud gaboury пишет:
> >
> > You probably want graphic device under it, something like
> >
> > /sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
>
>
> # loginctl attach seat1 /sys/bus/pci/devices/:01:00.0/drm/card0
> No error thrown, but:
>
>
With right distro I mean which carry the patches so the multiseat
stuff works. Don't know if Arch has them. Last time I tried gdm was
_required_ for a graphical multi-seat session.
With monitor I meant the gpu... and you need to figure out which of
the usb devices is your keyboard.
___
> You can get a list of all usable devices including their path by
> loginctl seat-status seat0
loginctl seat-status seat0
seat0
Sessions: *c2 c1
Devices:
├─/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
│ input:input6 "Power Button"
>
> You probably want graphic device under it, something like
>
> /sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0
# loginctl attach seat1 /sys/bus/pci/devices/:01:00.0/drm/card0
No error thrown, but:
# loginctl list-seats
SEAT
seat0
1 seats listed.
No new seat1 !
% udevadm
You can get a list of all usable devices including their path by
loginctl seat-status seat0
after that attach a monitor and keyboard (and optionally mouse) and if
you run the right distribution (I've tried with openSUSE and Fedora)
and run gdm as login manager, you new gdm should pop up as soon as
В Sat, 23 Aug 2014 16:26:33 +0200
arnaud gaboury пишет:
> > I understand from loginctl(1) I have to first create 1 new seat with
> > loginctl using 1 existing graphic device:
> > $ attach seat1 /sys/bus/pci/device/:00:01.0@ (my graphic card as
> > listed by $lspci).
>
> Not a very good start
> I understand from loginctl(1) I have to first create 1 new seat with
> loginctl using 1 existing graphic device:
> $ attach seat1 /sys/bus/pci/device/:00:01.0@ (my graphic card as
> listed by $lspci).
Not a very good start :-(
$ lspci
01:00.0 VGA compatible controller: NVIDIA Corporation GK
В Sat, 23 Aug 2014 16:47:51 +0400
Ivan Shapovalov пишет:
> This patchset allows systemd to parse resume= kernel command line parameter
> and initiate resume from the specified device.
>
> It adds:
> - a 'systemd-resume' tool which takes path to a device node and
> writes its major:minor to /sy
В Sat, 23 Aug 2014 16:47:53 +0400
Ivan Shapovalov пишет:
> diff --git a/units/[email protected]
> b/units/[email protected]
> new file mode 100644
> index 000..f760f16
> --- /dev/null
> +++ b/units/[email protected]
> @@ -0,0 +1,23 @@
> +# This file is part of sys
Hej,
2014-08-23 13:46 GMT+02:00 Luca Bruno :
> I'm going to do an experiment with NixOS: replace the whole current initrd
> process made of scripts and hooks with systemd.
>
> Before doing any work however I'd like to hear whether systemd in initrd is
> still wanted in the future, or there's any p
Archlinux 3.16.1
systemd 215-4
Xorg 1.16
Until now, I have been enable to set a dual seat following the
archwiki[1]. In short, I had to modify the /etc/X11/xorg.conf
accordingly, then $ startx -- layout seat0 -config
xorg.conf.multiseat.
I am now trying to migrate to the new facilities for multi
This patchset allows systemd to parse resume= kernel command line parameter
and initiate resume from the specified device.
It adds:
- a 'systemd-resume' tool which takes path to a device node and
writes its major:minor to /sys/power/state;
- a corresponding '[email protected]' templated un
resume-generator understands resume= kernel command line parameter and
instantiates the [email protected] accordingly if it is passed.
This enables resume from hibernation using device specified on the kernel
command line, where the device path may point to an arbitrary udev-created
symlink,
This can be used to initiate a resume from hibernation by path to a swap
device containing the hibernation image.
The respective templated unit is also added. It is instantiated using
path to the desired resume device.
---
Makefile-man.am | 9 +
Makefile.am
With this change, it becomes possible to order a unit to activate before any
modifications to the file systems. This is especially useful for supporting
resume from hibernation.
---
units/[email protected] | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/units/systemd-f..
I'm going to do an experiment with NixOS: replace the whole current initrd
process made of scripts and hooks with systemd.
Before doing any work however I'd like to hear whether systemd in initrd is
still wanted in the future, or there's any possible idea about dropping
this support.
Also, apart
48 matches
Mail list logo
