Otherwise, edit /etc/default/grub like the image in the previous post, insert it between the quotes of GRUB_CMDLINE_LINUX_DEFAULT
Code: Select all
GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp quiet splash"
Code: Select all
sudo update-grub
Code: Select all
GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp quiet splash"
Code: Select all
sudo update-grub
Code: Select all
grub2-mkconfig -o /boot/grub2/grub.cfg
Code: Select all
/etc/default/grub
Code: Select all
grub2-mkconfig -o /boot/grub2/grub.cfg
Code: Select all
passwd -u root
Code: Select all
chsh -s /bin/bash root
Really? What does this return:droppointalpha wrote: I have trialed the fix above using sudo and successfully wrote the the command into the grub file via nano. It seems to function as the grub.cfg edit did. No changes.
Code: Select all
sudo cat /proc/cmdline
Actually you've reinforced the analogy, but that's a discussion we might have on another day.droppointalpha wrote:I understand your analogy but it seems more than a bit off in its comparison.
I'll check. But to re-iterate, since I think my statement may not have been wholly clear, the cmdline edit on /etc/grub/ works exactly the same as the grub.cfg edit (which is my expectation) and there it no difference in system performance. The touchpad settings tab, for instance, is still all greyed out but I would expect nothing different, as the edit of one file was simply the same edit made permanent for the other file.kode-niner wrote: Really? What does this return:Code: Select all
sudo cat /proc/cmdline
Having a small fleet of vehicles, I'll ahead and say no. Root access is like having a computer hooked up to the ECM and making live changes to F/A mixtures and timing while you are driving. A guest account is a passenger driving and a normal user account with usual system privileges is a regular driver. One of these can't change the background/headlights, one can't change some fundamental system operations/engine timing, and one can screw the whole pooch very fast and cause the system/vehicle to crash via violent destruction of critical components.kode-niner wrote:Actually you've reinforced the analogy, but that's a discussion we might have on another day.droppointalpha wrote:I understand your analogy but it seems more than a bit off in its comparison.