SliTaz Forum

Ceel

Administrator

Registered: 2011-04-02

Posts: 1,424

Re: Users become unusable

@ Slizzard,

Tazpkg will never install something you didn't ask for but [c]pam[/c] and [c]systemd[/c] could have been installed as depends of another package.

Did you install [c]drbl[/c] or [c]clonezilla[/c]? Can you post your tazpkg.log?

At the update that followed the [c]pam[/c] installation, the [c]*-pam[/c] packages are automatically installed for the equivallent "normal" packages that are installed. I've seen this behaviour with [c]cups[/c]: [c]epdfview[/c] was installed on my system; during the update that followed the [c]cups[/c] installation, [c]epdfview-cups[/c] has been installed.

So, check if [c]pam[/c] is required by another package:

[c]tazpkg rdepends pam[/c]

If not, you should be able to remove the packages in this order (with tazpanel or from a terminal): [c]systemd[/c], [c]pam[/c] and then the [c]*-pam[/c].

Slizzard

Member

Registered: 2021-03-14

Posts: 23

Re: Users become unusable

Ceel;

Thanks for your continued interest.

You wrote...

Did you install drbl or clonezilla?

*** Both are installed.  I only remember installing clonezilla. I think drbl is another tag-along.

Can you post your tazpkg.log?

*** Yes, it is included at the end of this post.

So, check if pam is required by another package:

tazpkg rdepends pam

*** output of that command below:

  busybox-pam (712K)

  dropbear-pam (356K)

  libcap-pam (40K)

  openssh-pam (5.6M)

  partimage-pam (428K)

  ppp-pam (748K)

  slim-pam (356K)

  systemd (6.4M)

    drbl (7.1M)

      clonezilla (3M)

*** PAM appears to be required by systemd, drbl, and clonezilla.  I think I can do without drbl and clonezilla, but I thought systemd was an essential system file.

At the update that followed the pam installation, the *-pam packages are automatically installed for the equivalent "normal" packages that are installed. I've seen this behaviour with cups: epdfview was installed on my system; during the update that followed the cups installation, epdfview-cups has been installed.

** So if I understand correctly, by "normal" package you mean eg: dropbear instead of dropbear-pam.

*** tazpkg.log is attached.  The April 2022 start date of the log is the day I re-installed Slitaz because of the previous occurrence of the login issue.

Slizzard

Ceel

Administrator

Registered: 2011-04-02

Posts: 1,424

Re: Users become unusable

Hello Slizzard,

Your [c]tazpkg.log[/c] short story (numbers are the line number in the log):

[*][c]busybox[/c] (70), [c]dropbear[/c] (88), [c]libcap[/c] (73), [c]ppp[/c] (264) and [c]slim[/c] (208) are installed during Slitaz installation (1-322)

[*]during [c]clonezilla[/c] installation (484-532)Tazpkg install

[c]openssh[/c] (502), [c]partimage[/c] (505), [c]libcap[/c] (515), [c]pam[/c] (518), [c]systemd[/c] (523), [c]drbl[/c] (525), [c]openssh-pam[/c] (527) because [c]openssh[/c] is a dep of [c]sshfs-fuse[/c] (528), but [c]pam[/c] is now installed.

[*]during [c]zoneminder[/c] installation (536-571), Tazpkg install

[c]busybox-pam[/c] (536) because [c]busybox[/c] is a dep of [c]mysql[/c] (539) but because of [c]pam[/c]...

[*]during update 2023-01-11 (583-874) Tazpkg install

[c]libcap-pam[/c] (603+672), [c]partimage-pam[/c] (605+761), [c]dropbear-pam[/c] (615), [c]ppp-pam[/c] (803), [c]slim-pam[/c] (816) because there are new builds for [c]libcap[/c], [c]partimage[/c], [c]dropbear[/c], [c]ppp[/c], [c]slim[/c] available on the mirror, but [c]pam[/c]...

Then each time you try to update your system, Tazpkg sees that [c]busybox[/c], [c]dropbear[/c], [c]libcap[/c], [c]partimage[/c], [c]ppp[/c] and [c]slim[/c] are not uptodate but can only install the corresponding [c]-pam[/c] packages

So, I see 3 ways to solve this "issue":

[*]remove [c]clonezilla[/c] and all its dependences; this will be a little long...

[*]remove all the [c]-pam[/c] packages (that the solution I suggested at Ravenslock and it seems working); remove [c]systemd[/c] and [c]udev[/c] and re-install [c]systemd[/c]

[*]remove [c]busybox[/c], [c]dropbear[/c], [c]libcap[/c], [c]partimage[/c], [c]ppp[/c], [c]slim[/c], [c]systemd[/c] and [c]udev[/c]; this must be done from a host as described in a previous post because you'll remove [c]busybox-pam[/c] and [c]busybox[/c] (by the way, I edited the post because I forgot to mention to remove [c]pam[/c]); reinstall [c]pam[/c], [c]systemd[/c] and the [c]-pam[/c]

.

*** PAM appears to be required by systemd, drbl, and clonezilla. I think I can do without drbl and clonezilla, but I thought systemd was an essential system file.

SliTaz comes without [c]systemd[/c] by default; [c]systemd[/c] was installed as a dependence during [c]clonezilla[/c] installation.

** So if I understand correctly, by "normal" package you mean eg: dropbear instead of dropbear-pam.

Yes, I could also write " a non-[c]pam[/c] package" ;-)