Classic Pup 2.14X -- Updated 2 series

[ttuuxxx]

Ok how did pnethood work for you? I removed the man pages and stripped the bins for samba and its 85MB, I also looked at the help documents, that takes 15mb, but at 85 MB its still a 31MB pet, I compared it to Barry's stripped down version, and well it looks nothing like it. Do you want me to post the 31MB pet of samba? I'll see if I can find a older/smaller version first.
ttuuxxx

[BarryK]

I have also been busy with Puppy2:

http://puppylinux.com/blog/?viewDetailed=00779

Feedback invited about what reasons you still use Puppy2.

[ttuuxxx]

package removed

[ecomoney]

Wow! So much work going into 2 series! This is really going to save such a lot of old kit. I have used 2 series via ecopup (2.15ce based) essentially since it came out, and now I have some experience of 4 series. I was thinking of switching to offering a 4 series based install to my clients...I might have to rethink that.

The reasons I was thinking of switching were basically because I was having a lot of problems with 2 series with wireless...either new usb dongles or laptops with built in wireless....as well as trouble with it not running the latest applications (which this will solve). I was also having problems with newer printers (especially usb ones).

While its easy to get hold of older computers, getting hold of older peripherals is not. Ttuuxxx I hope you will use some of your valuable time to update the number of wireless dongles/cards automatically detected, as well as updating the Apps/CUPS which youve already done.

Ive got such a lot on at the moment getting the Mission cybercafe working so I can get a little money in, and my "company" is being audited at the moment as they are suspicious weve posted no profit in four years! This leaves me little time for testing this hardware-wise ATM.

When my current projects are done, my next move is to return to and finish the Puppy "Phoenix" CE project. This will essentially be an exercise in testing the "just works" part, as well as making improvements to look and feel, installers, file type handling and improving access to the most used/requested larger "end user" applications (i.e. Firefox/OpenOffice). This updated 2 series is looking to be a fine base for this, and if it is I will make sure you are well credited Ttuuxxx, and everyone else who has contributed.

Any news on the updated NTFS driver? And will you be adding an icewm package? Also a sensitive question...will Zigberts pSeries apps work? These seem to be maturing and overcoming their technical bugs/inefficiencies well.

Keep up the good work Ttuuxxx/others

[ttuuxxx]

Keep up the good work Ttuuxxx/others

Well I'll update as much as I can, Its going pretty good now, a few minor quarks, but it would good if we a had one of our network/wireless/Video pro's lend a hand. Other than that, The last thing I'll do hopefully is a Cups package if we had some dedicated testers for it.
ttuuxxx

PS it wouldn't take much to get any of zigberts P products working, looks like I might install pburn, since I didn't get any feedback from the xfburn package I posted.
I already have Search Monkey in, so Pfind isn't needed and also I have LXtask installed so Pprocess isn't needed. Unless your talking about Pwidgets, then all you would need is conky compiled and the pwidgets add on package.
ttuuxxx

[tempestuous]

As one of the contributors/developers of Puppy 214R, I thought I would jump in with some information about Flash and XMMS in Puppy2.

On the Developer Blog entry "The return of Puppy2!" -

Flash is terrible, The glibC is outdated and I can't update that, or it will cripple the who OS.

The issue of glibc is complex. Some knowledgeable person on the forum recently mentioned that for maximum compatibility and stability in Linux all applications and libraries should be compiled under the same version of glibc. We all knew that this was true of kernel modules, and to a lesser extent; Xorg and GTK2. But everything else?
This was something I had always suspected might be true, and I now believe it. But there's no point getting too fussed about complete glibc compatibility. Puppy already has a mish-mash of utilities carried over from earlier versions. I should know: I contributed the wpa_supplicant application used in the current Puppy 4.2. But it was introduced somewhere in the (Slackware 10-compatible) Puppy 3 series.

So back to Flash. I can't speak for the current version of Flash, but back when I was helping pakt and Dougal build 214R we had a similar warning about glibc ... but this was just an installer script warning.
Personally I hate installer scripts anyway. All we had to do was manually extract the Flash binaries and place them in the correct location. Flash then worked fine.

So glibc compatibility is desirable, but not necessarily essential.
More to the point: some modern applications won't compile under older versions of glibc.
But then many modern applications won't compile under older versions of GTK2.
And if you upgrade glibc, and GTK2, then you might as well upgrade the kernel and Xorg! Then Puppy 2 isn't Puppy 2 any more.

Gtk1.2 is still useful for some older apps like Xmms, but it ran buggy on 2.14X so I removed it

