On 2016-07-27 19:54, Michał Zegan wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does not care about it. Neither systemd nor udev rules set the
> system time using the hardware clock.
Strictly speaking, systemd does at bootup what hwclock used to
coding style as close as possible to the original.
Michal Soltys (1):
vconsole-setup: updates & fixes
src/vconsole/vconsole-setup.c | 260 --
1 file changed, 125 insertions(+), 135 deletions(-)
--
2
This patch updates vconsole helper to:
- correctly handle fonts of heights different than 16
- avoid issues with setfont's -m option
And adds:
- new vc_max tunable, so user can set how many consoles should be adjusted
- iutf8 flag is now set/reset as necessary
Short revised code flow overview:
On 2016-06-22 13:32, Andrei Borzenkov wrote:
Well, depends =) It was easy to do it cleanly, but rarely anyone cared. It's
How is different to what we have now? :)
I guess =)
Well, getty's are spawned dynamically on demand and there is no direct
dependency between various targets and runn
On 2016-06-22 05:39, Andrei Borzenkov wrote:
21.06.2016 23:23, Michal Soltys пишет:
TBH, switch between run-time levels never really worked in the past,
before systemd, so at least there is no regression :)
Well, depends =) It was easy to do it cleanly, but rarely anyone cared.
It's
Hi,
This was tested with recent stock arch distro. I'm not sure if it's
intended to be able to isolare rescue.target from multi-user, but I
noticed two issues:
1) getty service and IgnoreOnIsolate option
This beautifully conflicts for console access with sulogin on whichever
console systemc
1) font_copy_to_all_vcs(): copying fonts of height different from
"standard" 16 produces garbage on all other terminals (with exception of
builtin basic vga).
The workaround is to call setfont directly providing another terminal
with -C option (or log in and type the command blindly), e.g.
s
On 2016-04-08 18:12, Andrei Borzenkov wrote:
08.04.2016 18:20, Michael Biebl пишет:
2016-04-08 16:25 GMT+02:00 Michal Soltys :
On your root partition keep /var/run symlink to /run - so regardless if /var
is or isn't mounted, the path will be correct. Wouldn't that help ? (unles
On 2016-04-06 11:15, Łukasz Stelmach wrote:
Hi,
I've hit a problem caused by a mix of: automounting + glibc + udev + my
partition layout. Apparently it is impossible to make /var automountable
because udev (which needs to enumerate devices befor mounting them) is
trying to connect to /var/run/ns
On 11-11-08 17:46, Michal Soltys wrote:
Then even existing intiramfs image could (probably) be mdmon-agnostic.
Actually:
chroot /run/initramfs mdmon --takeover --all
worked just fine (after preparing new root - so after all mount --binds,
and before pivot_root(8)).
So in context of
On 11-11-08 01:11, Michal Soltys wrote:
I've peeked into systemd, and from what I can see, it /only/ jumps back
to initramfs (prepare_new_root() and pivot_to_new_root()) if shutdown
"binary" is present on initramfs. And whenever mdmon is still running or
not, is not in any way
On 11-11-02 14:32, Lennart Poettering wrote:
What we do right now is this:
kill_all_processes();
do {
umount_all_file_systems_we_can();
read_only_mount_all_remaining_file_systems();
} while (we_had_some_success_with_that());
jump_into_initrd();
As long as mdmon references a file fro
12 matches
Mail list logo
