Re: Password incorrect after name change Home folder

From	"s\|b" <me@privacy.invalid>
Newsgroups	alt.os.linux.mint
Subject	Re: Password incorrect after name change Home folder
Date	2025-10-25 17:22 +0200
Organization	XXII
Message-ID	<mm489vFbajfU1@mid.individual.net> (permalink)
References	(7 earlier) <slrn10fn4c2.2if.dan@djph.net> <mm200fFu9m7U1@mid.individual.net> <10dhem2$31su2$1@dont-email.me> <mm3sq3F9dfqU1@mid.individual.net> <10dik43$3bvfl$1@dont-email.me>

Show all headers | View raw

On Sat, 25 Oct 2025 09:42:25 -0400, Paul wrote:

> On Sat, 10/25/2025 8:06 AM, s|b wrote:
> 
> > That's a bit overwhelming. If we would choose some obscure distribution,
> > let's say Tiny11, I would imagine there would be less support than for
> > instance Linux Mint. That's not good, is it?

> I guess I'm not doing a good job on the analogies.

Could be the language barrier. (-;
 
> As a helper, as an initial skill, you should read up
> on what the "standard procedure is".
> 
> Let's use as an example, someone drops by your help center.
> They say
> 
>    "I have a new printer. How do you install those, anyway ?"

I'm interrupting, but (most) people will say "I have a new printer. Can
YOU install his?"
 
> And you, having read the official page for it, follow the
> procedure, make sure CUPS is installed, and then use some
> dialog pointed at port 631 and start the printer install.
> 
> Now, maybe the printer is a tough one, and requires a
> few minutes search on Google to determine "status on
> July 2025 printer that just arrived". Or, it's an existing
> printer (like the one I bought, an end of line), and
> the driver is mature. The customer leaves happy.
> 
> Six months pass. Something happens to the printer. You're
> not available. They go to the Linux Cafe for help. The helper
> there asks "how did he install it?". The customer replies
> "he used the standard procedure". The helper then has a context
> and the customer does their best to fill in the anecdotal bits.
> 
> That's better than the customer saying, "Oh, s|b hacked it in
> with some custom assembler code, but I don't have the code
> he used." That's going to considerably complicate the situation.
> Who knows what the assembler code damaged while it worked?

This is why it's probably a good idea to cooperate with a Linux Repair
Café. I just want to add that our target group doesn't even have a
printer in most cases. The library (not our organisation) offers
printing documents as a service. (We would have to set up LibreOffice to
save documents that are compatible with Office365, but that is easily
done.)

> There is no end to the complexity a potential situation could raise.
> There would be questions here nobody could answer. They could
> likely answer them when sitting in front of the machine
> and looking around, as sometimes all it takes is one hint
> from a look around, to figure it out. The knowledge tree
> starts with a solid knowledge of the fundamentals underneath.
> It's the same way we learn maths.

That's why we have the KIS principle: Keep It Simple.
 
> Try using the OS with just sudo. The machines are most likely
> to be single user, there won't be situations where john peeps
> at mary's files using sudo.
>
> sudo can be restricted to only allowing "mount" and "umount"
> as privileged activities. That was more likely to be the
> intended usage of sudo in UNIX days. The UNIX box didn't come
> with sudo enabled. You installed it and edited the sudoers file
> with a "blessed" editor. And those are the privileges I
> was given back in the day, all I was allowed was "mount" and "umount".
> Sudo activites were logged, and sent to the administrator.
> (If you were abusing it, someone might notice.)

I made a note and will look into this. Or maybe you have a URL I can
take a look at?
 
> If you did become root, by adding the password, as root you
> could edit the sudoers file and restrict the activities of others.
> 
> As long as the disk isn't encrypted, I'm willing to bet you can
> always exploit it. Using things like chroot, from a boot key.

We wouldn't encrypt the drive. The option comes up during installation,
but I already said to my supervisor that it wouldn't be a good idea for
the people we want to reach. Easier to retrieve data in case of a
problem was the main idea. Keep in mind everybody would still have an
external hdd with backup data of their Windows laptop/PC.

-- 
s|b

Thread

Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 14:43 +0200
  Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-21 12:59 +0000
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 16:10 +0200
      Re: Password incorrect after name change Home folder "Alan K." <alan@invalid.com> - 2025-10-21 11:04 -0400
        Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-21 15:45 +0000
        Re: Password incorrect after name change Home folder Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-23 07:16 +0000
        Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-23 09:06 -0400
      Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-21 15:42 +0000
        Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-22 02:05 -0400
  Re: Password incorrect after name change Home folder "Alan K." <alan@invalid.com> - 2025-10-21 09:24 -0400
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 16:16 +0200
    Re: Password incorrect after name change Home folder Gordon <Gordon@leaf.net.nz> - 2025-10-22 07:51 +0000
  Re: Password incorrect after name change Home folder pinnerite <pinnerite@gmail.com> - 2025-10-21 14:47 +0100
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 16:20 +0200
      Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-21 13:12 -0400
        Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 11:42 +0200
  Re: Password incorrect after name change Home folder yossarian <<nomail@gmail.com>> - 2025-10-21 18:14 +0200
    Re: Password incorrect after name change Home folder Joerg Walther <joerg.walther@magenta.de> - 2025-10-21 18:22 +0200
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 22:55 +0200
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 11:43 +0200
      Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-24 09:50 -0400
        Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 17:21 +0200
          Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-24 22:41 -0400
            Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 13:31 +0200
      Re: Password incorrect after name change Home folder yossarian <<nomail@gmail.com>> - 2025-10-24 17:07 +0200
        Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 13:33 +0200
  Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-21 13:08 -0400
    Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-21 23:08 +0200
      Re: Password incorrect after name change Home folder Chris Elvidge <chris@internal.net> - 2025-10-22 12:32 +0100
        Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-22 08:46 -0400
        Re: Password incorrect after name change Home folder Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-23 07:13 +0000
        Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 11:47 +0200
          Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-24 10:49 +0000
            Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 15:53 +0200
              Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-24 14:47 +0000
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 20:48 +0200
                Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-24 23:03 -0400
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 14:06 +0200
                Re: Password incorrect after name change Home folder vallor <vallor@vallor.earth> - 2025-10-25 12:52 +0000
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 16:40 +0200
                Re: Password incorrect after name change Home folder Chris Elvidge <chris@internal.net> - 2025-10-25 14:31 +0100
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 16:46 +0200
                Re: Password incorrect after name change Home folder vallor <vallor@vallor.earth> - 2025-10-25 17:39 +0000
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-26 17:02 +0100
                Re: Password incorrect after name change Home folder yossarian <<nomail@gmail.com>> - 2025-10-26 17:44 +0100
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-27 21:07 +0100
                Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-25 09:42 -0400
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-25 17:22 +0200
                Re: Password incorrect after name change Home folder lisa <not.in.use@home.invalid> - 2025-10-28 14:22 +0100
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-29 19:35 +0100
                Re: Password incorrect after name change Home folder lisa <not.in.use@home.invalid> - 2025-10-30 09:30 +0100
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-30 15:28 +0100
                Re: Password incorrect after name change Home folder Dan Purgert <dan@djph.net> - 2025-10-25 13:27 +0000
                Re: Password incorrect after name change Home folder [OT] "s|b" <me@privacy.invalid> - 2025-10-25 17:04 +0200
                Re: Password incorrect after name change Home folder Gordon <Gordon@leaf.net.nz> - 2025-10-26 22:51 +0000
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-27 21:34 +0100
                Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-27 18:57 -0400
                Re: Password incorrect after name change Home folder [OT] "s|b" <me@privacy.invalid> - 2025-10-29 19:40 +0100
                Re: Password incorrect after name change Home folder Monsieur <Monsieur@notreal.invalid> - 2025-10-28 15:05 +0100
                Re: Password incorrect after name change Home folder [OT] "s|b" <me@privacy.invalid> - 2025-10-29 19:48 +0100
          Re: Password incorrect after name change Home folder Chris Elvidge <chris@internal.net> - 2025-10-24 14:54 +0100
            Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 17:33 +0200
              Re: Password incorrect after name change Home folder Chris Elvidge <chris@internal.net> - 2025-10-24 17:52 +0100
                Re: Password incorrect after name change Home folder "s|b" <me@privacy.invalid> - 2025-10-24 20:55 +0200
              Re: Password incorrect after name change Home folder Gordon <Gordon@leaf.net.nz> - 2025-10-26 22:04 +0000
          Re: Password incorrect after name change Home folder Paul <nospam@needed.invalid> - 2025-10-24 11:08 -0400
  Re: Password incorrect after name change Home folder Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-23 00:20 +0000

csiph-web