There was planned to be an update to Puppy 214R called Minipup216, with a significantly different suite of applications. For this release I compiled XMMS 1.2.11 and pakt tested it quite thoroughly. He didn't find any bugs. It's available as a dotpet here
http://www.murga-linux.com/puppy/viewtopic.php?t=26528

I should point out that the Xorgwizard in 214R was completely overhauled by Dougal. It's the only version of Puppy which offers the correct resolution of 1280x1024 as the default value for my 17 inch LCD monitor.

[mawebb88]

Its the flash or a combo of plugins located in /usr/lib/seamonkey-1.1.16/plugins if you move the plugins to another location then restart Seamonkey you should be fine, It could be one of the other plugins. I'll keep working on it, maybe I might have to recompile Seamonkey, since all the changes to the backend.
I'll try that. Might have to disableutf8.
ttuuxxx

@ttuuxxx
I renamed /usr/lib/seamonkey-1.1.16/plugins to /usr/lib/seamonkey-1.1.16/nbg_plugins and restarted SM and as you predicted sites which crashed SM are now okay. Many thanks
Rgds Mike

[mawebb88]

before trying pnethood could you try this package I made up, I have no idea what I was doing with it it, but it made sense, lol
Never messed with samba before, so bare with me. lol
ttuuxxx

Tried your Samba PET. Unfortunately after installation of this LinNeiighborhood does not open shares when clicking on a machine.

Rgds Mike

[ttuuxxx]

]

I should point out that the Xorgwizard in 214R was completely overhauled by Dougal. It's the only version of Puppy which offers the correct resolution of 1280x1024 as the default value for my 17 inch LCD monitor.

Hi tempestuous, thats kind of what I was trying to say, but you said it way better:), I think the key ingredients of 2.14R which stand out is the kernel, that was used, and Xorg. Both work excellent together. The gtk2 is already updated in this version, Really if we had a modern base, eg Dpup or Upup, with 2.14r kernel/Xorg and no other unnecessary addons like Dpup&Upup both enjoy, eg, Extra Gnome libs, Dbus etc. we would have a winning combo on our hands for older computers. Once I'm finished this project. I'm going to rip apart Dpup and recompile all the Debian parts without the extra libs. and bring the size down, and make a regular pup out of it, Dpup does work excellent on my pc, the best pup for speed so far, well on my modern pc.
ttuuxxx

[ttuuxxx]

before trying pnethood could you try this package I made up, I have no idea what I was doing with it it, but it made sense, lol
Never messed with samba before, so bare with me. lol
ttuuxxx

Tried your Samba PET. Unfortunately after installation of this LinNeiighborhood does not open shares when clicking on a machine.

Rgds Mike

ok just uninstall it and try the Pnethood pet I posted, that should work. Thanks for testing the package, I had my fingers cross with that one
ttuuxxx

[mawebb88]

before trying pnethood could you try this package I made up, I have no idea what I was doing with it it, but it made sense, lol
Never messed with samba before, so bare with me. lol
ttuuxxx

Tried your Samba PET. Unfortunately after installation of this LinNeiighborhood does not open shares when clicking on a machine.

Rgds Mike

ok just uninstall it and try the Pnethood pet I posted, that should work. Thanks for testing the package, I had my fingers cross with that one
ttuuxxx

Ok I tried an uninstall of your Samba PET but it did not cure the LinNeighborhood problem (could not expand a machine to shares). No big deal I just emptied my pup_sav file and rebooted to start again. Installed your PNetHood PET and it works. A couple of observations. PNetHood seems to have difficulty to wake up my LANDisk. I set it to the max scan time (30 sec) and also edited /etc/samba/smb.conf to put workgroup=WORKGROUP2 (my workgrouip name). I can wake it up okay with LinNeighborhood and then PNetHood finds the Samba LANDisk (not usually a problem in 412). Also I still need my CIF code I reported above in order to see files in Rox.
Rgds Mike

[puppyiso]

Maybe it is only me but the seamonkey browser doesn't work.

Besides that, it is the one I wanted for a long long time.

What seems to be a problem?

[ttuuxxx]

Maybe it is only me but the seamonkey browser doesn't work.

Besides that, it is the one I wanted for a long long time.

What seems to be a problem?

Its the flash in the seamonkey browser that doesn't work, if you remove the flash, it works really stable and doesn't crash, I tried about 6 different flash versions from early 9 - 10 beta's included and had the issue, I'll look into recompiling glib/seamonkey again and see what happens.
Really we could probably use Opera and that would work, but I don't want to give up on Seamonkey just yet.
ttuuxxx

[clarf]

Maybe it is only me but the seamonkey browser doesn't work.

