Page 7 of 7
Re: MX 19.2 KDE
Posted: Sat Aug 22, 2020 8:49 pm
by dolphin_oracle
well if Uncle Mark is happy, then so am I
Re: MX 19.2 KDE
Posted: Sat Aug 22, 2020 9:29 pm
by uncle mark
dolphin_oracle wrote: Sat Aug 22, 2020 8:49 pm
well if Uncle Mark is happy, then so am I
Oh, I'm sure I'll be able to find something to whine about.
While I've got your attention, care to refresh my memory on how to write a boot stanza in menu.lst in grub-legacy for a chainload from a standalone boot partition?
This is what I have currently for the Mint KDE I'm running now on sdc:
Code: Select all
title mint18kde SSD at sdc1
root (hd2,0)
kernel /boot/grub/i386-pc/core.img
If I install the new drive as sdd, then I'm thinking I should write it as:
Code: Select all
title MX-KDE SSD at sdd1
root (hd3,0)
kernel /boot/grub/i386-pc/core.img
That third line has caused me problems in the past.
When installing, I should tell grub the boot drive is sdd and to install grub to root, correct?
It been a looong time since I was installing distros regularly for testing or just for fun. Old age has done a number on my enthusiasm and attention span.
Re: MX 19.2 KDE
Posted: Mon Aug 24, 2020 6:17 pm
by tony37
Remarkable tidbit: if I want to get rid of the 'Hibernate' button in the menu (because hibernation never worked for me anyway), I have to do exactly the same as in a systemd distro: adding the following lines to /etc/systemd/sleep.conf :
Code: Select all
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
Logout + login and the button is gone. And I'm definitely using Sysvinit here.
Talking about systemd, my impression is that it is a full 4 seconds faster in booting than sysvinit over here. Maybe KDE is better optimised to work with systemd?
I found one annoyance using systemd (but already I can't reproduce it anymore): when Konsole is open when I do a shutdown I get a message saying: Konsole closed unexpectedly, to file a bug report ... etc.