-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/04/2013 11:12 AM, Frank Steinmetzger wrote: > On Wed, Sep 04, 2013 at 09:16:55AM -0500, Canek Peláez Valdés wrote: > >>> Well, it’s an experiment, but I’m still quite hesitant to switch. It really >>> shuts down fast >>> (1 to 2 seconds or so), but I don’t see much improvement in booting time >>> (still around 40 >>> seconds until KDM is finished). I like the small stuff around it though, >>> for instance >>> timedatectl is neat and that there is no consolekit thread spam in htop. >> >> Even considering that you need to input the LUKS password, 40 seconds is too >> much. You can >> use systemd-analyze and systemd-analyze blame after a fresh boot to see what >> is taking most >> of the boot time. > > I stopped the timer during password entry. systemd-analyze said (IIRC, > netbook is off ATM) a > little more than 20 seconds altogether. But as I mentioned it’s a slow > machine. From the kind > of noises it made during boot, I guess that the HDD is the bottleneck. The > time from the > initial blank X screen to KDM alone is more than 10 seconds. Perhaps there is > still stuff > starting in the BG. > >>> I also see now why some people rant about it, e.g. that it has an own >>> logging daemon (“one >>> big block of everything”) which uses a binary data format. OTOH, logging >>> becomes very handy >>> with it in that you can see all messages associated with a particular >>> service. Systemdadm >>> is a start, but impractical on a netbook screen. >> >> Don't forget journalctl -b -p err and journalctl -b -p warning. Hugh time >> savings. > > I’m just so used to tail -f /var/log/messages, and it’s a hard fact of > reality that switching > to something new/else/different always takes personal effort. > >>> I was hoping I could have openrc and systemd in parallel on the system (so >>> I don’t have to >>> maintain two systems, especially on a slow netbook), but b/c I removed >>> consolekit >>> altogether, a lot of stuff doesn’t work anymore if I try booting with >>> openrc. >>> >>> Perhaps someone can give me a hint about the following: - I’m missing >>> openrc’s feature of >>> using the menu key to switch between the last two TTYs, that’s very useful. >> >> I didn't realized it was gone. > > Well not in openrc, obviously. But it isn’t there in systemd. > >> However, I don't think is a feature of OpenRC, it's just that OpenRC calls >> agetty differently >> from systemd, I suppose. > > I didn’t know where to look for that option specifically and thought it was > openrc (because I > can’t remember any other distro having this, like many other details such as > a colourful promt > by default). > >>> - No login prompt on TTY1. >> >> Sure it is. Perhaps is just garbled? Try to log in and do a reset. > > I have boot output on TTY1 and logins on TTY2-6., but not on one I tried > various keys and > conbinations such as Ctrl+C. > >>> - A resource link on how to set up networking without network manager. I >>> always did it the >>> conf.d/net way. >> >> You can set up the network without networkmanager just fine. > > I was obviously too lazy yesterday to research it. I poked blindly into the > dark by trying the > pre-existing wpa_supplicant and dhcpcd services without any custom > configuration (with > wpa_supplicant.conf being the only real requirement for my network setup), > but wpa_supplicant > always failed to authenticate, so I gave up for that night. >
The various systemd units involved assume that you have KDM set up like Fedora does, with the first graphical terminal (:0) on tty1, so kdm.service actually *conflicts* with getty@tty1.service. If you actually want to set up kdm to act in this manner, edit the file /usr/share/config/kdm/kdmrc and change the following options in the [General] section: ServerVTs=1,-7 ConsoleTTYs=tty2,tty3,tty4,tty5,tty6 If you don't want kdm.service to conflict with getty@tty1.service, copy the file /usr/lib/systemd/system/kdm.service to /etc/systemd/system/kdm.service, and remove the line: Conflicts=getty@tty1.service - -- Jonathan Callen -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJSKW2FAAoJELHSF2kinlg4f/YP+wZMh4CDv60ca3v8FA6UySnE UQ/HEcQFa5MIhwwF2PNzG1+0w5wolUG98iuS08YHuX6+BWrHmX8v3OqkZhZYZxRD am80cYBiJUbtNVBqIZJIO54HJs4q8aS5OR8tN5UhHk7tBDVup3se4yEL2HU9OqYT wnOAUQwCicVnVJ7jUhlZ/81BFcXzJv7A5fVy12r6FXRIItTabFQbWki1tMd7MBCU 0nVIu87QQPc5fGmoODFWOc7bedkeCYE+xotY4cfGzkzTdEEd1iqer0yMtp/00E3f Ip+nmjjonCEoOdyxVPYHVPAJ7Oamod+v5Hv4n8Km3c9DU2oMWfvG2rUP4FqTIPNJ qIlJXFEXdZV0VvMG5ZgI1N+17q5v0N52mlrH+hYX4LS91RY9DbOuaZtfQsb9F0Ud OxC5KSbqzFhGipQymOW2kOlERLXfaGOvfV6LS4rleWS75o9vfQJuVzLv0iHdqt8Z VWN9fhtyUkw9JGWzDgbHv3USW0HwOXvhpCV0LvPm5fT2xWKl+Ep9/0pH2dpkpT/e faLAksYSg0Aky3IHjTnNpWFCKF4dxWCVbFHe9OmDKnLKq5CfNbu/JbMc9ZrXjlEF 0N1uAk6KYr5HhUub9VL/2o/sO91eSst9b0TDozUif7AMJbnN2fRFoaTXs2Gqe+Nl hl5of0qIw2533RHMVwtr =hY5I -----END PGP SIGNATURE-----