Sadly I´m testing 2.14 in vwmare for work reasons (I´ll test it at home as soon as I can).

Seamonkey browser doesn´t work for my either, if I start it from the Network menu it don´t start and I have to kill the process. But If I use the Browser link from the Desktop, Seamonkey starts without problems.

Dillo is there and works great, bad thing it doesn´t have proxy support... Talking about proxy support, I can´t download any package from Package Manager, I had to manually download them. Is there any way to configure a proxy connection in Package Manager?

ThightVNC is super fast and works without problems, but It seems a ripped version, How could I change the connection properties?. (protocols, compression, etc.)

P.D: First time ever that I have no issues with Xorg running in VMWare, great work Dugal.

[mawebb88]

Maybe it is only me but the seamonkey browser doesn't work.

Sadly I´m testing 2.14 in vwmare for work reasons (I´ll test it at home as soon as I can).

Seamonkey browser doesn´t work for my either, if I start it from the Network menu it don´t start and I have to kill the process. But If I use the Browser link from the Desktop, Seamonkey starts without problems.

Dillo is there and works great, bad thing it doesn´t have proxy support... Talking about proxy support, I can´t download any package from Package Manager, I had to manually download them. Is there any way to configure a proxy connection in Package Manager?

ThightVNC is super fast and works without problems, but It seems a ripped version, How could I change the connection properties?. (protocols, compression, etc.)

P.D: First time ever that I have no issues with Xorg running in VMWare, great work Dugal.

SM works for me. The crashing issue was fixed for me with the renaming of the plugins folder (ttuuxxx suggested moving it but I just renamed it). (see earlier post).
Rgds Mike

[cthisbear]

ttuuxxx
" Its the flash or a combo of plugins "

""""""""""

" I renamed /usr/lib/seamonkey-1.1.16/plugins

to /usr/lib/seamonkey-1.1.16/nbg_plugins "

""""""""

I will try mawebb88 fix.

A real pain in the neck Seamonkey crashing.
Really noticeable.
Not having a go....never had this issue in previous pups.

Despite some critics...generally this was a great release.

Pity SM can't be as fast in Windows.
Lost the plot.

Chris.

[clarf]

SM works for me. The crashing issue was fixed for me with the renaming of the plugins folder (ttuuxxx suggested moving it but I just renamed it). (see earlier post).
Rgds Mike

thanks mawebb88 but your solution didn´t work for me. I had problems starting SM from JWC menu, when I click Internet - SeaMonkey web browser, a mozilla process start (using 100% processor) but browser never opened. Instead using Desktop shortcut SeaMonkey browser opened without problems...

Edit: I could solve the problem just editing /root/.jwmrc and changing mozilla for seamonkey, in the Program tap for SeaMonkey web browser.

[ttuuxxx]

SM works for me. The crashing issue was fixed for me with the renaming of the plugins folder (ttuuxxx suggested moving it but I just renamed it). (see earlier post).
Rgds Mike

thanks mawebb88 but your solution didn´t work for me. I had problems starting SM from JWC menu, when I click Internet - SeaMonkey web browser, a mozilla process start (using 100% processor) but browser never opened. Instead using Desktop shortcut SeaMonkey browser opened without problems...

Edit: I could solve the problem just editing /root/.jwmrc and changing mozilla for seamonkey, in the Program tap for SeaMonkey web browser.

or install this, I just changed the .desktop file, now back to flash
ttuuxxx

[clarf]

Edit: I could solve the problem just editing /root/.jwmrc and changing mozilla for seamonkey, in the Program tap for SeaMonkey web browser.

or install this, I just changed the .desktop file, now back to flash
ttuuxxx

Thanks ttuuxxx. After I edited /root/.jwmrc I could call SeaMonkey from JWM menu, but "mozilla" word reappeared in .jwmrc each time I installed or uninstalled a PET. Your pet finally solve the problem changing the SeaMonkey-web-browser.desktop file in /usr/share/applications/, I didn´t know that... It apply to IceWM too?.

[ttuuxxx]

Thanks ttuuxxx. After I edited /root/.jwmrc I could call SeaMonkey from JWM menu, but "mozilla" word reappeared in .jwmrc each time I installed or uninstalled a PET. Your pet finally solve the problem changing the SeaMonkey-web-browser.desktop file in /usr/share/applications/, I didn´t know that... It apply to IceWM too?.

yes it applies to icewm and jwm, if you ever want to change a icon or a menu entry in the /Menu/ you change it in usr/share/applications then when you refresh/fix menus, xdg builds a new menu with all the .desktop files, this works for all .xdg menus, like jwm,icewm etc
ttuuxxx