You are not logged in.
Why does systemD have to be so ugly when booting? The SysVinit which is beeing used by Archlinux today have fancy colors and done text. It looks clean and neat.
Is it possible to get it to look better?
Last edited by thoho180192 (2012-07-14 22:16:14)
Offline
I guess it depends on your taste. But systemd boot looks fine for me. Colors indicating OK/FAILED/... and messages about what is / has been started.
Without more information it is not easy to tell if you have encountered a bug or not....
Offline
I havent switched yet. I've just been watching a few youtube movies with Archlinux and sysD and it dosnt look as good as the current init system.
I think Im going to install and see for myself though.
Thanks for reply.
Offline
By default, the systemd boot doesn't say anything. I see the bootloader text, and then one line of output from fsck preening the root filesystem, and then the screen clears and the getty login prompt appears. It's possible to get detailed status output from systemd during the boot (see systemd's homepage for a Fedora-based example of this), but it's not enabled by default.
Offline
I've installed systemD now and it actually both look and work great. I have one problem thou. I cant enable networkmanager and the gdm service.
It gives me a error message reading "Failed to issue method call: No such file or directory"
Wiki says it should work so I dont know.
Do I need the archlinux units package? I thought that were to get old configs to work.
Offline
I cant enable networkmanager and the gdm service.
It gives me a error message reading "Failed to issue method call: No such file or directory".
you need to add ".service" - also networkmanager.service doesnt exist, its called NetworkManager.service
so you do:
systemctl enable NetworkManager.service
systemctl enable gdm.service
Last edited by Rasi (2012-07-15 08:23:22)
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
gdm.service is part of systemd-arch-units
Offline
Thanks
It was an easy switch. Im running systemD without sysvinit and its much faster then it used to be
Thanks for the help
Offline
I havent switched yet. I've just been watching a few youtube movies with Archlinux and sysD and it dosnt look as good as the current init system.
I think Im going to install and see for myself though.
Thanks for reply.
So... this is solved, or what? Was there ever any real problem?
I'm being rhetorical. Half-baked film criticism is the sort of stuff blogs are made for. Really, how long do you need to look at boot info before a login prompt? If it's really a problem for you, use a splash screen.
Offline
Good point
I've tried some splash screens in the past. Never got satisfied. Nothing compares to the beautiful Arch SysV boot, but ofcourse this systemD thing is extremly fast compared to the old one. I think I can manage.
Offline
Why does systemD have to be so ugly when booting?
Looks like Debian. I wouldn't say ugly. Just different. The most beautiful booting IMO has Gentoo. Even better than Arch.
Offline
heh, i have this first-nerd-problem, too.
surely the only way is to patch systemd to use arch-blue?
Offline
Think so
Offline
I think we all know what the OP meant.
Offline
I switched over to systemd and I have to say, I am amazed how fast it boots up. I really don't mind that it isn't pretty because it doesn't stay on the loading screen for very long. Like three seconds for me lol.
Offline
wow, i’ve located how it’s done:
in the file systemd/src/core/job.c is a function job_print_status_message(Unit *u, JobType t, JobResult result)
it contains this:
switch (result) {
case JOB_DONE:
if (u->condition_result)
unit_status_printf(u, ANSI_HIGHLIGHT_GREEN_ON " OK " ANSI_HIGHLIGHT_OFF, format, unit_description(u));
break;
case JOB_FAILED:
unit_status_printf(u, ANSI_HIGHLIGHT_RED_ON "FAILED" ANSI_HIGHLIGHT_OFF, format, unit_description(u));
unit_status_printf(u, "", "See 'systemctl status %s' for details.", u->id);
break;
case JOB_DEPENDENCY:
unit_status_printf(u, ANSI_HIGHLIGHT_YELLOW_ON "DEPEND" ANSI_HIGHLIGHT_OFF, format, unit_description(u));
break;
case JOB_TIMEOUT:
unit_status_printf(u, ANSI_HIGHLIGHT_RED_ON " TIME " ANSI_HIGHLIGHT_OFF, format, unit_description(u));
break;
default:
;
}
all hard-coded! man, that’s not going to change
Offline
all hard-coded! man, that’s not going to change
Why not? Just use the constant ANSI_HIGHLIGHT_BLUE_ON if it exists, or change the definition of ANSI_HIGHLIGHT_GREEN_ON to actually be blue.
Hell, it could hardly be easier to change.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Anyone got that code working?
Offline
I had some warning messages pop regarding AMDs cool and quiet which is a known bug in the kernel. So I just installed Plymouth so I didn't have to look at it.
Offline
I wouldn't call it ugly just because its not blue, I think it looks fine.
Offline
Why not? Just use the constant ANSI_HIGHLIGHT_BLUE_ON if it exists, or change the definition of ANSI_HIGHLIGHT_GREEN_ON to actually be blue.
Hell, it could hardly be easier to change.
I think flying sheep would simply rather not have to recompile systemd just to change one simple thing that (IMHO) really should be externally configurable.
As for me, I don't even see them; I have 'quiet' in my kernel cmd line.
EDIT: Not to mention, you'd have to re-apply this patch every time a systemd update rolled around.
Last edited by MrCode (2012-09-20 21:39:06)
Offline
It should be configurable for accessibility reasons. Red/green colour blindness is the most common form and people shouldn't have to recompile systemd in order to easily distinguish successes from failures.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
@cfr: Good point!
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
It should be configurable for accessibility reasons. Red/green colour blindness is the most common form and people shouldn't have to recompile systemd in order to easily distinguish successes from failures.
I'm red-green colorblin-- wait a second, it's green!? [/joke]
Really, though, this should be configurable. I'll look at the code and see if I could write a patch. (I'm not that great of a coder, but this shouldn't be too hard.)
Offline