Its a pet. It runs a pinstall script. I like the sfs I made.
Basicly I have a sfs i call mbuild. Inside of this is all the stuff I like to run when building stuff/depends/etc. I now do all my compiling from ram mode no save file.
vs a pet i have to install every time.

Right Clicks PET runs a bunch of rox memes etc.
I like the simple method of making a .desktop file and then declaring Hidden=true. This way it does not load to the taskbar.
However with my version a symbolic link to of the .desktopfile '/root/.config/rox.sourceforge.net/OpenWith/.inode_directory/' It will produce a right click option for directories in ROX with my icon i declared in the desktop file. No screwing around with rox.

Right Clicks PET does not have a make sfs option. I know it has a pet option. but the build scripts don't have the make md5 option.

I wrote in checks I like for user ease.

#Cecks if hdir2sfs is installed and or in the propper dir
#If not then it tells usr what ta do
#check that dir2pet is installed
#check that mksquash is installed

and allot more checks with warnings and what to do if a package is missing or a file fails etc ++++.

I don't know if there is a package of this that works on LH64
again ill start sorting on that in a few weeks.

I'll be looking forward to that, thanks!

Meanwhile, this is a rushed project I'm doing to fill a gap left by someone else - is there a ready-for-LH64 video editor that can get it done - even if less optimal than openshot?_________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
TahrPup64 & Lighthouse64-b602 & JL64-603

Its a pet. It runs a pinstall script. I like the sfs I made.
Basicly I have a sfs i call mbuild. Inside of this is all the stuff I like to run when building stuff/depends/etc. I now do all my compiling from ram mode no save file.
vs a pet i have to install every time.

Right Clicks PET runs a bunch of rox memes etc.
I like the simple method of making a .desktop file and then declaring Hidden=true. This way it does not load to the taskbar.
However with my version a symbolic link to of the .desktopfile '/root/.config/rox.sourceforge.net/OpenWith/.inode_directory/' It will produce a right click option for directories in ROX with my icon i declared in the desktop file. No screwing around with rox.

Right Clicks PET does not have a make sfs option. I know it has a pet option. but the build scripts don't have the make md5 option.

I wrote in checks I like for user ease.

#Cecks if hdir2sfs is installed and or in the propper dir
#If not then it tells usr what ta do
#check that dir2pet is installed
#check that mksquash is installed

and allot more checks with warnings and what to do if a package is missing or a file fails etc ++++.

Meanwhile, this is a rushed project I'm doing to fill a gap left by someone else - is there a ready-for-LH64 video editor that can get it done - even if less optimal than openshot?

There is a openshot.sfs for fatdog64 620 that seems to work, don't know for sure because I've never used openshot before.
Works in fatdog64 620 not Lighthouse602b2 but if it's a rushed project you could install fatdog620 and get it done.

@Edoc, I don't remember who helped me, but I seem to remember that I used Live AND Kirk made an updated version of Kino. I also used Kino, but seem to remember that it was slow, but may have worked for a family video I edited.. Kino is built-in to LightHouse. Have you tried it for your project?

Meeki wrote:

... As for audio editing out background noise. I use Audacity http://audacity.sourceforge.net/

I don't know if there is a package of this that works on LH64
again ill start sorting on that in a few weeks.

This package, Audacity, can be gotten via the Update Icon on the desktop.

Further, here's a dumb question: Is there a tool to do PET2SFS and SFS2PET where. say. someone can drag a PET or an SFS to its dialogue box and have it convert?

Curious_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

@Edoc, I don't remember who helped me, but I seem to remember that I used Live AND Kirk made an updated version of Kino. I also used Kino, but seem to remember that it was slow, but may have worked for a family video I edited.. Kino is built-in to LightHouse. Have you tried it for your project?

Further, here's a dumb question: Is there a tool to do PET2SFS and SFS2PET where. say. someone can drag a PET or an SFS to its dialogue box and have it convert?
Curious

Naww its good question.

SFS2PET = yes
PET2SFS = kinda works

So pets can have install scripts or uninstall scripts. These are made and run for all sorts of resons. chown or set file RW permissions things like that. Or basicly any thing you want to run in a bash script when you install.

Now I know what your thinking just make the PET2SFS load these scripts into Startup with a check to see if they have been ran before. Well that would be nice but some pet makers make their install scripts check for the pet file. Hell ive seen one that checks that the pet file was installed.

Well as you can see a ton of stuff that must happen in pet will not carry over to SFS 100% of the time.

I guess that a guy could make a PET2SFS that checks for an install script.
OR do what I do and just make SFS's then if someone needs a pet its no prob

Oh and I got LAMP (Linux, Apache, MySql, PHP) installed and working in LH64. ... Just got webmin working too! ... .

Webmin is one of my favorites on mainline Unix/Linux distros. So many great management functions to control subsystem configurations and behavior. And, its interface is consistent no matter the distro that its used on.

But, I seem to remember several years ago, where Barry or someone explained that Puppy was not structured in its file system to be consistent with Webmin. Further Webmin in a "spot" desktop is somewhat of a leap in my understanding of how to make use of this root level management tool. "Usermin" I understand and can see as a "spot" user desktop use.

Questions

Did I understand wrongly that Webmin would have issues in Puppy?

Should a thread be opened on "Webmin in 64bit Puppy" so that issues with management features, that may exist, can be available?

Webmin is such a great tool_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

But, I seem to remember several years ago, where Barry or someone explained that Puppy was not structured in its file system to be consistent with Webmin. Further Webmin in a "spot" desktop is somewhat of a leap in my understanding of how to make use of this root level management tool. "Usermin" I understand and can see as a "spot" user desktop use.

Questions

Did I understand wrongly that Webmin would have issues in Puppy?

Should a thread be opened on "Webmin in 64bit Puppy" so that issues with management features, that may exist, can be available?

Webmin is such a great tool

Webmin does have issues in puppy. Depends on what your trying to do with it.
As it stands right now I have it in control of Apache, MySql, and PHP.

I got sidetracked after that point as making all the other options in webmen working with puppy is not the goal. It will be nice but more of an added extra.

After I got It all working after many many many tries...... from late apr to now Ive been using the same builds from then.

Right now I'm compiling the latest release of MySql for it. not that I have tons of notes and tweek commands to work from.

Should a thread be opened on "Webmin in 64bit Puppy
I don't think so at this point. Lets see how far i get with it first.

"spot" desktop is somewhat of a leap in my understanding of how to make use of this

Welcome to my reality months ago. spot is one of the least documented areas of puppy. main reason I see for this is that users don't see its use. Fatdog really brought it into the forefront. But still Users of puppy even those capable of compiling stuff dont tend to compile things that should use it. (web servers, or any thing that's listing on a open port)

spot is a user without root, so when you make packages that run from spot they get angry when they cant access a dir or write to them. You cant go chown-ing around Setting access to stuff for spot. Example : chown -R spot /root/spot/lamp/mysql ya just gave control of your entire lamp to spot. ya have to be more surgical and only give permissions to files or specific directorys. Ontop of all this many files that i need are outside of spot to protect they system. I've really thought about the install of LAMP in LH64 and how it should be setup.

also I wanted the lamp to sit in spot where users can access what they want instead of all over the system so I got 99% of it in /root/spot/lamp/*.* minus all the depends.

I also spent some time making dirs make sense for end user and not the IT guy. An example of this is the MySql Data is in /root/spot/lamp/mysql/mysqldatabase and only shares another folder there of mysql5.

All of this adds to the headach of the build. see my cmake im using to build Mysql right now.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum