(old)Puppy Linux Discussion Forum

hitatchi ht72

Is that a travelstar drive - part of the 'deathstar' range?!

Full install to ext4 partiton.

Loaded several pets and checked them out.

Only problem I have encountered is: Fixmenus will not work
# error: could not open display
error: could not open display
#

Otherwise, looks good.
Thanks 01micko for your continued efforts in providing great puppies for us to play with.

majorfoo wrote:Only problem I have encountered is: Fixmenus will not work

I did a fresh full install of slacko-5.4-firefox-4g and fixmenus worked OK. I wonder if you have installed a PET with a bad .desktop file. It would be worth tracking this down.

It seems like recent Puppies are more susceptible to menu problems.

Anyone have a standalone sfs for kdenlive compiled? I know there is a pet but it is huge and I also know that it exists for saluki but I tried it just now and it does not work. On a side note, is there a way to DL packages but not install them, and then use some pet2sfs thing to turn a whole Dir into a sfs?

morgonzola wrote:Anyone have a standalone sfs for kdenlive compiled? I know there is a pet but it is huge and I also know that it exists for saluki but I tried it just now and it does not work. On a side note, is there a way to DL packages but not install them, and then use some pet2sfs thing to turn a whole Dir into a sfs?

Download the pet from the site not via Puppy Package Manager.
If you have Dons right clicks installed, simply right click on the pet and extract here. Make sure you have the pet in an empty directory, just for simplicity, not really necessary. Now you should have a directory something like kdenlive-x.x
In a console type dir2sfs kdenlive-x.x and a sfs will be created.

If the pet contained a pinstall file the sfs file may not work, depending on what action the pinstall needed to take.

Hi.

On a side note, is there a way to DL packages but not install them, and then use some pet2sfs thing to turn a whole Dir into a sfs?

Usually only applications that download with its dependencies can be saved without to install (from the package manager).

For the other applications just install them and then use gnewpet by jpeps to recreate the installed .pet (application - should work also on installed .deb files).

To turn a complete directory into a single sfs use LazY PaDS (combines .pet and .deb files from a directory into a single sfs).

Both are in the Forums Utilities Section.

TheAsterisk's VirtualBox installer virtualbox-4.2.4-x86_src.install.pet works magnificently in Slacko 5.4 PAE K3.4.17. You can get it here:

http://www.silverdollarsolutions.com/Pu ... guide.html

Install the Slacko 5.4 devx and k3.4.17 kernel sources and then run the pet.

Bravo! and Three Cheers for TheAskerisk!

I would strongly recommend against attempting to install VirtualBox from Oracle's run files. I tried several versions that had installed successfully on previous Puppies. The best you can hope for is simple failure (terminated signal -9) on launching the virtual machine, more likely is a complete freeze up requiring a reset with the hardware button on the box. This can lead to file system corruption (in the one case where this happened, I was fortunately able to use Windows XP's chkdsk to repair damage to my FAT32 partition).

See the VirtualBox thread:

http://murga-linux.com/puppy/viewtopic. ... d9e71b6768

for further information on this problem.

I have devx5.4.sfs installed and have installed python separately as well. Python not found still appears when installing Calibre, an ebook management program. I haven't had this problem in a long time. Missing link somewhere?

Thanks for a very nice OS.

Hi All,
I'm sure I saw someone in one of the Slacko5.4 threads asking about keeping the packages that PPM downloads and then installs, but I can't find it.

Anyway here's a .pet with modified downloadpkgs.sh and installpkg.sh that will install the packages but leave the downloaded packages in /root. You just have to move them to where you want them.

Only briefly tested, so use at your own risk.

Cheers, J

EDIT!: If you're happy with this one, fine, but there's a better one down the page.

jrb wrote:Hi All,

Anyway here's a .pet with modified downloadpkgs.sh and installpkg.sh that will install the packages but leave the downloaded packages in /root. You just have to move them to where you want them.

Fantastic! Thanks a lot

Thom

drblock2 wrote:TheAsterisk's VirtualBox installer virtualbox-4.2.4-x86_src.install.pet works magnificently in Slacko 5.4 PAE K3.4.17. You can get it here...
...
Bravo! and Three Cheers for TheAskerisk!

I saw your post in the VirtualBox thread, and snuck in here to take a look. Happy to help, and thanks!

I'm sorry I've gotten a bit behind in the Puppy world- work and family issues and a new (used) car to pay for- but I'll be getting some updated VBox packages uploaded either tonight or tomorrow, including some for Slacko 5.4. (My other packages will see updates very soon, too!)


Puppy Prosperity in Perpetuity!

i made a .pet of gtk-youtube-viewer for the new slacko http://www.murga-linux.com/puppy/viewtopic.php?t=76835

