1 |
On Wed, Sep 04, 2013 at 09:16:55AM -0500, Canek Peláez Valdés wrote: |
2 |
|
3 |
> > Well, it’s an experiment, but I’m still quite hesitant to switch. It |
4 |
> > really shuts down fast (1 to 2 seconds or so), but I don’t see much |
5 |
> > improvement in booting time (still around 40 seconds until KDM is |
6 |
> > finished). I like the small stuff around it though, for instance |
7 |
> > timedatectl is neat and that there is no consolekit thread spam in htop. |
8 |
> |
9 |
> Even considering that you need to input the LUKS password, 40 seconds |
10 |
> is too much. You can use systemd-analyze and systemd-analyze blame |
11 |
> after a fresh boot to see what is taking most of the boot time. |
12 |
|
13 |
I stopped the timer during password entry. systemd-analyze said (IIRC, netbook |
14 |
is off ATM) a little more than 20 seconds altogether. But as I mentioned it’s |
15 |
a slow machine. From the kind of noises it made during boot, I guess that the |
16 |
HDD is the bottleneck. The time from the initial blank X screen to KDM alone |
17 |
is more than 10 seconds. Perhaps there is still stuff starting in the BG. |
18 |
|
19 |
> > I also see now why some people rant about it, e.g. that it has an own |
20 |
> > logging daemon (“one big block of everything”) which uses a binary data |
21 |
> > format. OTOH, logging becomes very handy with it in that you can see all |
22 |
> > messages associated with a particular service. Systemdadm is a start, |
23 |
> > but impractical on a netbook screen. |
24 |
> |
25 |
> Don't forget journalctl -b -p err and journalctl -b -p warning. Hugh |
26 |
> time savings. |
27 |
|
28 |
I’m just so used to tail -f /var/log/messages, and it’s a hard fact of reality |
29 |
that switching to something new/else/different always takes personal effort. |
30 |
|
31 |
> > I was hoping I could have openrc and systemd in parallel on the system |
32 |
> > (so I don’t have to maintain two systems, especially on a slow netbook), |
33 |
> > but b/c I removed consolekit altogether, a lot of stuff doesn’t work |
34 |
> > anymore if I try booting with openrc. |
35 |
> > |
36 |
> > Perhaps someone can give me a hint about the following: |
37 |
> > - I’m missing openrc’s feature of using the menu key to switch between |
38 |
> > the last two TTYs, that’s very useful. |
39 |
> |
40 |
> I didn't realized it was gone. |
41 |
|
42 |
Well not in openrc, obviously. But it isn’t there in systemd. |
43 |
|
44 |
> However, I don't think is a feature of OpenRC, it's just that OpenRC calls |
45 |
> agetty differently from systemd, I suppose. |
46 |
|
47 |
I didn’t know where to look for that option specifically and thought it was |
48 |
openrc (because I can’t remember any other distro having this, like many other |
49 |
details such as a colourful promt by default). |
50 |
|
51 |
> > - No login prompt on TTY1. |
52 |
> |
53 |
> Sure it is. Perhaps is just garbled? Try to log in and do a reset. |
54 |
|
55 |
I have boot output on TTY1 and logins on TTY2-6., but not on one I tried |
56 |
various keys and conbinations such as Ctrl+C. |
57 |
|
58 |
> > - A resource link on how to set up networking without network manager. I |
59 |
> > always did it the conf.d/net way. |
60 |
> |
61 |
> You can set up the network without networkmanager just fine. |
62 |
|
63 |
I was obviously too lazy yesterday to research it. I poked blindly into the |
64 |
dark by trying the pre-existing wpa_supplicant and dhcpcd services without any |
65 |
custom configuration (with wpa_supplicant.conf being the only real requirement |
66 |
for my network setup), but wpa_supplicant always failed to authenticate, so I |
67 |
gave up for that night. |
68 |
|
69 |
-- |
70 |
Gruß | Greetings | Qapla’ |
71 |
Please do not share anything from, with or about me with any Facebook service. |
72 |
|
73 |
The advantage of being smart is that one can pretend to be stupid. |
74 |
The opposite is far more difficult. |