On Mon 13 Jun 2022 at 19:03:47 (-0400), gene heskett wrote:
On 6/13/22 14:36, Greg Wooledge wrote:
On Mon, Jun 13, 2022 at 01:56:12PM -0400, gene heskett wrote: >>
I appear as user 1000 seem to be stuck behind some sort of a >>
permissions wall. > > SHOW. US.
I got tired of fighting with it Greg, so I did install #32 and installed
gnome_desktop (that was new) and xfce4 during the install, and
now things including the screen colors are back to normal,
I've installed the brother printers and scanner drivers and I can modify t
them by the usual rules. I also set a root pw in addition to adding myself
to /etc/group in the appropriate places.
↑↑↑↑↑
On Thu 07 Dec 2023 at 20:49:19 (-0500), gene heskett wrote:
On 12/7/23 20:24, Greg Wooledge wrote:
On Thu, Dec 07, 2023 at 08:06:52PM -0500, gene heskett wrote:
Thats bug #1. Single for rescue demands a root pw.
This isn't a bug. It's just how things *are*.
People who choose not to set a root password are simply setting themselves
up for this failure. It *will* happen eventually. I strongly recommend
setting a root password on your systems. And you should either *use* it
once in a while, so you don't forget what it is, or else make it the same
as your regular account's password. So you don't forget what it is.
If you *still* choose not to set a root password, then you will need to
know how to get around the issue you ran into. You won't be able to use
single-user mode to rescue your system, so you'll need other ways. There
are two straightforward alternatives: boot from external media (USB or CD
or DVD), or learn how to do the "init=/bin/bash" thing from your boot
loader, which includes bind-mounting /proc and /dev and so on.
.
I've now set a root pw, about 34 chars, so they'll be a couple eons
guessing it AND (horrors) have written it down.
As you set a root password on at least one machine a year ago, can you
just check that you now have a root password on all your machines,
before we have threads like this for each machine, and Greg gets hoarse.
Cheers,
David.