... I finally got around to writing up some notes on the tips I presented for accessing the systemd journal at that talk last year <https://github.com/WLUG/meetings/tree/master/2016/2016-06-27>.
Thanks wolf On 28/07/17 13:00, Lawrence D'Oliveiro wrote:
... I finally got around to writing up some notes on the tips I presented for accessing the systemd journal at that talk last year <https://github.com/WLUG/meetings/tree/master/2016/2016-06-27>. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: https://list.waikato.ac.nz/mailman/listinfo/wlug
It took you a year to write that up? I hope all the 'bugs' that opened all systemd users up to gross security leaks and remote excecution get fixes in a little more timely manner. ;) On Fri, 2017-07-28 at 13:00 +1200, Lawrence D'Oliveiro wrote:
... I finally got around to writing up some notes on the tips I presented for accessing the systemd journal at that talk last year <https://github.com/WLUG/meetings/tree/master/2016/2016-06-27>. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: https://list.waikato.ac.nz/mailman/listinfo/wlug
Thanks Lawrence, that's handy. For some reason I always forget the journalctl command. Another notable mention: `systemd-analyze blame` is a really good tool for boot-speed profiling: $ systemd-analyze blame 5.952s NetworkManager-wait-online.service 1.531s keyboard-setup.service 1.489s apt-daily.service 736ms dev-mapper-2017\x2d\x2dvg\x2droot.device 693ms apt-daily-upgrade.service 525ms systemd-rfkill.service 274ms networking.service 263ms wg-quick(a)wg0.service 237ms NetworkManager.service 214ms ModemManager.service 169ms bluetooth.service 157ms accounts-daemon.service [...] E -------------------------------------------- Q: Why is this email five sentences or less? A: http://five.sentenc.es On Fri, 28 Jul 2017, at 13:00, Lawrence D'Oliveiro wrote:
... I finally got around to writing up some notes on the tips I presented for accessing the systemd journal at that talk last year <https://github.com/WLUG/meetings/tree/master/2016/2016-06-27>. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: https://list.waikato.ac.nz/mailman/listinfo/wlug
On Sun, Jul 30, 2017 at 01:11:35PM +1200, Eric Light wrote:
Thanks Lawrence, that's handy. For some reason I always forget the journalctl command.
Another notable mention: `systemd-analyze blame` is a really good tool for boot-speed profiling:
$ systemd-analyze blame 5.952s NetworkManager-wait-online.service
I would guess that "apt-get purge network-manager" should fix that problem nicely. It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-) But if slow boot speed is really annoying you, forget systemd and install a solid state drive. That will improve boot speeds far more than systemd ever did, of which I am lead to believe was originally the primary reason given for developing systemd! Cheers Michael.
1.531s keyboard-setup.service 1.489s apt-daily.service 736ms dev-mapper-2017\x2d\x2dvg\x2droot.device 693ms apt-daily-upgrade.service 525ms systemd-rfkill.service 274ms networking.service 263ms wg-quick(a)wg0.service 237ms NetworkManager.service 214ms ModemManager.service 169ms bluetooth.service 157ms accounts-daemon.service [...]
E
On Sun, 30 Jul 2017, at 13:37, Michael Cree wrote:
I would guess that "apt-get purge network-manager" should fix that problem nicely. It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-)
Haha -- "Oh no, now I have no gui, and no network connection to Google a resolution!" ;) I use Cinnamon though; really happy with it's speed and usability. Really the only reason I use NetworkManager is for the wifi - all my other interfaces are manual, and I just haven't gotten around to learning how to drive wifi any other way.
But if slow boot speed is really annoying you, forget systemd and install a solid state drive.
Oh hey absolutely; I've been SSD-only for years now, and I'm never going back!
I am lead to believe was originally the primary reason given for developing systemd!
... really? Was the original goal simply better speed? I had no idea. E -------------------------------------------- Q: Why is this email five sentences or less? A: http://five.sentenc.es
On Mon, Jul 31, 2017 at 12:27 AM, Eric Light <eric(a)ericlight.com> wrote:
On Sun, 30 Jul 2017, at 13:37, Michael Cree wrote:
I would guess that "apt-get purge network-manager" should fix that problem nicely. It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-)
Haha -- "Oh no, now I have no gui, and no network connection to Google a resolution!" ;)
I use Cinnamon though; really happy with it's speed and usability.
Really the only reason I use NetworkManager is for the wifi - all my other interfaces are manual, and I just haven't gotten around to learning how to drive wifi any other way.
RaspberryPi site has a good guide to config wireless network with commands: https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cl... cheers, william
On Mon, Jul 31, 2017 at 12:27:18AM +1200, Eric Light wrote:
On Sun, 30 Jul 2017, at 13:37, Michael Cree wrote:
I would guess that "apt-get purge network-manager" should fix that problem nicely. It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-)
Haha -- "Oh no, now I have no gui, and no network connection to Google a resolution!" ;)
Why do you assume removing network-manager means no GUI? There are GUIs (at least in Debian) that only have a recommends on network-manager and will work fine without it. No network connection? Well, I had assumed one would know to wire up the network in /etc/network/interfaces, but maybe I should have stated that a bit more clearly ;-) But watch out, Debian Stretch names network interfaces with the most ridiculous scheme so if you specify eth0 you won't have a network. Fortunately, a fix has been proposed, even may be applied now, in Debian Sid that enables one to configure the first network interface enumerated by the kernel, i.e., to configure the device as if it was eth0 without knowing what ridiculous name the system has decided to invent for it.
I use Cinnamon though; really happy with it's speed and usability.
When I tried it a year or so ago it was far too slow on an older machine and did not usefully support 2160p display. Maybe that has change in the meantime?
I am lead to believe was originally the primary reason given for developing systemd!
... really? Was the original goal simply better speed? I had no idea.
Certainly boot speed was something the systemd developers wanted to address and highlighted as one of their main goals. I just find it ironic that a couple or so years after systemd was adopted by most distributions that a hardware advance came along that delivered a boot speed that systemd could not get anywhere near when booting on spinning disk. Cheers Michael.
On Sun, 6 Aug 2017, at 21:41, Michael Cree wrote:
It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-) Haha -- "Oh no, now I have no gui, and no network connection to Google a resolution!" ;) Why do you assume removing network-manager means no GUI?
It was just a silly response to your comment about removing Gnome, no seriousness involved. :) Gotta admit though, the funny Debian interface naming took me for a ride the first time I encountered it. <s>But, en6s12 has grown on me now.</s>
When I tried [Cinnamon] it a year or so ago it was far too slow on an older machine and did not usefully support 2160p display. Maybe that has change in the meantime?
Umm it's possible, but I wouldn't put money on it. I'm running it on a Dell Latitude E6410 with no trouble, but I haven't really challenged it.
Certainly boot speed was something the systemd developers wanted to address and highlighted as one of their main goals. I just find it ironic that a couple or so years after systemd was adopted by most distributions that a hardware advance came along that delivered a boot speed that systemd could not get anywhere near when booting on spinning disk.
Haha maybe that's why Lennart is so salty. That's cool, thanks for the history tidbit. E -------------------------------------------- Q: Why is this email five sentences or less? A: http://five.sentenc.es
On Mon, Jul 31, 2017 at 12:27:18AM +1200, Eric Light wrote:
On Sun, 30 Jul 2017, at 13:37, Michael Cree wrote:
I would guess that "apt-get purge network-manager" should fix that problem nicely. It might want to also remove gnome if you had already accidently (or unwisely) installed that, and, of course, you should absolutely answer yes to doing that. Then you will get a much improved system ;-)
Haha -- "Oh no, now I have no gui, and no network connection to Google a resolution!" ;)
Why do you assume removing network-manager means no GUI? There are GUIs (at least in Debian) that only have a recommends on network-manager and will work fine without it.
No network connection? Well, I had assumed one would know to wire up the network in /etc/network/interfaces, but maybe I should have stated that a bit more clearly ;-)
But watch out, Debian Stretch names network interfaces with the most ridiculous scheme so if you specify eth0 you won't have a network. Fortunately, a fix has been proposed, even may be applied now, in Debian Sid that enables one to configure the first network interface enumerated by the kernel, i.e., to configure the device as if it was eth0 without knowing what ridiculous name the system has decided to invent for it.
I use Cinnamon though; really happy with it's speed and usability.
When I tried it a year or so ago it was far too slow on an older machine and did not usefully support 2160p display. Maybe that has change in the meantime?
I am lead to believe was originally the primary reason given for developing systemd!
... really? Was the original goal simply better speed? I had no idea.
Certainly boot speed was something the systemd developers wanted to address and highlighted as one of their main goals. I just find it ironic that a couple or so years after systemd was adopted by most distributions that a hardware advance came along that delivered a boot speed that systemd could not get anywhere near when booting on spinning disk.
Cheers Michael. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: https://list.waikato.ac.nz/mailman/listinfo/wlug
On Sun, 30 Jul 2017 13:37:31 +1200, Michael Cree wrote:
But if slow boot speed is really annoying you, forget systemd and install a solid state drive. That will improve boot speeds far more than systemd ever did, of which I am lead to believe was originally the primary reason given for developing systemd!
I would say the speedup comes from doing both. Since SSDs don’t require head seeks, the contention between running multiple startup tasks at once under systemd is less.
participants (6)
-
Eric Light -
gb -
Lawrence D'Oliveiro -
Michael Cree -
William Mckee -
Wolf