On Sun Nov 29, 2020 at 1:14 PM CET, Lone_Wolf wrote:
> It wasn't clear to me (and still is not) what initramfs environment your
> questions were about.
>
>
> Do you want answers based on systemd manpages OR on a systemd initramfs
> as setup by mkinitcpio on archlinux ?
As I conjecture below, I
On 28-11-2020 19:24, Riccardo Paolo Bestetti wrote:
I'm informed on what the supported boot processed for Arch are, and I
very well known which one I'm running, as I configured it. :)
I'm grateful for your help, but you didn't really answer any of my
questions, which are about some specifics
"Riccardo Paolo Bestetti" wrote:
> I2'm trying to fully make sense of the boot process with systemd.
>
> I've read various pages from the manual, including bootup(7). There are
> two points I don't fully understand.
>
> * Filesystem mounts during initrd
> The man page, under the initrd
On Sat Nov 28, 2020 at 1:58 PM CET, Lone_Wolf wrote:
> Archlinux has its own boot process, described at [1]
>
> Check the initramfs section and you'll see a reference to mkinitcpio [2]
> .
>
> On the mkinitcpio page look at the Common Hooks section.
>
> Basically there are 2 systems that archlinux
On 28-11-2020 10:22, Riccardo Paolo Bestetti wrote:
I2'm trying to fully make sense of the boot process with systemd.
I've read various pages from the manual, including bootup(7). There are
two points I don't fully understand.
* Filesystem mounts during initrd
The man page, under the initrd
I2'm trying to fully make sense of the boot process with systemd.
I've read various pages from the manual, including bootup(7). There are
two points I don't fully understand.
* Filesystem mounts during initrd
The man page, under the initrd section, says: "systemd detects that it
is run within an
It seems that we have splash-arch.bmp included with Arch Linux systemd package.
The included .bmp image is the two-color standard version (arch word in black
text). It would be useful to also include the two-color inverted version (for
dark backgrounds, also Arch main logo).
The .bmp images
The fact is that pushing to get some experimental software installed
and, especially, configured by default in Arch is rude from my
viewpoint (as an Arch user), extremely so when
* There are alternatives already in the Arch repos, while this one is
not even packaged
* "This is a project in
Hi Chris,
> I consider your response:
> 1. Disrespectful to me.
I agree.
> Is this sort response representative of the Arch Linux community?
A minority seem to think OpenBSD's, perhaps inaccurate, reputation is a
target.
> Relative newcomers, and first time posters, should expect this kind of
El vie., 17 ene. 2020 a las 5:18, Chris Murphy
() escribió:
> Is this sort response representative of the Arch Linux community?
> Relative newcomers, and first time posters, should expect this kind of
> hostility? I think it's embarrassing.
In arch-general list can write anyone. Just ignore him.
> ... installed by default ...
> ... Is it really a feature that the user needs to know about specific
> implementations?
> ... always including it in an installation by default, just like the existing
> swap units, rather than expecting users to manually install a package.
You obviously know
> From: Chris Murphy
> Sent: Mon Jan 13 05:51:15 CET 2020
> To:
> Subject: [arch-general] systemd-zram generator
>
>
> Hi,
>
> swap-create@.service generator for zram devices
> https://github.com/systemd/zram-generator
>
> zram: Compressed RAM based block
Hi,
swap-create@.service generator for zram devices
https://github.com/systemd/zram-generator
zram: Compressed RAM based block devices
https://www.kernel.org/doc/Documentation/blockdev/zram.txt
The gist is, if a configuration file exists, a /dev/zram0 device is
created during early boot and
On 2018-06-30 13:55:18 (+0200), Tinu Weber wrote:
> On Sat, Jun 30, 2018 at 13:34:11 +0200, Bjoern Franke wrote:
> > > Are you truly logged in as this second user for whom it does not work,
> > > or just su(1)'d, etc?
> >
> > Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
On Sat, Jun 30, 2018 at 13:34:11 +0200, Bjoern Franke wrote:
> > Are you truly logged in as this second user for whom it does not work,
> > or just su(1)'d, etc?
>
> Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
> an own zsh as user2 would do the right thing.
-s only
Hi Bjoern,
> > Are you truly logged in as this second user for whom it does not
> > work, or just su(1)'d, etc?
>
> Erm, just used "sudo -u user2 -s" to login as user2. I assumed
> spawning an own zsh as user2 would do the right thing.
It doesn't here. As UID 1000 logged into an XFCE desktop
Hi Ralph,
>
> Are you truly logged in as this second user for whom it does not work,
> or just su(1)'d, etc?
Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
an own zsh as user2 would do the right thing.
> My guess is there's a user.service running for the user ID where
Hi Bjoern,
> > I'm trying to create a systemd timer for a user to run duply daily.
> > For one user the enabled worked fine, but another one:
> >
> > systemctl --user enable backup.timer
> > Failed to connect to bus: No such file or directory
Are you truly logged in as this second user
On 27 June 2018 at 08:26, Bjoern Franke wrote:
> Hi,
>
> I'm trying to create a systemd timer for a user to run duply daily. For
> one user the enabled worked fine, but another one:
>
> systemctl --user enable backup.timer
> Failed to connect to bus: No such file or directory
>
> I have no clue
Hi,
> Good,
>
> Each user + the system has his own dbus. Normally, you should have
> dbus.service and dbus.socket units somewhere (/usr/lib/systemd/user
> and/or /etc/systemd/user and/or .config/systemd/user)
>
> If it works correctly for one of the users, then probably
> /usr/lib/systemd/user
> systemctl --user status has the same error. How do I start dbus for the
> second user? systemctl enable --user dbus fails due the same error, and
> system's dbus is running.
Good,
Each user + the system has his own dbus. Normally, you should have
dbus.service and dbus.socket units somewhere
Hi Ismael,
thanks for your both hints.
>
> The two clues I have according to your error are
> - Is .config/systemd/user created? (Maybe it has to be created manually)
Yes, I've dropped there the timer and service file.
> - Does the second user have dbus started correctly? (for instance, does
Hi Bjoern,
> I'm trying to create a systemd timer for a user to run duply daily. For
> one user the enabled worked fine, but another one:
>
> systemctl --user enable backup.timer
> Failed to connect to bus: No such file or directory
>
> I have no clue why this happens, systemctl daemon-reload
Hi,
I'm trying to create a systemd timer for a user to run duply daily. For
one user the enabled worked fine, but another one:
systemctl --user enable backup.timer
Failed to connect to bus: No such file or directory
I have no clue why this happens, systemctl daemon-reload (also with
--user) did
Hi,
>
> from time to time, systemd-suspend hangs on my Thinkpad X140e. After
> starting a suspend (through e.g. closing the lid), the following happens:
>
>
For the record: The issue was caused by setting any other alpm policy
than "max_performance" (Redhat has a bugreport for it:
Hi,
from time to time, systemd-suspend hangs on my Thinkpad X140e. After
starting a suspend (through e.g. closing the lid), the following happens:
Mär 21 22:32:56 ostrea systemd[1]: Started Suspend.
Mär 21 23:26:07 ostrea systemd[1]: Starting Suspend...
Mär 21 23:26:07 ostrea
Related bug: https://bugs.archlinux.org/task/56828
The issue is caused because systemd assumes that nobody user have the
UID 65534, but in Arch Linux it have the UID 99.
Temporally fix is do a `chown 65534` to the file. And take note that
the `ls -l` command shows nobody with UID 99 and 65534
I will be out of the office from January until March.
If you need immediate assistance please contact the office.
Kind Regards,
On Fri, Feb 02, 2018 at 11:23:34AM +0800, Oon-Ee Ng via arch-general wrote:
> On Fri, Feb 2, 2018 at 9:40 AM, Oon-Ee Ng wrote:
>
> > Did something change recently w.r.t this? I have smbd, postgresql, and
> > squid all failing on me with the following error:-
> >
> >
Hi,
I'm enjoying a holiday at sea and will be off the grid until the end of month!
I'll get back to you that week. You could also reach out to my colleagues via
the support mail.
Thanks for your patience and talk to you then!
Best regards,
On Fri, Feb 2, 2018 at 9:40 AM, Oon-Ee Ng wrote:
> Did something change recently w.r.t this? I have smbd, postgresql, and
> squid all failing on me with the following error:-
>
> systemd[1]: smbd.service: Permission denied while opening PID file or
> unsafe symlink chain:
Hello,
Thank you for your mail. I will answer as fast as possible.
Did something change recently w.r.t this? I have smbd, postgresql, and
squid all failing on me with the following error:-
systemd[1]: smbd.service: Permission denied while opening PID file or
unsafe symlink chain: /var/run/smbd.pid
systemd[1]: postgresql.service: Permission denied while opening
On 09/19/2017 09:36 PM, Marc Boocha via arch-general wrote:
> I am unable to send to arch-dev-public for some reason so i am send my
> reply to arch general.
You need to be whitelisted to post on arch-dev-public, since its purpose
is to offer a publicly *readable* medium for the Developers,
I am unable to send to arch-dev-public for some reason so i am send my
reply to arch general.
I think the filesystem can be split, the sysuser/tempfile will be in the
independent package. I do believe we seriously need a meta package for
some parts of base. Systemd, Glibc, PAM, Filesystem,
arch-general <arch-general@archlinux.org>
Subject: Re: [arch-general] systemd on bios computer
That's not a package I specifically installed, but may have been pulled in by
another package dependency. I'll check for the package and remove it if
found.
On Wed, 5 Jul 2017, Eli Schwartz via
<arch-general@archlinux.org>
>> To: arch-general@archlinux.org
>> Cc: Eli Schwartz <eschwart...@gmail.com>
>> Subject: Re: [arch-general] systemd on bios computer
>>
>> On 07/04/2017 02:52 PM, Jude DaShiell wrote:
>>> When doing a systemd upgrade I g
rch-general@archlinux.org>
To: arch-general@archlinux.org
Cc: Eli Schwartz <eschwart...@gmail.com>
Subject: Re: [arch-general] systemd on bios computer
On 07/04/2017 02:52 PM, Jude DaShiell wrote:
When doing a systemd upgrade I get:
(3/7) Upgrading systemd-boot...
Couldn't find EFI syst
On 07/04/2017 02:52 PM, Jude DaShiell wrote:
> When doing a systemd upgrade I get:
> (3/7) Upgrading systemd-boot...
> Couldn't find EFI system partition. It is recommended to mount it to
> /boot. Alternatively, use --path= to specify path to mount point.
> error: command failed to execute
Jude DaShiell on Tue, 2017/07/04 14:52:
> When doing a systemd upgrade I get:
> (3/7) Upgrading systemd-boot...
> Couldn't find EFI system partition. It is recommended to mount it to
> /boot. Alternatively, use --path= to specify path to mount point.
> error: command failed
On 07/04/2017 01:52 PM, Jude DaShiell wrote:
> When doing a systemd upgrade I get:
> (3/7) Upgrading systemd-boot...
> Couldn't find EFI system partition. It is recommended to mount it to
> /boot. Alternatively, use --path= to specify path to mount point.
> error: command failed to execute
Just ignore this error, as it is irrelevant to your machine.
W dniu 04.07.2017 o 20:52, Jude DaShiell pisze:
> When doing a systemd upgrade I get:
> (3/7) Upgrading systemd-boot...
> Couldn't find EFI system partition. It is recommended to mount it to
> /boot. Alternatively, use --path= to
When doing a systemd upgrade I get:
(3/7) Upgrading systemd-boot...
Couldn't find EFI system partition. It is recommended to mount it to
/boot. Alternatively, use --path= to specify path to mount point.
error: command failed to execute correctly
Are either of the above alternatives even viable
eneral Discussion about Arch Linux <arch-general@archlinux.org>
To: General Discussion about Arch Linux <arch-general@archlinux.org>
Subject: Re: [arch-general] systemd latest upgrade
On 01/31/17 at 04:18pm, Jude DaShiell wrote:
For the last several systemd upgrades an error complaini
On 01-02-17 10:12, Jelle van der Waa wrote:
On 01/31/17 at 04:18pm, Jude DaShiell wrote:
However any package install now finishes with the
message:
Arming ConditionNeedsUpdate
That's just a pacman hook to touch /var, for the recent CVE issue in
systemd [1] [2]
[1]
On 01/31/17 at 04:18pm, Jude DaShiell wrote:
> For the last several systemd upgrades an error complaining about a missing
> uefi directory has come out when those upgrades were being installed. Today
> that happened too.
No clue
> However any package install now finishes with the
> message:
>
For the last several systemd upgrades an error complaining about a missing
uefi directory has come out when those upgrades were being installed.
Today that happened too. However any package install now finishes with
the message:
Arming ConditionNeedsUpdate
This system is an old x86-64
Op 8 dec. 2016 02:53 schreef "sivmu" :
>
> Am 08.12.2016 um 02:01 schrieb Leonid Isaev:
> > On Wed, Dec 07, 2016 at 11:56:25PM +0100, sivmu wrote:
> >> [...] Systemd happened!
> >> Or rather systemd-resolved and the systemd time sync daemon.
[...]
> Thats concerning...
> Maybe
On 2016-12-07 23:56, sivmu wrote:
> Today I noticed there were network services running on my system.
> I DON'T have have permanently running network services.
> WTF happened? Systemd happened!
> Or rather systemd-resolved and the systemd time sync daemon.
>
> It seems that a recent update set
Am 08.12.2016 um 02:01 schrieb Leonid Isaev:
> On Wed, Dec 07, 2016 at 11:56:25PM +0100, sivmu wrote:
>> Today I noticed there were network services running on my system.
>> I DON'T have have permanently running network services.
>> WTF happened? Systemd happened!
>> Or rather systemd-resolved
On Wed, 7 Dec 2016 18:01:59 -0700, Leonid Isaev wrote:
>resolved and timesyncd are not enabled in systemd 232-6
Neither in 232-4 from core.
On Wed, Dec 07, 2016 at 11:56:25PM +0100, sivmu wrote:
> Today I noticed there were network services running on my system.
> I DON'T have have permanently running network services.
> WTF happened? Systemd happened!
> Or rather systemd-resolved and the systemd time sync daemon.
>
> It seems that a
On Wed, 7 Dec 2016 23:56:25 +0100, sivmu wrote:
>Today I noticed there were network services running on my system.
What network services? How could I check this?
[rocketmouse@archlinux ~]$ grep systemd /var/log/pacman.log | tail -4
[2016-12-01 12:53] [ALPM] upgraded libsystemd (231-4 -> 232-4)
On Wed, 7 Dec 2016 23:56:25 +0100
sivmu wrote:
> Today I noticed there were network services running on my system.
> I DON'T have have permanently running network services.
> WTF happened? Systemd happened!
> Or rather systemd-resolved and the systemd time sync daemon.
>
> It
Today I noticed there were network services running on my system.
I DON'T have have permanently running network services.
WTF happened? Systemd happened!
Or rather systemd-resolved and the systemd time sync daemon.
It seems that a recent update set those services to start by default.
I thought I
On Mon, 14 Nov 2016 23:25:45 +0100
Tung Anh Vu via arch-general wrote:
> I managed to make the boot menu screen not appear by holding the minus key
> down to 0 second timeout in the boot menu itself.
> Thanks everyone, especially David Thurstenson.
>
> PS: I still
I managed to make the boot menu screen not appear by holding the minus key
down to 0 second timeout in the boot menu itself.
Thanks everyone, especially David Thurstenson.
PS: I still have no idea, why does systemd-boot ignore the timeout setting
from loader.conf, but obeys the rest.
On Mon, Nov
timeout 0 <-- in loader.conf 1st line
default arch <-- in loader.conf 2nd line
On 11/14/2016 12:58 PM, David Thurstenson via arch-general wrote:
On Mon, Nov 14, 2016 at 12:55 PM, Tung Anh Vu via arch-general
wrote:
Exactly. I'm successfully booting, so the
I just tried and it didn't help. Just in case, is the location
/boot/loader/loader.conf correct?
Also, do I need to explicitly reload the conf file using some bootctl
command?
On Mon, Nov 14, 2016 at 7:58 PM, David Thurstenson via arch-general <
arch-general@archlinux.org> wrote:
> Try setting
On Mon, Nov 14, 2016 at 12:55 PM, Tung Anh Vu via arch-general
wrote:
> Exactly. I'm successfully booting, so the /boot/loader/entries/arch.conf is
> present and appears to be correct.
> My problem is, that I'm trying to make the boot menu to *not* appear, but
>
Exactly. I'm successfully booting, so the /boot/loader/entries/arch.conf is
present and appears to be correct.
My problem is, that I'm trying to make the boot menu to *not* appear, but
without any success.
On Mon, Nov 14, 2016 at 7:47 PM, David Thurstenson via arch-general <
On Mon, Nov 14, 2016 at 12:39 PM, Zachary Kline wrote:
> Hello,
>
> I think the boot menu will still appear, because the default boot entry just
> indicates which OS will be booted after the timeout. It doesn’t stop the menu
> from appearing, or you couldn’t pick another
Hello,
I think the boot menu will still appear, because the default boot entry just
indicates which OS will be booted after the timeout. It doesn’t stop the menu
from appearing, or you couldn’t pick another OS easily.
Best,
Zack.
> On Nov 14, 2016, at 10:02 AM, Tung Anh Vu via arch-general
>
To: arch-general@archlinux.org
Cc: Tung Anh Vu <cutt...@gmail.com>
Subject: [arch-general] systemd-boot ignores loader.conf
Hello all,
I'm using systemd-boot on my laptop. My /boot/loader/loader.conf contains only
the line:
default arch
but when booting, the boot menu still appears. What
Hello all,
I'm using systemd-boot on my laptop. My /boot/loader/loader.conf contains
only the line:
default arch
but when booting, the boot menu still appears. What could be the cause of
this issue? Thanks in advance.
- Tung Anh
Hello David,
Am 13.10.2016 um 14:51 schrieb David Runge:
Hello Peter,
[...]
blueman-applet doesn't show any bluetooth devices and doesn't even search
for those.
Hm, does it show your builtin hardware in the "Adapter" menu?
If so, you're all set to go, just have to make your computer
Hello Peter,
On 2016-10-13 13:33:27 (+0200), Peter Nabbefeld wrote:
> Okt 13 05:05:47 tuchola systemd[1]: Starting Bluetooth service...
> Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth daemon 5.41
> Okt 13 05:05:48 tuchola systemd[1]: Started Bluetooth service.
> Okt 13 05:05:48 tuchola
Hello David,
Am 13.10.2016 um 13:04 schrieb David Runge:
Hey again,
On 2016-10-13 12:01:42 (+0200), Peter Nabbefeld wrote:
I've got problems with bluetooth (service does not start), which seem to be
caused by systemd problems, as several services are "dead".
you might want to check the log
Hey again,
On 2016-10-13 12:01:42 (+0200), Peter Nabbefeld wrote:
> > > I've got problems with bluetooth (service does not start), which seem to
> > > be
> > > caused by systemd problems, as several services are "dead".
> > you might want to check the log output of those services then.
What does
Hi David,
Am 13.10.2016 um 11:35 schrieb David Runge:
Hi Peter,
On 2016-10-13 08:37:13 (+0200), Peter Nabbefeld wrote:
Hello,
I've got problems with bluetooth (service does not start), which seem to be
caused by systemd problems, as several services are "dead".
you might want to check the
Hi Peter,
On 2016-10-13 08:37:13 (+0200), Peter Nabbefeld wrote:
>
> Hello,
>
> I've got problems with bluetooth (service does not start), which seem to be
> caused by systemd problems, as several services are "dead".
you might want to check the log output of those services then.
>
> Output
Hello,
I've got problems with bluetooth (service does not start), which seem to
be caused by systemd problems, as several services are "dead".
Output of info --test´ is at https://dpaste.de/LC2h
Kind regards
Peter
Most systemd user accounts are present in the /etc/passwd file provided
by the filesystem package. This is not the case for only two of them,
namely systemd-journal-upload and systemd-journal-remote, which are set
up by systemd-sysusers, executed when the systemd package is installed.
Is there a
On 2 February 2016 at 21:28, Daniel Milewski wrote:
> Most systemd user accounts are present in the /etc/passwd file provided
> by the filesystem package. This is not the case for only two of them,
> namely systemd-journal-upload and systemd-journal-remote, which are set
>
Op 2 feb. 2016 22:24 schreef "Damjan Georgievski" :
> it's better to let `systemd-sysusers` create all users, /etc/passwd
> should probably not be included in any package
> since it changes in the lifetime of the distro and updates are hard to
merge.
Agreed. And while we're at
hello,
thought i'd ask here first, in case it's a distro problem.
was wondering if we can use systemd to start and stop a daemon for
testing purposes during development. meaning, i would like to not have
to "install" my daemon nor its systemd service file, and instead run
all from the working
On Sat, Jan 30, 2016 at 2:22 PM, Andre "Osku" Schmidt
wrote:
> On Sat, Jan 30, 2016 at 1:41 PM, Damjan Georgievski wrote:
>> On 30 January 2016 at 12:48, Andre "Osku" Schmidt
>> wrote:
>>> hello,
>>>
>>> thought i'd
On 30 January 2016 at 12:48, Andre "Osku" Schmidt
wrote:
> hello,
>
> thought i'd ask here first, in case it's a distro problem.
>
> was wondering if we can use systemd to start and stop a daemon for
> testing purposes during development. meaning, i would like to not
On Sat, Jan 30, 2016 at 1:41 PM, Damjan Georgievski wrote:
> On 30 January 2016 at 12:48, Andre "Osku" Schmidt
> wrote:
>> hello,
>>
>> thought i'd ask here first, in case it's a distro problem.
>>
>> was wondering if we can use systemd to start
> Say you start out on wifi, and open an ssh connection. Then you plug in
> ethernet. The ssh session will remain on the wifi route until it is
> closed. There's no way* to make an existing connection "jump ship" from
> one route to another. If you were to disable the wifi connection as soon
> as
On Thu, Nov 12, 2015 at 07:52:20PM +0100, Bennett Piater wrote:
>
> I mostly just use LAN when I need to download a lot of stuff at home,
> because WIFI is much slower even at 54 Mb/s, especially since my home
> network is 1 Gbps. So I could just turn WIFI off in those cases, that
> would be an
On Thu, Nov 12, 2015 at 12:30:36PM +0100, Bennett Piater wrote:
> > Say you start out on wifi, and open an ssh connection. Then you plug in
> > ethernet. The ssh session will remain on the wifi route until it is
> > closed. There's no way* to make an existing connection "jump ship" from
> > one
> Well, it depends on whether wlan0 and eth0 are on different networks. If
> they are, then the answer is yes, and you are screwed.
>
> If both interfaces get the same ip, then you can maintain persistent
> connection. For example, let's assume that you constantly switch between
> different
Hello!
I installed Arch on my new Thinkpad T450s over the weekend.
Everything works well, but I have a question:
I use systemd-networkd to manage my network interfaces and netctl for
the connections. I set everything up according to (this)[0] and
(this)[1] to get automatic activation of wifi via
On Wed, Nov 11, 2015 at 09:35:05 +, Ben Oliver wrote:
> On 11 November 2015 at 09:18, Ludwig Zins wrote:
>
> > On 11/11/15 09:47, Bennett Piater wrote:
> > > Hello!
> > > I installed Arch on my new Thinkpad T450s over the weekend.
> > > Everything works well, but I have a
> I don't use netctl, but you can usually see what default route it uses with
>
> ip route
Thanks for that, I didn't know that command.
The LAN is shown above WIFI, which (I assume) means that it takes
precedence.
>
> I have made the experience that newly configured interfaces "steal"
On 11/11/15 09:47, Bennett Piater wrote:
> Hello!
> I installed Arch on my new Thinkpad T450s over the weekend.
> Everything works well, but I have a question:
>
> I use systemd-networkd to manage my network interfaces and netctl for
> the connections. I set everything up according to (this)[0]
Expanding on the ip route command, you can you see what interface is used
to reach the Internet by looking at the default route. The entry that has
the destination as 0.0.0.0 and the subnet mask as 0.0.0.0 is the default
route. If your LAN is shown above your wifi interface I'm going to assume
ip route get 8.8.8.8
ip route get 7.7.7.7
will show the routes for those ip addresses. you can check several to
see where they go (in case the 2 default routes have the same metric)
On 11 November 2015 at 14:38, Andrew Von Stein <16vo...@gmail.com> wrote:
> Expanding on the ip route command, you
On Wed, Nov 11, 2015 at 16:06:18 +0100, Bennett Piater wrote:
> They have different metrics as per the example from the wiki.
>
> However, no wiki article or manpage that I encountered explained what
> exactly the metric does. Could you explain that to me?
>
> Cheers,
> Bennett
>
> > If there
On 11 November 2015 at 09:18, Ludwig Zins wrote:
> On 11/11/15 09:47, Bennett Piater wrote:
> > Hello!
> > I installed Arch on my new Thinkpad T450s over the weekend.
> > Everything works well, but I have a question:
> >
> > I use systemd-networkd to manage my network interfaces
On Wed, Nov 11, 2015 at 09:47:25AM +0100, Bennett Piater wrote:
> Hello!
> I installed Arch on my new Thinkpad T450s over the weekend.
> Everything works well, but I have a question:
>
> I use systemd-networkd to manage my network interfaces and netctl for
> the connections. I set everything up
Hi,
Arch runs without any issues, so I randomly discovered this:
[rocketmouse@archlinux ~]$ grep EE /var/log/Xorg.0.log
[26.702] Current Operating System: Linux archlinux
3.10.61-rt65-1-rt-lts x86_64
[27.745] (EE) systemd-logind: failed to get session:
Wed, 23 Sep 2015 09:09:06 +0200
Ralf Mardorf :
> What could be the reason?
It's Xorg, run from the login manager, of course it doesn't belong to any
session. Same here with sddm.
--byte
pgphG4mvcGxv_.pgp
Description: Digitale Signatur von OpenPGP
in 226, systemd-networkd now supports predictable interface names
for virtio devices.[1]
For people running Arch in KVM with virtio-net (as I do), that means
the network interface name will change from eth0 to - in my case -
ens5.
That, for me also meant no ip address after reboot. Make sure to
or maybe net.ifnames=0 on the kernel command line to completely disable
network interface renaming.
W dniu 09.09.2015 o 17:34, Damjan Georgievski pisze:
in 226, systemd-networkd now supports predictable interface names
for virtio devices.[1]
For people running Arch in KVM with virtio-net (as
I just upgraded to systemd 215, and connaction to my container is broken.
# machinectl login MyMachine
Connected to machine MyMachine. Press ^] three times within 1s to exit session.
Then it hangs here indefinitely. No login shell.
--
google.com/+arnaudgabourygabx
I'm trying to set up a server network configuration in Arch using
systemd-networkd tools. The networkd configuration files that I have
are not doing what I think they should be doing.
My setup is this: 4 physical ports - bond0 - vlans 2-8 - a few on
bridges, a few on their own.
First I'll post
I interpreted this thread as a bug report with 'The Arch Way' page on
the wiki so it hasn't been for naught. That page has been rewritten to
better reflect what has always been the development philosophy instead
of being a vague advertisement for the distribution with questionable
claims.
2015-07-02 18:46 GMT-03:00 Daniel Micay danielmi...@gmail.com:
Now, it would be technically possible to replace *systemd* in base with a
generic init-system which could be provided by both *systemd* and
*openrc*,
but that would make things much more complicated and *much* more effort
to
1 - 100 of 717 matches
Mail list logo