@smokey01
Hi, just want to say thanks for an excellent version of Puppy. I'm using 5.3.3. I thought it would be cool to upgrade to new 5.4, but can't get my savefile from 5.3.3 to work with your newest version. Tried several different ways and will only boot to prompt. I was wondering if it would be possible to make like a delta-x file to upgrade my 5.3.3 to 5.4. I remember some of the earlier versions of I think Lupu had this feature when new versions came out. Could you do this with your Slacko versions? I think that would be really cool if you could and I bet there are a lot more folks out there that would love it also. I have other puppy versions installed on this box, but Slacko-5.3.3 is my daily driver and I don't want to change unless I can easily get the newest version. Thank you for your fine work.
Lee

drblock2 wrote:TheAsterisk's VirtualBox installer virtualbox-4.2.4-x86_src.install.pet works magnificently in Slacko 5.4 PAE K3.4.17. You can get it here:

http://www.silverdollarsolutions.com/Pu ... guide.html

Install the Slacko 5.4 devx and k3.4.17 kernel sources and then run the pet. ...

I see the following:

• PAE Slacko
• Slacko Devx
• VBox pet#1 AND VBox pet#2

Questions

1. Where should the kernel source be found?
2. How should it be installed?

There is a Slackware kernel source reference in the Slacko PPM, but, not the same number you show.

Thanks in advance

Hello gcmartin

when drblock2 wrote:TheAsterisk's VirtualBox installer virtualbox-4.2.4-x86_src.install.pet works magnificently in Slacko 5.4 PAE K3.4.17. You can get it here:

http://www.silverdollarsolutions.com/Pu ... guide.html

Install the Slacko 5.4 devx and k3.4.17 kernel sources and then run the pet. ...

He was refering to this package: virtualbox-4.2.4-x86_src.install.pet
It is near the bottom of the page he linked to, under the heading: Alternative Source-Based Installer

gcmartin wrote:..
Questions

1. Where should the kernel source be found?
2. How should it be installed?

There is a Slackware kernel source reference in the Slacko PPM, but, not the same number you show.

As i suspect you are well aware, Slacko comes in a variety of flavours.
Below is a snippet from the Official announcement

Slacko 5.4 is available with a choice of kernels, 3.2.33 compiled for processors that do not support PAE and 3.4.17 for processors that do. The 4g (non PAE) version comes with a choice of Opera browser or Firefox

So, get the appropriate devx for your particular version (from where you got your ISO image)
then use the Sfs manager (not the PPM) to get the kernel sources.
It should offer the correct file for your version,
one of these two.

• kernel_sources-3.2.33-slacko_4g.sfs
  kernel_sources-3.4.17-slacko_PAE.sfs

Load them by whatever method you prefer,
either the usual way via the BootManager or the alternative way via SFS-Load-on-the-fly

After that has been done, you can install the virtualbox-4.2.4-x86_src.install.pet

Hope this helps
CatDude
.

In regard to the .pet I posted above I've had a request to build in a screen asking where the user wants to save downloaded packages. Unfortunately I'm not very good at building such screens.

But what I have just done is changed the .pet so all downloaded packages are moved into /root/Downloaded_Packages. This folder will be created with your first download. This folder can then be moved wherever you want (maybe /mnt/home) using ROX and then symlinked back into /root. Future packages will then follow the symlink into /mnt/home/Downloaded_Packages.

Besides I've found out with the first .pet that packages disappear if you choose "trim the fat". That doesn't happen with this one.

jrb wrote:
But what I have just done is changed the .pet so all downloaded packages are moved into /root/Downloaded_Packages. This folder will be created with your first download. This folder can then be moved wherever you want (maybe /mnt/home) using ROX and then symlinked back into /root. Future packages will then follow the symlink into /mnt/home/Downloaded_Packages.

Shame on you...in addition to all those good features, it also saves the deps...so you can now add them to your local library.

Thanks.....you do good stuff!

Thom

I just read the review of Slacko 5.4 in the news section of Distrowatch, and what a great review it was.
Great work, Micko1 and team! I have to admit, I agree with Jesse (the reviewer) that this is the smoothest experience I've had with Puppy so far, and I have always liked Puppy a lot more than he.
Also, I tried every version of Puppy I have in my collection of CD's, which may be all of them, and Slacko 5.4 is the only one that would boot into my wife's HP Pavilion G7 notebook with a graphical environment and wireless detection out of the box.

@arcanis

I starting collecting puppy iso's and went a little mad and now have 993 builds

I too am a massive slacko fan and have found that it runs on every machine I try it on without complaint (IBM t21's, lenovo t61, amd dual core desktop, dell p4's and eeepc's)

I have had to migrate back to 5.3.3 but will be back to 5.4 if I can resolve the hdd hang

ally,

Please explain further the "hard drive hang".
IOW, is this during the boot or later on?
And what type of install are you using as well as the type of partition you are installing to?