(old)Puppy Linux Discussion Forum

Pmount is fully functional with libc6_2.11.2-10_i386 installed in Puppy Linux 3.01.

Pmount will only launch--but not mount--with this libc installed in Puppy Linux 4.12 and 4.31.

So I've tested the 3.01 Pmount shell script with 4.12 and 4.31 (and this libc).
Everything works fine...at least so far...

Attached:
Pmount shell script from Puppy Linux 3.01.
(Updated 12/20/2013: now a .pet.)

Dewbie wrote: Pmount will only launch--but not mount--with this libc installed in Puppy Linux 4.12 and 4.31.

After glibc upgrade in puppy 4.31 pmount works if you run it in terminal with not fatal errors. I have edited /usr/share/applications/Pmount-mount-unmount-drives.desktop in this way:
Run fixmenus after the changes. Now pmount will work.

watchdog's fix (above) also works with 4.12.

.

simargl wrote:

Why don't you give a try to other newer Puppy versions if you think that Precise is slow or too big.

Some of us like playing with the old stuff to keep it going.
(and to see what we can get away with... )

And you can find smaller distributions than are easier to use than Puppy, for example Slitaz

"Easier" is a relative term, since you would have to start out again as a beginner...

.

Slitaz can't be the lite Arch Linux, as Arch Linux is crap, unstable, bloated, and uses systemd (which is bloatware itself).

Slitaz, at least doesn't require your system to break when a major upgrade is done (but Arch does).

.

@simargl

Maybe rather than being a troll here and f***ing up the forum saying how puppy linux is shit and attacking those who say they have problems with your alphaOS, maybe you can be constructive. This is why forums are set up.

Now don't get me wrong alphaOS is okay, but you you don't take kindly to suggestions. A common request that is made is support for broadcom BCM4313 and you completely ignore them. A good developer would take into consideration of those with very good suggestions.

PS: For those with broadcom, the only to get it to work in alphaOS is to switch the alphaOS kernel with one from Precise/Slacko, which does take some work.

PS 2: I sense that another user "rivalry" is coming. There is already one with gcmartin vs. Q5sys. I don't want one to start but sadly trolls are a cancer that infect every community and they have to deal with that from time to time.

Back to glibc upgrade discussion...(I hope)...

I believe a glibc upgrade can provide benefits.

The fixes posted on page 3 will only work with 4-series.
They will not work with Wary.
Edit: see below

Dewbie wrote:The fixes posted on page 3 will only work with 4-series.
They will not work with Wary.

In my wary 5.5 install pmount is not broken after glibc upgrade and all seems to work. Glibc upgrade breaks only locale in wary and the fix is to put in /etc/profile:

watchdog wrote:

the fix is to put in /etc/profile:

Code: Select all

export LC_ALL=C

Thanks...which line does it go in?

Dewbie wrote:watchdog wrote:

the fix is to put in /etc/profile:

Code: Select all

export LC_ALL=C

Thanks...which line does it go in?

I have put the line at the end before the end of the file. I have to say that in my install I upgraded jwm by compiling the 688 snapshot. There are more recent upgrades at:

http://www.murga-linux.com/puppy/viewto ... 31&t=83949

EDIT: I confirm. I did some trials with a fresh install. Installing:

1)libc6_2.11.3-4_i386.deb
2)dbus (PPM)
3)dbus-glib (PPM)
4)service-pack_5.5TO5.5.1_wary5.pet
5)jwm upgrade at snapshot 688

and putting "export LC_ALL=C" in /etc/profile as described and rebooting, pmount works ootb.

OK, thanks...followed your directions, but no luck.

They will not work with Wary.

I tested with the Warys that I have (5.1.1 / 5.1.4.1 / 5.2.2), assuming that it applied to all of them.
Would've helped if I was more specific.

I edited the SFSes, stripped out all 2-series SeaMonkeys and replaced them with BK's SeaMonkey 1.1.18 from 5.1.4.1.
So no need for the dbus stuff.

And obviously the service pack wouldn't apply either.
Plus, yours might have newer libs.

I have resurrected my wary 5.3 install with glibc upgrade and I got pmount working after installing jwm2-755-w5c.pet from the link above, correcting locale by "export LC_ALL=C" in /etc/profile and rebooting. I have not earlier versions of wary.

thank you guys, tested in 4.31 with the vi edit recommended, and this works in terminal as a nice tool. I will go ahead and add this to puppylinux431.com

Appreciate the efforts to make the good stuff better.


Kent C.

Uh-oh, just uncovered a strange bug :

I converted libc6_2.11.3-4_i386.deb to a .pet using dejan555's deb2pet.

This caused /lib/libc.so.6 to link to /lib/libc-2.10.1.so.
(instead of /lib/libc-2.11.3.so, as it did in the original .deb)

Consequently, Pmount worked.
(The upgrade usually breaks it--hoses the locale.)
But SlimBoat didn't.

On the other hand, this is not a problem with the older libc6_2.11.2-10_i386.deb.
(/lib/libc.so.6 links to /lib/libc-2.11.2.so, whether .deb or .pet.)

So if you're upgrading these libs in pre-4.3 Puppies (which won't install Debian packages natively), then convert the older .deb to a .pet and use that one instead.

In Feb 2016 a serious bug was found affecting glibc 2.9 to 2.22. There is a patch. Where can we find a patched 2.11?